Progress motivates action

Progress motivates action. It's not just the reward; it's the feeling of progress that drives commitment.

Two groups of customers were given punch cards awarding a free car wash once the cards were fully punched. One group was given a blank punch card with eight squares; the other was given a punch card with ten squares that came with two free punches. Both groups still had to purchase eight car washes to receive a free wash; however, the second group of customers - those that were given two free punches - had a staggering 82 percent higher completion rate.

Hooked: How to Build Habit-Forming Products

Engagement Isn't a Number

Most engagement surveys don't measure engagement.

They measure vibes.

The problem isn't the intent - it's the output. You run a survey. You get a 67.8% “engagement score.” Someone builds a deck. Charts go up, comments stay anonymous, nothing changes.

That number doesn't tell you who's struggling. It doesn't tell you why trust is low. It doesn't tell you where the rot is starting. It just tells you people clicked a box.

Real engagement isn't a metric. It's a conversation.

Ask them how they're feeling. Ask what's blocking them. Ask what's making their work better - or worse. Then shut up and listen. Not just in surveys. In 1:1s. In retros. In offhand comments. The signal's already there. You don't need a dashboard. You need ears.

Pie charts don't build trust. Conversations do.

The secret to a message that sticks

Success comes from repeating the right words, not just saying them once.

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.

Write It Down Before Misalignment Costs You

This is such a great example of how important written communication is. Misalignment happens all the time - on the problems, the solutions, the details and even the language we use. So, as soon as you sense there's misalignment and nothing is written down, the best move is to put it into words.

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.

Framing is Everything

Recently I wrote about the most important skill for Product Managers.

Regardless of whether you are a Product Manager or not, the communication will help you with all aspects of your career. If you want to manage or be a leader, you have to be a good communicator. Specifically, you need to get better at framing.

What's your goal? Are you looking for feedback, sharing information, wanting to influence, asking for approval or something else entirely?

What are you sharing? Is it a problem? Maybe a solution? A vision? Or a mix?

How much detail are you planning to share? Is this a helicopter or detailed view? Or perhapse, both?

Who's your audience? Your team, the entire organisation or the executive group?

Your communication needs to be adjusted depending on the answers.

Early in your career, you use the same message no matter the context.

To grow, you need to get better at tailoring your message - what you say, how you say it and when to say it.

The Cost of Indecision

Misaligned leadership doesn't announce itself. It creeps in. Slowly. Quietly. Then it wrecks your team.

Leaders think the damage is minor. Temporary. Invisible. But it's not. It's heavy. It's real. It shows up in whisper networks, in backchannel Slacks, in passive standups where nobody commits because no one knows where things are going.

You see it when smart people play it safe. When the loudest voice wins. When meetings drag on because no one wants to be the first to say what everyone's thinking. You feel it in the hesitation. That's the real killer.

Disagreement isn't the problem. Lack of alignment isn't even the real issue. Teams can live with that. What they can't survive is hesitation. Leaders who won't commit. Who won't decide. Who stay neutral until it's too late and now the team's solving the wrong problem. Again.

Indecision isn't neutral. It's destructive. Especially when disguised as “consensus-building” or “being thoughtful.” Teams need a decision. Even the wrong one. Because wrong moves can be corrected. Hesitation can't.

Leaders, pick a path. Say it out loud. Then stand behind it until you know it needs to change.

Make the fucking decision. Your team's already waiting.

Trust breaks when promises break

Trust breaks when promises break. People notice, even in silence and they remember. Honour commitments - trust depends on it.

Empowering Without Overdirecting

This afternoon I spoke with the team about the challenges for any leader and their team in finding the balance between telling them what/how to do (Directive Leadership) and letting the team figure it out themselves, make some mistakes and learn (Empowering Leadership).

The balance is hard.

You definitely wouldn't want to over-index on either side. So you've got to find a sweet spot.

But it also could be multidimensional, and the balance might shift depending on the area.

For example, you might want to give more direction in terms of the problem the team is solving compared to how the problem is solved. Or you might want to give less direction in the team's communication style but more direction in terms of the standards of produced work.

Regardless, it might be helpful to be open about that balance and have a regular conversation about it.

Because that balance isn't static either. As the team gets better and better, it requires you to adjust the balance.

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.

Tough Love, Strong Teams

Currently refreshing my memory on Radical Candor by Kim Scott. These quotes are amazing:

The best way to keep superstars happy is to challenge them and make sure they are constantly learning.

As you probably know, for every piece of subpar work you accept, for every missed deadline you let slip, you begin to feel resentment and then anger. You no longer just think the work is bad: you think the person is bad. This makes it harder to have an even-keeled conversation. You start to avoid talking to the person at all.

Trust Over Control

Most people think leadership is about control. They assume great leaders are the ones who tell people what to do, make all the calls and keep everyone in line.

That's outdated thinking.

The best leaders don't control. They share context & intent, inspire, empower and trust their teams to make mistakes.

Control stifles. Trust unleashes potential.

Impact Over Firefighting

Bad leaders like convenience over value.

They push those who make their lives easier - small tasks, fire drills and ego bosts. Problem solvers, whose work eliminates chaos, go unnoticed because their success erases the memory of the problem itself.

Leaders fear losing their “firefighters” more than those who ensure a fire never starts. The latter rarely gets rewarded.

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.

Clarity Over Complexity

A strategy isn't about looking smart. It's about making sure everyone understands it.

Clarity beats complexity in any organisation. A strategy packed with jargon or overblown ideas creates confusion, not action. The goal is alignment - getting everyone moving in the same direction with confidence.

Simple, clear strategies win because they get executed.

Leah Tharin - The Death of Classical Sales in B2B SaaS

📘 Sales teams built around short-term incentives create long-term drag. Here's what's happening inside most B2B SaaS companies. Sales reps like “Gary” overpromise because they're incentivised to close deals, not build sustainable value. Product and support teams get blindsided. Customers churn. Internal trust crumbles. Gary's just doing what he's paid for - but the cost to the business is compounding.
📘 The future isn't no-sales. It's product-led... read more

You join a team meeting and just listen.

The team is in control - they cover the options, ask thoughtful questions and share feedback.
You watch them gelling, getting in the flow.
They are considering all the right angles: customer, business and tech.
The conversation moves naturally. They are calm and focused.

They don't even need you there and it feels amazing!

Customers Aren’t Always Right - Their Problems Are

Prioritising customer requests purely by volume is a bad choice.

Volume doesn't mean this is the right problem to solve.
But it still blinds teams.

Yes, customer feedback is great for spotting patterns and surfacing needs. But raw demands don't point to the best answer. Building features based solely on who shouts loudest will result in bloated products or patchwork fixes that don't scale.

A client might demand Feature X but their request likely reflects a deeper pain point solvable in a more elegant, cheaper, faster and more beneficial way.

Strong product teams distil customer insights. Instead of asking: "What do customers want?" ask: "What problem are they trying to solve?".

Your customer problems are your problems.

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.