Innovation – a Social Process: Turning Observations into Effective Innovation

One person notices that customers regularly use a process differently from the way it was designed. Another recognises that several apparently unrelated errors have the same underlying cause. Someone connects two fields of knowledge and identifies a possibility that no one has previously considered.

None of these observations is an innovation yet. An observation must first be recognised as relevant. It has to be expressed in a way that enables others to understand it. It encounters competing interpretations, existing responsibilities and differing interests. A possible solution must be evaluated, developed, funded and tested. Finally, people, processes or technical systems must actually adopt the new approach.

Innovation as a social process therefore encompasses far more than the generation of ideas. It develops throughout the journey from an initially individual perception to a new approach that becomes effective within an organisational system.

The initial insight can only be planned to a limited extent. The path that knowledge must travel through an organisation, however, can be designed.

Innovation as a Social Process: The Idea Is Only the Beginning

Innovation in Organisations Begins Before Ideas Are Generated

Many innovation models begin with a problem that has already been identified: customers need something, a process is too slow or a product needs to be improved.

In practice, however, it is often not yet clear what the problem actually is. Exceptions may be accumulating within a business process. Employees may be developing informal workarounds. A digital system may be in formal use while essential work continues to take place in private spreadsheets. Individual complaints may appear insignificant but form a recognisable pattern when viewed together.

Before an organisation can develop a solution, someone must notice these deviations and consider them meaningful. Whether this happens depends on more than the quality of the observation. It often also depends on who raises it, how it is expressed and whether it fits existing expectations.

Consider a hypothetical situation. A customer service employee recognises that a new booking system is not failing because staff lack sufficient training. Instead, the system’s workflow contradicts the actual sequence in which customer conversations take place. When this observation is framed as “resistance to change”, the organisation will look for better training. When it is understood as evidence of a flawed process assumption, the system itself must be reviewed. The same observation can lead to entirely different interventions. The decisive factor is how the problem is framed.

Problem Framing Determines Which Solutions Appear Possible

Problems rarely arrive with a complete and objective description. They are framed. A high error rate can be interpreted as a skills problem, a quality problem, an overload problem or the consequence of contradictory requirements. Falling sales can be attributed to the product, pricing, communication or a change in the market. Each interpretation activates different knowledge and produces a different solution space.

Defining the problem too quickly therefore risks more than an incomplete analysis. An organisation may develop a persuasive solution to the wrong problem. A robust innovation process keeps alternative explanations open for long enough to test them:

• Which observations support our current description of the problem?
• Which observations do not fit?
• Who experiences the situation differently?
• Which assumptions are we already treating as facts?
• Which solution would appear plausible if we framed the problem differently?

Innovation does not always begin with an explicitly stated customer problem. It may also originate in technological possibilities, scientific findings, regulatory changes or friction within the organisation itself. Customer orientation remains important. It should not, however, become a rule of thought according to which only needs already articulated by customers represent legitimate starting points for innovation. People cannot reliably request solutions whose possibility they do not yet know exists.

Diverse Teams and Innovation: Difference Has to Be Processed

Different professional experiences and ways of thinking can expand the range of knowledge available to a team. This does not mean that a diverse team will automatically develop better solutions. Research has long described diversity both as a potential resource and as a possible source of social tension. The decisive issue is whether a team actually exchanges, examines and integrates its different knowledge. This process is known as information elaboration.

A team can contain highly varied perspectives while still working at a superficial level. This happens, for example, when:

• contributions are collected but not related to one another;
• the easiest perspective to understand is prematurely treated as the best;
• individuals are expected to translate their specialist language for everyone else without support;
• people with greater hierarchical status define the frame of interpretation at an early stage;
• conflict is avoided even though substantive contradictions remain unresolved.

Diversity is then present, but it is not converted into shared understanding.

More recent research on information resources in teams supports this distinction. Functional diversity and access to external knowledge can provide valuable information. They do not guarantee that a team will elaborate on that information and make it useful for innovation.

The relevant question is therefore: What happens to differences once the people involved begin working together?

Different Ways of Thinking Require Translation, Not Standardisation

People differ in the signals they notice, the way they structure relationships and the point at which they consider an explanation sufficiently robust. One person may think associatively and connect fields of knowledge that initially appear far apart. Another may systematically examine dependencies and inconsistencies. Someone else may quickly recognise how an idea would affect customers or operational processes.

