Operations and workflow design
SOP & Workflow Documentation System for Project Joy
Project Joy, a mission-driven organization, had important workflows that depended too heavily on individual memory and experience. Staff knew how to move the work forward, but different versions of the process created inconsistent execution, unclear handoffs, and an onboarding burden for new team members.
Approach
EBS framed the challenge as a systems issue, not simply a documentation problem. Writing down the process as it existed would have preserved the same friction, so the work began by understanding how responsibilities, decisions, information, and tools moved through the organization in practice.
We proposed a four-part method: discover how the work happened, clarify gaps and decision points, document the agreed process, and prepare staff to use and maintain it. The goal was to create clearer and more consistent operating practices while preserving the practical knowledge staff had already developed.
How we worked with the team
We started with the team's lived experience of the work. Staff knowledge was treated as an organizational asset: the starting point for understanding what happened in practice, where approaches differed, and which informal workarounds had emerged to keep the work moving.
Together, we examined the triggers, owners, handoffs, approvals, tools, and exception paths within each priority workflow. Process variation was treated as useful information about where the system needed clarification, rather than as evidence that individual staff members were the problem.
Once the team agreed on how the work should move, EBS translated those decisions into process maps, SOPs, role and ownership definitions, checklists, job aids, and reusable templates. The documentation was designed around day-to-day use, so staff could find the next step, understand who was responsible, and know what to do when the usual process did not apply.
The final phase focused on adoption and stewardship. Staff were prepared to use the tools, and the organization had a clearer foundation for maintaining and improving the documentation over time. Because the process was clarified with the people closest to the work, the resulting system reflected operational reality rather than an imposed version of it.
Results
Before the engagement, critical knowledge lived largely with individuals, process steps varied, and handoffs depended on memory or knowing whom to ask. Afterward, the organization had visible workflows, defined ownership, documented expectations, and shared tools that supported more consistent execution.
The concrete results included process maps, agreed SOPs, role and approval definitions, checklists, job aids, templates, and an approach for moving the documentation into use. Staff had a common reference point for recurring work, and new team members had clearer tools for learning how responsibilities and decisions fit together.
The work reduced the organization's dependence on informal knowledge and gave the team a more sustainable way to teach, follow, review, and improve critical processes. That shared operating foundation made it easier to support onboarding and adapt the work as responsibilities, staffing, and organizational needs changed.