Need someone to lead product management at your software company? I create software for people that create software and I'm looking for my next opportunity. Check out my resume and get in touch.

Strategy Means Saying No

Freshness Warning
This blog post is over 3 years old. It's possible that the information you read below isn't current and the links no longer work.

It’s not the notes you play, it’s the notes you don’t play. - Miles Davis

An oft-overlooked aspect of strategy is to define what you are not doing. There are lots of adjacent problems you can attack. Strategy means defining which ones you will ignore.

There are three types of opportunities you’ll come across. Those you’ve decided to tackle, those you’ve decided to ignore, and those you didn’t know existed. By defining which ones you’ll ignore alongside those you’ll tackle, you bring clarity to how you think about a problem.

I once worked with an executive that called himself an "and leader." When confronted with his organization asking if they should focus on this or that, he would proudly say yes to both.

This is a failure of leadership.

Anyone can say yes to everything. They don’t need a leader to do that for them. Thinking strategically means deciding what you’ll do. The list of things you’ll do is only meaningful if there’s a limit to the list.

Leaders communicate strategy by explaining what the organization is going to do, but often forget to communicate what they’ve chosen not to do. It is more effective to include negative choices when communicating strategy. It’s easier for people to understand the choices you made when you put them in the context of the choices of what to leave out. They’re two sides of the same coin. Communicate them as such.

By having a clear strategy that covers both what you’ll do and what you won’t do you’ll improve your organization’s ability to make decisions themselves and to execute.

An effective strategy acts as guide rails. If people know what to say no to, it’s clear whether you’ll pursue or evaluate a new opportunity that appears.

Recently Written

Too Big To Fail (Apr 9)
When a company piles resources on a new product idea, it doesn't have room to fail. That keeps it from succeeding.
Go small (Apr 4)
The strengths of a large organization are the opposite of what makes innovation work. Starting something new requires that you start with a small team.
Start with a Belief (Apr 1)
You can't use data to build products unless you start with a hypothesis.
Mastery doesn’t come from perfect planning (Dec 21)
In a ceramics class, one group focused on a single perfect dish, while another made many with no quality focus. The result? A lesson in the value of practice over perfection.
The Dark Side of Input Metrics (Nov 27)
Using input metrics in the wrong way can cause unexpected behaviors, stifled creativity, and micromanagement.
Reframe How You Think About Users of your Internal Platform (Nov 13)
Changing from "Customers" to "Partners" will give you a better perspective on internal product development.
Measuring Feature success (Oct 17)
You're building features to solve problems. If you don't know what success looks like, how did you decide on that feature at all?
How I use OKRs (Oct 13)
A description of how I use OKRs to guide a team, written so I can send to future teams.

Older...

What I'm Reading

Contact

Adam Kalsey

+1 916 600 2497

Resume

Public Key

© 1999-2024 Adam Kalsey.