The 30x Effect: The Slow Work Behind Fast Decisions
Prime Mover Advantage - Episode 3
Prime Mover Advantage - Episode 3
The Slow Work Behind Fast Decisions
The first call surprised James.
He’d sent ten emails over two days. Not the usual check-ins—not feature requests, not satisfaction surveys. Questions that came from the frame Sam had given him. What are they trying to become?
Seven people responded. He’d expected scattered answers. What he got was the same answer in seven different voices.
The fourth one scared him.
“Honestly?” said Lisa, the VP at Kedaris. “We thought Dayanos would help us decide faster. Not just see what’s happening—actually change how we make decisions. Move from insight to action without the usual coordination nightmare.”
James wrote that down. “And did it?”
Lisa paused.
“We love the product. The visibility is incredible. But…we’re still spending weeks aligning on what to do with all that information. The decision-making part? That hasn’t changed.”
The calls before hers had said it differently. Same meaning. After Lisa’s, James stopped taking notes and started scrolling back through files he’d ignored.
Especially Ramorian’s last interview. He’d read it once, skimmed the praise, filed the rest. Now the second sentence jumped out:
“We loved seeing what was happening, but we still couldn’t decide what to do about it fast enough.”
He’d celebrated the first half of that sentence for months. Built a case study around it. Put it in pitch decks. The second half—the part that actually mattered—he’d treated like a feature request.
They needed decision systems, not dashboards.
Rachel texted him that afternoon. It’s been two days. Team’s asking questions. What do I tell them?
He typed back: Tomorrow. I’ll have something tomorrow.
Clarify The Real Problem Before Moving
He didn’t have language for it. Not yet. Whatever it was, it had already started to cost him time.
But the industry report was still open on his screen, and this time he wasn’t looking for who was winning. He was looking for how they moved.
Sam had said to watch for the absence—what the companies pulling ahead weren’t doing. James had skimmed this report two weeks ago looking for validation. Now he was looking for movement patterns.
One company kept appearing. Too often to ignore.
Amalakai.
James had dismissed them six months ago. Their positioning back then—”AI-powered workflow optimization”—sounded like everyone else. Commodity language. The kind you stop hearing halfway through.
Their homepage now read something different: “Intelligent decision support.”
Seemed like more than a rebrand. They’d changed their offer from doing work faster to making decisions faster. They weren’t selling software anymore. They were selling time back—and companies were buying.
James pulled up their recent activity. Product launches happening in coordinated waves. Customer testimonials about “decisions that used to take weeks now happening in days.” Not scattered announcements followed by scrambled messaging—integrated moves where product, marketing, and customer success seemed to land simultaneously. Nothing shipped half-baked.
He compared that to every other company in the report.
Most companies moved the way Dayanos moved. Product shipped features. Marketing scrambled to explain the story after the fact. Engineering cleaned up afterward. Customer success fielded confused questions, call after call.
Amalakai moved like a different species.
He pulled up timeline data. The typical company in the report took three to four weeks from insight to coordinated market launch. Amalakai was doing it in days. With fewer meetings and fewer people.
James opened Dayanos’s last product launch retrospective. Six weeks from initial decision to market. And that hadn’t even been coordinated—it had been sequential. Build, then message, then fix, then explain.
The gap between Dayanos and Amalakai wasn’t incremental. It was a different order of magnitude.
He pulled out his phone and texted Sam: “Found something in that industry report. Need to show you.”
The response came immediately: “Tomorrow morning. 9am. What did you find?”
James looked at the two tabs on his screen. Seven customer conversations saying the same thing. One competitor moving at a speed he couldn’t explain.
“The pattern you mentioned. And the company that’s already doing it.”
Speed Only Works When Systems Exist
Sam walked in the next morning to find James’s office rearranged.
Printouts covered the desk. The whiteboard was filled with competitor timelines and customer language. Post-its clustered by theme on the wall behind his chair.
“You found it,” Sam said.
“Amalakai.” James turned his screen toward Sam. “Six months ago, their positioning sounded like everyone else. Now they’re launching coordinated moves in days. We take six weeks. And ours aren’t even coordinated — they’re sequential.”
Sam studied the screen, then the whiteboard, then the post-its. He sat down.
“What did the customers say?”
“Same thing. All of them.” James pointed to the cluster of post-its nearest the window. “Decision systems, not dashboards. After the third one, it stopped sounding like feedback. Lisa at Kedaris said it the clearest — they can see everything, but they still can’t decide fast enough.”
“And Ramorian?”
“It was in their exit interview the whole time. It wasn’t that they lacked visibility. It was that nobody could decide with it.”
Sam nodded slowly. “So what do you want to do with this?”
“Show my team. This afternoon. Get everyone in the war room, walk them through what I’m seeing and why it matters—”
“Slow down.”
James stopped.
“Remember your calendar?” Sam said. “After our first conversation, you wanted to combine all your meetings immediately.”
“You said that was rearranging deck chairs.”
“And you agreed. Because you didn’t understand what you were rearranging toward yet.” Sam leaned back. “So what’s different now?”
“I understand the problem. Decision systems, not dashboards. The speed at which decisions actually get made.”
“That’s the diagnosis. Do you know how to build what comes next?”
James didn’t answer.
“What happens if you walk into that room this afternoon with a diagnosis and no treatment?” Sam gestured at the Amalakai printout. “Your team is smart. They’ll see the gap. And what do smart people always do when they see a problem they can’t build for yet?”
James didn’t answer.
“They reach for what they already have. More meetings. More planning docs. A judgment problem attacked with coordination tools.”
“So I shouldn’t show them?”
“I didn’t say that.” Sam paused. “I said if you show them without something to build on, they’ll default to what they know. And what they know is execution. More process. More overhead. The thing that’s already drowning you.”
James looked at the wall of research. Two days of work. Validated hypothesis. Clear competitive gap. And Sam was telling him it wasn’t enough.
“We have fifty-seven days to turn things around,” James said. “Amalakai’s already ahead. Every day we spend preparing is a day they’re —”
“Is a day they’re what? Building the system you don’t have yet?” Sam’s voice wasn’t harsh. Just direct. “Six months of fast execution built the wrong thing. And now — what’s the instinct?”
“Move fast again,” James said. “But in the right direction.”
“Same instinct.” Sam let that sit. “Different direction. Still the same instinct.”
That landed.
“Then try it,” Sam said.
James looked up.
“This afternoon. Get your team together. Show them what you’re seeing. Teach them what you’ve learned. See what happens.”
“You want me to fail.”
“I want you to feel the gap between knowing something and being able to build it. Right now you understand the problem. You don’t understand the system. Who decides, when they decide, and what they’re allowed to decide with. That’s not a criticism — it’s where you are. But you won’t believe me until you feel it yourself.”
James looked at his research spread across the office. Customer validation. Competitive analysis. The speed gap. He had the pieces. He just didn’t know how they connected into something his team could actually use.
“And after I feel it?”
“Then we do it properly.” Sam pulled the chair back from James’s desk. “Three days. Your leadership team. I’ll facilitate.”
The room was quiet for a moment. James understood what Sam was offering. Not advice over coffee. An engagement. The kind of thing you bring in when you’ve admitted the problem is bigger than you can solve alone.
“That’s a real commitment,” James said. “For both of us.”
“It is.” Sam didn’t flinch. “I’d need to clear client work. Move some things around. But this is what I do now, James. This is the work I left to build.”
James thought about his team. Rachel waiting for answers, calendar already filling up. His Product VP and Engineering Director heads-down on a roadmap that might be pointed in the wrong direction. Everyone executing. Nobody steering.
“Send me the proposal,” James said. “But I’m trying it my way first.”
“Good.” Sam stood. “And James — if it doesn’t land the way you think it will — that’s not failure. That’s the gap showing you where the system needs to go.”
57 days left. And counting.
Implementation Exposes What Insight Hides
James stood at the whiteboard in the war room as his team filed in.
His leadership team sat around the table: Paul, Rachel, Elijah. Three people who’d been running hard for six months on a direction James was about to question.
He already suspected this wouldn’t go the way he planned.
Rachel had her tablet open. She’d been waiting two days for this.
“What’s this about?” Paul asked, checking his phone. “We have sprint planning in an hour.”
“Cancel it,” James said. “This is more important.”
That got everyone’s attention.
Rachel and Elijah exchanged a glance. James caught it.
“I figured out why we lost Ramorian,” James said. He pulled up the customer call themes on the screen. “And why we’re going to keep losing if we don’t change something fundamental.”
He turned to the whiteboard and wrote:
Customers don’t need better visibility. They need faster decisions.
“I talked to seven customers over the past two days. Every one of them said some version of the same thing. They can see everything now — that’s what Dayanos gives them. But they still can’t decide fast enough.”
Rachel frowned. “So visibility wasn’t the bottleneck.”
Elijah leaned forward, studying the whiteboard through his glasses. “That tracks. We’ve had support tickets about workflow bottlenecks for months. I assumed it was a UX problem.”
“It’s not UX,” James said. “It’s what happens after they see the data. The meetings. The alignment cycles. The time it takes to go from insight to action.”
“So what are you proposing?” Rachel asked. Direct, as usual. She’d been sitting on the Ramorian news for two days while James went dark. She wanted specifics.
James clicked to the next screen. Amalakai’s positioning shift. Their launch timeline. The speed comparison.
“This is Amalakai. Six months ago they sounded like everyone else. Workflow optimization, standard efficiency play. Now they’ve repositioned around decision support. And look at how they move.” He pointed to the timeline data. “Three to four days from decision to coordinated market launch. We take six weeks.”
Paul set his phone down. “Who are they? I haven’t tracked them.”
“None of us have. I dismissed them six months ago.” James let that sit. “But look at the difference. Their product launches land as integrated moves. Product, marketing, customer success — all synchronized. Not sequential like ours.”
“How?” Rachel asked.
“That’s what I’m trying to figure out. From what I can see, they’ve built something where people don’t need to check before deciding. So coordination happens naturally instead of through meetings.”
Paul crossed his arms. “Define ‘check before deciding’. Because we do shared planning sessions. We have a product roadmap everyone can see. What specifically are they doing that we’re not?”
James paused. He knew the answer conceptually. Shared context. Unified decision-making. But Paul was asking how. Tactically. The mechanism.
“It’s... the context they share. Not just the roadmap. A shared picture of where customers are going and what decisions need to happen to get them there. So when each team makes their own calls, those calls are already aligned.”
“How is that different from what we do now?” Elijah asked. Not challenging, genuinely trying to understand.
“Right now we each make decisions in our own area, then spend meetings reconciling them. They seem to make decisions that don’t need reconciling because everyone’s working from the same foundation.”
“Okay,” Rachel said slowly. “So we need to build that foundation. What does that look like?”
James looked at his notes. This was the part he didn’t have.
“It means... the strategy isn’t trapped in my head. Customer goals, competitive positioning, technical constraints — all visible to everyone who’s making decisions.”
Paul tilted his head. “So we document our strategy better? Create shared docs?”
“Not just documentation. Something that stays current. That updates as things change.”
“Who updates it?” Elijah asked. “Who decides what goes in? What format does it take? Because we’ve tried shared wikis before. They die in two weeks.”
James didn’t have an answer.
Paul leaned back. “James, I’m tracking what you’re saying. But I’ve got sprint commitments built around the current roadmap. If we’re pivoting direction, I need to know what that means for Q4. My team’s already built infrastructure for the AI feature rollout we planned.”
“And I’ve got positioning live in market right now,” Rachel added. “Pitch decks, case studies — all built around visibility messaging. If we’re shifting to decision support, I need to know what we’re actually saying. By Friday. Not conceptually — specifically.”
Elijah adjusted his glasses. “We just finished an infrastructure refactor based on the old direction. Three months of work. Are we saying that investment was wrong?”
The room went quiet.
James felt the meeting shifting under him. He had the pattern. Customer feedback, competitive gap, the speed difference. Every question landed at the same spot. He could describe what needed to change but not how to change it.
“Look,” he said, pulling up the Amalakai comparison again. “I don’t have all the tactical answers yet. But the gap is real. Our customers are telling us they need something we’re not building. And a competitor we dismissed six months ago is already there.”
Rachel spoke carefully. “I believe the customer feedback. That’s real data. But we need more than a direction. We need a process we can actually execute against.”
Paul nodded. “I think we need someone who’s built this before. Someone who can show us the system, not just the concept.”
James looked at the whiteboard. One sentence about decisions. A competitor comparison. Customer quotes. He had the edges of something — he could feel its shape. But his team was right. Feeling the shape wasn’t the same as building it.
“You’re right,” he said. “I have someone who can help. Let me set that up.”
The meeting ended twenty minutes later. No decisions made. No alignment achieved. Just more questions and three people who looked at James with a mix of respect and uncertainty.
Rachel stopped at the door after Paul and Elijah left.
“James.” She waited until he looked up. “Whatever happened at that board meeting, it clearly shook something loose. And I think you’re onto something real. The customer feedback alone tells me we’ve been missing something.” She paused. “But we need structure. I can’t rebuild positioning on a feeling.”
She was right. He’d given them the pattern without the process. The hard part he hadn’t done yet.
Sam had warned him this would happen.
A Diagnosis Isn’t A System
James sat alone in the war room after everyone else had left.
Rachel was right. A feeling couldn’t carry this.
His phone buzzed. A text from Sam: “Workshop proposal in your inbox as discussed. Three days, your leadership team. Let me know.”
James opened the email. Detailed. Professional. The kind of spend he’d explain to a board.
The whiteboard still had everything from the meeting. All of it explained the problem. None of it told him what to build. Sam’s encouragement to try the idea had been a test.
He typed back: “Confirmed. I don’t want to wait.”
Sam’s response was immediate: “Ok. We’ll start first thing Monday. Tell your team to clear three days.”
James pulled up his calendar and sent the invitation:
Strategy Working Session — Monday–Wednesday
Paul would have questions about the roadmap he’d already committed his team to. Rachel would want to know what this meant for positioning. Elijah would ask what it cost in engineering time.
And he wasn’t going to guess. But he knew something he hadn’t known two days ago.
Seven customers had told him the same thing. A competitor he’d dismissed was already there. And his team — good as they were — couldn’t build what they couldn’t see.
That was enough to move on. Not enough to move fast.
He closed his laptop and stood in front of the whiteboard.
Customers don’t need better visibility. They need faster decisions.He’d written that sentence three hours ago thinking it was the answer. Now he knew it didn’t tell him what to build.
54 days left. And no room for another miss.
PRACTICE: The Compression Test
Time: 2 minutes
Think of a strategic initiative currently in progress—something that’s taking weeks or months to move forward.
Ask yourself: What would this look like if it happened 30x faster?
Write one sentence about what’s actually slowing it down.
AI PROMPT:
The initiative that’s moving slowly is: [Your initiative]
If it moved 30x faster, here’s what would change: [Describe the compressed timeline]
What’s actually slowing it down is: [One sentence—coordination overhead, missing context, unclear decision rights, etc.]
Based on this:
1. Am I optimizing for speed or for coordination overhead?
2. What would need to be true to compress this from months to days?
Show me what’s possible.
The distance between the problem and the solution isn't resources.
It's context.
When the pressure hits, it’s easy to grab the first problem you can name and race to the fix.
Fixes that are fast, confident, but shallow.
The surface problem is never the real problem. And a solution without context isn't a fix — it's an ointment.
You can't fix what you can't frame. And you can't frame what you don't understand.