Pivot pressure is coming from all sides. Two product leaders share how they handled it: one executed an acquisition she didn't choose, one held conviction against an industry telling him to do the opposite,
A memo lands on your desk. The board has a new direction. Or the company just got acquired. Or investors are pushing a completely different go-to-market model.
You didn't ask for this pivot. You didn't choose it. But now you have to lead through it.
That's the scenario at the center of Episode 8 of the Product Leaders Lab. Two product leaders. Two completely different kinds of pivot pressure. Purnima Bihari was VP of Product when her Canadian workforce management SaaS company got acquired by a larger American competitor. She had to merge two competing product portfolios while navigating layoffs, culture clash, and nonstop organizational change. Nick Cust is CPO at Cake Equity, where the entire industry was telling him to go sales-led and high-touch, and he had to decide whether to follow the conventional playbook or bet on something different. One executed a pivot she didn't choose. One held conviction against a pivot he didn't believe in. Both have lessons worth studying.
Most product leadership content focuses on the pivots you initiate: the strategic bets you make, the roadmap shifts you drive, the repositioning you champion. What gets far less attention is the pivot that comes from above: the direction handed down from a board, an acquirer, or an investor who just saw what a competitor is doing.
That kind of pressure is different. You're not the author of the change. You're the person responsible for making it work. And the skills that help you lead your team through normal uncertainty (clear thinking, good judgment, strong communication) don't fully prepare you for the moment when the pressure is coming from outside your control.
Both Purnima and Nick found themselves in versions of this situation. And both of them, from very different angles, arrived at the same uncomfortable truth: hedging is the most expensive option on the table.
When the acquisition was announced, Purnima's team had been building competitive battle cards against the very company that just bought them. That's the context. They were proud of what they'd built. They were good at competing. And now they were being absorbed.
The direction was clear: get every customer onto the Canadian platform. No ambiguity there. But the execution was enormously complex. Two product portfolios. Different tech stacks. Different customer sizes. Different organizational cultures. And a migration that would take years.
The first thing Purnima reached for was those battle cards.
"Remember the battle cards? Because we already knew the weaknesses and the gaps. So then I went ahead with like, how do we have a roadmap and what does that roadmap and migration of customers looks like?"
This is underrated as a move. The competitive intelligence her team had built against the acquirer became the blueprint for the merger. She already knew where the gaps were. She already knew what needed to be built. She turned the adversarial knowledge into operational clarity.
But knowing what to build was only the beginning. The real challenge was sequencing it while keeping the business running. She described her approach as an allocation model: a deliberate split between maintaining the core product, migrating existing customers, and building what was net new. Three streams running at once, with clear ownership and sequenced priorities.
She also did something that rarely shows up in product playbooks. She had her PM team build internal knowledge programs for the whole organization.
"The payroll product, we realized when we started training people that people didn't understand a lot of payroll terms. So the PM team then went and created introduction to payroll."
Her PMs weren't just building features. They were building capability across two merged organizations. Because the pivot wasn't just a product change. It was a domain change. Sales, support, and customer success all needed to understand a new world before they could sell or support it confidently.
And then there were the layoffs. Not one round. Multiple rounds.
"I was upset the entire night before I had to do it. I think I choked up. Some of these decisions came to us and like you have to decide, like, how do you decide with the person who you literally... you know them personally, people have things happen in their life, but nobody cares."
That's the cost nobody puts in a post-acquisition playbook. You're executing a pivot you didn't choose. And some days that means having conversations that keep you up the night before.
What kept the broader plan from falling apart? Purnima was deliberate about how decisions got made across the two organizations.
"Democracy is an underrated skill in product. To get everybody onto the plane, you have to look for the right information. You do not go with your decisions or gut checks. You present facts and then you get people on the same plane and then you get people to vote on that and they can only vote on one option."
Three options, minimum. Outcomes wrapped around each one. Let people vote. It's slower in the short run. It's far more durable in the long run.
She also described the first version of her plan as something she put on paper specifically to be wrong.
"Whatever I gathered, I put it on paper. Like, this is how it looks on paper. And then there was a bunch of reactions... And then we went ahead and created like a full plan, which worked, iterated, brought it back. And that became like a guiding thing for both the teams to collaborate on for the next one and a half years."
The plan didn't work because it was perfect. It worked because it was real enough to react to.
Nick's situation looked different on the surface. Nobody handed him a memo. Nobody told him what to do. The pressure was more like gravity: constant, ambient, pulling the company toward a model that everyone in the industry said was the right one.
Hire salespeople. Go high-touch. Follow the VC playbook.
Nick saw it differently. But holding that conviction without proof is its own kind of hard.
"We were building fast, but building the wrong thing. We globalized too early. We were rebuilding the same features over and over again. And we really had this tension between should we go into more of a sales led, admin led, high touch, human service led moment or really commit to self-serve? And that nearly broke us until we really stopped thrashing."
He admits he sat on the fence too long.
"I sat on the fence too much. Some bad calls were made. I probably should have pushed earlier and harder for the self-serve angle, but I had, as a product person, you need proof."
Two things eventually gave him that proof. First, the economics stopped making sense. They were closing deals, but the complexity of a globally distributed, sales-service-led model meant they weren't building toward profitability. Nick's read was blunt: you can't out-service the incumbents. They're bigger, more funded, have more people. If you play their game, you lose.
The second inflection point was more concrete. The salespeople left (not through a crisis, just through natural attrition) and for a period of months, the product had to do the work on its own. And it did.
"We had a period of a number of months where we had just let the product do its work and all the work that we'd been putting into the onboarding journey, really watching our data, really investing in our data infrastructure showed us that we could do it."
That's the proof Nick had been waiting for. And once he had it, the decision wasn't about features at all.
"The decision to make was what company we are, rather than not the features. We were choosing the company, not choosing the features."
That's the insight that changed everything. This wasn't a roadmap decision. It was an identity decision. One ICP, one market, product does the work. No sales army. No high-touch service layer.
When the decision was made, the team's reaction was immediate.
"Relief I would say. It simplified things and it simplified our need to have to build in so many different ways."
The fog lifted. They finally knew what they were building and who they were building it for. And the constraint (no big sales team, no global expansion) became the design brief.
"As soon as we said, we're not going to play the game of hiring 300, 400 people and scaling like that, then that became the design brief."
The outcome: thousands of customers, majority self-serve, growing in the US, differentiated precisely because they didn't follow the playbook.
Purnima and Nick took opposite paths. She executed a direction handed down from above. He resisted the direction being pulled from outside. Both worked. But what's interesting is how much their underlying lessons overlap.
The first overlap: the first plan is just for feedback. Purnima said this explicitly: put something on paper, get the reactions, iterate. Nick lived a version of it too: he needed real-world proof before he could commit to a direction with conviction. Neither of them had the full answer at the start. Both treated early plans and early experiments as instruments for learning, not commitments to defend.
The second overlap: almost right is expensive. Nick said this directly. But Purnima lived it in every round of layoffs, every duplicated feature, every customer migration that revealed a gap. When you hedge and try to be two things at once, the cost compounds quietly. The leaders who committed earlier (to a clear direction, a defined ICP, a structured allocation model) moved faster and burned less.
The third overlap: clarity about identity unlocks everything else. Nick talked about choosing the company, not the features. Purnima talked about getting everyone on the same plane around the same options. Both of them were doing the same underlying thing: creating shared clarity about what matters. Without that, no amount of planning or execution holds.
Most product teams, when pivot pressure hits, try to buy time by hedging. They run the old model and the new one in parallel. They avoid the hard identity question because it's uncomfortable and the answer isn't obvious yet.
What Purnima and Nick both found is that the hedge is the most expensive choice. Not because taking a position is always right, but because the cost of being between two positions (in team energy, focus, and strategic coherence) compounds in ways that are easy to miss in the moment.
The structural move that both of them made, from very different angles, was to create conditions for a clear decision. Purnima did it by building a plan designed to surface reactions. Nick did it by waiting for the data that made the choice undeniable. In both cases, the clarity didn't come from a single brilliant insight. It came from building a process that forced the question into the open.
Pivot pressure reveals something about product leadership that normal operating conditions tend to hide. When the direction is clear and the roadmap is yours, almost any capable leader can execute. The real test is what happens when the pressure comes from outside. When you didn't choose the change and you still have to make it work.
What Purnima and Nick both demonstrate is that the response to that pressure is not primarily strategic. It's relational. It's about how you communicate across two organizations that were just competitors. It's about how you hold a team together through layoffs and uncertainty. It's about being honest enough to admit you sat on the fence too long, and clear-eyed enough to act once the evidence is in front of you.
As Nick put it: "We didn't lack effort. We just lacked direction."
Getting the direction right (whether you're executing someone else's call or building the case for your own) is the actual work.
Want to hear the full conversation? Listen to Episode 8 of the Product Leaders Lab wherever you get your podcasts:
