Product Principles

These are not aspirational values. They are decision filters. When a feature, UX pattern, or piece of copy is proposed, it must be able to trace back to at least one of these. If it can't, it doesn't belong in the product.

1. Meet them where they are

The Coach adapts to the learner — not the other way around.

In practice: a user with a shared low-end phone on 3G and a user with their own tablet on Wi-Fi should both get a full experience. The writing module's paper-and-photo pathway is the clearest expression of this tenet. If a feature only works well for well-equipped users, it isn't ready.

2. Relational, not transactional

The Coach builds a relationship with the learner, not just a record of drills completed.

In practice: the experience should feel like talking to a patient, encouraging person — not submitting answers to a scoring engine. Every interaction loop should leave the learner feeling seen, not evaluated. Avoid score-first UX patterns.

3. Private by default

Progress, struggle, and feedback belong to the learner.

In practice: no public leaderboards, no visible scores for others, no shame mechanics. The Coach's feedback is a private conversation. This is especially important for adults returning to learning after difficult experiences with formal education.

4. Confidence first, skill second

The primary goal is for the learner to believe they can improve — the skill gains follow.

In practice: the Coach celebrates effort and progress, not just correct answers. Feedback is framed constructively. Encouragement is specific ("you read that paragraph much more smoothly than last time") not generic ("great job!"). We measure re-engagement as a success metric alongside skill progression.

5. Safe to try, safe to fail

The Coach is a low-stakes environment where attempting something hard is always the right move.

In practice: errors are treated as information, not failures. The Coach never signals frustration or impatience. The learner should never feel penalised for attempting a harder module or making a mistake mid-exercise.

6. Earn trust before asking for effort

The learner's trust is the product's most valuable asset — and it has to be earned.

In practice: the first session should be light and encouraging, not demanding. The profiling step must feel like a conversation, not a test. If a learner doesn't trust the Coach, they won't come back — and a learner who comes back is the whole point.

7. Conversation, not content delivery

This is not a recording. It is not a pathway. It is a conversation.

In practice: every interaction loop must feel like a two-way exchange, not a broadcast. Static content screens, fixed learning pathways, and pre-recorded instructional sequences all fail this principle. The test: if the interaction would work identically for every learner regardless of who they are, it isn't a conversation.

8. Memory is the trust mechanism

Being remembered removes the shame of having to explain yourself again.

In practice: the Coach remembers the learner's name, their last session, what they found difficult, and what they achieved. This is not a nice-to-have — for adults returning to learning after years away, having to re-explain yourself feels like starting over from zero. Persistent, personal memory is what makes the Coach feel like a relationship rather than a service. Every session open should demonstrate that memory explicitly.

9. Reach out, don't wait Phase 2

The Coach nudges learners back at the right moment — it doesn't sit waiting to be opened.

In practice: proactive re-engagement — a notification, a message, a prompt — is how the Coach demonstrates that it noticed the learner was absent and that their return matters. Timing and tone matter enormously: a nudge that feels like nagging is worse than silence. The goal is to lower the barrier to returning, not to add pressure.

→ How the Coach applies these in practice → Feature Inventory → Who these principles are designed for