An employee notices something.

Customers keep asking the same unexpected question. A service designed for one purpose is being used in another way. A routine process contains a step that no longer appears necessary.

The employee senses that the observation matters, but they do not yet know what the solution should be.

They raise it during a meeting.

“What exactly are you proposing?” somebody asks.

The employee tries to explain, but the idea is still forming. There is no budget, implementation plan or evidence that changing the process will produce a commercial return.

The conversation moves on.

Several months later, a competitor introduces a service built around the same emerging need.

Only then does the organisation understand what the employee had begun to see.

The idea was not wrong.

It arrived before the organisation had developed the patience to understand it.

Organisations often confuse polish with potential

A polished proposal is easier to evaluate.

It contains a clear problem, a defined audience, supporting evidence, expected costs and an explanation of what should happen next. Decision-makers can compare it with existing priorities and judge whether the organisation should invest.

An unfinished idea provides less certainty.

It may begin with language such as:

“I keep noticing…”

“What if we looked at this differently?”

“I cannot fully explain it yet, but…”

“Customers appear to be doing something we did not expect.”

“These two problems may be connected.”

“There might be another use for this.”

These statements can sound vague. In some cases, they are vague. Not every observation contains a valuable opportunity.

But demanding that every early idea arrive in the form of a finished business case creates a deeper problem. It favours people with the time, confidence, language and organisational status to package their thinking persuasively.

The organisation may begin selecting presentation ability rather than insight.

A polished weak idea can appear more credible than a significant observation expressed without confidence.

Important ideas often begin as slow hunches

The popular image of creativity is the sudden breakthrough.

A person experiences a moment of inspiration and sees the complete answer. The idea arrives quickly, clearly and with enough force to overcome resistance.

These moments do occur. They are not the only way ideas develop.

Many ideas begin as what writer Steven Johnson describes as a “slow hunch”: an incomplete sense that something may be important. The person notices a pattern but does not yet possess the information required to explain it fully.

The hunch may remain inactive until it encounters another observation, conversation or piece of research. Two people may each possess part of the answer. A problem noticed in one department may connect with a capability being developed elsewhere.

What appears to be an individual breakthrough may therefore be the visible moment in a much longer process.

This changes how organisations should think about creativity.

If good ideas sometimes develop slowly, businesses need ways to retain observations before their value becomes obvious.

Ideas need somewhere to wait

Most organisations have systems for recording decisions, projects, finances and customer transactions.

Far fewer have a dependable way to preserve incomplete ideas.

An employee mentions something during a meeting. Another person writes it in their private notebook. A manager promises to return to it later. The team becomes busy, and the observation disappears.

The problem is not necessarily a lack of interest. The organisation has no memory designed for possibility.

A simple idea record could capture:

The original observation.

The problem or opportunity it may relate to.

Who noticed it and in what context.

What remains unknown.

Other ideas or projects that may connect with it.

The conditions that would make investigation worthwhile.

A date for review.

This does not require every suggestion to enter a complicated innovation database. Small organisations might maintain a shared document or devote part of a regular strategy meeting to revisiting unresolved observations.

The purpose is not to create an archive that nobody uses.

It is to prevent potentially valuable knowledge from disappearing simply because its importance was not immediately measurable.

An observation is not yet a solution

There is another reason to allow ideas to remain unfinished.

People often move too quickly from noticing a problem to defending their first solution.

A customer struggles with a booking process, so the organisation decides it needs a new website. Participation in an event declines, so the team assumes that more marketing is required. Employees fail to use a new system, so management schedules additional training.

Each response may be reasonable.

Each may also address the wrong problem.

The booking difficulty might result from unclear service choices rather than technology. Event participation might have declined because timing or transport changed. Employees may avoid the new system because it creates duplicated work.

When an observation is immediately attached to a preferred solution, investigation becomes an attempt to justify that solution.

Keeping the idea unfinished for slightly longer allows the organisation to ask better questions:

What exactly are we observing?

How often does it occur?

Who experiences it?

What might explain it?

Which assumption are we making?

What evidence would change our interpretation?

Are we seeing a symptom or the underlying problem?

The goal is not endless analysis.

It is to avoid becoming efficient at solving something that was never the real issue.

Conversation develops ideas

An unfinished idea may need another person before it can become useful.

One employee understands the customer problem. Another knows the operational constraint. A third has seen a similar pattern in a different sector. None possesses the complete answer independently.

The organisation’s role is to create encounters between these different forms of knowledge.

This is more than inviting several people to a brainstorming session.

Useful creative conversation allows contributors to explore the idea before positions harden. People can add information, question assumptions and recognise connections without treating the discussion as a competition for whose proposal will win.

A conversation might begin with:

“What does this observation make you think about?”

Rather than:

“Is this a good idea?”

The first question invites development. The second demands a verdict.

Verdicts are necessary eventually. They are often destructive when delivered too early.

Premature criticism can make ideas smaller

Critical thinking is essential to innovation.

Businesses must examine feasibility, cost, risk, relevance and unintended consequences. An idea that cannot survive serious examination should not receive investment simply because it is imaginative.

Timing matters.

When an idea is still emerging, immediate criticism can force it to answer questions it is not yet mature enough to address. The discussion becomes dominated by current constraints before the possibility has been understood.

Someone proposes a different service model.

The first responses are:

“We do not have the staff.”
“Our customers would never accept that.”
“That is not how the sector works.”
“Where would the money come from?”

These may become important questions. But if they appear before the underlying possibility has been explored, the organisation may reject the idea without understanding what it contains.

A more useful sequence separates development from evaluation.

First ask:

What is the underlying insight?

