DEV Community

Salem Evbogbai
Salem Evbogbai

Posted on Originally published at salemsmith.substack.com

Thoughts on “Bias Towards Action”

As long as one can remember and especially in tech spaces, the term “Bias for action” has become the default setting in a lot of modern settings. Speed matters. Markets move. Customers don’t wait.

But when everything becomes “go, go, go,” that bias can quietly create a few unhealthy patterns:

1. Solutions Looking for Problems

When we move too fast, we jump to answers before we fully understand the question.

It’s human nature: the more experience we have, the more likely we are to reach for familiar playbooks — a new process, a favorite framework, another tool.

The risk: we spend cycles polishing solutions that were never pointed at the real problem.

2. Motion Without Direction

In action-heavy cultures, “What are the next steps?” becomes the default ending to every meeting.

Action items, status updates, and “quick wins” pile up.

But if we’re not careful, we end up with a lot of motion and not enough direction.

Progress only matters if it’s progress toward something clear.

3. One-Way Doors Taken Too Quickly

The most dangerous form of action bias shows up with one-way door decisions:

  • Major strategic shifts
  • Big reorganizations
  • Large, irreversible bets

These are situations where speed still matters, but so does thoughtful input from the people who hold context and expertise.

Rushing through those can create long shadows.

A Better Lens: Match the Response to the Problem

Not every situation deserves the same tempo. A simple way to think about it:

  • Simple problems → Apply a known fix quickly

(Your laptop freezes, you restart it.)

  • Complicated problems → Analyze first, then act

(Rolling out a new internal system.)

  • Complex problems → Run small experiments

(Figuring out what customers truly value, exploring a new space.)

  • Crisis situations → Act now, analyze later

(Critical outage, true cash-flow emergency.)

The Key Distinction

  • Reversible decisions (two-way doors) → move fast. You can adjust.
  • Irreversible decisions (one-way doors) → slow down. Get perspectives. Be deliberate.

Most calls we make are reversible. A small minority are not. Knowing the difference is where judgment lives.

The Bottom Line

“Bias towards action” is powerful when it’s paired with context.

Without that, it’s like shooting before you’ve aimed.

Sometimes the most productive move isn’t to add another action item — it’s to pause, think, and choose the right kind of action for the problem in front of you.

That’s not being slow.

That’s being intentional.

Across many concentric circles, I have discovered that a lot of conversations about “product” leans towards product management which is popularly referred to as the intersection of strategy, technology and UX. That makes a lot of sense: Remarkable software is preceded by effective product management.

However, there is a bigger question. How can product leaders cultivate and inspire high energy, low ego, sound judgement teams to solve important problems and make an impact on the business? How do we get closer to our customers to envision, co-create and prioritize the right experiences at the right time? And what is the best way to approach each sprint, plan each next quarter and scale year on year?

While product management is primarily about solving customer and business problems, product leadership also entails developing your team and a great deal of partnership*.*

For anyone in a product leadership role, these questions are top of mind. I am hoping to address the topic of leading teams, exploring the associated challenges, tradeoffs and controversial decisions.

Below are a few principles that I believe product leaders should embrace.

The people are front and center

Product leadership becomes a forcing function to constantly take multiple steps back and ask: Where is your company’s unique value in this world? What is the vision for the enterprise? And how do you assemble and grow a team to passionately pursue that vision, without always having the formal authority to do so?

One thing is guaranteed: You won’t be able to do it alone. The most effective product leaders know that they succeed when the team succeeds. There is this humbling acceptance that your ideas (and solutions) may sometimes be rigorously examined as well.

Hire the right people with the right attitude, support them and then empower them to get stuff done.

True leaders lead with two things: they start with “why,” and put people first. This implies painting a picture of the future, while seeing and inspiring the best in others. It means being a mission-driven enabler that spends time in the weeds, not an authoritarian ruler. And it means giving credit publicly, owning and apologizing for mistakes, and delivering radical candor when needed.

Be maniacally focused

