# Video ordering / Order flow
ScreensFlow
An order flow, one step at a time
A step-by-step flow for ordering creator videos, with the scope set on the left and a live preview on the right.
View on DribbbleThe work
The moments we design
The paths we map before anyone designs a screen.
- Task flows
- Screen flows
- Decision points
- Alternate paths
- Errors and failure points
- Sign-up and log-in flows
- Checkout and payment flows
- Flows for different roles
- Flows across devices
- From flow to wireframe
- Flows to prototype
- Flow specs for developers
The problem
Sounds familiar?
If 2 or more of these ring true, map the flow before designing more screens.
{{ countLabel }}
{{ ctaText }}Book a call
Selected work
Selected flow work
Screens on Dribbble and Behance
# Influencer Marketing AI / Report flow
ScreensScreen flow
From a question to a report
The screens behind creating a report, from AI search and a custom query builder to report processing.
View on BehanceProof
“When we bring her a new feature idea, she quickly turns it into thoughtful design options with relevant user states, journeys, and clear assumptions.”
- Upwork Job Success
- 100%
- Regular clients
- 10+
- Recognized by
- Dribbble Select
Ways to start
2 ways to start
Map a new feature, or fix a flow people struggle with.
-
# New feature
Map the flow first
Every step, decision and failure point, mapped before the screens.
- Task and screen flows
- Alternate and error paths
- Open questions for the team
- Flow file in Figma
-
# Existing flow
Fix a flow that leaks
Find where people get stuck, then redesign the steps that cause it.
- Review of the current flow
- Friction points
- Redesigned flow and screens
- Handoff in Figma
01What’s the difference between a user flow and a screen flow?
A user flow shows the decisions and actions. A screen flow shows the actual screens for each step. We usually do both.
02How long does a project take?
It depends on the scope. Once we’ve seen the full picture, we’ll share a rough timeline.
03Do you include error and edge paths?
Yes. Failures, alternate roles and interrupted tasks are part of every flow we map.
04Can our developers use the flows?
Yes. The flows show every state and path, so developers know what to build.
05What comes after the flow?
Wireframes or UI, depending on how clear the screens already are.