Productivity Basics — Tasks Part 1

Completion Condition

There must be a defined outcome to a task. This is the most important part and what actually makes it a task. If you can’t determine whether a task has been completed then it’s not a task (or at least not your task).

The metrics to completing a task can be anything you decide as long as it is decided. It can be actually finishing something, obtaining some goal or simply a single step progress. It can also be time-based as an outcome, to simply spend a predetermined finite time on something.

I’ve covered actions and their own aspects in nature which then would be inherited by the task that comprises them. I use the plural because often a task will require multiple actions.

The larger and more complex the task you define to lead to some desired outcome then the more likely you will need more actions to accomplish it. If it becomes too complex and requires multiple steps you may want to consider then breaking it up into separate tasks, these then will become dependencies of each other but easier to manage if you need to split things over time.

E.g. work out at the gym, may include getting your gym clothes ready, setting an alarm to get up early and since those things, although make the task of “work out at the gym” easier to achieve they are likely to split over time to the previous day so they should be separate tasks with their own actions that the “work out at gym” task is dependent on. You would also want a clearer definition of what working out means, is it completing a set exercise routine or is it making sure you do something for at least 30 minutes?

This post was created with Typeshare

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store