01 / Context
Five autonomous engineering pods were shipping five completely disconnected user experiences.
Smart Manager powers enterprise restaurant operations through five primary capability domains: Labor, Reporting, Inventory, Sales, and Admin—each staffed by an autonomous engineering squad with its own PM. Each pod built localized optimizations: settings lived at four different menu depths, and reporting pulled data using incompatible schemas. What looked like rapid squad velocity was quietly fracturing the product experience for 10,000+ restaurant managers.
02 / The Shift
- • Disjointed navigation: General managers had to learn 5 different mental models to check labor vs inventory.
- • Weekly design reviews: Squads waited in bottleneck review queues to decide basic UI settings placement.
- • Incompatible schemas: Reporting metrics from labor and sales couldn't be reconciled on a single screen.
- • Universal reporting grid: Standardized dashboard, hybrid, and tabular views across all 5 capability domains.
- • Deterministic decision trees: Codified schemas allow engineers and PMs to position features without design tickets.
- • Load-bearing seam integration: Unified Smart Manager's recipe inventory depletion with Aloha Menu sales items.
Configuration hierarchy decision tree: the definitive schema used by all 5 squads to place settings without committee meetings.
03 / The Approach
Four operational governance frameworks that transformed inter-squad friction into compound velocity.
1. Cross-pod capacity modeling before sprint planning
Coordinating 5 pods required transparency into design capacity. Built a quarterly resource allocation model that mapped designer bandwidth across every epic and squad, resolving competing priorities before sprint planning began.
2. Unified inter-pod communication architecture
Defined how pod-to-pod data exchange and automated customer communications operate. Standardized email and push templates, event triggers, and data schemas so any pod could trigger notifications without engineering a custom stack.
3. Universal reporting grid and persona-based navigation
Reports pulled metrics from Labor, Inventory, and Sales, each formatted inconsistently. Established a universal report anatomy (dashboard, hybrid, tabular) paired with persona-based navigation to preserve context across deep drill-downs.
4. Cross-seam engineering: dissolving boundaries between Sales items and Inventory recipes
Personally designed the high-risk integration between Smart Manager's recipe inventory depletion and Aloha Menu's customer sales items. Engineered modular data patterns that let new capabilities plug in seamlessly without architectural refactoring.
04 / Impact
From multi-sprint negotiations to automated platform coherence across five engineering pods.
The governance frameworks became the permanent foundation for every subsequent cross-pod release. Labor, Reporting, Inventory, Sales, and Admin maintained their independent roadmaps while shipping against a unified configuration model, communications pattern, and reporting anatomy.
Unified Platform
Autonomous roadmaps aligned
Adopted Org-Wide
Comms, reporting, navigation
Delivery Velocity
Decisions codified in schemas
Platform Leadership Retrospective
When leading across autonomous squads, the frameworks become the deliverable.
Leading UX architecture across five independent pods cannot be managed by attending more meetings or running centralized approval queues. True organizational leverage comes from creating authoritative, self-service artifacts—configuration decision trees, reporting grids, and message schemas—that do the coordinating asynchronously so engineering teams can ship with velocity.