Your Operating Rhythm Is Your Strategy
Prime Mover Advantage - Episode 4: Strategy that lives in documents is already dead.
Prime Mover Advantage - Episode 4
The four questions that eliminate coordination overhead
“I’m willing to fund a recovery. I’m not willing to fund nostalgia.”
Sarah’s email waited when James opened his laptop at 5:42 AM. He’d sent the board update the night before: three-day strategic workshop with an advisor, full leadership team offline. What he hadn’t written was the advisor’s fee came from the same budget they’d earmarked to win back Ramorian.
Sarah saw it anyway. She always did.
He read the line again. Recovery, not nostalgia. They’d lost their biggest revenue line, and his answer was to pause sales, pause shipping, and put everyone in a room.
The board would read this the same way Sarah did. As a bet on whether the past could still pay rent.
James closed the laptop and got dressed.
The drive to the office seemed shorter than normal. No podcasts. No calls.
Rachel’s voice from last week kept looping instead. She’d said it at the door, after everyone else had left the war room. Not hostile. Honest. She needed something to build on, and all James had given her was a whiteboard sentence and an instinct he couldn’t yet explain.
Customers don’t need better visibility. They need better decisions.
He still believed it. Seven conversations had confirmed it. But believing something and being able to build a company around it — that was the gap he was driving toward.
The parking lot was nearly empty at 6:40 AM. One car he recognized. Sam’s.
Inside, the building was quiet. James pushed open the war room door. Sam stood at the whiteboard, uncapping markers, shifting chairs into a half-circle. Not decorating. Setting constraints.
“You’re early,” James said.
“This is the work,” Sam said, still writing. On the far right side of the board a structure was taking shape— a structure James couldn’t read yet from the doorway.
“How’d the board take it?”
“Sarah thinks I’m paying for nostalgia.”
Sam capped the marker and turned. “And are you?”
James dropped his bag. “My team will be here in twenty minutes, expecting answers I don’t have yet. Rachel needs new messaging she can use. Paul’s guarding the Q4 roadmap. Elijah wants to know if three months of engineering just changed direction.” He pulled out a chair. “And I got less than eight weeks to recover the Ramorian revenue.”
“Good,” Sam said. “If this were settled, we’d already be arguing about execution.”
James looked at the board. His sentence on the left. Sam’s framework forming on the right. The empty space between them was where the next three days would get decided.
“What do they need to see first?” James asked.
“What keeps stalling.” Sam tapped the whiteboard — not James’s sentence, but the empty space below it. “They know something’s wrong. You told them last week. But knowing the problem isn’t the same as seeing the mechanism. Today we make the mechanism visible.”
“And if they push back?”
“They should. We’re not starting with opinions. We’re starting with how their meetings actually run.”
Sam looked at James directly. “What information shows up too late. Where decisions slow down and who feels it. By lunch, they won’t be arguing about whether this matters. They’ll be arguing about what to fix first.”
Voices in the hallway. Rachel, rescheduling a client call. Paul too low to catch. Elijah asking why the room was booked through Wednesday.
James straightened in his chair.
Sam picked up a fresh marker.
The door opened.
What Your Calendar Already Knows
Rachel came in first, tablet under her arm, already scanning the whiteboard. Paul followed, coffee in one hand, phone in the other — he pocketed it when he saw Sam. Elijah paused at the door, noticed the chairs rearranged, the whiteboard half-filled, James already seated.
“This isn’t a status update,” Elijah said.
“No,” James said. “Three days. Starting now.”
Rachel sat down but didn’t settle. “Three days offline while we’re hemorrhaging from the Ramorian loss. What are we building?”
“The reason we lost Ramorian in the first place,” Sam said. He didn’t introduce himself further. They’d met last week. “James told you the insight. Customers need better decisions, not better visibility. You gave him room to pursue it.”
Rachel’s eyes flicked to James. That was her challenge from last week, coming back through someone else’s mouth.
“Let’s start with something concrete,” Sam said. He turned to the whiteboard. “Tell me about the last product decision Dayanos made. Not a feature tweak. A real decision — resources committed, direction chosen, people moved.”
Paul leaned forward. This was his territory. “Three weeks ago. We decided to rebuild the analytics pipeline. Six engineers, eight-week commitment. Major investment.”
“Walk me through how it happened,” Sam said.
“I brought the proposal to the leadership meeting. Usage data showed customers were hitting bottlenecks in the existing pipeline. Engineering had been flagging performance issues. I made the case, we discussed it, James approved it.”
“How many meetings before the approval?”
Paul thought. “The initial proposal meeting. Then a follow-up with engineering to scope it. Then a budget review with finance. Then back to leadership for final sign-off.” He paused. “Four meetings over two weeks.”
“And what did each meeting actually do?”
“The first one surfaced the problem. The second tried to scope a solution. The third checked whether we could afford it. The fourth made sure no one objected.”
Sam wrote on the board:
Meeting 1: Surface the problem
Meeting 2: Scope the solution
Meeting 3: Confirm affordability
Meeting 4: Confirm priority
“Four meetings. Two weeks. One decision.” Sam turned back to the room. “Now here’s the question that matters. Paul, when you brought the initial proposal—the usage data, the bottleneck analysis—what did you know about why customers were hitting those bottlenecks?”
Paul frowned. “They were running queries the pipeline wasn’t designed for. Volume had outgrown the architecture.”
“That’s the technical diagnosis. What were they trying to accomplish when they hit the wall?”
Silence.
“Were they stuck in the middle of something urgent? Were they trying to prove progress to their own leadership?” Sam let each question land separately. “What were your customers trying to do when your pipeline got in their way?”
“I don’t...” Paul sat back. “I had the usage data. I didn’t have that context.”
Sam looked at Rachel. “When Paul brought the pipeline proposal to leadership, what was your first question?”
“How does this affect our messaging timeline,” Rachel said immediately. “I had a product update campaign scheduled. A major rebuild would push it back six weeks.”
“Did you know why customers were hitting pipeline bottlenecks?”
“No. I knew the campaign calendar.”
Sam turned to Elijah. “When you scoped the rebuild with your team, what drove the architecture decisions?”
“Performance benchmarks. We designed for the query volumes we were seeing, plus projected growth.” Elijah adjusted his glasses. “We didn’t scope for what customers were trying to accomplish with those queries. We scoped for throughput.”
Sam stepped back from the board.
“Four meetings. Two weeks. Three functional leaders. Each one brought real expertise to the table. Paul brought usage data. Rachel brought campaign timing. Elijah brought technical architecture.” He tapped the whiteboard. “What nobody brought was the customer.”
He wrote underneath the four meetings:
Where were customers stuck?
How were they measuring their own progress?
What were they trying to accomplish?
What would have made them move faster?
“Your rhythm just doesn’t carry that context. Your meetings are structured around functional handoffs—product proposals, engineering scopes, marketing schedules, leadership approves. Each person brings their piece. Nobody brings the customer’s journey.”
Paul was staring at the board. “If I’d known customers were hitting the pipeline wall during quarterly board prep—that the bottleneck was costing them credibility with their own leadership—I wouldn’t have proposed the same rebuild.”
“What would you have proposed?” Sam asked.
“Something faster. Targeted. Fix the specific bottleneck they’re hitting during the highest-stakes moment, not a wholesale architecture overhaul.”
“Different decision,” Sam said. “Same team.”
Rachel leaned forward. “And I wouldn’t have pushed back on the timeline if I’d known the campaign could be built around solving that specific pain point. The messaging writes itself when you know what customers are actually stuck on.”
“Different decision,” Sam repeated. He pointed to the four meetings on the board. “Same four meetings. But if everyone walks in already knowing where customers are stuck, how they measure progress, what path they’re on, and what triggers their movement—how many of those meetings do you need?”
Elijah answered first. “The first one. Maybe.”
“Maybe,” Sam said. “Because the scoping meeting happens differently when engineering already understands the customer journey. The budget meeting becomes obvious when the business case is built on customer urgency, not internal metrics. The priority confirmation disappears entirely. The priority is self-evident.”
He drew a line through meetings two, three, and four.
“One meeting. One decision. The difference isn’t speed. It’s context.”
Sam circled the four questions he’d written.
“This is what’s missing from your operating rhythm. Not better process. Not better meetings. These four questions—where are customers stuck, how do they know they’re progressing, what path gets them unstuck, what makes them move—this is the context that turns four meetings into one.”
He set the marker down.
“Your calendar tells you what your strategy actually is. Right now? Endless coordination. Four meetings to do what shared context does in one.”
James was watching his team. Something different from last week. Last week they’d listened politely and asked how. This time Paul was staring at a decision he’d already made and seeing what it was missing. Rachel was connecting the gap to her own work. Elijah was recalculating the engineering investment against a question he’d never been asked to answer.
Systems Beat Heroics Every Time
Sam let the room sit with it. Then he turned back to the board and wrote above the four meetings:
DV = C × (D/M)
Rachel squinted at it. “Please tell me we’re not solving this with algebra.”
“We’re not. We’re naming what just happened.”
Sam continued, “James and I talked about this last week—decision velocity. Back then it was a napkin idea. More context, better decisions.”
He pointed to D/M. “One decision, four meetings. That’s your ratio.”
Paul exhaled. “When you put it that way.”
“Amalakai walks out of most meetings with multiple decisions made. Not because they’re smarter. Because they’re not spending meeting time building context in the meeting.”
Sam moved to C. “Context. The multiplier.”
He gestured to the four questions still circled on the board. “When you walk into a meeting already knowing where customers are stuck, how they measure progress, what path works, what triggers movement — context is high. One meeting handles what used to take four.”
He tapped the formula. “When context is low — when Paul has usage data but not the customer journey, when Rachel has the campaign calendar but not the customer pain point, when Elijah scopes for throughput instead of transformation — every meeting becomes a context-building exercise. You’re spending coordination time on what should already be shared.”
“Zero context, zero velocity,” Elijah said quietly. “Doesn’t matter how many meetings you hold.”
“You can tighten meeting agendas all you want. But if context stays low, you’re just rearranging coordination,” Sam said. “The ratio improves but the multiplier stays near zero.”
Elijah was still looking at the pipeline decision on the board. “We rebuilt the architecture,” he said slowly. “But we never rebuilt the moment that triggered it.”
Rachel was staring at the formula. “So the four questions aren’t just diagnostic. They’re how you raise C.”
Sam pointed at her. “That’s it. The four questions are how you build it. When everyone carries those answers—not in a document, not from a presentation, but as how they naturally think—context becomes high.”
James looked at the whiteboard. His sentence from last week on the left. The four questions in the middle. The formula on the right. Three pieces that hadn’t existed together until this morning.
“We’ve been optimizing D/M,” James said slowly. “Better meetings and tighter agendas. All of it was working on the ratio.”
“And ignoring the multiplier,” Sam said.
“The multiplier is the operating rhythm.” James stood up. “It’s not about running better meetings. It’s about what everyone carries into the room before the meeting starts.”
Sam didn’t confirm it. Didn’t need to. The formula was on the board. The pipeline decision was still underneath it.
Context Before Velocity
The room was quiet for a moment. Not the uncomfortable silence from last week, when James had tried to explain Decision Velocity without the mechanism to support it. This was different. Processing silence.
Rachel broke it first. “So we know the formula. We know our ratio is terrible. We know context is the multiplier.” She looked at the four questions on the board. “But we don’t actually have the answers. Where are our customers stuck? I couldn’t tell you with any precision right now.”
“Neither could I,” Paul said. “I know what features they request. I don’t know what transformation they’re trying to make.”
Elijah was still looking at the whiteboard. “We scoped an eight-week rebuild without asking a single one of those questions.”
Sam nodded. “That’s the gap. You have the diagnostic now. You can see what your operating rhythm actually produces. But the formula only works when the context is real—built from your customers’ actual journey, not assumed from internal data.”
He walked to the far right of the whiteboard where he’d been writing when James arrived that morning. Now James could read it:
Day 1: Where customers are going
Day 2: How they get there
Day 3: Territory you own
“After the break, we start building C,” Sam said. “Not theory. Your customers. Their transformation. The context your operating rhythm should serve.”
He capped the marker. “Fifteen minutes.”
The team stood. Rachel was already on her phone pulling up customer feedback. Paul opened his laptop to the product analytics dashboard, scrolling past the usage metrics to something he hadn’t looked at before. Elijah stayed seated for a moment, studying the formula, then pulled out his notebook and started writing.
James stayed at the whiteboard.
Three layers now. His sentence from last week — Customers don’t need better visibility. They need better decisions. The four questions in the middle. The formula on the right. And Sam’s three-day structure on the far edge, waiting.
They could see the gap.
Fifty-four days to close it.
Activity: The Operating Rhythm Audit
Time: 2 minutes
Look at yesterday’s calendar. Pick any meeting that lasted more than thirty minutes.
Ask yourself: Was this a meeting that produced a decision, or a meeting that coordinated to make a decision later?
Write down what actually happened. Not what the meeting was called. What it did.
AI Prompt:
I want you to help me see whether my operating rhythm is producing decisions or just scheduling them.
Ask me 2 questions about:
- A recent meeting that lasted more than thirty minutes. Did it produce a decision or build context that made a future decision possible?
- Thinking about last week, how much of my scheduled time didn't clearly do either—didn't decide anything and didn't build context toward a decision?
Then name the pattern my operating rhythm reveals about my actual strategy. Not the strategy I think I have, but the one my calendar is executing.
Your calendar reveals your real strategy.
Not the offsite deck. Not the wall plaque. Last week’s meetings–what they built and what they cost.
Every meeting does one of two things: it builds the context your team needs, or it produces a decision your business requires. If it does neither, time burns. And when enough time burns, the only option left is to force execution—fast, urgent, and without the context that would have made it right.
Your next quarter has twelve decision opportunities if you meet weekly. If eight of them go to meetings that did neither, the remaining four aren’t enough to be strategic. They’re enough for firefighting.
The gap between your strategy and your execution isn’t speed. It’s what your rhythm did with the time before speed became urgent.