Every box below is an abstract placeholder — no real questions, no real labels, just the shape of the interaction. Click each demo to trigger the behavior it's named for. The citation under each card points to where that exact pattern lives in the real Change Request form.
Answerable option
Selected
Newly revealed content
Step in left nav
!
UX challenges this form has to solve
The problems behind the 12 patterns below — click a tag to jump to the pattern that addresses it
Navigation & orientation
01
Path-length surprise
Q3 is a blind 4-way fork — picking "System change" commits you to a ~30-question journey with 3 nested levels, while "Flag an issue" is 4 questions. Nothing signals that imbalance before you click.
02
Depth disorientation
Path A → Q8 Add → Q18 Integration is 3 branch-levels deep. Easy to lose track of which top-level path you're still in.
03
Convergence ambiguity
Every path lands on the same closing section (Q50–53). Does the user trust that's intentional, not a glitch or a shortcut they got cheated out of?
Cognitive load & scannability
04
Long-form fatigue
Even within one relevant path, a fully expanded list of questions is exhausting; needs the answered-state collapse to stay scannable.
05
Re-findability after collapse
Once 20+ questions are collapsed to one-liners, how does a user locate and reopen one specific answer to fix a mistake, across sections?
06
Non-monotonic progress
The "X/Y answered" counter can drop when a branch reveals new required questions. Progress that moves backward is confusing if unexplained.
Trust & transparency
07
Unexplained appearances
When Q23 appears because Q22 = Yes, does the user understand why, or does it feel like the form glitched?
08
Invisible multi-field logic
RULE001 and RULE002 fire from combinations of answers the user never sees stated anywhere. A requirement that appears "from nowhere" erodes trust.
09
Silent governance consequences
Picking "Emergency" or "Production" quietly escalates risk tier and changes who has to approve the request. A user may not realize they just triggered executive sign-off.
10
Audit trail for skipped content
Q18 = No skips Q19–26 entirely; nothing in the submitted record says those 8 questions were intentionally not asked. A reviewer sees an absence, not a decision.
Data integrity
11
Stale, contradictory answers
If a user changes Q3/Q8/Q31 mid-flow, old answers from the path they left need to be invalidated, or the submission carries contradictory data.
12
Surprise data loss
Cascading-clear solves the integrity problem but creates a new one: a user who backtracks may feel the form "ate" answers they already gave, with no warning.
Scope & audience
13
One form, four mental models
"Add a new system" and "Flag a metadata issue" are different jobs wearing the same form shell. Switching via Q3 has to feel purpose-built, not generic.
14
Dev tooling bleeding into end-user UI
The branch console (tree/log/rules/JSON) is clearly built for reviewers, not the person filling out the form. Where's the line between submitter view and governance view?
15
Branch-conditional required-ness
Validation has to know a hidden question isn't required, but the same question becomes required the instant a branch reveals it — easy to get wrong at the edges.
A
Per-question behaviors
What happens the moment a single question is answered
01
No-Op Selection
Picking an option sets a value — nothing else on screen changes.
SEEN IN Q1, Q2, Q4–Q7, Q9–Q17 — most questions in the form
02
Inline Reveal
One option reveals a follow-up question directly below it, in the same place.
SEEN IN Q8 Modify → Q27 · Q22 Yes → Q23 · Q31 Add → Q32–Q37
03
Off-Canvas / Nav-Only Branching
The current question never changes — a new step quietly appears in the left nav instead.
SEEN IN Q3 routes to a path section · Q18 Yes → activates the Integration section
04
Multi-Way Fork
One question routes to one of three or four entirely different destinations.
SEEN IN Q3 (4-way: System / Metadata / Reference / Issue) · Q8, Q31, Q41 (3-way: Add / Modify / Retire)
05
Nested / Multi-Level Branching
A fork inside a fork inside a fork — each level only appears once the one above it qualifies.
SEEN IN Q3 → Path A → Q8 Add → Q18 Integration — three levels deep
06
Skip-Ahead
One option jumps over a whole stretch of questions instead of revealing or hiding them one by one.
SEEN IN Q18 No → skips Q19–Q26 entirely, jumps straight to Q28
B
Cross-field & system behaviors
Effects that depend on more than one answer, or live outside the form itself
07
Cross-Field Rule Trigger
A reveal driven by the combination of two separate answers, not either one alone.
SEEN IN RULE001 — Q29 = Yes AND Q30 = Yes → reveals Q75 cross-impact assessment
08
Path Convergence
Whichever path the user took, the form re-merges into one shared closing section.
SEEN IN Paths A, B, C, D all funnel into the same closing section (Q50–Q53) before Review
09
Global Chrome Side-Effect
An answer changes something outside the form entirely — here, a status pill in the top bar.
SEEN IN Q6 Emergency / Q2 Production → top-bar risk pill escalates, approver chip appears
10
Cascading Invalidation
Changing an earlier branch answer auto-clears downstream answers that no longer apply.
✓
✓
✓
SEEN IN Switching Q3, Q8 or Q31's branch clears any answers collected on the path you left
11
Answered-State Collapse
An answered question collapses to a one-line summary to keep long forms scannable.
✓change
SEEN IN Every answered question on v4-hybrid collapses into a one-line summary row
12
Dynamic Stepper
The left nav recomputes its entire step list from the chosen path on every answer.
SEEN IN Left nav only ever lists sections that are active for the path you chose