Noma had to work for two very different users at the same time. Employers needed a fast way to post shifts, review candidates, and keep staffing moving. Workers needed a simple way to scan pay, distance, schedule, and shift details from their phones. If either side felt slowed down or confused, the platform would lose momentum.
I took Noma from wireframes through build, with the experience centered around the actions that mattered most. That meant clearer paths for both audiences, fewer unnecessary steps, tighter calls to action, and a stronger mobile-first structure. Every screen was designed to make the next move easier to understand and easier to take.
Clarified the main paths so employers could post shifts faster and workers could get to live opportunities without sorting through extra choices.
Shortened onboarding and job-posting flows so new users could get into the product with less friction, especially on mobile.
Reworked job cards and filtering so pay, location, shift timing, and key details were easier to scan before someone committed.
Added stronger mobile calls to action and cleaner hierarchy so users always knew what to do next from sign-up through shift acceptance.
Gary needs to fill shifts quickly, review available workers, and keep operations moving without wasting time.
Olivia needs to find the right shift fast, understand the important details right away, and take action easily from her phone.
We mapped the core journeys early so the product stayed easy to understand before visual design entered the picture. The wireframes focused on the highest-value actions first: posting shifts, reviewing opportunities, and moving each user to the next step without confusion.
Once the structure was set, the product moved into build as a cleaner, more responsive experience designed for real use. The final interface made actions easier to find, content easier to scan, and the overall flow smoother across desktop and mobile.
Noma was designed with phone behavior in mind from the start. That meant larger tap areas, clearer content blocks, cleaner cards, and faster paths through the flows users relied on most.
We solved the user paths first. Visual design only worked once the product logic was easy to follow.
The mobile version was not a cut-down desktop view. It was the starting point.
Every screen was designed to shorten the distance between arrival and decision.
The work was shaped around real employer and worker behavior, not internal guesses.
Most teams split product thinking from build. That usually creates gaps, slower feedback, and a final product that drifts from the original intent. I handle both, which means the product stays consistent from strategy through launch.
Start With a Free UX Audit
