From Idea to Sustainable Enterprise · 3 of 10The Enterprise Beneath the Idea
Proximity Is Not the Same as Understanding
Why knowing, serving or belonging to a community does not remove the need to listen, test interpretations and share influence.
A founder develops an idea for a service intended to support people from a community they know well.
They may live in the same place.
They may share an identity, language or cultural background with the people the service hopes to reach. They may have experienced the problem personally or worked inside an organisation that has encountered it repeatedly.
This proximity gives the founder valuable knowledge.
They understand references that an external researcher might miss. They know why certain institutions are trusted and why others are approached cautiously. They recognise informal networks, unspoken expectations and the history behind reactions that could otherwise appear irrational.
The founder does not need to begin from complete ignorance.
But proximity creates a risk of its own.
Because the community feels familiar, the founder may stop asking questions.
They may assume that their experience is typical, that relationships automatically transfer into trust or that sharing one aspect of identity gives them authority to speak for everyone.
They may believe they already understand what people need.
Proximity can produce insight.
It can also produce misplaced certainty.
Belonging to a community does not make a founder representative of every person within it. Serving a group for many years does not mean that its priorities have remained unchanged. Living in a place does not reveal everything that other residents experience.
Proximity is not the same as understanding.
Understanding must remain an active practice.
Distance and proximity create different blind spots
External organisations often misunderstand communities because they are too distant.
They rely on demographic information, consultation reports and publicly available statistics. They may know how many people live in an area, the average household income and which categories appear in a funding application.
They do not necessarily know how people experience the place.
They may overlook informal leaders, local tensions, cultural memory and the relationships through which information actually travels. They can arrive with language that is technically appropriate but socially unfamiliar.
Their distance limits what they can see.
A founder with close personal or cultural proximity has a different advantage. They may understand why a particular word carries more meaning than its literal definition or why a seemingly practical suggestion would encounter resistance.
But proximity has its own limits.
Familiar experiences become so normal that they are no longer noticed. Longstanding relationships can be mistaken for permission. The founder may hear most often from people who already know them, agree with them or possess sufficient confidence to speak.
Distance can create ignorance.
Proximity can create overconfidence.
Neither position guarantees understanding.
The important question is not whether the founder is inside or outside the community. It is whether they recognise what their position allows them to know—and what it may prevent them from seeing.
No individual represents an entire community
The word “community” can create an illusion of coherence.
A community may be described by location, age, ethnicity, profession, faith, creative practice, shared experience or common interest. These categories can identify a meaningful connection.
They do not make everyone within the category the same.
People living in one neighbourhood may experience it differently according to age, income, disability, housing, work, family responsibilities and how long they have lived there.
Artists may share a profession but differ sharply in ambition, financial circumstances, cultural recognition and their relationship to institutions.
People from the same ethnic background may hold different political views, religious beliefs, languages, migration histories and expectations of business.
Young people do not become a unified group because an application places them inside the same age range.
A founder may possess genuine knowledge of one part of a community. The difficulty begins when that knowledge is expanded into a claim about the whole.
“I have experienced this” becomes “people like us experience this.”
“People I know want this” becomes “the community wants this.”
“I was able to overcome this barrier” becomes “this is how the barrier should be addressed.”
These shifts can occur without deliberate misrepresentation. The founder may genuinely believe that their experience provides a reliable guide.
But a single story remains a single story—even when it is important, moving and true.
Identity can provide insight without providing authority
Shared identity can make certain conversations possible.
People may feel less pressure to explain cultural references or defend the legitimacy of an experience. A founder may recognise forms of exclusion that institutions routinely overlook.
This is valuable.
Yet identity alone does not establish the founder’s authority to decide what other people need.
A university-educated professional cannot assume that they understand every person from the same ethnic background.
A disabled founder may possess deep knowledge of one impairment while knowing little about the experiences of people with different access requirements.
A successful creative practitioner cannot treat their route through the cultural sector as a universal model for other artists.
An older resident may understand the history of a neighbourhood while remaining disconnected from younger people developing new relationships with the same place.
Identity is not irrelevant. It affects perspective, access, experience and trust.
But it should be treated as a position from which to listen—not a certificate granting complete knowledge.
A culturally intelligent founder can say:
My experience helps me recognise this problem, but it does not allow me to define everyone else’s experience of it.
That is not a retreat from authority.
It is a more credible form of authority.
Lived experience and representative evidence are different
Lived experience is frequently described as expertise.
That recognition is important. Institutions have often privileged professional qualifications and quantitative data while discounting the knowledge of people who actually experience a system’s consequences.
But lived experience can be misused when it is expected to perform every kind of evidential work.
A personal account can reveal that something happens.
It can explain how an experience feels, how a process is interpreted and why an institutional response is inadequate.
It cannot, by itself, show how frequently the experience occurs or whether all people in similar circumstances interpret it in the same way.
Representative data can identify patterns across a population.
It cannot fully explain the meaning of those patterns or reveal experiences that the data collection process was not designed to notice.
These forms of knowledge should not be placed into a hierarchy where one must defeat the other.
They answer different questions.
A strong enterprise may need:
Personal experience
Community testimony
Behavioural observation
Local knowledge
Professional expertise
Administrative data
Market information
Historical context
Independent research
Evidence from small experiments
The task is to understand what each source contributes, whose perspective is missing and how much confidence the available evidence can support.
Familiar relationships do not automatically create permission
A founder may already know potential participants.
They have attended the same events, worked with local organisations or contributed to community initiatives. People recognise them and may respond positively when they describe the idea.
This can make early engagement easier.
But familiarity should not be mistaken for informed agreement.
Someone may listen politely because they value the relationship.
They may express encouragement without wanting to use the service.
They may hesitate to criticise an idea developed by a person they know.
They may agree to participate because refusing feels uncomfortable.
They may assume that the founder is acting on behalf of an organisation, funder or recognised local institution.
Relational warmth can conceal uncertainty.
A culturally intelligent founder therefore makes the purpose of each conversation clear. They distinguish an informal discussion from research, a request for feedback from an invitation to participate and an expression of interest from an actual commitment.
They also create space for refusal.
Trust is not demonstrated when people feel unable to say no.
Serving a community can create institutional assumptions
Organisations sometimes believe they understand a community because they have worked with it for many years.
They possess attendance records, evaluation forms and relationships with local partners. They may have delivered several successful projects.
This history provides valuable organisational knowledge.
It can also freeze the community in an earlier description.
The organisation remembers who participated previously and designs future work around them. It continues using categories created for an old funding programme. It consults the same visible representatives because those relationships are established and convenient.
Meanwhile, the place changes.
New residents arrive. Younger participants develop different expectations. Costs increase. Trusted venues close. Digital habits change. Previous participants take on new responsibilities. A local controversy alters how institutions are perceived.
An organisation can remain physically close while becoming culturally distant.
Past engagement is not permanent understanding.
It must be renewed.
The people easiest to reach are not always the people most affected
Founders often begin research with the people available to them.
They speak to friends, professional contacts, social-media followers and existing customers. These conversations provide useful early feedback.
But convenience creates a distorted picture.
The people most likely to respond may have more time, confidence, digital access or familiarity with the founder’s language. They may already feel comfortable participating in consultations.
The people experiencing the greatest barriers may be the least visible.
They may not attend organised meetings. They may abandon online forms. They may not describe themselves using the project’s categories. Previous experiences may have taught them that consultation rarely changes anything.
Some will be managing work, disability, caring responsibilities or unstable housing. Participation may require time and energy they cannot spare.
When these people are absent, an organisation may conclude that they are “hard to reach.”
The phrase places the difficulty inside the community.
A better question is:
What is making this organisation difficult to reach, trust or participate in?
This reframing changes the direction of responsibility.
Community engagement is not audience recruitment
A venture may want to develop an offer with a community and eventually sell, deliver or promote that offer.
These are different activities.
Community engagement asks people to contribute knowledge, perspective or influence.
Audience recruitment asks people to attend, purchase, register or participate in something substantially decided.
The two are often confused.
An organisation announces a consultation after the budget, venue, timetable and programme have already been established. Participants are asked whether they like the proposal, but the important decisions are no longer open.
The organisation records that the community was consulted.
In practice, the engagement functioned as early promotion.
Genuine participation requires clarity about what can change.
If only minor details remain open, that limitation should be stated honestly.
If people are being asked to influence the purpose, design, delivery or ownership of the venture, they should know how their contribution will enter the decision-making process.
Participation does not require handing every decision to everyone.
It requires avoiding the pretence of shared influence where none exists.
Listening is not the same as agreeing
A founder may listen carefully and still decide not to follow every suggestion.
People within a community will disagree. One person’s preferred solution may create a barrier for another. A request may be incompatible with the venture’s resources, ethics or purpose.
Understanding does not mean abandoning judgement.
It means ensuring that judgement has been informed by experiences beyond the founder’s own.
The founder should be able to explain:
What was heard
Where views differed
What changed as a result
What did not change
Why a particular decision was made
Which uncertainty remains unresolved
This creates accountability without implying that consultation will produce consensus.
A weak process collects feedback and silently selects the comments that support the original plan.
A stronger process records disagreement and shows how the final decision was reached.
Community knowledge creates questions of ownership
When people contribute stories, language, ideas and local knowledge, they create value.
A founder may use those contributions to design a service, write a funding application, create intellectual property or strengthen a commercial proposition.
This raises an important question:
Who owns the value produced through participation?
There is no single rule for every situation. An informal conversation about a developing idea is different from months of co-design work. Publicly available cultural knowledge is different from sensitive testimony or knowledge held through a particular community relationship.
But scale and consequence matter.
As the contribution becomes more substantial, the need to consider acknowledgement, payment, shared ownership or continuing influence becomes stronger.
Founders should ask:
Are people being asked to perform unpaid development work?
Is their knowledge becoming part of a privately controlled product?
Have expectations been explained?
Will contributors see what their input produced?
Are they being credited appropriately?
Should they receive payment or another tangible benefit?
Will they retain influence as the venture develops?
Could the commercial success of the idea depend on knowledge extracted from people who receive little in return?
Cultural intelligence requires more than listening respectfully.
It requires attention to what happens to the knowledge after it has been shared.
Representation cannot be solved by one visible person
Organisations sometimes respond to concerns about representation by finding one person who appears able to speak for a broader group.
That individual may be a respected community leader, practitioner or local partner. Their knowledge can be extremely valuable.
But one representative cannot remove internal difference.
Visible leaders may be more connected to institutions than other community members. They may hold formal roles that shape what they are comfortable saying. Some people may not recognise them as representative at all.
The answer is not to dismiss community leadership. It is to understand its context.
Ask:
Who recognises this person’s authority?
What knowledge do they possess?
Whose experiences might they not encounter?
Are alternative or dissenting voices present?
Does the venture repeatedly consult the same small circle?
Who would be approached if established institutions did not provide the contact?
Representation is not achieved by placing one person at the table.
It requires examining who designed the table, who feels able to enter and which decisions are actually being made there.
Trust must be earned for this particular venture
A founder may be trusted personally.
That does not mean people will trust every organisation, product or system they create.
A community member may believe that the founder has good intentions but remain concerned about pricing, privacy, funding relationships or who will control the venture in future.
They may trust the founder in an artistic or community role but not yet understand their new role as a business owner.
The venture may also introduce new technologies, staff, partners or investors that change the relationship.
Trust does not transfer automatically from person to institution.
The enterprise must establish:
What it is
What it wants from participants
What it will do with their information
How it will generate income
Who controls important decisions
What will happen if the founder leaves
How concerns can be raised
What accountability exists when something goes wrong
Personal credibility can open a conversation.
The venture’s conduct determines whether trust continues.
Difference within a community is strategic intelligence
Internal difference is sometimes treated as an inconvenience.
The founder wants a clear audience profile. Contradictory experiences make the proposition harder to explain.
But difference can reveal valuable strategic possibilities.
It may show that the venture has two distinct audiences requiring separate offers.
It may reveal that one service format creates access for some people while excluding others.
It may uncover a difference between the person who benefits and the institution capable of paying.
It may demonstrate that the problem changes across locations, stages of life or levels of experience.
It may show that the venture should begin with one narrower group rather than make an unconvincing claim of universal relevance.
Variation does not always weaken a business case.
It can make the design more precise.
Build an Audience and Community Relationship Map
At this stage, the founder can create an Audience and Community Relationship Map.
The map should not reduce people to customer types. It should show relationships, knowledge, influence, trust and the consequences of the venture.
People directly affected
Who experiences the problem or opportunity?
How do their experiences differ?
Customers and participants
Who might purchase, attend, use or contribute to the offer?
Are these the same people who benefit?
Decision-makers
Who gives permission, controls budgets, selects suppliers or determines access?
Existing relationships
Who already knows or trusts the founder?
What is the basis of that trust?
Community knowledge
Who understands the history, language, relationships and previous attempts surrounding the issue?
Connectors and gatekeepers
Who can create access?
Does their involvement expand participation or control it?
People carrying risk
Who could lose time, money, privacy, confidence, status or opportunity if the venture fails?
People creating value
Whose stories, ideas, labour, relationships or cultural knowledge will strengthen the venture?
Missing voices
Who is least likely to appear in conventional consultations?
Influence
Which decisions can different people genuinely shape?
The map should make visible the difference between knowing people, reaching people and sharing power with people.
A practical field exercise
Hold a small series of listening conversations with people who occupy different positions around the idea.
Include, where relevant:
Someone who experiences the problem directly
Someone who tried an existing solution
Someone who stopped participating
Someone with relevant community or cultural knowledge
Someone who might pay or authorise a purchase
Someone who is sceptical of the proposed idea
Do not ask only whether they like the idea.
Explore:
1. How do you describe the situation in your own words?
2. What do people outside it usually misunderstand?
3. What are you already doing?
4. What would make a new offer feel relevant?
5. What would make you cautious?
6. Who else should influence the design?
7. What should the venture never assume?
8. What would responsible participation look like?
9. What would you need to see before trusting the organisation?
10. How should contributors benefit if their knowledge shapes the venture?
Afterwards, compare what you heard with what you previously believed.
Record the differences rather than smoothing them away.
The decision to record
At the end of this stage, the founder should record:
Who the venture is currently for
Who may benefit without purchasing
Who may pay without directly using the offer
Whose knowledge has informed the idea
Which voices remain missing
What people understand differently from the founder
What influence participants will have
What the venture is asking people to risk
How contributions will be recognised
Which trust relationship must be built next
The founder should then make one clear decision:
Whose understanding must change the design before the venture moves forward?
This question moves participation from general intention to strategic consequence.
If the answer is “nobody,” the process is not participatory. It is promotional research.
Understanding is never permanently completed
There is a temptation to treat audience and community research as a stage that can be finished.
A founder completes interviews, creates profiles and moves on to developing the offer.
But people change.
Places change.
Language changes.
Economic conditions change what people can afford. Technology changes how they interact. Institutional failures change whom they trust. New cultural conversations change what appears acceptable, relevant or necessary.
The venture itself also changes the environment.
Once it begins operating, people respond to the experience it creates—not merely to the original problem.
Understanding must therefore continue after launch.
The founder should pay attention to:
Who participates
Who does not
Who returns
Who leaves
Which uses of the offer were unexpected
Which groups experience the greatest value
Where confusion appears
Which complaints are recorded
Which forms of quiet refusal remain invisible
How relationships change as money and institutional power enter the venture
A culturally intelligent enterprise does not claim to understand its community once and for all.
It builds the capacity to keep learning.
Belonging should deepen the responsibility to listen
Proximity matters.
A founder’s experience, identity, relationships and knowledge may give them an unusually strong starting point. These qualities can help an enterprise notice what distant institutions overlook and design something with genuine cultural relevance.
But the strongest use of proximity is not the claim:
I belong here, so I already know.
It is the commitment:
I belong in this relationship, so I have a deeper responsibility to listen carefully, distinguish my experience from other people’s and remain accountable for what I build.
Understanding does not require the founder to abandon their perspective.
It requires them to place that perspective alongside other forms of knowledge.
The result may be a more complex picture than the original business idea anticipated.
The audience may become narrower.
The service may change.
A community partner may need genuine decision-making power.
The venture may discover that it should support an existing initiative rather than create a competing one.
The founder may have to acknowledge that the problem is different from the one they personally experienced.
Each discovery makes the enterprise more credible.
Proximity can open the door.
Only continued listening, shared influence and accountable action can build the understanding required to walk through it responsibly.
Learning Path Reflection
Before continuing, consider:
1. What gives you proximity to the people or communities involved?
2. What does that proximity genuinely help you understand?
3. What might it prevent you from noticing?
4. Where have you mistaken personal experience for a shared experience?
5. Who is easiest for you to reach?
6. Who may be absent from your current understanding?
7. What are you asking people to contribute or risk?
8. Which decisions can participants genuinely influence?
9. How will community knowledge be recognised?
10. What would responsible disagreement with your interpretation look like?
Living Intelligence Record
Record:
Intended audiences, customers and participants
Communities connected to the idea
The founder’s position and proximity
Existing relationships and sources of trust
Different experiences within the community
Contributors of knowledge, labour and access
Decision-makers and budget holders
People carrying risk
Missing or underrepresented voices
Decisions open to shared influence
Cultural and relational considerations
The next relationship that must be developed
Related Map
Audience and Community Relationship Map
Continue the Learning Path
Next article: Value Does Not Exist Until Someone Experiences a Difference
The next stage examines how an enterprise can define the practical, cultural, social, emotional and commercial value it creates—without confusing features, effort or good intentions with a meaningful outcome.
About This Series
This article is part of The Enterprise Beneath the Idea, the original Cultural Intelligence Studio article collection accompanying the From Idea to Sustainable Enterprise learning path.
The learning path combines original CIS thinking with carefully selected videos, podcast conversations, practical exercises, a Living Intelligence Record and connected cultural intelligence maps.
Its purpose is to help people make stronger decisions about what should be developed, changed, tested, paused or left behind.
Optional CIS Support
The Idea Clarity and Validation Review provides an independent examination of an emerging idea, its problem definition, intended audiences and communities, important assumptions, proposed value, available evidence and smallest credible next step.
For community-led or place-based ventures, Community Project Development can provide more extensive support with participation, cultural context, partnership design and project development.
Engaging CIS is optional. Early investigation may show that further listening or relationship-building is more appropriate than purchasing additional support.