Complex organisational problems often create confident but incomplete answers. A leader sees the strategic opportunity. Finance sees the trade-off. Technology sees the dependency. A frontline team sees the additional steps required to make the process work. Customers and communities experience the consequence.

Each perspective may be accurate. The difficulty begins when one is treated as the complete description of the problem. The organisation then designs a solution that makes sense from one position and creates unintended work, risk or resistance elsewhere.

Different perspectives do not mean the organisation lacks expertise. They mean the expertise is distributed.

Power and proximity reveal different things

People with decision authority can see constraints and ambitions that are not visible locally. People closest to the work can see friction, workarounds and human consequences that are easy to miss from a strategic view. Neither position automatically produces the better answer.

BridgeWorks uses perspective as a discipline because it creates a pause before prescription. The purpose is not to collect every opinion or make all views equal in every decision. It is to understand what each position reveals, what it cannot see and how power shapes which perspective is heard.

What better looks like

Before: “People keep repeating their position, meetings return to the same debate and the solution feels obvious only to the group proposing it.”

After: “People can recognise what others see, assumptions are visible and the group has a shared enough picture to make the next decision.”

Shared understanding is not consensus

Teams sometimes avoid perspective work because they fear it will slow the decision or require everyone to agree. Shared understanding does not mean identical views. It means people understand enough of the whole situation to interpret the decision, anticipate the impact and act together.

A finance team may still prefer a lower-cost option. A delivery team may still believe the timeline is unrealistic. Shared understanding means those differences are explicit, the trade-off is understood and the decision is not presented as if the concerns never existed.

This matters for trust. People can accept a decision they did not choose when they understand how it was reached and can see that the consequences they raised were taken seriously.

Listen for what the perspective is protecting

Behind a position is often something the person is trying to protect: safety, pace, customer experience, professional judgement, reputation, affordability or the ability to deliver. Asking what matters beneath the stated preference can reveal common ground.

For example, one group may request more control while another asks for greater autonomy. Both may be trying to protect quality. The real design question becomes how to create reliable quality without forcing every decision to the centre.

Make assumptions visible

Many disagreements persist because people are using different assumptions about demand, capability, risk or behaviour. These assumptions can sound like facts when they have not been tested.

A useful perspective conversation separates:

  • What is known and supported by evidence.
  • What people have observed through experience.
  • What is being inferred.
  • What is feared or hoped for.
  • What remains genuinely unknown.

This does not weaken experience. It makes the basis of each perspective clearer and helps the group decide what needs evidence, experimentation or judgement.

Include the people who inherit the outcome

Organisations often involve those who design, fund and approve the change, then consult those who must live with it after the important choices have narrowed. The result may be technically sound but difficult to use.

People closest to the work should not be included only to validate a proposed solution. Their expertise should help shape the problem definition, reveal practical constraints and identify what capability will be needed after implementation.

A practical perspective map

  1. Name the challenge without embedding the preferred solution.
  2. Identify who has decision power, who performs the work and who experiences the consequence.
  3. Record what each perspective sees, needs and may be unable to see.
  4. Highlight conflicting assumptions and shared concerns.
  5. Rewrite the challenge using language each group can recognise.
  6. Choose the next decision or experiment, not the entire future solution.

The value is not the completed canvas. The value is the movement from “they do not understand” to “I can see why this looks different from where they stand.” That shift creates better questions and makes a more grounded decision possible.

The answer may still be difficult. Perspective does not remove trade-offs. It helps the organisation make them with greater clarity and respect for the people who will carry the outcome.

What you can take away

You can identify which perspectives are missing, distinguish facts from assumptions and create shared enough understanding for the next decision.

Try this next: Perspective Mapping Canvas. Map what different people see, what each perspective protects and what the wider group may be missing.

CapabilityWhy the best solution should make itself less necessaryHuman-centred AIAI adoption begins with confidence, not access