When a product team should ask for an outside reading

We decline work. A team that wants a reading as decoration — a report to wave at a funder, a map to match a palette — will not like the sitting. A team that has never looked at its own tickets will not like the intake, because we will send them back to the cupboard first.

The brief we take has a shape. Two camps have been arguing for weeks (design and operations is the usual pair). Both can point at the same chart. Neither can say what a person actually did in the hour the chart describes. The product is live. The audience can be spoken with. The question can be written in one paragraph.

If those conditions are missing, an audit is the honest next step: a week with the records, a letter that names the gaps, and no drawing that pretends the gaps are closed. If the conditions are present, a study is cheaper than another quarter of corridor talk.

Outside reading is not wiser because it is outside. It is useful because the reader does not have to live with the camp they sit beside at lunch. That distance is the whole of the offer. It is also why the briefing must include the people who can change the product. A report left with a camp that cannot act is a pamphlet.