What I Keep Noticing
Lately I have been sitting with one uncomfortable thought. Many enterprise teams are trying to win a new game with old instincts.
Many enterprise teams are trying to win a new game with old instincts.
We talk about AI, speed, and reinvention, but the day-to-day behavior still rewards certainty, control, and local optimization. That worked in slower environments. In this one, it breaks.
I do not think this is a tooling problem. I think it is a skills problem.
What Feels Off Right Now
The language sounds modern, but the operating model often does not.
I still see leaders asking for precision where ranges would be more honest. I still see transformation plans that treat change as a one-time program instead of a capability. I still see teams optimizing what they already know while the market keeps shifting underneath them.
That gap matters. If the pace of change is compounding at an exponential rate, then skill half-life is shrinking at the same time.
My Current View on the Skills That Matter
The skills I trust most in this era are less about knowing one more tool and more about how people think, learn, and collaborate under pressure.
First, creative problem framing. I need people who can redefine the problem, not just execute the default answer.
Second, willingness to challenge current thinking. If inherited assumptions are never questioned, we protect legacy logic long after it stops creating value.
Third, incremental delivery toward a clear target state. Big-bang change usually fails. Directional movement with tight feedback loops usually compounds.
Fourth, curiosity as discipline. Curious teams test faster, learn faster, and recover faster.
Fifth, customer focus over internal convenience. The moment internal process becomes the primary design driver, we start scaling friction.
Sixth, strong fundamentals. Tools keep changing, but decision quality, systems thinking, incentives, risk, and human behavior keep showing up.
Seventh, the blend of generalist and specialist skills. Martin Fowler described this well in his article on expert generalists. I agree with the core point. We need real depth and useful breadth in the same person, especially in leadership roles.
Eighth, sympathy for related domains. I am not looking for everyone to become everything. I am looking for enough appreciation across engineering, product, operations, finance, risk, and customer reality to make better tradeoffs.
Ninth, first-principles pattern recognition. Where is the real bottleneck? Which assumption drives the result? What incentive is distorting behavior? Those questions travel across every wave of technology change.
The Enterprise Gap I Keep Running Into
Here is the pattern I keep seeing in large organizations:
- Hire for narrow role fit
- Promote for execution inside the current process
- Measure short-term output over long-term capability
- Treat cross-domain thinking as optional
This produces local efficiency and system fragility at the same time.
That is why many transformation efforts look active but feel shallow. The organization is moving, but the underlying capability model did not change.
The Part We Do Not Like to Say Out Loud
Some of these skills are trainable. Some are difficult to teach directly.
You can teach experimentation methods. You can teach decision frameworks. You can create more cross-functional exposure.
What is harder is the unlearning. People have to let go of behaviors that made them successful in the previous era.
That includes certainty theater, false precision, process worship, and expertise as territorial control.
None of this is easy, because those behaviors were rewarded for years. But if we avoid the unlearning, old strengths turn into drag.
What This Changes for Leaders
If this view is right, leadership development has to change.
I would invest less in one-time training events and more in operating mechanisms that force better thinking every week:
- how decisions are made
- how tradeoffs are surfaced
- how assumptions are challenged
- how customer outcomes are measured
I would also redesign role expectations. The next era needs leaders who can go deep, think across domains, and move teams through ambiguity without pretending certainty.
Most of all, I would treat skill evolution as core infrastructure, not a side initiative.
Questions I Am Still Sitting With
If you are leading in this environment, these are the questions I think are worth carrying into your next strategy conversation:
- Which skills are we saying we value but not actually rewarding?
- Where are we still optimizing for predictability in places that now require adaptability?
- What assumptions are we protecting because they worked in the last era?
- Which strengths on our team become drag if we do not evolve them now?
I do not think we need perfect answers yet. I do think we need honest ones.
That feels like the real starting point for the next era.