Have you ever felt that the way decisions are made in your company is slowing your work down?
Or that the tech debt you’re paying for today is really the result of yesterday’s decision-making problems?

Maybe the wrong people made the call.
Maybe not all the data and constraints were on the table.
Maybe the people closest to the problem were never asked.

One of the biggest success factors for a company is its organisational model.
And I don’t mean job titles and reporting lines. I mean the decision-making structure: who decides what, based on which input, and how those decisions flow through the organisation.

You can think of this as a system: ideas pop up from teams, leaders, customers. They flow through the organisation, and some of them eventually become decisions that are executed.

But on their way to execution, things can go wrong:

• Bottlenecks – everything has to pass through one or two people.

• Good ideas get blocked because they land in the wrong forum or never reach the right owner.

• Bad ideas get promoted and prioritised without solid data or reasoning.

• Too many ideas are accepted without structure, and the product slowly turns into a mess.

If you don’t design this decision system deliberately, it will design itself. And you probably won’t like the result.

Examples of Immature Decision Design

Let’s dive into a few classical examples that point to a low maturity of the decision making system.

Example 1 – When one person becomes the decision bottleneck

In a young company, having one strong person at the centre of decisions can work surprisingly well.

Often that person is the CEO or CTO. Sometimes it’s a highly trusted senior engineer or other “glue person” who’s been around forever and seems to know everything.

They know the product inside out. They sat with the first customers. They remember every shortcut and trade-off made along the way. At that stage, routing major decisions through them is often the fastest and safest way to move.

The problem is that many organisations keep this decision pattern long after they’ve outgrown it.

The consequences:

• Decisions slow down.
  Teams are ready to move, but the next available slot in this person’s calendar is in a week or two.

• Decisions are made too far from the details.
  When every big choice is compressed into a short call or a couple of slides, a lot of nuance gets lost: edge cases, UX details, operational constraints. The decision might be directionally sensible, but misaligned with the messy reality of how the product behaves today and how the teams actually work.

• Teams stop feeling real ownership.
  Once the pattern is established, people either

  • relax, because “someone else is carrying the load”, or

  • get frustrated that “someone else is making the decision for us”. They might tweak slides to “sell” their story, or quietly give up on what they believe is right and fall back on: “We just follow a given direction.”

This is a decision-making system that was never designed for scale – one that still assumes a single person can and should sit in the middle of everything.

Example 2 – When no one owns a domain end to end

Another common pattern: many people shape a critical domain, but no one owns it end to end.

This domain might be the overall product experience, the overall product architecture, or a key product capability (onboarding, billing, search, integrations, etc.).

Different parts of the organisation drive different changes:

• Commercial teams push for features to close key deals.

• Operations pushes for changes to reduce manual work.

• Engineering pushes for refactors, performance and reliability.

Each initiative is valid. And each group has enough influence to get some of their needs into the roadmap. What’s missing is a clear owner of the domain as a whole – someone whose primary responsibility is to ask:

“How do all these changes fit together into one coherent system or experience?”

When everyone is pulling hard on their part of the rope, with no end-to-end owner for the domain, the overall direction is accidental.

Over time, you see the consequences:

• Product complexity. The product gets cluttered - user experience confusing, technical complexity increased with special cases or “just this once” hacks.

• Roadmap by negotiation. Priorities are set through escalation and negotiation. If you put all ongoing activities next to each other, you’d struggle to explain why some of them made it through as top priority or how they connect to company goals.

• No coherent “no”. Nobody is clearly mandated to say: “This request makes sense locally, but it weakens the product or system overall”.

The result is a gradual drift away from a sharp value proposition and a clear architecture, towards a product that reflects internal politics more than user needs.

Example 3 – When roles overlap and nobody is clearly accountable

Another common pattern is when leaders have overlapping scope.

On the org chart, it looks mature and well-structured – roles like Head of Platform and Head of Architecture, or Group Lead and Head of X.

But when their responsibilities aren’t sharply defined, the day-to-day reality gets inefficient very quickly.

Alignment overhead increases. People add more syncs: 1:1s, pre-meetings, “quick catch-ups”.

Double work or no work. Two people are writing their own strategy, principles or roadmap, or proposal, and then have to merge them afterwards. Other times, each assumes the other will take the lead on a tricky decision, so nothing happens until someone escalates.

Teams get stuck in ambiguity. When roles overlap, teams are never quite sure whose call it really is. So they start to: check decisions with both leaders “just to be safe”. They spend more energy navigating opinions and less energy on moving the work forward.

This is what happens when we create titles without clear decision rights.
It doesn’t create a big chaos, but it does reduce effectiveness and slows delivery down.

Principles to Design Your Decision-Making Architecture

All these examples share the same root cause: ownership and decision rights were never deliberately designed.

Don’t let your decision system “just happen” - you probably won’t like the result.

Instead, treat decision-making as part of your architecture: something you can design, test, and improve.

Once you look at it that way, a few simple principles can help you put the right setup in place.

Principle 1 – One strategy, one owner

For every important area, there should be one clearly named person who owns the strategy and how decisions are made in that area.

But:

One owner does not mean one person decides everything.
It means one person is accountable for the decision system in that domain.

Their job is to:

• Set direction and constraints.

• Decide which decisions are delegated and to whom.

• Step in when there’s conflict or ambiguity.

When you don’t have one owner, you get “everyone influences, nobody owns”.
When the owner decides everything, you get a bottleneck.

Principle 2 – Push decisions to the lowest level with enough context

Good decision architecture follows a simple rule:

Leaders define direction and rules.
Teams decide how to get there.

Decisions should live where:

• The information is richest (close to users, systems, incidents).

• The consequences are felt (by the people who build and run the product).

Leaders and domain owners should be asking:

• Which decisions must stay at my level?

• Which decisions can teams make on their own?

• Do they have the right business information and context to make that call?

If small UX choices, tech approaches, and team-level prioritisation still routinely go to the CEO/CTO/board, you don’t have strong governance – you have a centralised anti-pattern.

Principle 3 – Clear boundaries of responsibilities

“Shared ownership” sounds healthy.
In practice, shared ownership without clear boundaries usually becomes blurred accountability.

You want statements like:

• “You own this domain; I own that one.”

• “You decide implementation; I decide which problem we solve first.”

• “You own reliability for this surface; I own scope and timelines.”

If you ask, “Who decides when you disagree?” and people hesitate, your boundary isn’t real.

Double work, and “we thought the other person would lead this” are all symptoms of ignoring this principle.

Principle 4 – Treat important things as components with owners and metrics

Some parts of your product and organisation are critical or chronically painful.

If something is important, repeatedly painful, and measurable, consider treating it as a separate component.

That means:

• Give it a clear boundary – what’s inside, what’s outside.

• Assign one strategy owner.

• Define a small set of success metrics.

For example, “Customer data integration” for new clients. Instead of being everyone’s problem (sales, implementation, ops, backend), you treat it as a component:

• Set one owner accountable for the end-to-end integration experience.

• Set metrics like time-to-first-sync or number of one-off scripts to show measurable progress.

You can apply the same thinking to other domains that you find business critical.

Principle 5 – One owner, many deciders, shared principles

You don’t want either extreme:

• Centralised decision making: one person decides everything.

• Chaotic decision making: everyone decides everything.

The middle ground:

One owner for the strategy and decision system.
Many people making decisions locally.
All using the same principles.

Those shared principles can be, for example:

• Product principles – who we build for, how we want the product to feel, what we won’t do even if asked.

• Architecture principles – how systems interact, expected uptime and reliability, how configurable or bespoke the system is allowed to become.

Over time, these principles become part of how people think – ground rules that teams follow almost intuitively when they decide what to do next.

Principle 6 – Make important decisions visible

Invisible decisions are a source of rework or blame.

You don’t need heavy process, but you do need a habit.

For meaningful decisions, capture briefly:

• What we decided.

• The key options we considered.

• Who decided and who was consulted.

• What we’re trading off.

You create a “log” for the decision thinking, so you can later see patterns and refactor how decisions are made.

5. Where to Start: Refactor Your Decision-Making System

You don’t need to fix decision-making with a big-bang reorganisation.
You fix it the same way you fix a complex system: find one painful area, change how it works, learn and repeat.

Here are some tips on how to start.

1. Pick one domain

Pick one domain that you find important or where you observe a continuous pain. For example:

• A part of the product where development feels slow.

• A new capability (onboarding, billing, integrations) that is cluttered and confusing.

• A platform or architectural area where everyone has opinions and complains.

2. Do a quick decision audit

For the last 2–3 months in that domain, ask:

• What were the 3–5 biggest decisions?

• Who actually made them? How did they get there? (escalation, board meeting, data …)

• Which ones went well, and which felt painful, slow or frustrating for the team?

• Were there hidden, conflicting principles at play (“move fast” vs “minimise risk”) that nobody named explicitly?

3. Apply “one strategy, one owner”

Appoint one owner for that domain.

Make it explicit that their job is to:

• Own the strategy and direction for that domain.

• Design the decision system: who decides what, and where.

• Define metrics that person is responsible to drive.

Write it down in one or two sentences so everyone understands it.

4. Decide which decisions move down

With that owner and the core team for the domain, walk through:

• Which decisions genuinely belong with the owner? For example, big trade-offs, cross-team conflicts, major bets.

• Which decisions should we move down to teams? For example, implementation, UX details, local prioritisation, experiments.

Check if teams have enough context and information to own those decisions.
If not, fix that: share metrics, strategy, or any business constraints.

5. Set a few principles as guardrails

Co-create a small set of domain principles.

For example: “We optimise for user experience. Clear, intuitive design is our differentiator, even if it costs us extra effort in implementation.”

In exceptional situations, you might need to break a principle – but that should feel exceptional: the owner is consulted, or the decision is clearly logged as a conscious deviation.

A simple test: If people can’t use these principles to make everyday decisions without asking for permission, they’re too vague.

Tighten, clarify, and iterate until teams can confidently decide and still stay inside the guardrails.

6. Make it visible

Create a one-pager for the domain. Summarise important points like:

• Domain name

• Owner

• Key teams involved

• Main decision boundaries (owner vs teams)

• 3–5 principles

• Key metrics (if relevant)

Share it on Confluence. Point to it in meetings. Use it when someone asks “who should decide this?”.

7. Add light decision logging

Capture the key decisions in 1–2 short paragraphs each: what we decided, why, who decided, and what we traded off.

Then, every now and then, review these with the owner and the teams:

• Are we escalating the right things?

• Are the principles actually helping teams decide on their own?

• Are we still too centralised, or drifting back into chaos?

If the logs turn out to be useful, keep the habit.
If they’re not adding value, change the format or frequency—but don’t go back to a world where important decisions leave no trace at all.

Closing Thoughts

You can’t scale your organisation on the same decision system you designed for Day 1.

If you let your decision system “just happen”, it will – but you probably won’t like the result.

Ask yourself:

Have we designed a decision-making system that matches our size, strategy, and reality?

If not, start where the pain is highest – the overloaded executive, the incohesive product area, the overlapping roles – and begin to redesign your decision-making architecture iteratively and deliberately, one step at a time.

Enjoyed this Article?

Subscribe to Lean Product Growth for regular updates on building and scaling a successful product organization. Insights, strategies, and actionable tips—delivered straight to your inbox.

👉 If you found this useful, you might also enjoy my other articles on leadership, product strategy, and team dynamics:

If you’ve been in a Management Team long enough, you’ve heard this question. Big goals are set, the strategy looks sharp on slides, and the plan feels achievable.

But a few months later, deadlines slip, priorities shift, and frustration sets in. Three more months pass, the same thing happens again. Eventually, the strategy itself pivots, and the whole cycle restarts.

The common explanations are familiar: not enough resources, too much tech debt, too many dependencies. All of these can play a role, but they aren’t the root cause.

The deeper issue is the translation gap — the space between the dream at the top and the day-to-day work items at the bottom.

How Strategy Fades on Its Way to the Backlog

Big goals are born in MT meetings and boardroom slides. But while leadership spends its time shaping strategy,

business outcomes don’t live in the boardroom. They live in the backlog.

And the problem is: between the vision and the moment a developer picks up a ticket, the message gets reshaped again and again:

Each step is another round of broken telephone. Clarity blurs. Context gets lost. Sensitive details get softened. Gaps are filled with assumptions.

By the time a backlog item lands with a team, it often barely connects to the original goal. Work gets shipped, but it doesn’t move the business forward. Teams feel urgency — “This needs to be done by tomorrow” — but urgency isn’t the same as impact. Finishing it quickly doesn’t mean it addresses the core issue.

It’s like hitting the edge of the target instead of the bullseye: effort spent, but not full impact.

The result: energy spent, deadlines missed, and business plans slipping. Not because engineers can’t deliver, but because strategy doesn’t survive translation.

Scaling the Waste

When you have one small team, a translation gap might cost you a sprint. Painful, but manageable.

Now picture a company with 100 teams. Each one is a few degrees off. No single team is failing outright, but together those small misalignments snowball into missed quarters and plans.

And the more layers you have, the longer the telephone line gets — and the fuzzier the message becomes. That’s why large organisations often feel slow: the translation gap compounds faster than the company grows.

Culture as a Multiplier

Culture determines whether translation gaps get corrected or ignored.

In transparent cultures, teams feel safe to say: “This doesn’t connect to the bigger goal.” Concerns surface quickly, leaders hear the bad news early, and course-corrections happen before waste piles up. Miscommunication still happens, but it’s smaller and resolved faster. People can commit ambitiously because they know raising risks won’t get them punished.

In cultures of fear, the opposite happens. Progress gets sugarcoated. Promises blur as each layer colours the truth with polished updates instead of directness. Doubts are whispered in hallways, while official updates look safe. Engineers may see the real blockers, but if their voices aren’t welcome, leaders only learn the truth when it’s too late. Rigid, top-down roadmaps make it worse: people commit because they must, and communication turns into spin.

Transparency multiplies alignment. Fear multiplies waste.

The Leader’s Role in Closing the Gap

Leaders often underestimate how much of their job is translation. Setting the vision is only the start. The real work is making sure that vision can survive the long telephone line of portfolios, roadmaps, and backlogs without losing its meaning.

Here are some principles that help close the gap:

1. Fix the culture.

Create psychological safety so people feel comfortable speaking up when things don’t line up. Google’s research highlights psychological safety as the #1 factor in top-performing teams.

Listen carefully, show understanding. Model direct communication yourself by speaking plainly and being clear with the facts you can share. A practical way is to ask openly where things don’t connect and thank people for pointing it out. Group meetings, one-on-ones, or anonymous surveys can all help. When honesty is normalised, issues surface faster.

Way too often I’ve seen teams without psychological safety. Status updates looked polished, but real blockers were not raised. Communication became blurry and expectations drifted away from reality. The result — big delays, frustration and failing plans.

2. Simplify the chain.
Structure and clarity in the operating model are essential, especially as organisations grow. But every extra layer makes the telephone line longer and increases the risk of the strategy getting lost. Too many layers dilute the goal itself.

Be mindful of the balance. Cut unnecessary steps, shorten reporting lines, and give people enough autonomy to make calls without multiple escalations.

Watch out for roles with unclear responsibilities. This leads not only to duplication of effort, but also wasted time spent on alignment rather than progress.

You might have experienced situations where getting approval for a new tool requires five different sign‑offs. By the time the decision comes through, motivation has dropped and the relevance gone.

Simplify the chain. The simpler the chain, the clearer the message stays.

3. Clarity in communication (it is never too much).
A message that feels obvious in the boardroom can become vague two layers down.

Keep repeating goals until they stick. And use a plain and consistent language. Same phrases consistently across presentations, dashboards, and team updates.

Be consistent with terminology too. Business goals should have a clear and stable name. Initiatives should also have names that don’t change from one slide to the next. When labels shift, people get confused. When terms stay steady, the strategy becomes easier to follow.

For example, pin the top three goals to every company-wide deck, and make sure Jira epics or initiatives reference them directly.

Over-communicating clarity is better than letting silence create confusion.

4. Connect work to outcomes.
Backlog items only have real value when they clearly tie to business goals. The connection should be visible across every layer: from business goals to initiatives, from initiatives to roadmaps, from roadmaps to epics, and from epics to backlog items. When this chain is transparent, even the smallest ticket can be traced back to a meaningful outcome.

