Every system we build is held to one standard: 70 percent of the target team uses it every week by day 90. This article explains where that bar sits in an engagement and how the Adoption Mile reaches it.
The deliverable of a Forge Sprint is a live production system. A system in production is not the same as a system in use. The 70 percent weekly-active bar by day 90 is the standard the firm builds to, and it is written into the engagement from the start.
The Adoption Mile
Adoption is run as its own phase inside Forge Scale, on a monthly retainer scoped to the system. It has three named parts:
- A named operator who owns adoption.
- A weekly working cadence with the team.
- A live adoption scoreboard tracking weekly-active use.
Shipped is not done. Used is done.
What the scoreboard shows
The scoreboard tracks weekly-active use against the 70 percent bar. Everyone reads the same number every week. When the number stalls, the weekly cadence exists to find out why and fix it.
The bar also shapes what gets built. A system aimed at 70 percent weekly-active use has to fit the workflow the team already runs. That constraint is set during the Forge Diagnostic, before a single build week is priced.