Approach

The work goes best when direction and delivery are one track, same owners, same constraints, fewer translation losses. Decisions land better when they are made with delivery, operations, and change over time in mind.

03.1 ENGAGEMENT SHAPES

Common engagement shapes

Assessment and direction

Used when a platform exists but clarity is missing. The work maps what’s there, surfaces constraints, and sets an executable direction without forcing a rebuild.

ES-01 ASSESSMENT

New platform build

Used when something new needs to exist and the boundaries aren’t defined yet. The work clarifies the system, establishes the production path, and ships the first real version.

ES-02 NEW BUILD

Replatform / rebuild

Used when incremental change is no longer working. The work defines a migration strategy, reduces risk, and replaces the system without unnecessary disruption.

ES-03 REPLATFORM

Internal systems and operational tooling

Used when teams are blocked by workflows, tooling, or fragmented systems. The work clarifies the operational model and produces tools that reduce day-to-day friction.

ES-04 INTERNAL

03.2 ENGAGEMENT PRINCIPLES

How the work stays coherent

EP-01

Integrated direction

Direction is set by considering concept, structure, and feasibility together. This keeps the work anchored to what can ship with the smallest number of handoffs.

EP-02

Unified direction

The work stays under one direction across phases. That reduces translation errors, protects intent, and keeps the final result coherent.

EP-03

Production-informed decisions

Constraints are surfaced early. Tradeoffs are made explicitly. The work is shaped with a clear view of how it will be delivered, operated, and extended.

EP-04

Ownership returned to teams

Engagements end with a clean handoff: decision records, system notes, and a team that can run it.

03.3 DELIVERABLES

What you get

A clear system direction (what will be built, and why).
Boundaries and structure that support change (services, data, interfaces).
A production path (sequencing, constraints, and decision records).
Documentation intended for real internal ownership and operation.
A clean ending: the system is understandable, operable, and maintainable.