Something has worked for years. People are used to it, the results are acceptable, and nobody is complaining loudly enough to create pressure for change. Then someone asks whether it could be done better. That is where creativity can easily become a problem of its own: a new solution is not automatically better just because it is new.
Improving an existing process, product, or service takes more than coming up with an original idea. First, understand what works, where people encounter friction, and what a change might unintentionally break. Only then can you decide whether a small adjustment, a combination of approaches, or an entirely new concept makes sense.
First, find out why things are done this way
A familiar process may look outdated, but it often has reasons behind it that are not obvious at first. It may have been created for safety, cost, simplicity, accountability, or to suit the people who use it every day.
Before proposing a change, ask a few questions:
- What problem was the current solution originally designed to solve?
- Which parts of it work reliably?
- What actually slows people down or limits them?
- Which rules are essential, and which are simply habits?
- What might go wrong if the process changed too radically?
Without this step, you may remove something that looks unnecessary but is actually protecting the process from a problem.
Separate the problem from the solution
When someone says, “We need a new app,” they have already skipped an important step. Perhaps the real problem is simply that people cannot find the latest information. That may have a much simpler solution.
Try describing the problem without naming a specific tool. Instead of “We need a new system,” write something like “People waste time looking for the same information in three different places.”
The more precisely you define the problem, the more possible solutions you can consider. It may be enough to change the order of steps, remove a duplication, or improve how information is handed over.
Not every improvement needs a completely new idea
When developing a creative solution, it helps to distinguish between four basic options:
| Option | When it makes sense |
|---|---|
| Keep | When the solution works well and the problem lies elsewhere |
| Adjust | When a specific step or detail causes the problem |
| Combine | When two existing solutions address different parts of the problem |
| Replace | When the current foundation no longer serves its purpose or creates too many constraints |
This framework helps prevent “innovate” from automatically meaning “throw out the old and start from scratch.”
Talk to the people who use the solution
Someone who uses a process every day may see its problems more clearly than an outside observer. At the same time, they may be so used to the current way of doing things that they no longer notice some of its shortcomings.
So do not ask only, “What would you change?” Questions about specific behaviour are more useful:
- Which step takes up the most time?
- Where do mistakes happen most often?
- What do you have to write down or remember on top of everything else?
- Which part would you not want to lose?
- What do you do differently from the official process, and why?
That last question may reveal informal improvements people have already come up with themselves.
Limited resources can reveal the heart of the problem
When time, money, or materials are limited, you cannot solve everything at once. That forces you to identify which part of the problem matters most.
Imagine you could change only one thing. Which change would make the biggest difference? If you can answer that, you have probably come closer to the heart of the problem.
Look for inspiration outside your field
When familiar approaches do not work, it can help to look at a similar problem in a completely different setting. You do not need to copy a particular product. Look for the underlying principle.
For example:
- Nature: How does a system cope with limited resources or repeated strain?
- Another profession: How does it handle the same challenge involving sequence, checking, or communication?
- Earlier solutions: Has a useful principle disappeared simply because the technology changed?
- Art and design: How can navigation be made simpler, or unrelated elements connected?
- An extreme example: What would you do if you had half the time or budget?
This kind of transfer works best when you identify the principle first, then adapt it to your own problem.
Turn a bold idea into something testable
Sometimes a new proposal sounds too ambitious or unrealistic. The answer need not be to reject it immediately or stubbornly try to persuade everyone.
A more useful question is: What could we demonstrate on a small scale to find out whether this principle works?
For example, if you are proposing a completely new way to take orders, you do not have to redesign the entire system straight away. You could test the process with a small group to see whether it really reduces time or errors.
This turns the debate from “Is it a good idea or not?” into a question you can test.
Feedback should test the idea, not its creator
In creative work, criticism can easily become personal. If someone strongly ties their self-worth to an idea, every comment may feel like an attack.
It helps to agree in advance on how you will evaluate a proposal. For example, does it:
- solve a real problem,
- work under the available conditions,
- avoid making another important part more complicated,
- make sense to people without a lengthy explanation,
- lend itself to testing without unreasonable costs?
Then the discussion can focus on the proposal and its consequences, rather than on who came up with it.
An improvement can damage what already works
Every change comes at a cost. A new process may save time but increase errors. It may feel more modern but take longer to learn. It may suit experienced users while making things harder for newcomers.
Before introducing a change, ask:
- What will we gain?
- What might we lose?
- Who will be affected most?
- Are the benefits greater than the cost of switching?
If the answer is unclear, it may be worth testing the old and new solutions in parallel.
If a test fails, find out which hypothesis was wrong
An unsuccessful test does not automatically mean the whole idea was bad. The underlying principle may have worked, while its specific form did not. Or the test may have shown that the problem was defined incorrectly.
After a test, try to separate out:
- What did we expect?
- What actually happened?
- Which part of the proposal failed?
- Could a small change fix it?
- Or does the result challenge the whole direction?
This approach helps avoid two extremes: abandoning an idea at the first setback or endlessly patching it when it no longer makes sense.
When a completely new concept makes sense
A more radical change is worth considering when small fixes simply move the problem from one place to another. A typical warning sign is a growing number of exceptions, workarounds, and extra steps needed just to keep the original system running.
A completely new concept may be a better option when:
- the original purpose has changed substantially,
- today’s conditions are very different from those in which the solution was created,
- most of the time is spent working around the old system’s limitations,
- small adjustments no longer deliver a worthwhile result.
Even then, it is useful to identify which proven elements are worth carrying into the new solution.
A simple framework for creative improvement
When you want to improve something that already works, follow these seven steps:
- Define the problem: without deciding on the solution in advance.
- Identify what works: and why it is worth keeping.
- Find unnecessary constraints: those based on habit rather than necessity.
- Develop different kinds of solutions: keep, adjust, combine, or replace.
- Choose the smallest meaningful test: one that reveals the main risk.
- Weigh both benefits and costs: not just how new the solution is.
- Decide after testing: continue, adjust, or return to the original process.
Creative problem-solving is not a contest to produce the boldest idea. The best improvement is usually the one that solves a specific problem without unnecessarily disrupting what already works. The ability to distinguish necessary change from change for its own sake is what makes creative thinking useful in practice.