Explicit traceability is not bureaucracy — it prevents drift and keeps motivation high. People work harder and smarter when they know how their piece of the puzzle contributes to the bigger picture.

Consistency also matters. Use shared terminology across product, business, and engineering. If business calls it a “growth initiative,” product calls it an “epic,” and engineering calls it a “feature,” it causes confusion. It’s best to choose names that resonate with everyone and stick with them.

A practical step: set up your tools so this linkage is easy to see. For example, connect user stories to epics, epics to initiatives, and initiatives to top-level goals in your planning tool. Dashboards that show progress along this chain help leaders and teams speak the same language and see the same outcomes.

5. Keep communication data-driven.
Every time I see metrics and charts in a meeting, the discussion shifts. It becomes more objective, less biased, and less vague. Metrics ground conversations in evidence and make progress visible.

But data is not a replacement for dialogue — it should support it. Numbers need to be interpreted in context. Good leaders ask: What story does this data tell, and does it match what’s really happening on the ground?

When you keep the conversation data-driven, bias and emotions have less room to dominate and decisions become clearer.

Used well, data is a lever that increases alignment and effectiveness. It connects backlog items to real outcomes and helps everyone see whether the work is truly moving the needle.

Closing Thoughts

Delivery doesn’t fail because teams can’t ship. It fails because strategy doesn’t survive the journey from the boardroom to the backlog. The big goals blur, context gets lost, and thousands of small items drift just far enough off course to dilute the outcome.

Perfect alignment will never exist. But every step you take to close the translation gap pays back many times over.

When small backlog items line up with the bigger dream, they create compounding impact. That’s when business dreams start becoming reality.

Enjoyed this read? Subscribe to Lean Product Growth for regular updates on building and scaling a successful product organization.

Subscribe now

Access more product content on Lean Product Growth

They succeed because people believe in them.

As a leader, your role isn’t just to see the future — it’s to make sure your team can see it, feel it, and choose to walk there with you.

When Your Big Idea Lands Flat

You’ve had that spark of clarity. Maybe it came during a walk or a late-night brainstorm. You’ve just discovered a new workflow platform that could finally bring order to the chaos — automate the repetitive tasks and cut your team’s workload significantly.

In your mind, it’s a no-brainer: faster, better, more efficient.

You can’t wait to share it with your team.

So you step into the meeting, and announce: “Here’s the big idea. If we do this, we’ll unlock huge value.”

And then — silence. Someone cautiously raises a doubt. Another wonders aloud if this is just the latest in a long line of “new priorities.” A couple of polite nods suggest the message didn’t quite land.

Your idea might be strong. But your team isn’t there — not yet. And without their belief, even the greatest idea quickly fades as business as usual takes over.

That hesitation reveals there is a gap between your vision and your team’s belief.

Closing that gap doesn’t happen with a single speech or a polished slide deck. It happens step by step — in how you listen, how you show progress, and how you bring people along.

Here’s how.

Lesson 1: Start With Their Reality

Leaders often forget: while you’ve been connecting dots and thinking about the future, your team is fighting the present. Tight deadlines, bugs, customer escalations, or simply too much on their plate.

That’s why influence doesn’t begin with your vision. It begins with their perspective.

Ask questions. Listen deeply. What do they see? What’s blocking them today? What trade-offs feel impossible?

By starting here, you’re not only gathering insights that make your idea stronger — you’re showing respect. People are far more willing to move if they feel heard.

And if you can connect your vision to the problems they’re already fighting with, even better. Show them how tomorrow could be a little easier than today. But don’t jump too far ahead — your team doesn’t need a five-year utopia. They need to picture what changes in the next sprint, the next month or the next quarter.

Lesson 2: Plant the Seed Gradually

After you’ve listened to your team’s reality, the next step is to plant the seed of your idea.

Think of it like a gentle introduction rather than a one-time pitch. Mention the concept in a few different contexts, ask for opinions, and let it settle in. Give people the space to get used to it before expecting enthusiasm.

By surfacing the idea gradually, you make it feel familiar instead of disruptive. It’s not about pushing hard — it’s about making the change feel natural, almost inevitable.

And through these informal conversations, you’ll sense when the time is right to move forward and bring the idea to life.

Lesson 3: Find Your Early Adopters

Not everyone in your team is ready to jump into something new. Some are comfortable with the status quo — they might complain about the problems, but hesitate to risk trying a new solution.

But others lean forward. They’re curious, restless, or simply too frustrated with the current way of working to keep doing it the same old way.

Those are your early adopters. Start with them.

Give them space to test your idea in a smaller, safer way. Encourage them to experiment, adapt, even fail — and let them shape the first iteration. When progress becomes visible, these early adopters turn into your champions. They’ll share their experience in a language the rest of the team trusts far more than your presentation could.

Lesson 4: Start with a Small Pilot

Once you’ve got your early adopters on board, the next step is to set up a proof of concept—a small, manageable pilot that can show real results quickly. Think of it as a low-risk experiment that gives everyone a glimpse of what success could look like.

By starting small, you’re making the change feel less intimidating and more achievable. You're giving the team a chance to see tangible progress without the pressure of an all-or-nothing rollout. It's a way to build momentum naturally.

In other words, a pilot not only proves the concept—it gives your team a taste of success. And once they see those early wins, they're much more likely to get fully on board.

Lesson 5: Share the Wins Through the Team’s Voice

Once your small pilot has shown some real results, it’s time to share those early wins with the rest of the team.

Let your early adopters do the talking.

When the message comes from their peers—people who have actually used the new approach and seen the benefits—it feels much more genuine and relatable.

Encourage those early adopters to share their experiences in team meetings or informal chats. They can talk about what’s improved, what they’ve learned, and how it’s made their work easier or more effective.

This kind of peer-to-peer sharing can be much more effective than any polished slides or a top-down communication.

Lesson 6: Scale Gradually and Keep Iterating

When your early wins are visible and your champions are spreading the word, it’s time to scale. This doesn’t mean scaling overnight — it works best in stages.

Begin with one or two teams, learn from their experience, and then expand across the wider organization. Each step strengthens credibility and lowers the risk of a failed “big bang” rollout.

And remember: scaling isn’t about rolling out a “finished” idea. It’s about growing and refining it as you go. Keep feedback loops open. Ask what’s working, what’s frustrating, and where the idea can be improved.

Each iteration makes the solution stronger and increases ownership at every level.

Final Thoughts

In the end, turning a big idea into a shared reality is all about listening, planting the seeds, finding those early believers, and scaling thoughtfully. It’s not about rushing or pushing—it’s about guiding your team step by step until your vision becomes their dream.

And remember:

Belief is the real test of leadership.

Ideas are easy. Belief and action are what make them real.

👉 Want more practical leadership insights for scaleups? Subscribe to Lean Product Growth for regular updates on building and scaling a successful product organization.

Subscribe now

This thought often comes to mind when I’d look at a roadmap for the first time.

A roadmap isn’t just a delivery plan — it’s a cultural scan. Look closely, and it tells you a lot more than what’s being shipped. You can read:

• Decision-making style – Is it driven top-down, or do teams genuinely shape what gets done?

• Trust levels – Do leaders trust teams to commit openly, and do teams trust leaders to stick with priorities?

• Political balance – Which initiatives get the spotlight, and which quietly disappear?

Clues Hidden in Every Roadmap

An org chart shows how your company is supposed to work. A roadmap shows how it actually works.

Here are some clues hidden in every roadmap.

1. How Much is in it

Is the roadmap crowded with initiatives, or does it focus on a small number of deliberate bets?

What it reveals:

• An overloaded roadmap signals a reactive culture, attempts to satisfy too many stakeholders, or weak prioritisation. In practice, many of these items will likely remain unfinished or only partially complete as the team tries to tackle them all at once.

• A focused roadmap Indicates strong product leadership, clear trade-offs, and the confidence to say “no” when necessary.

An overloaded roadmap creates inefficiency. Stakeholders stop believing commitments, and teams often feel demoralised by carrying half-done work from one cycle to the next. A focused roadmap builds credibility, keeps energy behind the most important priorities, and increases the odds of delivering meaningful impact.

2. Time Horizons

Does the roadmap lay out detailed plans 12–18 months ahead, or does it focus only on the next quarter?

What it reveals:

• A very short-term (only the next sprints) roadmap indicates agile maturity and focus on learning. However, if there’s zero view beyond that, it often means reactive planning and no strategic clarity. This creates uncertainty for stakeholders and makes it hard to align resources.

• A detailed yearly plan may be necessary in regulated or highly predictable contexts. However, in many cases it’s a sign of top-down, milestone-heavy thinking that sacrifices flexibility and locks teams into outdated priorities.

• A balanced approach is an example of an effective roadmap. It illustrates clear, more concrete plans for the next quarter (where execution is in focus), while keeping longer-term items more strategic and less fixed. This ensures teams have both direction and room to adapt.

A roadmap’s time horizon shows whether the organisation is optimising for control or adaptability — and whether it’s being honest about the uncertainty it faces.

Too short, and you risk drifting without direction. Too long, and you risk building the wrong thing very efficiently.

3. Language

Are items described in broad, generic terms like “Enhance platform capabilities”, or in clear, outcome-focused language like “Reduce mobile checkout time from 90s to under 45s”?

What it reveals:

• Vague language is often a sign of fear of commitment, internal politics, or a desire to keep all stakeholders happy without making trade-offs visible. It can also signal lack of clear focus and lack of clarity on what the team wants to achieve.

• Specific, outcome-oriented language suggests high trust, alignment on priorities, and a willingness to be held accountable for results. Teams understand the problem they’re solving and the value it delivers.

The way work is described reveals the psychological safety and clarity within the organisation. Clear, measurable language makes it easier to prioritise, track progress, and know when something is truly done. Vague descriptions keep everyone busy — but make it hard to tell if you’re moving the needle.

4. Work Mix

Does the roadmap include a balance of new features, maintenance and technical improvements — or is it almost entirely focused on shipping new features?

What it reveals:

• A Balanced Mix shows leadership recognises that sustainable delivery requires continuous investment in product health and stability. It also signals an understanding that reserving capacity for experimentation and discovery is essential — both to keep the product differentiated today and to unlock new opportunities for tomorrow.

• Feature-only means that progress with new features takes priority over long-term value. With no dedicated space for maintenance, debt reduction, or exploration, the product risks slowing down over time and missing chances to create differentiated solutions.

Focusing only on short term wins almost always backfires at some point — and usually at the worst possible moment, such as during a major release or growth push. A roadmap that consistently allocates time for technical improvements or innovation has much higher chances for long term success.

5. Silos vs. Collaboration

Is the roadmap divided into separate streams for components (e.g., frontend, backend, infrastructure), or is it organised around shared outcomes that deliver value end-to-end?

What it reveals:

• A component-focused roadmap suggests siloed ways of working, where each function optimises its own output without a clear view of the overall outcome. This often leads to delays, unnecessary handoffs, and a lack of accountability for whether real value is delivered.

• An Integrated roadmap indicates cross-functional collaboration, with teams aligned on solving problems and delivering value as a whole. Work is framed around customer or business impact, not internal boundaries.

When work is planned in silos, teams may look productive on paper but fail to deliver meaningful results. A roadmap centred on outcomes fosters alignment, reduces waste from handoffs, and ensures that every function contributes directly to value creation.

6. Outcome Framing

Does the roadmap list outputs like

“Launch new reporting dashboard”, or does it describe problems to solve and results to achieve, such as

“Enable managers to identify performance issues within 24 hours”?

What it reveals:

• An output-driven roadmap means that success is measured by shipping deliverables, regardless of whether they create value. This mindset often leads to teams hitting deadlines but missing the real needs of users or the business.

• An outcome-driven roadmap shows that the focus is on the impact, value, and learning gained from the work, and on how each initiative connects to bigger strategic goals. It shows that the team understands why they’re building something and leaves space for iterating on the how. It encourages exploration for different solutions options that may deliver greater results than the original idea.

Framing shapes behaviour and changes team’s focus. If the roadmap speaks in outputs, teams will optimise for outputs — delivering what was asked for, but not necessarily what was needed. Outcome-focused framing, especially when tied to broader organisational goals ensures that delivered work moves the company meaningfully forward.

When the Roadmap Isn’t Grounded in Reality

Not every roadmap reflects how things actually work. Some are designed to look tidy for investors, customers, or executives — polished artefacts that tell a simple story but leave out the messy truth.

You can often recognise one of these when:

• Work is evenly distributed across teams, as if by design.

• No delays, trade-offs, or shifts in priorities are visible.

• Every item is framed as equally important.

In these cases, the real working roadmap usually exists elsewhere in a less polished form. But even the curated version still tells you something valuable: it shows the image the organisation wants others to believe about its priorities and culture.

How Leaders Can Use This Knowledge

If you’re a leader, you can put this roadmap-reading skill to work in two ways:

1. Audit your own roadmap
Step back and look at it like someone seeing it for the first time — maybe a new hire or an external partner.

• What story does it tell about your culture, priorities, and decision-making style?

• Does it reflect the organisation you are, or the one you want to be?
  If there’s a gap, that’s your cue to adjust — not just the roadmap, but the way you set priorities and communicate them.

2. Decode roadmaps in new environments
When joining a new company or taking over a team, ask to see their roadmap early.

• How is work framed — outputs or outcomes?

• Who owns what, and how balanced is the mix of work?
  You can often learn more about the real dynamics, decision-making habits, and cultural tone from a roadmap than from any onboarding pack or company presentation.

Your roadmap is more than a plan — it’s a mirror. Whether you like it or not, it’s telling a story about your priorities, your culture, and your leadership style.

The only question is: are you happy with the story it’s telling?

👉 If you found this useful, you might also enjoy my other articles on leadership, product strategy, and team dynamics.

Subscribe to Lean Product Growth for regular updates on building and scaling a successful product organization. Don’t miss out on insights, strategies, and actionable tips—delivered straight to your inbox.

Subscribe now

Most of my toughest weeks as a leader didn’t come from poor execution—they came from failing to manage up.

It wasn’t about doing better work. It was about making the work visible, understandable, and assuring that things were under control.

Not every manager will have the time or space to dive deeper and understand the nuance behind your decisions.

The good news? It’s a growth opportunity. These moments push you to sharpen how you communicate, build trust through clarity, and grow your influence by connecting the dots consistently.

Managing up isn’t about politics. It’s not about playing games or performing for promotion. It’s about communicating with intent. It’s strategic storytelling: ensuring your impact is seen, your direction is clear, and your team’s work continues to move forward.

1. Communicate Regularly and Reliably

I’ve seen leaders clean up internal chaos in just two months—only to face skepticism in the management room.

Why?

Because they forgot to tell the story. They focused entirely on solving the problem and assumed results would speak for themselves.

But senior leaders don’t always have the luxury to wait for the full picture. And when they don’t hear progress, they often assume there isn’t any.

When you don’t communicate on time, decisions get made based on assumptions. Your brilliant progress might go unnoticed. Your great idea might be missed. The team’s success can stall—not because of performance, but because of perception.

Communicating progress isn’t extra work. It is the work.

Even if no one is asking, create visibility. It’s your responsibility.

A 1-on-1 update, a concise email, a short Slack post, or a one-slide summary—choose whatever fits the context.

Align early on how your manager wants to stay informed. Ask:

“What’s the best way for you to stay updated—weekly summaries, monthly highlights, or something in between?”

Make it easy for them to digest the update and see your impact—and even easier for them to share it when you’re not in the room.

2. Bring Just Enough Detail

When you share too little, your manager fills the gap with assumptions.

When you share too much, you risk overwhelming them—or losing their attention altogether.

The skill is in calibrating just enough.

Start with the outcome and your rationale. Let their curiosity pull you deeper if needed.

“We considered three options. We’re leaning toward Option B. This is fastest to implement, and lowest cost. Happy to go deeper if you’d like to unpack it.”

If you’re unsure of how much to share, just ask:

“Was this too high-level or too detailed? What would make it more useful for you next time?”

Remember: your goal isn’t to offload your entire thought process—it’s to build clarity and trust.

3. Don’t Try to Impress—Try to Inform

