These are not case studies. They are moments.
Real ones. From real organizations. With real leaders who were willing to ask the hardest questions.
No company names are revealed. We protect the people. We never protect the problem.
Story 1 – The Pivot That Became Something Else
The number on the whiteboard was $50 million.
Twelve months. That was the target. That was the ambition. That was the pressure sitting in the room every single day.
The company was at $5 million ARR. Profitable. Stable. Respected in their market. But the CEO had seen something – a gap, an opportunity, a vision of what the company could become if it was willing to make one big move.
Pivot from B2B to B2C.
Ten times the revenue. One year. Go.
A ship that does not know its port will mistake every shore for a destination.
And that is exactly what happened.
The VP of Product had already drafted a PRD. The thinking was there. The market analysis was reasonable. The vision was directionally right.
But the moment they sat down together, something became clear that no slide deck had captured.
The team had no idea why they were doing this.
Not the what. They understood the what. New product. New market. New users.
But the why. The deep, honest, organizational why. The reason this pivot made strategic sense beyond the number on the whiteboard, had never been communicated.
And the culture in that room was B2B. Every instinct. Every assumption. Every way of thinking about a user, a problem, a solution. It had been shaped by a decade of building for businesses, not people.
Now they were being asked to build for people. With the same instincts. The same assumptions. The same way of seeing the world.
So that is exactly what happened.
The PRD became a suggestion. Then a collection of ideas. Then a wishlist. Features arrived from everywhere. Gamification, because it was trending. Social feeds, because someone had seen it work elsewhere. Community tools, because why not.
When everyone brings one ingredient to the pot; you do not get a feast. You get a mess.
The product became everything the team had ever seen, and nothing the user had ever asked for.
By the time the MVP shipped; it was unrecognizable. The team was exhausted. Leadership was frustrated. And the questions were getting harder to answer.
Then came the decisions that always follow a product without direction.
The product team was cut. Headcount reduced. The people who understood the user – gone.
Engineering took the lead. Because someone had to. Because the product still needed to be built even if nobody could agree on what it was supposed to be.
Marketing was left trying to translate what engineering was building into something a customer might actually want. They could not. Because engineering was not building for customers. They were building for specifications that had long since lost their connection to a real human problem.
The $50 million never came.
What came instead was a product that nobody owned, nobody understood, and nobody could sell.
Not because the people were not talented. Not because the CEO’s ambition was wrong. Not because the market opportunity was not real.
But because the most important conversation, the one about why this pivot mattered and who it was really for, was never had.
A pivot is not a product decision. It is not a technical decision. It is not even a market decision.
It is a human decision.
And when the humans in the room are not aligned on the why; no amount of features, funding, or ambition will save what gets built.
They were fast. They were committed. They were talented.
They just never agreed on where they were going.
Story 2 – The Migration That Solved the Wrong Problem
Nobody argues with a burning building.
The legacy system was not burning, but it was smouldering. Years of features built on top of features. Technical debt layered so deep that every new capability came with a hidden cost. The engineering team had become archaeologists, carefully excavating around old code, afraid to touch anything too hard in case it brought something else down.
Leadership made the call.
Migrate to a modern tech stack. Clean slate. New foundation. Build something the team could actually scale.
It was the right decision.
What nobody defined was what success looked like on the other side.
The migration happened. Engineering delivered. The new system was faster, cleaner, more modern. From a purely technical standpoint, mission accomplished.
But engineering was not happy.
They had spent months rebuilding something users had already learned to live with. And nobody had told them what this new system was supposed to enable that the old one could not. What new capability would now be possible. What problem would now be easier to solve.
They had migrated the technology. But not the thinking.
Leadership was not happy.
The product looked the same to customers. The investment was invisible. The board wanted to see growth and what they saw instead was a team that had spent a year running in place.
Marketing was not happy.
There was nothing new to sell. No new story. No new capability to put in front of customers. Just a different engine under the same hood; and you cannot sell an engine to someone who just wants to get where they are going.
Sales was not happy.
Customers noticed the new design. They appreciated it for about thirty seconds. Then they asked the same question they had always asked: What does this actually do for me that it did not do before?
Nobody had a good answer.
Because the question that should have been asked before the redesign began, what do our users actually need right now, had never been asked at all.
So another decision was made.
Redevelop the entire product. MVP to Version 1. Version 1 to Version 2. Start again. New design. New interface. New everything.
The problem with digging a new well every time the water tastes wrong, is that the problem was never the well.
More months. More effort. More energy diverted from growth into rebuilding.
And through all of it – – the migration, the redevelopment, the restarts – – the same question remained unasked: What problem are we actually solving for our users? And what does success look like for every team in this organization, not just engineering?
A migration is never just a technical project.
It is an organizational decision that touches engineering, product, marketing, sales, and every customer who interacts with what you build. When the business outcome is not defined before the first line of code is written, every team fills the gap with their own assumption of what success means.
And those assumptions never match.
Ten fast runners going ten different directions do not win a race. They create a stampede.
The company was fast. Committed. Full of talented people who genuinely wanted to build something great.
They were just never all running in the same direction.
At PPLCO, that is the work we do before anything else.
Not the migration plan. Not the product roadmap. Not the growth strategy.
The alignment. The clarity. The shared understanding of why, before a single decision is made about what or how.
Because when everyone in the room is running in the same direction, you do not need to rebuild twice.
You build it right the first time.
If this felt a little too familiar, Good! That feeling is where the real work begins.
Let’s have that conversation.