NotionProduct Thinking6 min readMaking a blank page survivable
The hardest screen in Notion is the one with nothing on it.
- The surface
- The first workspace after signup: the new page screen, the template picker, the slash command, and the sidebar of starter pages.
- What the user wants
- I have a mess of notes and tasks in five places, and I want one place that finally holds them without me having to build a system first.
The new page
A new Notion page opens as a near empty canvas with a title field and a short set of starting options, including templates and importing from other tools.
The empty state: What a screen shows before there is any content in it. is a design surface
A blank page is the worst moment in any flexible tool, because flexibility means the product cannot tell the user what to do next. Notion treats that screen as real estate for options rather than leaving it clean. What is offered there defines what most users believe the product is for.
Starter pages in the sidebar
New workspaces have long arrived with example pages already present, such as a task list or a simple document, rather than an empty sidebar.
Seeded content beats instructions
A populated workspace shows the structure of the product without a tour, because the user can open a page and see what a good one looks like. It also means the first action is editing something rather than creating something, which is a far lower bar. Deleting an example is easy and teaches the model too.
The template gallery
Templates are grouped by use case, such as project tracking, notes or a wiki, and can be duplicated into the workspace in one action.
Recognition over recall
Most people cannot describe the system they want, but they can point at one. Browsing named use cases turns an open ended build into a choice from a list. The duplicated page also arrives already filled with sample rows, so the user is editing rather than starting.
The slash command
Typing a forward slash inside a page opens an inline menu of every block type, filtered as the user keeps typing.
progressive disclosure: Showing the few controls most people need, and keeping the rest one step away.
Notion has a large vocabulary of blocks, and a visible toolbar holding all of them would be unreadable. Hiding the vocabulary behind one keystroke keeps the page calm while making the full set one character away. The discoverability cost is paid once and repaid every session.
Databases introduced as views
A table, board, calendar or list can be created as views over the same underlying database, and views can be switched without moving the data.
One model, many surfaces
Users think in artifacts (a board, a calendar) rather than in schemas. Letting them start from the artifact they recognise and discover later that it was a database all along delays the conceptual cost until they are already invested. The switch between views is what teaches the model.
Building the workspace as commitment
Pages are nested inside pages, and the sidebar grows into a structure the user has arranged themselves.
IKEA effect
People value things more when they built them, and a Notion workspace is unavoidably self-built. Every hour of structuring raises the perceived cost of moving elsewhere, even when the underlying content would export fine. The switching cost here is emotional before it is technical.
What the blank page ends up meaning
What not to copy
- Templates create a cliff. The duplicated page looks professional and the user's own second page does not, so the gap between the demo and their real work becomes a reason to stop.
- Flexibility postpones the decision rather than removing it. Notion is very good at letting someone build the wrong system quickly, and the product gives almost no feedback that a structure is going to fall apart at scale.
- The slash menu is invisible until someone tells you about it. A keyboard-first vocabulary in a tool aimed at non-technical teams leaves a large group using perhaps a tenth of the product.
- Starter content in a shared workspace ages into clutter. Example pages that nobody owns tend to sit in the sidebar for months, which teaches teams that the sidebar is not trustworthy.
The takeaway
If your product is flexible, the empty state is your real onboarding, and whatever you put there becomes the definition of what the product is for.
Finished the teardown? Bank it and the day counts toward your run.
Where the principles come from
- Progressive Disclosure, Jakob Nielsen, NN/g
- Recognition vs. Recall in User Interfaces, NN/g
- The IKEA Effect: When Labor Leads to Love, Norton, Mochon and Ariely
- The Design of Everyday Things (conceptual models, affordances), Don Norman
Written from public behaviour of the product, not from inside it. Interfaces change often, so treat the flow described here as of the time of writing and check the live product before quoting it.