Organization ERP
Oorah runs 10 departments, from camps and events to tuition and matchmaking, on 5 aging legacy systems. We audited them together, then designed one ERP department by department, on a shared records system and one design system.
- Client
- Oorah
- Product
- Organization-wide ERP, shared records
- Departments
- 10, each with its own workflows
- Scope
- Collective audit, UX architecture, design system
What we walked into
Oorah runs 10 departments, including TorahMates, tuition, a boys camp, a girls camp, a matchmaking site and an events team. Each had grown its own way of working, spread across 5 very old legacy systems that didn’t share records.
How we worked
First, a collective audit across every department, to see what they shared and how to build it in a way that scales. Then department by department, designing the features each one needs: complex financial flows, ticketing, event planning, tasks and department homepages. Hundreds of workflows were rethought and merged along the way.
Ten departments, one set of records, one way of working.
The goal for the whole organization
Where it landed
One ERP for the whole organization. Every module sits on a shared global records system and one inclusive design system, so a camper, a family or a staff member is the same record everywhere.
10 departments on one shared records system.
Every department got the modules it needs. Underneath, the same people, records and design system connect them all.
- TorahMates
- Tuition
- Boys camp
- Girls camp
- Matchmaking
- Events
- +4 more
- Finance
- Ticketing
- Event planning
- Tasks
- Homepages
- Design system