The GreenBox Story · Series
Scaling the Machine
The model works. GreenBox is growing toward 5,000 subscribers, expanding to a second region, and the team is growing too. Time to build the foundations that scale.
Domain-Driven Design: Drawing the Boundaries
The codebase is becoming a monolith — and then Dave calls about Freshly. Charlotte helps the team draw boundaries before everything tangles further.
Decision Tables: Making Maya's Brain Explicit
The substitution rules Maya carries in her head need to scale to a growing team. Watching someone else learn them feels like letting go of the farm.
Architecture Decision Records: Why We Did It That Way
A new developer trusts the LLM's confident-but-wrong explanation of why billing works the way it does. Nobody can explain because nobody wrote it down.
Value Stream Mapping: Finding Where to Focus
Fifteen people, two cities, and lead time has tripled. The team maps where value flows and where the process is bleeding time.
Wardley Mapping: Build, Buy, or Borrow?
Should GreenBox build its own delivery tracking or use a third party? When building is cheap, the calculus changes — but not always in the direction you'd expect.
Two Squads, One Direction
Perth changes an API without telling Melbourne. Three customers get allergen-violating boxes. Mrs Patterson calls, and she's worried.