The Effective Executive poses a question Peter Drucker says most managers never ask: "What can I contribute?"
The Effective Executive poses a question Peter Drucker says most managers never ask: "What can I contribute?"
The Effective Executive poses a question Peter Drucker says most managers never ask: "What can I contribute?"
π΅ππ ππππ ππ π° πππππππππππ πππ. π΅ππ ππππ π πππ ππ ππππ πππππππ. πΎπππ π π π° ππππππππ ππππππππππ ππππ πππππ ππ πππππππ ππ π° ππππ πππ ππππ.
When I started leading engineering teams, my contribution was mainly technical. I could read the architecture, spot the flaw, make the call. That credibility mattered. It shaped how the team received decisions.
Then scope grew. More teams, more systems, more business problems to connect to engineering decisions. The contribution question shifted. Less about reading the code. More about reading the situation β the organisational constraint, the risk no one had named yet, the tradeoff buried inside a delivery commitment.
That shift happens to every engineering leader at some point. The moment your value stops being what you can build and starts being what you can see that others cannot yet.
AI is accelerating that reckoning for a lot of people right now. When execution becomes faster and more automated, the residual value of an engineering leader becomes more visible β and more exposed. Judgment applied where no tool has the context to apply it yet. Institutional knowledge. The architectural decision from three years ago that nobody documented but everybody is now building on.
Drucker's question is more useful in 2026 than it was in 1967. Not because it changed β because the answer has fewer places to hide.
β ππ΅ πΈπ©π’π΅ π±π°πͺπ―π΅ πͺπ― πΊπ°πΆπ³ π€π’π³π¦π¦π³ π₯πͺπ₯ πΊπ°πΆπ³ π€π°π―π΅π³πͺπ£πΆπ΅πͺπ°π― π΄π©πͺπ§π΅ β π’π―π₯ π₯πͺπ₯ πΊπ°πΆ π―π°π΅πͺπ€π¦ πͺπ΅ πΈπ©π¦π― πͺπ΅ π©π’π±π±π¦π―π¦π₯?