Your reading room
Keep stories for your next steering committee, pick the questions to ask, and print the lot as one pack. It all stays in this browser.
What a kept list looks like
The newest story on three committee topics, with the question each one raises for your own programme. Keep for committee works for you too; the list below fills up in this browser.
- DoorDash's AI agents wrote code cleanups for $4.79 each. DoorDash estimates hours by hand.
Ask: Ask which AI tools already touch your ERP or finance data, including the ones nobody approved.
- Palantir's £330m NHS contract can be cancelled in February.
Ask: Ask which exit clauses your largest software and services contracts carry, and when each can be used.
- Anthropic's Claude helped researchers reach OpenAI staff accounts in three days.
Ask: Ask when systems of this kind in your landscape were last patched, and who confirms it.
Founding reader
Founding reader.
Issue 01 reader
Kept for committee
Nothing kept yet. Every story page has a Keep for committee line under its sources. Open the archive
The question bank
7 topics, 21 questions. They are about your own programme, never findings about a company in the news. Each topic lists the stories that raise it.
Cost and overruns
- Ask for the approved budget and the current forecast on the same scope, side by side.
- Ask which costs sit outside the programme budget today: internal staff, data migration, parallel running.
- Ask who may approve the next increase, and at what amount the programme goes back to the board.
Course changes and go-lives
- Ask which design decisions in your programme would be expensive to reverse, and when each was last reviewed.
- Ask which expected benefits change if the implementation approach changes.
- Ask who owns a decision to change course, and where it would be recorded.
Prices and licences
- Ask when each major software contract renews and what notice period applies.
- Ask which price protections are written into the contract and which rest on a sales conversation.
- Ask what a price rise on that line would do to the run budget, and who would notice it first.
Staffing
- Ask your integrator to name the people on your programme and to confirm which of them are staying.
- Ask what the contract says about replacing key people, and who approves a replacement.
- Ask where knowledge of your configuration is written down, outside the heads of the people who built it.
AI rollouts
- Ask which AI tools already touch your ERP or finance data, including the ones nobody approved.
- Ask what each tool is allowed to change, and who reviews what it changed.
- Ask how the result is measured, and who decides to switch a tool off.
Security and outages
- Ask when systems of this kind in your landscape were last patched, and who confirms it.
- Ask which finance and ERP accounts can be reached from outside, and how each sign-in is protected.
- Ask how long a restore took the last time it was tested.
Contracts and disputes
- Ask which exit clauses your largest software and services contracts carry, and when each can be used.
- Ask what leaving would cost, in money and in months.
- Ask who reads the contract when a dispute starts, and whether they have read it before.
Open the rest of the room
Founding readers see every question in the bank and can print the committee pack. Enter a work email to open issue 01 and the full room in this browser.
Get issue 01: the Zeiss case, for a steering committee
One ERP programme per issue, for the people who run and sign for it. Issue 01 is the Zeiss case.