In Brief
- Lack of initiative is rarely a motivation problem.
- People wait for instructions when the system has taught them to.
- Without a clear goal, action becomes risk — so people stay still.
- Without a learning environment, trying something new has no upside.
- The fix is structural, not motivational.
You’ve noticed it. Things only happen when you push them. Decisions wait for your input. Problems sit on desks until someone escalates them to you. The team is full of capable people, but it runs on instructions, not initiative.
Most founders try to solve this by adding motivation. New incentives. Stretch goals. A pep talk. An offsite. A book everyone reads about ownership culture.
These rarely work. The reason is that initiative isn’t a motivation problem. It’s a system problem.
What people are actually responding to
Profound Knowledge — Deming’s term for the four things every leader has to understand — starts with a hard idea. The behaviour of people in a system is mostly produced by the system, not by the people. When you change the system, the behaviour changes. When you change the people but keep the system, the behaviour comes back.
Apply that to initiative. A team that doesn’t take initiative isn’t a team of passive people. It’s a team responding rationally to the signals the system is sending them.
Watch for the signals.
When initiative gets corrected, not encouraged. Someone makes a small judgment call without asking. They get pulled aside and told “next time, check with me first.” Two of those, and they stop making judgment calls. Their thinking now is — it’s safer to ask.
When the goal isn’t clear. People can’t take initiative toward an unclear target. If the team can’t say in one sentence what success this quarter looks like, they can’t act independently — they’d be guessing in the dark. Asking permission becomes the safest behaviour because they don’t know what direction they’re meant to be heading.
When trying something new has no upside. Try something that works, and someone else gets the credit or asks you to scale it on top of your regular work. Try something that doesn’t work, and you get blamed. People notice. They stop trying things.
When there’s no learning loop. Take action, get no feedback, never know if it was right or wrong. Why act again? Initiative requires that what you did mattered to someone. If your manager never tells you, you assume it didn’t.
Any one of these would slow initiative down. All four together produce the team you’re working with now.
Clear goal first
In my PhD research with 19 Australian founders, the leaders whose teams ran on initiative had one thing in common — a clear shared goal that everyone could repeat without prompting.
Not a vision statement. A specific thing the business was trying to do. One founder spoke about a “Big Hairy Audacious Goal.” Another about a “Massive Transformative Purpose.” The labels matter less than what they pointed at — a destination so specific that people could make decisions about whether their action was moving toward it or away from it.
This is the Holistic Collective at work. When the purpose is shared and visible, every team member has a compass. They don’t need to ask whether something is worth doing. They can read the situation, check it against the goal, and act.
When the goal blurs into “hit targets, keep growing, look professional,” the compass disappears. Action without a compass feels reckless. So people wait.
If your team isn’t taking initiative, the first question isn’t about them. It’s about whether you’ve given them a goal worth acting toward.
Learning environment second
The second thing the high-initiative founders had was an environment where trying something and being wrong was survivable. Often, it was actively encouraged.
One founder told me his approach: “A fixable problem is not a problem. As long as it’s fixable, it’s cool.” Another, describing how he’d learned to act without permission as a child: his father’s approach was “get out of the way, and let them learn their own lesson.” Another said simply: “I think that you need to give people the opportunity to do things, and to encourage.”
This is the PDSA cycle working at the level of individuals — Plan something, Do it, Study what happened, Act on what you learned. Each cycle teaches the person something they didn’t know before. Each cycle builds the confidence to run the next one. Without the cycle, initiative is a one-way bet. With it, initiative is how people grow.
This is what I mean by innovation — not a special programme, but the everyday capacity of people to try, learn, and improve their work.
Most workplaces don’t have this. They have a culture where mistakes get evaluated rather than studied. The person feels the consequence, but the system doesn’t update. The same mistake happens to someone else six months later. Nobody learned anything. The lesson the team learned wasn’t about the work. It was about not trying.
What initiative actually looks like when it’s working
You can tell a team that runs on initiative from one that doesn’t by listening to how things get done.
In the first kind, the team member identifies a problem, decides what to do about it, does it, and then tells you what they did and what they’re watching. The conversation is informative, not consultative.
In the second kind, the team member identifies a problem, tells you about it, waits for your direction, executes your direction, and then waits to be told what comes next. The conversation is always consultative.
The difference isn’t in the people. It’s in what they’ve learned about which behaviour the system rewards.
What to do this week
You don’t need a motivation programme. You need three structural changes.
Make the goal repeatable. Can every member of your team finish this sentence — “By the end of this quarter, we need to…” — without thinking? If not, that’s the first fix. Spend a meeting making the answer clear. Test it the next week by asking three random people. If they all say the same thing, you’ve got it. If they don’t, do it again.
Pre-approve the small calls. Pick two or three categories of decisions where you’re currently the bottleneck. Tell the team: “From now on, you make these calls. Tell me afterwards.” Watch what happens. You’ll be wrong about some of them, but the team will be right about more than you’d expect.
Run a “what did we learn” review. Not a post-mortem when something fails. A regular short conversation — fortnightly, fifteen minutes — about what someone tried and what they noticed. No blame. No evaluation. Just observation. This builds the learning loop the system has been missing.
If you’d like a structured way to look at where the system is suppressing initiative across your team, the workplace diagnostic walks through it.
The team in front of you can take initiative. They already do, somewhere in their lives. The question is what your system has taught them about doing it at work.
Change what the system teaches, and the initiative shows up. Faster than you’d expect, and from people you’d written off.
For the broader picture across all seven patterns, see What 19 Australian founders taught me about workplaces people don’t leave.
