Two complete speeches to your own team, one for a good day and one for a difficult one. Names, companies, and numbers are fictional, the mechanics are real. After each speech, you will see why it works. Structure and length for other occasions are explained on the speech to your team page.
Example 1: The team lead at project close
Situation: Friday afternoon at a grocery retailer, 14 people in the room and three on a video call. After eleven months, the till-system migration is complete.
Ten minutes, then the buffet opens. Promise.
This morning at 6:12, branch 312 in Plymouth was the last to move to the new till system. That means Core Switch is done: 312 branches, 1,900 tills, eleven months, zero lost transactions. The old AS/400 in the basement will run until the end of July as a fallback, then it will be switched off. If you want to be there: 31 July, 5 p.m., server room. I will bring a red button that does nothing but looks good.
A few numbers no one outside this room can properly appreciate: 27 releases, 41 nights on call, 14 million migrated item records. And one find that paid for the entire project: Daria spotted a rounding error in the deposit system three weeks before the pilot. Eight tenths of a cent per crate, for years, across all branches: around 90,000 a year. The error was older than the project. Without the migration, no one would have seen it.
Two more names. Tim wrote the rollback script that we needed exactly once, on 3 February in Exeter, when the receipt printers produced nothing except blank lines. We had planned 30 minutes for rollback; Tim’s script needed four. The branch was taking payments again 26 minutes earlier than I had promised the board. And Mel and Jonah took 640 hotline calls in the hardest rollout week. The south regional manager wrote to me that he had never experienced an IT hotline where someone actually picks up. I am passing that praise on here.
What went badly belongs in these ten minutes too. We postponed the pilot twice, and the second postponement is on me: I scheduled the stock-system interface test in week 19 instead of week 4. The lesson is on page 9 of the closing report, and in the next project plan the interface test goes right at the front.
Next week, no meetings before ten, and if you want to take overtime back, enter it and I will approve it as a block. In two weeks we kick off self-checkout. If you want to join that, tell me by Friday. If after eleven months of tills you need to see something else first, tell me that too. It will not harm your career.
Thank you. It was a heavy piece of work, and you carried it. The buffet is open.
Why this speech works: The opening promises a length and then keeps it. For a tired Friday audience, that is worth more than a grand rhetorical structure. Praise names people with checkable facts: date, minutes, finding, number of calls. The team can verify this kind of praise; generic praise only asks them to nod. The paragraph about the speaker’s own planning error sits in the middle of the speech, with cause and consequence, which makes the recognition before it more credible. The ending resolves practical matters, overtime, kickoff, and the option to switch, rather than drifting into pathos. The red button gives the project a tangible end.
Example 2: The CEO after losing the biggest customer
Situation: Monday morning in the production hall of a metal manufacturer with 60 employees. On Friday, the largest customer cancelled the framework contract.
Good morning. The machines are stopped for twenty minutes. This is more important.
On Friday afternoon, Fielding Agricultural cancelled the framework contract as of 31 December. From January, the welded assemblies go to a supplier in Czechia that is 22 percent below our price. Fielding represents 31 percent of our revenue. Some of you have known this since Friday evening from the WhatsApp group. Now everyone has it first-hand. That is the situation, and I will answer the three questions everyone has in mind.
First: could we have prevented it? On price, no. We renegotiated twice, most recently in March. To match the Czech offer, we would have had to quote below our material costs. I would have rejected an order that loses money on every assembly even from a 19-year customer. What we should have done better: notice earlier that Fielding had been building second suppliers for a year. The signs were there. I took them seriously too late.
Second: what does this mean for jobs? Until the end of the year, nothing changes. Fielding orders continue in full, including the October batch. From January, we will be short of capacity equivalent to 14 of 60 roles. My goal is to close that gap by then. I cannot promise today that we will succeed. On 15 October, I will stand here again and give you the status, with numbers.
Third: how do we close the gap? Three tracks, all already moving. The enquiry from Brock Conveyor Systems for stainless steel assemblies: our offer goes out on Wednesday, and the volume would cover about half the Fielding gap. Then the rail audit on 9 September: with welding approval for rail vehicles, we enter a market where the certificate counts more than the last penny, and only one other company in this region has that approval. Third, I am accepting short production runs again, the ones we turned down in the full years. The margin is thinner, but it keeps machines and people in rhythm.
I will not give you a speech about opportunities today. We have lost a customer that was with us for 19 years and whose first order was taken by my father. That hurts. This company lost a third of its revenue once before, in 2009. What helped then was two new customers and eighteen months of discipline on spending. That is the plan, and you now know every number I know.
Questions now, here. And from tomorrow, every day in my office.
Why this speech works: The news arrives in the second sentence, with the two numbers that matter: 22 percent price gap, 31 percent revenue share. Anyone who heard the WhatsApp rumour immediately gets the reliable version. The admission about missing the second-supplier signals costs the speaker something and earns credibility for the plan. All three tracks have a date or weekday, which separates a plan from a hope. The ending avoids claimed confidence and offers a precedent from the company’s own history, one that older people in the hall can remember for themselves.
The pattern behind both speeches
Both speeches treat the team as people who will test every sentence against reality: one with named achievements, the other with open numbers. Both include a paragraph that costs the speaker something: the planning error, the missed signals. And both end with dates instead of appeals. If you are building your own team speech, first collect the facts only your team knows: names, dates, mishaps, numbers. The speech to your team page shows the structure around them, and eloqole turns your notes into a first draft.