Tribal knowledge isn't a system.
The café ran almost entirely on tribal knowledge — unwritten procedures, verbal training, and routines that existed in employees' heads. This worked when the same people were always there.
Inconsistency was the symptom. Without written SOPs, a defined training structure, and clear role accountability, the quality of execution varied entirely based on who was on shift.
A centralized operations system replacing tribal knowledge with documented structure.
I built a full operational infrastructure — written SOPs for every major process, a structured training roadmap, clearly defined shift roles, daily workflow guides, and an accountability system.
The goal was simple: the business shouldn't rely on any one person's memory to run correctly. Every process was written down.
Note: Specific operational details have been generalized to protect business confidentiality. The system was built and implemented at the café.
What's inside the system.
- SOPs for opening, closing, food prep, cleaning, and customer service protocols
- New hire training roadmap with structured week-by-week onboarding and competency milestones
- Shift role definitions clarifying responsibilities for each position at every daypart
- Daily workflow guides for each shift: task sequences, timing, and handoff procedures
- Accountability procedures including daily checklists and performance standards
- Escalation framework documenting how to handle exceptions and common problem scenarios
- Master operations document serving as the single source of truth for how the business runs
What was built.
The SOPs, training materials, and workflow guides from this project are proprietary to Lotus Café and aren't shared publicly out of respect for the business. What I can show is the structure of what was built:
Consistency, not dependency on any one person.
Before the system, the café ran on institutional memory — procedures lived in people's heads, training was verbal, and consistency depended on who happened to be working. A new hire's experience varied entirely based on who showed them the ropes. There was no fallback when experienced staff were off.
The completed operations system gave the business a single written source of truth: SOPs for every key process, a structured week-by-week onboarding plan, defined shift roles for each daypart, and daily workflow guides from open to close. New staff could be onboarded from documentation rather than word of mouth, and the quality of execution no longer depended on which employees were on shift.