Zoning in for business success. Every operation decomposed into bounded, governed zones with explicit entry and exit conditions — so handoffs become contracts, failures become measurable, and improvement becomes systematic.
The core dysfunction in most organisations is the gap between documented intent and measurable reality — and when things go wrong, no way to tell whether the failure was policy, operations, reporting, or structure. Tangram closes that gap by treating the boundary conditions between units of work — the points where responsibility is handed off — as the primary design objects.
A zone is a bounded operational space with one goal and two boundary conditions. The exit condition of one zone becomes the entry stake of the next, forming a chain of contractual handoffs; a message formally signals each crossing. You cannot manage what you cannot measure, and you cannot measure what you have not defined — Tangram makes your operations definable.
A bounded operational space — physical, logical, or both — defined by functional coherence: one goal, explicit entry and exit conditions, and a defined error path.
Objective governance, kept pure of operational contamination. Given the facts, a well-formed policy returns a deterministic decision — so it can be tested, audited, and reported on independently.
The day-to-day execution of service within a zone — the staff, procedures, tools, and workflows that enact policy decisions. A delivery channel is a medium; conops is the whole activity.
Nested levels of visibility — operational delivery, policy area, zone, and cross-zone program integrity — each aggregating the one below, from the front line up to the board.
The policy-purity principle: mixing policy with operations makes policy effectiveness unmeasurable and enforcement unpredictable. Keeping "what is permissible" separate from "how we do it" is the single most common — and most essential — discipline.
A chain of zones forming one end-to-end process. Zones are the units of operational management; continuums the units of program management — dozens of zones, three or four continuums.
Zone design is fractal — zones nest where complexity warrants it, and group where governance needs it. Add levels only when the benefit is clear; every level costs governance.
Failures are first-class citizens with their own entry conditions, operations, and a structured route back. If your only error handling is "contact a supervisor," you have an undesigned zone.
External partners and regulators sit outside your model — so you design your side of the interface: what they owe you, what you pass them, and what happens when they fail.
AI performs best when the problem space is well-defined, the inputs structured, and the outputs constrained — exactly what a zone provides. In return, AI takes on Tangram's most labour-intensive work: discovering zone candidates from operational data, drafting policy from regulatory text, evaluating cases against policy, and summarising zone reporting.
An AI agent inside a zone answers to the same policies, reporting, and error paths as a human operator — with models versioned and governed like policy, decisions traceable to policy criteria, a human escalation path, and drift monitored in zone reporting. This is where Tangram meets Origi: Tangram bounds where an agent operates; Origi governs whether it may act — the pairing proven in Northwind, Lamassu, MedBooth, and the ECCC engagement.
A quick self-check drawn from our use-case evaluation instrument. First rule out the structural incompatibilities, then tick each statement that holds true for your use case — the score maps to the same recommendation bands we use in formal assessments.
Structural incompatibilities that no design choice can resolve.
The highest-weighted criteria from the five evaluation dimensions.
Rule out the disqualifiers, then tick each statement on the left that holds true for your use case. Your score and recommendation appear here.
Adapted from the full instrument: 27 criteria across five weighted dimensions, scored 0–3 and normalised to 100.
Tangram is rigorous enough for formal governance yet pragmatic enough to adopt incrementally, in real organisations with imperfect documentation and legacy processes. Each stage produces a concrete deliverable, and reporting waits until the zone model is stable — a lightweight first pass is enough early on.
Book a working session and leave with a first-pass zone map of one of your own continuums.