A task-management system becomes useful when it is the place you trust to show the work that still needs to happen. If actions are divided between Workspace, email flags, notebooks, messages and individual team members’ private lists, no single view can tell you what is outstanding.
At Queensberry, our own task system became far more useful when it became our point of truth: actionable work goes into the system, the team works from it and completed Tasks are closed there.
What a point of truth means
Your task system should answer three questions:
- What needs to happen?
- When does it need attention?
- What context is needed to complete it?
This does not mean turning every email, conversation or piece of reference information into a Task. It means recording every action that must be remembered, completed later or made visible to the team.
Why split systems break down
A Task list cannot be trusted when some work is recorded there and other work remains in someone’s Inbox, notebook, memory or separate application. Team members then need to check several places, and an apparently clear Task list may still be missing important commitments.
This can create two problems:
- people stop trusting the system because it does not contain the complete picture; and
- once they stop trusting it, they use it less, making the information even less complete.
Decide what should become a Task
Create a Task when an action:
- is something you need to come back to later;
- cannot be completed immediately;
- needs a due date or reminder;
- needs to be visible to other people in the studio;
- depends on information or work from someone else;
- is part of a repeatable project process; or
- could be forgotten if it remains only in a message or conversation.
A Task can still be useful when none of the other conditions apply. Sometimes its purpose is simply to hold your place so the action is not lost when you move on to something else.
For example, you may answer a straightforward enquiry directly through the Inbox. If the reply requires tailored pricing, a mood board, availability research or input from another person, create a Task for that preparation or follow-up.
Capture work where it begins
Actions can begin in many places: an email, Live Chat conversation, meeting, telephone call, Project or client request. When an action cannot be completed at once, record it as a Task while the context is still clear.
Give the Task a useful title, link it to the relevant Project, Contact or Client where possible, and include enough information for someone returning to it to act without reconstructing the original conversation.
Agree how your team will use Tasks
A shared task system only works when the people responsible for the work use it consistently. Agree on a few simple expectations:
- new actionable work is recorded as a Task;
- real deadlines have realistic due dates;
- changes or delays are reflected in the Task;
- important context is kept with the relevant record; and
- Tasks are marked complete when the work is actually finished.
Workspace does not currently assign a Task to a named team member. We are implementing task assignment for shared accounts and expect to launch it soon. Until then, if several people share responsibility for the work, agree who will handle it through your current team process and use the Task title or details where helpful to keep that responsibility clear.
If work is discussed verbally or in a message, make sure the action also reaches the shared system. Otherwise the team is depending on two different processes.
Build a review habit
The system becomes dependable through regular use, not simply through initial setup.
- Review today’s and overdue Tasks at the beginning of the working day.
- Update Tasks when priorities or dates change.
- Use filters, Calendar or board views to focus on the work relevant to you.
- Review future Tasks regularly so they do not disappear from attention.
- Close completed work so the active list remains credible.
Move from split systems deliberately
If your work is currently spread across several places, choose a practical transition point. Bring across the open actions that still matter, decide where new work will be recorded from that date and make the change clear to the team.
A short transition period may be necessary, but avoid maintaining two permanent task systems. The longer both remain active, the harder it becomes to know which one is accurate.
Keep the system easy to trust
- Write one clear action per Task.
- Start the title with a verb such as “Prepare”, “Send”, “Confirm” or “Review”.
- Use due dates for genuine timing, not simply to make every Task appear urgent.
- Remove duplicates and close work that is no longer required.
- Keep passwords, payment-card details and other sensitive secrets out of Task notes.
- Store long reference material in the appropriate Project or document and use the Task to describe the required action.
Add workflows after the habit is working
Project Workflows can create repeatable groups of Tasks, but automation will not solve inconsistent task habits by itself. Begin by making the shared Task list dependable. Once the team is using it consistently, turn recurring processes into Project Workflows.
See How to use tasks and follow-ups in Studio Management and How to create and apply a Project Workflow.
The useful test
Ask yourself: if you were away tomorrow, could another person in the studio open Workspace and understand what needs to happen next?
If the answer is yes, the task system is becoming a genuine point of truth. If not, look for the actions that still live somewhere else and decide how they should enter the shared workflow.
