Sofie Rostova

Case Studies

Experience

Contact

Resume

Sofie Rostova

Case Studies

Experience

Contact

Resume

Sofie Rostova

Case Studies

Experience

Contact

Resume

Help in the Moment: Contextual Help, Whenever Parents Need It

Onboarding walks a new customer through their first days in the product — and it's also the moment parents decide whether the product is for them, or not. At Time4Learning, parents were canceling because they couldn't find their footing, even when what they needed already existed in the product. Existing customers were also reaching out for help because it was buried in the Help & Tips section.

Guided tour tooltip open on the Time4Learning parent dashboard

Company: Time4Learning, a PreK-12 online homeschool curriculum used by families across the U.S. and internationally

My role: UX Designer, sole UX on the project

Team: 1 designer (myself) with competitor-research support; product team of 6

Timeline: ~1–2 sprints of design (3-week sprints), built quickly by dev once approved

I designed a contextual help system — guided tours and a pop-up Help Center — that meets parents at the moment they're stuck, whether that's their first day or their hundredth login. It shipped fast, built as lightweight overlays on existing pages rather than a costly standalone tool, and is still part of the product today.

Who This Was Really For

Parents responsible for their kids' education, with no one else to catch what they miss but us.

Timeline diagram titled What a parent might be facing at each stage, with four stages left to right. First login: doesn't know where to start, new to homeschooling, homeschooling not by choice, sometimes starting mid-year. First week: finding footing, deciding if this is the right fit, needs things paced, not all at once. Regular login: comfortable, hits something new like changing a grade level or adding a student, logs in rarely. Reactivating: coming back after time away, might land somewhere unexpected like the billing page, needs a refresher like editing an existing plan.

Four stages of a parent's visit, from first login to returning visits

Newcomers: not just new to the product, but often new to homeschooling itself — double the stress of figuring out an unfamiliar tool while also figuring out how to homeschool at all

Established customers: parents who'd used the product for years but logged in rarely, needing a refresher on the tool itself, or hitting something new — like what courses a student needs once they reach high school

Circumstance: the decisions parents made here shaped not just a school year, but what could feel like a child's whole future

Secondary: customer service, who fielded the calls when either group got stuck

A new parent needed to know where to start without feeling overwhelmed — paced, one step at a time. An established customer needed something different: help only at the exact moment they got stuck, without extra messages getting in the way.

The Problem We Were Solving

This wasn't a new problem. Bandaid fixes were failing.

Help & Tips page, a grid of topic categories — Getting Started, How-To Videos, How Do I, Student Dashboard, Planning Tools, Member Perks, After School and Summer, FAQ — with a Contact Us panel

The Help & Tips page: good general help, but not helpful in the moment of confusion

• Parents canceling in their first days, saying things like "I can't understand how to use it" or "you don't have X" — when X existed, they'd just never found it

• Existing help lived in one place: a Help & Tips section, a signup video a few minutes long, and downloadable PDFs — none of it tied to where a parent actually was in the product

• Some of what existed wasn't tool help at all: a Quick Start Guide to Homeschooling PDF, guidance on which courses to enroll in. It addressed homeschooling itself, not just the software, but it was buried the same way the tool documentation was — a library to search through, not something that met a parent where they were.

• A typical support call: a parent stuck, a rep walking them step by step to the Help & Tips section, then pointing them to the right tutorial — a manual workaround for something the product should've surfaced on its own

• Prior fixes hadn't worked: more aggressive email campaigns, PDFs, and a redesign of the Help & Tips section itself — all more of the same kind of help, just louder or better organized

Existing solutions kept adding more information to existing sections, hoping parents just needed more explanation. What was actually missing was help that showed up in the moment it was needed — not a library they had to search through, or a support rep walking them there by hand, but information delivered exactly when it was relevant, so a parent didn't even have to think about what question to ask. It would feel like we'd read their mind.

Research & Process

We had a great product. So why didn't parents see it?

• That question was already being asked internally — support tickets and cancellations kept saying the same thing, and the product had answers parents just weren't finding

• The cancellation flow itself gave us data: parents had to select a reason before canceling, and "I can't figure this out" or "you don't have X" (when X existed) came up constantly

• Talked directly with customer service, who had years of accumulated data on why parents were calling and canceling — the same handful of reasons kept surfacing, year over year

