Business

Feedback lands best when the walls are down.

But too often, it does the opposite. It raises shields. Because even when intentions are good, the words feel sharp. The tone feels off. And the brain - wired for survival, not nuance - reads threat where you meant support.

It doesn't matter how thoughtful or constructive the feedback is. If the other person is in defence mode, they won't hear a word of it. They'll hear judgment. They'll hear risk. They'll hear “you're not good enough.” That's why intention isn't enough. Clarity is what cuts through.

So be clear.

​Not in a vague, corporate tone. In plain language. “You're doing well. I want to help you do even better.” Or, “This is something I wish someone told me earlier in my career - I think it might help.” You're not correcting.

Feedback delivered too late becomes irrelevant or awkward. Deliver it while the moment's fresh and the actions are remembered. But always with context. Always with care.

Because the goal of feedback isn't to win an argument. It's to build someone up without them feeling torn down.

If you're trying to improve how feedback lands, a product management coach can help you practise framing it in a way that actually builds trust.

Frame it right, and feedback becomes a shield. Not a weapon.

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.

No one starts with a perfect strategy. That's just not how it works.

You set a few goals, spot the obvious roadblocks and take your first steps. How about the rest you might ask? You figure it out along the way. Just keep an eye on the market and overall trends and adjust your strategy as needed. And yeah, unexpected problems will pop up. That's normal though. They aren't failures - just part of the process. Every setback teaches you something.

A plan points you in the right direction, but real clarity comes from doing the work. The teams that adapt, adjust, and keep moving - especially when things feel uncertain - are the ones that make real progress.

So don't wait for the “perfect” plan. Just start. You'll get there.

To build great products you need to start asking great questions.

A simple question: “What problem are we solving?” will shift a team's mentality from execution to purpose. And you can feel the exact moment when task-doers start to solve problems.

It's when they talk less about delivery and shipping features and ask more about business challenges, user pain points and the market. That's when they stop taking orders - and start shaping work.

Questions fuel curiosity and curiosity drives collaboration. Teams that ask deeply create better products.

Centralised decision-making will always create bottlenecks. Sooner or later, this will prevent your company from growing.

Traditional and rigid organisations value hierarchy, and leaders often think they need to control every decision.

But this slows innovation, delays time to market, and prevents teams from learning.

Create a culture of ownership at every level. Empower your team to make decisions within their areas of expertise. Trust fuels faster progress.

Joining a new company as a leader is tricky and sometimes it does feel like stepping into chaos.

There's so much for you to process – new people, culture, challenges, expectations, competing and unclear priorities and pressure to deliver results.

I like to slow it down. I don't try to fix everything on day one. I focus on the context, the big picture first, understand the team and what they need my help with. Once I get where we are going and why, I can focus on the culture and processes to get to the destination faster with stronger teams.

It's crazy how many leaders don't know much about their team. They are not curious about their motivations or aspirations, not only professionally but also on a personal level.

Get to know your team. What are their hobbies? What are they exploring? How are their families? Where are they planning their next trip? What are they watching? What are they reading?

Make it a weekly session. It takes just half an hour but builds a much stronger connection. This is important. Stronger connection = more trust. More trust = better feedback, better communication, higher quality of work and more motivation.

Set the Tone

Push others. Push yourself harder. High standards beat perfection. They beat pressure. They are built on one thing - refusing to let average settle in.

Raise the Bar Around You

Call it out when your peers drift. Remind them what great looks like. Challenge your boss to reach higher. Hold the mirror up. Then hold yourself to an even sharper edge. Show them what it means to care - about the work, the craft, the outcome.

Build Incrementally

Pick one standard. Nail it. Then raise another. Layer it like muscle. Burnout comes from trying to change everything at once. Strength comes from building it piece by piece.

Quiet Consistency Wins

High standards are not loud. They are lived. Patience wins. But only if you refuse to lower the bar while you wait.

Kindness Isn't Compliance

Most people confuse kindness with acceptance. Being kind doesn't mean tolerating mediocrity. Great teams grow because someone had the courage to raise the standard when it was easier to stay quiet.

Watch Out for “Good Enough”

Average is always looking for a way back in. It hides in phrases like “good enough” or “we'll fix it later.” Kill that thinking. Make high standards the default - not the exception.

Lead By Example

Start small. One line of copy. One slide. One handover doc. Show the difference. Set the bar by example. Then hold the line. Hold it when no one's watching. Hold it when others let it slip.

Make Quality Contagious

That's how you lead without the title. That's how you make quality contagious. High standards are built in silence. But their results speak loud.

The concept of a Trust Battery is that it typically starts at 50% and then every interaction charges or drains the trust battery.

It's interesting how, once you pass a certain percentage - let's say 80% (mind you, it's a bit abstract) - on the other person's Trust Battery, a shift happens. Walls drop. And suddenly the next level of collaboration unlocks.

Love these moments.

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

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.

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

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.

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.

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