Tier two — capability architecture

Programs end.
Systems compound.

The measure of an architecture is whether it runs without its architect. Tier two builds the systems that make capability structural: leadership operating systems, competency and measurement architectures, and the certified internal communities that keep them alive.

This is the layer most organisations try to buy as a program and then rebuild eighteen months later. Built as an architecture, it is handed over, owned internally, and extended without me.

Train-the-Trainer Academy →How intelligence keeps it alive

60-day to multi-quarter · handover is the deliverable

What gets built

Four architectures.

Leadership

Leadership operating systems

Designed from a blank page: the decisions leaders at each altitude must make well, the behaviours that produce them, and the measurement that proves it moved.

Multi-quarter →
Measurement

Competency & measurement architecture

Competency identification through to observable indicators, rubrics, pre/mid/post evaluation and the governance that keeps calibration honest.

Per function →
Internal capacity

Trainer certification systems

A certified internal facilitator community under manager-calibrated rubrics, so facilitation is built rather than rented in perpetuity.

60 days →Practice

Play Labs™ licensing

The methodology licensed to consultancies, partner networks and internal teams who want to deliver it themselves. Referral, co-delivery or full licence.

Application →
The licensing principle

Licensed, never handed over.

Program IP is licensed per cohort or annually, with facilitator certification billed separately. Editable source is never handed over for a one-time fee.

That is not a commercial trick. A program whose source has been handed over drifts within two cohorts — the anchors soften, the hard scenarios get cut, and the measurement quietly disappears because it is the most uncomfortable part to run. Licensing keeps the designer in the room every time a cohort runs, which is the only reliable way the architecture survives contact with a calendar.

Where an organisation genuinely wants to own and extend the asset, that is Work Intelligence — where the ontology, the labelling protocol and the evaluation harness are designed to be handed over in full.

Build it once.

An architecture that needs its architect is a dependency, not a system. Every engagement at this tier is designed around the handover.

See the portfolio →

Four tiers, scoped by depth