For partnersFor consulting firms, coaches, and PE operating teams.Are you a client?
Decide with evidence · Data to make great decisionsA real leadership question in. One checkable next move out.
The data to make great decisions on the high-stakes people calls inside an engagement: a merger, a system rollout, a bench that has to be ready now. Every judgment carries its evidence, and anyone can re-run it.
- The cutoff is published before anyone sees a score.
- Every judgment is signed and versioned, so the recommendation you made is the one on record.
- You record what happened afterwards, and see how often the calls were right.
Your decision goes in. A move with a deadline comes out.
Seven steps get you from the question you are actually asking to the number you will check against, every time.
You bring the decision, not a survey.
Something like "Can this team run the new system without a stumble?" or "Who is ready for a stretch role now?" That question is what gets measured.
It weights the measurement for that decision.
A merger question weights differently than a promotion question. The engine picks the weighting; you just asked the question.
It measures your people against that decision.
Can they adapt: explore, bounce back, stay steady, reskill. How they work: decisive or careful, fast or steady. How far along they already are on this specific change.
It turns those measurements into one number.
A single readiness score, 0 to 100, for the exact decision you asked about. Not five sub-scores you have to interpret yourself.
It checks that number against a published line.
The cutoff is stated up front, before you see the score. Above the line: proceed. Below it: you know exactly who or what isn’t ready.
It names who crossed the line, and where.
A person, a team, or the whole company. If nothing is below the line, nothing gets raised. No manufactured urgency.
It hands you the move, not just the finding.
A specific action, a target number, and a deadline. Take the move, then check the same score against the same line to see if it worked.
What lands on the sponsor’s desk.
Ready or needs-support
A ready or needs-support call on real people and teams, answering the decision you asked. Not a vague engagement score.
Paired moves
A paired move for everyone marked needs-support: who covers for whom, and the specific thing that unblocks each of them.
Live readiness view
A live readiness view the whole leadership team checks the moves against, kept current while the change is underway.
Rehearsal first
A rehearsal before the real event: the team runs the scenario in a simulation first, so the gaps show up before the stakes do.
Frame the engagement’s decision.
Every engagement decision falls into one of four postures. Each one weights the evidence for what the client is facing.
Grow
Scaling what already works.
“Which managers can run a second location or a bigger team now?”
See how it reads your teamTransform
A large business model or product change.
“Launch the new model everywhere at once, or phase it group by group?”
See how it reads your teamM&A
Buying, selling, or integrating.
“Who makes the calls while things are murky?”
See how it reads your teamBuild
A start-up, or a new unit inside an existing company.
“Is this founding team ready to add its first layer of managers?”
See how it reads your teamThe tools behind every judgment.
Decision Engine
A real leadership question in. One checkable next move out, with the evidence attached.
Judgments register
Every decision on record: what was asked, when, and what it rested on.
Proof reports
A signed, versioned report of a judgment that anyone can re-run and check.
Outcomes and calibration
Record what actually happened, and see how often the calls were right.
Market intelligence
Outside signals about a client’s market arrive in a review queue. You keep only what you approve.
Staleness alerts
A warning when the evidence behind a decision is old enough to need another look.
Works alongside.
See it on a demo engagement.
A 30-minute walkthrough of a demo engagement, from the firm side and the client side.