Tensions in Practice: Different perspectives and the work of combining them¶

Designing a reusable workshop tool

A user notices what makes a tool awkward to operate; a repairer notices what makes it hard to service. Keeping their ideas separate can support independent exploration. To shape one tool, however, the views must meet in a design that confronts their conflicts. A shared session can create that path, but hearing both sides is not the same as resolving every difference.

Preserve distinct viewpoints

Let people with different functional experience identify different possibilities and problems.

Produce a coherent shared design

Bring relevant insights into one plan that can be built and assessed.

Why these aims pull against each other

Separate perspectives can remain available without influencing one another. Combining them can reveal blind spots, but takes translation, discussion, and choices that may leave some preferences unmet.

Compare the arrangements

Explore separately

The user and repairer each develop a candidate from their own perspective, without integrating their findings in this phase.

What it protects: Each line of inquiry can develop without spending effort negotiating an early common design.
What it costs: Neither candidate automatically incorporates what the other perspective discovered. Selecting one later can discard a relevant concern.
When it fits: Plausible during early exploration or when outputs serve independent purposes; insufficient by itself to claim the benefits of integrated judgment on one tool.

Illustration note: The two roles are invented functional perspectives. The diagram does not claim their views are internally uniform or inherently opposed.

Work on one design

Bring both sets of findings into joint design work. Record which choices address each concern and which tradeoffs remain, then produce a candidate for assessment.

What it protects: Both perspectives can alter the same design, exposing conflicts that separate candidates could hide.
What it costs: Participants must translate concerns and resolve or explicitly retain disagreements. A shared design can become a compromise that satisfies neither well.
When it fits: Plausible when both perspectives are relevant to the same product and the process gives each a real opportunity to affect its choices.

Illustration note: The joint work is an editorial response to T5. It does not guarantee consensus, better performance, or complete inclusion merely because a meeting occurs.

What this illustration does—and does not—establish

Diversity: The diversity bonus depends on integration; without it, diversity becomes fragmentation supplies the difference between presence and integration. The separate and shared design paths are editorial contrasts with explicit exploration and coordination costs.

Functional relevance must be established; collecting different labels or more disagreement does not itself create useful diversity.
The graph shows a route for perspectives to influence choices, not a measured diversity benefit or proof that all voices had equal influence.
These are judgments about one design, not successive manufacturing stages or redundant implementations that keep a service running.

Source entries

Diversity

Prime · Source of the tension

Diversity: The diversity bonus depends on integration; without it, diversity becomes fragmentation supplies the integration requirement and its costs. The example concerns functional differences in experience, not demographic labels or disagreement for its own sake.

Different perspectives need an integration path

T5: The diversity bonus depends on integration; without it, diversity becomes fragmentation. Diversity's benefits (broader exploration, blind-spot detection, adaptive capacity) only manifest when diverse elements are genuinely integrated—when perspectives are heard, when diverse types work together, when insights from different approaches are combined.

Read the source section

Integration itself takes work

The cost of integration (communication, conflict resolution, consensus-building) can be high, and not all organizations sustain it.