Being maniacal means being unmoved in service of the goal. It is rooted in knowledge that external distractions will always come, but the goal remains the focus. The interesting corollary to this is leaders are flexible on how the goals will be achieved. They anticipate change, help establish frameworks and facilitate momentum in their teams, ensuring that decisions made today still matter a year later, and if they don’t, the team learns valuable lessons from them.

If everything is important, then nothing is.

While it is easy to get caught up in documentary / performative activities like JIRA tickets, feature requests, meetings and executing, executing, executing all day long, it is more important to identify where those activities fit into your overall strategy and roadmap, you will be constantly prioritizing the wrong things.

Give every issue its fitting attention, so don’t get caught up in distractions. If everything is important, then nothing is. This is why strategy must be carefully crafted, so it informs what to do next with limited information and resources and, ultimately, when to say no.

Make things happen

By design, leaders should drive outcomes. In doing this, they are trained to spot and more importantly, overcome problems. It is why they can spot opportunities amidst chaos and inspire (and in most cases, coach) others to do the same.

That said, as you lead talented people, you need to be incredibly self-aware (especially about the things you are not good at). Make sure you have a team that supplements what you lack. Hire the right people with the right passion, empower them and then stick together as a team to get stuff done. Sometimes, that means working with them to figure out what’s getting in the way. And other times, that means you are the one who needs to get out of the way.

And this goes beyond the product itself. Product leadership not only includes setting the strategy, guiding the roadmap, and scaling the team, but also contributing to the building process (which takes immense collaboration with business, legal, design, engineering and anything that has to do with nailing the customer experience). In the eyes of your customers, everything they experience related to your company is “the product.” Make sure you are supporting and partnering with those in customer-facing roles.

And when things don’t go as planned, remain calm. Grace under fire is a beautiful thing. Channel any pressure, stress or fear in productive ways. Difficult times will test and refine a team; see this as an opportunity to lead by example.

Perpetually optimizing

I’ve always liked the idea of Kaizen: change for the better. Product leadership means continuously optimizing; constantly getting better; never feeling like you’re done. And products are never done, so everything can always be improved — from how we do agile processes, how we run sprints, how we present, how we question our assumptions to how we think about customer pains and needs. As a product leader, I need to make sure our team keeps getting better. Sometimes that means working with them to figure out what’s getting in the way. And other times, that means I’m the one who needs to get out of the way.

Leadership isn’t a task; it’s a mindset. Anyone on the product team can embody this.

Speed is a popular (and controversial) topic in product management. Some people believe you shouldn’t focus on it. Others think your team should always be getting faster. Without a sense of urgency, startups do not survive, and big companies start to decline.

I think it’s a case-by-case basis; there are some things you have to let brew and make sure you get them right. But at the end of the day, if you are getting better at something, you should be able to gain velocity. It’s like exercise, the more your teams collaborate and measure progress, the better and faster they will be able to move. However, I think trying to be fast for the sake of being fast means losing sight of the customer. You should optimize for customer outcomes, not just software outputs. Velocity without impact is meaningless.

Again, take absolute care of the customer

We are not just here to deliver a product, but to provide value to each customer, giving them the context and actionability they need to solve problems. And that requires good design, taste, creativity, and empathy for the customer. And those aren’t just empty words. Everyone talks about “empathy”; it has become a buzzword, but there is real meaning and substance behind it.

True product leaders care first and foremost about the customer; they are responsible for the customer’s success as it relates to the product.

In Summary

I maintain that leadership is not a task, but a mindset. Anyone on the product team can embody this: From developers to product managers to designers. It’s everyone’s responsibility to take care of the customer. You do not need a title to become a leader.

Great product leaders elevate the entire organization, while bad ones bring everybody else down with them. That’s why, every day, we ask ourselves: What problem are we solving? Who are we solving it for? How do we measure success? And what have we learned?

I leave you with a mantra that has stayed with me over the years;

Not everything we ideate is going to be developed; not everything we develop will be shipped; not everything we ship will succeed. But we will learn, and we will value each lesson we learn as we go from zero to 1 to 100.

Top comments (0)