Fewer support requests
Designing the states people actually hit — empty, loading, error, permission denied — removes the questions your team answers by hand later.
Design complete school journeys with clear next steps.
We prototype programme discovery, open-day enquiries and practical-information tasks. Form validation, unavailable events and external handoffs are part of the design, with clear distinctions between an enquiry, a booking and a completed application.
A few clients we’ve worked with
What we do
UX/UI design for schools: Task mapping, Interface states, Handoff specification.
Decisions that shape the work.
Which tasks belong on the public website?
What does each confirmation actually establish?
What interface decisions cost when nobody makes them.
Interfaces are not decorated; they are decided. When the tasks, roles and states are never agreed, they get invented during development — one screen at a time.
Development stops guessing
An agreed screen inventory and behaviour means engineers implement decisions instead of making product decisions in code review.
The product survives its next feature
Patterns designed once hold when the roadmap adds a role, a plan tier or a new workflow.
UX/UI design: scope of work.
The brief records the website scope, approved source material and responsibilities for review.
Task mapping
Separate prospective-family actions from routine information and existing-student destinations.
Interface states
Design menus, filters and forms with empty, error and completion behavior.
Handoff specification
Record supported external-system boundaries and what visitors should expect next.
What clients say.
Reviews from the companies we have built and maintained websites for.
Read every review on Clutch“We didn’t choose them to be impressed — we chose them because we knew they’d deliver high-level results with no risk. As a CTO myself, that’s exactly what I look for in a long-term partnership.”
“And, you know, the great part about the fact that you hit the goal, it's not that you had to compromise anything that you were doing, because, honestly, the end result far exceeded what we could have imagined.”
“I would just say that you deliver on quality … I just thought we clicked, and you delivered what we were looking for.”
“Norml Studio's professionalism and responsiveness were impressive.”
What you receive.
The agreed engagement produces the following artifacts.
- 01
Audience journey maps.
- 02
Interactive Figma flows.
- 03
Form and navigation state specifications.
Our process
How the work runs.
Map the tasks
Review common family questions and responsible staff routes.
[ 01 ]
Prototype interactions
Use synthetic examples to cover ordinary and unsuccessful actions.
[ 02 ]
Review completion
Confirm each message matches the actual provider or staff workflow.
[ 03 ]The people who do this work.
No account layer between you and them. These are the Norml specialists this work runs through.
Let's chat
“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 startedUX/UI design for schools: questions.
Does an enquiry confirmation mean a place is offered?
No. The interface must distinguish receipt from admission or enrolment decisions.
Can the work cover a student portal?
A portal needs a separately defined scope, users and data permissions; it is not assumed in the public website brief.
Website 2.0 combines strategy, design, development and launch in one engagement.