Structural exploration — [question under review]

Three wireframe directions for the same brief. Compare layout, hierarchy, navigation, and reflow — before any visual design.

Tier-1 disposable · canonical source: none · review question: [what should be on the screen / how should the task work]

A · Overview-first

Tradeoff: best for orienting newcomers; the primary action sits below the fold.

[product name]
Primary action
Feature one
Feature two
Feature three
Annotation — assumption: the review question is about first-run orientation, so content density is low here. [Change if the real question is task speed.]

B · Task-first

Tradeoff: one dominant path, minimal distraction; secondary functions are tucked into the top-right menu.

Start
Open question: should the task run inside this screen or navigate to a dedicated flow?
Annotation — behavior: the primary CTA is the only color-anchor; everything else recedes on purpose. [Structure question: does making one path dominate hurt discovery?]

C · Split-pane

Tradeoff: strongest for working against live content (two things at once); most complex at mobile width.

List / index
KPI
Detail / editor
Annotation: master-detail pattern. What happens when the panel is the whole screen on mobile?
Annotation — responsive: on ≤700px the split collapses to stacked panels; verify the hierarchy survives.
Review question: [the structural decision this exploration exists to settle]. Pick a direction, then hand the winner to html-plan / html-prototype as appropriate.