Triangulation

Triangulation compares evidence from different roles, artefacts and episodes so the organisation does not depend on a single account of itself. It is one of the simplest ways to move from opinion to diagnosis.

In brief

Every role sees the organisation from a position. The founder sees one version, managers another, operators another, systems another. None is automatically false, but none is complete.

Triangulation puts these views side by side. The goal is not to average them into a polite middle. The goal is to see where they converge, where they diverge and what the divergence reveals.

Operational definition

Triangulation uses at least two, preferably three, independent sources for the same condition.

The sources may be people, documents, system traces, cases, meetings, emails, process maps or quantitative data.

A strong triangulation asks the same diagnostic question through different channels: what does the role say, what does the artefact show, and what did recent cases actually do?

Why it matters for SMEs

SMEs rely heavily on verbal knowledge. That makes diagnosis fast but vulnerable to hierarchy, memory and local perspective.

If the founder is the only source, the diagnosis inherits founder blind spots. If operators are the only source, it may miss strategic constraints. If the system is the only source, it may miss what happens outside the system.

Triangulation reduces dependence on any single view.

Observable signals

Use triangulation when people disagree about the same process.

Use it when a problem is politically sensitive.

Use it when the official system does not match daily practice.

Use it when a diagnosis comes only from the top team.

Use it when the same issue appears in interviews, traces and repeated episodes.

Common mistakes

The first mistake is asking everyone together. Group settings often hide divergence.

The second mistake is treating divergence as noise. Divergence is often the finding.

The third mistake is using several sources that are not independent.

The fourth mistake is collecting views without comparing them on the same question.

Operational example

A company believes delays come from production. Interviews with sales support that view. System timestamps show that production cycle time is stable. Recent order reconstruction shows that most waiting occurs before release, in technical validation.

The triangulation changes the diagnosis. The issue is not production speed but pre-release quality and decision ownership.

Diagnostic questions

Which sources describe the same condition?

Are the sources independent?

Where do they agree?

Where do they diverge?

What does the divergence make visible?

Which source is missing from the current diagnosis?

Practical implications

Collect views separately. Compare them against the same question. Add artefacts and recent cases wherever possible. Preserve divergence instead of smoothing it too early.

Use triangulation before prioritising interventions, especially when the issue involves roles, decisions or process reality.

MARTRO reading

In MARTRO’s reading, triangulation is a core diagnostic discipline. The distance between sources is not an inconvenience; it is often the structural signal.

It connects directly with role gap, process reality and qualitative indices.

Frequently asked questions

Is triangulation only interviews? No. It can include documents, system data, cases and operating artefacts.

How many sources are enough? Three independent angles are usually a strong start.

What if sources disagree? Treat disagreement as data. Ask what each source can see that the others cannot.

Does triangulation slow diagnosis? It takes more effort than asking one person, but it prevents wrong priorities.

Why is it important in SMEs? Because informal knowledge and hierarchy can make a single account look more complete than it is.