Case study · Product education & first-run activation

Educating busy users without slowing them down

How Grupop explains itself to Irish primary teachers - and why splitting pre-signup education from in-app guidance beat a walkthrough video.

Problem

A new classroom SaaS needed to teach both what it is and how to use it - without asking time-poor teachers to sit through long tutorials that would undermine the product’s simplicity promise.

Decision

Split the jobs. Welcome-page carousels for pre-signup product education; five contextual first-run hints for in-app activation. Refuse long walkthrough videos.

Principles

Progressive disclosure · minimise time to aha / time-to-value · right content for the right stage · friction as a design constraint.

Proof

Two × 6 captioned screenshot carousels on grupop.ie/welcome · strict rule of five dismissible in-app hints after setup (<1 minute to ready).

Welcome page carousel showing two captioned Grupop Rewards System slides
Welcome: captioned screenshot carousel on the landing page - not a video
Classroom page with first of five first-run hints: Clicking the logo brings you back to the classroom page
Classroom: first-run hint 1 of 5 - in place, skippable
1. Situation

Grupop is a classroom rewards and management web app. Its design brief was always simplicity: something teachers can fold into a live lesson without breaking flow. From classroom experience, I knew teachers are already buried in paperwork, policies and procedures - they do not want another long screen, PDF or handout to study before they can get value.

Rolling out near the start of a busy school year sharpened that constraint. Product education had to feel as seamless as the product: low friction, high clarity, minimal time-to-understanding.

2. Task

As a new product, Grupop had no existing user mental model. Prospective teachers needed to grasp what it was and why it might help; new account holders needed to reach first value quickly once inside the app. The goal was an introduction as quick and stress-free as the product itself - without defaulting to heavy training collateral that would signal complexity.

3. Action - assumption, friction, pivot, solution

Starting assumption

Written instruction dumps are rarely the best way to teach a tool. I barely considered a long help document and initially assumed a video tutorial would engage people more naturally - one medium to explain the product to the outside world.

The friction problem

While building the app I had invested heavily in speed: a teacher can complete setup in under a minute. Planning the video exposed a mismatch. Explaining Grupop often took longer than using it. By the time a narration covered what the product was, a minute could pass before setup even began. A walkthrough meant to prove simplicity was becoming anything but simple for the viewer.

That would erode trust. If the product’s job is to take pressure off teachers, asking them to risk four or five minutes on a tutorial before they even know whether it is worth their time works against the brand. The medium was raising perceived complexity and delaying the aha moment.

Experimentation: strip the medium back

To shorten time to understanding I iterated toward less, not more:

  • Captions instead of narration → short clips instead of one long walkthrough → captioned stills instead of clips or GIFs.
  • Endpoint: if the “video” was only screenshots and captions, video itself added friction (play, wait, scrub) without adding clarity.

The pivot: two audiences, two jobs

The deeper issue was not only length - it was scope. One artefact was trying to teach what Grupop is, why it might help, and how to use it. Those are different learning moments for different audiences:

  • Pre-signup (prospects): product education - understand the value proposition fast enough to decide whether to try it.
  • Post-signup (new users): first-run guidance / activation - orient inside the real UI and reach time-to-value without a separate training course.

Treating “the flyer” and “the instruction manual” as the same deliverable was the constraint. Separating them unlocked progressive disclosure: right content, right stage.

Solution: clear paths for each stage

Pre-signup - Welcome page carousels. Two carousels of six captioned screenshots on the landing page (grupop.ie/welcome). Carousel 1 explains core rewards mechanics in seconds. Carousel 2 introduces secondary features for visitors who want more depth. Split this way, the core idea is scannable immediately; deeper features are optional - speed and simplicity without dumping everything at once.

Post-signup - five contextual hints. Inside the app, screenshots were unnecessary: users are already in the product. After a self-explanatory setup (<1 minute), five single-sentence hover hints appear on the main classroom page - the hub teachers use day to day. Strict rule of five: no multi-step modal tour, no mandatory walkthrough. Hints are dismissible. If more than five tips were required to explain the core loop, the fix would be simplifying the UI, not adding more guidance.

4. Result & takeaways

The outcome was a product-led path where the interface largely speaks for itself, instead of pulling people away into long external training. Showing the product in context builds trust more readily than over-explaining from a distance.

  • Pre-signup: scannable product education that protects time to aha.
  • Post-signup: minimal effective first-run guidance aimed at fast activation.
  • Design rule: knowing when not to build heavy enablement collateral is part of enablement - friction is a signal, not something to paper over with video.

Built by a former primary and special education teacher. About · Try the Welcome page