Skip to main content
Worknestle

What we build

Four things make a workspace worth keeping, and none of them is a longer page

Databases joined to each other so nothing is written twice. Views that answer a question instead of listing everything. Templates so the tenth start is set up like the first. And a way in for somebody who was not there when it was made. Everything below is a schema of how those four fit together, drawn in plain shapes.

Three shapes of job

Personal, team, knowledge base

They are listed in this order because they build on one another, but a job is not obliged to start at the beginning. Which of the three you need depends on where the work already is.

One person, working alone

Personal notes and tasks

Notes in one application, tasks in another, and the thing you wrote down last Tuesday nowhere either of them can find it.

Databases it needs

  • Inbox
  • Tasks
  • Projects
  • Notes

What gets built

  • One inbox that takes anything, typed in a hurry, sorted later.
  • A task list that knows which project each task belongs to.
  • A notes database joined to those projects, so a note is never orphaned.
  • One home page showing what is in hand today and nothing else.

Two to a dozen people who hand work to each other

Projects for a small team

Everybody knows what they are doing and nobody can see what anybody else is waiting on.

Databases it needs

  • Projects
  • Tasks
  • Meetings
  • Clients

What gets built

  • Projects and tasks joined, so a project shows its own work without anybody copying it across.
  • A board by status and a schedule by week, over the same records.
  • Meetings filed against projects, with decisions leaving the meeting as tasks.
  • A project template, so the tenth project is set up like the first.

A team that keeps answering the same question

An internal knowledge base

The answer exists. It is in somebody’s head, a message thread and a document nobody can find, and all three say something slightly different.

Databases it needs

  • Handbook
  • Notes
  • Tasks
  • Projects

What gets built

  • One handbook database, by topic, with a named keeper for each entry.
  • A review property, so an entry that has gone stale says so rather than being quietly wrong.
  • Entries joined to the tasks and projects that use them.
  • A way in for a new starter that does not depend on somebody being free to explain.

Part one

Databases, and the joins between them

A database is a list that knows what its rows are made of. The work happens in the joins: a relation means a project can show its own tasks, and a task can say which project it belongs to, without either being typed twice.

The databases, and what one row of each of them is.
Database One row is Properties that carry the work
Inbox Anything caught in a hurry, before anybody has decided what it is.
  • Caught
  • Sorted
  • Becomes
Projects One piece of work with a beginning and an end.
  • Stage
  • Owner
  • Client
  • Opened
  • Tasks
Tasks One thing somebody has to do next.
  • Status
  • Project
  • Owner
  • Week
  • Blocked by
Clients One organisation the owner of the workspace works for.
  • Account
  • Main contact
  • Projects
  • Notes
Meetings One conversation and what was decided in it.
  • Date
  • Present
  • Project
  • Decisions
  • Tasks raised
Notes Anything written down that is not yet a task.
  • Source
  • Project
  • Written
  • Follows on to
Handbook How a thing gets done here, written once.
  • Topic
  • Keeper
  • Last read through
  • Used by
The joins. A relation is read from both ends, which is the whole point of having one.
Join What it means in practice
Inbox Notes What was caught in a hurry becomes a note, or a task, or nothing.
Projects Tasks A project holds the tasks that move it on.
Projects Clients A project belongs to one client account.
Meetings Projects A meeting is filed against the project it was about.
Meetings Tasks What was agreed leaves the meeting as tasks.
Notes Projects A note keeps the project it came out of.
Handbook Tasks A way of working is attached to the tasks that follow it.

A count is not a target, and a workspace for one person needs fewer than the table above shows. The number that matters is how many databases a record has to be findable from, because that is what the relations are for and what takes the time to get right.

Part two

Views: one set of records, read from wherever the question comes in

A view is a question asked of a database: what is mine, what is stuck, what falls in this week. The records underneath do not move, so nothing has to be kept in step by hand.

List

Grouped by project · 8 records

Harbour Lane rebrand

  • Write up the opening call Ada · Done
  • Collect the old logo files Rowan · Done
  • First set of marks Ada · In hand
  • Sign-off on the shortlist Ada · Waiting

Tide & Timber packaging

  • Box dimensions from the maker Nils · Waiting
  • Lay out the sleeve Nils · In hand
  • Proof the print file Rowan · Not started

Studio newsletter

  • Draft the spring letter Ada · Not started

Board

Grouped by status · the same records

Not started

  • Proof the print file

    Tide & Timber packaging

  • Draft the spring letter

    Studio newsletter

In hand

  • First set of marks

    Harbour Lane rebrand

  • Lay out the sleeve

    Tide & Timber packaging

Waiting

  • Sign-off on the shortlist

    Harbour Lane rebrand

  • Box dimensions from the maker

    Tide & Timber packaging

Done

  • Write up the opening call

    Harbour Lane rebrand

  • Collect the old logo files

    Harbour Lane rebrand

Schedule

Grouped by week · the same records

Week 1

  • Write up the opening call Harbour Lane rebrand
  • Collect the old logo files Harbour Lane rebrand
  • Box dimensions from the maker Tide & Timber packaging

Week 2

  • First set of marks Harbour Lane rebrand
  • Lay out the sleeve Tide & Timber packaging

Week 3

  • Sign-off on the shortlist Harbour Lane rebrand
  • Proof the print file Tide & Timber packaging
  • Draft the spring letter Studio newsletter

Part three

Templates, so the tenth start looks like the first

A workspace falls over slowly: the structure is right on the day it is handed over and drifts a little every time somebody starts something in a hurry. A template is the cheapest defence against that there is. It arrives with the properties already set, the sections already there, and the linked views already pointed at the right thing.

One template comes with every package; a template for each routine start is part of the larger two. Which ones you need is worked out from the brief, because it depends entirely on what you begin often.

New project

Template

Arrives with

Stage
Opening
Owner
Whoever opened it
Opened
Today's date
Client
Left empty on purpose

Opens with

  • A brief, with the four questions this workspace always asks at the top.
  • A decisions list, empty, ready for the first meeting to fill it.
  • A linked task list already filtered to this project.
  • A handover section that is written as the work goes, not at the end.

Before you ask

The subscription is yours, in your name

Any Notion subscription your plan needs is bought by you, directly from Notion, and is not part of what Worknestle Limited charges for.

If what you have described fits inside a free plan, we will say so rather than letting you find out later. Where a paid plan is genuinely needed, the reason is named in the brief, against the feature it is needed for.