ReadyTech
•
End-to-end
How my team and I took a sensitive, sprawling ask and built it on a pattern Ready Student already had, so one record now works across five products.
complex in, simple out
ROLE
Lead Product Designer
TEAM
Me, a PM and an engineer, with the Admissions team
TIMELINE
2026
COMPANY
ReadyTech
5
products reading one record, from the school’s application to the trainer’s roll
4
gaps filled on a pattern we already had, instead of a new feature
1
flag on the type decides what every portal offers

The problem
We were asked to design support needs for one cohort, school students applying for vocational courses through their school. It didn’t stay that small for long! Learning and medical needs matter for every student, and the same details had to be entered by schools, checked by admissions staff, kept by the training provider and seen by trainers. It’s also some of the most sensitive information a provider holds, and one client had already told us that even a visible tag on a profile felt like too much.
Taking a step back
Before designing anything new, we took a good look at what Ready Student already did. Turns out Properties, a pattern every client already configures, did half the job. It just couldn’t keep a need private, hold a note or a file, or tie a need to the enrolment it matters for.

What we built
We filled those four gaps on the property type itself, and added one flag that tells every portal “this is a support need”. Set it once and every need of that type follows along. Restricted really does mean restricted, too. If you’re not on the list, you don’t get a greyed-out row, you just see nothing at all.
My role: lead designer, from discovery and interaction design right through to working prototypes in each product. Our PM drove the carve-out and sequencing, and our engineer kept us feasible.
Following one need everywhere
Then we followed a single need through every product that touches it, screen by screen, in an interaction artefact the whole team could click through. For each product we worked out what it shows, what it can change, and what it leaves out on purpose.
School, in the VETDSS portal: declares each need with its own note and files. It can add, but never rewrite what the provider wrote.
Admissions staff, in Ready Admissions: check and edit, one need at a time, before the student enrols.
Ready Student: the one record, and the only place the settings live.
Educator portal: read only. A quiet halo on the roll, with the detail one tap away.
Student portal: their own record, read only.
The key decision
Extending what we had, instead of inventing something new. I’d already designed and prototyped a dedicated support needs page. When a colleague asked why it wasn’t using what Ready Student already had, we stopped and looked, and they were right. We kept the thinking, scrapped the new feature and moved it onto Properties. That meant fewer new things for clients to learn, and one less place for sensitive data to live.
Outcome
One model, read by five products, from a school’s application to a trainer’s roll
Designed so a new kind of support need is a setting, not a project
Sensitive detail stays invisible to anyone not nominated, enforced in one place
Now its own initiative, with dev-ready packages for all four product teams