Start with the work you need done.

Start from the work, not the feature

These pages take a kind of work and show which surfaces it uses, in what order, and where a person has to decide something. The approval boundaries do not change between domains — only the sources, the vocabulary and the shape of an acceptable result do.

Worked examples

• Sales — researching organisations without losing the source behind each fact.
• Finance — evidence-led research where the citation matters as much as the figure.
• Legal — questions asked across a document collection, answered from the passage.
• Insurance — document review that stays traceable from intake to decision.
• Life sciences — scientific material organised so a reviewer can follow the evidence.
• Engineering — development work with a diff and a check you can read before accepting it.
• Everyday work — an open question carried through to a finished, shareable artifact.

Adapting one

1. Replace the sources first. A workflow is only as good as the material it is entitled to read, and that is the part that differs most between teams.
2. Keep the review step where the example puts it. Moving an approval later saves a click and costs the ability to catch the wrong scope before it runs.
3. Write down what a good result contains before running it, so that the first fluent answer does not become the definition of success.