Judgment Is the Advantage
Prime Mover Advantage - Episode 2: : The Frame That Redefines How Teams Move
Prime Mover Advantage - Episode 2
The frame that redefines how teams move
“We’ve decided to move in a different direction.”
The email was still open on James’s screen.
Half his revenue. Gone.
He’d been staring at the industry report for an hour. The pattern was there—companies pulling ahead, something he couldn’t name. He needed someone who could see what he couldn’t.
His phone buzzed. A text from an old colleague, Sam.
“Heard through the grapevine your board meeting got interesting. Coffee?”
Sam had been one of the first hires when Dayanos was growing faster than it could think. He’d left a few years ago to build his own practice, but they’d stayed in each other’s orbit.
James typed back: “Interesting is one word for it. You at the usual place?”
“Already here. Figured you might need it.”
Twenty minutes later, James walked into the coffee shop where he and Sam had mapped out Dayanos’s early strategy on napkins. Sam was at their corner table, same spot they’d always taken.
“How bad?” Sam asked as James sat down.
No preamble. That was Sam. Direct. Always had been.
“We lost Ramorian.”
Sam set his coffee down.
He’d been there when they signed them. First enterprise customer. The name that made the next calls easier.
“When?”
“Yesterday,” James said. “During my board presentation. I was on the adoption slide for the new meeting intelligence platform when the email came in—twenty minutes before I was about to call the quarter a win.”
Sam nodded once, like he was filing it away.
“They were using it more than anyone,” James said. “Almost everyone there. They helped us win Kedaris last year.” He shook his head. “And they still walked.”
Sam let the sentence sit.
“Your highest-usage account,” he said. “And they left.”
James looked down and gave a small nod.
Sam leaned forward. “Walk me through your last conversation with them.”
James opened his mouth. Stopped.
“I don’t know,” he said. “Nothing changed on our side. We shipped on time. Usage was climbing.”
Sam kept his voice even. “That’s your side. What did they tell you on theirs?”
James stared at the table.
“Tell me about Ramorian since I left,” Sam said. “Not the metrics. What were they trying to become?”
James looked at him. “Trying to become?”
“Every company that buys something is trying to reach somewhere they can’t get to on their own. What was Ramorian’s somewhere?”
James opened his mouth. Closed it.
“I don’t—” He stopped. “I know what they bought. I know what they used. I had usage patterns, satisfaction scores — everything that said it was working.” He looked at Sam. “I thought I knew what they wanted to become. I just — I built for it.”
“That’s the gap,” Sam said.
“Okay. I get it.” James exhaled. “So what do I do now?”
Sam didn’t answer immediately. He picked up the napkin — old habit from their early days.
“Before you do anything,” Sam said, “you need to know what Ramorian was actually trying to reach. Not what they bought. Not what they used. What they were trying to become.” He wrote a single line at the top:
What are they trying to become?
“Because whatever you do next,” Sam said, “you don’t want to build another six months on the same assumption.”
James looked at the napkin. The question was simple. The implication wasn’t.
“Let’s start there,” Sam said. “Everything else follows from that.”
Winning Metrics Don’t Mean You Own the Win
“The board said something that stuck,” James said. “They said we were climbing the wrong summit.”
“Yeah. They’re right.” Sam paused. “So what does every strategy conversation at Dayanos start with?”
James thought about it. “Our position. Our product. Our roadmap. The competitive landscape.”
“And where does the customer show up in that?”
James didn’t answer. He’d never framed it that way.
“Okay,” James said. “I have their exit interview notes. And emails from their VP of Ops.” He opened his laptop. “Let me show you what David said.”
They spent the next twenty minutes going through Ramorian’s feedback. Sam asked questions James hadn’t thought to ask. Not about what features Ramorian wanted or which competitors they were evaluating—about what problems Ramorian was trying to solve. What decisions they struggled to make. What they hoped would be different six months after implementing Dayanos.
David, Ramorian’s VP of Operations, had said something in their last quarterly review that James had filed as praise: “We can finally see what’s happening across teams.” In the exit call, he’d said something James had filed as a feature request: “We loved seeing what was happening, but we still couldn’t decide what to do about it fast enough.”
James had celebrated the first sentence. He’d completely missed the second.
“Read those two statements back to back,” Sam said.
James did.
“They could see everything,” Sam said. “What couldn’t they do?”
“Decide. They couldn’t decide fast enough.” James sat back. “We gave them visibility. They needed—”
“Keep going.”
“They needed to make decisions faster. But the visibility just gave them more to coordinate around. More meetings. More alignment sessions. And every meeting showed up in our usage dashboards. More—”
James stopped.
“More…?” Sam asked.
“More activity. Same problem we have.” James looked up. “They were doing exactly what we’re doing.”
He let that settle.
“Meetings about meetings. They could see more than ever. They just couldn’t move.”
“Now you’re seeing it.”
James set his coffee down. “We gave them a dashboard for a car with no steering wheel.” He heard his own metaphor from the night before land differently now. “But it’s worse than that. We built the dashboard because that’s all we know how to build. We can’t help them steer because we can’t steer ourselves.”
Sam let that sit.
“The problem Ramorian had,” Sam said quietly. “Is it the same problem Dayanos has?”
James thought about his leadership team. Product presenting slides while Marketing checked their phones. Engineering taking notes. Everyone in the same room. Supposedly aligned. Making almost no real decisions.
“Yes,” James said. “Same problem.”
Meetings Are a Tax for Alignment You Don’t Own
Sam looked at the napkin. The question was still written at the top: What are they trying to become?
“So what was Ramorian actually trying to become?” Sam asked.
“An organization that could move faster from seeing something to doing something about it.” James paused. “That’s what David kept circling back to. Not more visibility. Faster decisions.” “And why couldn’t they get there?”
“Because seeing more created more to coordinate. And they didn’t have—” James searched for the word. “They didn’t have enough shared context to decide without getting everyone in a room first.”
Sam nodded. “I worked with a company last year—can’t say which, but same place. Meetings about meetings. When we tracked actual decisions? Three or four per month. Everything else was coordination overhead.”
“That sounds painfully familiar.”
“So what do you think changed for them?”
James considered it. “They found a way to get people the context before the meeting?”
“What if they didn’t need the meeting at all?”
James looked at him.
“Think about an orchestra,” Sam said. “When it’s time to perform, nobody’s having an alignment meeting on stage. Every musician already has the score. They know the tempo, the interpretation, their part in relation to everyone else’s. All that context was built before they ever sat down together. When they play, coordination is almost invisible—not because they’re communicating in real time, but because they already share the picture.”
“And we’re the orchestra that skipped rehearsal,” James said.
“You’re the orchestra that replaced the score with a meeting schedule. Different musicians, different interpretations, same conference room. Then you wonder why it doesn’t sound right.”
“That’s what I saw in the industry report,” James said. “Companies moving with a kind of precision we’ve never achieved. I thought it was something about their product or their team. But it’s not, is it?”
“What do you think it is?”
“It’s how fast they can go from seeing something to making a decision about it.”
Sam picked up the pen and wrote below the question on the napkin:
More context clarity = Higher Decision Velocity
“Decision velocity,” Sam said. “Not execution speed. How fast you can make quality decisions.” He tapped the napkin. “What happens when you optimize for execution speed instead?”
“You build the wrong thing faster,” James said.
Sam waited.
“That’s exactly what we did.” James looked down at the napkin. The question at the top. The formula below it. One led to the other.
“Six months,” he said quietly. “We spent six months proving that.”
“You’re not alone. Most companies do.”
You Can’t Fix What You Can’t Frame
“The early days,” James said slowly, “When we first started Dayanos. We had decision velocity. The three of us in one room. We all saw the same picture. We made decisions in hours.”
“I remember,” Sam agreed. “Didn’t need alignment meetings because context was already shared. Constantly. Naturally.”
“But we grew. More people. More teams. More—”
“More coordination overhead. And instead of finding ways to keep that shared context as you grew, you built systems to coordinate people who didn’t have it. Meetings filled the gap.”
James felt the weight of it. Every sprint planning session. Every roadmap review. Every alignment meeting that felt necessary because people were working from different starting points.
“You taught me something in the early days,” Sam said. “You kept asking: are we building what matters, or just what’s next?” He turned the napkin. “I took that question with me when I left. Took it a different direction than you probably intended. Down some roads that didn’t make sense to anyone else for a while.”
James remembered teaching Sam how to think strategically, how to see patterns when everything felt like chaos. He’d always wondered where Sam had taken that foundation after he went out on his own.
“I stopped asking that question,” James said quietly.
“I know.” Sam’s voice was calm. “That’s why I’m here.”
They sat in silence for a moment. The coffee shop hummed around them—conversations, espresso machines, the familiar rhythm of a place they’d spent countless hours.
“I need help,” James said finally. “I have sixty days.”
“I know.”
“But I don’t even know where to start.”
“You’ve already started.” Sam pointed at the napkin. “You have a question and you have a formula. What you don’t have yet is the full pattern. And until you see it—really see it—anything I give you will just be another template to fill out.”
“So what do I do?”
“Talk to your customers. Not about features, about outcomes. Ask them what they’re trying to become. Ask them what’s different about how they make decisions since they started using Dayanos. And listen for the gap between what they can see and what they can do.”
“And then?”
“Then look at that industry report again. But don’t just look at who’s pulling ahead. Look at how they’re moving. The gap between companies that have traction and companies that are just shipping faster.”
“And then I’ll know what to do?”
Sam smiled. “Then you’ll see what I can’t explain to you yet. And when you do—call me.”
James wanted to push for more. Sam read it on his face.
“You taught me something else back then,” Sam said, standing. “’Don’t solve a problem you don’t fully understand.’ You made me sit with questions until the answers became obvious. Right now, you have a concept and a hypothesis. But you don’t see the full pattern yet.”
“So I need to see it myself.”
“You need to see it yourself.” Sam paused at the door. “One more thing. When you look at that report—pay attention to what those companies pulling ahead aren’t doing. Sometimes the absence tells you more than the activity.”
“Talk soon.”
Then Sam left.
James stood outside the coffee shop, napkin in hand.
What are they trying to become? More context clarity = Higher Decision Velocity
A question and a formula. Simple. And different from how Dayanos operated.
He looked at his calendar.
Board prep meeting. Board debrief meeting. Scheduled three hours apart. Marketing alignment Monday. Product sync Wednesday. Engineering check-in Friday. He wasn’t scheduling decisions. He was scheduling reconciliation—not preventing misalignment, fixing it after the fact.
The same problem Ramorian had.
Combining meetings wouldn’t fix it. He’d just have fewer rooms where people still weren’t seeing the same picture.
James walked back to the office. His leadership team was still there—they always were, stuck in coordination meetings, trying to agree on next quarter’s roadmap.
He passed the main conference room. Through the glass, he could see his Product VP and Engineering Director leaned over a laptop, working through what looked like a sprint plan. Not looking up. They didn’t know yet—or maybe they did and were doing the only thing they knew how to do. Keep shipping.
Were they seeing the same picture? Or just occupying the same room? He was halfway to his office when his Marketing VP caught up with him.
“Is it true about Ramorian?”
“It’s true.”
“James, that’s every pitch deck we have. Our prime case study. What are we going to do?” “I’m working on something. Give me two days before we pull the team together.”
She looked like she wanted to push further but read his face. “Okay. But the team’s going to ask questions.”
“I know. I’ll have better answers soon.”
She broke off toward her office. James kept walking. He wasn’t done yet.
He pulled out his phone and started drafting emails to customers. Not the usual check-in emails. Different questions this time.
“What transformation were you hoping Dayanos would enable?”
“Six months after implementing, what did you expect would be different about how your team operates?”
“When you think about the summit you’re trying to reach, what does success actually look like?”
He sent ten emails before he reached his office. Then he opened the industry report. This time, he wasn’t looking for who was winning. He was looking for how they moved.
And more importantly—what they’d stopped doing that created the difference.
Now it counted.
59 days left.
Activity: The Traction Test
Time: 2 minutes
Think of the metric you’d report to your board to show progress.
Ask yourself: Does this metric also move your customer closer to their summit?
Write one sentence about what you see.
AI Prompt:
The decision that required multiple meetings was: [Your decision]
We needed multiple meetings because: [What was missing - context, clarity, decision rights, etc.]
If we had that from the start: [One sentence on what would have changed]
Based on this:
1. Where am I treating coordination as decision-making?
2. What context, shared upfront, would eliminate most coordination overhead?
Help me see the pattern.
The metric that moves your board doesn’t always move your customer.
Traction isn’t about usage or satisfaction.
It’s about whether they’re getting closer to the summit they’re trying to reach.
If you track your progress but ignore theirs, you end up with dashboards for cars with no steering wheel.
The question that matters is simple: does this number move them too?