Zorg • Organizational Design & Oversight

How a structure is designed

Six delivery phases. Six internal controls, one applied per phase.
Applies to Diagnostic Review, Structural Build, and Retained Oversight Architecture engagements alike.

Overview

A reporting line is a legal instrument before it is an org chart. It determines who was told what, when, and whether they were positioned to act on it. Most organizations inherit this instrument piecemeal, one hire and one reorganization at a time, and discover its actual shape only during an incident, an acquisition, or a subpoena. By then the shape is evidence, not design.

Zorg's methodology treats structural design as an engineering discipline rather than a facilitation exercise. Every decision right we assign, every escalation path we draw, and every audit trail we specify is built to survive contact with the event it was designed for. What follows are the six phases through which a structure moves from diagnostic to delivery, and the internal control applied at each one to keep the phase honest.

Delivery Phases

Phase	Duration	Deliverable
01 · Diagnostic	10 business days	Structural map of current reporting lines, decision rights, and escalation gaps, with named findings.
02 · Reporting Line Design	10 business days	Draft accountability structure with decision rights assigned to named roles, not named individuals.
03 · Escalation Path Engineering	10 business days	Dependency-mapped incident routes from first detection to executive notification, with a milestone deadline at each hop.
04 · Compliance Framework Build	15 business days	Standard operating procedures and control documentation mapped one-to-one against the new structure.
05 · Audit Readiness Review	5 business days	Structural simplification pass; documentation sufficient for external review without a walkthrough.
06 · Delivery	—	Board-ready package. Conversion to Retained Oversight Architecture available at close.

Phase durations total ten weeks for a single-entity engagement, run largely in sequence. Multi-entity engagements parallelize phases 01 through 03 per entity, which is what moves total delivery time toward the fourteen-week upper bound quoted for a Structural Build.

Internal Controls

Source Verification Desk

Applied at Phase 01

No finding enters a diagnostic map on the basis of an interview alone. Every reporting relationship, decision right, and escalation gap named in a diagnostic is checked against a primary document (an org chart, a delegation of authority, a board minute) before it is written down. A finding with no matching document is logged as unverified, not omitted.

Credibility Verification Unit

Applied at Phase 02

Checks that a named accountable owner in a proposed structure actually holds the authority the structure assigns, rather than the title alone. A role that can be escalated to but cannot act is flagged before the design proceeds.

Reproducibility Control

Applied at Phase 03

An escalation path does not ship until it has been run against two independent incident simulations with matching outcomes. A path that resolves differently depending on who is on shift is not yet a path; it is a preference.

Structural Review Cycle

Applied at Phase 04, and quarterly under retainer

A plan-do-check-act cycle applied to the compliance framework itself, not to the people operating under it. When a control fails, the correction is made to the system that produced the failure. Individual performance is a separate conversation, held elsewhere.

Failure Premeditation Desk

Applied at Phase 05

Every structure is stress-tested against its own worst credible failure before delivery: the escalation path that misses its deadline, the decision right that is exercised by the wrong role, the audit that arrives before the documentation does. The structure is not signed off until it has a defined response to its own collapse.

Internal Audit of the Auditor

Applied continuously, reviewed at Phase 06

The function that reviews this methodology for the blind spots the methodology itself is not positioned to see. It reports structurally outside the delivery team that built the engagement under review. Zorg does not recommend applying this control outside a retained engagement: structures reviewed under it convert to Retained Oversight Architecture at roughly twice the base rate, which is reason enough that some clients request it anyway.

Scope

This methodology applies uniformly regardless of the entity requesting it, including portfolio companies under common ownership and entities whose own oversight function is core to their product line. Zorg evaluates a structure's internal consistency: whether the decision rights, escalation paths, and audit trails it specifies would survive the event they were built for. Zorg does not evaluate, and is not asked to evaluate, the reason a structure was requested.

Zorg - J.F. Zorg - Subcommittee Testimony - Everything Group