These differences can contribute to better outcomes. They can also create difficulties in communication. The aim should therefore be neither to romanticise difference nor to make it disappear through standardised communication. Appropriate forms of translation are required.

These may include visual representations of relationships, explicit documentation of assumptions, clearly separated phases of discussion or facilitation that does more than distribute speaking time and actively establishes connections between contributions. Differentiation is particularly important when considering neurodivergent ways of thinking.

The organisational question is: To what extent does the recognition of an observation depend on whether it is presented in the expected language, sequence and social form? A precise insight should not lose its value simply because it has been expressed in an unfamiliar way. In many organisations, however, it does lose its organisational legitimacy and its ability to connect with existing structures.

Different Ways of Thinking Require Translation, Not Standardisation

People differ in the signals they notice, the way they structure relationships and the point at which they consider an explanation sufficiently robust. One person may think associatively and connect fields of knowledge that initially appear far apart. Another may systematically examine dependencies and inconsistencies. Someone else may quickly recognise how an idea would affect customers or operational processes.

These differences can contribute to better outcomes. They can also create difficulties in communication. The aim should therefore be neither to romanticise difference nor to make it disappear through standardised communication. Appropriate forms of translation are required.

These may include visual representations of relationships, explicit documentation of assumptions, clearly separated phases of discussion or facilitation that does more than distribute speaking time and actively establishes connections between contributions. Differentiation is particularly important when considering neurodivergent ways of thinking.

The organisational question is: To what extent does the recognition of an observation depend on whether it is presented in the expected language, sequence and social form?

A precise insight should not lose its value simply because it has been expressed in an unfamiliar way. In many organisations, however, it does lose its organisational legitimacy and its ability to connect with existing structures.

Idea Management in Organisations Is Also Evaluation Management

In surveys and corporate principles, organisations frequently express a desire for bold and original ideas. In actual decision-making situations, however, they often favour solutions that are familiar, predictable and easy to explain. This is not merely a contradiction between aspiration and behaviour. New ideas generate uncertainty by definition. Their costs, side effects and likelihood of success are more difficult to estimate than those of familiar approaches.

Experimental research suggests that uncertainty can encourage an implicit bias against creative ideas. People may support creativity in principle while still finding it difficult to recognise the value of a specific novel proposal. Effective idea management in organisations therefore requires more than a channel through which employees can submit suggestions. It has to distinguish between different activities:

• Recognition: Is an observation or idea recognised as potentially relevant at all?
• Evaluation: Which criteria are used to assess usefulness, novelty, risk and feasibility?
• Selection: Which ideas receive time, funding or access to an experiment?

The criteria should reflect the maturity of the idea. An early observation cannot yet provide a complete business case. An initial approach does not need to account for every possible consequence. When immature ideas are measured against the requirements of a final investment decision, familiar and incremental proposals are the most likely to survive. Early evaluation should therefore focus primarily on whether the underlying observation is relevant and which assumptions should be tested next.

An Unfinished Idea Is Not Necessarily a Poor Idea

Many relevant thoughts initially appear incomplete. One person recognises a pattern but cannot yet identify a solution. Another sees the technical opportunity but underestimates its effects on operational processes. A third understands the commercial value but lacks the specialist knowledge required for implementation. Innovation in this situation does not emerge because one person presents a fully developed idea. It emerges through the integration of these different pieces of knowledge.

Organisations that accept only complete proposals transfer the entire burden of translation and development onto individuals. This favours people who have sufficient time, status and rhetorical confidence. It disadvantages observations whose significance only becomes apparent through interaction with others.

Designing Innovation Processes: Safety Is Not Enough

Psychological safety can help people to ask questions, raise concerns about errors and express observations that differ from the dominant view. It is relevant to learning and innovation. It does not, however, solve the entire problem.

A person may feel sufficiently safe to raise an objection and still be regularly ignored. A team may discuss issues openly without having any influence over priorities or budgets. A workshop may feel respectful while the subsequent selection process remains based exclusively on short-term returns. There is a substantial difference between being allowed to say something and being able to influence a decision.

Anyone seeking to improve or design innovation processes must therefore examine organisational structures as well:

• Who is permitted to place an issue on the agenda?
• Who determines the evaluation criteria?
• Who controls information and resources?
• Who can approve an experiment?
• Who carries the risk of failure?
• Who can stop an idea informally?
• Who will later be expected to integrate the innovation into everyday work?

