§ Work

Selected work, described by structure and approach.

Each case below is one engagement, generalized: the situation, the approach, the figure that carries the argument, and what was handed over. Clients are unnamed and their numbers stay their own. What remains is the part another organization can learn from: how the problem was framed and how the system was held to that framing.

Every case ships only with the written consent of whoever owns the work, and after a guardrail test confirms that no client, product, person or figure appears.

§ 02

How a case is written

The same discipline the practice sells, applied to its own publicity.

A case is written from the engagement's own artifacts: the definition, the requirements, the design, the code and its tests. Every sentence on a case page is listed in a register with the artifact behind it, and a sentence with nothing behind it is cut rather than softened. The register is kept outside the repository because it names what the page does not.

Three things are removed by rule and checked by test before a page ships: names of clients, products, vendors and people; every figure; and any phrasing the client's own materials use. What is left is general on purpose. The pattern in each case is meant to be recognizable from the outside, so that a reader can judge whether it fits their situation before a conversation starts.

§ 03 — Contact

Recognize your situation in one of these?

Say which case comes closest, what is different about yours, and the decision that is coming up. We respond directly.