Alignment Is A Contact Sport
Prime Mover Advantage - Episode 8: Alignment isn't agreement. It's shared context that travels.
Prime Mover Advantage - Episode 8:
Alignment isn’t agreement. It’s shared context that travels.
The conference room had changed over the past week.
What started as a blank whiteboard and Sam’s pointed questions had become something denser — the Strategy Flywheel on the main board, redrawn twice since the first version.
Next to it, a leadership cadence they’d been designing together: how decisions would flow between James, Rachel, Paul, and Elijah.
Sam was already there when James arrived. But something was different. His bag was packed. Laptop case zipped. Coffee cup rinsed and upside down on the counter.
“Before we get started,” Sam said, “I need to tell you something.”
He looked at James. “You don’t need me anymore.”
Rachel started to object, but Sam raised a hand.
“You built this.” He nodded toward the walls — the flywheel, the leadership cadence, Decision Architecture as their territory, the operating rhythm they’d been pressure-testing all week. “The work on these walls is yours. Not mine.”
James didn’t move. Rachel, Paul, Elijah — all watching him. Every question they’d been directing at Sam all week was now looking for somewhere else to land.
“What do we do first?” Elijah asked.
Not to Sam. To James.
Sam grabbed his bag. “I’ll leave you to it.”
He walked to the door. No handshake. No lingering. Just a man who’d built the ladder and recognized that the person climbing it had found footing.
At the door, he paused. Turned back.
“The flywheel isn’t a framework you explain. It’s how you operate.” He let that land. “Alignment doesn’t come from understanding — it comes from contact. Real decisions, made together, under real pressure.”
Then he was gone.
The room held its silence. Elijah adjusted his glasses and studied the flywheel on the whiteboard.
James looked at the empty doorway a moment too long. Then he turned to his team.
“Week one goal,” he said. “Prove we can practice what we’re claiming. Not perfect. Functional. Show ourselves we can do this before we try to teach anyone else.”
Rachel leaned forward. “What’s the first decision?”
James almost smiled. Not because it was easy. Because she’d asked the right question.
“Kedaris. The call is tomorrow at two. Do we pitch capability or product?” He looked around the room. “Let’s decide it together. Using the flywheel. Right now.”
Constraints Reveal the Real Strategy
Paul opened his laptop. Elijah pulled out his notebook. Rachel already had her notes from the week.
“Positioning,” James said. “What’s the transformation story for Kedaris? From what we learned in discovery, Lisa’s team sees opportunities closing before they can act. Not lack of data — lack of decision capability.”
“So the pain is judgment speed, not decision quality,” Elijah said. “They’re not making bad decisions. They’re making slow ones.”
“Which means the transformation is becoming a high-velocity organization,” Paul said. “Not because they decide faster. Because the right decisions happen without waiting for permission.”
“Prioritization. What matters most in tomorrow’s call?”
“Proving we understand that transformation,” Paul said. “Not listing features.”
“Process. How do we structure the call?”
Rachel was already thinking. “We don’t pitch. We diagnose. Ask Lisa to describe a recent missed opportunity. Then show how Decision Architecture would have changed the outcome.”
“Performance. How do we know if the call worked?”
“She commits to the beta,” Elijah said. “Four weeks.”
“People. How do we mobilize for this?” James looked around the room. “Who’s on the call, and what’s each person’s role?”
“Rachel leads the diagnosis,” Paul said. “I map the architecture to their workflow. Elijah listens for the technical gaps.”
“And you hold the frame,” Rachel said to James. “You’re the one who has to make Decision Architecture feel like something we live, not something we sell.”
James stepped back. The whiteboard still had Sam’s handwriting on half the framework. James’s handwriting covered the rest. He could see exactly where one ended and the other began.
Paul checked his watch. “Twelve minutes.”
The room was quiet.
“We didn’t need an alignment meeting,” Elijah said. “The context was already loaded.”
“Positioning. Customer understanding. Priorities,” Rachel said. “We were already working from the same architecture—” She stopped. Looked at James.
“Each of you,” James said. “With your teams. Today. Don’t explain the flywheel. Use it. Pick a real decision. Work through it. Let them experience what we just experienced.”
“What if it doesn’t work?” Paul asked.
“It won’t. Not smoothly. Not the first time.” James could still hear Sam’s voice. “Alignment is a contact sport. The only way to improve is practice.”
The team scattered — Rachel already making notes, Paul heading for the door, Elijah lingering a moment at the whiteboard before following.
The practice had begun.
Customer Pull Sets the Pace
James and Rachel sat in the small conference room. Laptop open. Video call loading.
Lisa appeared on screen.
“Thanks for making time,” James said. “I know your calendar—”
“It is,” Lisa said. “So let’s get to it. When we spoke last time, you asked me a question nobody else had asked — what we were trying to become. I’ve been thinking about that.”
“So have I,” James said. “You told me the visibility was incredible but the decision-making part hadn’t changed. That stuck with me.”
“It should have.” No edge, just precision. “You want to know what we’ve tried? I’ll save you the discovery call version. Process redesign firm first. Mapped every workflow, every approval chain. Beautiful documentation. Nothing moved faster.”
“Then a change management consultancy. Culture workshops. Leadership alignment offsites. My team liked each other more by the end of it. Decisions still took the same amount of time.”
“Then yours. Dayanos.” “My team loved the product. Adoption was strong, which almost never happens with tools we bring in. We could see what was happening across every function in a way we never could before.”
“But seeing wasn’t the problem,” James said.
“No. It wasn’t.” Lisa paused. “We were still spending weeks aligning on what to do with everything we could suddenly see. The coordination nightmare didn’t go away — it just got better lighting.”
Rachel glanced at James. He didn’t flinch.
“So three different approaches,” he said. “Process, culture, and our own product. And none of them solved it.”
“The process people optimized the wrong layer. The culture people treated symptoms. And you — you gave us incredible visibility into decisions we still couldn’t make fast enough.”
Lisa leaned forward. “So when your team reached out about something different — decision velocity — I wanted to know if that’s a new slide in the same deck, or if something actually changed.”
“Something changed.”
“What?”
“Us.” James met her eyes. “After we spoke, I couldn’t unhear what you said. We stopped building a platform that shows you what’s happening and started asking why organizations can’t act on what they already see.”
Lisa studied him. “I told you that a week and a half ago.”
“I know. And it took me longer than it should have to hear it.”
The room shifted. Not a pitch anymore. A conversation between two people who’d already been honest with each other once.
“Here’s what I keep coming back to,” Lisa said, quieter now. “We’re not slow at decisions. We’re slow at recognizing when a decision is even needed. By the time someone flags it, the opportunity is gone.”
“You’re not making bad decisions,” he said. “You’re making them too late.”
“Exactly.” The first crack in her skepticism. “So. What’s your pitch?”
“A question.” James leaned back. “What if the problem isn’t your decision-making process? What if it’s your decision-making architecture?”
“What’s the difference?”
James glanced at Rachel, who pulled up the simple diagram they’d built that morning. “Process is how you run meetings, who approves what, how information flows. Architecture is what sits underneath all of that — the shared understanding of who you serve, what matters now, what you’re optimizing for.”
He was finding the words as he spoke. “When that context is already present, decisions happen at the speed of opportunity. When it’s not, every meeting starts at zero.”
Lisa studied the diagram. “I’m listening.”
“Your teams are smart. Your data is good. But every decision requires rebuilding context from scratch. That context doesn’t travel between meetings, between teams, between weeks. So your organization can’t move any faster than its slowest alignment cycle.”
“And you’ve built something that changes that.”
“We’re building it. Right now.” James paused. He could feel Rachel tense beside him — they hadn’t rehearsed this level of honesty. “I won’t pretend we’ve been doing this for years. We started practicing it last week. But the results are already visible in how we work.”
Lisa studied him for a long moment.
“You’re telling me you’re running this on yourselves. That your own organization is the proof point.”
“We wouldn’t ask you to operate differently than we operate ourselves.”
A silence. Rachel sat very still, watching Lisa process.
“What kind of commitment?” Lisa asked.
“Four weeks. First week, we baseline your current decision velocity — measure where you are. Weeks two and three, we install the operating practice in your leadership meetings. Real decisions, real pressure — not a workshop, not a training. Your team making actual calls using shared context. Week four, we measure what changed.”
“If it doesn’t work?”
“Then you have a clear diagnosis of why your organization can’t move at the speed it should. That’s valuable either way.”
“Four weeks is significant for my exec team.”
“Then start with your leadership team only. If the diagnostic doesn’t reveal anything actionable, we stop there.”
Lisa tapped her pen against the desk. Once. Twice. Then set it down.
“That’s actually reasonable,” she said. “When would we start?”
“Next week. You’d be our first external proof point.”
“I’d want to baseline before we change anything. Measure our current meeting decisions, cycle times, the whole picture. I need to see the before so I can trust the after.”
“Absolutely.”
Lisa almost smiled. “Okay. Let’s do it.”
The call ended ten minutes later. Baseline sessions scheduled. Four-week commitment confirmed.
Rachel closed the laptop. “You didn’t pitch.”
“No.”
“You described how her organization would operate. Not what we’d deliver.” She paused. “And it was true. Every word of it.”
Shared Context Beats Shared Calendars
Friday afternoon. The leadership team gathered in the conference room.
“Before we scatter for the weekend,” James said, “I want to try something. We’ve been running the flywheel for a week. Any wins — top of mind. What worked?”
Paul went first. “Feature scoping. I started by asking who’s going to use what we’re building and what their experience needs to look like. My team pushed back — ‘We already know what we’re building, why are we starting there?’”
He shook his head. “But by the end of the session, the feature we’d been debating for three weeks resolved itself. Not even the one we’d been arguing about — a different feature entirely, better scoped and with a clearer purpose. One session instead of three.”
“What changed?”
“Starting from the people using the product instead of the backlog. Once we had their outcomes in the room, half the arguments disappeared.”
James turned to Elijah.
“Architecture review,” Elijah said. “Forty minutes instead of two hours. We stopped asking ‘what’s the cleanest way to build this’ and started asking ‘what does the customer need to decide faster.’ Turns out the platform’s decision architecture was optimizing for the wrong input — feeding the system data it couldn’t act on. Once we saw that, the approach was obvious.”
“Rachel?”
“We killed the one-pager we’d been circling on for a week.” She said it without hesitation. “Replaced it with a diagnostic for Lisa. Demonstrate Decision Architecture rather than describe it. The positioning work we did before the Kedaris call made it clear — we don’t need to explain it. We need to show it.”
James nodded slowly.
“What about friction? What didn’t work?”
“None of it was smooth,” Paul admitted. “My team’s still skeptical. They did the exercise, but I wouldn’t say they’re bought in.”
“That’s fine,” James said. “Buy-in comes from results. They’ll see it in the next sprint.” He leaned forward. “What else? Anything from Kedaris prep?”
Rachel nodded. “Lisa mentioned something in our prep call yesterday. Kedaris isn’t just slow at decisions — they’re slow at recognizing when a decision is needed. Opportunities pass before anyone flags them.”
“That’s different from what we assumed,” Paul said. “We thought the bottleneck was alignment. But if they’re not even identifying decision moments—”
“Changes how we approach the baseline next week,” Elijah finished.
“Good,” James said. “What else?”
“’Context that travels,’” Paul said. “That phrase kept coming up when I explained our approach to my team. They connected immediately — ‘we rebuild context every meeting’ was their exact complaint.”
He paused, something turning over.
“There’s something happening here. The way we’re starting to operate — it’s not organized around features or functions anymore. It’s organized around how the customer moves through change.”
He didn’t finish the thought. But James noticed him writing something in his notebook.
“’Context that travels,’” Rachel said. “I’ll use that phrase with Kedaris.”
Elijah turned to Paul. “I had a question for your team about whether the authentication timeline affected mobile notification integration. Was going to schedule thirty minutes.”
Paul started to pull up his calendar, then stopped. “Wait. You already asked me about this.”
“In the hallway. This morning. Took two minutes.” Elijah leaned back. “I already knew your team’s priorities from standup. Didn’t need the meeting.”
Paul stared at him. “Did we just skip a meeting?”
“We had the context. Didn’t need to rebuild it.”
“That’s what I wanted to hear,” James said. He stood and wrote on the whiteboard, below Sam’s flywheel diagram:
WEEKLY CONTEXT REFRESH
“Same time every Friday, before we scatter.” He set down the marker. “Fifteen minutes. Everyone shares what they learned.” He looked around the room. “Enjoy the weekend.”
Outcomes Make Believers
Rachel lingered.
The others filed out. She waited until the door closed, then turned to James.
“Got a minute?”
He sat back down.
“I spent yesterday afternoon writing the Kedaris diagnostic,” she said. “The positioning summary. How we’d describe what we’re offering Lisa’s team.”
She paused.
“I didn’t have to exaggerate.” Her voice was steady but quiet. “Do you understand what I’m saying? I sat down to write the story of what we do, and for the first time in — I don’t know how long — every sentence was true. Not stretched. Not dressed up. Not a version of what we hope to become. Just... what’s actually happening.”
James waited. He’d seen Rachel skeptical. He’d seen her resist. He’d never seen her stripped of the armor she wore so well that most people didn’t know it was there.
“Two weeks ago, I wasn’t sure about any of this. New frameworks. Sam’s workshop. The whole Traction Loop concept.” She shook her head. “Felt like another pivot. Another direction change I’d have to spin into something that sounds intentional.”
“And now?”
“Our meeting just took fifteen minutes. And we made more decisions in two weeks than we usually make in two months.” She paused. “But that’s not what got me.”
“What did?”
“When Paul and Elijah solved that integration question in the hallway. No meeting. No calendar invite. No alignment session.” She looked at James directly. “That doesn’t happen here. That’s never happened here.”
James waited.
“I’ve been a marketing leader for eleven years,” Rachel said. “Every single company, every single role — I’ve been handed strategy that’s half-baked and told to make it sound like it’s done. Make the approximate sound precise. That’s the job.”
She looked at James. “This week, when I sat down to write for Kedaris, I didn’t have to do that. The strategy was real. The results were real. I just wrote what was true.”
A pause.
“When I talk to Lisa next week, I’m not describing a methodology anymore. I’m describing what happened to us. That’s a completely different conversation.”
She stood. Straightened her jacket.
At the door, she turned back. “You should reach out to Ramorian.”
Ramorian. The account that started everything.
“It’s early,” James said. “We haven’t proven anything externally yet.”
“You will. Kedaris will work.” She opened the door. “When it does, you’ll want Ramorian to already know you’re different.”
Then she was gone.
James sat alone in the conference room.
Sam’s handwriting on the left side of the whiteboard. His own on the right.
WEEKLY CONTEXT REFRESH written underneath in block letters that were already starting to feel like the room’s permanent furniture.
He opened his laptop. Found the last email thread with Ramorian — months old. David’s polite rejection still sitting in his inbox like a stone.
He started typing.
Hi David — it’s been a while. I know we parted ways, but something’s changed at Dayanos. Significantly. I’d love thirty minutes to share what we’ve been building. No pitch. Just a conversation.
His cursor hovered over Send.
Not yet. But soon.
He closed the laptop. The flywheel on the whiteboard caught the late-afternoon light.
42 days left.
Activity: The Sport Of Alignment
Time: 2 minutes
Alignment isn’t created through presentations. It’s created through coordinated decisions under real pressure.
Think about your last three strategic meetings. How many actual decisions did you make? Not discussions. Not alignments. Not action items. Decisions.
If the answer is less than one per meeting, you’re coordinating around decisions instead of making decisions together.
AI Prompt:
Here’s our current coordination challenge:
[Describe what’s creating misalignment or slow decisions—meetings that circle, decisions that stall, context that doesn’t travel between teams]
Our leadership team includes:
[List roles/functions represented]
The decisions we need to make faster:
[Describe 2-3 recurring decision types that get stuck]
Help me design a 30-minute meeting where:
1. Each person shares ONE insight per category:
- Customer/market: What shifted in our understanding?
- Positioning: How is our story landing?
- Priorities: What matters most right now?
- Process: What did we learn about how we work?
- Measurement: How do we know it’s working?
2. Context refreshes without becoming a status meeting
- Insights, not accomplishments
- What changes how we think, not what we did
3. The meeting enables faster decisions BETWEEN weeks
- Shared context travels through the week
- Cross-functional questions get resolved without scheduling
Design this meeting so it’s:
- **Sustainable:** high value, people show up prepared
- **Coordinating:** Builds shared context
- **Progressive:** Gets better with practice
Show me the structure, including:
- How to open (setting the frame)
- How to move through each element (time per section)
- How to close (what people leave with)
- How to evolve it over the first month