Which need might this address?

What becomes possible if the assumption is correct?

Is there a smaller version worth exploring?

Then ask:

What evidence supports it?

What could make it fail?

What would implementation require?

Is it strategically relevant?

Can we test it proportionately?

This sequence does not protect ideas from criticism.

It ensures that the organisation criticises the idea that has actually been proposed, rather than its weakest first expression.

Language and status influence which ideas survive

Ideas are not evaluated in isolation. They are affected by who presents them and how.

A confident senior employee may describe an early thought as a strategic opportunity. A junior colleague may present the same insight hesitantly and describe it as “just an idea.”

The first contribution is likely to receive more attention.

Professional language can help explain an idea, but it can also disguise bias. Organisations may mistake fluency, confidence and familiarity with management vocabulary for intelligence.

This creates cultural and commercial consequences.

People from different professional, educational or cultural backgrounds may frame ideas differently. Some will communicate directly. Others may begin with context, story or lived experience. A person speaking in their additional language may see something clearly without expressing it in the style the organisation normally rewards.

Leaders need to listen for the insight beneath the performance.

They can ask clarifying questions without taking ownership away from the contributor. They can help develop the idea while keeping its origin visible.

Otherwise, organisations may repeatedly overlook ideas until somebody with more status learns how to present them.

Protect the contributor as well as the idea

Sharing an unfinished idea creates vulnerability.

The contributor reveals thinking that may contain gaps. They risk misunderstanding, dismissal or embarrassment. If the organisation responds carelessly, they may decide to bring only safe, conventional proposals in the future.

This does not mean that people should receive praise for every suggestion.

A respectful response might be:

“There is something worth examining here, but we need more information.”

Or:

“I do not think the proposed solution is practical, but the underlying observation is important.”

Even when the organisation decides not to proceed, it can acknowledge what was contributed and explain the decision.

Credit also matters when the idea develops through collaboration.

An early observation may be refined by several people and eventually presented by a senior leader. The organisation should avoid rewriting the history of the idea so that only the final presenter appears responsible.

Recognition communicates that contributing knowledge is worthwhile.

Not every idea deserves development

Respecting unfinished ideas does not require organisations to investigate everything.

Time, attention and money are limited. Pursuing too many possibilities can fragment strategy and prevent the organisation from delivering its existing commitments.

The challenge is to decide which ideas deserve further attention before demanding a complete business case.

Useful early criteria might include:

Relevance

Does the observation connect with the organisation’s purpose, customers or strategic priorities?

Importance

Does it concern a significant need, risk or opportunity?

Evidence

Is the idea based on something observed, or only on a general assumption?

Distinctiveness

Could it lead to a meaningfully different response, or does it reproduce an existing approach?

Testability

Can the central assumption be investigated without major commitment?

Cultural implications

Who may benefit, participate or be excluded? What history, identity or community knowledge matters?

Timing

Is this the right moment to explore the idea, or should it be recorded for later?

These criteria help an organisation distinguish between an idea that is incomplete and one that is disconnected from its work.

Small experiments give ideas definition

An unfinished idea does not need to remain abstract indefinitely.

A small experiment can help it acquire shape.

Suppose a cultural organisation notices that people are attending events but not returning. The initial idea might be to create a membership programme.

Before building the programme, the organisation could investigate the assumption that visitors want a continuing relationship. It might interview a small group, test a follow-up invitation or offer one limited returning-visitor activity.

The experiment could reveal that the problem is not membership. Visitors may want more accessible scheduling, clearer information or opportunities to participate rather than simply attend.

The original idea has changed.

That is not failure. It is development.

A prototype should not merely demonstrate that the creator’s idea works. It should create an opportunity to discover why it might not.

Technology can produce more ideas than an organisation can understand

Generative AI has made idea production faster.

A team can request dozens of product concepts, campaign directions or strategic possibilities within minutes. This can be useful when the organisation needs a broad starting field.

But abundance creates a new problem.

When ideas are easy to generate, attention becomes more valuable than production.

An organisation still needs to determine which possibilities are culturally relevant, commercially credible and connected to a real need. It must distinguish between an idea that sounds persuasive and one grounded in the organisation’s circumstances.

AI can also encourage premature polish. A weak thought can be transformed into fluent language, complete with a name, target audience and implementation plan. The presentation may look finished before the underlying idea has been examined.

Fluency is not evidence.

Businesses should remain willing to ask what observation produced the idea, whose experience informed it and what would need to be true for it to create value.

Knowing when an idea is ready

An idea cannot remain unfinished forever.

At some point, the organisation needs to decide whether to invest, test further, postpone or stop.

An idea may be ready for a more formal decision when:

The underlying problem is clearly described.

The people affected have been identified.

Important cultural and operational conditions are understood.

The central assumptions are visible.

Some relevant evidence has been gathered.

The organisation knows what the next commitment would involve.

The remaining uncertainty is proportionate to the decision.

Readiness does not mean certainty.

It means that the organisation understands enough to take the next responsible step.

The discipline to recognise potential

Organisations need polished proposals. They also need the ability to recognise what might eventually become one.

That ability depends on patience, memory and conversation. It requires leaders who can hear an incomplete idea without either approving it uncritically or dismissing it prematurely.

The person who notices something important may not yet understand everything they have noticed.

They may need research. They may need another person’s knowledge. They may need a small test that reveals why the first solution was wrong but the original observation was valuable.

The best ideas do not always enter the organisation with a presentation and a plan.

Sometimes they arrive quietly—as a question, an irritation or a connection that nobody else has made.

Their unfinished state is not proof that they lack value.

It may simply mean that the work of understanding them has only just begun.