An outcome not yet turned into a programme
You have an outcome written into a plan or strategy, not yet reaching a real programme, platform or experience a child lives.
A Dawani service
Children's programmes and initiatives for government bodies
We turn an outcome your body wrote into a plan or strategy into a programme, platform or experience a child actually lives, not content merely explained to them. We build a gray prototype and test it with real children, with their parents' consent, and collect as little data as possible at every step.
What you get
- A written scope document linking your broad outcome to a behaviour observable in the child.
- A proposed situation and mechanic the child actually lives, not content merely explained to them.
- A plain gray prototype tested with real children, with their parents' consent.
- A success indicator and a guardrail indicator agreed in writing before any full build.
How we work
We start from your outcome exactly as written, and the outcome-to-experience tool turns it into a behaviour, a situation and two indicators. We then build a gray prototype tested with real children before any final version, under the same four laws that govern every decision here, as our process page describes.
When the programme includes a digital product the child uses, we also review it against the Dawani Child-Safe Design framework.
When you need this service
Signs this is the right service for you
An existing initiative that needs review
You have an initiative that today is content explained to the child, and you need it turned into an experience they actually live.
An RFP that needs the goal phrased first
Your team is writing an RFP for a children's initiative, and needs the goal and the indicator phrased before the technical requirements.
How the service runs
Four stages, a gate after each
1 Understanding the goal
We listen to your outcome exactly as written, and ask what you actually want to change for the child, not what merely reads well in a document.
Gate: Understanding leaves this stage once your team and ours agree on one clear behaviour we want to see in the child.
2 Written framing
We write with you a document naming the proposed situation and mechanic, the success indicator and the guardrail indicator, and what is out of scope.
Gate: The document leaves this stage once you approve its scope in writing before any design work begins.
3 Gray prototype and testing with children
We build an undecorated version of the proposed situation, and real children try it with their parents' consent before any final build.
Gate: The prototype leaves this stage once it works with children as we assumed, or once its failure teaches us what to fix before we continue.
4 Delivery and measurement
We deliver the full version, and measure impact against the success indicator agreed from the start, not against a general impression.
Gate: This stage stays open for the programme's whole life; the guardrail indicator does not stop at delivery.
In scope and out of scope
| Aspect | In scope | Out of scope |
|---|---|---|
| The outcome | We agree a success indicator and a guardrail indicator before any build. | We do not guarantee a specific result for the child. |
| Duration and price | We agree the scope and deliverables in writing before any commitment. | No delivery time before we understand the request, and no price published on the site. |
| Legal compliance | We review the programme against Dawani's independent safety framework. | We issue no legal compliance certificate and no legal opinion. |
| The ad campaign | We design the programme and the experience the child lives. | We do not design the ad campaign or its media plan. |
Before you write to us
A tool, a post and a reference
The outcome-to-experience tool
Try your outcome inside the tool before a first conversation, so you reach us with an early behaviour, situation and two indicators, not only a general sentence.
Open the toolFrom a broad outcome to an experience a child lives
Read why an outcome like "raising awareness" fails alone, and how we turn it into a chain of behaviour, situation, mechanic and two indicators.
Read the postThe government pathway
See the kinds of deliverable we design for government bodies, and the same method in public-sector language.
Visit the government pathwayBefore a first conversation
Questions often asked about this service
Do we need an outcome written in its final wording before we talk?
No. The tool and the first conversation are built exactly for turning an early, unfinished outcome into a sharper wording; do not wait for a final version to start.
How does this service differ from an ad campaign urging children toward a certain behaviour?
An ad campaign measures success by how many people saw it; our service measures success by a behaviour that actually appears in the child inside a situation designed for it. The difference shows up in the indicator agreed from day one.
What is the difference between this service and the children's app design service?
This service starts from a broad outcome that might become an app, a platform, a field experience, or a programme with no digital product at all; the app design service starts once the shape is already decided to be an app.
Start here
Have an outcome for children that needs a shape?
Describe your situation plainly, and we will get back to you within a few working days.
Your path: government body
Your idea arrived.
A real person from the Dawani team will read it and reply within a few working days. Thank you for thinking about kids.
Updated: