A multi-stakeholder approval chain that didn't collapse under its own complexity Manager creates, Finance approves budget, HR approves headcount — at any point either can request changes, raise queries, or reject. The challenge was making this feel like a guided conversation, not a bureaucratic obstacle course.

​

The solution: a discussion and objection system built directly into the approval flow — query flags with severity levels, shared conversation history, unread badges, and response status tracking. Every stakeholder always knows exactly where the request stands.

The org chart at the moment of decision, not elsewhere Finance and HR were approving job requests without seeing where the role sat in the company hierarchy. The org chart was embedded directly into the review interface — role position, band, and salary range visible at the point of decision. No individual employee names exposed.

Role-based access that reflected real trust boundaries Every permission boundary was a trust decision as much as a design decision. Managers see their team but not all employee contact details. HR and Managers toggle between administrative and personal views. The CEO sees strategic KPIs, not individual task tracking.

Design system before design Designing without a shared foundation across a large surface area with two designers would have created inconsistency that cost more to fix than to prevent. Components, spacing, typography, colour tokens, and interaction patterns were defined before a single hi-fi screen began. The system became the reference layer connecting design to implementation.

What a job post actually needed to be Once approved, HR needed to turn a request into a publishable post without writing from scratch every time. A drag-and-drop text block library — pre-defined blocks for culture, benefits, requirements, and policies — solved it. Applicants apply via a direct platform link so every candidate is tracked internally from first touch.