Why a team doesn't take initiative
- The framework is fuzzy: without knowing what you can decide, taking initiative is risky.
- Past initiatives got taken back: if the owner redoes things behind them, people stop trying.
- Mistakes are punished: then doing nothing is the safest choice.
- The direction isn't known: without knowing where the business is going, you can't tell which initiative would help.
- Nobody is named: when everyone is responsible, nobody is.
A clear framework you're free within
Autonomy doesn't oppose a framework: it depends on one. A good framework answers three questions, in writing:
- Where are we going? Strategy and goals, known to everyone. See aligning your team.
- Who owns what? One name per topic, in the job descriptions.
- What can I decide alone? The limits: an amount, a type of decision, a level of risk.
Within that frame, everyone is free. Outside it, they ask. Simple, and it changes everything.
Practices that empower
- Name an owner for every topic, process and goal.
- Set the result, not the method: say what you expect, let the person choose how.
- Let those who do the work write the methods: people apply better what they built. See documenting processes.
- Accept honest mistakes, and turn them into the rule that prevents the next one. See repeated mistakes.
- Open up suggestions: anyone can propose improving a method, approved by leadership before it applies to all.
- Recognise: the author's name on the method, results celebrated in meetings.
Follow up without micromanaging
Empowering isn't abandoning. Follow-up changes nature: you follow the result at regular intervals rather than approving every step. A weekly check-in on goals and current actions is often enough.
Trust doesn't rule out checking. A clear framework and regular follow-up are what make trust possible. Without them, you either control everything or nothing.
See also how to delegate and the 10 most common team problems.

