i.Deadline
There's a real decision date
A contract, budget cycle, business commitment, or project checkpoint creates a useful deadline.
Decision sprint
Get one big technology decision resolved.
A decision sprint gives leadership the smallest useful record to choose, assign an owner, and move on.
Use it when
The decision is contained, but it affects more than one team.
This fits one live decision: a vendor renewal, platform direction, risk response, investment gate, sourcing decision, or project go/no-go. It's not a substitute for broader discovery when the real issue is a whole portfolio, not one decision.
ii.Comparability
The options can actually be compared
We can frame the choice without pulling your whole technology environment into scope.
iii.Authority
Someone with authority is at the table
The recommendation can reach a person who can actually accept the trade-off.
How it works
From open question to an owned next step.
Frame the decision
Define the business consequence, who owns the decision, the timing, and what's explicitly out of scope.
Build the evidence
Separate confirmed facts from assumptions, vendor claims, open questions, and constraints.
Compare the real options
Check who's responsible for what, total effort, risk, how reversible it is, dependencies, and commercial terms.
Record the recommendation
State the preferred option, the trade-off you're accepting, any dissent or uncertainty, the owner, and the next decision point.
What you get
A decision record that outlasts the meeting.
Exact deliverables are agreed in scope. A focused engagement usually needs only what makes the choice easy to check and hand off.
01
Decision statement
The question, the consequence, who decides, and the deadline.
02
Criteria and evidence
What a responsible option has to satisfy, and what evidence exists today.
03
Option comparison
Trade-offs, dependencies, who's responsible for what, risk, and open questions.
04
Recommendation and next step
The chosen direction, the uncertainty you're accepting, the owner, the first action, and when to review it.
How it's priced
Scope follows how complex the decision is - not a per-user rate.
A written scope covers the decision, who's involved, the evidence needed, the output, timing, exclusions, and when the engagement ends. Price reflects the actual work, not an arbitrary seat count.
- What drives the scopeHow many options, how much evidence, who's involved, the deadline, and how deep the review needs to go.
- When it growsThe question turns out to be a roadmap, operating-model, or recurring leadership problem rather than one contained decision.
- When it's doneThe person with authority can choose, and a named owner can carry the next step.
Start
Bring the decision that matters but has no clean frame yet.
The decision brief tool can help you state the question before you share any context with us.