• Most parents signed up for the 14-day free trial — just checking it out. They'd land on the dashboard and get completely lost.

• Looked at how other products handled onboarding, including a reverse-trial model like Duolingo's — letting users in immediately with some features gated, easing them toward a purchase through real usage. It didn't fit: our purchase flow ran through a shopping cart decided upfront, not a gated in-app unlock

• Then the "aha": walked through our own onboarding as someone who'd used the product for years, landed on the parent dashboard, and froze — didn't know what to do next. Brought it to my supervisor in a 1:1, and it clicked for both of us — if I felt lost, a brand-new parent would feel far worse

• Started designing toward guided tours from there — then got a vendor quote that came back too expensive, and even if we'd had the budget, there was no clear owner to build or maintain the guides

• Buying a walkthrough tool wasn't an option. What we built and shipped — skins over existing pages, plus a persistent Help Center — solved the problem just as well.

Decisions & Tradeoffs

No budget. No vendor. No problem.

Getting around the budget wall

A vendor quote for a proper walkthrough tool came back too expensive — and even with budget, there was no clear owner to build or maintain the guides going forward. It was painful to hear that we were tabling it until a different time, because deep down I knew it was the fix we needed most at that moment — one that would put us in a better place against our direct competitors.

I had an idea: build the tours as skins over our own existing pages instead — no new software, no licensing, just design and a bit of dev work layered on top of what already existed. I booked a meeting with a developer ASAP, and when we heard it was doable, the green light was back on.

It shipped as four tours, one developer, one build. No standing team, no recurring license, no unclear ownership going forward.

A guided tour tooltip open on the Manage Students page, mid-tour with Skip Tour, Back, and Next controls

A step in the Manage Students tour, layered over the existing page

Designing for two completely different users

A new parent needed a lot of help, in digestible pieces. An established customer needed help on demand, at the right moment — like changing a grade level, or adding a new student to the account.

The guided tour handled the first case: four tours, triggered automatically when a new parent landed on key pages, using a standard pattern — tooltip, next, skip, step count. The rules also covered returning parents: accounts that hadn't logged in for a while, or were reactivating, would see the tour again as a refresher, triggered the first time they landed on a given dashboard page. If a parent canceled the tour, the Help Center opened at the bottom with links — a clear, visible way to relaunch the tour later if they wanted to.

The Help Center also handled the second type of user. A persistent widget sat in the bottom-left corner, always available. Its content changed depending on the page a parent was on, with links to Help & Tips, guided tours, how-to videos, or other getting-started material — on their own terms. Whether a parent logged in daily and just hit something unfamiliar, or came back after months away, they had somewhere to go, with a clear call to action instead of a wall of text to search through.

A new parent needed a lot of help, in digestible pieces. An established customer needed help on demand, at the right moment — like changing a grade level, or adding a new student to the account.

The guided tour handled the first case: four tours, triggered automatically when a new parent landed on key pages, using a standard pattern — tooltip, next, skip, step count. The rules also covered returning parents: accounts that hadn’t logged in for a while, or were reactivating, would see the tour again as a refresher, triggered the first time they landed on a given dashboard page. If a parent canceled the tour, the Help Center opened at the bottom with links — a clear, visible way to relaunch the tour later if they wanted to.

The Help Center widget, open

The same Lesson Planning & Reports page with the Help Center collapsed to its launcher icon

The Help Center widget, collapsed

The real complexity wasn't visual

The real complexity wasn’t visual

The tooltips and the Help Center widget were the easy part to design — grounded in existing best practices, even from groups like Nielsen Norman Group. The real complexity was in the logic underneath: knowing which tour to trigger, on which page, for which kind of account — and what to do when a parent didn't land where the "ideal" flow assumed they would. Edge cases came up constantly.

A reactivating parent, for example, might not land on the dashboard homepage at all. They could come back through a link, make a payment, and land on the account and billing page — with no way of knowing where they'd go from there. The rules had to account for that: which tour, if any, made sense to trigger from that entry point, and what happened if a parent had already seen part of a tour before and was now landing in a different context.

The Help Center had its own version of the same problem: which links to surface, for which type of user, on which page. A new parent on the dashboard needed something different than an established customer troubleshooting a billing question.

