The whole room raised a hand.

Seventy-plus people raised their hand to admit they'd learned something about their own work.

Monday covered the decision to hold the meeting. This is what happened inside the hour, and what it told me about where the story usually goes after a QBR.

The idea didn't start with me. In the QBR, the leaders across the table mentioned that a State of the Team hadn't happened in a while. They had just watched the quarter laid out end to end, and they realized, as we did, how broad the combined effort had become. When the people you report to notice that your own team hasn't seen the picture, take the hint.

So we booked an hour and filled a room with seventy-plus people, in person. All 11 section leaders got a slot. Network, platforms, operations, architecture and the security teams each had a leader stand up and tell their own team's part, every one of them in the same format and in five minutes or less.

The promise of the hour sat on one slide, and I'll give it to you as written, because it's the most reusable thing in this piece. What you should leave with. We have a mission and vision. The work we do connects to it. We delivered results in 2026. Our work is measured and has impact. 2027 planning is underway and we know what to expect.

Read those in order and you can see the job the meeting had to do. The first line is the one every organization already claims. The second line is the one almost nobody delivers to the people doing the work, and every line after it depends on that second one holding.

What they told, once you heard all 11 back to back, was the fabric. Combined efforts, processes that had been aligned across teams, and more than 76,000 hours of work, which nobody in that room had ever heard added up in one place. Each team had lived its own share of those hours. The total had only ever existed in a deck built for leadership.

The moment I keep coming back to was a question. The operations team asked the network team about the new network design, the one I wrote about in week 41, which network, security and endpoint planned as one team. You could watch it land in real time. Operations immediately saw the impact of that design and how useful it was for their own work.

Think about what that means. Two teams in the same department, both working the same platform transformation, and one of them got the details of the other's design in a meeting that was supposed to be a recap. That exchange happened because operations finally got to see a piece of work it had been living beside, and once they saw it, they had a use for it.

Near the end, I asked the room one question. Who learned something new here?

The entire room raised their hand, without hesitation.

The feedback afterward came from everyone. One member of the team said it directly. "That was fantastic. I didn't know how much we had accomplished. Thank you for sharing the entire story."

I'd call that hour a win, and it was one. Look at the hands again, though, because they cut both ways. Those were the people who put in the 76,000 hours. They didn't know the whole story either, and until that afternoon nobody had ever handed it to them.

I've started calling this the one-way story. Every planning cycle produces a narrative. Somebody assembles the quarter into something coherent, ties the projects to the strategy, and shows how the pieces support each other. That narrative goes to leadership, because leadership funds the work, and there it stops. The people doing the work get their slice back as a task list with a due date on it.

Nobody chooses this. A QBR gets built for an audience, and the audience is the room that approves the budget, so the story gets shaped for that room and filed when that room is done with it. The meeting that would carry it back down never gets cancelled, exactly. It just stops getting scheduled, which is how you end up with a State of the Team that "had not occurred in a while."

A team that has only ever seen its own fragment will plan a fragment. Hand them the whole story before they write next year's plan, and they start planning for the fabric.

The operations question is where the one-way story shows its real price, and the price runs well past morale. A team that can't see the work around it makes local decisions, and the fabric absorbs those decisions later as rework, duplicate effort, or a design somebody had to explain twice. Operations didn't need a pep talk about the network design. They needed to know it existed in enough detail to use it, and an hour of cross-team storytelling handed them that faster than any architecture review would have.

The leaders in the QBR are part of the pattern too, which is easy to miss. They are the audience the story gets built for, and they still came away realizing for the first time how broad the combined effort was. If the people receiving the full narrative every quarter can be surprised by its size, the people receiving none of it have no chance at all.

This also picks up a thread from last week, and it's line four on that slide. I wrote then that my team, myself included, couldn't yet connect the work to the value and the value to the strategy. The State of the Team didn't solve that, and I won't pretend it did. It did something the metrics work can't do by itself, which is show seventy people how their work connects to everyone else's work. That's the first link in the chain, and you can't measure your way to the second one while the first is missing.

Most organizations treat the all-hands as a morale item. It gets scheduled when there's something to celebrate or announce and cancelled when the quarter gets busy, and when it does happen, it usually runs as the senior leader presenting the deck. The team hears leadership's version of their own work, nods along, and goes back to their slice.

That version is appealing for honest reasons. The deck already exists. One presenter is easier to schedule than eleven. The leader keeps control of the message, which feels responsible when budgets are open and people are nervous about next year. All of that is true, and the result is still a room full of people hearing about their work secondhand.

The version that worked for us split the job. I was the primary presenter and carried the frame, the mission and vision and the five takeaways. The work itself came from the people who led the hours, eleven section leaders each telling their own team's part in front of every other team. That changes who is talking and who is listening. The network team wasn't being summarized by somebody who sat through their status meetings. They explained their own design, and the operations team asked them directly about it. A question like that doesn't happen when one person presents everything, because nobody in the audience owns the answer.

Timing matters more than format. Put the State of the Team between the QBR and the start of strategic planning, while the story is assembled and before anyone starts writing next year's goals. Ours landed in that gap, with budgeting open and department strategic plans just starting. Hold it after the plans are written and it's a retrospective. Hold it before, and it's input.

Give every section leader a slot and one job, which is to tell their team's part of the story in a way the other teams can use. Leave room for questions between teams, because the most valuable minute of our hour was a question that went sideways across the room instead of up to a leader. Write your own version of that five-line slide before you build anything else, and make sure the second line, the work we do connects to it, carries the most weight. Then close with the question about who learned something new. It's a crude measurement, and it's the only one you need for that hour.

The second-order effect shows up in the planning. Our department strategic plans aren't finished, and I won't claim the meeting rewrote them. They are improving as a result, and the feedback is leading to precision of plan. The gross trajectory hasn't moved, and it didn't need moving. Precision is what you'd expect when a team knows what the other ten teams are building and writes goals that fit beside theirs instead of colliding with them.

Where it gets hard is the clock. Eleven leaders in sixty minutes leaves about five minutes each, and we held every leader to the same format. Without that, some leaders will spend their five minutes reading a status report instead of telling a story. Give them a prompt ahead of time and ask what their team's work made possible for somebody else in the room. A leader who can't answer that has found the gap before the meeting did.

The other hard part is the cadence, because "had not occurred in a while" is how every one of these meetings dies. Our next one comes after planning is complete, as the rally around next year's plan, so everyone can see it all again before the work starts.

Next year, schedule it before anyone has to ask why it hadn't happened in a while.