ERP Implementation Support

The team was tracking everything in Airtable—test cases, training, change management, stakeholder readiness, go-live tasks. But the base had been built reactively, one urgent need at a time. Every new phase got new tables. Every workstream built their own. The result: 150+ tables, data duplicated across dozens of places, and reporting that required someone to manually stitch together information from multiple sources just to answer basic questions.

I redesigned the base around entities instead of phases. Instead of five separate test case tables for each testing round, one table with a phase field. Instead of scattered tables for risks, issues, and change requests, one unified register. The data didn't change—but now it lived in 25-30 connected tables instead of 150+ siloed ones. Views handled the filtering. Dashboards gave leadership real-time visibility. And the structure finally matched how the project actually worked, not how it had accumulated over time. The design also connects to an enterprise employee roster as a synced dataset—one source of truth for people, linked to tasks, responsibilities, training completion, and workstream assignments. Update the roster once, and it flows everywhere.