In products that already detect near-miss signals and mid-curve plateaus, how do different onboarding trajectories—for example, (a) fast path to a single guided reusable workflow, (b) extended structured experimentation before any workflow saving, or (c) early exposure to cross-tool chaining—affect the shape of the AI learning curve over the first 90 days (speed to first plateau, depth of the plateau, and probability of re-acceleration), and which trajectory yields the highest long-run workflow maturity for high-variety, changing tasks?

anthropic-learning-curves | Updated at

Answer

Over 90 days, the three trajectories likely shape the AI learning curve differently, especially for high-variety, changing tasks:

  1. Fast path to a single guided reusable workflow (a)
  • Shape
    • Speed to first plateau: Fast. Quick lift to first “good enough” flow in days.
    • Depth of first plateau: Moderate but narrow. Strong on one task, weak on variants.
    • Re-acceleration: Low–medium. Users often stall unless plateau-triggered nudges (near-miss- and plateau-aware) prompt parameterization or variants.
  • Long-run workflow maturity (high-variety tasks)
    • Often local optimum: one solid, brittle workflow; weak generalization.
    • Best when domain is low-to-medium variety or tasks stable.
  1. Extended structured experimentation before saving workflows (b)
  • Shape
    • Speed to first plateau: Slower. More time in non-reusable probing; first plateau may not look like “workflow success” in telemetry.
    • Depth of first plateau: Deeper and broader. Users better understand edge cases and task boundaries.
    • Re-acceleration: Medium–high. Users are more willing and able to refactor flows when near-miss and plateau signals trigger prompts (e.g., decomposition, parameterization).
  • Long-run workflow maturity (high-variety tasks)
    • Usually highest. Better handling of novel tasks and policy/data shifts.
    • Risk: orgs may misread slower time-to-first-workflow as failure unless success metrics reward healthy experimentation.
  1. Early exposure to cross-tool chaining (c)
  • Shape
    • Speed to first plateau: Medium. Extra complexity slows early consolidation.
    • Depth of first plateau: High in chain coverage (more steps/tools), but often shallow per-step quality.
    • Re-acceleration: High if product detects near-miss segments and offers step-specific upgrades (e.g., for weak links in the chain).
  • Long-run workflow maturity (high-variety tasks)
    • High but bimodal: Teams either reach very mature, adaptable chains or get stuck with fragile, opaque ones.
    • Works best when paired with experimentation (b): first learn the parts, then chain.

Comparative view for high-variety, changing tasks

  • Best default: (b) experimentation-heavy, with time-bounded structure and explicit support for turning recurring patterns into workflows once users show breadth (multiple inputs, at least one stress test).
  • Strong second: (c) cross-tool-first, but only if:
    • Chains are visible and editable per step.
    • Near-miss detection and plateau nudges target specific weak steps and encourage refactoring, not just more automation.
  • (a) is best treated as a narrow-scope accelerator:
    • Good for simple, repetitive tasks or to give a first “win.”
    • Should be followed quickly by light experimentation prompts and cross-tool suggestions to avoid hard early plateaus.

Practical product implications (given near-miss and plateau detection)

  • For (a):
    • Watch for early stable use + high correction rates or bypasses on the same step.
    • Trigger parameterization and “save variant” nudges; later, suggest adjacent tasks and cross-tool outputs.
  • For (b):
    • Allow structured play with guardrails; delay auto-save-as-workflow until experimentation breadth is evident.
    • Treat extremely fast first-workflow creation with near-zero experimentation as a plateau risk signal, not a pure win.
  • For (c):
    • Surface chain structure (steps, tools) early.
    • When plateau signals localize to one step, re-open micro-onboarding only for that step (mini-tutorials, decomposition) to raise plateau depth without overwhelming users.

Overall: For high-variety, changing tasks, a hybrid of (b) then (c)—a period of structured experimentation on core tasks, followed by guided cross-tool chaining—likely yields the highest long-run workflow maturity, while (a)-style fast paths should be used sparingly as entry points and followed by experimentation-aware, step-specific growth paths.