Notion is a writing tool that makes reading, writing and organisation easy. At Nomio, Notion is integral to our internal processes: whether it's tracking our sales pipeline, reviewing a technical design or booking a holiday, it's all done in Notion. (And yes, this article has been drafted in Notion!)
Our Product & Engineering team have used Notion to organise their work since 2019. One benefit of using Notion over purpose-built task management tools like JIRA is that you have to build everything from scratch: this encourages us to keep our process lean, and to question every part of the process. We regularly review our process and throw away anything that doesn't help us keep our work organised.
In this article, I'd like to illustrate how we currently manage our Product & Engineering work, and explain some of the decisions we made along the way. Hopefully this can be an inspiration for your own work management process!
At Nomio, we've got two sizes of work: tasks and projects.
Tasks are the basic unit of work in the Product & Engineering team. We keep them as small as we can, so we can regularly feel progress — this could be anywhere between a few minutes' and a few days' work.
Take a look at our actual product task list above: tasks travel from left to right, gaining detail as it goes along.
Tasks start in the Backlog. Anyone in the company can create a task, and we provide templates to ensure we get as much detail into the task as we can.
Once a week, the Product & Engineering team review every task in the Backlog — this stops tickets from going stale and never getting worked on.
Tasks with enough detail are accepted; otherwise, we determine what we need before we can accept the work and assign the ticket to someone.
When a task is accepted, it is also given a priority: this is a combination of two factors:
In general, low-effort/high-value tasks are done before high-effort/low-value tasks.
Tasks are listed in priority order: when an engineer is ready to work on something new, they'll take the top task from the list and work on that. This straightforward framework means we work on the most impactful things first.
Above is an example of a task. Tasks are given enough detail for any engineer to work on. Tasks are given a priority when accepted, which is based on the value to the stakeholder and the roughly-estimated effort required by the Engineering team.
Once done, tasks are usually tied one-to-one with a pull request, which allows us to keep track of what we're going to deploy.
Sometimes work is bigger than a single task — for that, we have projects, which are simply groups of tasks.
Above you can see our actual project list. As with tasks, projects can be written by anyone. Often a task gets turned into a project as it gets scoped out and we realise that there's more work to do than first thought.
We've got three basic "time buckets", which communicate with the rest of the company when we expect things to be worked on:
Within these buckets, projects are manually ordered by priority and reviewed each week by the team to ensure we're ready to work on the next project.
Above is an example of a project. Projects contain enough detail to explain the problem and to outline a potential solution.