Landing the Discovery+ launch on a CEO-set deadline
A launch date announced by the CEO, six teams, and a rebrand workstream that did not fit the time available. We made the delivery risk visible early enough that somebody could still act on it.
- development teams coordinated
- 6
- launch hit under a fixed deadline
- On time
- platforms: Discovery+ and Eurosport
- 2
We made delivery risk visible early enough to act on it, getting a six-team rebrand across the line on time.
- Client
- Discovery
- Duration
- 10 months
- Sector
- Media and streaming, United Kingdom and Europe
- Engagement shape
- Delivery leadership and probabilistic forecasting under a fixed, publicly announced deadline.
What we walked into
Discovery+ had a hard launch date announced by the CEO and six teams that needed to redesign and merge content. The visual rebrand team Tenhaw was asked to run was badly overloaded relative to the time available.
The work itself
Run against The Tenhaw Way, which is published in full and free to adopt without engaging us.
We moved delivery onto a data-driven footing, recalibrating Story Points to reflect actual capacity after completion rather than optimistic estimates. Across three sprints we presented Head of Delivery with Happy, Normal, and Sad path forecasts, made the probability of missing the date undeniable, and issued daily recommendations to lift speed and quality.
Nobody was told the date was impossible. They were shown what would have to be true for it to be possible.
What came out of it
- development teams coordinated
- 6
- launch hit under a fixed deadline
- On time
- platforms: Discovery+ and Eurosport
- 2
Discovery+ and Eurosport got the clarity to manage delivery under real constraints and hit the launch. By the end of the engagement both teams could run those forecasting and tracking practices autonomously.
Why a buyer usually lands on this one
Written for the person arriving mid-programme with a question.
The board has announced the date. Now what?
This is the most common shape of the AI programmes we are called into. A date exists, it was announced by someone senior, and the delivery evidence for it does not. The instinct is to re-plan. What actually works is to stop presenting a single date and start presenting a distribution.
Here that meant three forecasts every sprint, happy, normal and sad, built from measured capacity rather than optimistic estimates, put in front of the Head of Delivery until the probability of missing was undeniable.
Why this matters more for an agentic programme, not less
An AI programme director is asked for a date on work carrying more uncertainty than a rebrand: model behaviour shifts underneath you, integration surfaces turn out to be unowned, and the evaluation criteria are often still being argued about in week three. A single date on that is fiction, and everyone in the room knows it.
A range with a stated confidence, updated weekly from real throughput, is defensible to a board and, more usefully, actionable. It tells you which week to add a person, cut a scope item or move the date, while moving it is still cheap.
What this engagement does not claim
The same caveats the case studies hub carries, narrowed to this engagement so nothing here is a surprise to your analyst.
- 01
Not an AI engagement.
Delivery, forecasting and coordination. No models, no agents, no AI in the deliverable.
- 02
We ran one workstream, not the launch.
Tenhaw was asked to run the visual rebrand team and to make delivery risk visible across the programme. The launch was landed by six teams and the organisation around them.
Probabilistic forecasting and confidence intervals are exactly what leadership needs to govern an agentic transformation: not a single guessed date, but a range you can plan and intervene against.
Programme & Delivery Management
We will govern the programme whether or not we are building any of it. £18k–£35k / month · Programme duration.
What that engagement coversOther engagements
Sector first, because that is the next question. All twelve are on the hub, grouped into the two we would call AI work and the ten we would not.
Roughly a year of stalled work, rebuilt as a working proof of concept in two weeks
12 months → 2 weeks, prior build effort rebuilt as a working proof of concept
Standing up the delivery engine behind a £40bn hydrogen business case
£40bn, business case underpinned
Turning erratic global delivery into something the business could plan around
3, regions: UK, USA, Singapore
Want the same thing, in your organisation?
A 30-minute call with James Rooney. We will tell you which parts of this we have done before and which we would be doing for the first time, and you will leave with a rough scope either way.
Most organisations start with a fixed-price Agent-Readiness Audit · £30k–£90k · 6–8 weeks