Writing the adoption decision
A written decision prevents the most common reason adoptions stall: nobody knows who decided what.
Contents
Why write it down
- It names an owner who can make the next decisions.
- It records the evidence, so the decision can be explained later.
- It lists the risks you accepted, so nobody is surprised by them.
The template
ADOPTION DECISION
Date: <date>
Decided by: <name and role>
Owner of the site: <name and role>
What we adopt: Exponential <version line, e.g. 6.0.x>, served by <engine>, on <database>
For: <the sites and purposes>
Why: <three reasons, with the scorecard total>
Evidence: <proof of concept write-up, scorecard, answers to questions>
Who runs it: <ourselves / hosting company / partner / 7x>
Budget: one-time <...>, per year <...> (from the budget worksheet)
Timeline: <launch target, measured from rehearsals>
Accepted risks: <risk - how we reduce it>
Not included: <what we decided not to do now>
Revisit if: <conditions that would reopen the decision>After the decision
- Share it with everyone who will work on the adoption.
- Move to Planning.
- Review it at the first annual review (Annual value review).
Related pages
- Deciding
- Project brief template
- Project templates
- Risks and how to weigh them
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.