One problem. Two design directions. Which would you choose?
For AEGIS / 001.05 . Traffic Operations, we explored two approaches to the same challenge: helping city operators understand congestion, incidents and network-wide disruptions without overwhelming them with information.
Both solve the same operational problem. Different approaches to hierarchy and interaction.
If you were behind the control desk . Option A or Option B?
Just finished building a Salon Booking Management System!
The goal was simple: make appointment management easier for salon owners and reduce the manual work involved in handling bookings and reminders.
The system connects the complete workflow in one place:
1 Customer makes a booking
2 Booking gets confirmed
3 Owner sees it on the dashboard
4 Upcoming appointments are organized clearly
5 Reminders help the owner stay on top of appointments
One of the key things I focused on was making the experience simple, clean, and easy to understand, while keeping the workflow practical for a real business.
This project helped me think beyond just building screens — and focus more on the actual business problem, user flow, and overall product experience.
Excited to keep improving it and turn it into an even more polished product.
What happens after a customer requests a home service?
Booking is only the beginning. The real challenge is managing everything that happens afterward — operations, crew assignment, service progress, and completion.
So I built QuickFix around the operation behind the service: