BetterFleet Workflow Map¶

This is the compact visual companion to the Product Development System. Use it to orient people quickly, then drill into the process guides only when the next question requires detail.

%%{init: {
  "theme": "base",
  "themeVariables": {
    "fontFamily": "Inter, -apple-system, BlinkMacSystemFont, 'Segoe UI', sans-serif",
    "primaryColor": "#FFFFFF",
    "primaryBorderColor": "#111827",
    "primaryTextColor": "#111827",
    "lineColor": "#4778E8",
    "tertiaryColor": "#FFFFFF",
    "clusterBkg": "#FFFFFF",
    "clusterBorder": "#A7C2FF"
  },
  "flowchart": {
    "curve": "basis",
    "nodeSpacing": 42,
    "rankSpacing": 48,
    "htmlLabels": true,
    "padding": 16
  }
}}%%
flowchart TB
  Signal["<b>SIGNAL</b><br/>Slack / support / customer<br/>product / repo"]
  Triage["<b>TRIAGE IN LINEAR</b><br/>one issue<br/>enough context<br/>HoE + Lead Product Manager decision"]
  Backlog["<b>BACKLOG / NOT NOW</b><br/>clear state<br/>owner<br/>missing decision visible"]

  subgraph Product["GOVERNED PRODUCT"]
    direction TB
    Index["<b>INDEX</b><br/>challenge"]
    Project["<b>LINEAR</b><br/>project spec"]
    Issues["<b>LINEAR</b><br/>issues"]
  end

  subgraph Other["OTHER RESPONSIBLE PATHS"]
    direction LR
    Bug["<b>SUPPORT/BUG</b>"]
    Incident["<b>INCIDENT</b>"]
    Fix["<b>SMALL FIX</b>"]
    Docs["<b>PROCESS/DOCS</b>"]
  end

  Active["<b>ACTIVE WORK</b><br/>one current Linear item<br/>owner / status / blockers"]
  Repos["<b>REPO EVIDENCE</b><br/>code / tests<br/>ADRs / docs / notes"]
  Handoff["<b>HANDOFF</b><br/>evidence<br/>current Linear state<br/>remaining gaps"]

  Signal --> Triage
  Index --> Project --> Issues
  Triage --> Product
  Product --> Active
  Triage --> Other
  Other --> Active
  Triage -.-> Backlog
  Active --> Repos --> Handoff
  Handoff -.-> Active

  classDef box fill:#FFFFFF,stroke:#111827,color:#111827,stroke-width:1px
  classDef intake fill:#F8FAFC,stroke:#111827,color:#111827,stroke-width:1px
  classDef product fill:#EEF5FF,stroke:#111827,color:#111827,stroke-width:1px
  classDef other fill:#FFF8ED,stroke:#111827,color:#111827,stroke-width:1px
  classDef active fill:#ECFDF5,stroke:#111827,color:#111827,stroke-width:1px

  class Signal intake
  class Triage,Backlog other
  class Index,Project,Issues product
  class Bug,Incident,Fix,Docs other
  class Active,Handoff active
  class Repos box
  style Product fill:#FFFFFF,stroke:#A7C2FF,stroke-dasharray:3 3,color:#111827
  style Other fill:#FFFFFF,stroke:#A7C2FF,stroke-dasharray:3 3,color:#111827
  linkStyle default stroke:#4778E8,stroke-width:1.2px

Reading The Map¶

• Start at the top: work can arrive through conversation, support, customer commitments, product goals, or direct repo maintenance.
• If the work is new or unowned, capture it as one Linear triage issue with just enough context to decide the path.
• Governed product work follows Index -> Linear Project -> Linear Issues -> Repos only after triage makes it governed product work.
• Support/bug work, incidents, small fixes, and process/docs maintenance take their responsible path, while keeping Linear accurate where tracking is needed.
• Day-to-day work stays anchored to one active Linear item that matches the work actually happening.
• Backlog work is visible and clear, but it is not delivery-ready just because it exists.

The Product Development System explains the model when this visual summary needs interpretation.