Home → Leadership
New-Generation Leadership: Authority Is Gone, Now What?
There was a time when "because I want it this way" silenced a room. Now somebody raises a hand and says "why?". The good news: that question is the most valuable gift your team gives you.
- The two foundations of the title eroded: the information monopoly and dependence. Both are gone.
- What replaced them is context. Not what to do, but which problem we are solving and why.
- Saying "I do not know" does not reduce authority, it increases trust. One of the most counter-intuitive findings.
- Three things did not change: fairness, clarity, keeping your word. The rest is style.
What actually changed?
This topic usually turns into a generational argument — "kids these days". I think it is not about generations but about a shift in the balance of power. Four concrete things changed:
1. The information monopoly ended
The manager used to be the person in the room who knew most, because information accumulated upward. Today everyone on the team reads the same docs, the same forums, the same AI tools. Yesterday's junior can form a reasonable opinion within an hour on something that took you three years.
This does not mean your knowledge is worthless. It means knowledge can no longer be the source of authority.
2. Dependence ended
A good engineer knows what they are worth. Someone who knows that works because they are convinced, not because they obey. "It will be this way because I said so" no longer ends the argument; it just moves the argument somewhere you cannot hear it.
3. Visibility ended
With remote and hybrid work, "are they at their desk?" became meaningless. One measure is left: what shipped. That is uncomfortable for some managers, because it exposed the difference between managing and watching.
4. The ladder flattened
Careers used to point one way: up. Now people move sideways — switching domains, specialising, deliberately not wanting to manage. "I will make you a manager" is no longer a carrot that works everywhere.
What replaced authority?
Three things. And all three are re-earned every day; none of them is banked once.
Your biggest contribution is seeing the picture the team cannot. Why this work, why now, what constraints exist, what is not negotiable. A leader who shares that gets decisions close to their own even in situations where they are not present.
What the team usually wants from you is not direction but the road being cleared: the answer that never came from another team, the test environment broken for two weeks, the licence that was not approved. A leader who solves those earns respect without issuing a single instruction.
A wrong decision does less damage than indecision. A team can correct a wrong decision; in indecision it can only wait. And when a decision turns out badly, saying "I made that call" instead of "I told you so" is a leadership test on its own.
Order versus context: a concrete example
"Write the notification service with a Redis queue, due Thursday."
Result: exactly that gets built. When it turns out Redis is not persistent in that environment, nobody flags it, because nobody knows why a queue was wanted.
"Here is the problem: notifications are lost at peak hours and it is costing us customer trust. There is a demo on Thursday and it has to work without loss by then. We have Redis in the stack, not RabbitMQ, and we cannot buy anything this week. How you solve it is up to you."
Result: the team notices the persistence setting and either fixes it or proposes an alternative. Either way, you hear about it first.
The difference is not that the second version is politer. The difference is that it forces the team to think. In the first version the only person thinking is you, and that is exactly where you stop scaling.
The power of "I do not know"
In my first year as a manager I tried to talk about something I did not understand in a meeting. The most senior person on the team corrected me politely. On the way home I realised: everyone in that room already knew I did not understand. Only I was performing.
The next time I said "I do not know this, let me look and come back". I expected to lose standing. What happened instead was that two other people said what they did not know either. The cost of asking a question dropped in that team that day.
What the new generation actually wants (not the clichés)
"They want flexibility and meaning" is true but too general. Three more concrete things show up in the field:
| What is said | What is actually wanted | What to do |
|---|---|---|
| "Flexibility" | Predictability. Plans not changing without warning. No "needed by Monday" arriving on Friday evening. | Announce priority changes with reasons, and in time |
| "Meaning" | Visible impact. Knowing who benefits from what they built. | Put them in touch with users; let them run the demo |
| "Growth" | Fast feedback. Knowing where they stand without waiting for December. | 20 minutes a month, concrete and event-based |
So does everyone decide everything now?
No, and this is the most common trap. Letting go of authority is not creating a vacuum. Leave a vacuum and the loudest person fills it, and what you get is not the absence of leadership but unelected leadership.
The simple split I use:
- Reversible decisions: the team decides and learns from the outcome. Library choice, folder structure, order of work within a sprint.
- Irreversible decisions: you decide, but you explain your reasoning. Data model, external API contract, hiring, architectural direction.
Managers who do not make this split either get involved in everything or in nothing. Both exhaust the team.
Three things that did not change
Amid all this change, what stayed the same? Three things:
- Fairness. The same behaviour getting different responses depending on the person is where a team dies.
- Clarity. People are worn down by ambiguity, not by bad news.
- Keeping your word. Saying "I will look into it" and not looking is the most repeated and most expensive leadership mistake.
These three were the same fifty years ago and they are the same now. Only the way you demonstrate them has changed.
Checklist
- When I assigned work this week, did I explain the why?
- Was there a moment I said "I do not know" in front of the team?
- Did I actually look into the thing I said I would look into last week?
- How many obstacles did I remove versus how many instructions I gave?
- Did I make a reversible decision that the team should have made?
- If priorities changed, did the team hear it from me or from someone else?
- Did I respond differently to the same behaviour from two different people?
Conclusion
Authority did not end; it stopped being free. It used to come with the title, now it is earned through behaviour and re-measured every sprint.
And back to that "why?": the team asking it is not a team questioning you. The team that does not question you has already given up.