3 min read

One Training Website, Three Different Needs

A fictional worked example: help people choose a useful route without guessing who they are.

On this page — choose a section

This is a fictional design scenario, not a customer case study or measured result. The people’s needs are stated for the example; they are not facts discovered from browsing.

The setup

A leadership-development organization offers team programs, open-enrollment courses and facilitator certification. Three people arrive with different tasks:

  • Visitor A — corporate buyer. Comparing training for a team of 150.
  • Visitor B — individual learner. Looking for a course with a suitable date, price and format.
  • Visitor C — aspiring certified facilitator. Checking the certification requirements and next steps.

A useful site should make all three routes understandable. It does not need to identify someone’s job or predict a purchase to do that.

The traditional site

In this fictional starting point, one dense homepage mixes the three offers. Its “Contact us” form gives no indication of which team will answer or what information would help.

A clearer static page and better navigation might solve the problem. Adaptation is worth trying only if it adds something useful beyond that improvement.

The visitor-aware version

The page asks: “What are you looking for?” It explains that the answer changes which offer appears first, not prices, eligibility or access. “Show all options” remains available.

This scenario uses explicit choices. Any cross-visit memory or human handoff would be a separate, explained option—not a hidden consequence of answering.

Visitor A's second visit

If Visitor A chose to save a team-training scenario, the site offers “Resume your team-training comparison” and “Start fresh.” Without that saved context, it shows the ordinary page.

  • Team-program information appears first after the visitor chooses that route.
  • Individual courses and certification stay reachable through stable navigation.
  • A saved calculator input is labeled as the visitor’s assumption, not a fact about their organization.
  • “Discuss team training” opens a matching inquiry. The person can review and edit an optional summary, choose the recipient and remove the summary before sending.

The advisor could start with the context actually shared. Whether this saves time or improves the conversation must be tested.

Visitor B's first visit

After choosing individual learning, Visitor B sees dates, formats and prices first. The page explains the change and keeps the other offers accessible.

“View course dates” leads to dates—not to an unexplained sales form. A reservation label would be appropriate only if the destination really supported a reservation.

Visitor C's first visit

After choosing facilitator certification, Visitor C sees requirements, costs and the sequence of steps first. “Explore the certification path” leads to that information. It does not claim the visitor is eligible or silently submit an application.

What changed under the hood

  1. An explicit input: the visitor chooses a task, with a clear explanation of its effect.
  2. A bounded rule: relevant content moves first; essential facts and stable navigation remain.
  3. A useful default: missing, unknown or cleared choices return to the complete ordinary page.
  4. Optional continuity: any saved scenario needs a defined lifetime and visible reset controls.
  5. A reviewed handoff: only context the person selects goes to the explained recipient.

These options are discussed in the Patterns Library. The first-build guide demonstrates the smaller choice-and-order rule without memory or a handoff. A CMS can support either approach; a full rebuild is not assumed.

The cold-start arithmetic

A handoff might reduce repeated questions, but this scenario supplies no measured time savings. Establish a baseline and compare useful outcomes, staff effort, mistaken assumptions and the visitor’s experience. Include the cost of implementation and ongoing review.

Do not collect or retain a full browsing history just to make a hypothetical savings calculation look attractive.

What this scenario demonstrates

The example shows how three clearly stated tasks could lead to different starting points without hiding the rest of the site. It does not prove that adaptation outperforms good navigation, that the categories fit real visitors, or that a behavioral model can identify them accurately.

Start by testing the clearer ordinary experience. Add the small rule only if it helps people complete the task.

Further reading