You live the details. Your manager doesn’t.

Your job is to elevate the signal from the noise.

They don’t need the full story—they need the headline, the why, the next steps. And they need your level of confidence to bring everything to green.

Don't aim to impress with technical depth. Don’t make drama out of the challenging problem you’ve managed. Aim to inform with clarity.

Instead of:

"It’s really complex and challenging. We’ve been firefighting 2 days. Let me walk you through everything.

Say:

"We hit a blocker that affects our timeline. Here’s what we’re doing about it. We have high confidence that this will bring things on track.

Your credibility goes up when you keep it simple and grounded.

4. Show Ownership and Accountability

Things won’t always go as planned. Your manager knows that. What they want to see is whether you’re in control, and confident in how to move forward.

If you hit a blocker, acknowledge it. That’s normal. But don’t stop there—show that you're thinking ahead. What are the options? What’s your next move?

Instead of giving excuses or blaming someone else

“We didn’t make progress because X didn’t deliver and Y failed.”

Show how you plan to solve the problem.

“We hit a blocker. Here’s what we’re doing to resolve it. We may need a decision from X to proceed.”

Own the resolution, even if you don’t own the problem. That’s what accountability looks like.

And if you don’t feel on top of the situation or you are out of options—say so. Earlier is better. Ask for help clearly and calmly:

“We’re hitting repeated blockers, and I don’t think we can fully resolve them internally. I’d appreciate any input or ideas you might have.

It’s not a sign of weakness. It’s a sign of leadership maturity—naming the problem, proposing a path forward, or asking for help when necessary.

5. Keep Your Composure—Even When It’s Hard

This might be the most transformative habit you can build for long-term leadership success:

Don’t match emotion with emotion.

One of the most powerful lessons from a recent leadership program was this:

Ego meets ego = explosion. Ego meets calm = clarity.

Mature leadership means mature communication. Even when a conversation gets tense. Even when you're challenged unfairly. Your tone sets the tone. And your ability to stay calm when others aren’t is what builds trust over time.

Stakeholders, execs, and team members won’t always react positively. But that’s not your cue to mirror their energy. It’s your moment to steady it.

Hold this mindset close:

“I do the best I can. I don’t take it personally. I’m here to help.”

This is what separates reactive managers from grounded leaders. It’s not about suppressing emotion—it’s about choosing response over reaction.

If you struggle with this, start by reconnecting to why you’re in this role. You care about outcomes. You’re here to build. And not every challenge is yours to absorb.

Staying grounded doesn’t just improve the moment—it defines your presence as a leader.

6. When Your Ideas Don’t Land, Be Strategic

Sometimes you have a brilliant idea, but you can already feel the resistance in the room.

Don’t push. Pause. Reflect. Look for the gap.

The timing might be wrong. The context might be missing. The trust might not be there yet.

Don’t be pushy or let your ego get bruised when things don’t click immediately. Be strategic in how you build alignment. Strong ideas need strong delivery to land well.

Instead of:

"This is clearly the right path. I don’t understand why we are not doing it."

Say:

"I get that this might feel early. Would it help if we tested this idea on a small use case and learned from it together?"

Start small. Let people see the value first, not just hear about it. Be strategic in how you build alignment.

Managing Up Recap

No matter how capable or empathetic your manager is, they can only make decisions based on what they know—and what they know often comes from you.

If managing up feels awkward or unnatural, you’re not alone. It’s rarely taught. But it’s a skill that’s learnable.

Here are the essentials to keep in mind:

• Make your work visible. Don’t wait for the results to speak for themselves—it might be late.

• Adapt to their style. Communicate in a way your manager can absorb quickly and act on.

• Aim to inform, not impress. Keep it clear and to the point.

• Own the resolution. Even if you don’t own the problem, show how you’re moving forward.

• Ask for help early. It shows maturity, not weakness.

• Stay calm when it’s hard. Your tone sets the tone—especially under pressure.

• Be strategic when ideas don’t land. Timing, trust, and delivery matter just as much as the idea itself.

  Managing up isn't just a skill—it’s a leadership accelerator. The more intentional you become, the more your impact compounds.

Enjoyed this Article?

Subscribe to Lean Product Growth for regular updates on building and scaling a successful product organization. Insights, strategies, and actionable tips—delivered straight to your inbox.

Subscribe now

Then you step away.

And suddenly—momentum stalls. Decisions pile up. Priorities blur. The clarity you worked so hard to build begins to fade.

This is a common challenge—even for great leaders. Success is still too dependent on their presence. It’s because the system around them hasn’t been designed to operate without them.

What’s missing isn’t effort or skill — it’s System Leadership.

System Leadership – From Operator to Architect

System leadership is the shift from solving problems yourself to designing the conditions in which problems get solved—consistently, and without you.

It’s about shaping the environment where decisions get made, priorities stay clear, and execution keeps moving—even when you're not in the room.

A system is the sum of people, processes, culture, and tools that together determine how outcomes are produced.
Every team operates within a system—whether it was designed intentionally or not.

Traditional leaders operate the system: they drive progress, remove blockers, and solve problems themselves.

System leaders take a step back. They don't just run the system—they architect it.
They ask:

• Where do things typically break down?

• What rituals, tools, or constraints could help the system run more smoothly?

• How can clarity and accountability persist without me?

They don’t scale by doing more.
They scale by building systems where effectiveness is the default — so that progress continues even in their absence.

That’s the essence of systems leadership: making yourself obsolete—so the system can succeed on its own.

A Few Lessons from System Leadership

Here are five mindset shifts that show what systems leadership looks like in practice — whether you're leading a team, a product, an organization, or a cross-functional initiative.

Lesson 1: Your Product (or Team) Is a System

A product isn’t just a backlog or roadmap — it’s a living system.
It evolves as customers change, as teams grow, and as strategy shifts.

And living systems need care: feedback loops, clear structure, shared context, and cultural alignment.

That’s why planning alone isn’t enough. Great leaders are systems thinkers.
They don’t just ask, “What’s the next feature that brings value?” But rather:

“What needs to be true for this team to keep delivering value — even when I’m not in the room?”

That’s how you scale. Not just your product, but your impact.

Lesson 2. If You’re Always in the Loop, You Don’t Have a System

If your team can’t move forward without checking with you first, you’re not leading effectively — you’re causing a bottleneck.

System leaders design for autonomy.

They ensure priorities are clear, responsibilities are defined, and context is shared early and often.

When decisions are distributed, speed increases — and people grow.

Lesson 3. Good Systems Make Average Days Look Great

Long-term scale doesn’t come from bursts of effort — it comes from consistent, compounding execution.

System leaders build the conditions where momentum is sustainable:

• Strategic priorities are visible and aligned across teams

• Dependencies are clear and actively managed

• Feedback loops ensure learning happens in real time

In a system like this, progress isn’t exceptional — it’s the default.
Because the system is designed to keep moving, even when no one’s pushing.

Lesson 4: Don’t Scale Chaos — Scale What Works

As a company grows, messy workflows start to multiply.

If you scale before fixing inefficiencies, you don’t accelerate progress — you accelerate chaos.

System leaders pause to ask:

• What’s actually working here that we can make repeatable?

• What’s not working — and needs to be simplified or redesigned before we grow further?

They identify what works — and turn it into repeatable patterns.

Scaling doesn’t start with adding more people or process.
It starts with fixing what’s broken — and doubling down on what works.

Lesson 5: Culture Is the Invisible System Behind How Work Gets Done

Culture isn’t just how people feel — it’s how they behave under pressure, how they make decisions, and how they treat each other when no one’s watching.

It shows up in meeting dynamics, communication tone, how feedback is given, and how conflict is handled.

System leaders know these patterns don’t emerge by chance.
They can be shaped: by incentives or processes— the invisible structures that guide everyday behavior.

If your system tolerates blame, silence, or burnout — that is your culture.

It’s not what’s written in your values slide, but what happens when things get hard.

Recognizing the Signals is Where System Leadership Starts

If the lessons above reflect the mindset of a systems leader, the examples below show where that mindset begins: in the patterns already playing out around you.

Start observing those patterns with intent, and you’ll uncover opportunities to redesign the way your team works. Here are a few common signals to look for:

Prioritization Becomes a Weekly Argument

If every sprint planning or check-in turns into a debate about what matters most, you don’t need a better agenda — you need a clearer system.

Define how priorities are set and what trade-offs are acceptable. A shared model or link to OKRs will increase focus and clarity for everyone.

Every Release Feels Like Firefighting

Rushed launches, last-minute fixes, and unclear handovers are signals that your release process isn’t working well.

A system leader doesn’t treat these as isolated mistakes—they see them as signals that the process needs redesign. They introduce simple, repeatable structures—like checklists, pre-launch reviews, or shared release rituals—to make shipping smoother, safer, and more consistent.

Urgent Requests Constantly Disrupt the Plan

Unplanned work derails your focus not because it’s unexpected — but because it has nowhere to go.

System leaders don’t just say “no” more often—they redesign the system. They create dedicated tracks for triage, an escalation protocol, or an ops function to protect the core team.

Customer Feedback Doesn’t Guide Decisions

When customer insights are scattered across tools and anecdotes, they can’t shape product direction.

System leaders create a structured flow: tagged feedback, regular voice-of-customer reviews, or a central source of truth. The goal is streaming an input into the system so decisions are grounded in reality, not assumptions.

Too Much Time Goes to Manual, Repetitive Work

If your team is spending hours on repeatable tasks, your system is quietly leaking capacity.

You don’t need more people—you need a better system. System leaders identify friction points and look for opportunities to automate, streamline, or standardize the work.

Closing Thoughts

At scale, greatness isn’t shipping more features faster. It’s building a system where great features ship by default.

At scale, that's the real product:

• The system of decision-making,

• The system of customer understanding,

• The system of prioritization and execution.

Success isn’t being needed. Success is designing a system that creates clarity, flow, learning, and ownership — with or without you.

When that’s in place, you either move up to bigger, more complex systems or move on to build again.

Enjoyed this Article?

Subscribe to Lean Product Growth for regular updates on building and scaling a successful product organization. Insights, strategies, and actionable tips—delivered straight to your inbox.

Subscribe now

Try a simple experiment. Ask your team a simple question:

“Do you feel your unique strengths and skills are fully utilized in your current role?”

Then, ask yourself the same thing.

What you’ll uncover may surprise you: hidden potential, untapped strengths, or perhaps even some frustration from talents not being fully utilized.

Natural Talent vs. Forced Growth

From a young age, we naturally gravitate toward what we excel at.

A child instinctively chooses the toys or games they enjoy—the ones they’re good at. They immerse themselves, improve effortlessly, and get better every day. Their motivation doesn’t come from pressure; it comes from the joy of mastering something they love.

But what happens when a talented child is forced into an “all-round” framework?

The result is a child who feels frustrated, disengaged, and bored—while their true potential remains hidden.

The same often happens in the workplace.

Have you ever had a performance review where the conversation focused on "fixing" weaknesses, while your real potential wasn’t even acknowledged?

How did that feel? Draining, demotivating, confidence-crushing?

What Research Says About High-Performing Companies?

When it comes to building high-performing teams, research highlights the importance of leveraging individual strengths.

Here's a look at what the data tells us:

Top-Performing Companies Have “Spiky” Leaders

Strength-based leadership has been studied extensively by organizations like Gallup, McKinsey or Harvard Business School. Their research shows that focusing on individual strengths drives better performance.

For example, McKinsey’s leadership research analyzed effectiveness across various organizations. The highlights:

• Average companies tend to focus on creating “well-rounded” leaders by fixing their weaknesses.

• Top-performing companies have “spiky” leaders. These are leaders who are exceptionally good at a few competencies, but average, or even below average, at other competencies. Instead of trying to make leaders good at everything, the top performing companies help their leaders double down on their unique strengths.

The Theory of Flow - When Do We Achieve Peak Performance

Flow is a another concept introduced by psychologist Mihaly Csikszentmihalyi, describing a state of peak performance of an individual. This state happens when we’re doing something we’re naturally good at, and it feels effortless.

In Csikszentmihalyi’s words,

A flow is a state in which people are so involved in an activity that nothing else seems to matter. The experience is so enjoyable that people will continue to do it even at great cost, for the sheer sake of doing it.

When employees operate in their area of strength, they enter this “flow state,” where creativity, productivity, and engagement peak. The more a person can spend time in flow, the more fulfilled and effective they become.

When employees frequently work outside of their flow state, their performance drops, they start experiencing anxiety or boredom. They disengage and eventually leave.

Practical Tips For Leaders To Build High-Performing Teams

So, what can you do starting tomorrow to improve productivity and build a stronger, more engaged team?

1. Leverage Each Person’s Talents

Understand the unique strengths of every team member—not just what they’re good at, but what drives them. Get to the heart of their passions, skills, and career goals.

You can use assessment tools like Gallup StrengthsFinder or PI Assessment to gain deeper insights, but don’t underestimate the power of a direct conversation.

It’s your job to understand your team’s strengths so that you can strategically align the right skills with the right activities.

The next time you’re forming a team for a new project, you’ll be prepared to create a strong team setup, and the results will speak for themselves.

2. Fill Each Other’s Gaps

Build a team around you that excels in areas where you're not as strong.

For example, if you’re not naturally inclined to organize team events, don’t waste time forcing yourself to get good at it unless you truly want to improve in that area. Perhaps there’s someone on the team who would gladly take on that responsibility. Find that person and delegate.

Encourage your team members to do the same. Understand where they’re burning out by handling tasks that drain their energy, and have a conversation about how they can offload those tasks to others who are more naturally suited for them.

3. Acknowledge Strengths

When conducting performance evaluations, genuinely recognize the person’s strengths and the impact they’ve made. This boosts motivation and drives results.

If someone’s strengths differ from your own, it might be harder for you to see their value. Stay open-minded and take the time to shift your perspective. You should recognize the unique contributions they bring to the team.

This doesn’t mean underperformance should be accepted. If someone consistently has low performance, it’s absolutely necessary to provide actionable feedback.

4. Focus On Outcomes, Not Weaknesses

Everyone has weaknesses. But instead of focusing on fixing them, focus on the outcomes a team member needs to deliver. If a weakness is hindering their ability to meet those outcomes, discuss how they can navigate it. If they’ve found their own way to work around it while still delivering great results, appreciate it.

For example, if a team member struggles with presentations but successfully lands a major client through their relationship-building skills, celebrate their success. Then, explore how they can continue to leverage their strengths while finding alternative ways to approach presentations—whether that means delegating the task to someone more suited for it, adapting the presentation style to fit their natural strengths, or even removing formal presentations from the process altogether.

The goal is not to mold them into a one-size-fits-all framework, but to maximize their impact in a way that aligns with their natural strengths and behaviors.

5. Inspire Growth But Don’t Force It

People grow and evolve—interests shift, behaviors change, and perspectives broaden over time.

But change can't be forced. It happens when the time is right, often initiated by life experiences that shift how they see the world.

When your behaviors, beliefs, and vision align with their values, you’ll spark a natural drive to improve. They will then take ownership of their growth.

As James Clear puts it:

“To change your behavior, you first need to change your beliefs. Once you change your identity—who you believe you are—your habits will follow.”

Focus on assigning a goal to an employee that resonates with them and where their strengths can shine. As they work towards these goals, they’ll naturally develop complementary skills, including their weaknesses, without it feeling forced. Their strengths will lead the way, while weaknesses improve in the background.

6. Let Individuals Shape Their Own Development Path

Every role is unique, and every individual brings their own strengths and working style. Whether you’re leading a lead, product manager, engineer, or any other role, it’s crucial to recognize these differences.

The best leaders understand this and adapt their expectations accordingly. For instance, when evaluating a product manager, use a product competency matrix—but remain flexible in how you apply it.

They might excel in some areas more than others, and that’s perfectly fine. If they’re exceptional at strategic thinking, leverage that strength to maximize their impact.

Allow them to take ownership of their development and decide which competencies to further develop, while keeping business priorities in focus.

If their personal goals don’t align with the team’s immediate needs, be open and transparent about it. And if they eventually decide to move on, you’ll know you’ve explored all options for growth.

The Bottom Line

Building a high-performing team is about maximizing the potential of each individual in a way that aligns with business goals.

