How to use this in the call
- 1. Walk the screens first. People correct a picture far faster than they answer a list.
- 2. The open questions are held separately, in PROPS_Prototype_Questions.xlsx, one row per decision with the screen it belongs to. Work through it after the walkthrough, not during it.
- 3. Where a decision changes the design rather than a detail, the screen is drawn both ways — Enrolments shows the proposed model, Old subscription the current one. Pointing at one is the answer.
- 4. Screens for modules that are live but unscoped carry a plain note saying so.
- 5. Say plainly that this is a conversation piece, not a commitment. Screens will change.
What a pilot sees
7 screens
What a company administrator manages
27 screens
What PROPS operations works in
20 screens
Shared
5 screens
What we changed, and why
The prototype keeps the PROPS identity — logo lock-up, your co-branding slot, the navy and orange palette, the course badges, the same navigation groups — so it reads as the platform you already have. What changed is how it behaves.
- Buttons say what they do
- "Invite pilot", "Record outside training", "Post seat change" — not "Submit", "OK", or three same-coloured buttons competing on one row.
- One name for each thing
- The same object is not a Program in one place and a cert in another; two roles are not both called "PROPS Manager". Where the live system has two systems doing one job, the prototype draws one.
- Empty states do something
- "Total Quiz: 0" next to a greyed-out button becomes a sentence explaining what goes there and a way to fill it.
- No unexplained jargon
- PDH is spelled out, "Investments" becomes a price, "pilots with mixed courses" is replaced by a filter that answers the same question.
- Failures are honest
- The session collision that silently logs people out now says what happened and what to do. See the sign-in screen.
- Status never relies on colour alone
- Every state carries a symbol and a word, so it survives a projector, a photocopy, and colour blindness.
What this prototype is not
- • Not connected to anything — no data is real, nothing saves, no sign-in is required.
- • Not a commitment to a design. Layouts will change once decisions land.
- • Not a complete feature list. Screens for features nobody has decided to keep are drawn with a note saying so, not built out.
- • Not the build. It informs the real implementation; it isn't the start of it.