---
id: guides/put-it-in-front-of-its-users
about:
  label: Put it in front of its users
  description: >-
    Make the output fit the meeting, the screen and the person who will use it,
    then watch them use it.
guide:
  stage: 8
provenance:
  origin: agent
  reviewed: '2026-10-18'
  reviewed_by: >-
    Claude, written for the patrons in devlog/20261018-patrons.md from entries
    on this site; not yet read by Anselm
  status: draft
---
The model is built, checked, and sitting on a modeller's laptop. The last step is getting its answer into the room where the decision happens, in a form the people there can argue with.

## Fit the meeting

Ask how the decision is actually made: a council agenda, a budget sheet, a morning briefing, a public hearing. Produce the output in that form. A beautiful 3D scene that cannot be printed into the agenda pack is not in the meeting.

## One picture, and the sentence under it

For each scenario, one map or chart that a person can read in thirty seconds, with the sentence from [the check](/guides/check-it-against-what-happened/) under it: how close the model came to the past. Everything else is a layer down, for the people who want it.

## Let them touch it

Where the question is one people argue over, give them the controls: a browser page where they can change the one thing they care about and watch the result. The [combining proposals](/questions/combining-proposals/) question page lists tools built for this. Keep the controls few.

## Watch

Sit with the users the first few times. Note where they hesitate, what they ask, what they ignore. Fix the output before fixing the model; the most common failure is a correct answer nobody could read.

## Publish what you can

A model whose outputs, inputs and sources are public can be checked, reused and cited. [Bay Layers](/twins/bay-layers/) on this site publishes its source; the [digital twins](/twins/) section marks which projects run and which are open.

## Next

[Keep it alive](/guides/keep-it-alive/), or decide not to.