When you empower your team to focus on what they do best, you not only improve productivity but also create a team of engaged, fulfilled, and happy individuals.

🌟 Are you leveraging the full potential of each team member?
🤝 Are you focusing on creating a well-rounded team of exceptional individuals whose strengths complement each other?
📈 What’s one step you will take today to help your team work in their flow and maximize their strengths?

Curious about building and scaling a high-performing product organization? Subscribe and let’s learn!"

Subscribe now

Leaders are driven to hit ambitious goals, scale businesses, and deliver results. But in the pursuit to achieve these outcomes, one critical aspect often gets overlooked: the growth and development of the people driving the progress.

Without clarity in roles, responsibilities, and expectations, questions start to arise:

• How can I grow and advance here?

• Am I meeting expectations?

• What does success in this role look like?

When answers on these questions are vague, confusion sets in—leading to misalignment, inefficiencies in hiring, or disappointment during performance evaluations.

A competency matrix is a simple and practical solution. It helps align expectations, improve communication, and support both individual and team growth.

What Is a Competency Matrix

A competency matrix is a tool that maps the skills, knowledge, and behaviors required across roles within a job family. It provides a clear structure for hiring, performance evaluations, and career progression.

For example, a product management competency matrix might outline the progression from an Associate Product Manager to Chief Product Officer. It defines not only the skills needed at each level but also the broader competencies like strategy, leadership, and stakeholder management.

Why You Need a Competency Matrix

A competency matrix brings a few key benefits: Fair Evaluations, Spotting Skill Gaps and Improved Hiring.

Especially for product teams, where roles often differ between organizations, this framework can make a big difference. It aligns expectations and ensures everyone—from leaders to new hires—knows what success looks like.

How to Create a PM Competency Matrix

Here's how to create a competency matrix.

1. Identify Job Families and Seniority Levels

If you are building a competency matrix for your team, first start by defining the job families in your team. What job families do you identify? What are the progression levels for each of them?

Here are some examples of job families and their seniority levels:

• Product Management — Associate PM → PM → Senior PM → Director of product → CPO

• Product design — Junior Designer → Designer, Senior designer, Director of Design

• Engineering: Junior Engineer → Engineer → Senior Engineer → Engineering Manager → CTO

A competency matrix refers to a specific job family.

2. Define Core Competencies

Now let’s get into the heart of building a competency matrix: defining the core competencies for the product management (PM) family.

What makes a competency?
A competency is more than just a skill—it’s a combination of knowledge, skills, abilities, and behaviors required to perform a role effectively. While skills are often technical or task-specific, competencies focus on how those skills are applied in real business contexts.

For example:

• Skill: Using a roadmapping tool.

• Competency: Product strategy and roadmapping—combining tools, vision, and decision-making to deliver a meaningful product plan.

Approach This Thoughtfully.

Creating a list of competencies isn’t something to rush. It should reflect your organization’s values and expectations for success at every level.

• Collaborate with Stakeholders: Engage with team leads, peers, and leadership to align on what matters most. Competencies should reflect not just the role but also the culture and goals of the organization.

  • What does our organization value?

  • What do you expect from PMs at each level?

  • What baseline skills, behaviors, and mindsets are essential for success?

• Keep It Flexible: Allow room for flexibility and iteration as your team evolves. If you review it in a few weeks, you’ll likely spot points to improve.

Here’s an example of eight competencies for the product management job family, classified in four categories: Strategy, People, Process, and Pproduct:

Note that some competencies, like product strategy and roadmapping, are unique to the product management job family. Others, such as leadership and stakeholder management, are more universal and apply across multiple job families, including both product management and engineering.

3. Build the Competency Matrix

If you're confident in the chosen competencies, it's time to build the competency matrix. This involves mapping out the responsibilities and proficiency levels required for each competency across different seniority levels.

Here’s a glimpse of what it could look like:

For the full Product Management Competency Matrix, including a downloadable Excel version, scroll to the end of this post.

How to Use a Competency Matrix

Now that you’ve built your competency matrix, it’s time to turn it into a practical tool that drives growth, alignment, and better decision-making. Here’s how to put it to work effectively:

1. Personal Evaluations

Most organizations already have a process for performance evaluation and development. Integrate the competency matrix in the existing process to make it more actionable.

• Map Individual Progress: Assess where each team member stands within the matrix.

  • Are there gaps holding them back from achieving their goals?

  • Do these areas of improvement align with their aspirations?

• Bring It to 1:1s: Use the matrix as a foundation for open discussions. Instead of vague feedback, you’ll have a structured framework to:

  • Highlight strengths.

  • Address areas for improvement.

  • Agree on next steps for growth.

• Buy-In Is Key: Without the team’s agreement and engagement, the matrix risks becoming a checkbox exercise. Focus on collaboration, not just evaluation. When the process feels fair and actionable, it becomes a tool for empowerment rather than judgment.

2. Identifying Team Gaps

The matrix isn’t just for individuals—it’s a powerful tool to identify gaps at the team level.

Use these insights to address gaps. Consider targeted training, mentoring, or hiring for new roles.

• Map the Team: Assess the current skills and competencies of your team against the matrix:

  • Are there key skills missing in the team in critical areas?

  • Are there gaps that could limit your ability to scale?

• Define Actions: Use these insights to address gaps.

  • Invest in targeted training or mentorship programs.

  • Use the matrix to identify roles that could fill these gaps.

3. Improve Your Hiring Process

Try using your competency matrix in the hiring process. It will bring clarity and structure at every stage.

• Before the Interview: Use the matrix to define exactly what you’re looking for in a candidate. This keeps the process focused on what truly matters for the role.

• During the Interview: Use the matrix as a live guide to evaluate candidates:

  • Map their skills, behaviors, and experience against the required competencies.

  • Ask questions to assess how well they meet key expectations.

  • When candidates ask, “How can I grow in this role?” use the matrix to outline a clear growth path.

• After the Interview: Use the matrix to align stakeholders on the candidate’s suitability. A shared framework reduces bias and ensures consistency.

How a Competency Matrix Helped Us Hire

When I introduced a new role to address a critical gap on my team, it quickly turned out to be more challenging than expected.

The role was highly collaborative, requiring coordination across multiple teams within the organization. Naturally, stakeholders from various departments were eager to provide their input in the hiring process, which added layers of complexity.

Finding the right candidate was difficult, but a deeper issue surfaced: a lack of clarity and alignment.

• Each stakeholder had a different interpretation of the role’s responsibilities.

• Finding a candidate who met everyone’s expectations was nearly impossible.

• The misalignment was slowing the process down for everyone involved.

We introduced a competency matrix. It pushed us to revisit and refine the role’s requirements, clarify the key competencies, and formalize the position’s growth potential. The matrix became the foundation for a more aligned, efficient, and effective hiring process.

Here’s what changed:

• Improved clarity: Everyone gained a clear understanding of the role’s expectations, purpose, and growth path.

• Structured interviews: Discussions with candidates became more focused, consistent, and aligned with key competencies.

• Aligned evaluations: Stakeholders assessed candidates using the same criteria, leading to better and faster decision-making.

Practical tips: Make your Competency Matrix a Living Tool

When used the right way, a competency matrix can be a powerful asset. But if it’s treated as a “check-the-box” exercise, its value quickly fades.

Keep it relevant, actionable, and impactful with these practical tips:

Use It as a Guide, Not a Box

The matrix is a tool—not a rigid rulebook. Respect individual talents and unique profiles.

Exceptional candidates and team members often don’t check all boxes but they have exceptional unique skills that can bring immense value.

Use the matrix to guide decisions, not to limit them.

Keep It Fresh: Regular Updates

Teams evolve, companies grow, and priorities shift. To stay relevant, revisit the matrix periodically. Every iteration is an opportunity to improve.

When to review it?

• When new roles are introduced.

• When teams expand.

• When the business or strategy changes.

Involve Teams for Alignment

Engage relevant stakeholders to ensure alignment, especially for competencies that overlap across job families or teams (e.g., leadership or stakeholder management). While expectations for roles differ, basic ground rules should apply across the organization.

For example:

Leading a team of engineers should compare reasonably to leading a team of designers or analysts. While the specifics may differ, the core expectations should align.

Stay Aware of Industry Trends

Every company is unique, but benchmarking against industry practices keeps your matrix grounded.

• Is your “Director of Product” role in line with similar companies at your scale?

• Are you using language that resonates with both internal and external audiences?

Follow the trends to make the role understandable and appealing for both internal and external hires.

Share the Matrix

Make the matrix accessible to your team so they know what’s expected from them and how they can grow.

Sharing it also opens the door to valuable feedback, allowing you to refine and ensure it remains relevant.

Use Tools That Work For You

The matrix is quite simple, so there’s no need to use any advanced tooling.

Excel, Google Sheets, Miro, or Confluence, anything works perfectly well.

Choose what’s already accepted and familiar in your organization. Most important is to ensure adoption of the tool.

To Wrap Up

A structured approach to people development demonstrates maturity and professionalism.

If you’ve relied on gut feeling only when hiring or promoting, introducing a competency matrix can make a difference. It brings clarity for you, clarity for your team, and clarity for new hires.

That said, remember: the matrix is a guide, not a rulebook.

Exceptional people don’t fit into predefined boxes — their strengths and weaknesses are unique. This is what sets them apart.

Keep room for flexibility and let your talent shine.

Originally published at https://blog.logrocket.com/ on December 27, 2024.

📥 Download the Full Product Management Competency Matrix in Excel Format
This detailed matrix includes all the core competencies, progression levels, responsibilities and actionable examples (Available for paid subscribers).

Read more

For most businesses, large or small, software delivery is accompanied by delays, late nights, and the inevitable frustrations that come with them.

In the article Why does it feel like product features take forever to ship, we explored the key reasons behind software product delays. While the topic is far too complex to capture in a single list, one key takeaway remains:

Misaligned priorities, communication breakdowns, technical debt, and other systemic issues ripple across the company, affecting both engineering teams and stakeholders.

Until these deeper issues are addressed, delays will remain a recurring challenge.

How to Keep Software Delivery on Track

Delays in software delivery are not an engineering problem only — they’re a shared responsibility.

From leadership to business stakeholders, product managers, and engineering teams, every part of the organization has a role to play in addressing this challenge.

Leadership’s Role: Culture as the Foundation

Change starts with culture. Culture sets the tone for how teams behave, communicate, and how ambitious goals they set.

A strong, cohesive, ambitious, and blameless culture sets the foundation of high productivity and timely delivery.

Here are key areas where leadership can make a difference:

1. Breaking Down Silos

How well do your sales, product, and engineering teams understand each other?

A sales rep is unlikely to grasp the intricacies of a technical challenge. But can they empathize when an engineer says, “We’re at high risk of a delay”?

Similarly, are engineers confident enough to raise red flags without fear? And can they empathize with the sales team’s urgency and pressure to deliver the next feature release?

Transparency and psychological safety have shown to be the number one factor for high productivity. Without it, teams retreat into silos, withhold information or avoid critical conversations. When that happens, delays become inevitable.

If your teams operate in silos, it’s time to break the walls.

• Organize cross-functional workshops where teams learn about each other’s challenges.

• Share dashboards and data across teams to increase transparency and foster alignment.

• Publicly encourage open dialogue and reward transparency.

2. Teams Accountable to Outcomes

If your business teams define what to built, while success for engineering teams is measured by timely execution only, it’s a red flag.

When decision-making rests entirely with stakeholders, technical solutions are rarely optimal, inefficiencies and delays are inevitable.

Shift the focus from output (features, timelines) to outcomes (business impact, user behavior).

Instead of requesting: “Deliver Feature X by next month?”

ask: “How can we achieve the desired user behavior or business impact?”

Empower product and engineering teams to deliver on clear outcomes.

This makes them better positioned to find innovative, efficient solutions that achieve the same goals with optimal technical resources.

3. Focus on Big, Clear Goals

If you want to drive meaningful progress, set bold and clear goals.

Leaders should define clear goals, inspire their teams, and align everyone around a shared vision.

The guiding principle here is: less is more. When there are too many initiatives, all labeled as equally important, people often fail to feel a sense of urgency for any of them. But when one key goal is emphasized, it becomes a unifying focus, orienting teams toward solving the same challenge.

When coffee chats and informal conversations revolve around the same goal, you know you’ve achieved focus. At that point, teams aren’t just working together—they’re working toward a shared vision.

4. Data-Informed Culture

Data increases transparency. It highlights risks and potential delays by making progress measurable and visible.

When discussions between IT and business teams are backed by data, personal biases are removed, shifting the focus from opinions to solutions.

Research shows that Data-mature organizations achieve 2.5 times better business outcomes than their less mature counterparts. This underscores the impact of embracing data-driven practices.

Integrating data starts from creating a data-informed culture. Leaders must set a high standard by emphasizing the use of data to track progress and measure outcomes. They should create an environment where teams are empowered to leverage data—not just for tracking progress but also for steering product roadmaps and making informed decisions.

5. A Culture of Quality

Engineering productivity and quality go hand in hand. Scalable architecture, automated processes or adopting new technologies are key to accelerating product development.

But quality doesn’t come for free.

Engineers need the mental space and time to innovate and improve. A constant pressure to deliver quickly erodes quality, leading to higher costs, slower progress, and unexpected delays down the line.

While maintaining quality is a core responsibility of engineering teams, leadership plays a crucial role in supporting this effort. This involves fostering quality awareness across teams, pushing for modern tools and technologies, and recognizing when strategic investments—like a major system migration—are necessary.

When leadership backs quality, teams are empowered to build better, faster, and more sustainable solutions.

Sales Role: Align Customer Needs With Product Strategy

Sales teams are the frontline of customer interaction. They bring new demand and ideas for product features.

Their role isn’t just about closing deals—it’s about aligning customer needs with the product strategy and maximizing satisfaction with what the product can realistically deliver.

Here are key principles to follow:

1. Communicate Value, Not Features

Customers request specific features, but the real value is understanding Why they need them. Without digging deeper, the true problem the feature is meant to solve may remain hidden.

Ask questions:

• What problem are the users trying to solve?

• How will this feature change their behavior or workflow?

• Will it help them make better decisions?

Focus the communication (both with the customer and the product teams) on value. Avoid getting into a discussion about a rigid feature description or specific implementation. Let the product team decide how to deliver the value in a most effective way.

2. Stay Close to the Product Roadmap

Customers often ask for specific features with great enthusiasm. Resist the urge to immediately say "Yes" unless it aligns with the next priority on your product roadmap.

Being overly flexible with customer requests doesn’t necessarily make you customer-centric—it can signal that your product’s sustainability and scalability are at risk.

Here’s an interesting phenomenon: what seems urgent today often loses its relevance within a day or two. Instead of rushing to commit, take a step back and consider:

• Would this feature truly address the customer’s current top priorities?

• Is this request a strategic step for your product? Does it align with your roadmap and provide value for other customers?

If the feature’s value is questionable or misaligned with your strategy, redirect the conversation. Highlight for example an upcoming feature that offers even greater value and supports your customer’s goals. This approach not only keeps customers excited about what’s to come but also makes life easier for your product teams by avoiding unnecessary detours.

Check out Ben Yoskovitz's guide for practical tips on navigating sales conversations without derailing the product roadmap, How Do You Decide to Build a Feature to Close a Deal?

3. Avoid Time Commitments

New features are rarely as simple as they seem.

Delivery involves more than writing code—it includes testing, deployment, maintenance, and handling unforeseen challenges along the way. Data indicates that the effort spent on maintaining a feature over its lifetime is about five times greater than the effort required to build it.

Avoid promising timelines without consulting the engineering team. Try to keep promises as much as possible realistic to maintain credibility with both customers and internal teams.

Product Manager’s Role: Clarity, Prioritization and Focus

Product Managers (PMs) sit at the intersection of business, engineering, and customer needs. Their role is to prioritise smartly and ensure focused execution.

Here’s how PMs can contribute.

1. Set Clear Priorities and Focus

Is your roadmap cluttered with various initiatives and you don’t feel it’s connected to the reality?

If so, step back. Cut the nice-to haves and all distracting items on your roadmap and highlight the few initiatives that would generate highest value.

