First-time use. Shows the map but not the destination.
The framework
It depends on the task.
Conversational interface
When the task is ambiguous, exploratory, or generative
Lets users explore without a defined path
Handles open-ended, creative inputs well
Feels human and low-friction
Graphical interface
When the task is structured, repetitive, or high-stakes
Shows users what's possible at a glance
Guides them through clear, repeatable steps
Reduces effort for known actions
The question
What if we kept what conversation does well and added structure where it falls short?
Before
What would you like to do?
↑
+ structure
After
What would you like to do?
Plan a sprint
Onboard my team
Just exploring
↑
↖Same conversation. But now the user can see what's possible.
Act 3 of 3
Onboarding with both, working together
FlowBoard — Welcome back
What brought you here today?
↑Your turn — tap one
Got it. Here's where to start.
Sprint board
My tasks
Team
Start here
Add your three highest-priority tasks for this week.
↖One question. One tap. The product figured out what you needed.
The reveal
Why the combined approach worked
What just happened
1AI inferred intent from one tap, not a typed prompt
2The graphical interface reorganised itself around that intent
3A single, specific next action replaced the menu of possibilities
↖The graphical interface gave structure. The AI gave it intelligence. Neither could've done this alone.
Why this works
Users don't have to know what they need — the interface infers it. Structure handles affordance and predictability; AI handles personalisation and intent.