Corporate parenting logic
Whether the centre adds more value to a business than it costs it, and by what logic. The honest test behind most group restructures and demergers.
The printable canvas and the handoff into Claude Code are part of a paid plan. See what a plan includes. It needs the Claude desktop app on this machine, and your team and the prompt library already installed in that project — we cannot see your disk, so open it there.
What it is
A test of whether a group's corporate centre genuinely adds value to its business units, or merely costs them, applied through Goold and Campbell's three parenting logics. Not which units to keep — that is a portfolio question, answered elsewhere — but whether the centre itself, as currently configured, deserves to exist in its current form.
- Portfolio manager
- A centre that allocates capital and monitors performance, adding minimal cost and minimal help beyond disciplined capital allocation. Right when businesses are genuinely unrelated and need little beyond a capital markets function.
- Synergy manager
- A centre that actively creates value by sharing capabilities, customers or infrastructure across units. Right when genuine synergy exists — and a frequent source of self-deception when it is claimed but does not.
- Parental developer
- A centre with a specific transferable parenting skill — turnaround expertise, brand-building, a particular kind of deal-making — that it applies across otherwise unrelated businesses.
- Value added versus value cost
- Named separately for each unit: what the centre specifically contributes, and what it specifically costs in management time, decision friction and constrained autonomy.
- Fit test
- Whether the group's actual parenting logic — however it is described in the annual report — matches what the units genuinely need. A mismatch is a strong signal for restructuring.
How you run it
- Name the group's actual parenting logicPortfolio manager, synergy manager or parental developer — as the centre genuinely behaves, not as it is described in the annual report.
- List what the centre specifically does for each unitCapital allocation, shared capability, a transferable skill. Specific enough that a reader could check whether it actually happens.
- Price what the centre costs each unitNot just an allocated overhead charge — the management time, decision friction and constrained autonomy the unit genuinely bears.
- Test fit for each unitDoes what this unit needs from a parent match what this centre's logic actually provides. State the mismatch plainly where one exists.
- Draw the implicationWhere fit fails, the implication is restructuring the centre's role, the unit's ownership, or both — named rather than left as an observation.
The prompt
Run this tool in your own Claude
The short prompt starts your partner against the library on your disk. The long one carries everything with it and needs nothing installed.
Your playbook
It lands in the earliest stage this tool suits. Move it on the Playbook page.
You’ll need
- What the centre currently does for each business unit, stated specifically rather than generically
- What each unit would look like standalone, or under different ownership
- Honest cost of the centre — not just its budget, but the management time and decision friction it adds
You’ll end up with
- A named parenting logic — portfolio manager, synergy manager or parental developer — for the group as it actually operates
- Per-unit verdict on whether the centre adds more value than it costs
- Where the answer implies restructuring the centre's role or the portfolio itself