03 · IMPLEMENT
Build the decision system, not the tool. Ship the muscle, not the dashboard.
Implementation methodology anchored in adoption from day one, value tracking from week one, and traceability from requirement to test case to live decision.
Three anchors
- 01·
Adoption from day one
Day-in-the-life designs for every decision-making role before configuration begins. UX prototypes co-tested with planners by week six. Enablement materials built alongside the build, not after it. User acceptance becomes a formality because the users helped build the thing.
- 02·
Value tracking from week one
The value case from the Pilot becomes the build’s North Star. Every sprint ships a measurable value increment. We instrument the value tracking infrastructure inside the platform, not in a separate BI tool that nobody updates.
- 03·
Traceability end-to-end
Every business requirement traces to a decision policy, to a configuration artifact, to a test case, to a production decision. When a decision goes wrong six months in, we can trace it back to the requirement that produced the policy that produced it. Most implementations cannot do this. That is why most implementations cannot defend their own value.
How we run it
Two-week sprints. The principal who designed the solution leads the build. We do not separate design from delivery. We do not staff with juniors. We do not subcontract.
Data and integration are not the last workstream — they are the first. Every sprint runs against the customer’s real data from sprint one. We do not discover data issues at user acceptance. We discover them, and fix them, while the design is still cheap to change.
| Workstream | What we do | What most firms do |
|---|---|---|
| Data & integration | First workstream. Real data from sprint one. AI-assisted audit and gap closure throughout. | Last workstream. Real data at UAT. Surprises in cutover. |
| Configuration | Principal-led. Two-week sprints. Same person designs and builds. | Junior-led offshore. Throw-over-the-wall from design. |
| Adoption | Embedded from week one. UX prototypes by week six. | Two-week training course before go-live. |
| Value tracking | Instrumented inside the platform from sprint one. | Promised at kickoff. Built into a BI tool after go-live. Stops getting updated by quarter three. |
| Governance | Decision policies are first-class artifacts. Versioned. Reviewed quarterly. | Configuration buried in master data. Nobody knows what changed when. |