Claim and evidence
Show a pre-populated example project in the empty state so the interface introduces itself.
No dated example yet. Treat this tactic as a hypothesis.
Anecdotal
Practitioner experience without published numbers.
Historical · 2026-11 Interview from 2014; practice persists in many tools but no data fetched.
What the numbers show
No published number for this tactic has passed our word-for-word check yet, so there is no chart.
Why it works
People understand a product faster from a finished example than from a blank canvas.
How to run it
- Create a realistic sample project
- Show it in the first empty state
- Make it easy to delete
- Point to what the real version would look like
Before / after
Generalised wireframe of the pattern, not a copy of any company's screen.
Ways to run it
Design options to test, not promised results.
- Option ADemo project
Show a filled-in example project in the empty state so the interface introduces itself, as Basecamp did.
- Option BEasy to remove
Label the sample clearly and offer one-click deletion so it never clutters real work.
- Option CPoint to the real version
Next to the sample, explain what the user's own project will look like.
Timeline
- 12014 first documented: Samuel Hulick, Heavybit interview
- 22014 Basecamp — Pre-populated demo projects in blank states; Hulick says the interface "uses itself to introduce itself".
- 32026-11 status checked: Historical
Dated examples
- 2014
Basecamp
Pre-populated demo projects in blank states; Hulick says the interface "uses itself to introduce itself".
No metric.
heavybit.com · 2014-08-05
Does it still work?
Interview from 2014; practice persists in many tools but no data fetched.
Risks
- Sample data can be mistaken for real data
Sources
Change log
- 2026-11-20 — status working -> historical (only an old case, not re-checked)
- 2026-11-20 — harvest v0.1 (activation)