Plotline onboarding: six directions

Six first-run screens that differ in layout, tone and density, each with the tradeoff it makes

Plotline is a project tracker for small agencies. The first-run screen appears right after sign-up and has one job: get a new user to their first real project. The six directions below are deliberately far apart. Each card states the tradeoff it is making, then its layout, tone and density, then a wireframe.

The six directions

1. One Pass

Tradeoff: fastest to finish and easiest to build, but it looks like paperwork.

  • Layout: one column, every field visible at once
  • Tone: terse and neutral ("Set up Plotline")
  • Density: high, 6 inputs on one screen
+------------------------------+
| Set up Plotline              |
| Name      [______________]   |
| Role      [______________]   |
| Team size [______]           |
| Work email [_____________]   |
| Found us via [___________]   |
| [x] I agree     [ Create ]   |
+------------------------------+

2. Guided Wizard

Tradeoff: collects clean profile data and feels supportive, but it delays the product by four screens.

  • Layout: centered card, stepper at the top, one decision per step
  • Tone: warm and conversational ("What kind of work do you do?")
  • Density: low, about 2 inputs per step
+------------------------------+
|  (1)--(2)--(3)--(4)          |
|                              |
|  What kind of work do you    |
|  do?                         |
|    ( ) Agency  ( ) In-house  |
|                              |
|  Back                [ Next ]|
+------------------------------+

3. Checklist Dashboard

Tradeoff: no gate before the app, but a user can ignore the checklist and never reach value.

  • Layout: the real app shell with a pinned progress panel
  • Tone: task-oriented ("2 of 5 done")
  • Density: medium, 5 actions visible with progress
