Every Tuesday at 2 PM
Why "aligned" splinters on the way down through the org, and the practice that puts it back together
This piece was supposed to run last Monday. One intervening event ran in its place: the Chappie James portrait removal. It shares the architecture this essay describes, which is part of why next week’s writing returns to social moment. The extra week added the directional vocabulary a Substack reader gave me, the team-learning research I would otherwise not have read, and the opening scene below.
The scene below is anonymized at the operational level. The directive was real. The host government was real. The base opened on a documented date. The names of the command, the directive, and the eventual base are kept out because the mechanism travels regardless, and because the people who sat in those meetings deserve the courtesy of not being narrowed by association. Replace the operational shell with whichever multi-decade plan you have watched arrive in a meeting.
A Project Governance Meeting, 2005
I was a mid-level manager at a Marine Corps logistics command in Japan, reporting to the Chief of Staff. The directive on the table at a project governance meeting was a multi-decade relocation plan. The American side said they were aligned on it. I was taking notes.
What “aligned” meant in that room depended on where you sat.
The Washington headquarters needed it to mean strategic posture. Footprint reduction in one country, force projection from another. A geopolitical claim that the Department of Defense and the State Department could carry into other rooms.
The local command needed it to mean operational logistics. Where the people, equipment, and host-nation contracts would go. Which buildings would close, which would open, which would transfer. Millions of square feet of facilities and thousands of active-duty personnel had to translate the strategic claim into a moving plan.
The host government needed it to mean sovereignty and economic acceptance. Which prefectures. Which workforce. What compensation. Whether the relocation could survive a local election and the next one.
Three readings of one word. All in the room when the directive arrived.
There was also a Japanese phrase I would not have a name for until twenty years later: ashinami o soroeru, “to fall into step.” What the host-government side was doing in the meeting, in retrospect, was holding the pace. Signaling that the footsteps could not run ahead of the local political reality. The American “aligned” pulled up toward false specificity, the agreement we wanted the Japanese side to make. The Japanese coordination pulled down toward leveling, the agreement the Japanese side could actually deliver. Two cultures, opposite directional vectors, same magnet word.
The meeting closed with everyone saying they were aligned.
Eighteen years later, a new base opened.
The C-suite said the words. Every governance meeting for two decades did the meaning repair the Harvard Business Review piece I took up earlier this month treats as a one-time event. The second sentence is the one that finished the base.
The HBR Piece Names the Symptom
The June 10 WDYM Field Guide took up “The False Alignment Trap” by Julia Dhar, Kristy Ellmer, and Philip Jameson in the July–August 2026 issue of Harvard Business Review. The reporting is sharp. The diagnosis is right. Executive teams behave as if they agree on a change when they do not. Four splinter meanings of one word collide at the top. The change program splinters by Friday.
The piece names what happens at the C-suite. It does not name what happens after the C-suite agrees.
The five-step process Dhar and her co-authors outline runs in the boardroom, once, during a defined transformation. Their evidence base is executive teams. Their unit of analysis is the top of the org chart. That is reasonable for a piece written about transformation officers.
It also leaves the harder problem unaddressed.
The harder problem is what the word does when it moves.
What the Word Does When It Moves
Below the C-suite, the slogan arrives without its context.
The executive team has hours of negotiated meaning before “aligned” lands in the all-hands. They watched each other concede. They saw the trade-offs named. They know which version of the word their colleague was actually agreeing to. The slogan, by the time they broadcast it, has a documentary trail behind it.
The team leads who receive the slogan do not have the trail. They have the slogan and a calendar invite for Tuesday afternoon.
By Tuesday at 2 PM, the four splinter meanings the executive team already worked through are back in play, this time among people who do not know each other’s pressure constraints. The regional manager hears “aligned” as the cost-reduction directive she has been preparing for. The IT lead hears it as the system consolidation he flagged in March. The project officer hears it as the headcount freeze she has not been told is coming. The administrative assistant hears it as instructions that need to be on the floor by Friday.
By Friday, four different operational versions of the same word are in motion. Each is being executed in good faith. Each was derived from the same all-hands. Each will produce a different artifact when the quarter closes.
The slogan was the only thing that survived the cascade. Everything else got translated, reinterpreted, or dropped on the way down.
What the Research Says
Gartner’s October 15, 2024 report, based on a July 2024 survey of 473 HR leaders, found that 74% of them said their managers are not equipped to lead change. Another 73% said their employees are fatigued from change. Three-quarters said their managers were overwhelmed by the expansion of their responsibilities.
The same survey found that 75% of organizations had made significant updates to their leadership development programs, and more than half were increasing spending. Mark Whittle, Gartner’s vice president of advisory in the HR practice, put the result in one sentence: “They are not seeing results.” Gartner’s research notes that traditional leadership development methods, seminars and lectures, have a negative effect on development.
That last finding is the load-bearing one.
It says the way most organizations try to fix the cascade problem makes the cascade problem worse. The seminars and lectures are themselves the milestone format the HBR piece describes. A leader is pulled out of the work, attends a development session, returns to the meeting where the slogan still has four meanings, and the meeting still ends with everyone saying they are aligned. The milestone left no installed practice behind.
Amy Edmondson and Jean-François Harvey, in their 2025 Small Group Research paper “Team Learning in the Field,” locate the problem one level below the org chart. They argue that organizational learning is, mechanically, team learning. The unit of analysis is not the company or the C-suite. It is the recurring group that has to do the work together.
Their paper makes another observation worth carrying into this argument. Today’s performing units often do not constitute “a real team” in J. Richard Hackman’s classic sense: stable membership, clear purpose, clear norms. Hybrid work, remote arrangements, contract labor, AI-augmented workflows, and reorganizations have made team boundaries fluid. The cascade problem hits harder when the people receiving the slogan are not the same people from one week to the next.
Stack the two findings. Managers are not equipped to lead change. The teams they would lead through change are themselves not stable enough to absorb the change as a team. The slogan from the C-suite hits a moving target. Of course it splinters.
What Arimitsu Saw
A Substack reader who writes under the name Arimitsu, and who works front-of-house in hospitality, left a note on the Aligned WDYM. The note added the comparative case the argument needed.
In English, “aligned” pulls upward. The word performs an agreement on specifics that the people saying it have not actually reached. Four meanings collapse into one slogan because no one in the room has the time, or the social standing, to ask which one the others meant. The upward pull is toward false specificity.
In Japanese, the equivalent phrase, ashinami o soroeru, “to fall into step,” pulls downward. It carries a leveling pressure: holding back whoever is faster, bringing them to the slower line, letting the footsteps appear synchronized whether or not the substance behind them lines up. As Arimitsu wrote: “even when there’s no substance behind it, simply seeming to face the same direction is enough to let people say the footsteps are in step.”
Same end state. Opposite directional vectors.
The shared lesson is structural. Coordination pressure produces meaning failure regardless of cultural starting point. The American pull rises. The Japanese pull falls. Both arrive at the same place: a meeting that closes on a word with no shared referent underneath it.
Bring that observation back to the governance meeting in 2005. The Washington side was pulling “aligned” up toward strategic posture, faster than the local political reality could support. The host-government side was pulling the coordination down toward what the prefecture could actually deliver. Both sides said they were aligned. Both meant different things. The base eventually opened because two decades of meetings reconciled the up-pull and the down-pull, one Tuesday afternoon at a time.
Installed Practice
The HBR five-step process happens once. Installed practice runs every meeting.
The four sentences from the June 10 WDYM are the unit of installed practice. State the specific decision. Name the owner. Set the deadline. Name the trade-off. Get them visible to everyone before the meeting closes. If the team cannot produce the sentences, the team is not aligned. They discussed a topic. That is a different thing.
Installed means the practice happens whether or not the C-suite has issued a slogan that week. It happens on Tuesday afternoon for the regional manager. It happens on Wednesday morning for the IT standup. It happens on Thursday at noon when the project officer brings her revised plan to the team leads. The practice is the muscle the team builds by repetition.
A milestone trains the executive team to make a transformation announcement. Installed practice trains the team that has to deliver on it.
The architecture has three layers.
The first layer is the meeting itself. Every meeting closes on four sentences. No meeting closes on the word “aligned” alone. The five-dollar fine from the HBR piece is optional. The substitute behavior is not.
The second layer is the decision log. A short written record of what got pinned, by whom, by when, and what got excluded. The log is not for compliance. The log is for the version of the team that exists in three months, after the project officer has rotated out and the regional manager is on parental leave. Future-us inherits the map.
The third layer is the revisit. Every pinned decision has a date attached for review. The revisit is the practice that catches drift before drift becomes failure. Without a scheduled revisit, the team finds out the meaning has drifted only when an artifact ships that contradicts another artifact.
Three layers. Each one ordinary. None of them dramatic. All of them repeatable. The combined effect is that the team builds the capacity to repair meaning on the fly, without waiting for an executive directive that may not arrive.
Scripts for Five Roles
For the leader running the meeting. “Before we close, let’s write what each of us just agreed to do. One sentence per person. Specific verb, named owner, date. If I cannot put it on the board, we have not closed the meeting.”
For the peer who heard four meanings. “I want to check something before we move on. I am hearing three different versions of what ‘aligned’ means here. Can we say out loud which one we are going with for this room, today?”
For the direct report who needs the slogan translated. “I will take the action item. Before I do, what does success look like in two weeks? I want to make sure what I deliver is what you are picturing.”
For the partner across the table from a colleague hearing the same slogan differently. “Tell me how you would describe what we just agreed to. In your own words. I will do the same, and we will see if the two descriptions line up.”
For yourself, when the meeting closed on a word and you are not sure what just happened. Write the four sentences in your notes, before you leave the room. Send them to the meeting owner before end of day. If you got it wrong, you will know on Tuesday morning. If you got it right, you have the record.
Reflection Questions
What was the last meeting you attended that closed on the word “aligned” without producing four sentences? What did your team build the next week?
Where in your organization does the slogan arrive without the context? Name a specific recurring meeting. What would change if the practice were installed there?
If you replace the operational shell of the 2005 scene with your own multi-decade plan, who in the room is pulling the word up? Who is pulling it down? What would the meeting need to do differently to converge?
The Architecture for the Year
A base opened eighteen years after a directive landed on a table in a room I was taking notes in. The C-suite said the words once. The governance boards said the four sentences hundreds of times. The latter is what built the base.
Next week begins a three-part essay that takes this directional vocabulary out of the boardroom. The same upward and downward pulls that show up around “aligned” in workplace coordination show up around other magnet words in civic life. The first part returns to one of the rooms named at the top of this essay. A directive arrived there too. The room closed.
For now, the practice: no meeting closes on “aligned” until four sentences are written and visible. That is the unit. The architecture is the rest.
Jerry W. Washington, Ed.D., is a Marine combat engineer veteran, independent researcher, and instructor at UCI Division of Continuing Education. He writes What Time Binds on Substack.
If today’s essay gave you the architecture, please share it with one person whose Tuesday afternoon meeting closes on the wrong word.
Sources
Dhar, J., Ellmer, K., & Jameson, P. (July–August 2026). The False Alignment Trap. Harvard Business Review.
Edmondson, A. C., & Harvey, J.-F. (2025). Team learning in the field: An organizing framework and avenues for future research. Small Group Research. https://journals.sagepub.com/doi/full/10.1177/10464964251316877
Gartner, Inc. (October 15, 2024). Gartner Survey Finds Leader and Manager Development Tops HR Leaders’ List of 2025 Priorities for Third Consecutive Year. Press release. https://www.gartner.com/en/newsroom/press-releases/2024-10-15-gartner-survey-finds-leader-and-manager-development-tops-hrleaders-list
Hackman, J. R. (2002). Leading Teams: Setting the Stage for Great Performances. Harvard Business School Press.
Arimitsu (June 10, 2026). Comment on “What Do You Mean? ‘Aligned.’” What Time Binds.