A website redesign for Kacperkowo, a private kindergarten — rebuilding the digital experience for parents, from desktop to mobile.
A website redesign for Kacperkowo, a private kindergarten — rebuilding the digital experience for parents, from desktop to mobile.
A website redesign for Kacperkowo, a private kindergarten — rebuilding the digital experience for parents, from desktop to mobile.
Role
Role
research
UX/UI design
responsive design across breakpoints
developer handoff (CSS + HTML specs)
research
UX/UI design
responsive design across breakpoints
developer handoff (CSS + HTML specs)
Time
Time
3 months
3 months
Industry
Industry
EdTech
EdTech
Why I do this?
Outdated visuals, a confusing layout, and zero mobile support. My task was to modernize the site completely — new structure, fresh content, and a mobile-friendly experience parents could actually rely on.
Impact
Parents had no choice but to call the kindergarten directly, often unsure which branch they'd even reached. Directors ended up relaying information between each other to answer basic questions — like a game of broken telephone, with information getting lost or distorted along the way.
Why it mattered for the business
Every missed or confused call meant lost time for directors who should've been focused on running the kindergarten, not fielding questions the website should answer. It also created a poor first impression for parents choosing a kindergarten for their child — trust and clarity matter most at that decision point, and an outdated site undermined both.
When the website can't answer a simple question,
parents pick up the phone instead.
Before
No branch names, photos, or "learn more" links
1
3
2
4
"Prywatny żłobek" is unreadable — light green text gets lost against the busy radial background lines
Low-contrast text — blue on light blue, hard to read
No branch names, photos, or "learn more" links
Huge unused space — not responsive, desktop-only layout
Every one of these issues pointed to the same root cause: parents couldn't find what they needed, fast. That became the foundation for the redesign.
After
Why I do this?
Why I do this?
Outdated visuals, a confusing layout, and zero mobile support. My task was to modernize the site completely — new structure, fresh content, and a mobile-friendly experience parents could actually rely on.
Impact
Parents had no choice but to call the kindergarten directly, often unsure which branch they'd even reached. Directors ended up relaying information between each other to answer basic questions — like a game of broken telephone, with information getting lost or distorted along the way.
Why it mattered for the business
Every missed or confused call meant lost time for directors who should've been focused on running the kindergarten, not fielding questions the website should answer. It also created a poor first impression for parents choosing a kindergarten for their child — trust and clarity matter most at that decision point, and an outdated site undermined both.
Every missed or confused call meant lost time for directors who should've been focused on running the kindergarten, not fielding questions the website should answer. It also created a poor first impression for parents choosing a kindergarten for their child — trust and clarity matter most at that decision point, and an outdated site undermined both.
When the website can't answer a simple question,
parents pick up the phone instead.
Before
"Prywatny żłobek" is unreadable — light green text gets lost against the busy radial background lines
Low-contrast text — blue on light blue, hard to read
Huge unused space — not responsive, desktop-only layout
No branch names, photos, or "learn more" links
"Prywatny żłobek" is unreadable — light green text gets lost against the busy radial background lines
Low-contrast text — blue on light blue, hard to read
Huge unused space — not responsive, desktop-only layout
No branch names, photos, or "learn more" links
Every one of these issues pointed to the same root cause: parents couldn't find what they needed, fast. That became the foundation for the redesign.
After
Step #1 Stakeholder Requirements
Step #1 Stakeholder Requirements
Research began with a conversation with the director rather than formal user interviews. Her requirements shaped the foundation of the redesign:
Research began with a conversation with the director rather than formal user interviews. Her requirements shaped the foundation of the redesign:
Sidebar navigation for easy access to every section
Dedicated, detailed information for each branch
Consistency with the kindergarten's existing brand colors and typography
A live feed from their catering service, so parents could see meals in real time
Sidebar navigation for easy access to every section
Dedicated, detailed information for each branch
Consistency with the kindergarten's existing brand colors and typography
A live feed from their catering service, so parents could see meals in real time
Translating the director's requirements into a first rough sketch — navigation, branch sections, and a spot for a director's photo.
Translating the director's requirements into a first rough sketch — navigation, branch sections, and a spot for a director's photo.
What changed, in detail?
What changed, in detail?
The kindergarten specifically requested detailed, comprehensive descriptions for each branch — the goal was to answer as many parent questions upfront as possible, reducing phone inquiries. This meant balancing thoroughness with readability, a trade-off made deliberately with the client.
The testimonials were pulled directly from Google reviews, and I hadn't accounted for the fact that not every reviewer has a profile photo — resulting in inconsistent avatars (real photos vs. placeholder letters). This is something I'd revisit: either using consistent placeholder avatars for everyone, or designing a fallback style that still feels polished
Pairing each description with its own building photo made the two branches instantly distinguishable — something parents later confirmed in their feedback.
Pairing each description with its own building photo made the two branches instantly distinguishable — something parents later confirmed in their feedback.
1
2
3
3
2
The kindergarten specifically requested detailed, comprehensive descriptions for each branch — the goal was to answer as many parent questions upfront as possible, reducing phone inquiries. This meant balancing thoroughness with readability, a trade-off made deliberately with the client.
Pairing each description with its own building photo made the two branches instantly distinguishable — something parents later confirmed in their feedback.
The testimonials were pulled directly from Google reviews, and I hadn't accounted for the fact that not every reviewer has a profile photo — resulting in inconsistent avatars (real photos vs. placeholder letters). This is something I'd revisit: either using consistent placeholder avatars for everyone, or designing a fallback style that still feels polished
Step #2 — Learning from others
Step #2 — Learning from others
Before sketching the final structure, I looked at how other kindergartens and nurseries in Kraków handle the same challenge: multiple branches, one website. Five competitors, one question — how do parents actually find their branch?
Before sketching the final structure, I looked at how other kindergartens and nurseries in Kraków handle the same challenge: multiple branches, one website. Five competitors, one question — how do parents actually find their branch?
Some patterns stood out immediately. KIDS&Co. gives every branch its own dedicated page, complete with photos, a local director, and real reviews. Fair Play lets parents filter by type and city — the closest thing to a "find your branch" tool among the five. Others repeated the exact confusion Kacperkowo was trying to escape: Malutkowo splits into two separate brands on the same street, and Happy Kids identifies branches by number alone, with no photo to tell them apart.
Some patterns stood out immediately. KIDS&Co. gives every branch its own dedicated page, complete with photos, a local director, and real reviews. Fair Play lets parents filter by type and city — the closest thing to a "find your branch" tool among the five. Others repeated the exact confusion Kacperkowo was trying to escape: Malutkowo splits into two separate brands on the same street, and Happy Kids identifies branches by number alone, with no photo to tell them apart.
The kindergartens parents could navigate fastest all shared one thing: a strong visual identity per branch. Not just a list of addresses — a face, a photo, a name people could remember
The kindergartens parents could navigate fastest all shared one thing: a strong visual identity per branch. Not just a list of addresses — a face, a photo, a name people could remember
Step #3 — Structuring the content
Step #3 — Structuring the content
With stakeholder requirements and competitor insights in hand, the next step was turning them into an actual structure. Every page needed a clear job — and every branch needed to stand on its own, not get lost in a list.
With stakeholder requirements and competitor insights in hand, the next step was turning them into an actual structure. Every page needed a clear job — and every branch needed to stand on its own, not get lost in a list.
Seven pages, one clear hierarchy — and branches that finally have a home of their own. From here, it was time to turn structure into screens.
Seven pages, one clear hierarchy — and branches that finally have a home of their own. From here, it was time to turn structure into screens.
Step #4 — Bringing it to every screen
Step #4 — Bringing it to every screen
Structure was ready, but "mobile-first" was still just a word in the requirements — it needed proof. Every page was designed across three breakpoints — desktop, tablet, and mobile — so parents could get the same clear experience whether they were at a computer or checking on their phone mid-call.
Structure was ready, but "mobile-first" was still just a word in the requirements — it needed proof. Every page was designed across three breakpoints — desktop, tablet, and mobile — so parents could get the same clear experience whether they were at a computer or checking on their phone mid-call.
Homepage (Desktop)
On desktop, both branches are visible at once, with full descriptions and photos.
On desktop, both branches are visible at once, with full descriptions and photos.
Homepage (mobile)
On mobile, the same information stacks into a vertical scroll, keeping the same hierarchy — highlights → branches → testimonials → contact — without losing a single block.
On mobile, the same information stacks into a vertical scroll, keeping the same hierarchy — highlights → branches → testimonials → contact — without losing a single block.
Branch/Director page (desktop)
Probably the strongest proof that the case study's core problem got solved: every branch now has a face, a personal note, and a clear description of that specific location — instead of a bare address on a cloud, where this all started.
Probably the strongest proof that the case study's core problem got solved: every branch now has a face, a personal note, and a clear description of that specific location — instead of a bare address on a cloud, where this all started.
Branch/Director page( mobile)
the director's photo and welcome note stay right at the top, so parents recognize the branch before they even start scrolling — the gallery and details follow below in the same order as desktop.
the director's photo and welcome note stay right at the top, so parents recognize the branch before they even start scrolling — the gallery and details follow below in the same order as desktop.
Step #5 — Bringing it to every screen
A quick note before diving in: the final live site differs slightly from the UI shown here. Alongside the Figma files, I handed off detailed CSS and HTML specs to guide implementation as closely as possible — but the kindergarten's original domain and hosting couldn't support some of the design's features, and fully implementing them would have required additional budget the client wasn't ready to commit to at the time. What follows is the intended design.
Results
The redesign wasn't just a visual refresh — it changed how the kindergarten runs day to day.
The redesign completely changed how I manage my daily routine. Before the launch, I spent hours on the phone every single week answering the exact same questions from parents: 'Where are you located?', 'What's the price?', 'Which documents do we need?' Now, when parents call, they already know the details and just want to schedule a visit. It feels like the website is finally working for us, not against us. It saved me at least 4–5 hours of repetitive phone calls every week, allowing me to focus on the children and nursery operations."
— Director, Kacperkowo
"When we were choosing a nursery for our son, Kacperkowo was on our shortlist, but we were so confused about their two different locations. The new website made the difference immediately. The separation between Nursery 1 and Nursery 2 is perfectly clear, with photos, distinct addresses, and specific details for each branch. It built trust right away, and we knew exactly which director we needed to contact."
— Parent
The 'broken telephone' is gone. Parents get answers before they even pick up the phone — and the director finally gets her time back.
Under the hood, the numbers back it up too.
100
All other pages desktop & mobile
91/56
Homepage desktop & mobile
A conscious trade-off: the homepage's mobile speed dips for the emotional first impression that makes parents stop scrolling — first on the list for a v2 pass.
What I learn from this project
This project taught me that a design rarely survives development 100% intact — and that's not a failure, it's just reality. What actually makes the difference is staying close to the developer, listening to their constraints, and treating the handoff as a conversation, not a one-way delivery. That's when things go smoothly
Research doesn't always look like user interviews. I didn't have formal sessions with parents — but a direct conversation with the director, paired with a close audit of the existing site, gave me just as much real insight. Good research is about listening carefully to whoever holds the information, not following a fixed process for its own sake.
Reviewing my own work honestly is part of the job. Going back through the final site, I could see choices that made sense in theory but didn't quite land in practice — like the alternating branch layout, or inconsistent testimonial avatars. Catching those myself, instead of assuming everything worked as intended, is something I want to keep doing on every project going forward
More works
Ideas, internships, collaborations?
Let's talk!
Step #5 — Bringing it to every screen
Step #5 — Bringing it to every screen
A quick note before diving in: the final live site differs slightly from the UI shown here. Alongside the Figma files, I handed off detailed CSS and HTML specs to guide implementation as closely as possible — but the kindergarten's original domain and hosting couldn't support some of the design's features, and fully implementing them would have required additional budget the client wasn't ready to commit to at the time. What follows is the intended design.
Results
The redesign wasn't just a visual refresh — it changed how the kindergarten runs day to day.
The redesign completely changed how I manage my daily routine. Before the launch, I spent hours on the phone every single week answering the exact same questions from parents: 'Where are you located?', 'What's the price?', 'Which documents do we need?' Now, when parents call, they already know the details and just want to schedule a visit. It feels like the website is finally working for us, not against us. It saved me at least 4–5 hours of repetitive phone calls every week, allowing me to focus on the children and nursery operations."
— Director, Kacperkowo
"When we were choosing a nursery for our son, Kacperkowo was on our shortlist, but we were so confused about their two different locations. The new website made the difference immediately. The separation between Nursery 1 and Nursery 2 is perfectly clear, with photos, distinct addresses, and specific details for each branch. It built trust right away, and we knew exactly which director we needed to contact."
— Parent
The 'broken telephone' is gone. Parents get answers before they even pick up the phone — and the director finally gets her time back.
Under the hood, the numbers back it up too.
100
All other pages desktop & mobile
All other pages desktop & mobile
91/56
Homepage desktop & mobile
A conscious trade-off: the homepage's mobile speed dips for the emotional first impression that makes parents stop scrolling — first on the list for a v2 pass.
A conscious trade-off: the homepage's mobile speed dips for the emotional first impression that makes parents stop scrolling — first on the list for a v2 pass.
What I learn from this project
What I learn from this project
This project taught me that a design rarely survives development 100% intact — and that's not a failure, it's just reality. What actually makes the difference is staying close to the developer, listening to their constraints, and treating the handoff as a conversation, not a one-way delivery. That's when things go smoothly
Research doesn't always look like user interviews. I didn't have formal sessions with parents — but a direct conversation with the director, paired with a close audit of the existing site, gave me just as much real insight. Good research is about listening carefully to whoever holds the information, not following a fixed process for its own sake.
Reviewing my own work honestly is part of the job. Going back through the final site, I could see choices that made sense in theory but didn't quite land in practice — like the alternating branch layout, or inconsistent testimonial avatars. Catching those myself, instead of assuming everything worked as intended, is something I want to keep doing on every project going forward
