When onboarding combines multiple supports—such as goal-oriented wizards, prompt galleries, and power-user walkthroughs—which sequences and timings of these elements most effectively reduce time to (a) first reusable workflow and (b) stable independent execution, and how do these optimal sequences differ between scaffold-heavy versus bottom-up, exploratory adoption environments?

Answer

Most effective patterns are short, staged sequences that front‑load success (wizard), then expose patterns (gallery), then teach strategy (power‑user). Timing and aggressiveness differ by environment.

a) Fastest path to first reusable workflow

Scaffold‑heavy environments

• Day 0–1: Lead with a narrow goal‑oriented wizard tied to 1–2 high‑value tasks. Auto-save the resulting flow as a named reusable workflow.
• After 3–5 runs of the same wizard: Surface small, in‑context variants from a mini gallery (“other ways to run this task”) seeded by org‑approved prompts.
• After 5–10 runs: Convert the most used wizard flow into an editable personal variant and nudge “make this your default workflow.”

Bottom‑up / exploratory environments

• Day 0: Start with a very short gallery pass (“pick 1–2 examples for your job”), then a single wizard for the chosen example.
• First week: Interleave light gallery surfacing before each new task (“similar workflows others use”) rather than repeating the same wizard.
• As soon as a pattern repeats ≥3 times: Suggest “save as workflow” and make that the entry point for that task.

Net effect: In scaffold‑heavy settings, wizard‑first sequences minimize time to first reusable workflow; in bottom‑up settings, gallery‑first then a targeted wizard works better because it helps users find good candidates for reuse.

b) Fastest path to stable independent execution

Scaffold‑heavy environments

• After N successful guided runs (typically 3–6): Start each run in “expanded” view showing key steps and 1–2 editable fields (goal, audience).
• After user edits and reuses the same workflow ≥2 times: Offer a short, inline “power‑user replay” of someone running a similar workflow end‑to‑end, emphasizing how they change parameters.
• After 2–3 successful runs post‑replay without help: Make the customized workflow the default entry point and hide most onboarding UI for that task.

Bottom‑up / exploratory environments

• First week: Encourage small prompt edits every time a gallery prompt is used; show a compact “what changed” diff to build pattern recognition.
• After a user runs the same structure ~3 times without opening help or gallery: Trigger an optional power‑user walkthrough that explains general tactics (chunking, chaining, constraints) using their own workflow as the example.
• After that session: Pin a one‑click shortcut to the user’s version and stop re-showing galleries for that task.

Net effect: Independent execution comes fastest when galleries and walkthroughs are triggered by evidence of repetition and light editing, not just by elapsed time.

Key sequencing differences

• Scaffold‑heavy: wizard → repeated wizard → gradual parameter exposure → personalized variant → short power‑user replay.
• Bottom‑up: gallery → light wizard for a chosen pattern → repeated gallery use with edits → targeted power‑user session → pinned custom workflow.

In both cases, the optimal timing is: introduce the next support right after 2–5 successful repetitions of a pattern, and begin withdrawing heavy scaffolds once users run a personalized version 2–3 times without re-opening instructions.