01 / The challenge
One admin panel, several operational roles.
Wallet Codes needed one place to manage sales, customers and products for its game-credit platform. The challenge was to keep routine work clear without stripping out the detail that administrators needed.
I worked with the lead developer and product owner to understand those functions, then kept managers, salespeople and developers involved as the interface evolved.
02 / Collaboration
Keep the feedback loop close to the work.
We used weekly sprints rather than a longer iteration cycle. That gave the team a regular point to surface technical constraints, review changes and adjust the interface.
Understand the technical model
Work through sales, customer and product functions with the product owner and lead developer before resolving the interface.
Review with the people using the system
Bring feedback from managers and salespeople into the same conversation as implementation constraints.
Make handoff a shared reference
Use Zeplin to carry interface detail into development.
03 / Interface evidence
An overview is useful when the detail stays within reach.
Reporting, payment settings and user management each demand a different level of detail. The screens below show how those jobs were handled within the same admin interface.
- Reporting context
- The period controls sit with the chart, keeping the reporting window visible.
- Task navigation
- The left rail provides access to the admin functions without competing with the central report.
04 / Delivery
A connected interface and a practical route to delivery.
The deliverables were admin-panel interfaces covering reporting and management tasks, developed through weekly review and prepared for engineering handoff.
The central lesson was the value of shared understanding: a useful admin interface depends on how well the designer understands the work of the people operating it.
Next project