Home About Case Studies Hire Me Contact
Currently available for select engagements

Hire UI/UX Designer for Schools
Senior, direct, no layers

Interfaces for education that people understand on first use: learners, parents, applicants, and staff.

15+
Years Experience
100+
Projects Delivered
6
Countries Served
$25M+
Revenue Enabled
Schools — UI/UX Designer

A senior ui/ux designer for schools

A UI/UX designer makes the digital products of a school usable by the people who actually use them: applicants who are unsure, parents in a hurry, pupils on phones, and teachers and office staff under time pressure. For schools and school groups, the cost of confusing design is concrete: abandoned applications, calls to the office for things the screen should have explained, and staff workarounds that bypass the system entirely. The work is research first: watching real users, finding where they stall, and redesigning flows around their tasks, with accessibility built in rather than added later.

Engagements start with a conversation about the actual job to be done, not a package. Book a free discovery call and we will test the fit before any scope is agreed.

What you get

What this engagement covers for schools

  • User research — Interviews and observation with applicants, pupils, parents, and staff to find where current flows actually fail.
  • Journey and flow design — Redesigned journeys for applying, enrolling, checking progress, and getting help, with dead ends removed.
  • Wireframes and prototypes — Testable prototypes for the highest-traffic flows, proven with real users before anything is built.
  • Accessible visual design — Clear typography, contrast, and touch targets, with keyboard and screen-reader support as standard.
  • Design system — Reusable components and patterns so future pages stay consistent without redesigning each time.
  • Handover to developers — Specifications, states, and edge cases documented so developers build what was tested, not an approximation.
Systems you already run

Built around the tools schools actually use

Most schools run a student information system such as PowerSchool or Blackbaud at the centre, with Google Classroom or Schoology for classwork, Clever for single sign-on, and tools such as ClassDojo or Seesaw for parent communication in younger year groups. Finance and billing often sit in a separate system such as FACTS, and admissions enquiries may live in spreadsheets or an inbox before they ever reach the SIS. Any new build has to respect that split: staff will not adopt a tool that forces them to re-enter the same pupil data twice, and parents will not use a portal that contradicts what the school office tells them. Design work is grounded in your existing platforms and their constraints, so prototypes reflect what your systems can actually do, and the design system is built to survive inside your real product rather than as a standalone showcase.

The practical rule is simple: new work should reduce the number of places staff have to look, not add another one. That is why integration, permissions, and handover are part of the scope from the start, rather than items discovered after launch.

How it works

From kickoff to delivery for schools

  1. Research real users

    Interview and observe the people who use the product, and record where they stall, in their own words.

  2. Redesign the priority flows

    Redesign the flows that lose the most people first, and prototype them for testing.

  3. Test and refine

    Test prototypes with real users, fix what fails, and retest before build.

  4. Hand over and support build

    Deliver specifications and a design system, and support developers through build so the tested design survives.

Realistic outcomes

What to expect, honestly

The realistic outcome is higher completion on the flows that matter, fewer support calls asking what a screen means, and a consistent product your team can extend. Design does not fix a broken policy or a missing feature: it makes the existing service understandable. Where research shows the problem is policy or content rather than layout, that finding is reported plainly.

Why Omer

Why hire Omer

  • Research first: designs proven with real users, not decided in a meeting room.
  • Accessibility as standard: keyboard, screen-reader, and contrast requirements built in.
  • Flows, not screens: journeys redesigned end to end, including errors and edge cases.
  • Design system included: consistent components your team can reuse.
  • Senior-only delivery: one person owns research, design, testing, and handover.
FAQ

Questions, answered

How is UX design different from making things look better?
Visual design is part of it, but the core work is flow: whether people can complete applying, enrolling, or finding help without stalling. Testing with real users is what separates the two.
Who do you test with?
Real users from your audiences: applicants, pupils, parents, and staff, including people who use assistive technology where that is relevant to the product.
Do we need to rebuild to benefit?
Not always. Research often shows a small set of flow fixes that outperform a rebuild. A rebuild is recommended only when the underlying structure is the problem.
What do we receive at handover?
Tested prototypes, a design system, and developer specifications covering states and edge cases, so the design survives build intact.
How do you handle pupil data and safeguarding?
Pupil data stays in your existing systems wherever possible, and any new tool is given the minimum access it needs, with role-based permissions for staff. Work is planned around your safeguarding and data-protection policies from the start, including who can see what, how long messages and records are kept, and how a parent request to correct or remove data is handled.
Currently available for select engagements

Ready to get started?

The best way to explore working together is a quick conversation. Reach out through your preferred channel and let us discuss your project.