Most delivery methodologies begin with requirements. A better place to begin is with a sentence that will not be spoken for another year: the one the customer's sponsor says to their CEO when the project is finished. Every enterprise technology program eventually gets compressed into that moment, when a vice president takes two minutes at the end of a quarterly review to explain what the investment produced. That account is the victory speech, and it is the only summary of the work that will survive inside the customer's organization. Service providers who write it before the engagement starts differ from those who discover it afterward.
The speech is worth taking seriously because of what it is not. It contains no epics, no story points, no architecture decisions, and no mention of the provider's methodology. It is short, delivered under time pressure, and addressed to someone who was never in the room. What it does contain is a business result stated in a number, a comparison to how things worked before, and a named group of people whose lives changed. It also carries the sponsor's own credibility. That person staked part of their standing on this program, and they are not reporting a result so much as collecting on a bet.
Drafting the speech at kickoff, with the sponsor rather than for them, changes the conversation. The question is simple enough for a first workshop: a year from now, what do you want to be able to tell your CEO about this? Sponsors are rarely asked. They are asked about requirements, integrations, and timelines, all of which are downstream of the answer. Asking directly tends to surface the actual objective, which is frequently narrower than the stated scope and occasionally different from it.
Once written, the speech becomes a north star with unusual practical utility. Scope disputes get adjudicated against it, since a feature either strengthens the sentence the sponsor will say or it does not, and most do not. Sequencing changes, because the components that produce the headline number get built first rather than last. Measurement discipline improves, which is the part teams most often get wrong. A speech claiming a forty percent reduction in cycle time requires a baseline captured before anything was touched, and baselines cannot be reconstructed after the fact. Instrumentation becomes a first-week deliverable rather than a reporting afterthought.
There is a commercial reading, too. A provider who can write the victory speech can usually price the outcome it describes, which is the practical bridge from effort-based billing to outcome-based models (https://alten.capital/blog/from-time-to-outcomes). And as AI absorbs a growing share of delivery labor, the scarce contribution is no longer execution capacity but judgment about which outcomes are worth pursuing and how to prove they happened (https://alten.capital/blog/the-new-agentic-fde). The case study, incidentally, is not a separate marketing project. It is the victory speech with permission to publish it.
The exercise is most valuable when it fails. If neither the provider nor the sponsor can write a speech a CEO would find interesting, the program has a problem that no amount of delivery excellence will solve. Perhaps there is no sponsor with real stakes, or the objective is compliance rather than value, or the number the project can move is too small to mention at that altitude. Those are useful things to learn in week one, rather than month eighteen. The quiet failures are the ones where nobody ever established what success would sound like when someone had to say it out loud.
Alten Capital invests in technology services businesses. Reach out to explore potential partnerships.