In this guide
Give the team usable conditions
  1. 01Set purpose and boundaries
  2. 02Provide knowledge and capacity
  3. 03Review the learning
  4. 04Resolve the next commitment
A practical leadership inquiry, not a personality test or a promise of innovation success.

Leading innovation means creating conditions in which people can investigate worthwhile possibilities and remain accountable for what they learn and commit. Give a team a clear problem, usable boundaries, access to relevant knowledge and a decision process that can respond to inconvenient evidence.

A motivational speech cannot settle who can approve a customer trial or free an engineer from current work. Start with those practical conditions. Innovation management provides the wider system; this guide focuses on the manager’s day-to-day contribution.

What the research helps you notice

Amabile’s componential theory of creativity connects expertise, creativity-related processes and task motivation with the social environment. It is a framework for understanding creative work, rather than a test for identifying a fixed creative personality. A person’s contribution depends partly on the work they can access and the conditions around it.

The Center for Creative Leadership’s account of innovation roles also distinguishes leadership responsibilities at different levels. A supervisor may clear obstacles for a local test; an executive may need to change resource allocation across units. The source is practical guidance, not independent proof that a particular leadership routine improves commercial results.

Treat these ideas as prompts for inquiry. Ask what the team can decide, what it must ask permission for, which expertise it lacks and what happens when a result contradicts a sponsor’s preference. Those questions are more actionable than telling people to adopt an innovative mindset.

Define the boundaries before asking for ideas

In a hypothetical lighting workshop, a manager wants a table lamp that customers can repair more easily. The designers interpret the request as a new enclosure; the service technician thinks the connector is the main obstacle. The purchasing colleague knows that replacement parts are ordered in quantities unsuitable for occasional repairs.

Two colleagues discuss the open base and wiring of an unplugged lamp prototype.
Figure 1. Define the boundaries before asking for ideas.Illustration credits

A useful brief names the intended user benefit and leaves room to question the solution. It could ask the team to investigate how someone can replace the component that commonly needs attention, while preserving the product’s required safety and quality conditions. The team would need appropriate technical review before making or testing any actual electrical change.

Separate non-negotiable conditions from assumptions. A required product standard is a constraint. A preferred supplier may be a negotiable commercial choice. A manager’s belief that customers want a different casing is a hypothesis. If all three appear as mandatory requirements, the team has little genuine room to investigate.

Write a short working agreement:

FieldWhat to agree
PurposeThe problem the work should help someone resolve
FreedomDecisions the team may make without escalation
BoundaryConditions requiring specialist or sponsor approval
CapacityNamed people and the work being displaced
EvidenceWhat the next review needs to learn
DecisionWho can continue, change or stop the commitment

This is an original management aid, not a validated leadership instrument. If the assignment itself remains contested, use change contracting before commissioning another workshop.

Make relevant knowledge available

Involve people who know how the work happens. For the fictional lamp, that includes repair staff, assembly workers and users with different practical abilities. Inviting them only to approve a finished concept turns participation into a late checkpoint.

Ask contributors to bring concrete incidents or objects. A technician can show a difficult connection. An assembler can demonstrate the order in which parts are fitted. A customer can describe a recent repair attempt. These contributions may disagree; the manager’s job includes giving the team time to examine that disagreement.

Use customer interviews for accounts of real situations and observation for the work itself. Keep preferences separate from demonstrated behaviour. Someone saying that a product should be repairable does not establish that they will buy spare parts or perform a repair.

Access also includes practical support. If the test requires a service technician, arrange that person’s time rather than relying on goodwill. Record the consequence for their ordinary workload. Where commitments repeatedly collide, consider whether the wider organization needs a different ambidexterity arrangement.

Review the learning and the working conditions

An early review should examine the question, the evidence and the conditions of the test. Ask the team to show what it attempted, what it observed and what remains uncertain. Avoid asking only whether the result supports the original proposal.

Two people examine an unplugged lamp and replacement components at a repair bench.
Figure 2. Review the learning and the working conditions.Illustration credits

The Institute for Healthcare Improvement’s testing guidance uses prediction, observation and adaptation within local PDSA cycles. Applied cautiously outside healthcare, this suggests a useful discipline: specify what the next bounded attempt is meant to teach before running it. It does not make a lamp trial a controlled experiment or justify general conclusions from a few attempts.

In the fictional workshop, one review might concern whether a technician can identify the replacement component from the proposed instructions. A later review might concern assembly time or spare-part access. These are different questions and may require different participants and evidence.

Also review the environment. Did the team obtain the promised technical advice? Was a customer session cancelled because the necessary prototype was unavailable? Did someone conceal a problem because the presentation had already been announced? These observations can explain why the evidence is weak without attributing failure to a person’s attitude.

Respond usefully to inconvenient information

Edmondson’s research on psychological safety and learning behaviour concerns the interpersonal conditions for taking risks such as asking questions or reporting mistakes. It does not mean removing performance expectations. A manager can require careful work while making it possible to discuss an error early.

When a team brings a disappointing result, first establish what happened. Ask which assumption changed and what decision follows. Acknowledge a careful investigation even if the idea stops; recognition should describe the useful contribution rather than imply that every experiment succeeds.

Do not infer intent from one difficult meeting. Use a specific feedback conversation when someone dismisses a concern or withholds a needed decision. Clarify the observed behaviour and its effect, then ask about the circumstances. The same standard applies to the sponsor as to the team.

Watch the incentives you create

Counting suggestions can encourage a growing collection without useful follow-up. Celebrating launches alone can make a justified stop look like failure. Requiring every concept to promise immediate savings can exclude questions whose value lies in reducing uncertainty.

Choose measures that fit the responsibility. A local team might track whether commitments receive an answer and whether tests address their stated questions. An executive might review competing demands on shared specialists. Neither measure alone establishes innovation success. The idea management guide explains how to connect suggestions with decisions and feedback.

Keep reward discussions grounded in the local work. No single incentive system suits every problem, and the conceptual sources here do not establish an optimal bonus formula. If a measurement becomes a target, periodically inspect what behaviour it is encouraging and what contribution it is missing.

Limits and a practical next move

Leadership is one part of an innovation system. Supplier constraints, technical feasibility, market demand and organizational authority can limit a well-supported team. These sources do not justify promises that a particular leadership style will produce successful products. The lighting-workshop narrative is hypothetical and contains no reported trial result.

For the next project, take the working agreement to the people doing the work. Ask them to identify one decision they cannot currently make, one dependency they cannot obtain and one assumption they need permission to question. Resolve those items before asking for a more ambitious idea.

Sources: