B2C · Mobile · Freelance

ParentWiser

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.

My role
Solo product designer
Context
Freelance · Istanbul
Period
May 2018 – Mar 2019
Platform
iOS mobile app
ParentWiser — Articles screen
1 Context 2 Problem 3 Deliverables 4 Approach 5 Execution 6 Outcomes 7 Learnings

Translating child psychology expertise into a mobile 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 struggled to find reliable, expert-backed advice

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

Ideas without a buildable product

The project owner had a few ideas and an established audience — a large social media following and published books — but nothing tangible that would move him closer to building a digital product to support parents. There was no defined business model, no target audience profile, and no MVP scope.

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.


One business model, a customer profile, and end-to-end design — ready to hand off

The project owner had an audience but no product. By the end of the engagement, he had a chosen business model, a clear picture of who he was building for, and production-ready designs to hand to a development team.

1
Business model selected from multiple candidates — value proposition, revenue streams, and go-to-market strategy
1
Customer profile canvas synthesized from surveys and interviews — gains, pains, and jobs to be done
E2E
End-to-end UI design delivered — information architecture, all screens, and edge cases

Mixed-method research to understand parents' real needs

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.

1

Stakeholder interviews

Mapped the team's expertise, expectations, and what they knew about parents' problems. Aligned the team before talking to users.

2

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.

3

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.

4

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 — gains, pains, and jobs to be done

↑ Research output — 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.


From research insights to business model and experience design

#1 Business model workshop

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.

Workshop session with the team
Workshop sticky notes Workshop canvas
Business Model Canvas for ParentWiser

Business Model Canvas — revenue from online course fees, free articles as acquisition channel

#2 Wireframes

The backbone of the application consists of three main sections: articles, courses, and notifications. Articles open the app — free, expert-backed content designed to surface answers to the most common parenting problems and up-sell premium courses. The courses page leads with a free course so parents can experience the format before committing. A notification centre completes the loop, giving us a channel to re-engage users at the right moments.

Articles wireframe

Articles

Courses wireframe

Courses

Notifications wireframe

Notifications

#3 Design decisions
1 User gain

Parents want to read research and case studies for the problems they're trying to solve — not just opinions.

1 Design decision

Articles are tagged with R (research) and C (case study) icons. The same color system carries through into article detail pages.

2 Jobs to be done
  • Cooking and feeding
  • House cleaning
  • Grocery shopping
  • Going to park and spending time
1

A day of a parent is all about taking care of their child. So in accordance with their context, we made all articles audible.

2

We've also added the bookmark feature for them to continue wherever they left off when interrupted.

3 Pain point
1

Difficulty in applying solutions from books, because of the differences between children.

2

Being impatient in solving problems.

1

No child is the same, so solutions need to be personalised. We created an "If your child is..." component with specific tips for different child types — hyperactive, distracted, and more.

2

Parents often get impatient when trying to solve a problem. We added a "Pay attention to" section to warn parents about the challenges they might face along the way.

4 Business model requirement

Making revenue by selling online courses.

1

While designing the articles page, we also imagined it as a place to up-sell courses. At the end of each article, we added relevant courses where parents can go deeper on the subject.

2

Since the revenue model depended on selling courses, parents needed to experience the value first. We made one course free so they could try it before committing.

5 Business model requirement

Making revenue by selling online courses.

1

We added a 30-day money-back guarantee to all courses to encourage parents to commit — knowing they could get a refund if unsatisfied.

2

In the course detail page, we answered "Who should take this class?" and "What will I learn?" to help parents make a confident decision.

3

We added a cross-selling section to surface other relevant courses at the end of each course page.

Chapter screen Course final screen Notifications screen

Key insights

1

Expert credibility matters

Parents trusted advice more when they understood the science behind it. "Why" was as important as "what to do."

2

Timing is everything

Parents needed advice in the moment — not scheduled reading sessions. Access had to be instant and mobile-first.

3

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.