Tuesday, 10 a.m. The weekly program call on an S/4HANA rollout: 60 minutes, 12 workstreams.
Each lead reads their status. On track. Two items complete. One date moved a week. Green, green, amber, green.
At 10:52 the program manager raises the one question that needed the whole room: do we start the second mock data load next week, or wait for the client refresh in two weeks? Three people start to answer. At 11 a.m. the call ends, and the decision moves to next week’s call.
By then, starting next week is no longer possible. Nobody chose to wait for the refresh. Moving the decision made it.
Everyone on that call is good at their job. The status was accurate. The meeting did what status meetings do.
Status is a fact. Show it.
Everything read aloud in the first 50 minutes was already written down. It is in the plan, on the board, in the workstream trackers. Dates are easy to get.
So put it where it already lives. Send it as a pre-read to the people senior enough to have it pushed to them. Leave it ready to pull for everyone else. Put it on the screen when the call starts, and don’t read it out.
The question “what changed since last week?” is answered before anyone joins.
A pre-read is only as good as the word “complete”
A pre-read works only if written status means what spoken status means, and the word that slips most is “complete.”
A change gets called complete when the configuration has moved. Nobody has yet looked at whether the training content needs to change, whether the process design document still describes what was built, or whether the test cases still test it.
Give “complete” its checklist: configuration or code moved, test cases updated and run, process design document updated, training content checked. Then a pre-read that says complete can be trusted without anyone asking.
The room has a memory now
Teams records the call and transcribes it. Copilot can read every meeting in a program before the director who owns it has finished her coffee.
So the words spoken in the room are now part of the record, and the question becomes which words are worth adding.
On Tuesday the answer was 50 minutes of status the record already held, and eight minutes of a decision that got made by default.
Spend the spoken time on decisions
Make the agenda a list of open decisions, not a walk through the workstreams. For each one, the chair asks five questions, and the people who know answer out loud.
What has to be true for us to decide?
What else does this impact?
What options did we rule out, and why?
Who owns the decision, are they here, and when is it due?
Any concerns we haven’t heard yet?
Here is Tuesday’s decision, run that way.
What has to be true? The target client has to be refreshed to include the latest configuration changes, and the data extract has to reflect the latest design decisions. The extract we have predates the last two design decisions.
What else does this impact? Every system integrated with SAP needs its master data aligned to the new load, or integration testing fails on mismatched customer and material numbers. The first one affected is the distributor EDI feed for one entity. In this program, “EDI” means four different vendor integrations depending on the company and the country, so name which one.
What did we rule out? Loading next week on the old extract. Data built to an earlier design would not tell us whether the load works against this one.
Who owns it? The data migration lead owns it and is here. The Basis team isn’t on this call, so the cutover lead confirms the client refresh with them by Friday, and the data migration lead makes the call on Monday.
Any concerns? One voice: if the refresh slips, there is no room for a third mock before the freeze.
That took about two minutes. In the room, “EDI” would have been enough, because everyone knew which feed. The second question is where words leave the room, so that is where they have to be exact.
Then check the dependencies
Status shows what each team is doing. It rarely shows what one team is quietly waiting on from another.
So before the call ends, each workstream lead answers two questions, in a sentence each:
What do you need from another team to finish next week’s work, and do they know?
What are you not getting to next week that someone else may be waiting on?
Master data needs the updated reporting requirements by Wednesday. Then the follow-up: from whom? Several teams own a piece of those requirements, and each assumed another was pulling them together.
That is the dependency nobody had written down, because nobody had claimed it.
In the last two minutes, the chair reads back the decisions and the dependencies that were named. Anyone who heard them differently says so while the people who could correct it are still there.
The stand-up version
The same rule holds at the daily stand-up. The board is on the screen, so nobody needs to read it.
Say out loud only what the board doesn’t show. Name the item by its number, not “this one.” Give a blocker its shape: blocked by what, since when, and what would release it.
The two dependency questions work here too, on a shorter horizon: what do you need from someone else today, and what are you not getting to that someone may be waiting on?
What the record holds now
The director asks on Friday what changed in cutover risk. The status was in the pre-read all along. What she finds now in the transcript is a decision with its conditions, a named impact, an option ruled out with its reason, a name and a date, a concern about the freeze, and a dependency nobody had claimed.
Status was always in the record. A meeting can add only what nobody has written down yet.
Two cautions
Report on the work, not the people. Tell everyone what is recorded, what is drawn out of it, and how it is reported. Report by decision and by topic. A transcript read as a log of who said what turns a working meeting into a performance review, and people start talking to the reader instead of to each other.
Ask, don’t infer. It is tempting to let software judge how worried the room sounded. In the EU, the AI Act prohibits systems that infer emotion in the workplace, and the Commission’s guidance ties that to voice and facial expression. The fifth question gets you the same signal by asking for it, and a concern someone chose to state is worth more than one a model detected. Check the specifics with counsel for the countries you operate in.
This week
Take your next status call. Send the status as a pre-read, put it on the screen, and don’t read it out.
Use the time for the two or three decisions that are open, and ask the five questions. Before you close, ask every workstream lead the two dependency questions, then read the decisions and dependencies back.
Then ask Copilot, or whichever AI assistant you use, to summarize this week’s call and last week’s, and put the two summaries side by side.