Assess it before you are committed to it.
An assessment of a new tool, supplier or architecture before you sign, so you know the residual risk and the conditions under which accepting it is reasonable while you still have leverage.
What triggers this engagement.
A decision is imminent and reversing it later will be expensive, or a tool is already spreading through the organization without having been vetted.
Adoption is rarely a yes or a no. It is a yes with conditions, and the conditions belong in writing before you sign.
Where the boundary sits.
A scope that is not written down is a scope that grows. Ours is agreed before work starts and it is printed in the report.
- The proposed tool, supplier or architecture as it would actually be deployed
- The data that would flow into it, and where that data would rest
- The supplier's own posture, on evidence rather than on their brochure
- The conditions that would make the residual risk acceptable
- Commercial negotiation and pricing
- Systems the change does not touch
- A guarantee of approval, since the answer is sometimes no
- The proposal, contract or documentation under consideration
- Access to whoever is sponsoring the change
- The date the decision has to be made
Scoped to your decision date wherever the date allows a defensible answer. If it does not, we say so rather than rush the work.
What you receive.
One document, layered so that a board and an engineering team can both work from it.
Is this the right scope for you?
Tell us the decision you are facing. If a different engagement fits better, we will say so before you commit to this one.