goop
operating field guide
information · decisions · interfaces
back to the guide ↗

an industrial engineering perspective

how work flows.
where it may wait.

A swimlane map: actors on the left, phases from left to right. Branches show parallel work; diamonds mark decisions and convergence points.

model to validate

Activities draw on official sources and the Notion directory. Routes, decision gates and risks are consulting hypotheses; no bottlenecks or lead times have been measured.

from agreement to delivery

full-screen process canvas ↗click a step to explore its detail ↗ · arrows show the handoff
activity decision / convergence information risk to validate
    Phases are not drawn to a time scale. Lanes represent functional actors, not reporting relationships. “No” sends work back for review; return paths show potential rework.

    the system around the flow

    coordination also
    needs support.

    leadership and strategy

    Priorities, decisions and escalation. The official job posting assigns strategy and decisions to both co-CEOs; it does not specify every operational approval here.

    official source ↗

    people & legal

    Capacity, working agreements and review boundaries. Distinguish legal approval from content acceptance or budget approval.

    explore functions ↗

    IT & engineering

    Data, access and integrations. A handoff across teams needs consistent definitions and versions to move between tools.

    explore functions ↗

    how to test a hypothesis

    observe the wait.
    measure the handoff.

    To confirm a bottleneck, follow real cases. Record when a complete input arrives, when a decision is made and how often the work returns.

    decision queue
    Time from a complete case to a decision; number of pending cases.
    incomplete input
    Which document or data is missing, and which team must complete it.
    rework
    Review rounds, rejection reasons and material versions.
    synchronization
    Gap between the first and last inputs needed to release a deliverable.
    how to read sources and decision rights

    “Supported activity” means a source describes that function or capability. It does not establish that the proposed route, owner or sequence is the current process. Each diamond distinguishes who prepares a decision from who should make it; the final owner remains to be confirmed.

    The guide uses the official executive job posting ↗, the editorial policy ↗, the contact channels ↗ and the department directory ↗. Each profile links its evidence and identifies what is proposed.

    expanded view · esc to returngoop