Work can feel overwhelming. What to do next is not often clear. One way of handling this overwhelm is to “break it down” into smaller parts.
But how far is useful? If we continue to write many tasks that feel unnecessary, we only create busy work or procrastinate.
There are two measures to consider when breaking down tasks:
1 – For simple work, break to the Point of Confidence
2 – For mastery, break to the Fundamentals
When doing simple work, I find it is useful to break something down to the point of confidence. For example, I may break down “Clean home” into “Clean kitchen” and “Tidy living room”. While the latter two don’t fully convey cleaning the entire home, the original task was far too broad. The latter make more sense to me. I know what to do to clean the kitchen or tidy the living room. Someone else without the practice may wish to break things down farther, e.g. “Clean dishes”, “Wipe counters”, etc.
But, when I’m doing a work I intend to master, that’s a different story. Doing only things that I am confident in is a great way to stall. There are quite a few musicians who noodle away at their instrument without making much headway in their skills simply by doing what they already know. While there is much to be praised about review, there are also paths of unknown that need traversing.
In the case of mastery, it is useful to break things down to the point of fundamentals. In other words, we need to break the work into its most basic components, the most simple, even atomic, parts that cannot be broken down any further. Each of those parts, separately and together, can be played with and worked over until they are individually effortless.
As there are two points of measure, it is therefore very important that before beginning work, we consider if we are aiming for mastery. Mastery is a path that takes dedicated and regular time and effort. We are all limited in our time and attention.
Work can feel overwhelming. What to do next is not often clear. One way of handling this overwhelm is to “break it down” into smaller parts. But how far is useful? If we continue to write many tasks that feel unnecessary, we only create busy work or procrastinate....read more
Francis Wade at Schedule U has put together a round up of posts about scheduling tasks on a calendar. I'm not one to schedule everything on my calendar, but I fully admit that there is utility to the practice. Wade invited me to contribute my thoughts. Check out my...read more
What does "Going with the Flow" mean? Does it mean we simply react to our surroundings? Does it mean doing what we want at whim? Does it mean avoiding confrontation? A Dilemma Intuitively, we know that being interested in work can make a big difference. We are...read more
What is time blocking? Time blocking is the act of scheduling sessions of work on a calendar. By deliberately assigning work time on a calendar, we automatically acknowledge the immutable resource of time. Several productivity writers tout the strengths of time...read more
One of the big complaints made in the transition from OmniFocus 1 to 2 was the loss of the Inbox from the Project view. The workarounds were to either: assign a task to a project using the given fields or the Inspector create a new window using Option-Command-N to...read more
Welcome to the Chaotic Workflow series. Check out Part 1, Part 2, and Part 3 here. In the last several posts, we’ve been addressing chaos using at least three major categories: • Saying “No” • Satellite Task Systems • Creating Space for Practice Today we'll look at...read more
In the last post, Workflows in Chaos, we looked at the importance of making settled decisions and a difference between task management and workflow mastery. Moving on to addressing chaos, let's consider at least three major categories: Saying "No" Satellite Task...read more