Prototype — Phase: Design

Change Request Form

Three UX explorations of the same branching questionnaire engine. Same JSON workflow, same rule engine, three completely different interaction models.

Safe
Variation 1
Step Wizard
Traditional multi-step form with a left sidebar showing section progress. One section at a time, clear back/next navigation. Familiar to all users.
Left sidebar nav Section-by-section Back/Next buttons Review screen
Open Variation 1 →
Balanced
Variation 2
Command Centre
Dark-mode split layout. Left panel shows a live branch map. Right panel shows real-time state: active sections, fired rules, and the payload preview.
Dark theme 3-column layout Live rule preview Branch map
Open Variation 2 →
Experimental
Variation 3
Flow State
No steps. Questions cascade down the page as you answer. New sections emerge inline. A floating minimap keeps you oriented. Feels like a conversation unfolding.
Cascade scroll Inline sections Floating minimap Collapse answered
Open Variation 3 →

All three variations share the same engine

JSON-driven workflow — no code changes needed to update questions
Real branching: sections activate/deactivate based on answers
Nested questions: Q12 appears only when Q11 = "downtime required"
Multi-condition rules: Q75 appears only when both Q29 + Q30 = Yes
Risk level computed live (LOW → MEDIUM → HIGH → CRITICAL)
Approvers auto-assigned based on environment, urgency, type
Label prefixes ([Q1], [Q29], etc.) for dev/business/client traceability
Submission payload: answers + activated sections + rules triggered
Demo tip: To see branching in action — in any variation, answer Q3 as "System Change" to unlock the System Changes section. Then answer Q18 = "Yes" (integrations) to unlock the Integration section. Answer both Q29 = "Yes" and Q30 = "Yes" to trigger Rule RULE001 and see question Q75 (Cross-Impact Assessment) appear.