Skip to main content

Value Stream

Template: Value Stream Map | Tight Five: Principles

Where does value flow — and where does time die?


The Stream

Two value streams run in parallel. Meta sells the dream. Docs build the engineering.

Meta Pipeline

Trigger: idea captured (friction noticed, question emerges)

StepCycle TimeWait Time%C&AWaste
ICP — who needs this?2h060%Often skipped entirely
Capture — raw idea into hopper30mdays-weeks80%Ideas wait in hopper indefinitely
Transform — four voice drafts4h1-2 days70%Over-processing — drafts too long
Qualify — score, merge, craft2h050%Rubber-stamped under load
Question — iterate or release?30mdays40%Decision paralysis
Ship — publish, distribute1h080%LinkedIn posts not always created

Total cycle time: ~10h Total lead time: 1-3 weeks Flow efficiency: ~5-10% (typical)

Bottleneck: Wait between Capture and Transform. Ideas sit. The hopper is inventory.

Docs Pipeline

Trigger: gap noticed (missing page, broken link, weak connection)

StepCycle TimeWait Time%C&AWaste
Research — understand the territory1-4h070%Sometimes skipped — writing before understanding
Draft — write the page1-2h060%Pages too long, not following flow pattern
Link — wire into architecture30m050%Linking as afterthought, not during writing
Review — content-flow gates30m040%Gates eyeballed, not mechanically checked
Push — CI validates5m0-1h90%MDX errors caught late

Total cycle time: 3-8h Total lead time: 3-8h (minimal wait — this is the strength) Flow efficiency: ~80% (good)

Bottleneck: Quality of linking. Pages created but edges not drawn.


Seven Wastes

WasteWhere It Shows UpSeverity
WaitingIdeas in hopper between Capture and TransformHigh
OverproductionFour voice drafts when two would sufficeMedium
ReworkPages edited multiple times for flow violationsMedium
MotionContext switching between meta and docs workLow
Inventory14 ideas in hopper, 6 shippedHigh
Over-processingPreachy editorial that gets cut anywayMedium
TransportHandoff between skill invocation and manual executionLow

Flow Efficiency

StreamCycle TimeLead TimeEfficiencyTarget
Meta pipeline10h1-3 weeks5-10%25%+
Docs pipeline3-8h3-8h~80%Maintain
Cross-linking30m/pagevariesUnknownMeasure

The docs pipeline is efficient. The meta pipeline has a wait-time problem. The fix isn't speed — it's reducing inventory (fewer ideas in hopper, faster to ship).


Gate: Bottlenecks identified. Proceed to Dependencies →