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.

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. People notice, even in silence and they remember. Honour commitments - trust depends on it.

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.

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.

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.

And the polar opposite:

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.

As a leader, it can get very tough. Or at least it might seem that way. You might have the most amazing relationship with your direct report; you might even call it friendship. But if the person doesn't perform, you have to address it.

And the solutuion is actually quite obvious….you have to call it out and address it as it's your direct responsibility as a manager. And if you consider yourself a friend as well.

The alternative is all downsides: you're not doing your job, you're not helping your friend by denying them an opportunity to learn and you're also dropping the team standards.

Your team operates at its weakest link and helping that person helps everyone.

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.

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.

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.

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.

📘 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!

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.

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.

Everyone talks about ‘hitting the ground running' after the Christmas break.

Let's be honest, no one feels like sprinting straight away at this time of the year.

Some are still catching up on sleep, recovering from all the desserts they've eaten, wrapping their heads around what day it is and trying not to fail one of their New Year's resolutions in the first week of the year.

Forcing yourself into work mode overnight is hard.

I'd rather ease into it. Spend the first day reconnecting with your team, archiving all the emails from last year and marking all Slack messages as read. Oh, that feels great.

By the second day, you're already feeling more in control.

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.

You don't need a fancy tool to manage your team.

Complex software won't fix miscommunication or misalignment. Tools often distract, leading to over-documentation, micromanagement and wasted focus on processes over outcomes.

Management is clarity. Set expectations, align on what's important and build trust with open, honest conversations. Keep the focus where it belongs - on the work itself.

Competition boils down to two questions.

Can competitors do this? Will they? The first measures capability, the second intent. Together, they predict your landscape.

Anticipating both keeps you ahead.

Uncertainty defines startup life.

Prioritising the right problems keeps you grounded. Communicating your vision aligns your team. Flexibility lets you navigate the unexpected. These habits aren't luxuries - they're survival skills.

Adaptability and focus turn uncertainty into opportunity.