FILE // METHODCYCLE // OPEN

The method goes to work here first.

Diagnose, Position, Shape, and Transform are not four boxes on a consulting slide. They are controls applied to the business that already has to perform.

METHOD // APPLIEDREAD // IN ORDER

Not four boxes. A working cycle.

The controls are applied to the business that already has to perform. Each movement changes the conditions for the next.

  1. CONTROL 0101DiagnoseCONSTRAINT FIRST

    Find the constraint before the tool.

    The IMO is metered as an operating system: people, cases, decisions, handoffs, data, delay, and responsibility. Symptoms do not receive software. The root constraint receives a diagnosis.

    FAILURE CONDITION // DIAGNOSE
    A wrong diagnosis makes every correct build irrelevant.
  2. CONTROL 0202PositionBOUNDARY FIRST

    Put capability where consequences are understood.

    AI placed without context creates confidence in the wrong output. Positioning defines where a tool belongs, what information it may use, where a human must intervene, and what cannot be delegated.

    • AEnvironment

      Understand the people, process, data, and obligations surrounding the tool.

    • BBoundary

      Name what the system may decide, assist, surface, or never touch.

    • COwner

      Keep a responsible person attached to every consequential output.

  3. CONTROL 0303ShapeOUTPUT FIRST

    Structure output so the operation can hold it.

    Output no one understands is output no one owns. SP+ must make work inspectable, correctable, and transferable. The system serves the operator. It does not become an unchallengeable black box.

    Output
    Legible
    Decision
    Traceable
    Ownership
    Human-held
  4. CONTROL 0404TransformEVIDENCE FIRST

    Change the operation, not the vocabulary.

    AI-powered means a feature was added. AI-native means the architecture of the work changed. Transformation is not declared when SP+ runs. It is demonstrated when the operation works differently because SP+ is part of it.

    FIELD TEST // TRANSFORM
    The deliverable must survive contact with the business.
  5. CONTROL 05↺Re-diagnoseNEXT STATE

    Secure the next state.

    Every prospective system eventually becomes part of the operating foundation. Once it does, the work is measured again. New constraints surface. The next cycle begins without pretending the future has stopped moving.

    RETURN PATH05 / 01
    RE-DIAGNOSEDIAGNOSE
    See the active application