Discovery: Landing the Discovery+ launch on a CEO-set deadline

James's own role, not an engagement delivered under the Tenhaw banner. It was one of James Rooney's delivery and transformation roles, and he ran the visual rebrand team on the Discovery+ launch for ten months, one of six development teams working to a launch date the CEO had announced. The case study sits on tenhaw.com because the discipline it demonstrates is the one Tenhaw installs today, probabilistic forecasting that leadership can plan and intervene against. We are always clear about which engagements were the founder's roles and which were Tenhaw's, and will walk you through which is which on a call.

By making the risk of missing it visible early enough to act on. On the Discovery+ launch, six development teams had to redesign and merge content for a date announced by the CEO, and the visual rebrand team was badly overloaded relative to the time available. Delivery moved onto a data-driven footing. Story Points were recalibrated to reflect actual capacity, three sprints of Happy, Normal and Sad path forecasts made the probability of missing the date undeniable, and daily recommendations lifted speed and quality. The launch hit its date on both Discovery+ and Eurosport.

Three delivery scenarios put side by side: what happens if everything goes well, what happens at the pace the data says is normal, and what happens if it does not. On the Discovery+ launch these went to the Head of Delivery across three sprints, built on Story Points recalibrated to actual capacity. Together they made the probability of missing the CEO's announced date undeniable. That is what leadership needs. Not a single guessed date, but a range of outcomes it can plan and intervene against.

Not when the forecast is built on measurement. On the Discovery+ launch, three sprints of scenario forecasts made the probability of missing the CEO's date undeniable, and what came back was clarity, not blame. Discovery+ and Eurosport could finally manage delivery under real constraints, and the six-team launch hit its date. What backfires is the alternative, a single optimistic date defended until it collapses. A forecast presented as a range gives leadership time and options to intervene while intervening can still change the outcome.

Because estimates made under deadline pressure drift optimistic, and forecasts built on optimism are fiction. On the Discovery+ launch the fix was to recalibrate Story Points after completion, so they reflected the capacity each team had actually demonstrated and not the capacity everyone hoped for. That recalibration is what made the Happy, Normal and Sad path forecasts credible enough to act on. They were grounded in what the teams had really done, sprint after sprint. Once the numbers reflected reality, the conversation about the launch date could too.

First make the overload a measured fact instead of a feeling. On the Discovery+ launch, the visual rebrand team James ran was badly overloaded relative to the time available, one of six teams working to a fixed date. Recalibrating Story Points after completion, so they reflected the capacity the team had actually demonstrated, turned that overload into numbers nobody could argue with. Once the constraint was measurable, the Happy, Normal and Sad path forecasts kept its consequences in front of the Head of Delivery sprint by sprint. Daily recommendations worked the problem from the other end by lifting speed and quality.

Yes. By the end of the ten-month engagement both the Discovery+ and Eurosport teams could run the forecasting and tracking practices autonomously, without James in the room. That was deliberate, not a side effect. The point of making delivery risk visible is that the client's own people keep doing it once you leave. It is the same standard Tenhaw holds today under the built to leave principle, and the forecasting method itself is published free in The Tenhaw Way, so nothing about it depends on a consultant staying.

Governing an agentic transformation needs what governing the Discovery+ launch needed. Leadership does not want a single guessed date. It wants a range of outcomes it can plan and intervene against. Probabilistic forecasts and confidence intervals tell an executive how likely a programme is to land where it is pointed, early enough to change course instead of holding an inquest. The method carries over intact, because it never depended on what was being delivered. On the Discovery+ launch it turned an overloaded team's demonstrated capacity into three sprints of scenario forecasts the Head of Delivery could act on, and both platforms hit the date.

On the Discovery+ launch, three sprints. That was the gap between putting delivery on a data-driven footing and forecasts that made the probability of missing the launch date undeniable to the Head of Delivery. The credibility came from the inputs. Story Points were recalibrated after completion to reflect actual capacity, so every forecast was built on what the teams had demonstrably done and not on what they had promised. Trust in a forecast is really trust in its data, and three sprints of honest numbers was enough to change how a six-team launch was governed.

No. A hard deadline is when waiting a week between course corrections costs the most. On the Discovery+ launch, daily recommendations to lift speed and quality ran alongside the sprint-level forecasts, so the teams always had something specific to change while there was still time for the change to matter. The forecasts told leadership where the launch was heading, and the daily recommendations were the mechanism for bending that trajectory. Delivery risk made visible early enough to act on it is what made the difference, and a six-team launch hit its date.

It does not have to. It usually does when the squeeze only becomes visible in the last fortnight. On the Discovery+ launch, six development teams had to redesign and merge content for a date the CEO had announced, and the visual rebrand team was badly overloaded relative to the time available. The daily recommendations issued to those teams covered speed and quality together, not speed alone, and they were useful because the pressure showed up early. Story Points recalibrated after completion exposed the real capacity, and three sprints of Happy, Normal and Sad path forecasts put the consequences in front of the Head of Delivery while there was still room to act. Both Discovery+ and Eurosport hit the date.

Yes, and the Discovery+ launch is the case in point. James ran the visual rebrand team for ten months, one of six development teams whose job was to redesign and merge content across Discovery+ and Eurosport. The method does not depend on what the work product is. Story Points were recalibrated after completion to reflect the capacity a team had actually demonstrated, and that measures design and content output as readily as it measures code. The Happy, Normal and Sad path forecasts built on those numbers were credible enough to change how the launch was governed. Both platforms hit the date.

Whoever can move something. On the Discovery+ launch that was the Head of Delivery, who saw Happy, Normal and Sad path forecasts across three sprints, because that was the person who could act on constraints sitting across six teams rather than inside one. A forecast that reaches people with no levers becomes a report, while a forecast in front of someone who can intervene becomes a decision. The teams themselves needed the same information in a different form and got it, as daily recommendations to lift speed and quality. That is something a team can use the next morning, while the date is still reachable.

The incentive to shade a number largely goes away when nobody is being asked to bid one. On the Discovery+ launch every forecast took its input from measurement after the work, Story Points recalibrated to the capacity a team had already demonstrated, so there was nothing to inflate in advance. The other half of it is what the numbers were used for. When three sprints of Happy, Normal and Sad path forecasts showed the visual rebrand team was badly overloaded relative to the time available, the response was daily recommendations to lift speed and quality rather than an inquest. People defend themselves against measures used against them, and rarely bother with one that gets them help.