Volume 01 · Field Notes

Brief executive observations from the work.

Field Notes are short editorial entries — written in the course of perspectives and operating model work, published when an observation is sharp enough to stand on its own.

  • FN-01

    The Hidden Cost of Platform Fragmentation

    Most platform debt is paid in the coordination tax executives quietly absorb to keep fragmented systems delivering a coherent enterprise.

    Enterprise Architecture
    In Development
  • FN-02

    Capability Maps Before Technology

    Naming what the enterprise must be able to do — before naming the systems that will do it — is the single most consequential act of restraint in a transformation program.

    Capability Maps
    In Development
  • FN-03

    AI Is Becoming an Enterprise Capability

    AI matures into the institution the moment it becomes a capability with owners, platforms, and a governance cadence — rather than a portfolio of projects.

    AI Operating Models
    In Preparation
  • FN-04

    The Difference Between Strategy and Operating Model

    A strategy describes the world the enterprise intends to win in. An operating model describes the enterprise that can actually win there.

    Operating Models
    In Preparation
  • FN-05

    Enterprise Architecture Is an Organizational Design Problem

    Architecture decisions that look technical almost always resolve, on inspection, to questions about who is accountable for what. The diagram follows the org chart.

    Enterprise Architecture
    Research Underway
  • FN-06

    Engineering Compounds Or It Decays

    Engineering organizations evolve in one of two directions. With deliberate investment in the conditions that make capability compound, they grow into institutions; absent that investment, they revert to delivery shops.

    Engineering Leadership
    Research Underway
On Field Notes

A field note is an executive observation. Each one is published because it is useful to a leader presently holding the same question.