Parentapp
Turning a child psychology expert's knowledge into a viable mobile product — from zero to a clear value proposition, business model, and end-to-end design.
A popular expert, no product
The project owner was a well-known child psychologist with a large social media following and published books. He had a vision for a mobile app for parents, but no clear product direction, business model, or MVP scope to act on it.
His existing audience was an asset — but without a validated product structure, it couldn't be monetized. The goal was to turn that expertise and audience into something buildable: a real product with a defined value proposition, a sustainable revenue model, and a clear target audience.
I joined to help shape the idea into something buildable — and then to design it end to end.
User problem
Parents with young children (ages 3–5) struggled to find reliable, expert-backed advice they could trust and act on quickly. Generic content felt hollow — they needed to understand why an approach worked for their specific child, not just what to do. And they needed it in the moments that mattered, not in scheduled reading time they didn't have.
Business problem
The project owner had an established audience — a large social media following and published books — but no product to monetize it with. There was no defined business model, no target audience profile, and no MVP scope. A vision existed, but nothing buildable to act on.
I was brought in to close that gap: to shape the idea into a real product with a clear value proposition, a sustainable revenue model, and designs ready to hand to a development team.
From idea to buildable product
The project owner had an audience but no product. By the end of the engagement, he had a validated business model, a defined MVP scope, a clear target audience, and production-ready designs to hand to a development team.
Why this approach?
There was no existing product, no analytics, and no prior user data. Any business model we chose without first understanding the user would have been a guess. So the decision was clear: research before screens, always.
We also had the advantage of a built-in audience through the expert's Instagram following — which meant we could run surveys quickly and cheaply with real parents, rather than recruiting from scratch. That shaped the sequencing: surveys first to understand who they are, interviews next to understand why.
Stakeholder workshop — aligning on assumptions before talking to users
Stakeholder interviews
Mapped the team's expertise, expectations, and what they knew about parents' problems. Aligned the team before talking to users.
Online surveys
Two rounds via the expert's Instagram account. First to identify demographics; second to uncover jobs, pains and expectations. Audience: 25–44 year olds with 1–2 children aged 3–5.
User interviews
8 interviews with parents, in-person and by phone. Synthesized into a customer profile to create a shared understanding of who we were building for.
Competitor review analysis
Analyzed 3 competing apps via 1-star and 5-star reviews to learn what parents love and what to avoid.
Customer profile canvas synthesized from survey and interview data
What trade-offs shaped it?
Time and budget were limited — every method had to be lean and fast. We ran research, strategy, and design in parallel, treating early findings as directional and revisiting assumptions as more data came in.
How we ran it
Using research outputs, we explored multiple value propositions, ran a SWOT analysis on different business models, and aligned on a direction: free articles to attract, premium online courses to monetize.
Business Model Canvas — revenue from online course fees, free articles as acquisition channel
Parents want to read research and case studies for the problems they're trying to solve — not just opinions.
Articles are tagged with R (research) and C (case study) icons. The same color system carries through into article detail pages.
Parents are occupied with childcare, cooking, and housework all day — they can't always stop to read.
All articles are made listenable. A bookmark feature lets parents pick up exactly where they left off.
Parents feel like a failure when standard advice doesn't work with their specific child.
Articles include an "If your child is..." component with personalized tips for different child types — hyperactive, distracted, and more.
.png)
Key insights
Expert credibility matters
Parents trusted advice more when they understood the science behind it. "Why" was as important as "what to do."
Timing is everything
Parents needed advice in the moment — not scheduled reading sessions. Access had to be instant and mobile-first.
Community reduces guilt
Knowing other parents struggled with the same issues was as valuable as the advice itself. The tone needed to be warm, not clinical.
These insights directly shaped the product's core features: tagged articles for credibility, audio listening for accessibility, and a warm editorial voice throughout.
What I've learned
Clearly communicating the scope of deliverables at the start is as important as the work itself — misaligned expectations create friction even when the output is strong.
The team's limited familiarity with lean product methodology was a constraint. Bringing everyone to the same mental model — with examples — was a prerequisite for good decisions.
Regular communication with the project owner isn't just courtesy — it's a design tool. Gaps in communication compounded ambiguity in already undefined territory.