Clean and simple roadmap is what will keep teams focused and motivated.

2. Clear and Transparent Communication

Miscommunication leads to rework, missed expectations, and unrealistic timelines.

For product teams: Make sure engineers have a clear understanding of prioritized goals and expectations. Keep product requirements concise, well-documented, and specific. Shorten feedback loops to avoid unnecessary back-and-forth.

Practical tip: Never leave a discussion with ambiguity. If there’s even a hint of misalignment or confusion, address it immediately—ambiguity almost always leads to mistakes and delays.

For stakeholders: Be upfront about what’s feasible, what’s at risk, and the trade-offs involved. Transparent communication builds trust and reduces last-minute surprises.

3. Ambitious Yet Realistic Planning

PMs should champion challenging but realistic planning that considers technical complexities and potential risks.

Work closely with engineering to estimate timelines based on actual effort and anticipated challenges. Agree on must-have goals but also stretched goals.

Keep it balanced. Overly conservative plans can kill innovation, while overly ambitious plans can demoralize teams. Strive for ambitious yet realistic goals to keeps the team challenged without overwhelming them.

Engineering Role: Quality and Waste Reduction

Engineering teams are at the heart of product delivery. They might not control every factor influencing delays, but they have the power to make significant improvements.

Here are a few key principles for engineering teams to excel:

1. Focus on Quality

A low-quality product creates a long-term technical debt that hampers your ability to deliver effectively.

While it may be tempting to cut corners under tight deadlines, shortcuts should be the exception, not the norm. Left unchecked, technical debt can quickly escalate, slowing down progress and increasing costs.

The same applies to the software development process itself. Software development is often accompanied with waste, from task switching and inter-team dependencies to manual processes and vague requirements.

Building waste reduction into your sprint routine by dedicating 10–15% of each sprint on fixes inefficiencies can make a big difference. This could include automating repetitive tasks, clarifying requirements upfront, or simplifying workflows.

Keep high product standards. This boosts productivity but also overall team satisfaction.

2. Communicate Risks Early and Back Them With Data

Engineers are often the first to identify risks that could impact timelines or create bottlenecks.

Don’t wait until it’s too late to raise concerns. Share high-risk areas as early as possible. If you feel your voice isn’t being heard, work on the clarity of your message.

Here’s how to make your message resonate:

• Use simple language to explain risks. Avoid focusing on the technical details; instead, emphasize the business impact.

  For example: "If we proceed with this architectural decision, it could increase maintenance costs and delay future releases by six months."

• Support your concerns with data to add credibility.

  For example, highlight how a suboptimal architectural choice today could double workload or create delays down the line.

Not every concern will immediately become a top priority, but creating awareness is key. When the decision-makers understand the real implications of a flagged issue, they can balance it against the other business priorities. What might seem like a lower concern today could be the next quarter’s most urgent initiative.

3. Master Planning

Accurate planning is a tough challenges in engineering, but it’s critical.

Whether you use story points, velocity metrics, or other estimation tools, the key is to continuously refine and improve your planning process. Start simple—use basic time estimates—and focus on improving accuracy with each iteration.

Most importantly, plan for the unexpected. Build in buffers for unforeseen hiccups and avoid relying solely on best-case scenarios. The goal is to strike a balance: set realistic, achievable targets while keeping them challenging enough to inspire teams to push their limits.

Wrap Up

While systemic challenges require collective effort, you don’t have to wait for the perfect scenario to start making an impact.

Begin with what you can control.

If you’re an engineer, raise risks early, improve the clarity of your communication, and stay committed to quality.

If you’re a product manager, review your roadmap critically and speak up if it feels unachievable.

Small actions can inspire others and create momentum. When your manager recognizes the value of your small initiative, it can ripple upward, encouraging leadership to set bigger goals and drive meaningful change.

By applying these strategies, you’re not just reducing delays—you’re laying the foundation for trust, innovation, and excellence across your organization.

What’s one small step you can take today?

Enjoyed this read? Subscribe to Lean Product Growth for regular updates on building and scaling a successful product organization.

Subscribe now

Access other relevant content on Lean Product Growth

In favorable circumstances, leaders often steer their teams with optimism and confidence, naturally leading to strong results.

But what happens when the conditions change—when uncertainty arises and challenging times are on the horizon? Shifting priorities, limited resources, or declining team morale can leave leaders feeling stuck, overwhelmed, or even burned out.

How do you gather the strength to push forward and uplift your team in these situations?

In this article, we’ll explore key strategies and practices for leading effectively through uncertainty and difficulty.

If you prefer listening, you can follow the key insights from this article in an audio format— AI generated.

6 Strategies for Resilient Leadership During Tough Times

1. Embrace Your Role and Acknowledge the Reality

Why It Matters

In times of uncertainty, your role as a leader becomes more crucial than ever.

As the saying goes, “People don’t leave companies, they leave managers.” This holds even more weight during difficult times.

When a team trusts their manager and feels supported, they are far more likely to remain engaged and committed, even in the face of adversity.

Your Role as a Leader

Accept the reality of the circumstances. The challenges ahead are fixed, but your response to them is not. This distinction makes all the difference.

When you face a tough situation, the outcome may not be perfect—and that’s okay. What matters is your ability to maximize the outcome within the constraints of the challenging reality.

Shifting your mindset this way is essential for staying calm and grounded. It allows you to focus on what you can control without stressing over what you can’t change.

When you lead from this place, you project calm and confidence—both of which are contagious. Your steadiness provides the team with stability and direction during uncertain times.

2. Practice Pragmatic Optimism

Why It Matters

In tough times, your team's motivation is strongly influenced by your outlook. If you show doubt in their ability to overcome challenges, they will likely lose confidence and disengage. Optimism keeps them focused and committed.

But this optimism must be pragmatic. It’s not about pretending everything’s fine. Instead, it’s about acknowledging the difficulties while maintaining a belief in the team’s ability to find a way forward. This balanced mindset helps your team stay resilient and hopeful, even when the road is challenging.

Your Role as a Leader

Find the positivity in the situation. By staying focused and positive, you lead by example.

Be transparent about the challenges without sugarcoating them. Show confidence in your team’s ability to succeed. This belief can be the driving force that keeps them motivated and moving forward.

A great example of pragmatic optimism comes from a film production manager who was leading a high-pressure project. Her team was exhausted, morale was low, deadlines were looming. While others took days off to recuperate, she remained present, maintaining a positive yet realistic outlook. When asked, “How are you still going strong?” she simply replied, “Of course I’m tired, but if I give up, we all lose. The team needs me to keep pushing.” Her determination and optimism kept the team going, even when the situation was tough.

3. Communicate Clearly and Transparently

Why It Matters

Transparent communication is the foundation of effective leadership, but during challenging times, it becomes even more critical. Maintaining trust and keeping your team aligned is a must.

When a team senses that leadership is withholding information, gossip spreads, fear about the future rises, morale drops, and trust erodes.

Some leaders try to sugarcoat the situation to give a false sense of security. While this may offer a temporary boost, when the truth inevitably surfaces, it can severely erode trust and morale.

Your Role as a Leader

Be clear, direct, and honest with your team. Share the facts you know and that are safe to disclose. Don’t speculate or vaguely discuss what you don’t know yet or what can’t be shared at the moment.

Think of how doctors deliver difficult news: calm, direct, and focused. They don’t offer false hope, nor do they create unnecessary worry. They share information when it’s necessary and appropriate, allowing time for patients to process the news and ask questions. Approach your communication in the same way.

Gather your team, provide updates on what has been accomplished, and explain what lies ahead. Give them space to ask questions, and encourage them to come to you individually if there are concerns.

It’s okay to admit that not all risks can be eliminated or that you can’t guarantee specific outcomes. What’s most important is showing your trust in their ability to face the challenges together.

4. Establish Clear Priorities

Why It Matters

In uncertain times, prioritization can be the difference between your team succeeding or failing. You can’t afford to let their efforts become scattered or allow resources to be wasted. Every team member needs to focus on what truly matters, applying the 80/20 rule—ensuring that 80% of the results come from 20% of the most important tasks.

Your Role as a Leader

As a leader, prioritization is one of your key responsibilities. It’s your job to maintain a clear overview and ensure that the right priorities are being executed daily.

You can’t allow details overwhelm you. Stay in control by keeping the big picture in mind and remaining vigilant. Identify areas where focus is unclear or resources are being misallocated, and adjust as needed.

Here’s a rule I always follow: when something seems ambiguous or unclear, we tend to avoid it. But these are often the areas where the biggest issues arise. Take the time to understand these gray areas—chances are, the greatest risks or challenges lie there.

5. Be Open to Change

Why It Matters

In times of uncertainty, sticking to the status quo rarely leads to favorable outcomes. After all, if things were stable and predictable, it wouldn’t be called a tough time.

This is why you and your team need to be open to change. Being prepared for the possibility that tomorrow’s team structure, workflows, priorities, or budget might not look the same as today is essential.

Your Role as a Leader

Your mindset matters here—being comfortable with uncertainty is key.

Some changes might be driven by other stakeholders—the executive team, shareholders, or external market conditions. Stay open to these. Understand the reasons behind the changes, and acceptance becomes easier.

At the same time, you will play a pivotal role in driving change. Think creatively and embrace out-of-the-box strategies. For example, consider scenario planning—preparing for best-case, worst-case, and middle-ground outcomes to keep your team ready for any shift. When planning your roadmap, build flexibility into next to team’s focus. It’s not just about staying on track; it’s about being adaptable enough to pivot when necessary.

And, of course, as a leader, you need to prepare your team for the unknown by being transparent and keeping morale high. A rigid, closed mindset is no longer an option. Show them that flexibility and adaptability are powerful strengths necessary to navigate any challenge.

6. Don’t Be Afraid to Make Tough Decisions

Why It Matters

In difficult situations, none of the available options may seem ideal. Yet, the only way to move forward is to make tough decisions. These could involve reorganizing teams, reducing staff or hours, or discontinuing a program with significant time and investment behind it.

You may not feel entirely satisfied with the decision, and you may not be 100% sure it’s the best option. But delaying action during tough times will only make the problem worse.

Your Role as a Leader

Consult with relevant stakeholders, your team, and align with the company's goals. Gather data, assess the risks of different scenarios, and make an informed decision. Ultimately, the responsibility to choose between option A or B lies with you.

“If you make decisions that everybody likes all the time, then those are the decisions they would make without you. So you’re not actually adding value.” - Ben Horowitz

Accept that your decision may not be popular, and there may be people who disagree with it. That’s part of leadership.

Once the decision is made, clearly explain the reasons behind it. Transparency helps people understand and accept the situation without filling the gaps with negative assumptions.

If certain individuals are upset, have these difficult conversations. Listen, show empathy, and acknowledge their feelings. You may not be able to change the outcome, but showing understanding can go a long way.

Final Thoughts

Are you currently navigating a tough situation, or have you faced one recently? Did your reaction set a tone for your team? Could you have approached it differently Consider which of these principles and tactics you can apply to make the process smoother and more manageable.

While these times may be challenging, remember these are exactly the situations you need to sharpen your leadership skills. You’ll emerge stronger, more confident, and with a deeper understanding of what truly makes for effective leadership. Embrace the challenge as an opportunity to grow and lead with greater impact.

Enjoyed this read? Subscribe to Lean Product Growth for regular updates on building and scaling a successful product organization.

Access more product growth content on Lean Product Growth

How to Scale a Product Company: Leaders’ Guide to Growth

How the Over-Promise and Under-Deliver Strategy Pushes Team Performance

How Authentic Leadership Can Empower Humanity

I recently came across a statement from Shreyas Doshi who suggested "Over-Promise and Under-Deliver" as a strategy for teams.

At first, it sounded strange, contrary to the conventional wisdom of "Under-Promise and Over-Deliver." The suggested approach felt risky—why would anyone advocate for setting expectations high, only to fall short?

But as I looked through it more carefully it started to make sense.

Shreyas is making an excellent point. Over-Promise and Under-Deliver can push individuals and teams beyond their usual limits, and foster greater success and innovation within organizations.

It opens up possibilities for growth that might otherwise be missed.

The Traditional Approach: Under-Promise and Over-Deliver

We’ve all heard the traditional advice: Under-Promise and Over-Deliver. This strategy is deeply ingrained in professional culture for a reason.

The idea is to commit to delivering something you’re confident you can achieve. By doing so, you minimize risk, maintain your reliability, and protect your reputation.

This approach undoubtedly remains the best course of action in many situations. For instance:

• When dealing with clients, it’s crucial to meet or exceed their expectations. Delivering on your promises not only boosts customer satisfaction but also builds trust and fosters stronger relationships over time.

• Internally, this strategy is equally important when a major milestone is on the horizon and multiple teams are interdependent. In such cases, everyone needs to fulfil their promises to ensure the overall project stays on track. A delay of one team can have a cascading effect, leading to missed deadlines, disrupted plans, and unnecessary stress for everyone involved.

• When an organization hires you to solve a major problem, it’s wise to promise what you’re confident you can deliver. It’s important to clearly communicate what is certain to be achieved and what is possible but not guaranteed. This transparency helps set realistic expectations and ensures that both parties are aligned from the start.

The Power of Over-Promise and Under-Deliver

The traditional approach however, has its downsides when applied within an organization.

By consistently playing it safe, teams may fall into a conservative mindset, sticking to what they know rather than reaching for more ambitious goals. This can lead to missed opportunities for innovation and growth, as the focus shifts to maintaining the status quo rather than pushing boundaries.

This is where the Over-Promise and Under-Deliver strategy comes into play.

The Over-Promise and Under-Deliver strategy encourages teams to set ambitious goals and push themselves beyond their comfort zones. It forces them to think creatively and find new ways to reach higher objectives.

Teams transition from the Comfort Zone to the Stretch Zone, where the magic of growth and innovation happens.

The Stretch Zone is the sweet spot—where optimal growth and innovation occur. It’s the desirable target for any ambitious team.

For example, when a team defines their OKRs (Objectives and Key Results), the goal they should always aim to set ambitious goal without being discouraged if 100% success isn’t achieved. Achieving 70-80% of an ambitious goal is a win, as it indicates significant progress.

The key here is progress, not perfection. Each iteration brings the team closer to excellence.

Culture as a Key Prerequisite

The success of the Over-Promise and Under-Deliver strategy is closely tied to a company’s culture and can flourish only in environments that actively support it.

Several key factors should be considered:

Performance evaluations: Performance evaluations should go beyond simply measuring the achievement of the goals set. They should also recognize the effort, creativity, and learning that come from pursuing ambitious objectives. This approach encourages employees to take calculated risks and think beyond conventional limits.

Encouraging higher objectives: When teams consistently deliver on their promises, motivate them to set even higher objectives. Encourage the adoption of the 80% rule—where meeting 80% of a goal is considered a success, and anything beyond that is seen as exceptional. This mindset pushes teams to stretch their capabilities.

Valuing progress over perfection: Value and praise teams for making significant progress, even if they haven’t fully met their commitments. Leadership should encourage a culture where progress is celebrated, rather than punishing shortfalls. Only then can teams feel safe to challenge themselves and drive meaningful change, rather than worrying about management's reaction to unmet goals.

Balancing Ambition with Realism

Ambition is valuable, but unrealistic ambition can have negative consequences.

The Over-Promise and Under-Deliver strategy should be applied in the right situations and with careful consideration.

Beware of the Danger Zone

While the Stretch Zone is where the most growth occurs, it’s crucial to maintain a balance and avoid crossing into the Danger Zone.

Setting goals that are too ambitious and far from reality can lead to stress, burnout, failure, misalignment, and lost trust.

To prevent this, it’s important to keep teams challenged but not overwhelmed. Staying in the Stretch Zone without crossing into the Danger Zone requires careful evaluation and constant reassessment of goals.

Transparent Communication

Another critical aspect is clear communication and expectation management. It’s great for a team to set ambitious goals, but it’s equally important to be transparent with stakeholders about the nature of these goals.

When teams communicate that these are stretch targets, not guarantees, the focus remains on the ambitious goal without leading to miscommunication, eroded trust, or misaligned expectations.

Final Thoughts

The Over-Promise and Under-Deliver strategy has significant potential to drive innovation and motivate teams to exceed their own expectations.

