Gmail now has an “undo send” feature.
Why Knowledge Work Can be So Hard
In the last post (actually, two posts ago now), we saw that it can be very helpful and clarifying to define the deliverables on your projects.
This leads to the reason knowledge work can be so hard. Not hard in the sense of heavy lifting, but in the sense of — for lack of a better word — “mystifying.”
The challenge of knowledge work is that, usually, we have to define our own projects and deliverables. I often find myself looking back fondly to when I was in school, and all of the “deliverables” were handed to me on a silver platter (= syllabus).
You didn’t even really need to keep a project list — all of your “projects” were defined for you, with detail, right there in the syllabus. (Although if I had it to do over, I would keep a project list now.)
I didn’t know about David Allen back then. Yet, “knowing what you were not doing” was simple. I kept on top of things by simply saying to myself every once in a while “Hmm, I wonder what I’m supposed to be doing? Better look at the syllabi from my classes.” (That’s very GTD-ish, by the way.) This worked very well, and I actually think that there are some lessons to be learned from this (more on that down the road, hopefully).
The challenge in the world of work (and business of life, even if you are in school) is that you don’t have people defining all your projects for you. You do have people assigning you things, such as your boss. But you also have people “requesting” things. And then, for the most part, you are responsible to know what you need to do in order to accomplish the purpose of your position (or life at home — parenting, keeping up the house, etc.).
There is variation here, of course. For example, some positions might indeed largely consist of work that is defined very clearly and assigned by a boss or customer workflow or etc.
But regardless, my point is that we all have an ever-changing “syllabus,” most of which we have to create. And we have to create it in real-time.
The result is that, in addition to being skilled in actually doing our work, we also have to be skilled in defining our work. And there are some interesting trade-offs there: define your work poorly or inadequately, and the doing of your work will suffer. Additionally, time spent defining your work takes away time from doing it. On the other hand, define your work well, and that will pay off rich dividends in the doing of your work, in terms of both time savings and quality improvements.
Figuring this all out is, possibly, one of the greatest opportunities for increasing knowledge worker productivity on a large scale — and bringing more sanity to life at the individual level as well.
The Science of the Spring Equinox
My kids are very excited about the first day of spring (today). They are celebrating with ice cream and just plain enthusiasm.
Fox News has an interesting article today on the science of the equinoxes and solstices. Here’s one interesting piece:
At the North Pole, the sun rises only once a year — at the start of spring. It gets higher in the sky each day until the summer solstice, then sinks but does not truly set until late September, at the autumn equinox.
Define the Deliverables on Your Projects
Here is a practice that is very simple, but very powerful.
Whenever you have a new project (either created/identified by you or assigned to you), one of the first things you should do is define the deliverables for the project.
The deliverables on a project are the specific work products that you have to produce in order to complete the project.
For example, if the project is to create a new policy on this or that, the deliverables might be (1) collected research of the various policy options and then (2) a completed policy document. If the project is to set up a new room in your house, the deliverables might be (1) furniture (2) stuff for the walls and (3) a room that is arranged and put together.
Defining the deliverables is really just a component of asking “what’s the intended outcome?” It helps to clarify what the project means and, therefore, how to complete it.
Now, here’s the most important thing about this: Defining the deliverables directs your attention to outcomes rather than activities.
Activities are not necessarily productive. Many of the activities we do are not necessary. When you think about your projects, if you think first in terms of “doing activities” to get them done, your mind will probably create a lot of unnecessary work. This is only natural — if you think that doing a project means doing activities, that’s where your focus will go and your mind will have no shortage of ideas.
On the other hand, if you think first of deliverables, your mind is directed right away to outcomes instead. This will immediately filter out a whole bunch of activities and cause you to identify and focus in on only the activities that are actually essential to the project.
This will save you time and provide you with better results.
Six Thinking Hats
Mindtools has a good overview of a decision-making tool called the Six Thinking Hats. This tool helps improve your decision making by enabling you to look at a decision from all angles.
“Six Thinking Hats” is a powerful technique that helps you look at important decisions from a number of different perspectives. It helps you make better decisions by pushing you to move outside your habitual ways of thinking. As such, it helps you understand the full complexity of a decision, and spot issues and opportunities which you might otherwise not notice.
The hats are:
- White hat: focus on the data available.
- Red hat: look at the decision using intuition and emotion.
- Black hat: look at things pessimistically [my least favorite! — but it will help make your plans tougher].
- Yellow hat: look at things optimistically.
- Green hat: look at things creatively.
- Blue hat: this stands for control, which means directing attention to the most needed hat when circumstances require. For example, if ideas run dry, directing focus to the green hat, or directing focus to the black hat when it’s time to create contingency plans.
For more details and examples, read the whole thing.
David Allen on the Productive Use of Social Media
David Allen has a good article in Businessweek on Time Management in the Age of Social Media.
Here is an especially interesting observation:
The challenge is that each of those social media involvements can represent another virtual in box, with an implicit assumption that you should think about and deal with what lands there. If “processing” those additional streams of input is simply a matter of scanning to see what’s of interest to you, that may not take much time; and you can simply drop in and out on a whim. That’s no different than channel surfing, other than the added seductiveness of interactive rabbit trails to pursue.
But if you are expected—by yourself or others—to be more familiar with the content, or to contribute and respond to content directly, you’re going to have to be judicious in how you manage your social media commitments. It’s not as innocuous as another cable station, unless you have specifically downgraded your expectations of how you’re going to be involved.
Time Management is not First About Getting More Done in a Day
From To Do Doing Done:
Successful time management is not about getting more done in a day; it’s about getting the things done that matter most. Just trying to get more done every day is life in a squirrel cage running faster and faster to nowhere. Getting done what matters most leads to a life of balance, personal satisfaction, and inner peace. Choosing the tasks to be done is more important than any system of completing random tasks. The tasks we manage on a daily basis need to flow up from the pyramid base of our values. If tasks aren’t related to our values, why would we devote our time to them? (p. 67)
I would tweak two things. First, I would not want to say that getting done what matters leads to inner peace. I don’t think it is possible to find inner peace through any form of productivity, even the right kind where we are genuinely getting the right things done. If our inner peace depends upon any productivity approach, or even just getting done what matters, we are still going to fail often and thus are just setting ourselves up for frustration. But if by “inner peace” she just means a life that is not chaotic, which is functioning well, and is aerodynamic and effective (and thus more pleasant), then I would definitely agree with that.
Second, I would add that it is not enough for our tasks to align with our values. For it is possible for our values to be wrong. Our values must align with correct principles in order to be truly useful.
There is a broad scope of values that align with correct principles, so there is much room for personal uniqueness. But values aren’t the end of the story when it comes to defining the right things to be doing. Values must be based on something deeper — namely, correct principles.
Being Organized is (in part) about Being Ready
From Time Management from the Inside Out:
Being organized, whether with your space or time, is all about being ready. It’s about feeling in command so that you are prepared to handle all of the opportunities, distractions, and surprises life throws your way. We live in a complex, fast-paced world filled with infinite possibilities and opportunities. When you develop good time-management skills, instead of being overwhelmed by it all, you celebrate it. You know what to choose. You feel clear and focused, ready to take on life.
This observation on how organization is about being ready echoes the title of David Allen’s second book, Ready for Anything. When you are productive, you are ready for what comes your way.
I would add (and so would the author, Julie Morgenstern, but she just didn’t emphasize it as much here) that being organized is also about being able to execute on your priorities.
So their are two aims and benefits of organization: being ready to deal effectively with what comes your way, and being able to chart the course you want to take. There are both reactive and proactive components to productivity.
Ultimately, these two come together, for even in responding to the unexpected things that come our way, we want to do so in alignment with our priorities. Being organized means you know what those priorities are and that you are able to able to act on them, both in responding to the opportunities and surprises that come your way and in charting the course you want to take.
Catalytic Mechanisms for Improving Organizational Performance
Here are some key points from an article summarizing Jim Collins research on catalytic mechanisms for improving organizational performance.
Catalytic mechanisms are galvanizing, non-bureaucratic links that turn objectives, such as Collins’ concept of the BHAG, into performance.
There are several characteristics of catalytic mechanisms.
First, they often produce results in unpredictable ways. “Unlike traditional systems, procedures and practices – which may lead to bureaucracy and mediocrity – catalytic mechanisms let organizations achieve greatness by allowing people to do unexpected things, to show initiative and creativity, to step outside the scripted path.”
Second, they have teeth. “In contrast to lofty aspirations a catalytic mechanism puts a process in place that all but guarantees that the vision will be fulfilled.”
Third, rather than being designed to get employees to act in the right way, “catalytic mechanisms help organizations to get the right people in the first place, keep them, and eject those who do not share the company’s core values.”
Fourth, they have an ongoing effect. “Unlike electrifying off-site meetings, exciting strategic initiatives, or impending crises, a good catalytic mechanism can last for decades.
Notes on Weekly Management One on Ones
One-on-one’s are weekly 30-minute meetings between a manager and each person that reports to him or her.
The guys at Manager Tools say that they are the most effective management tool that they know of. They have a series of three podcats on one-on-one’s along with a worksheet that provides some additional details.
I found the podcasts so helpful that I took some notes over them. Here are my notes.
Purpose
The purpose of 1:1’s is communication. A culture of communication, in turn, is a key ingredient of organization-wide alignment and coordination across departments. Communication is the most important lever an organization has for performance.
Basics
- Regularly scheduled.
- Rarely missed. This means “always reschedule,” instead of canceling. [I would say that sometimes, it just won’t be possible to reschedule and a week will have to be missed.]
- Primary focus is on the team member.
- Take notes. Keep in a notebook or electronically, and in each meeting refer back to follow-up items.
Agenda
Here is the standing agenda that seems to work best:
- 10 minutes: Them. Agenda items they bring and whatever they want to talk about.
- 10 minutes: You. Agenda items you’ve brought; updates that will be useful to them to know. Touch base on status of projects and quarterly goals if desired.
- 10 minutes: The future/development. (If there is time left for this.)
Preparation
To prepare, they suggest that it can be helpful to review 5 questions. [What I basically do is review notes from the last meeting and pull together agenda items I’ve collected along other items that come to mind (updates that will be useful, etc.).]
Anyway, here are the five questions they suggest:
- What things in my notes from last meeting do I need to follow up on? Then write them on your agenda.
- What do I need to be sure to communicate to this person?
- What positive feedback can I give this person?
- What adjusting feedback am I going to give this peson?
- Is there something I can delegate? (“There is a gross under-delegation epidemic in America.”)