+------------------------------+
| Welcome, Sam.    2 of 5 done |
| [########-----------]  40%   |
| [x] Create your first project|
| [x] Add a client             |
| [ ] Invite a teammate        |
| [ ] Connect your calendar    |
| [ ] Send a first update      |
+------------------------------+

4. Personalization Quiz

Tradeoff: strongest tailoring and a playful first impression, but six screens before any product.

  • Layout: one big question per screen, large tap targets, full bleed color
  • Tone: playful and chatty ("How do you run your Monday?")
  • Density: very low, 1 question and 2 to 4 answers per screen
+------------------------------+
|           3 / 6              |
|   How do you run your        |
|   Monday?                    |
|  +-----------+ +-----------+ |
|  |  Lists    | |  Boards   | |
|  +-----------+ +-----------+ |
+------------------------------+

5. Template First

Tradeoff: near-instant time to value, but a user with an unusual workflow sees nothing that fits.

  • Layout: gallery of 6 starter projects, a single click starts one
  • Tone: minimal, almost no copy
  • Density: medium, 6 visual tiles and one escape hatch
+------------------------------+
| Start from a template        |
| +-------+ +-------+ +------+ |
| | Brief | |Launch | | Audit| |
| +-------+ +-------+ +------+ |
| +-------+ +-------+ +------+ |
| |Retain | |Pitch  | | Event| |
| +-------+ +-------+ +------+ |
|          [ Start blank ]     |
+------------------------------+

6. Sandbox Tour

Tradeoff: teaches by doing and needs no setup, but it is the most work to build and keep current.

  • Layout: a populated sample project with coach marks over the real UI
  • Tone: instructional ("This is a task. Drag it to Done.")
  • Density: high, a full board plus one tooltip at a time
+------------------------------+
| Sample: Acme Rebrand         |
| +-----------+                |
| | To do|Done|  (1) This is a|
| | [ ] [ ]   |  task. Drag it|
| +-----------+  to Done.     |
| [Skip tour]  [Use my own 1/5]|
+------------------------------+

Side by side on the three axes

directionlayouttonedensitybest when
1. One Passsingle columntersehighusers arrive with intent, such as invited teammates
2. Guided Wizardstepper cardwarmlowyou need profile data to route the user
3. Checklist Dashboardapp shell plus paneltask-orientedmediumthe product explains itself in seconds
4. Personalization Quizfull-bleed questionsplayfulvery lowthe audience is mixed and engagement is the risk
5. Template Firsttile galleryminimalmediumcommon workflows cover most of your users
6. Sandbox Tourcoach marks over sample datainstructionalhighthe product is unusual and needs demonstrating

What each costs the user

Estimated effort before the user reaches their first project.

Estimated seconds to first project
1 One Pass75 s
2 Guided Wizard140 s
3 Checklist20 s
4 Quiz95 s
5 Template First30 s
6 Sandbox Tour45 s
Data
directionseconds
1 One Pass75 s
2 Guided Wizard140 s
3 Checklist20 s
4 Quiz95 s
5 Template First30 s
6 Sandbox Tour45 s
Effort estimates (lower is lighter)
directionsecondsfieldsscreens
1 One Pass7561
2 Guided Wizard14074
3 Checklist2021
4 Quiz9566
5 Template First3012
6 Sandbox Tour4505
low → high
Fields and screens per direction
Fields and screens per directionBar chart, 6 values of direction. fields goes from 6 (1 One Pass) to 0 (6 Sandbox Tour); highest 7 at 2 Guided Wizard, lowest 0 at 6 Sandbox Tour. screens goes from 1 (1 One Pass) to 5 (6 Sandbox Tour); highest 6 at 4 Quiz, lowest 1 at 1 One Pass.02.557.51 One Pass · fields: 61 One Pass · screens: 12 Guided Wizard · fields: 72 Guided Wizard · screens: 43 Checklist · fields: 23 Checklist · screens: 14 Quiz · fields: 64 Quiz · screens: 65 Template First · fields: 15 Template First · screens: 26 Sandbox Tour · screens: 5617421661251 One Pass3 Checklist4 Quiz6 Sandbox Tour
Fields and screens per directionBar chart, 6 values of direction. fields goes from 6 (1 One Pass) to 0 (6 Sandbox Tour); highest 7 at 2 Guided Wizard, lowest 0 at 6 Sandbox Tour. screens goes from 1 (1 One Pass) to 5 (6 Sandbox Tour); highest 6 at 4 Quiz, lowest 1 at 1 One Pass.02.557.51 One Pass · fields: 61 One Pass · screens: 12 Guided Wizard · fields: 72 Guided Wizard · screens: 43 Checklist · fields: 23 Checklist · screens: 14 Quiz · fields: 64 Quiz · screens: 65 Template First · fields: 15 Template First · screens: 26 Sandbox Tour · screens: 5617421661251 One Pass3 Checklist6 Sandbox Tour
Data
directionfieldsscreens
1 One Pass61
2 Guided Wizard74
3 Checklist21
4 Quiz66
5 Template First12
6 Sandbox Tour05

How to choose

One path through the questions below lands on each direction.

Which direction fits
Which direction fits11 nodes. Need profile data on day one? → Do users arrive with intent? (yes); Need profile data on day one? → Is the product obvious in 30 seconds? (no); Do users arrive with intent? → 1. One Pass (yes); Do users arrive with intent? → Is personalization the hook? (no); Is personalization the hook? → 4. Quiz (yes); Is personalization the hook? → 2. Guided Wizard (no); Is the product obvious in 30 seconds? → Do reusable starting points exist? (yes); Is the product obvious in 30 seconds? → 6. Sandbox Tour (no); Do reusable starting points exist? → 5. Template First (yes); Do reusable starting points exist? → 3. Checklist (no)d1 → d3: yesd1 → d2: nod3 → one: yesd3 → d5: nod5 → quiz: yesd5 → wiz: nod2 → d4: yesd2 → sbx: nod4 → tpl: yesd4 → chk: noNeed profile dataon day one?Is the productobvious in 30seconds?Do users arrivewith intent?Do reusable startingpoints exist?Is personalizationthe hook?SVC1. One PassSVC2. Guided WizardSVC3. ChecklistSVC4. QuizSVC5. Template FirstSVC6. Sandbox TourYESNOYESNOYESNOYESNOYESNO
  1. Need profile data on day one? → Do users arrive with intent?: yes
  2. Need profile data on day one? → Is the product obvious in 30 seconds?: no
  3. Do users arrive with intent? → 1. One Pass: yes
  4. Do users arrive with intent? → Is personalization the hook?: no
  5. Is personalization the hook? → 4. Quiz: yes
  6. Is personalization the hook? → 2. Guided Wizard: no
  7. Is the product obvious in 30 seconds? → Do reusable starting points exist?: yes
  8. Is the product obvious in 30 seconds? → 6. Sandbox Tour: no
  9. Do reusable starting points exist? → 5. Template First: yes
  10. Do reusable starting points exist? → 3. Checklist: no
DECISIONSVC

Recommendation


Back to the examples