Support learning

Learning requires challenge. New skills emerge when people exert effort—or so the traditional assumption goes. However, customers abandon tasks when overwhelmed and remain passive when tasks appear too complex. The question is: How much support do people need to develop new skills? When does help become a hindrance—and what does the evidence show?

Studies

The Tutorial Experiment

David Wood, Jerome Bruner, and Gail Ross coined the term "scaffolding" in 1976 through an experiment with 3- to 5-year-old children at Oxford University. The children were asked to build a complex pyramid from wooden blocks—a task they could not solve on their own. A tutor sat with each child and offered graduated assistance: first demonstrating partial steps, then providing verbal cues, and finally offering only confirmation. The remarkable finding: children who received this systematic reduction of support were later able to solve the task independently. Children without scaffolding or with constant help failed. The success rate increased from 0% without assistance to 87% with properly timed scaffolding.

The Software Tutorial Study

Sadhana Puntambekar and Roland Hübscher investigated how digital scaffolding works in a 2005 study at Rutgers University. They assigned 156 students to learn complex statistical software under three conditions: one group received adaptive scaffolding (support that automatically decreased based on performance), another received fixed scaffolding (consistent support throughout), and a third received no help. After four weeks, clear differences emerged. The adaptive group achieved 78% independence in complex analyses, while the fixed-help group reached only 34%—they continued clicking help buttons rather than thinking independently. The control group without scaffolding had a 45% dropout rate. The surprising finding: too much help proved almost as detrimental as none at all.

Principle

Which principle for Customer Experience Design can be derived from this? The Scaffolding Principle demonstrates that successful customer experience emerges through intelligent, temporary support that guides users step-by-step toward independence. Rather than permanently hand-holding customers or abandoning them entirely, companies should strike a balance: providing sufficient help to get started while systematically reducing this support as competence develops. This principle works particularly well for complex products or services, where users may initially feel overwhelmed but should ultimately operate independently. The key is communicating from the outset that support measures are temporary and framing the reduction of assistance as a sign of growing competence. The following guidelines show how to implement this principle in practice.

Guidelines

Tiered onboarding assistance with gradual reduction

New users require intensive support—tooltips, guided tours, and sample data. However, these aids must systematically fade once users achieve basic competency. Track usage patterns and reduce assistance after successful repetitions. Make this reduction visible: "You've successfully used Feature X three times—from now on, you're on your own." This signals competency growth and motivates continued learning.

Progressive task complexity

Begin with simplified versions of complex tasks. For example, a financial dashboard initially displays only the three most critical metrics rather than all 20. A CRM system first activates basic functions, with advanced features unlocked only after successful usage. The key is ensuring users experience mastery before complexity increases. Communicate progress clearly: "Level 1 mastered—ready for advanced features?"

Contextual Just-in-Time Help

Provide help exactly when it's needed—not beforehand as an overwhelming flood of information. When a user opens a filter for the first time, display a brief tooltip. The second time, reduce it to an icon reminder. By the third time, remove the help entirely. Crucially, the help must be contextual to the task, not relegated to a separate tutorial section. This approach reduces cognitive load and enables learning by doing.

Simplify competency-based navigation

Navigation should scale with user competency. Beginners see a highly simplified menu structure featuring the 5-7 most essential functions. Intermediate users access additional options, while experts receive full control. Include explicit 'Simplify/Expand' toggles. Software like Photoshop demonstrates this approach: a beginner mode dramatically lowers the entry barrier while leaving power users unrestricted. The transition should be gradual rather than binary.