Week 1: Problem diagnosis
Establish whether the capability named going in is the real problem, and reach the root cause before any path is costed.
Strategy · Facilitator-led
One capability decision, weighed three ways
Five rooms: four guided documents and one simulation, run by whoever owns the decision, with the leadership team meeting in each room. Documents are built around the team's own decision and the simulation around each participant's role and seniority. Unlimited attempts.
Start programLeadership teams of three to seven facing one capability decision, such as a data platform or a payments function, chaired by whoever owns it.
A five-week program for the leadership team deciding whether to build, buy, partner or wait on one capability, chaired by whoever owns the decision, built on Renatus. Four document rooms and one simulation room · Five weeks, one room a week · Unlimited attempts · Ongoing thereafter.
The team brings the capability problem from set-up, in its own words.
Calibration: the capability being sourced, its strategic role, what building, what buying and what partnering would each look like, and the hardest constraint.
Calibration: the named partner, what the partnership is meant to achieve, what each side gets, how decisions between the two organisations will be made, and what needs to integrate operationally.
Calibration: the period being reported, the company's stage and context, the board's composition, the headline KPIs, where things are off-plan, the decisions requested and the material risks.
Calibration: role title, the audience, named as the board, the industry or sector and a line of working context, with the organisation's website as an option.
A capability decision drifts when nobody owns the evidence: the engineering lead wants to build it, someone has seen a vendor demo, and three months later the board asks what was decided and hears three opinions. This program prepares the leadership team through four structured decision documents and one rehearsal. Ren tests the real problem behind the capability, weighs build, buy, partner and wait on the same criteria, tests the named partner on strategic fit and governance, and builds the board report the decision needs, before the chair defends it to a board member who has already formed a view.
Establish whether the capability named going in is the real problem, and reach the root cause before any path is costed.
Weigh build, buy, partner and wait on the same criteria, and land a verdict with the killer assumption named.
Test the named partner path on strategic fit, economics, governance and integration, whatever week 2's verdict said.
Put the decision in front of the board in one document: the KPIs, the exceptions, the decisions requested and the material risks.
Rehearse defending the recommendation to a board that has already formed a view, before the real meeting.
0% Starting...