Subtasks with a twist!
The format of an individual task is the backbone of Kanban-style task management and the entire Workstreams.ai experience. It’s the essential building block for all your taskboards, workflows, and Goals. It is also the first step in successfully executing your ideas and hitting key milestones on your projects. It’s everything!
What's in a task?
Knowing that we’ve done our utmost to refine the Workstreams.ai experience into something that gives our customers the right level of flexibility and granularity needed for all sorts of tasks. Your Workstreams.ai tasks can be precise, title-only snippets or they can be thoroughly filled with detailed descriptions, labels, attachments, and subtasks. That last part, the subtasks, is the area where we have long seen the huge potential for our customers. Here’s why.
When we launched the checklist inside the Workstreams.ai task, we envisioned that our customers will use it to break down the steps needed to successfully execute the tasks and to have an overview of where work is. And we were right! Folks were using the subtasks to jot down steps they needed to do, as well as list specific things that were needed to complete a task. But, after digging into our numbers and talking more with our customers, we felt that we could make our “checklist” even more useful, and let it “graduate” into not just mere checkable items, but full-on subtasks.
For that to happen, we needed to add functionality that would really transform a mere checklist item, into an actionable, executable subtask. We worked with a bunch of our customers and within our team, to define what the building for a true subtask would need to be. We landed on two essentials. The first is having the possibility to apply start and end dates to subtasks, and the second one, which delighted several of our clients enrolled in our BETA program, was the ability to assign teammates to a subtask.
How do we think about assigning work
Let’s go a bit deeper into our way of thinking here. At Workstreams.ai, the concept of a task assignee is one where at any given time, a single person is assigned to something. We don’t offer the functionality of multiple assignees, as we believe that in a specific step of the process, a particular person is doing the particular work needed. That doesn’t mean that he or she doesn’t need support in any specific way from others. The ability to assign your teammates to a subtask proved to be the most elegant way forward. The person assigned to the task still retains accountability and responsibility for overall success, but they are now more clearly supported by the teammates assigned to subtasks. It made sense to us, and we are happy to report it also has been met with praise from our customers.
The addition of the start and end dates seemed like a logical extension of the due dates. They are there to provide granular control when certain subtasks need to be finished. When you are dividing tasks into chunks, this is often a requirement. It also allows the assignees of the subtasks to be in the know about when you need certain things done. Nifty!
All in all, we are extremely excited about the innovative ways our user base has begun utilizing the subtasks and the bits and pieces we’ve built around the. If you have any ideas on how we can further improve this functionality or any other features across our product, do let us know. You can reach us the old fashioned way on email@example.com, or you can join our community on Slack!