Open collaboration
Why Sharing Ideas Matters—and How to Do It Constructively
Learn how sharing problems and early ideas can improve understanding, attract new perspectives and connect unmet needs with people able to solve them.
People often keep ideas to themselves. They may worry that the idea is unfinished, that someone will criticize it or that another person will take it. In organizations, an employee may also assume that raising an observation is outside their role or unlikely to change anything.
These concerns are understandable. However, an idea that remains private cannot benefit from other people’s experience, reveal whether the underlying need is shared or reach someone capable of helping it progress.
Sharing does not mean presenting an idea as finished or giving away confidential information. It means making an observation available for constructive examination.
Sharing helps separate a personal frustration from a wider need
When an idea is based on your own experience, it is difficult to know how widely the problem is shared. Other people can provide important context:
- They may recognize the same need.
- They may experience it in a different situation.
- They may already use a workaround you have not considered.
- They may explain why an apparently simple solution would be difficult.
- They may show that the problem is less significant than it first appeared.
All of these outcomes are useful. The purpose of sharing is not only to receive agreement. It is to improve understanding.
Other perspectives make ideas stronger
An initial idea usually reflects one person’s knowledge and assumptions. A customer, designer, engineer, salesperson, researcher or service employee may notice entirely different aspects of the same situation.
One person may focus on ease of use, another on technical feasibility and a third on whether a sustainable business model is possible. Constructive disagreement can expose risks early and prevent a team from becoming attached to an incomplete solution.
The OECD describes innovation as a distributed process in which knowledge flows between companies, customers, suppliers, research organizations and individuals. Digital platforms, crowdsourcing and other collaborative methods can help organizations receive ideas, comments and suggestions from more diverse sources.
Sharing can connect a need with the ability to solve it
The person who experiences a problem is not always the person who can solve it. A consumer may recognize an unmet need but lack technical expertise. A small company may understand an industry problem but lack development resources. A specialist may be able to create a solution without knowing that the need exists.
Making the problem visible can connect these complementary perspectives. The original contributor may gain a solution or an improvement to a product they use. A company may discover an opportunity to serve customers better. An innovator may find a meaningful challenge worth exploring.
Early feedback reduces avoidable effort
It is easy to become attached to a solution before testing whether the problem has been understood correctly. Early discussion can reveal that:
- the need affects a different group than expected;
- the proposed feature addresses a symptom rather than the cause;
- an existing solution already works well;
- the obstacle is organizational rather than technical;
- users value a different outcome than the creator assumed.
Discovering this before significant investment is not failure. It is progress. Feedback can redirect effort toward a more relevant problem or a better approach.
What should be shared: the problem or the solution?
Both can be useful, but they serve different purposes.
Sharing a problem or unmet need invites several possible solutions. It keeps the discussion open and helps determine whether other people recognize the situation.
Sharing a solution idea gives people something more concrete to evaluate, but it can also anchor the conversation too early. Participants may debate features before agreeing on what needs to improve.
A productive contribution often starts with four elements:
- Situation: Where and when does the issue occur?
- Need: What is the person trying to achieve?
- Obstacle: What currently makes this difficult?
- Consequence: Why does improving it matter?
A solution can be introduced afterwards as one possibility rather than the only correct answer.
How to share an idea constructively
Be specific
“Customer service should be better” is difficult to act on. “Customers cannot see the status of a service request and repeatedly contact support for updates” gives other people something concrete to examine.
Separate observations from assumptions
State what you have seen or experienced, and identify what you merely believe. For example: “Three customers asked for the same information this week” is an observation. “All customers would pay for an automated service” is an assumption.
Explain who is affected
An idea becomes easier to assess when readers understand the relevant group. Avoid claiming that “everyone” has the problem unless evidence supports it.
Invite development rather than defend ownership
Ask what others have experienced, what alternatives already exist and what constraints should be considered. The objective is to learn, not to win an argument.
Protect what genuinely needs protection
Do not publish trade secrets, confidential customer information, personal data or material that belongs to an employer or another person. If patentability, contractual confidentiality or commercially sensitive implementation details may be involved, obtain appropriate professional advice before disclosure.
It is often possible to discuss a general problem and its effects without revealing protected details.
A signal is not proof
Positive reactions, votes and comments can show that people recognize a need. They can help prioritize what deserves further study, but they do not guarantee demand, technical feasibility or commercial success.
Strong decisions require additional evidence: conversations with the relevant people, observation of existing behaviour, analysis of alternatives and small experiments. Sharing is therefore not the end of validation. It is one way to begin it.
Ideas become more useful when they can be found
Many organizations already contain valuable observations, but they are scattered across emails, meetings, support systems and individual notebooks. Public needs are similarly dispersed across reviews, forums and conversations.
A shared and searchable place gives these observations a longer life. Similar needs can be connected, patterns can become visible and people can contribute when they have relevant knowledge—not only when they happened to attend the original discussion.
An unfinished idea does not need to be presented as a promise. It can be shared as an invitation: Here is something that should work better. Does anyone else recognize the need, and what could move it forward?
That invitation is often where collaboration begins.
Further reading
- OECD and Eurostat, Oslo Manual 2018: Business innovation and knowledge flows
- Design Council, History of the Double Diamond