Power is not inherently hostile to innovation. Innovation requires decisions, resources and prioritisation. Power becomes problematic when it remains invisible and personal or political interests are presented as purely objective evaluation.

Psychological safety should not be confused with harmony either. Innovation requires openness, but it also requires substantive disagreement. A team that interprets every criticism as a lack of support will examine new ideas no more thoroughly than a team in which criticism leads to personal consequences.

Prototypes Provide Data, Not Unambiguous Answers

Design thinking, prototyping and experiments can make abstract assumptions visible and testable. They do not automatically produce innovation.

A prototype can only answer the question that was actually investigated through it. Imagine, hypothetically, that an organisation tests a new digital application with a group of particularly technology-confident existing customers. Their feedback is positive. This does not demonstrate that the application is understandable to the entire target group. The test may show that the basic concept works. It cannot prove that no barriers to access remain.

Prototyping is therefore not simply a matter of building something quickly. It is an organised form of learning under uncertainty. A useful experiment examines the question: Under which conditions does it work, for whom does it work and which assumptions do we need to revise?

Implementation Determines Whether Innovation in Organisations Takes Place

Many innovation initiatives invest considerable attention in workshops and idea development. The more difficult phase often begins after a prototype has been successful. The new approach must now be connected with existing processes, responsibilities, technical systems and performance indicators. People have to change their behaviour. Some receive additional responsibilities. Others lose decision-making authority or familiar routines. Implementation therefore becomes an organisational change process in its own right.

The OECD definition makes this point explicit. A product only becomes an innovation when it is made available to potential users, while a process only becomes an innovation when it is actually brought into use. Innovation activities also include development, financing and commercial activities directed towards implementation.

Between an idea and its application, organisations often need people who can explain the new approach, build coalitions and organise support. Innovation research describes this behaviour, among other concepts, as idea championing. It forms an important link between the generation of ideas and their implementation. This does not mean that every idea requires an especially forceful individual to push it through the organisation. On the contrary, when implementation depends entirely on personal persistence, the process itself is structurally weak.

Seven Questions About Your Organisation’s Capacity for Innovation

You can examine the social journey of an insight by asking seven questions.

1. Perception: Who recognises deviations at an early stage in your organisation, and through which channels do those observations become visible?

2. Understanding the Problem: How do you examine competing explanations before agreeing on a description of the problem?

3. Access to Knowledge: Which professional, operational or experiential knowledge is regularly absent from your decisions?

4. Translation: Who connects different specialist languages, interests and ways of thinking?

5. Evaluation: Are you assessing early ideas against criteria that are actually intended for mature solutions?

6. Decision-Making Power: Whose support do ideas officially require, and whose support do they require in practice?

7. Implementation: What happens after a successful test to ensure that processes, decisions and behaviour actually change?

The answers indicate where knowledge is being lost within your organisation.

Perhaps you do not lack ideas but appropriate channels through which observations can become visible. Perhaps differences are collected but never processed. Perhaps experiments succeed, while no one is responsible for the subsequent implementation.

The Social Journey of an Insight Can Be Designed

Innovation does not emerge solely in the minds of particularly creative individuals. Nor does it arise automatically through diversity, psychological safety or a particular method.

A relevant observation must be noticed, made understandable, connected with other knowledge and tested against competing interpretations. A possible solution must be recognised without being rejected too early because of the uncertainty created by its novelty. It must be tested and subsequently transferred into actual use.

Almost every one of these stages is social. At the same time, each can be influenced through organisational design. You cannot prescribe the moment at which someone makes an unexpected connection. You can, however, create conditions in which unusual observations are not prematurely dismissed. You can adapt evaluation processes to the maturity of an idea. You can make translation work visible and clarify responsibility for implementation at an early stage. An organisation’s capacity for innovation is therefore demonstrated above all by what it does with a relevant insight after someone has expressed it.

---

Under what social and organisational conditions lead different ways of thinking to innovation? Organisations already have access to a great diversity of perspectives and ways of thinking. Currently, most processes don’t make use of this. Monika Wolff explores and shapes the conditions needed to turn this diversity into shared insight, better decisions and genuine innovation. A two-week assessment and a report with recommended actions will give you a overview of what is possible (book dicsovery call).