Sunny TingProduct builder · Calgary, AB

I build. I question.
I change direction.

I built LekkerKids to help Calgary parents find kids’ activities. I handled research, design, development and studio outreach. User feedback shaped what I changed next.

lekkerkids.comLiveLekkerKids homepage showing the class finder, activity discovery, and Calgary family events.
Studios listed
200+
Page views
10,000+
Visitors reached
2,000+

LekkerKids · Product decisions

Visit live product

Three months.
Three assumptions I had to change.

I built LekkerKids as a parent information platform for Calgary families. Over three months, evidence kept challenging what I thought would work.

01 / Interface

Map-first → List-first

Location mattered. The map wasn’t how people explored.

What I believed

I thought location would drive discovery. I built the experience around a map.

What challenged it

I observed and interviewed 10 parents. I also reviewed tracking data. Parents scanned the list and barely used the map.

Decision

Make the list primary. Keep the map available on demand.

The trade-off Less space for the map. More space to compare options.

Before · Open map markers to explore individual options
After · Scan dates, times and prices. Open the map when needed.

02 / Strategy

The product got better.
Distribution didn’t.

Parent-first → Supply-side

Social postTraffic spikeBack to baseline
Observed pattern · Illustration, not an analytics chart

Promotional posts drove short bursts of traffic. Visits soon returned to the previous level.

What I believed

If I made discovery useful enough, parents would start coming back.

What challenged it

I asked parents why they weren’t using LekkerKids. They already had familiar ways to find activities. Usability wasn’t their main concern.

I had confused product quality with acquisition.

Decision

Add studio pages with richer program information for parents. Use those pages to start partnerships and encourage studios to promote LekkerKids.

The trade-off

Less time and capacity to maintain and improve the Activities page.

Studios as a distribution path: still a hypothesis.

03 / Diagnosis

I changed the message.
The result stayed the same.

Message → Friction

Hypothesis

I expected a better preview, clearer explanation and shorter email to raise claims. My target was 40–50%.

The action stayed the same: claim an existing studio profile to manage its information on LekkerKids.

V1 · 200 wordsBaseline
4of 20 studios claimed
  • Longer explanation
  • Basic profile preview
Better preview
Clearer explanation
200 → 100 words
V2 · 100 wordsRevised
4of 20 studios claimed
  • Clearer explanation
  • Better profile preview
Readout

Clearer and shorter. Same 20% claim rate.

Small, non-randomized sample: 40 studios in two batches. The result challenged my message diagnosis, but it did not identify the main barrier.

Still unresolved

Trust · Perceived value · Setup friction

Why 40–50%?

This was a go/no-go threshold, not a benchmark. If close to half claimed a ready-made profile, the channel would be worth more investment.

Current bet

Pre-fill studio information with AI. Ask owners to review and confirm it instead of entering everything themselves.

In progress · No result yet

From building to the frontline

Neo Financial

I started seeing the same pattern at Neo.

Sales Representative · Neo Financial

LekkerKids

Parents already had familiar ways of finding activities.

Neo

Some customers keep using a familiar card, even when Neo offers better benefits.

Existing behaviour is harder to change than I originally assumed.

Some customers are unsure how cashback works or what it is worth. Both experiences make me curious about how people understand and adopt products.

More experiments

My other projects

Two more ways
I test ideas.

Mobile product discovery

Daycare Management Product

An iOS and Android app concept. Research led me to pause it before launch.

Role
Product Discovery / Research
Platform
iOS / Android
Outcome
Paused before launch
Teacher portal classroom view: a row per child with meal, toilet, and sleep logging, and an arrival status on the right.
iOS / Android teacher app: daily classroom log.
Explore

Research

  • Spoke with daycare operators and startup founders.
  • Studied workflows and the existing software landscape.
Assess

Evaluate

  • Confirmed meaningful workflow pain.
  • Weighed incumbents, data sensitivity, trust, and switching friction.
Decide

Pause

  • The evidence did not justify the cost of entry.
  • I redirected effort toward faster validation.
Research, decisions, and what I learned