None of this showed up as a single screen. It was a set of conditions — page, account status, tour history — that had to line up for the tour to feel like it knew where the parent actually was, instead of assuming everyone took the path it was designed for.

The tooltips and the Help Center widget were the easy part to design — grounded in existing best practices, even from groups like Nielsen Norman Group. The real complexity was in the logic underneath: knowing which tour to trigger, on which page, for which kind of account — and what to do when a parent didn’t land where the “ideal” flow assumed they would. Edge cases came up constantly.

A reactivating parent, for example, might not land on the dashboard homepage at all. They could come back through a link, make a payment, and land on the account and billing page — with no way of knowing where they’d go from there. The rules had to account for that: which tour, if any, made sense to trigger from that entry point, and what happened if a parent had already seen part of a tour before and was now landing in a different context.

Diagram in two parts. Top, What the parent sees: a tooltip reading The right tooltips, in the right order, and a Help Center bubble reading Help Center populated based on the page and the user type. Bottom, What had to line up underneath: page location, account status, tour history, course enrollment and progress so far. A note at the bottom says a library of pre-built tooltips and articles was triggered when the right combination lined up, such as a course-map tooltip only for parents whose kids were taking high-school courses, and Help Center content that changed as a family moved further along.

A simple experience on top, and the logic underneath that made it work

Making help available without blocking the task

We also solved another issue in this project. Our tutorial videos were embedded in a way that meant watching and working were mutually exclusive — a parent had to close the video, remember what they'd just seen, and try to reproduce it on their own. One of Nielsen Norman Group's core usability heuristics is that help shouldn't force a choice between reading it and doing the thing it's explaining.

We fixed it by having dev build a floating video player that stayed on top of the page, so a parent could watch a step and act on it in the same window. The same principle shaped the Help Center more broadly: help had to be reachable without losing your place, whether that meant a floating video, a link that opened in a new tab, or a widget that stayed open alongside the page instead of taking it over.

We also solved another issue in this project. Our tutorial videos were embedded in a way that meant watching and working were mutually exclusive — a parent had to close the video, remember what they’d just seen, and try to reproduce it on their own. One of Nielsen Norman Group’s core usability heuristics is that help shouldn’t force a choice between reading it and doing the thing it’s explaining.

What Changed for Parents

From "good luck, you're on your own" to "welcome — let me show you around."

• Four guided tours, live on key pages, triggered automatically the first time a parent landed there — no digging through a help section to find them

• A canceled tour didn't disappear — the Help Center opened in its place, so a parent could always come back to it

• A persistent Help Center widget, always available, with content that changed based on the page — Help & Tips, guided tours, how-to videos, or getting-started material, depending on what a parent actually needed there

• Returning and reactivating parents got tour refreshers automatically, without needing to ask

• Tutorial videos that stayed on top of the page instead of taking it over, so a parent could watch and act at the same time

• A support call that used to require walking someone step by step to Help & Tips became something a parent could resolve on their own

For a new parent, the product went from "figure it out" to "here's where to start." For an established customer, it went from silence to a quiet, reliable way back in whenever they hit something unfamiliar.

Outcomes

30 percent fewer support inquiries than the same period a year earlier. Fewer parents needing a rep to walk them to Help & Tips, because the product was doing it for them.

The fix that almost never happened ended up doing more than the "proper" one might have — for a fraction of the cost, built and shipped by one designer and one developer.

Reflection

The best parts of this project came from a constraint and a conversation.

Sometimes a constraint can force a better solution than the original ask. If the vendor tool had come in on budget, we would have bought it — and I don't think the Help Center exists in that version of the project. It also would have taken longer: vendor onboarding, integration, setup, and a learning curve for whoever had to run it, instead of one dev meeting and a same-week yes. Skins were the workaround, but building it ourselves is what let us add a second, quieter layer of help alongside the tour, aimed at a completely different kind of user. The budget wall didn't just limit the solution. It changed what problem we ended up solving.

A personal moment can move a project forward. Freezing on my own dashboard told me the problem was real — but it stayed just my experience until I brought it to my supervisor in a 1:1. Saying it plainly is what made it land: if I felt lost, and I knew this product cold, a brand-new parent would feel far worse. That one conversation is what got the project taken seriously.

Screens shown as originally designed. The product has since been rebranded.