Value Flow
How does value flow from customer demand to a stocked shelf, and where does time die?
Value Stream Map
The page job is value-flow now: trace how demand becomes a stocked shelf, a catalogue promise, a POS transaction, and a Monday decision. The waste is not only labour. It is wait time, handoffs, rework, and decisions made before the signal arrives.
Crackerjack value stream
- Trigger — customer demand, supplier deal, stock movement, or catalogue cycle starts a value-flow decision.
- Step 1 — buying and supplier judgement selects the offer; buyer knowledge is real value, admin drag is waste.
- Step 2 — catalogue and price publication turns the offer into a customer promise; saleId must travel with the promise.
- Step 3 — store, POS, e-commerce, and replenishment execute the promise; stock mismatch creates customer trust loss.
- Step 4 — finance and marketing reconcile what happened; today the Monday number arrives Wednesday.
- Output — next catalogue, stock, margin, and buying decision should improve because the loop learned.
Value-stream metric: flow efficiency = cycle time / lead time. Crackerjack's first bottleneck is the Business Analysis weekly report because wait time and artifact handoffs delay the decision by 2-4 days.
Workflow Inventory — Where Time Dies
The Monday merchandising report still costs 7-13 hours per week, but the deeper wound is lead time: the answer arrives after the decision window. Stage 1 should increase flow efficiency by removing artifact handoffs from the highest-value stream first.
Wake-up pain: Monday report still 7-13 hours and the number cannot be trusted manually
Business Analysis weekly Monday-number report
ARTIFACTOwner: Finance + Owner/CFO
Hops: 7·Hours/mo: 7-13 hrs/wk
Catalogue saleId production + price publication
ARTIFACTOwner: Marketing + Buying
Hops: 7·Hours/mo: 16-31 hrs/cycle
Catalogue price loading + POS sync
ARTIFACTOwner: Finance + Operations
Hops: 7·Hours/mo: 5-10 hrs/wk
Store-level inventory replenishment (×15 stores)
HYBRIDOwner: Store Managers + Buying
Hops: 4·Hours/mo: 22-37 hrs/day
Buyer admin tax (60% of week)
HYBRIDOwner: Buying team
Hops: 7·Hours/mo: 72-120 hrs/wk total
E-commerce publishing + stock-by-store sync
ARTIFACTOwner: E-commerce / Marketing
Hops: —·Hours/mo: 10-20 hrs/wk
| # | Workflow | Owner | Hops | Hours/mo | Type |
|---|---|---|---|---|---|
| 1 | Business Analysis weekly Monday-number report | Finance + Owner/CFO | 7 | 7-13 hrs/wk | ARTIFACT |
| 2 | Catalogue saleId production + price publication | Marketing + Buying | 7 | 16-31 hrs/cycle | ARTIFACT |
| 3 | Catalogue price loading + POS sync | Finance + Operations | 7 | 5-10 hrs/wk | ARTIFACT |
| 4 | Store-level inventory replenishment (×15 stores) | Store Managers + Buying | 4 | 22-37 hrs/day | HYBRID |
| 5 | Buyer admin tax (60% of week) | Buying team | 7 | 72-120 hrs/wk total | HYBRID |
| 6 | E-commerce publishing + stock-by-store sync | E-commerce / Marketing | — | 10-20 hrs/wk | ARTIFACT |
Waste Classification
Stage 1 = eliminate knowledge-work waste before adding new features. Of 7 workflows, most lost time is not customer value creation:
Seven wastes applied to Crackerjack
- Waiting — Monday question waits until Wednesday for the reconciled answer.
- Transport — POS, e-commerce, catalogue, and finance data move by CSV, email, and spreadsheet.
- Rework — catalogue, price, stock, and margin views need manual reconciliation.
- Motion — buyers, finance, and store managers context-switch between tools to reconstruct truth.
- Inventory — open decisions pile up while weekly and fortnightly cycles keep moving.
- Over-processing — reports are hand-polished after the useful decision window.
- Defects — saleIds, stock views, and margin assumptions can be wrong at handoff.
Stage 1 attacks the largest delay in the value stream: Business Analysis. Once the Monday decision has Monday truth, Stage 2 can attack store-communication wait time and Stage 3 can attack buyer admin tax at the point of decision.
Value-Flow Automation Candidates
Current → Flow target → Instrument → Dependency
- Business Analysis manual 7-13 hrs/wk → Auto Monday-number with anomaly flagging → BI substrate (Metabase / Hex / Power BI Premium) → POS export feasibility confirmed
- Catalogue production + price-sync chain → Single Marketing-Buying sheet auto-loading Catalogue + POS + e-com in one payload → Integration layer on UC1 substrate → Catalogue Platform API access
- Store-Manager replenishment phone/email → Unified stock-position view per Store Manager with AI-recommended action → Store-Manager UI on UC1 (Stage 2) → UC1 live + Documentation Sprint
- FX exposure spreadsheet → FX Tracker with scenario modelling and hedge-cover recommendation → Scenario layer on UC1 (Stage 2) → Demand-forecast layer in UC1
- Buyer admin tax → AI-assisted Buyer Brief per supplier deal → RAG over supplier history (Stage 3) → Documentation Sprint complete + UC1/4/5 in production
Flow Efficiency Math
Capacity reclaimed matters, but only because it shortens lead time and raises flow efficiency. The target is not fewer human hours in isolation. The target is value reaching the next decision before the window closes.
Hours/week reclaimed by stage
- Finance + Owner Monday number — today 7-13 hrs/wk → Stage 1 Month 4 0-2 hrs/wk → Year 1 Month 12 0-1 hrs/wk
- Marketing time on catalogue post-mortem — today 4-6 hrs/cycle → Stage 1 1-2 hrs/cycle → Year 1 0.5-1 hrs/cycle
- Store-Manager replenishment comms — today 1.5-2.5 hrs/day → Stage 1 unchanged → Stage 2 Month 9 0.5-1 hrs/day
- Buyer admin tax — today ~24 hrs/wk per buyer → Stage 1 unchanged → Stage 3 Month 12 ~12-16 hrs/wk
- Aggregate FTE-equivalent reclaimed by Month 12: 2-3 FTE-equivalent of decision-velocity capacity — without hiring, without restructure
Done-When (Stage 1 Value Flow)
Stage 1 is done when: value flows through the Monday decision loop before the decision window closes. The Monday number arrives at 8am Monday for 4 consecutive weeks; the previous catalogue saleId ROI is reviewed by Marketing + Buying jointly within 48 hours of cycle-end; Finance owns the report (Dream team out of operations loop).
The numbers
- Number: 4 consecutive weeks of on-time Monday number
- Date window: Month 4 (Week 16 from kickoff)
- Owner: CFO + Finance Lead
- The Ops Director can name the day the Stage 1 milestone is hit — by calendar not by inference
- Schedule: approve the Week 16 milestone review with CFO; pilot the unified Monday report by Week 6 in dual-run mode