Skip to content

01 / Mapu brand system

Built to become unnecessary

Most family products want to be opened every day for years. Mapu is designed to be needed less each month. That single commitment shapes the strategy, the interface and the tone of every sentence.

The progression

Four stages, each one a handover. The path rises and the platform recedes.

  1. 01

    Supported

    The parent holds most of the structure. Expectations are written down and visible to both, so nothing depends on memory or mood.

  2. 02

    Practised together

    The young person takes a decision with the parent alongside. Both agree in advance what a good outcome looks like.

  3. 03

    Increasing autonomy

    The decision moves across. Review continues, but lightly, and on a schedule both chose.

  4. 04

    Independent navigation

    The item leaves the system. There is one fewer thing in Mapu, and that is the point.

Scaffolding, not supervision

Scaffolding

Temporary by design. Visible to everyone it touches. Built to hold weight while something is being learned, then taken down without ceremony.

Supervision

Permanent by design. Visible to one side only. Built to detect failure rather than to make success repeatable. Mapu never behaves this way, in product or in language.

What follows from the idea

In the product
Success is measured by items leaving the system, not by time spent inside it. There is no daily streak and no engagement metric on any screen.
In the interface
Every record a parent can see, the young person can see too. Symmetry is the default, not a setting.
In the language
Mapu describes what a family is doing, not what a child is failing to do. Progress is noticed; it is never celebrated at someone’s expense.
In the identity
Restraint reads as competence. The brand does not raise its voice to prove it is working.