Flow mapping
Document the steps and decisions in the selected user tasks.
Optional analytics, advertising and case-study videos are off. Allow them all, or open settings to choose. Privacy policy

A buyer, partner and account user may need different routes through the same B2B platform. We map the chosen tasks and design screens for their actual states instead of assuming one polished view covers every journey. Norml Studio works with Jacksonville teams from its Florida office in Fort Myers.
A few clients we’ve worked with










Design flows, screens and interaction states that support a defined user task.
We do not have an office in Jacksonville, and the map is honest about it: the pin is our Florida office in Fort Myers, about 300 miles north of our Fort Myers office. The distance changes how easy it is to meet, not how the work runs.
Buyer, partner and account-user tasks are squeezed into one navigation pattern.
Empty, loading and error states were left out of the design.
Desktop screens are approved before anyone checks the mobile task.
Developers must guess how controls behave after a click or failed input.
The selected Jacksonville team workflows define which flows, screens and implementation states enter the design scope. We choose the journeys and user roles in scope, then design the information hierarchy, screens, interactions and states. The work may cover a website, dashboard or product workflow. Research and usability testing are specified separately when they need participants or data access.
Document the steps and decisions in the selected user tasks.
Arrange content and controls around the information users need at each step.
Design representative layouts and behaviours across the agreed devices.
Show validation, empty, loading and error states with implementation notes.
The output must explain behaviour, not just show finished screens.
User-flow maps for agreed tasks.
Responsive Figma screens and components.
Interaction and edge-state specifications.
Developer handoff notes and review criteria.
Our process
Agree users, goals and the workflows to design.
[ 01 ]Resolve steps, information and decisions before detailed screens.
[ 02 ]Create responsive screens and interaction variants.
[ 03 ]Document behaviour and review implementation where included.
[ 04 ]
“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”
Max TymoshynFounder & Architect
Get started