But this approach must be applied carefully. It is not appropriate for every situation, especially when dealing with clients where commitments need to be firm. This strategy is best suited for internal use within a safe environment that supports transparency and encourages calculated risk-taking.

When employed in the right context and executed thoughtfully, this strategy can inspire teams to push boundaries and achieve remarkable results.

What are your thoughts on this strategy? Share your experiences or questions in the comments below!

You enjoyed this read? Subscribe to Lean Product Growth for regular updates on building and scaling a successful product organization.

Subscribe now

So, what factors can boost team productivity and motivation?

In this article, I will share a story to reflect on how to boost team productivity. I’ll conclude with the key principles you can use to build an effective and scalable team.

Situation: Growth with Declining Productivity

A few years ago, I was brought in to help a software development team working on an innovative product.

This team, which had been working together for several years, had achieved remarkable results and built a well-functioning product that was well-received by end users.

When I joined, the team was a harmonious unit — members supported each other and shared good collaborative efforts.

But as the team grew to a dozen people and the number of customers rose, they faced a significant productivity decline. Delving deeper into their daily work revealed substantial challenges: diverse priorities and a productivity trap.

Diverse priorities

The backlog was stuffed with diverse activities — from server management tasks to customer-specific software configurations, customer requests, product refactoring to increase scalability, or long-term initiatives aimed at improving product usability.

And with every new sprint project, the list of tasks was growing overwhelmingly long.

It was not feasible to select the top three high-priority items, as everything on the list appeared to be of high importance.

Plus, new items, often urgent, constantly emerged from customers or other departments. These tasks were critical to address early — delaying them could result in unhappy customers, blocked workflows, or risks to important milestones.

Productivity Trap of Early Growth

Growth was on the horizon.

New customers were coming in, bringing new needs for the product. And we needed to expand the team.

But, adding more people to the team without ensuring an efficient workflow didn’t seem wise.

The current team setup had worked well when the team was smaller, but now, it was clear that changes were necessary. Moreover, the current team structure was not scalable. Hiring more people might increase the headcount, but coupled with the already existing inefficiencies, it would mean a waste of resources.

We identified these productivity problems:

• No clear team purpose — No single inspiring mission unified all team members. Asking them about their goal gave me so many different answers

• Insufficient accountability — With so many priorities circling in the team, some areas were left immature, lacking clear ownership and responsibility

• Suboptimal scalable structure — The team structure was not prepared for scaling. And without a clear structure, adding more people was ineffective and wasteful.

How did we Boost Productivity

So, although everyone was eager to drive improvements, it was essential to first understand the existing dynamics. Why are things done the way they are? What are the team members’ perspectives? How do they feel about change?

Disruptive change could be a double-edged sword.

When executed correctly, it can lead to rapid improvements and inspire the team. But, if introduced at the wrong time or in the wrong manner, it can disrupt existing workflows, demotivate team members, and cause chaos.

So, we didn’t make the change overnight. It happened gradually. People needed time to gain the right skills, adapt to changes, and, most importantly, understand the strategic direction of the change. This gradual approach ensured everyone was on board and ready for the next step.

1. Understanding the team's activities

We began by categorizing the backlog tasks into distinct categories. Each item needed a clear purpose and had to fit into a specific bucket, whether technical debt, customer support, product enhancement, or another area.

This initial step gave everyone a clearer picture of the team’s activities. The initial list of categories needed some refinement, but the pile turned neater with each new week.

Planning sprint tasks became much more straightforward, and identifying bottlenecks in the team became easier. We could now see where most of the work was coming from and where we needed more capacity.

2. Identifying domains

Within a few weeks, it was clear that we could identify certain domains of work within the team.

Customer support domain

It became evident how much time was actually spent addressing customer requests. These activities were challenging to plan in advance and often disrupted other development work, slowing the team in building new features. Moreover, this supporting work required different skills than those typically possessed by software developers.

So, we dedicated a few members to this subdomain and hired people exclusively for service management. In a few months, this became a separate team with clear goals — service delivery excellence, customer satisfaction, and continuous improvement.

Product domains

Initially, everyone viewed the product as a single, unified entity — a sophisticated piece of software that analyzed data from customer software systems and provided various insights for the end user.

However, as we delved deeper into its functionality, it became clear that two distinct parts of the product had emerged over time:

• User-facing product — This part of the product was designed to be intuitive and user-friendly, providing a seamless experience for our customers and had its own challenges like users demanding more features, greater ease of use, and faster performance

• Analytics product — The user-facing component relied heavily on a complex analytics component in the background. This part needed understanding different software languages, tracking language trends, and analyzing performance metrics. The challenges here were different: optimizing performance, building for reusability, and understanding software patterns

As these two parts became more distinct, we naturally began to form subteams, dedicating roles focused specifically on one or the other part of the product. This allowed for more specialized attention and expertise, improving both the user experience and the effectiveness of the analytics.

3. Decreasing dependencies between teams

Making the subteams effective and fully independent didn’t happen immediately. Knowledge was shared across teams. But as the split became more distinct, it became apparent that the teams needed to be more independent.

So, people started working more on documenting the knowledge, establishing clear, standardized processes, and thinking about automating specific process steps.

The user-facing and analytics products were already well split into precise modular components, which helped teams be more independent in their development and maintenance.

To make the split fully operational, we started establishing more apparent interface dependencies (APIs) between them so we had more agile teams, and each team could be independent in its release cycles.

4. Building small but effective teams with a clear mission

By creating smaller and well-aligned teams, their mission became much clearer.

The customer support team started to focus more on customer satisfaction. They could see the effect of delaying requests more clearly and began implementing new tools and processes to increase efficiency and customer satisfaction. By tracking data from customer requests, they discovered bottlenecks in the entire process.

The analytics team became more focused on its mission. It had to empower the product with advanced data-driven insights and robust software analysis, ensuring optimal performance. It also needed to follow programming language trends and optimize analysis algorithms. Relieved from the burden of handling various customer requests, its work became much more meaningful.

The user-facing team had a different goal — providing an exceptional user experience, ensuring ease of use, and continuously adapting to meet the evolving needs of users. They could now incorporate new ideas and ways of working to achieve better results in their goal.

Lessons Learned

This evolution happened over a few months, more like a year. It was a continuous improvement process. As the company grew, new needs emerged, necessitating further changes.

However, adopting an improvement mindset makes new changes easier to implement.

So here are the key takeaways from this story.

Establish a clear mission

A team with a clear mission is happier, more motivated, and more productive. A clear mission helps team members understand their purpose and remain focused on their goals. They can quickly implement meaningful OKRs connected to the company’s strategic goals. Eventually, they are more challenged to change the status quo.

Small teams are more effective

Small, focused teams are more agile and effective. They can make decisions faster, communicate more efficiently, and clearly focus on their specific goals. This structure allows for greater accountability, stronger synergy, and better collaboration within the team. And it allows for growth.

Less dependencies means higher productivity

If teams are separate, they should be able to work independently and autonomously. Fewer dependencies allow them to manage workflows, set timelines, and release features without being bottlenecked by other teams.

Last words

Revolutionary changes can offer significant advantages but also come with substantial risks.

Instead, implementing changes gradually allows time for adaptation and skill development. It carries people along the change journey, minimizes resistance, and helps smooth transitions.

Following these basic principles inspires, motivates, and encourages a team to make a difference, which is when productivity flourishes.

Originally published at https://blog.logrocket.com/ on 17 Jul 2024.

If you enjoyed this article, don't miss out on more content! Subscribe to Lean Product Growth for more valuable resources on how to build and lead scalable product organizations, delivered directly to your inbox.

Subscribe now

How can we encourage this essential problem-solving skill in the youngest minds among us?

The ability to tackle complex problems isn't just a professional benefit—it's a life skill. And this skill doesn't start in boardrooms or coding schools but in the playrooms of our childhoods.

This post dives into two very simple games that promise not just fun but a solid foundation in problem-solving for the youngest kids. These games are lessons in thinking differently, creatively, and strategically.

A Brief Summary of Problem Decomposition

Complex issues cannot be solved in one go. Attempting to tackle them as a whole often leads to merely addressing a symptom rather than the root cause of the problem. The more complex the problem, the less we can rely on our intuition.

Complex problems should be broken down into smaller subproblems. We start by dividing a large problem into distinct subproblems. Each of these can then be split further into even smaller, mutually exclusive and collectively exhaustive (MECE) tasks. We continue this process until the subproblems are simple enough to be tackled independently.

Decomposing a problem requires creativity; there is no one prescribed way to segment the issue. This process can be approached in multiple ways and often taps into our intuition, and you might argue, our intelligence. But with regular practice, what initially seems complex gradually becomes a straightforward technique.

Let's now turn the attention to two simple games that offer a fun and effective way to practice this skill with children.

Game 1: The Mystery Object Hunt

How It Works:

Imagine an object somewhere in your home, and challenge your child to identify it. However, rather than guessing the object randomly, the child should ask strategic questions to gradually narrow down the options. This exercise focuses on breaking the problem (guessing the object) into smaller, more manageable subcategories.

Why It's Complex:

At first glance, guessing an object in the house might seem a trivial question. Kids often want to leap to conclusions by guessing specific items immediately:

"Is it a chair?"

"Is it a ball?"

But without a stroke of luck, pinpointing the object directly could be time-consuming and test their patience.

The Strategy:

Teach them narrow the field of possibilities. This can be achieved in various ways—for instance, by identifying the object's location (e.g., living room, kitchen), which are mutually exclusive and collectively exhaustive (MECE) categories. Determining the room first significantly reduces the number of potential objects. Further breaking it down by the type of object or its colour transforms an initially difficult task into an easier one.

Through deductive reasoning, children learn to break down broad questions like "What is an object we have at home?" into smaller, more specific inquiries that lead them to the answer like "What metal object do we have in the kitchen that is used for eating?", as described in the example below.

Alternatives:

You can introduce this game to children at a very young age and adjust it according to their development.

For younger children, you might simplify the game by reducing the range of objects they can choose from. You can use a set of objects that can be grouped by shape, color, or material.

For older children, broaden the scope of the game to include a wider array of possibilities. You could expand beyond physical objects in the home to include animals, plants, and even celestial bodies such as planets and stars. This expanded version fosters exceptional creativity and problem-solving abilities.

Read more

What are Problem-Solving Techniques?

You might associate problem-solving with the math exercises that a seven-year-old would do at school. But problem-solving isn’t just about math — it’s a crucial skill that helps everyone make better decisions in everyday life or work.

Problem-solving involves finding effective solutions to address complex challenges, in any context they may arise.

Unfortunately, structured and systematic problem-solving methods aren’t commonly taught. Instead, when solving a problem, we tend to rely heavily on intuition. While for simple issues this can work well, solving a complex problem with a straightforward solution is often ineffective and can even create more problems.

The 7 Steps Problem-Solving Technique

Here’s a commonly adopted problem solving framework that guides you through seven crucial steps: Define the problem, Break it down, Prioritise, Plan, Analyse, Synthesise, Communicate.

Let's explore each step of these steps.

1. Define the problem: Start by clearly defining the issue at hand. Your problem statement should be precise, specific, measurable (when applicable), outcome-focused, and time-bound. Don't overlook the importance of alignment—ensure that it meets the expectations of all key stakeholders and decision-makers involved. When you execute this step effectively, your efforts will be targeted at solving the core problem, rather than getting distracted by peripheral issues.

2. Break it down: Complex issues often require deeper analysis. Instead of tackling the entire problem at once, the next step is to break it down into smaller, more manageable components. Various types of logic trees (also known as issue trees or decision trees) can be used to break down the problem. At each stage where new branches are created, it’s important for them to be “MECE” – mutually exclusive and collectively exhaustive. This process of breaking down continues until manageable components are identified, allowing for individual examination.

3. Prioritise: The next step involves prioritization. Not all branches of the problem tree have the same impact, so it's important to understand the significance of each and focus attention on the most impactful areas. Prioritising helps streamline efforts and minimise the time required to solve the problem.

4. Plan the analysis: For prioritised components, we may need to conduct in-depth analysis. Before proceeding, a work plan is created for data gathering and analysis. If work is conducted within a team, having a plan provides guidance on what needs to be achieved, who is responsible for which tasks, and the timelines involved.

5. Analyse: Data gathering and analysis are central to the problem-solving process. It's a good practice to set time limits for this phase to prevent excessive time spent on perfecting details. You can employ heuristics and rule-of-thumb reasoning to improve efficiency and directs efforts towards the most impactful work.

6. Synthesis: After each individual branch component has been researched, the problem is not yet solved. The next step is synthesising the data logically to address the initial question. The synthesis process and the logical relationship between the individual branch results depend on the logic tree used.

7. Communicate: The last step is getting the word out. Share the story and the solution with stakeholders and decision-makers through a clear and engaging message. Only when people fully understand the solution and its importance will they feel comfortable basing their decisions on it. This step brings everyone onto the same page and reinforces the value of the solution you've crafted.

Problem-Solving in Various Contexts

While problem-solving has traditionally been associated with fields like engineering and science, today it has become a fundamental skill for individuals across all professions. In fact, problem-solving consistently ranks as one of the top skills required by employers, regardless of the employee's role.

Problem-solving techniques can be applied in diverse contexts:

Individuals: What career path should I choose? Where should I live? These are examples of simple and common personal challenges that require effective problem-solving skills.

Organisations: Businesses also face many decisions that are not trivial to answer. Should we expand into new markets this year? How can we enhance the quality of our product development? Will our office accommodate the upcoming year's growth in terms of capacity?

Societal Issues: The biggest world challenges are also complex problems that can be addressed with the same technique. How can we minimise the impact of the climate change? How do we fight cancer? These are just a few examples of societal issues.

Despite the variation in domains and contexts, the fundamental approach to solving these questions remains the same. It starts with gaining a clear understanding of the problem, followed by decomposition, conducting analysis of the decomposed branches, and synthesising it into a result that answers the initial problem.

Real-World Applications of Problem-Solving Techniques

Let’s now explore some examples and look into the key steps of the problem solving process.

Problem: In the production of electronic devices, we observe an increasing number of defects. How can we most effectively reduce the error rate and improve the quality?

To tackle this issue, we can build the tree considering the various reasons why defects might occur by using a logic tree:

Before delving into data analysis, we can deprioritise branches for which we already have information or branches that are of lower importance. For instance, while transportation delays may occur, the resulting material degradation is likely negligible.

For other branches, additional research and data gathering will be necessary. We could do the research by analysing any available data, conducting surveys or talking to employees.

Given that our goal is to find the most effective solution to decrease defects, we need a method to rank potential solutions. One approach could be to evaluate the impact and the effort required for each solution identified at the leaves of our logic tree.

Data analysis might reveal that outdated or malfunctioning equipment is a major contributor to defects. However, replacing all equipment at once will be costly and complex. Conversely, improving communication could be a simpler yet impactful method to enhance work quality and reduce defects.

By assessing both impact and effort, we can systematically prioritise areas for improvement, focusing on those that offer significant benefits yet require minimal effort. This strategy ensures that resources are efficiently allocated to generate the highest return on investment.

Problem: What should my next job role be?

When breaking down this problem, we need to consider various factors that contribute to our future happiness in the role. This could include aspects like company culture, our interest in the work itself, and the lifestyle that the role's salary will support.

However, not all factors carry the same weight for us. To organize our thoughts, we can assign a weight factor to each element. For instance, passion for the job role may have a weight factor of 1, while interest in the industry might only have a weight factor of 0.5, as it's less crucial to us.

With this framework, we can systematically compare different roles. To evaluate a specific role, we would rate each factor, multiply that by the weight of the factor, and sum all these values.

Ultimately, while choosing a role, our intuition plays a significant role. However, by documenting all factors, we can approach our decision more objectively, ensuring that we aren’t biased and that we don't overlook an important factor that we might later cause regret.

Improving Your Problem-Solving Skills

Problem-solving requires practice and a certain mindset. The more you practice, the easier it becomes. Here are some strategies to enhance your skills:

Practice structured thinking in your daily life. Break down problems or questions into manageable parts. You don’t need to go through the entire problem-solving process and conduct detailed analysis. When conveying a message, simplify the conversation by breaking the message into smaller, more understandable segments. When making a small decision, consider using a basic logical tree to explore different outcomes.

