Changes

From two scattered tools — a Power BI dashboard for the pipeline and a separate system for reviewer assignments — to one product where SPD's data, documents and roles live together.

Pipeline overview Before
+
Reviews Assignment System Before
=
Module 02
Pipeline
Assignments
Module 02 · Operational Support Now

Before
Two tools
Pipeline in Power BI · assignments elsewhere
Now
One product
Pipeline + assignments in one screen
Q3 2026
Why a single product
A single source of truth
Convergence for data, EZShare for documents. No duplicate Excels.
From aggregate to detail
Leadership sees the big picture; each module owns its operation.
Each module goes live at its own pace
Modules roll out separately, without holding each other back.
What it unlocks
01
Roles & reviewers built in
Reviewers (SDV/SQR) assigned and monitored; Front Office management strengthened.
02
Documents & visibility
Document review and follow-up simplified; status and workload transparent at a glance.
03
Integrated pipeline
Pipeline initiated directly from the Tracker — consistent information, less operational overhead.
01
Integrate from day one
Building features as separate pieces and stitching them later costs more than designing the integration upfront. We learned this rebuilding the bridge between pipeline and assignments.
Scope & architecture
02
Test early, not at the end
Testing only after developers finish makes rework expensive and slow. Smaller, earlier rounds catch problems while they are still cheap to fix — and keep the team aligned with users.
Process & cadence
03
Map the process before you build
Coding before the process is clearly mapped produces errors that look like bugs but are really design gaps. We now map roles, steps, and document standards before development starts.
Discovery first
04
Use AI to iterate on design
AI-assisted prototyping puts a working concept in front of users in days, not weeks. We validate with SDV and SQR, adjust, and only then hand it to developers.
New way of working