Writing about software is easy to get wrong in both directions. Say too little and nobody understands what a product does. Say too much and a pilot starts to sound like a platform, an illustration starts to sound like a customer result. We use a simple discipline to stay in the middle.

Six moves

• Name the object: the system, version, environment and source.
• Give it a state: live, pilot, prototype, simulation or concept.
• Attach the trail: the artifact, the method, the date.
• Draw the boundary: what the evidence does not establish.
• Show the denominator: a baseline, a sample, a period and an owner for any metric.
• Keep the record current: revisit the state when the facts change.

A preview is not a deployment. A capability is not an audited outcome.

Why it matters to us

SeerFlow is a live product. Auctra is in a private pilot. Our illustrated interfaces are authored examples, not live accounts. Saying those things plainly costs nothing and earns something more useful than excitement: the reader’s confidence that the next thing we tell them is true.

The full method, with examples from our own products, is published on our methodology page.

— Tetheric Systems