T-shape

There’s a question that keeps coming back, no matter what field you’re in.

Should you go deep into one thing, or learn a bit of everything?

At the start, the answer usually feels obvious. You pick something specific, focus on it, and try to get good as quickly as possible. It works. You become useful, maybe even valuable, because you can do something clearly defined.

That’s the specialist path.

It has a kind of momentum to it. The rules are clear, the feedback is fast, and the progress is measurable. If you’re a software engineer, you write code and see if it works. If you’re a surgeon, you follow procedures that have been refined over years. The system rewards precision.

For a while, this approach is hard to beat.

But over time, something subtle starts to happen.

The problems change.

They stop being well-defined. Instead of clear tasks, you get messy situations. Instead of direct feedback, you get delayed consequences. And suddenly, being very good at one narrow thing doesn’t always translate into making good decisions.

That’s where generalists start to look different.

They don’t necessarily move fast at the beginning. In fact, they often look slower, even unfocused. They spend time exploring different areas, picking up pieces that don’t seem connected.

But later, those pieces start to form patterns.

Because many real-world problems aren’t isolated. They sit between domains. Technology affects business, business affects people, people affect design. And someone who has seen multiple perspectives can navigate that space more easily.

It’s not that they know more in total. It’s that they see connections others might miss.

If you look at history, both paths show up again and again.

Some breakthroughs come from deep focus. Someone spends years pushing the limits of a single idea until it breaks open. Others come from combining things that were never meant to be together. Not deeper, just… different.

Neither approach is enough on its own.

And that’s where the idea of a “T-shape” comes in.

Instead of choosing between depth and breadth, you build both, but not equally.

You go deep in one area first. Deep enough to understand how things actually work, not just at the surface. That becomes your anchor. It gives you credibility, and more importantly, it gives you a way to think rigorously.

Then, slowly, you expand outward.

You learn adjacent fields, not to master them, but to understand how they connect. You start seeing how your core skill fits into a larger system.

Over time, the shape becomes clear.

A vertical line of depth. A horizontal line of context.

The depth helps you solve problems.

The breadth helps you choose the right problems.

And in a world that keeps getting more complex, that combination matters more than either one alone.

So the question isn’t really “which one should you pick?”

It’s more about timing.

At the beginning, depth gives you a place to stand.

Later, breadth gives you a way to move.

author: Ope tag: #content links: