User and task research
Review stakeholder input, existing research, product behavior, and user feedback to define the tasks the interface must support.
Norml designs the journeys, screens, and interface systems people use to complete tasks. We work on B2B websites, dashboards, and web products, connecting user requirements with layouts, interactions, and developer-ready designs.
Book a callA product needs a clear sequence for onboarding, searching, or completing a workflow.
Different user roles need different access, actions, and views.
An interface needs loading, empty, error, and success states alongside its main screens.
New features need to fit an existing component system.
Developers need responsive rules and interaction details before implementation.
We agree the users, tasks, screen inventory, and available evidence before detailed design. Research, usability testing, and design QA are included according to the needs and access available for the project.
Review stakeholder input, existing research, product behavior, and user feedback to define the tasks the interface must support.
Organize screens, navigation, content, and role-specific journeys so the required actions have a clear sequence.
Explore screen structure, content priority, and interaction patterns before committing to visual detail.
Design the approved screens with responsive behavior and the loading, empty, validation, and error states they require.
Connect key flows in an interactive prototype and use agreed review or testing sessions to identify confusing steps.
Prepare reusable components, variants, tokens, interaction notes, and implementation reviews for the development team.
The agreed scope identifies which of these deliverables your project needs.
An agreed user-task and screen inventory.
Information architecture and user-flow diagrams.
Wireframes for the journeys in scope.
High-fidelity screens and interface states.
A prototype and testing findings where included.
A Figma component system and developer handoff.
Our process
Review the product goals, user roles, current behavior, technical constraints, and evidence already available.
[ 01 ]Organize the journeys and screen structure, including decision points and edge cases.
[ 02 ]Develop wireframes and visual screens using the approved brand and interaction direction.
[ 03 ]Walk through key flows, collect user or stakeholder feedback, and resolve issues within the agreed scope.
[ 04 ]Document components, states, and responsive rules, then support implementation review where included.
[ 05 ]