Real Innovation Begins When We Stop Being Afraid to Think Differently
Why meaningful innovation requires curiosity, unconventional people, simplicity and the courage to challenge established thinking.
Most organisations claim to value innovation.
It's written into their strategies, included in their corporate values and regularly discussed by leadership teams. Businesses invest in innovation programmes, workshops, frameworks and initiatives designed to encourage employees to think differently.
Yet I believe there is a fundamental contradiction at the heart of much of this activity.
Organisations say they want different thinking, but their systems often reward people for thinking and behaving in familiar ways.
They encourage employees to challenge established practices, then ask them to demonstrate how their ideas align with existing processes. They want original solutions, but prefer predictable outcomes. They celebrate creativity while surrounding it with approval structures that favour the conventional.
This raises an important question.
Can an organisation genuinely innovate if it is unwilling to challenge the assumptions on which it already operates?
I don't believe it can.
Not in any meaningful or sustained way.
Innovation requires more than generating ideas. It requires the willingness to question what we believe, understand problems from different perspectives and occasionally abandon approaches that have become so familiar we no longer consider whether they are right.
And I believe the process of achieving this could be considerably simpler than many organisations make it.
Innovation Is Not a Workshop
If I were responsible for improving innovation within an organisation, the first thing I would do is stop treating it as an event.
I wouldn't begin with a large conference room, a professional facilitator or an elaborate programme of activities.
I wouldn't ask fifty employees to spend an afternoon writing ideas on coloured notes.
And I certainly wouldn't measure success by the number of suggestions generated.
Instead, I would start with a conversation.
Perhaps in the office canteen.
Perhaps around a table in a small meeting room.
I'd invite a handful of people who actually perform the work we're trying to improve.
Not necessarily their managers.
Not exclusively senior employees.
And certainly not only those with impressive job titles.
I'd invite people who understand the practical reality of what happens every day.
Then I'd ask them to explain it to me.
What works?
What doesn't?
What frustrates you?
What takes longer than it should?
What would you change if you had the freedom to do so?
And perhaps most importantly:
What are we doing simply because that's how we've always done it?
I would listen before suggesting solutions.
I would ask questions before making assumptions.
And I would resist the temptation to turn the conversation immediately into a formal improvement programme.
Because before we can improve something, we need to understand it.
Go Where the Work Happens
One of the most important principles of effective improvement is understanding reality rather than relying entirely on reports about reality.
There is a reason the Japanese concept of genchi genbutsu, commonly associated with the Toyota Production System, emphasises going to the actual place to understand a situation.
A process diagram can tell us how something is supposed to work.
A management report can tell us how that process is performing against selected measures.
But neither necessarily tells us what people experience while carrying it out.
The employee performing the work may know about informal workarounds, unnecessary approvals, duplicated effort or systems that create more problems than they solve.
These details can be invisible to senior management.
I think there is something valuable in the underlying idea of programmes such as Undercover Boss, even if the television format is designed for entertainment.
The principle is simple: leaders need to understand the reality experienced by the people doing the work.
But I would go further.
Why should understanding frontline work be a special event?
Why should a senior leader need to disguise themselves to discover what employees experience?
Shouldn't that understanding be part of how an organisation operates?
If I wanted to improve a customer service process, I would spend time with the people handling customer enquiries.
If I wanted to improve a software development process, I would speak directly with developers, testers and support teams.
If I wanted to understand why a business process takes six weeks, I would follow an actual request from beginning to end.
I would want to see where it waits, where it gets duplicated, where decisions are delayed and where people have created workarounds.
Not because management has nothing useful to contribute, but because the people closest to a problem often possess knowledge that isn't visible from above.
And that knowledge should be the starting point for improvement.
The Courage to Be Different
In his book Purple Cow, Seth Godin explores the importance of being remarkable.
The central idea is that simply being good, competent or similar to competitors may not be enough to attract attention in a crowded market.
A remarkable product or service gives people something worth noticing and discussing.
Marty Neumeier explores a related idea in Zag: when competitors converge on similar approaches, meaningful differentiation can come from choosing a different direction.
I find both ideas compelling.
But I think they reveal a wider problem within corporate innovation.
Many organisations want the benefits of being different without accepting the discomfort of doing something different.
They study competitors.
They benchmark their processes.
They adopt recognised practices.
They examine industry standards.
They seek reassurance that their decisions are consistent with what other organisations are doing.
None of these activities is inherently wrong.
Learning from others is sensible.
Understanding established practice can prevent expensive mistakes.
But when benchmarking becomes imitation, organisations risk eliminating the very differences that might make them exceptional.
If every company studies the same competitors, employs people with similar backgrounds, follows the same frameworks and reaches decisions through similar approval structures, why should we expect radically different outcomes?
Perhaps the most valuable question isn't always:
What are other companies doing?
Perhaps sometimes it should be:
What is everybody else doing that we could deliberately choose not to do?
That doesn't mean being different for the sake of it.
Difference alone isn't innovation.
A new approach must still create value.
But originality becomes difficult when conformity is treated as the safest measure of good judgement.
The People Who Don't Fit the Mould
I believe one of the greatest opportunities for innovation lies in the diversity of people involved.
Not simply diversity of professional background, although that matters.
I'm talking about diversity of thought, personality, experience, temperament and perspective.
I would want analytical people.
Creative people.
Practical people.
Quiet people.
Outspoken people.
People who question everything.
People who notice small details.
People who see patterns.
People who prefer structure.
People who dislike structure.
Neurodivergent people whose ways of processing information may differ from those around them.
People with decades of experience.
And people who are new enough to ask questions that everyone else has stopped asking.
I would want the unconventional thinker alongside the cautious realist.
The imaginative person who proposes something unexpected alongside the person who can explain exactly why it might fail.
The individual who sees the entire system alongside the person who notices one small defect that everybody else has overlooked.
Because innovation isn't necessarily produced by surrounding ourselves with people who agree.
It often emerges when different perspectives challenge one another.
Of course, disagreement alone doesn't guarantee better ideas.
And being unconventional doesn't automatically make someone innovative.
The important thing is creating an environment in which different perspectives can contribute meaningfully.
That requires more than inviting different personalities into a room.
It requires ensuring they can be heard.
A quiet employee with an excellent idea should not be overlooked because someone more confident dominates the discussion.
An unconventional suggestion should not be dismissed simply because it sounds unfamiliar.
And disagreement should not automatically be interpreted as negativity.
The objective isn't to create conflict. It's to create constructive intellectual friction.
A group that agrees on everything may be comfortable.
But comfort isn't necessarily the environment in which the best ideas emerge.
The Value of Small Things
Innovation is often associated with major breakthroughs.
Entirely new products.
Revolutionary technologies.
Disruptive business models.
But I think this focus can cause organisations to overlook something equally important.
Small improvements.
Stephen Bartlett frequently explores the significance of behaviour, psychology, experience and details in business. The broader principle I take from this is that seemingly minor elements of an experience can have a disproportionate effect on how people feel and behave.
Consider a customer using an online service.
Perhaps the service itself is excellent.
But the customer has to enter the same information three times.
Perhaps the instructions are confusing.
Perhaps a confirmation email never arrives.
Perhaps resolving a simple issue requires contacting several departments.
Individually, these might appear to be minor inconveniences.
Collectively, they can define the entire experience.
The same principle applies internally.
A form that takes five minutes longer than necessary may not seem important.
But if hundreds of employees complete it repeatedly, that friction accumulates.
A confusing process might generate unnecessary questions, delays and errors.
An extra approval may add little value while creating days of waiting.
These are opportunities for innovation.
Not necessarily spectacular innovation.
But valuable innovation.
And that brings me to a principle I particularly admire.
Kaizen: Improvement as a Habit
Kaizen is commonly understood as continuous improvement and is a central principle associated with Toyota's production system.
Its emphasis is on making ongoing improvements to quality, efficiency and performance, often through relatively small changes informed by the people doing the work.
I find this approach appealing because it removes the assumption that innovation must always be dramatic.
Sometimes the most valuable change is simply making something easier, faster, safer or more reliable.
A better layout.
A clearer instruction.
A removed approval.
A simplified interface.
A more effective handover.
Individually, these changes might appear modest.
But improvements can accumulate.
More importantly, they encourage people to think about improvement as part of their everyday responsibilities rather than something reserved for a quarterly workshop.
I would want employees to feel comfortable identifying problems and suggesting improvements whenever they encounter them.
Not through an elaborate submission process.
Not by completing a lengthy business case for every small adjustment.
But through a straightforward mechanism that allows sensible ideas to be considered and, where appropriate, tested.
The crucial part is what happens next.
An idea that disappears into an approval process is unlikely to encourage further participation.
An idea that is tested, evaluated and acted upon demonstrates that improvement is genuinely valued.
And even when an idea doesn't work, the organisation can learn something.
Innovation should be something an organisation does, not something it periodically announces.
Simplicity Is an Advantage
I have always been drawn to simplicity.
Not because complex problems are unimportant, but because complexity should serve a purpose.
A well-designed solution often hides considerable thought and effort behind an experience that feels straightforward.
Steve Jobs understood this distinction.
His approach to design was not simply about making products visually attractive. It involved considering how products worked, how people interacted with them and how the different elements of the experience fitted together.
That is an important lesson.
Excellent design is not just appearance.
It's functionality.
It's usability.
It's the removal of unnecessary friction.
And it's the experience created when those elements work together.
Apple also demonstrated the commercial potential of creating an integrated experience rather than treating products as isolated collections of features.
People can develop relationships with brands because of what those brands enable them to do and how using their products feels.
That doesn't mean excellent design automatically sells itself. Distribution, pricing, marketing and competition still matter.
But genuinely thoughtful design can give customers a compelling reason to choose one product over another.
I believe the same philosophy should apply to internal business processes.
If a process requires a thirty-page guide to explain a routine task, perhaps the process itself needs reconsidering.
If employees regularly make mistakes, perhaps we should examine the design of the system before assuming the employees are the problem.
If customers repeatedly ask the same questions, perhaps the information isn't as clear as we think it is.
Simplicity should not mean removing necessary controls or ignoring complexity.
It should mean refusing to add complexity without a good reason.
The best solution isn't necessarily the one with the most features, steps or sophistication. It's the one that solves the problem most effectively.
Why Organisations Struggle to Change
I think this is where the central challenge lies.
Organisations often have plenty of intelligent people.
They have access to technology.
They have ideas.
They have experience.
They have resources.
Yet meaningful innovation can still be difficult.
Why?
Because innovation introduces uncertainty.
Established processes offer predictability.
Familiar approaches feel safer.
Recognised best practices provide reassurance.
And managers are often held accountable for delivering results within defined budgets, deadlines and risk tolerances.
Under those conditions, choosing an unfamiliar approach can feel personally risky.
Even when it might produce a better outcome.
This is not necessarily evidence of incompetence.
It's often a rational response to the incentives within an organisation.
If managers are rewarded for avoiding failure but receive little recognition for thoughtful experimentation, caution becomes understandable.
If unsuccessful ideas damage careers, people will naturally become reluctant to propose them.
If challenging established decisions is interpreted as disloyalty, employees will learn to remain silent.
And if every proposed improvement must demonstrate certainty before it can be tested, genuinely new approaches may never progress.
You cannot demand originality while punishing the uncertainty that comes with it.
This doesn't mean abandoning governance or accepting reckless decisions.
It means distinguishing between risks that genuinely threaten the business and uncertainties that can be explored safely.
A small, reversible experiment should not necessarily require the same approval process as a major operational change.
A limited pilot can provide evidence before a larger investment is made.
And an unsuccessful experiment should be judged by whether the reasoning was sound and something useful was learned, not simply by whether it succeeded.
The objective should be disciplined experimentation.
Not uncontrolled change.
How I Would Approach Innovation
If I were asked to improve innovation within an organisation, I would keep the approach deliberately straightforward.
I would begin by identifying a real problem.
Not a vague ambition to become more innovative.
A specific problem affecting customers, employees, quality, cost or performance.
Then I would spend time with the people who experience that problem.
I would observe the work, listen to their explanations and ask questions until I understood what was actually happening.
Next, I would bring together a small group of people with genuinely different perspectives.
Some would understand the existing process.
Others would bring experience from outside it.
I would encourage them to challenge assumptions and explore alternatives without immediately dismissing unfamiliar ideas.
Then we would identify a small number of promising approaches.
Not fifty suggestions that nobody has time to implement.
Perhaps two or three.
We would examine the likely benefits, costs and risks.
Where possible, we would test them on a limited scale.
We would observe what happened.
Listen to feedback.
Measure whether the change actually improved anything.
Then make a decision.
Adopt it.
Adapt it.
Or abandon it.
And repeat.
I wouldn't judge the exercise by how many people attended, how many ideas were generated or how impressive the presentation looked.
I would judge it by what changed.
Did we remove unnecessary work?
Did we improve the customer experience?
Did we reduce errors?
Did we save time?
Did we create something genuinely different or valuable?
Did we learn something that challenges our previous assumptions?
If the answer is yes, we've made progress.
If the answer is no, we need to understand why.
That, to me, is a practical approach to innovation.
Leadership Has to Make It Possible
There is one final ingredient that I believe matters more than almost anything else.
Leadership.
Not leadership as a job title.
Leadership as behaviour.
An organisation can encourage employees to think differently, but if senior managers consistently reject unfamiliar ideas, the message becomes meaningless.
Leaders need to demonstrate curiosity.
They need to ask questions without already deciding what the answers should be.
They need to acknowledge when existing approaches aren't working.
They need to be willing to hear uncomfortable truths.
And occasionally, they need to accept that someone with less seniority may understand a particular problem better than they do.
That shouldn't be threatening.
It should be useful.
A good leader doesn't need to have every answer.
But they do need to create the conditions in which better answers can emerge.
That includes giving people time, authority and support to explore improvements.
It means removing unnecessary obstacles rather than adding new ones.
And it means recognising that genuine innovation may challenge decisions made by the very people responsible for approving it.
That takes confidence.
It also takes humility.
The Difference Between Talking About Innovation and Actually Innovating
Ultimately, I believe organisations need to reconsider what they mean when they say they want innovation.
Do they want genuinely different ideas?
Or do they want familiar ideas presented in more exciting language?
Do they want employees to challenge established thinking?
Or do they want employees to reinforce decisions that have already been made?
Do they want to discover better ways of working?
Or do they want to demonstrate that an innovation initiative has taken place?
These are very different ambitions.
I don't believe innovation requires an elaborate framework.
I don't believe it needs to begin with a workshop.
And I don't believe it should be restricted to a particular department, job title or personality type.
It begins with curiosity.
With understanding.
With different perspectives.
With a willingness to question assumptions.
And with the courage to act when evidence suggests that something better is possible.
Sometimes that will produce a remarkable new product.
Sometimes it will lead an organisation in a direction its competitors haven't considered.
Sometimes it will improve a small detail that makes a customer's experience noticeably better.
And sometimes it will simply remove a process that should never have existed.
All of those outcomes have value.
But none is likely to happen consistently if organisations insist on protecting every established assumption from challenge.
Conventional thinking is not inherently wrong. Unquestioned conventional thinking is the problem.
We should retain practices because they work, not merely because they are familiar.
We should embrace new ideas because they create value, not simply because they are new.
And we should encourage people to think differently without expecting every different idea to be comfortable.
Because genuine innovation is not about demonstrating how creative an organisation claims to be.
It's about being prepared to discover that the way we've always done something may not be the best way to do it.
And then having the courage to change it.