Regularly challenging yourself with games and puzzles can help you keep your cognitive skills sharp. Solving puzzles, riddles, or strategy games can boost your problem-solving skills and cognitive agility.

Engage with individuals from diverse backgrounds and viewpoints. Conversing with people who offer different perspectives provides fresh insights and alternative solutions to problems. This boosts creativity and helps in approaching challenges from new angles. This is important skills you’d need especially for the problem decomposition phase.

Final Thoughts

Problem-solving extends far beyond mathematics or scientific fields; it's a critical skill for making informed decisions in every area of life and work.

Now, try this out: what's one question currently on your mind? Grab a piece of paper and try to apply the problem-solving framework. You might uncover fresh insights you hadn't considered before.

🧩🧒 Training problem-solving skills can begin as early as possible in life. In the upcoming articles, I'll share fun games you can play with your young children to help them develop these crucial abilities from their youngest age. Subscribe now to get it delivered directly to your inbox!

Subscribe now

Originally published at https://blog.logrocket.com at 2nd April, 2024

Gallups research on employment engagement showed that In 2022, only a mere 23% of the world’s employees were actively engaged in their work. While it’s encouraging to see a positive trend of this number over the last decade, this figure remains disappointingly low.

The key determinant of employee engagement is trust in leadership. Extensive research on this topic yields pessimistic results, with findings indicating that only 20% of the US employees strongly agree that they trust their organisational leadership.

Business leadership has become associated with a lack of respect. This negative perception extends to individuals who naturally possess strong leadership qualities, but they hesitate to take on leadership roles, feeling disconnected from the values and personality they believe a successful leader should embody.

Why does this negative perception persist?

This phenomenon can largely be attributed to the lack of authenticity displayed by many leaders in their daily behaviour and actions.

Bill George's perspective on authentic leadership

What is authentic leadership?

Authentic leadership signifies being genuine, true self, and acting consistently with your principles and values, without showing any sense of pretense. It is closely associated with honesty and integrity.

Authentic Leadership is a relatively recent theory in the field of leadership. It is closely associated with Bill George, executive fellow at Harvard Business School. In 2003, Bill elaborated on this idea in his book Authentic Leadership, and later he published his best selling book on this topic True North.

Character vs charisma

Bill believes that the negative emotions we experience today towards business leadership arise from our frequent preference for charismatic leaders over those with character-based leadership qualities.

We often favour individuals based on their image rather than those who consistently demonstrate integrity in their daily work. This tendency to prioritise style over substance leads to a command-and-control leadership approach. However, leadership based solely on image, without foundational integrity, is short-lived, and it won't be long before we lose trust with the decisions made by such leadership.

New generations ask for authentic leadership

Today, as the world faces numerous crises, we need a different type of leader —authentic leaders. Millennials and Gen Z know that. They value purpose over appearance. They seek workplaces that prioritise saving lives, support environmentally conscious initiatives, champion diversity and inclusion, and make the world a better place to live.

Bill George's personal journey

Bill George himself understands the downside of pretending to be someone he's not. He recalls a time when he worked in an environment where his values did not align. He felt like a stranger to himself, engaging in superficial gestures like wearing cufflinks to impress the board of directors. One day, while driving home on a beautiful day—he looked in the mirror and realised he felt miserable.

Upon joining Medtronic, he felt like coming back home to a place he had never been before. It was then that George truly comprehended the essence of authenticity. Medtronic's values and mission resonated with his own, allowing him to be his genuine self and lead with unwavering integrity. Under his leadership, Medtronic achieved remarkable success, with the company's growth exceeding 40-fold.

Core tenets of the authentic leadership

There are several key aspects that make the core of Authentic Leadership: purpose, values, heart, relationships, and self-discipline.

Purpose

Authentic leaders are driven by a strong sense of purpose. This purpose is bigger than their personal interests and is rooted in the desire to make a meaningful impact on the lives of customers and contribute to a better world.

Making money for shareholders is not a purpose. Saving lives, addressing climate change, offsetting income inequality—these are valid purposes. - Bill George

Bill George's leadership at Medtronic illustrates what purpose truly means. The company developed a product that significantly improved people's quality of life. While achieving remarkable growth, with revenues increasing from $750 million to an astonishing 40-fold, the true measure of success for Medtronic was the value delivered to the customer. The company’s key metric was the time it took to restore a person using Medtronic's product. And they managed to reduce this number from 100 seconds to only 0.5 seconds.

When a purpose-driven metric becomes the core of a company, employees gain a profound understanding of the true purpose behind their work. They recognise that their diligent efforts are not aimed at impressing their managers but at saving people's lives. This sense of purpose instills in them a strong sense of responsibility to deliver their best work.

Values

Authentic leaders have values. These values are not just mere words; they are real, deeply ingrained in their personality. They understand their values and never compromise on them. Every decision they make aligns with their values.

It's not about the perfection of their decisions. Mistakes are a natural part of any growth. What sets them apart is their unwavering integrity in decision-making and the transparency they exhibit. This transparency encourages others to follow, trust, and feel at ease with the decisions they make.

Heart

Targets and metrics matter significantly, but leaders should also show qualities beyond a strict focus on numerical outcomes. They ought to demonstrate empathy and genuine concern for their team members. This entails genuinely caring about the needs of others, recognising the importance of their needs, and being willing to make personal sacrifices to enhance employee well-being.

Leaders should foster an environment where open and honest closed-door discussions are encouraged. Freely expressing frustrations, acknowledging feelings of failure, or expressing career growth dissatisfaction—everything is welcomed. Open communication is what can unveil all bottlenecks, enhance people's well-being, and ultimately boost productivity.

Relationships

Authentic leaders care about their people beyond work. They take the long-term view. They maintain an open dialogue about career development with their team members while avoiding unrealistic promises.

When the time comes for an employee to transition to a new role or organisation, authentic leaders continue to offer support to the individual. While work is important, the well-being of people matters even more. Leaders provide assistance when possible, prioritising the well-being of individuals over the work itself.

Self-discipline

Leaders often find themselves balancing a lot responsibilities and competing priorities. Keeping focus and effectively moving an idea into tangible outcomes can be quite challenging.

An essential trait of authentic leaders is their capability to sustain unwavering focus and persistent dedication to tasks until completion. It entails the ability to remain cool, calm and focused, even in the face of stressful circumstances.

A heartening example of authentic leadership in action

Sean Georges shares an extraordinary personal story that serves as a powerful demonstration of what authentic leadership truly means in practice.

A young girl named Peyton was driving a car when she collided with a fully loaded coal truck, leaving her life hanging in the balance. First responders, comprising a diverse team of a police officer, volunteer firefighters, and an ambulance crew, rushed to the scene to save the life of this young girl. The outlook was pessimistic, and saving the girl's life appeared nearly impossible.

The team explored every opportunity without wasting a single minute. They managed to find a small sunroof opening. With strong determination, one of them climbed through the sunroof and found a way to extract the girl from the car. The girl was rushed to the hospital, where she underwent multiple serious surgeries.

They achieved what seemed impossible. After two years, the girl not only survived but thrived. She rejoined her class, graduated from high school, and now attends college.

What the crew demonstrated was an exceptional example of authentic leadership.

They had a clearly defined, shared, and powerful purpose: save the girl’s life. They were guided by their values, acting with integrity and compassion. It didn't matter who performed which action; it was all about the mission. They worked with a wholehearted commitment, driven by a profound sense of empathy and selflessness. They displayed an incredible level of self-discipline and focus knowing that every second is precious.

This story serves as a reminder of what authentic leadership can achieve. It demonstrates how humanity can reach incredible heights when these principles guide our actions.

How to foster authentic leadership style within your team

Is authentic leadership an inherent trait, or can it be learned?

I believe it necessitates a blend of both. Having a genuine personality, values that align with the core principles of authentic leadership, and alignment with the company's values should be integral to a leader's personality.

Once this foundational alignment is established, you can refine your leadership skills and continually improve. While some aspects may come naturally to some leaders, others may require deliberate attention.

1. Establish psychological safety in your team: Cultivate an open and transparent environment that embraces vulnerability. This creates a safe space for team members to do the same and share their challenges.

2. Share the purpose: Achieving goals begins with a shared purpose. Communicate regularly this purpose with your team, connect metrics to this purpose.

3. Practice active listening: Learn to listen until you have a comprehensive understanding of others' viewpoints. Ensure that every team member's voice is heard, not just the loudest ones. Practice one-on-one discussions to connect with each team member individually.

4. Share and seek feedback: Offer feedback constructively. Acknowledge achievements and point out areas for improvement. Don't forget to seek feedback from your team, you’ll uncover valuable insights.

5. Connect beyond work: Find opportunities to connect with your team members on a personal level outside of work. This fosters authenticity and a sense of safety within the team.

We owe authenticity to our people

Authentic leadership goes beyond appearance, image, or communication skills; it entails leading with genuine sincerity and a well-defined purpose.

In today's complex world, authentic leadership is not a preference; it's a necessity. This is what the new generations rightfully expect from leaders, and it's a path toward making the world a better place to live.

Authentic leadership is our responsibility to our people.

Originally published at https://blog.logrocket.com on November 28, 2023.

We all want to raise accountable children. One great approach is to involve them in responsibilities from the earliest age.

You could start with simple tasks like having them water the plants. If you ask them every day to water the plant – they'll probably do it diligently. However, the true test of accountability lies in what happens when we stop reminding them.

Will they still remember and take care of the plant?

If not, we have a diligent child who hasn't yet grasped accountability.

An accountable child feels responsible for the plant's health, making sure it receives sufficient water at the right moments. An accountable child would realise that the plant does not need water even when you tell them to water the plant. And if anything is not right with the plant, an accountable child will be on the lookout for solutions.

That's how accountability works!

Traditionally, product teams were not accountable teams.

In traditional product development, product teams followed a fixed roadmap with a predetermined set of features. Their measure of success was around completing these features on schedule.

Teams weren't held accountable for the ultimate success or failure of the product or product features. They were even unaware of whether their actions would contribute to the product's success. Understandably, as they operated within a context that shielded them from the broader business perspective, and their responsibility solely revolved around delivering what others had instructed them to create.

Decision-making authority rested entirely with stakeholders who often lacked an understanding of the technical complexities of the product and lacked the necessary data to assess the potential value of a feature.

Within such an environment, making well-informed decisions and constructing a successful product was a real challenge.

High-performing product teams are accountable to the Outcomes.

High-performing teams have different approach towards building a product. They have embraced Accountability as one of their key principles.

Accountability involves entrusting product teams not just with executing a product feature, but also with its ultimate success or failure. Team members feel a sense of responsibility and ownership in the outcomes they deliver.

Accountability introduces a level of autonomy within the team, and shifts the decision power from the outside stakeholders towards the team. This shift reflects a deeper sense of ownership, where team members are driven by a commitment to delivering meaningful results rather than just completing tasks as instructed.

Accountability does not mean full autonomy.

Accountability is often mistaken for teams being entirely autonomous and independent. However, there's a distinction between accountability and full autonomy.

Accountability doesn't imply that teams have unrestricted freedom to make decisions and take actions on their own. It doesn't mean that the team operates as a separate entity disconnected from the rest of the organisation.

In fact, accountable teams are in continuous communication with the rest of the organisation. This is crucial because their goals may shift if the broader company objectives change.

Accountable teams function within a defined framework. They have a clearly outlined objectives aligned with the broader company goals. Within this framework, they are given the authority to make specific decisions.

Accountability is not on individual, but team level.

Picture a football team competing in a tournament. The collective achievement of the team outweighs individual accomplishments.

This principle applies to business and specifically product teams as well. While every individual should undoubtedly bear responsibility and be committed to achieving their personal objectives and commitments, the team comes first.

This means adopting a mindset that prioritises the execution of team objectives over individual pursuits. This fosters a sense of cohesion, collaboration, and unity.

This doesn't mean that individuals aren't important. Instead, it shows that everyone is committed to reaching the company's goals and vision.

How do you foster Accountability in your team

So, how do you go about fostering a sense of accountability in your team?

In my previous two articles, I covered the first two principles of high-performing teams: Psychological Safety and Purpose with Clear Goals. I believe these two principles lay the foundation upon which Accountability would naturally thrive.

Now, let's delve into some key aspects to focus on:

Outcome-driven goals

Having a great team working towards the right objective can make remarkable progress in the company.

The same team working towards the wrong objective is a huge waste of time.

It's essential that your team's goals revolve around achieving concrete results. These goals should be outcome-oriented and should consistently align with the broader strategy of the entire company. For instance, a goal shouldn't just be about adding a new feature; rather, it could aim to improve user engagement.

Support and resources

While providing your product teams the autonomy to make decisions is crucial, they must also be equipped with the necessary support and resources. Accountable teams are those who operate independently, yet have access to the support they require.

As a manager, your intuition comes into play here. You need to gauge the right amount of assistance needed and when it's needed. Whether it's facilitating decision-making, providing essential tools, or connecting them to relevant sources of knowledge, this support is crucial.

Regular check-ins

Over time, circumstances change, company priorities might change, this is inevitable. Also the team learns along the way and their ideas evolve.

For an accountable team, it's vital to engage in regular check-ins regarding progress toward the company's objectives. Is there sufficient progress made towards the goals? Should new approaches be explored to achieve results faster? Is the original goal still relevant?

Engaging in these check-ins with your teams doesn't mean managing them; it's more about ensuring the ongoing synchronisation of their efforts with the company's overarching goals. It’s about tracking progress toward desired outcomes and making any necessary adjustments timely.

Embrace failure as part of the journey

An accountable team is not a team who always wins. it encompasses setbacks too. But an accountable team should own their failures, and should become much stronger and smarter after a failure.

For this to work effectively, it's crucial to normalise failure. You need to create an environment where people feel safe to experiment. A culture where failure is embraced as a way to help people learn and grow.

Make it a gradual transition

If you find yourself immersed in a traditional product development setup, implementing these principles directly can be a big transition. Such a significant shift might encounter resistance. That’s understandable. People need time for big changes.

Allow individuals the time to fully comprehend these principles. Give them space to internalise these concepts and cultivate belief in their potential impact.

Make the transition gradual, take small steps. As time unfolds, you'll witness substantial progress taking shape, ultimately leading to rewarding outcomes.

PPS. Here’s an index of all the articles in this series:

Intro: Key Principles of High-Performing Teams

#1 How to Cultivate Psychological Safety in Your Team

#2 How to Achieve Purpose and Clarity in Your Team

#3 How to Set a Culture of Accountability in Your Team

In my previous article, I covered three crucial principles for high-performing teams:

1. Psychological Safety

2. Purpose and Clear Goals

3. Accountability

Now, let's dive into the second principle: Purpose and Clear Goals. We'll explore why this aspect is vital and how you can instil it within your team.

From Task Completion to Purpose-Driven Work

In the past, work was often viewed merely as a means to earn income. You'd show up, complete your tasks and call it a day.

However, times have changed. People no longer aim to merely complete tasks; they seek meaning in their work. They want to contribute positively and make an impact. This desire for purpose is particularly prominent among younger generations, for whom making a difference is a top priority when choosing a job.

A study by McKinsey & Co. found that 70% of Americans, especially millennials, derive their sense of purpose from their work. They actively look for opportunities to contribute to a broader purpose through their job.

The absence of a clear sense of purpose can significantly impact both motivation and productivity. This is particularly crucial for teams that rely on creative problem-solving. Without motivation, achieving high-quality results becomes challenging, hindering the ability to innovate, create new solutions, or act proactively to drive any improvements.

How to foster Purpose and Clarity Among Your Team

How can you as a manager effectively nurture purpose and clarity within your team? How can you empower your team and propel them toward high-performance? Let's delve into the key strategies.

Get the right people on board

If you aim to foster a shared vision and purpose among your team and within your company, the initial step is to bring the right individuals on board. Often overlooked, this critical process begins during recruitment. While conducting interviews, it's not enough to solely evaluate a candidate's technical abilities or problem-solving skills. Instead, ensure that there is a good alignment between the candidate’s beliefs and the company's mission and values.

