One step for the moment, not another library of advice

A small survey identifies a question, not an answer

In a convenience survey of 31 parents, 65% selected difficulty regulating their own emotions as a challenge. This sample is not representative and cannot demonstrate that a particular intervention works.

I used that signal to frame ten desk-research questions, review 41 sources, and map Jobs To Be Done (JTBD) and eight task flows. In the moment, a parent may have little energy to scan a long feed. Situational support should lead to one short action.

Design for both before and after a conflict

The SOS flow begins with the situation and age context, then a short suggestion with source and review status. A no-result state matters more than forcing irrelevant advice.

Some parents will open the app after losing their temper. The Recovery flow supports reflection, reconnection, and closure. Its copy should avoid judging the parent or promising a psychological outcome.

Source, privacy, and safety belong in the UI

Guidance about children needs clear provenance and review status. The prototype explains that a child’s age helps select developmental context, not evaluate the child; additional profile details can be skipped.

SOS does not replace professional care. Emergency escalation routes have not been verified. Family Space and Check-in remain design assumptions, not proof of this flow’s effectiveness.

• Mark source and review status.
• Minimise and explain child data.
• Offer no-result and recovery paths.
• Seek expert review before publishing sensitive guidance.

A prototype is not evidence of impact

A 43-screen interactive prototype exists, but no 1:1 interviews, usability tests, expert reviews, or production outcomes are documented.

The next step is to test task success and comprehension, plus expert review of sensitive guidance. Completing a prototype does not show improved parental wellbeing.