The most important lesson I learned when I first stepped into leadership was re-framing how I approached problems. Here's a high level view:
- A bad leader approaches problems vertically
- A good leader approaches problems horizontally
- A great leader does both, and knows when to do which
Vertical vs horizontal thinking
Let's first define these 2 words:
- Vertical thinking is when you focus deep on solving a problem
- Horizontal thinking is when you examine a problem across multiple dimensions & perspectives
To illustrate better, here's a recent scenario I dealt with:
A few reports brought up to me (paraphrased & names changed):
"Johnny, I think Bob is a poor product manager. Every time I work with him, it takes way too long to get a response, and the tasks he assigns me are nowhere near as good as Suzie's. I think we really need to get Bob to work on his communication skills or back-fill someone more like Suzie onto the team."
Here's a vertical reaction to this insight:
- Multiple people have brought this up, so there's clearly a problem here
- I should find a way to address this with Bob and help him improve around this area
Here's a horizontal reaction to this insight:
- Do other parts of the org feel the same way about Bob?
- How does Bob feel about the people he's working with? Could there be a misalignment or assumption of expectations?
- Regardless of whether Bob's communication is the actual problem, something is not working in how my team operates. What is the root issue?
Which one felt more natural to you? I'll bet it was the vertical reaction (me too honestly!).
Most people are naturally good vertical thinkers. This makes sense because for most of life, someone with more context than you is giving you a problem to solve (i.e. teachers giving you assignments, bosses giving you tasks).
The script that has worked so far suddenly breaks, because at the leadership level, no one has more context than you. You are now forced to think horizontally because you can't trust the problems that are being presented to you. Not because the people bringing up problems are wrong, but because they lack the context to see the bigger picture.
This is why I said great leaders need both horizontal and vertical thinking:
- Horizontal thinking allows you to question the problem to determine if it's the right problem to solve
- Vertical thinking allows you to solve a problem once you're sure you can trust it
How to think horizontally
In the context of a leadership role in a company/startup, horizontal thinking requires you to put every problem through a pipeline:
1. Signals & assumptions
As a leader you should never trust anything at face value. Not because people are lying, but because:
- People have limited context and don't see the full picture
- People are not good at articulating what they actually mean
- People are biased and emotional
Do not try to solve every problem that comes your way (vertical habit). Instead, treat it all as nothing more than a signal. Once you've stored enough signals, you'll start to notice patterns, and build some assumptions. For example:
- I notice this person is consistently bringing up issues about Bob. Could they dislike him? Can I trust this person's judgement of people?
- I notice more than once Bob being called out for being a vague communicator. Could that be true? Or do the people he's working with require too much hand-holding?
- I notice that Bob seems to be delivering on his work. Could he be overstretched and keeping to himself?
- I notice I don't know the sales team's POV on Bob. Would that help me in any way?
2. Building more context
From some of the signal examples above, we clearly see that thinking horizontally has revealed we lack a lot of context, leading to a lack of conviction. The next step is to build more context by talking to more people. How deep and wide you go here depends on the problem and how much conviction you feel like you need to build.
It might seem daunting to have to do this for every single problem, but in reality, as you do this, you start to build up more context naturally. This process gets much easier over time. In the beginning, you're going to be overloaded, but eventually, you'll do this so much that certain problems won't even require you to do this step anymore.
Some people's instincts might be to wait until 1:1s to have a conversation with reports, but that's usually not the right way to go because:
- You don't know how long these calls are going to go
- You don't want to take up 1:1 time to discuss this when your direct report might have something more important they want to discuss
- Some problems can't wait
Instead, whenever something is on your mind, just reach out and hop on a quick chat with the person to get their perspective. People are always more than happy to offer their perspective on something.
3. Build conviction
Once you've built enough context, you should start to notice patterns form, and this is where you start to build conviction. True conviction forms here because you're removing all silos and now thinking horizontally, as if you were the organization instead of any individual. When you do that, you start to see problems from multiple dimensions, and you get to the root of what's going on.
Through practicing this, you'll naturally notice yourself asking more organizational questions like:
- Are you missing leadership anywhere?
- Are the current meetings or structures broken?
- Are there problematic individuals?
- Is there a misalignment between company goals and team goals?
- Are there any assumptions being made that aren't being said out loud?
Only once you build conviction and signal through horizontal thinking can you comfortably apply vertical thinking, because you will know with more certainty that you are addressing the actual root problem.