The Tatitatu team needed the system ready within a short time frame, as it would support their new outlet launch. This meant I had to analyze and design an end to end system for 9 user roles and over 15 moduls all within one month.

The challenge wasn’t just technical or time related it was also human and structural

Each department had its own spreadsheet logic, formulas, and recording habits. Unifying these differences required changing behaviors without disrupting familiarity the new system had to feel natural.

Together with the project manager and Tatitatu’s internal supervisors, we created a Business Requirement Document (BRD) based on system analysis

We conducted in depth interviews and live sketching sessions to map their existing workflows, identify pain points, and define functional requirements for each module. I also reviewed every spreadsheet and formula from COGS and payroll to bonus logic to understand how data flowed between departments.

We analyzed each feature by user type while I simultaneously built a design system to ensure efficiency and consistency during the high fidelity design stage. After every user interview, I discussed implementation details directly with the developer to ensure the logic could be realistically applied. Once a feature was finalized, I conducted regular usability testing.

Some key feedbacks that shaped the iterations included :

• Color differentiation for user roles. Users working in different outlets needed clear visual indicators for their respective roles.

• Instead of clicking “+” or “–” repeatedly, users can now add items instantly with a single tap, streamlining adding item.
  
  

After all features and user flows were finalized, I created a simple Product Requirement Document (PRD) that outlined which users could access which modules. This documentation helped both the development team and the client track progress and avoid misunderstandings.

Taking Over as Project Manager

When the project manager couldn’t continue until the end, I stepped in to keep the project on track. Even though I don’t have a coding background, I managed the team by doing check-ins every three days and setting clear goals for each feature delivery. During development, user error reports came in almost every day, so I made an error log spreadsheet to record where and what the issues were. This helped developers find and fix problems faster. After each fix, I rechecked all related modules to make sure no new bugs appeared elsewhere.