Skip to main content
Worknestle

Notion workspace setup · Independent

Your work, held in one place that was built around it

Worknestle designs and sets up Notion workspaces for one person or one small team: notes, tasks, projects and a knowledge base joined to each other, with the templates and the written notes that keep the thing running after we have gone.

Projects

Database

One piece of work with a beginning and an end.

  • Stage
  • Owner
  • Client

Tasks

Database

One thing somebody has to do next.

  • Status
  • Project
  • Owner

Meetings

Database

One conversation and what was decided in it.

  • Date
  • Present
  • Project

Handbook

Database

How a thing gets done here, written once.

  • Topic
  • Keeper
  • Last read through
  • A project holds the tasks that move it on.

  • A meeting is filed against the project it was about.

  • A way of working is attached to the tasks that follow it.

Where we stand

Worknestle Limited is an independent company. It is not affiliated with, endorsed by, certified by or a partner of Notion Labs, Inc. Notion is a trademark of Notion Labs, Inc. and is named here only to say which tool the work is carried out in.

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

What gets built

Three shapes of job, and they are genuinely different

A workspace for one person is not a smaller version of a workspace for a team, and a knowledge base is not a task list with longer pages. Each of these needs a different structure underneath it.

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.

  • 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.
  • Inbox
  • Tasks
  • Projects
  • Notes

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.

  • 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.
  • Projects
  • Tasks
  • Meetings
  • Clients

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.

  • 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.
  • Handbook
  • Notes
  • Tasks
  • Projects

What each of the three is made of, in full

Views

One set of records, three ways to read it

What turns a workspace into a mess is the same work being written down in three places. It should be written once and read from whichever angle the question comes in at. Below is one set of task records shown as a list, a board and a schedule.

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

Nothing above is copied between the three panels. They are the same records grouped on a different property, which is what makes a workspace worth keeping: change a status in one place and every view that cares about it has already changed.

Packages

Three sizes, measured on what makes a setup bigger

How many working processes the workspace has to carry, how many databases those need, and how much of the joining-up has to be worked out rather than copied. Those three things decide which package a job sits in.

One person

Single space

One working process, set up properly. Notes, tasks and projects joined to each other and one home page that answers what is in hand today.

Processes
One
Databases
A small connected set
Views
One way in, two ways to read it
Templates
One
Handover
Written notes and one walkthrough

A small team working on the same projects

Team space

Several processes that hand work to each other: projects and tasks, meetings that leave decisions behind them, and views that let people see each other’s work without asking.

Processes
Two or three, joined
Databases
A wider set, with relations between them
Views
Per person, per project and per week
Templates
One for each thing the team starts often
Handover
Written notes and a session with the team

A team whose workspace has become the place work actually happens

Connected operations

Several processes across a team with a knowledge base behind them, kept honest by review properties, templates and a navigation layer built for people who were not there when it was made.

Processes
Several, across the team
Databases
A full set, joined in both directions
Views
Entry points by role as well as by record
Templates
A template for every routine start
Handover
Written notes, a session per role and a review afterwards
What is in each package

There is no figure on this site. Price, timescale and the number of revisions included belong in a written quotation for the job in front of us, in pounds sterling, with everything included in the amount quoted.

How it goes

Brief, quotation, prototype, review, handover, walkthrough

Nothing starts before a quotation has been accepted and the order confirmed back to you in writing, and your own material does not go anywhere near the workspace until the structure has been stood up on sample records and you have said it is right.

  1. 01

    Brief

    A conversation and a written summary

    We go through how the work moves now: what gets written down, what gets lost, who has to ask somebody else before they can carry on. What comes back is a written brief listing the processes to be carried, the databases they need and which route the build takes.

  2. 02

    Quotation

    Scope, figure and timescale, in writing

    The brief becomes a quotation naming the package, the full price in pounds sterling with everything included, the timescale and how many revisions are covered. Nothing starts until you accept it and we confirm the order back to you in writing.

  3. 03

    Prototype

    The structure, standing up, on sample records

    The databases, their properties and the joins between them are built and filled with sample records, so you can see the thing working before your own material is anywhere near it. This is where a structure that looked right on paper gets corrected.

  4. 04

    Review

    You use it and say what is wrong

    You walk through the prototype against the jobs you actually do. Changes that come out of that are part of the revisions the quotation covers; a change that turns out to be a different structure is quoted before it is built.

  5. 05

    Handover

    The workspace, or the template, and the notes

    On the template route you get a duplicable template and the written notes. On the in-place route the structure is finished in your workspace and our access ends. Either way the notes say how it is put together and how to add to it without breaking the joins.

  6. 06

    Walkthrough

    A live session, and the questions that follow it

    We go through the workspace with you, on a call, and you drive. Afterwards you have a period for questions arising from using it, set out in the quotation.

Template handover

We never touch your data

The workspace is built in ours, on sample records, and handed to you as a template you duplicate into your own account. Nothing of yours is opened, shared or moved, and no access is asked for at any point. You fill it yourself, with the written notes beside you.

Suits

Anyone whose material is confidential, and anyone who would rather not hand over access to an outside company.

Built in your workspace

Access, agreed in writing, for as long as the work takes

You invite us into a workspace you control, at the level of access we agree in writing beforehand. We build in it, alongside what is already there, and the access is handed back and removed when the work is signed off. What we were given, and when it ended, is written in the order confirmation.

Suits

Teams already working in Notion who want the new structure around records they are using now.

The whole process, stage by stage

Boundaries

What we do not do, said plainly

Every line below is a thing somebody selling this could say and we will not.

We do not claim a partnership we have not got

No badge, no certification, no reseller arrangement, no logo borrowed from somebody else’s brand. We work in Notion, which is a different sentence entirely, and this site says only that.

We do not sell you the subscription

Whatever plan your workspace needs, you buy from Notion, in your own name, on your own card. It is not marked up, passed through or bundled into a quotation, and if a free plan carries what you need we will say so.

We do not resell a template as a design

A setup is drawn from how you already work. Where a structure that already exists fits what you do, you are told that is what it is rather than charged for a discovery that did not happen.

We do not promise what a workspace cannot do

No claim about hours saved, output raised or a team transformed. A workspace makes the state of the work visible and stops things being written down twice. What that is worth depends on you, and nobody selling one can honestly put a number on it.

Next

Tell us what the workspace has to carry

A name, an address to reply to and a couple of sentences about the work is enough to start. What comes back is a written brief and a quotation for the job as described, and nothing is agreed or owed until you accept it.

Or write to us

support@worknestle.org

An email saying the same things works exactly as well as the form. There is nothing to fill in before a person reads it.

Worknestle Limited 82a James Carter RoadMildenhallBury St. EdmundsEngland, IP28 7DE