This alignment forms the foundation for a strong connection between the employee and the company. It lays the basis that can inspire them to remain committed, even if they later receive more enticing offers from other organisations.

Communicate your company's vision

Surprisingly, leaders often presume that everyone is well-acquainted with the company's vision and purpose. However, if you were to ask different employees to explain the company's vision, you would likely receive a range of answers.

As the leader of the company, you have invested significant time in formulating and refining the vision. Nonetheless, this does not automatically guarantee a shared understanding. Simply communicating the vision once and considering the task complete is insufficient.

Instead, ongoing dialogue is essential. Take advantage of every chance to reiterate the company's mission, vision, and impact. The more these discussions occur, the more deeply these concepts will become ingrained in your employees. And next to that, it’s crucial that every decision made by the company aligns with its vision and values. This is how employees truly internalise the vision and purpose, fostering a sense of unity.

Share context for effective decision-making

Having a team comprised of highly skilled and dedicated individuals who share a common mission is undoubtedly valuable. However, their effectiveness can be compromised if they lack the necessary context to guide their work decisions. And hard work can be wasteful if based on wrongly made decisions.

To prevent such pitfalls, sharing necessary context is crucial. It ensures that everyone in the team possesses a shared understanding of the circumstances or conditions in which you want to achieve something. Equipping your team with the appropriate background information empowers them to make informed choices. And even more, it reinforces your team's trust in the company's decision-making by assuring them that the choices made are accurate.

This does not mean that you should overload everyone with irrelevant information. For instance, engineers who are busy with a technical challenge might not be keen on delving into all the intricacies of the business context. Additionally, some information should be kept confidential due to its sensitive nature.

You as a manager should find the balance between what is essential to be shared and what isn't. The challenge lies in translating business context into relevant information that enhances the team’s productivity and effectiveness. This involves distilling complex business information into actionable insights relevant for the team and their decision-making process.

Align Objectives

Highly successful companies excel in establishing focused and clearly defined objectives. They go beyond leadership and extend these goals throughout the entire company, ensuring alignment across every individual with the company's objectives.

One valuable tool that supports this thinking is the OKR framework. The successful implementation of OKRs has yielded benefits for numerous companies. However, achieving effective goal alignment is not always straightforward. Many companies have attempted to adopt this framework without achieving the desired results. One significant factor behind such challenges is ineffective communication of these goals or setting objectives that are not in harmony with the company's overall strategy.

Leaders who establish concrete goals, need to be able to effectively convey them to the entire team. They need to articulate them in a way that resonates with the team members. Especially in large organisations, leadership's key responsibility is around pinpointing the right goals, ensuring their widespread understanding and instilling belief and enthusiasm among employees.

As a manager overseeing a team, your role encompasses a thorough grasp of the company's goals, translating them into specific objectives for your team, and effectively conveying these objectives to team members. The clarity in communicating goals and achieving alignment not only enhances team performance but also cultivates a sense of accomplishment and unity, thereby reinforcing the company's overarching mission.

Final thoughts

Nurturing a sense of purpose and clarity within your team should not be an abstract notion only. It requires genuine and profound attention.

It impacts the emotions people invest in their work, their level of motivation, and the quality of decisions they make in the workplace.

These elements collectively lay the groundwork for achieving exceptional performance within you team and steering everyone towards the same goal.

Till next week.

Best,

Marina

PPS. Here’s an index of all the articles in this series:

Intro: Key Principles of High-Performing Teams

#1 How to Cultivate Psychological Safety in Your Team

#2 How to Achieve Purpose and Clarity in Your Team

#3 How to Set a Culture of Accountability in Your Team

Plenty of research has been performed to understand what sets apart high-performing teams. What this investigation revealed is that the key lies in fostering an environment where people feel safe, motivated, and happy.

Research conducted at Google showed one characteristic that stands out as the number one factor of highest performing teams - Psychological safety.

Psychological safety means creating a team culture where individuals feel secure to openly share their mistakes and ask any question without fear of judgment.

Psychological safety creates team bonding and makes people motivated to come to the office and solve problems together as a team.

Transparency and honesty are vital in maintaining this psychological safety. Without it, problems remain hidden, negative emotions arise, and fear hinders progress. This leads to wasting valuable time on resolving issues that may not even exist or that can be solved very quickly.

If you are a manager of a team, you play an important role in fostering psychological safety. While the overall company culture also contributes significantly, it is within your power to disseminate and reinforce this culture within your team. Your team members perceive psychological safety mostly through your actions and interactions, as well as through the team dynamics they experience while collaborating.

So how do you make your workplace a psychologically safe place?

Show vulnerability and openness yourself

This is my most important advice. Share your own challenges, failures, and learning experiences with your team. Show your true self.

Managers who are open to show to the team their vulnerabilities and weaknesses are leaving room for the others to be open and share their mistakes as well. This fosters a culture where mistakes are seen as positive opportunities for growth.

In a 2018 Harvard study, it was revealed that managers who embrace their humanity and acknowledge their failings improve their reputation among their direct reports.

Alison Wood Brooks (Harvard Business School Assistant Professor) puts it nicely:

Let go of your ego and bridge the gap between you and your team. Remember, your role isn't to know everything or to be the person who never makes mistakes.

Instead, be the kind of leader who leads with authenticity, openness, and a growth mindset. Your team will find inspiration in your journey and be motivated to strive for excellence together.

How to show vulnerability?

I would not advise for any specific actions. Instead it’s about the subtle daily gestures that reflect your team-first mindset.

For example, acknowledge your mistakes when you could have done things better. When faced with something unfamiliar, you don't need to shy away from asking questions, acknowledge your lack of expertise and ask until everything becomes crystal clear. Having one-on-one conversations is also a great moment to show respect and empathy. Sharing your personal stories is also a good way to show your true self.

The key lies in cultivating a team-centric mindset—the appropriate actions will naturally flow from there.

Make sure everyone’s voice is heard

As a manager you need to be there for the others when they need you.

One-on-one meetings are an excellent opportunity to dedicate time and attention to each team member individually. Be an active listener during these sessions and show genuine interest in their thoughts, concerns, and ideas.

There's no need to follow a rigid formal process for one-on-one meetings. Tailor the frequency and format to accommodate each team member's needs. Some may benefit from weekly discussions, while others might prefer less frequent interactions. Treating individuals differently in this regard doesn't imply unfairness; rather, it demonstrates your commitment to supporting and being there for each team member when they need it.

Pay close attention during group discussions. Does everyone feel comfortable to openly share their opinions. Various factors such as personality, cultural background, level of seniority, and gender can influence how individuals participate in a group setting.

As a manager, it is crucial to create an inclusive environment where everyone's input is respected and valued. During group discussions, direct questions to specific team members to ensure that diverse perspectives are considered or use techniques like anonymous voting.

Recognise that some team members, particularly more introverted, might prefer to express their thoughts in a more private setting. Encourage them to share their opinions via email or during one-on-one meetings, where they may feel more at ease and willing to engage in deeper discussions.

Share feedback and ask for feedback

Feedback is powerful tool for growth.

Personal feedback is necessary for employee personal development. Team feedback, which delves into how the entire team functions, is equally vital, as it initiates healthy debates and discussions and stimulate improvement.

Liz Hilton Segel, McKinsey’s global leader of industry practices, puts it nicely:

Unfortunately, many managers encounter difficulty when it comes to giving feedback. It's a common struggle. They tend to avoid conflict out of fear of upsetting the recipient or having uncomfortable conversations.

Providing upward feedback can be even more challenging. When employees are unhappy with their manager, they might hesitate to express their concerns openly. As a result, valuable insights and opportunities for improvement often remain untapped.

As a manager, your crucial role is to create a safe environment where sharing feedback is encouraged. Don't wait for formal evaluation meetings; seize every chance to provide direct feedback when you spot areas for improvement or you feel someone deserves to be praised.

And equally important, be proactive in seeking feedback from your team members. You might discover valuable insights you were unaware of. This two-way feedback process strengthens the bond between you and your team, it helps build trust and deep connection.

When providing feedback, always do so in a positive and constructive manner, avoiding unnecessary criticism. To make the feedback process smoother, consider employing a feedback giving model that fits your team’s style. These models are designed to make giving feedback easier and more positive, ensuring a win-win situation for everyone involved!

Take a break and connect beyond work

While team-building events and celebrating milestones might be second nature to people managers, those more focused on goals and content may not naturally prioritise them. However, it is crucial not to underestimate their importance in building a happy and motivated team.

When I assumed leadership of my team, we began with a remote setup for two months, and it proved to be effective. However, during this period, I acknowledged the importance of forging deeper connections with my team members.

We decided to meet in person, taking a break from our daily challenges to encourage innovative thinking and engage in team-building activities. This shift brought significant value to our work and strengthened our collective bond.

I encourage you to find suitable moments for team-building and celebration activities. Allocating time for such events might feel like slowing down your regular work, but the return on investment is well worth it. It provides a substantial boost in team motivation and overall productivity.

Final thoughts

Psychological safety is the basis for building a high-performing team. While integrating various productivity techniques remains vital, establishing physchological safety as a foundation takes precedence.

When employees arrive at the workplace with motivation and enthusiasm, they naturally take the initiative to work more diligently, be more creative, and proactively seek opportunities to elevate their performance.

Till next week.

Best,

Marina

PPS. Here’s an index of all the articles in this series:

Intro: Key Principles of High-Performing Teams

#1 How to Cultivate Psychological Safety in Your Team

#2 How to Achieve Purpose and Clarity in Your Team

#3 How to Set a Culture of Accountability in Your Team

These industry giants are known for their great products. But there is something beyond that. Behind these great products are high-performing teams that drive excellence.

What sets these teams apart?

Certainly, having strong and skilled employees is one key factor. To pass a Google interview, for example, candidates need to pass many stages, meet high standards and demonstrate exceptional abilities.

But there's much more to their success than skills alone. It's the culture they foster, their guiding principles, and the environment they create that sets them apart. These companies create a culture that motivates and inspires their employees, allowing their teams to thrive and achieve remarkable results.

The good news is that even if your company isn't as prominent as Google, you can still aspire to become a place where high performance and excellence are the vision that every team aims for.

And it's not just about replicating the success of giants; it's about creating a unique environment that inspires and drives your team towards greatness.

So, what are the fundamental components of high-performing teams? Undoubtedly, each team is unique. However, certain key principles consistently stand out in all high-performing teams.

• Psychologically Safe Environment - Plenty of research has shown that the key to high-performing teams isn't about having the best individuals. It's about fostering an environment where people feel safe, motivated, and happy. Google's research highlights psychological safety as the #1 factor in top-performing teams. When team members can openly share mistakes without fear of judgment and freely seek answers through questions, productivity cal flourish.

• Purpose and Clear Goals - In the past, it was common to view work simply as a means to earn money. However, in today's world, people increasingly seek a deeper sense of purpose in their careers. This trend is particularly evident among the younger generations, who prioritise purpose when choosing a job. When teams have a shared sense of purpose and a clear goal to accomplish, they are much more motivated and engaged, which drives greater productivity and fulfilment within the team.

• Accountability - In a psychologically safe environment, coupled with a clear sense of purpose, teams are empowered to take Accountability for their work. This sense of ownership fosters a culture built on responsibility and trust, where every member is seen as reliable and committed to delivering on their promises. As accountability takes root, teams become creative, and open to explore new solutions and ideas. Failures become valuable learning opportunities, and continuous improvement becomes the norm.

While there are numerous other characteristics that define highly-performing teams, I believe that these three principles form the core foundation. They serve as the backbone of a healthy and productive team, laying the groundwork for success.

In a place where they feel safe, with a clear sense of purpose, and shared accountability, teams can build a solid framework for continuous growth and excellence, and are prepared to achieve remarkable results.

What follows is a series of short essays.

#1 How to Cultivate Psychological Safety in Your Team

#2 How to Achieve Purpose and Clarity in Your Team

#3 How to Set a Culture of Accountability in Your Team

In the upcoming weeks, I’ll dive into each of these topics and I’ll share tips and practices on how to build Highly-effective teams.

Till next week.

Best,

Marina

In this post, I’ll talk about product culture.

A culture plays a big role in every company. It sets the tone for how people collaborate together, how they approach their work, and how they contribute to the success of the company.

It influences employee engagement, talent attraction and retention, productivity, innovation, customer satisfaction, and the overall identity and reputation of the company.

A positive and inclusive culture is therefore essential for creating a successful company.

Best product companies have strong product culture. But what does product culture actually mean and what are the integral parts of such culture? Does your company have a mature product culture?

One great way to answer that is by observing how product-related decisions are made.

Let’s first explore examples of what is not a strong product culture.

Business-driven culture

If the power to make decisions primarily lies with business executives or managers, it indicates a more business-dictated or executive-driven culture rather than a strong product culture.

This scenario is quite common. Management makes decisions and then provides direction to product teams regarding what to build and which milestones should be achieved. Product teams, including engineering, design, and other functions, are expected to follow these directions without significant involvement in the strategic decision-making process.

In such an environment, the product teams execute the plans and priorities set by business leaders.

Because of this, product decisions are usually driven by business needs, like revenue goals, or financial considerations, rather than a deep understanding of customer needs or a focus on delivering an exceptional user experience.

Sales-driven culture

Another prevalent cultural form is the sales-driven culture. Product team's decisions about what to build are strongly influenced by sales needs and the requirements of the prospects in the sales pipeline.

While a sales-driven culture has its merits and is suitable for certain organisations, it's important to recognise that this is different than a product-driven culture. In such organisations, the likelihood of developing an innovative, strategically viable and highly scalable product with long-term market success is decreased.

Key traits of a strong product culture

A product culture is characterised by a deep focus on understanding and meeting customer needs, driving innovation, and continuously improving products. It is an integral part of companies that prioritize product excellence and are dedicated to delivering value to their customers.

Customer-centric mindset

A great product culture begins with a strong focus on customer-centricity. Everyone in the organisation shares a deep understanding of who the product is designed for. This includes the product team, including developers, who possess a keen understanding of the user.

The company goals are primarily defined from a customer perspective. In this way, decisions about product are made in a manner that maximises user benefits.

Empowered product teams

They product teams are empowered. They take ownership of their work and make decisions that align with the product vision and customer needs.

Every product team has a clearly defined goal that aligns with the company’s overarching objectives. The teams have the autonomy, accountability and necessary resources to innovate, experiment, and iterate towards achieving that goal.

They are actively encouraged to engage in constructive criticism, irrespective of hierarchy. The collective goal is to ensure that the best decisions are made, regardless of the origin of the ideas.

Decisions informed by data

Data plays an important role in decision-making. Product teams fully recognise the benefits the data. They seamlessly integrate product analytics into the product development process.

Regular practices such as user research, customer feedback, and usability testing are employed to validate assumptions. The insights derived from these validations hold significant weight in determining which features to prioritize and build.

Teams are actively encouraged to experiment, test hypotheses, and learn from both successes and failures. A lot of ideas undergo daily testing, with only the few showing promising results moving forward into production.

Cross team collaboration

The are no hard boundaries between departments. There is a strong emphasis on collaboration and breaking down silos between different departments.

Product, engineering, design, marketing, and other teams work together. They share knowledge and expertise to deliver outstanding products.

Higher company objectives are set across teams. Cross-departmental collaboration is fostered to achieve these goals.

Continuous Improvement and Iteration

Great product culture is a culture of continuous learning.

It encompasses ongoing improvement for the product, continual growth for the team and their way of working, as well as continuous personal development.

The teams don't aim for perfection right away. Instead they focus on learning and getting better with each new phase.

Clear product vision and strategy

Strong product culture means also a well-defined product vision and strategy.

They are both effectively communicated and comprehended throughout the company. They serve as guiding principles, fostering alignment and clarity. Their purpose is to steer everyone towards the desired outcomes and direction.

Final words

A great product culture does not just happen. It starts with awareness, and then gradually transitioning to a company where everyone is passionate about creating value for customers.

This transformation may need change, and change takes time. However, by actively working on it and continuously striving for improvement, you will enjoy the benefits more and more with each passing day.

Thank you for staying with me throughout this article. As usual, if you have any thoughts, questions, or comments, don't hesitate to get in touch.

Until next time, take care!

Marina