Training days don't make innovators. Practice does

A two-day innovation or design thinking course can introduce the vocabulary, but on its own it rarely changes how people work on Monday. What builds innovators is repeated practice on real problems, with someone experienced coaching at the moment each method is used, and a short honest review after each round. If you have a training budget, spend most of it on that, not on more seats in a classroom.

The belief, stated fairly

The belief goes like this: innovation is a set of skills; skills are taught; so if we train enough people in design thinking, lean or creative problem-solving, the organisation will become more innovative. It is a reasonable belief. It is how many organisations build other competencies, it is easy to plan and report, and a good course does leave people energised and curious.

The trouble is not that training is useless. It is that training is treated as the whole answer, and its success is measured by attendance and satisfaction.

Why it fails in practice

People forget what they don't use

Most attendees go back to a full inbox and the same processes they left. There is no live problem waiting for the methods they just learned. Psychologists have known since Hermann Ebbinghaus's experiments in the 1880s that unrehearsed material fades quickly. By the time a real project arrives months later, the course is a folder of slides and a vague memory of sticky notes.

Training cases are too clean

Course exercises are designed to work. The "user" in the case study is cooperative, the problem is neatly bounded, and the session ends with a satisfying prototype. Real problems are messy: the people you need to interview are hard to reach, the data is wrong, a senior stakeholder already has a solution in mind. These are exactly the moments where judgement matters, and a classroom cannot simulate them well.

Skill comes from feedback, not exposure

Research on expert performance, notably K. Anders Ericsson and colleagues' 1993 work on deliberate practice, points the same way: people improve through repeated, effortful practice with feedback on specific weaknesses, not through exposure to content. A training day gives exposure. It rarely gives anyone the chance to run an interview, hear what they did wrong, and run another one better the next day.

The work environment wins

Even a well-trained person returns to a team where nobody else uses the methods, a manager who wants answers rather than questions, and no time set aside for the work. Jean Lave and Etienne Wenger's research on situated learning describes learning as becoming part of a community of practice; if no such community exists at work, the new skill has nowhere to live.

Success is measured at the wrong level

Training is usually judged by attendance and end-of-day feedback. Donald Kirkpatrick's well-known evaluation model distinguishes four levels: reaction, learning, behaviour and results. Most innovation training is only ever measured at the first. Whether people behave differently three months later, or whether anything changed for customers, is rarely checked.

What works instead

1. Start with a live problem

Give a small team a real problem that matters to a sponsor and can show progress in six to eight weeks. The problem is the curriculum. Every method the team learns is learned because the work needs it.

2. Teach at the point of use

Teach stakeholder interviews the day before the first interviews. Teach how might we when the team is staring at a wall of findings. Teach the paper prototype when they have an idea they are tempted to build properly. Twenty minutes of instruction, then immediate use.

3. Coach, then withdraw

An experienced guide runs the first cycle, coaches in the second, and only reviews in the third. If the guide is still running sessions by the third cycle, the team is not learning; it is being served.

4. Review every round

A thirty-minute retrospective after each stage turns experience into learning. Ask what the team did, what happened and what it would do differently. This is the feedback that a classroom cannot give.

5. Measure behaviour, not attendance

Three months on, ask: are teams writing down assumptions before spending money? Are they talking to the people affected? Are projects stopped on evidence? These are the signs that practice has taken hold.

Where training still helps

Training is not worthless. A short introduction gives a wide group a shared vocabulary, which makes it easier for practising teams to explain what they are doing. It can help leaders understand what to expect from teams using these methods, and what their own role is. And specific techniques, such as interviewing, benefit from a focused skills session before practice. The rule is order and proportion: a little training, attached to a lot of practice.

Illustrative example: a city council's service redesign

Illustrative. The organisation is invented.

A city council in Melbourne had trained over a hundred staff in design thinking across two years. When the chief executive asked which services had changed as a result, nobody could name one.

The following year the council spent the same budget differently. Three teams of five each took on one live problem: missed bin collections, a confusing parking permit form, and a backlog in community hall bookings. Each team had an experienced coach for the first six weeks. Methods were taught in short sessions the day before use. Every two weeks, each team ran a retrospective.

By the end of the year, two of the three problems had tested changes in place, and the third had been stopped after interviews showed the backlog was a staffing issue, not a design one. Four people from those teams were coaching the next round. Fewer people had been "trained"; far more had practised.

Do's and don'ts

Do

• Attach any training directly to a live piece of work.
• Teach methods in short sessions just before they are used.
• Give each team a coach who plans to step back.
• Hold a short review after every stage.
• Check, months later, whether behaviour has changed.

Don't

• Measure success by attendance or satisfaction scores.
• Send people on a course and back to a team that doesn't use the methods.
• Use clean case studies as a substitute for real problems.
• Train hundreds before you have coaches for the first few teams.
• Certify people as innovators based on a course alone.

Questions people ask

Is design thinking training worth it? A short introduction is worth it if it is followed immediately by practice on a real problem with coaching. On its own, a course tends to raise awareness without changing how people work.

How do you train employees to be more innovative? Give them a real problem, a small team, an experienced coach for the first cycle and a short review after each stage. Teach each method just before they need it. Capability grows over two or three cycles, not in a single course.

How do you know if innovation training worked? Look at behaviour three to six months later rather than at end-of-day feedback. Are teams interviewing the people affected, writing down assumptions, testing cheaply and stopping work that the evidence does not support? If not, the training has not transferred.