No Place to Hide

AI won't replace Product Managers. But it will expose the ones who never should've had the job.

PMs who survive on vibe, templates and Jira tickets are already being outpaced. AI does what they do. But faster, cheaper and with better spelling.

AI is forcing PMs to evolve from backlog babysitters into strategic operators.

No more hiding behind status updates or pretending roadmapping is vision. AI writes specs. It cleans up research notes. It summarises meetings and drafts Jira tickets before the devs have logged off. If that's your whole job, start sweating.

But if you're the kind of PM who shapes bets, sharpens focus and asks better questions -you're not replaceable. You're rare.

Only sharp PMs know which bets to place, when to double down and when to walk away.

AI won't take your job. But a better PM using AI will.

PMF doesn't exist

Product-market fit doesn't exist.

It's a myth we tell ourselves to feel like we're on the right track.

“Agile” suffered the same fate (at least there's the agile manifesto that exists). Started as a working philosophy, ended up a bingo word. Everyone says they have PMF. No one can show you where it lives. They just point to a vibe. Some traction. A few good months. A round that closed fast.

“We've got it!” Based on what? Revenue? Retention? NPS? Survey? Gut feeling?

The phrase has become a catch-all. Founders claim it when growth feels easier than usual. Investors expect it before writing a cheque. But there's no standard. No scoreboard. Every product is different. Every market reacts in its own way. What looks like PMF for one company might be a dead end for another.

Product-market fit isn't something you find. It's something you feel.

And sometimes, you just hope you're right.

Make It Clear

Product Managers wait for clarity that never arrives.

They expect the strategy doc to have the answers. But nothing lands. Just more PowerPoint slides.

Because the higher up you go, the blurrier it gets. Goals get loftier. Language gets vaguer. No one wants to be wrong. So they delay, they decorate confusion with buzzwords. It feels smart but it isn't clear.

The best Product Managers don't wait. They start shaping. They turn fuzzy goals into concrete next steps. They don't chase alignment. They chase decisions. ​They poke holes (even when it creates discomfort). They write the draft no one asked for. They map the fog, not run from it.

Because anyone can follow a plan. But great Product Managers can make one. They stop asking “What's the direction?” and start saying “Here's what I'm seeing - poke holes in it”

Stop Taking Orders. Start Shaping Work

Some tech teams think their job starts when the requirements arrive.

But that mindset turns them into delivery machines - waiting for Jira tickets like orders at a café. The real value isn't in ticking off tasks. It's in shaping them. Working with product managers, not for them.

Because PMs aren't there to write task lists. They're commercial thinkers. They're shaping strategy, pushing customer insight, and holding the big picture. They don't need followers. They need partners.

Do less: waiting for answers.
Do more: collaborating to understand the “why.”

That's how you build better products - and better teams.

Validation Comes After Launch

You can't validate a product with opinions.
People love to be nice. They'll tell you what you want to hear. “I'd buy that.” “Sounds awesome.” “I'd totally use it.” They're not lying to be cruel. They're trying to be supportive. But support doesn't equal commitment.
The second you ask for money, everything changes.
That's the gap most early teams fall into. They build confidence through conversation, then get blindsided when no one converts. The t... read more

The Tech Debt Spiral

Like a snowball rolling downhill, technology debt simply gets bigger.

Cutting corners and patching things up work for a while. But eventually the codebase becomes a mess. Features take longer to build, and bugs pile up. The team becomes nervous about making changes. This triggers leadership demands speed, trapping everyone in a difficult cycle to break.

Outsourcing kills your product instincts

The best way to kill your product instincts is to outsource your customer research.

When you get answers neatly packaged in a fancy PDF with cool graphs and slick design, you feel good about it. It looks like the hardest part has been done, and you just need to look at the numbers and insights. On the surface.

As you go through the research prepared by someone else, you realise you only gain surface-level knowledge of the space.

Real research is about developing a good understanding of what your customers are experiencing - the small problems they face, along with all the nuances and frustrations.

You have to speak to them. No surveys or written responses will give you true insight into their challenges.

When you outsource research, someone else builds that understanding - not you.

Your product instincts start to fade over time.

The Two Types of Product Teams

There are two types of product teams - the slow-learning and the fast-learning.

The slow-learning team wants to deliver. They manage projects, write tickets, attend internal meetings and ask colleagues for design feedback. They mostly care about delivery and managing expectations.

The fast-learning team wants to learn. They talk to customers, read market news, push hacky code to production, and sometimes break things. They embrace ambiguity, but they learn fast.

The difference? The slow-learning team builds products for their bosses, and the fast-learning team builds products customers actually need.

Shift your focus. The best products come from deep insight, not just efficient delivery.

Hack Constraints

When your team isn't experimenting enough, it's most likely due to experiments taking too long to build, track and measure.

But every missed experiment is a missed opportunity. Insights go untapped. Ideas remain untested. Innovation stalls.

If the bottleneck is tech, hack it. Find workarounds even at the cost of degrading user experience but push forward.

Constraints spark the best solutions.

The title "Product Owner" shouldn't exist

Product Managers own the full lifecycle - strategy, discovery and delivery. Product Owners focus narrowly on Agile delivery. Splitting these roles fragments accountability and muddies product development.

True impact comes from roles with full ownership.

Clear Problems, Focused Teams

Engineers love clarity. The most important problem defines the mission.

A disjointed list of tickets signals confusion, while a vague objective offers no direction. Great work emerges when the goal is clear, focused and free of jargon.

When the problem is precise, teams know exactly where to aim.

Deciding If Your Team Needs a PM

Not every team needs a dedicated PM. Someone is already handling the PM work informally. It's not complex.

Eventually, though, clear ownership becomes unavoidable. Is an individual contributor juggling alignment, communication and strategy alongside their core work? Or is it time to delegate those responsibilities to someone focused entirely on them?

The decision shapes how the team prioritises and executes.

Great Products Begin with Why

A great product isn't just a checklist of requirements. It's built by understanding the customer's problem and why it actually matters.

Don't just follow instructions. Look deeper. Ask why. Question the logic.

The best solutions come from people who do a bit of detective work, not just execute.

Side projects teach product management faster than any course.

Finding a problem, crafting a solution and marketing it sharpen critical skills. You learn to balance creativity with practicality and adapt to real-world feedback.

Hands-on experience builds stronger product managers.

Big ideas need action to become real.

Break them into small, clear steps. Each win builds momentum and keeps you moving.

Perfection doesn't matter - progress does. Test, learn, improve, repeat.

No one will remember your first crappy step but they will when you cross the finish line.

Create, Don’t Wait for Ideas

Great ideas are crafted, not found.

They come from clear problems, real insights, diverse perspectives and bold inspiration. Ideation sessions - prep, sketch and develop. Turn this mix into better solutions and stronger buy-in.

Prep sets the stage. Sketching sparks creativity. Development refines ideas into actionable next steps. Keep it sharp and ideas will shine.

Trim the Dead Weight

Removing a feature signals a mistake. Few people feel comfortable admitting that.

This hesitation keeps bad features alive. Teams cling to them, fearing the optics of walking back a decision. But doubling down on something that doesn't work costs more in the long run - time, energy and user trust. Recognising when something doesn't fit and cutting it isn't failure. It's progress.

Users notice when products improve. Removing what's broken clears space for what works.

From Chaos to Clarity

The exec team was drifting, priorities misaligned, goals scattered. With OKRs, we trimmed 50 key results to 15, forcing clarity on what mattered most. The tough trade-off conversations exposed clashing perspectives but created alignment. Had to be done.

Fast Fades, Purpose Wins

In product management, it's tempting to move fast and break things. Sometimes, that works.

But moving with purpose works better. It means focusing on what matters, making smart choices, and building something valuable. Speed without direction leads to wasted effort. Purposeful action builds progress that lasts.

Fast fades. Purpose wins.

Clearing Space with No

Saying no is a leadership skill.

It's not about rejecting ideas, it's about protecting focus. When everything feels important, nothing is. Saying no clears space for what truly matters - what drives impact, not just activity.

Yes, it will sting. People will take it personally. But prioritisation isn't about popularity; it's about progress.

Every “no” to distractions is a “yes” to momentum.