Prime Mover Advantage: Episode 9
The Traction Loop: How Motion Becomes Momentum
New Readers: Start here at Episode 1 here.
“Saw your Friday context, talked to Engineering Saturday morning, made the call.”
Rachel mentioned it Monday morning as if it were ordinary. “We’re moving forward with the streamlined approach.”
“Three weeks ago, that’s three meetings and a slide deck,” James said.
Elijah was already past it. “If we’re clear on authentication, I need to lock in the API architecture. One path keeps our options open but adds a sprint. The other ships faster and matches what we’re showing Kedaris.”
“Which one reinforces the demo?” Rachel asked.
“The faster one. We practice what we sell.”
“Then ship it.”
Elijah nodded. Done.
James looked around the conference room. No one had scheduled this meeting. No agenda existed. Context was present. Rachel was already back on her laptop.
Paul sat at the far end of the table, notebook open. He’d been quiet, writing something in the margins. He looked up briefly, studied the room, then returned to his notebook.
“Lisa wants to move up their check-in,” Rachel said without looking up. “Says they have early results — and she sounded surprised by them.”
“How early?”
“One week in.”
His team wasn’t waiting for direction.
“When?”
“Two o’clock. I told her we’d confirm this morning.”
“Confirmed.”
Rachel was already typing.
Elijah closed his laptop. “If Kedaris’s pattern matches ours, we’re not looking at an anomaly.”
Paul’s pen paused over his notebook. He’d written something, circled it, then written a question mark beside the circle. He closed the notebook without sharing it.
Thirty-five days until the board meeting. And for the first time, James wasn’t counting them with dread.
What Survives Contact Is Strategy
Two o’clock. Lisa’s face filled the screen, sharp. The camera angle was low — she was sitting at her standing desk, leaning forward. The pen in her right hand tapped against her coffee cup. Four-second intervals. Decision rhythm.
“I need to tell you what happened this morning,” Lisa said.
James leaned forward. Rachel had her notepad open.
“Our Monday leadership sync. The one that usually runs ninety minutes.” Lisa paused. Almost laughed. “Twenty-two minutes. Three decisions made. Our meeting-to-decision ratio just flipped.”
Rachel glanced at James. He kept his focus on Lisa.
“What shifted?”
“People came prepared. They already knew the context.” Lisa’s pen tapped twice. “Friday afternoon we ran the fifteen-minute session you walked us through. Felt almost too short. But then this morning, people were referencing things from that conversation like they’d internalized them. Not repeating what was said — building on it.”
“Context traveled,” James said.
“That’s actually what my VP of Engineering called it.” Lisa leaned back. “His exact words. ‘The context traveled over the weekend.’ He didn’t mean the information traveled. He meant the understanding did. People weren’t rebuilding from scratch Monday morning. They were already two steps ahead of where they would have been.”
Paul was taking notes at the far end of the table.
“Lisa, can I ask you something?” James said.
“Go ahead.”
“Before this week — what did you think the problem was?”
Lisa considered the question. The pen went still.
“Slow decisions. We’d diagnose an opportunity, debate the approach, schedule alignment meetings, loop in stakeholders, circle back with analysis... and by the time we committed, the window had moved.” She stopped. “That’s what I would have said a week ago.”
“And now?”
“Now I think we were never slow at deciding. The deciding part took five minutes once we got there.” Her pen stopped. “We were slow at arriving. At getting everyone to the point where a decision could happen. That’s where the weeks went. Not the choice itself — the runway to the choice.”
“You weren’t slow,” James said. “You were rebuilding context every time.”
“Every single meeting. Starting from scratch. Explaining what we already knew to people who should have already known it.” Lisa exhaled. “One week. That’s all it took to see it. Now the context lives in the system, not just in people’s heads.”
Rachel unmuted. “Lisa, what’s your team saying?”
“They’re confused.” Lisa smiled. “The good kind of confused. They keep asking why it feels different. I told them we’d figure out the language later. Right now, we’re just going to keep practicing.”
Six weeks ago, James had stood in front of his own team and tried to teach them what Sam had shown him. He’d recited vocabulary they hadn’t earned. Now he was watching Lisa’s team arrive at the same place — not through teaching, but through practice. No one had given them a framework to memorize.
“There’s one more thing.” Lisa straightened, pen clicking against the desk. “I want to expand this to our product team. They’re the ones most affected by our coordination overhead. If this works for them like it worked for leadership...”
“Let’s design that together,” James said. “Same baseline process. Measure before and after.”
“Already started the calendar invites.”
The call ended five minutes later. The team sat in silence for a moment.
Paul spoke first. “Their pattern matches ours. Week one, same acceleration. Same confusion about why it feels different.”
“Exactly,” James said.
“Which means this isn’t about us.” Paul closed his notebook slowly. “It’s about the transformation itself. It transfers.”
The team filtered out. James stayed in the conference room.
The Ramorian email had been in his drafts since last week. He read it once more.
David,
We figured out what we got wrong with Ramorian. You needed transformation, and we showed up with visibility. That gap cost us the relationship, and it should have.
We’ve spent the last six weeks rebuilding around that difference. One of our customers just ran it for a week — their leadership sync went from ninety minutes to twenty-two. Three decisions made. They’re expanding it to their product team without us pushing.
I’d like to show you what we built. No pitch. Just the work.
—James
He read it once more. Then hit send.
