Answer
What is Embedded Adoption?
Embedded Adoption is the ongoing engagement after a Production Build: monitoring, business-hours support, a weekly operator review, a monthly executive review, one bounded improvement cycle each month and a managed change queue. It has a six-month minimum, and its price is set in the Spec conversation.
What it includes
Embedded Adoption is the third step on the engagement ladder, after the Workflow Spec and the Production Build. It keeps the tool running and keeps it getting used:
- Monitoring of the tool in production
- Business-hours support for the crew and the office
- A weekly operator review with the people who run the workflow
- A monthly executive review with the sponsor
- One bounded improvement cycle each month
- A managed change queue, so requests are collected, ranked and worked in order rather than lost
Why it exists
A tool that is used at acceptance can drift after it. The work changes, new people join the crew and small problems pile up until people start working around the tool. The weekly and monthly reviews catch that early, and the improvement cycle gives each month a fixed, bounded amount of change so the tool keeps fitting the work without turning into an open-ended project.
Price and term
The minimum term is six months. The price is set in the Spec conversation, once the workflow and the tool are understood. Talon Fox responds to monitoring and keeps deployed tools running, and Lorrie Lynn runs the change queue. See how we work for the full ladder.
Questions people ask
How much does Embedded Adoption cost?
The price is set in the Spec conversation, based on the workflow and the tool.
Is there a minimum term?
Yes. Embedded Adoption has a six-month minimum.
Is Embedded Adoption required after a Build?
No. It is one of the options after launch, alongside a keep-the-lights-on arrangement or a formal hands-off handover.