Programs

Strategy · Facilitator-led

Build, Buy or Partner

One capability decision, evidenced in four documents and defended once, over five weeks.

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.

5 weeks · 5 rooms · Total time 2 hours 30 min

Sign up to continue
Who it's for
Leadership teams of three to seven with one capability decision to make, chaired by the CEO, COO or chief of staff who owns it.
Cadence
5 weeks
Format
Facilitator-led
Program sessions
5

Who it's for

Leadership teams of three to seven with one capability decision to make, chaired by the CEO, COO or chief of staff who owns it.

Output

  • A named real problem, a build, buy, partner or wait verdict with its killer assumption, a partnership go or no-go, and a board report built from both
  • A scored rehearsal of defending the decision to the board, with the moment that earned each score and unlimited attempts
  • For the chair, each document as it completes and a Ren summary ready for the next live session
  • Scored against published frameworks: the Minto pyramid principle and Aristotelian rhetoric; every other document is built from what the team states and pressure-tested by Ren

Program contents

  1. Problem diagnosis — Problem Analysis
  2. Sourcing decision — Make vs Buy
  3. Partnership fit — Partnership Evaluation
  4. Reporting the decision — Board Report
  5. Defending the decision — Presentation Under Pressure

How the program works

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 rooms

Why this program exists

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.

What you'll achieve

  1. A named real problem, tested against what it is costing, with a recommended path and next steps that carry owners
  2. A build, buy, partner or wait verdict reached on the same criteria every time, with the killer assumption and the signal that would show it is wrong
  3. A partnership go or no-go, tested on strategic fit, economics, governance and integration
  4. A board report built from both verdicts, and a scored, rehearsed defence of it, with unlimited attempts

At a glance

Who it's for
A leadership team of three to seven with one capability decision to make: a data platform, a payments function, a sales channel, a manufacturing step. It is chaired by whoever owns the decision, typically a CEO, COO or chief of staff, who drives every room on the shared screen while the team answers. It assumes someone in the team can give rough costs for at least two paths, and that a candidate partner or vendor can be named by week 3.
Cadence
5 weeks
1
Problem diagnosis · Problem Analysis · Read the Recommended Path and Next Steps; check the cause is one the team would recognise
2
Sourcing decision · Make vs Buy · Read the killer assumption and its signal; check every costed path has a floor and a ceiling
3
Partnership fit · Partnership Evaluation · Read the verdict and the governance answer; check it names who resolves a dispute
4
Reporting the decision · Board Report · Read Decisions Requested and Material Risks against the two earlier verdicts
5
Defending the decision · Presentation Under Pressure · Read Lead Argument and Question Response; agree what changes before the real meeting

Session by session

1

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.

2

Week 2: Sourcing decision

Weigh build, buy, partner and wait on the same criteria, and land a verdict with the killer assumption named.

3

Week 3: Partnership fit

Test the named partner path on strategic fit, economics, governance and integration, whatever week 2's verdict said.

4

Week 4: Reporting the decision

Put the decision in front of the board in one document: the KPIs, the exceptions, the decisions requested and the material risks.

5

Week 5: Defending the decision

Rehearse defending the recommendation to a board that has already formed a view, before the real meeting.

One capability decision, evidenced in four documents and defended once, over five weeks.

Sign up to continue
Meet Ren
Your AI strategist
We use essential cookies to keep you logged in and protect your session. Our only optional cookies remember your language preference — we don't track you or collect unnecessary data. Cookie Policy · Privacy Policy

Cookie Settings

Choose which cookies you'd like to allow. Essential cookies cannot be disabled as they are required for the platform to function.

Essential Cookies Always Active
Login sessions, security tokens, and consent preferences. Required for the platform to work.
Functional Cookies
Language preferences, display settings, and last accessed report. Disabling may affect personalisation.
Analytics Cookies
Aggregated, anonymised usage data to help improve the platform. Never used to identify you personally.