The value of keeping a “to stop” list

If you are like me, I use a “to do” list all the time. Time management for a project manager is crucial to their success. Only it feels like it is not working for me these days! I have read some great posts on how to improve what you do, like Harry Jones’ post at his blog or Matthew Cornell’s post on “do, Don’t do, Stop Doing”. But recently a long time mentor of mine gave me some excellent advice on how to help make your hectic schedule a bit less hectic and better controlled. I would like to share it with you.

  The More Effective “To Do” List: The “To Stop” List

 

Article by Herb Rubenstein, President, Sustainable Business Group

Introduction

The “to do” list is a staple of executives, house wives, college students, and even elementary school students whose parents have drilled into their heads staying “on task.” Thanks to a webinar by Marshall Goldsmith, this article provides key insights into a potentially very effective complement to the “to do” list.  This is the “to stop” list.

The basic premise of the “to stop” list is that people today are very busy.  They multi-task, have challenges delegating tasks because they don’t have time to get organized enough to hand off some of their “to do” lists in an effective manner to others.  People want to do different things, but don’t have time to do them.  The goal of the “to stop” list is simple.  It is to help people in an organized manner begin to eliminate activities that are taking their time, but are no longer producing sufficient value or enjoyment to merit filling up our days and nights. The theory is simple.  An excellent way to make room in our busy schedules, or “make time” as some people like to say, for new or different activities, or activities we never seem to get to, is to eliminate some of the activities that have been regularly taking our time up to this point.

The Approach

Creating a “to stop” list is actually pretty easy.  It can start as simply as foods you no longer find useful to eat. In some ways it works just like a “to do” list, except in “reverse.”  Most people do not always complete everything on their “to do” list.  Similarly, you, in all likelihood, will not stop everything completely on your “to stop” list.  Some people respond better when someone, or especially, when they themselves, tell themselves to stop something rather than being told, or telling themselves, to do something.

The “to stop” list can be created and executed at the individual level, the family level, or at the organizational level.  The “to stop” list can successfully change a culture in an organization where discipline is lacking and “anything goes.”  It can create an opportunity for self-examination at whatever level it is implemented, and is needed more and more in our ultra busy and hurried times.

Specific Examples of Typical “To Stop” Items

In addition to putting things you do that are time wasters or not the most effective use of your time, you can actually put certain people on your “to stop” list if spending time with them is not useful or enjoyable.  Do you watch more TV than you think you should, or participate in too many staff meetings that do not contribute to the effectiveness of the organization in which you work?  Of course, if someone is on your “to stop” list, I urge you to be polite to them, but you need not continue to spend inordinate amounts of time with them that is not useful to you, or in your opinion, not beneficial to them.

Items on the “to stop” list may be very specific or include general categories of behavior.  For example, you might put a particular not useful activity like trolling on the internet to find bargains in home furnishings that you don’t really need or just list an item that is broadly applicable like “stop noise in my life.”  Another purpose of the “to stop” list is to have us look at our behavior that has become routine, including our habits, and re-evaluate their usefulness compared to the time they cost us.

In business or organizational life, one small business owner in her first day of writing her “to stop” list decided to stop doing all of the “minimum wage” activities that she was doing.  During the day she wrote down all of these “minimum wage” activities which a clerical assistant or high school or college intern could have performed just as effectively, and through writing down all of these activities, she had created a “job description.”  She posted the job description on several websites and in one week had hired an administrative assistant that freed up ten to fifteen hours of her time a week to do more productive and valuable things to promote her business that only she could perform.  Now she has more time to work “on the business,” rather than spending so much of her time “in the business.”

Conclusion

You can add or subtract items to the “to stop” on a regular or periodic basis.  It is a good practice to review the list at least weekly to see how you are doing in stopping or reducing the amount of time you spend on activities that are not producing value or enjoyment for you or your organization.  At the organizational level, having a discussion or posting items on a blog, list serve, chat room, or sharing ideas on that to stop is a useful exercise that will point out significant time wasters.  There will always be things you have to do because the activity is very important to other people or has some potential for benefit in either the short term or the long term. These items should not be on your “to stop” list.

The “to stop” list at the individual level may lead to your finding ways to delegate or automate tasks, or become much more efficient in completing them.  Overall, a good “to stop” list has the dual benefits of making you and your organizations both more efficient and more effective.  If we could say that about everything in our life, we would be more productive, more satisfied, and less harried.

Finally, to combine your to do list with a to stop list is an excellent combination. In a separate article I write about a third list that completes the package.  It is the “to decide” list.  Combining your “to decide” list, with your to stop list, and your to do list is a three pronged approach that will make you a more effective executive, student, and a person who become not only more decisive, but better at executing your decisions in a timely manner.

About the Author

Herb Rubenstein is the President of Sustainable Business Group a consulting firm to businesses.  The headquarters of the Sustainable Business Group is Denver, Colorado.  He is co-author of Breakthrough, Inc. – High Growth Strategies for Entrepreneurial Organizations (Prentice Hall/Financial Times, 1999. He has his law degree from Georgetown University, his Master of Public Affairs from the LBJ School of Public Affairs, a graduate degree in sociology from the University of Bristol in Bristol, England and was a Phi Beta Kappa/Omicron Delta Kappa graduate from Washington and Lee University in 1974.  His email address is herb@sbizgroup.com and he can be reached at 303 910-7961.

Learning from mistakes

There are several super Project Managers writing blogs that share their observations, experiences, and lessons learned. One I have found interesting and insightful is from Scott Berkun—particularly his essays that tend to include more detail and instructions than his blog posts. Scott is the author of two books on Project Management: Making things happen (an Amazon editor’s best pick for 2007) and The Myths of Innovation.

Scott was a manager at Microsoft from 1994-2003. He currently works as a writer and public speaker. He has taught at the University of Washington, blogs for Harvard Business, and has appeared as an innovation expert on CNBC and MSNBC.

In his essay on Learning from Mistakes, Scott tells us:

  • You can only learn from a mistake after you admit you’ve made it
  • To learn from mistakes, you must:
    • Put yourself in situation where you can make interesting mistakes
    • Have the self confidence to admit them
    • Be courageous about making changes
  • Scott then talk in detail about four kinds of mistakes:
    • Stupid
    • Simple—avoidable but your sequence of decisions made it inevitable
    • Involved—understandable but require significant effort to prevent
    • Complex—multiple causes, difficult to avoid

I recommend that you read Scott’s entire nine page essay. There is real value here for project managers, especially Scott’s questions to ask when trying to understand what happened on your project and his checklist for learning from mistakes.

Please share your thoughts and comments.

How to create and use predictive project scheduling

I was a bit naïve when I accepted the challenge to manage my first software project. I didn’t quite understand the “wink-wink, nod-nod” I got from the software veterans when I began asking for their input to the project task detail and schedule. Now many years and many projects later, I understand their skepticism. They had too often been victims of schedules that were not worth the paper or time used to develop them. They had seen schedule chicken played by professionals and had worked countless hours of overtime trying to meet unrealistic, unattainable deadlines.

However, I continue to believe whole-heartedly in the value of predictive schedules. To me, a predictive schedule is one that accurately reflects what has happened in the past and is a good predictor of the future.  It gives a believable prediction of the project end date and an accurate level of effort estimate to completion.

What are the necessary pre-conditions for a useful predictive schedule?

Let me tackle the most challenging requirement first—corporate or organizational culture. If your company has a “shoot the messenger” ethic, then predictive scheduling is doomed! Like a military plan, the initial project schedule rarely survives contact with the enemy. Staff changes, requirements creep, and vendors miss shipment deadlines.  Your project schedule must be detailed enough to identify potential problems and dynamic enough that you can reforecast to accommodate the real world. AND, senior managers need to be willing to hear the impact of changes on the project schedule.

For predictive scheduling to be useful, there must be trust on all sides of the equation:

  • As project manager, you do the best you can to create an accurate and meaningful schedule of tasks with an estimated level of effort (LOE).
  • Developers and team members work hard to meet schedule requirements and accurately record their time to each task as well as update estimate to complete (ETC).
  • Management trusts that everyone involved is doing their best and reporting accurately.  They provide support when needed.

What content is required for a useful predictive schedule?

Developing a predictive schedule is a top down and a bottom up process. You must start with the top level vision and goals for the project to set expectations and scope.  Then each deliverable is broken down into tasks that require no more than one or two week’s time to complete (that task may include the effort of several people or it may require less than the full-time effort of one developer). The point is that you need to be able to assess the project’s status weekly.

Now we come to the one of the most powerful features of predictive scheduling—task dependencies. Your schedule must show these dependencies. What must be completed before “Task X” can begin (predecessors) and what tasks depend on the successful completion of Task X (successors). Getting the task dependencies correct is 50% of the requirement for creating a useful predictive schedule.

The other 50% is estimating the effort really required to complete the task successfully. As project manager, you will want the input of others on the project to define tasks, dependencies, and effort. Then, you have to make a judgment on their input. First, you need to make sure that there is enough detail so that the schedule can document the project status and second, you will likely need to adjust the estimated level of effort (LOE).

Why do I believe that the initial effort submitted by developers will need to be adjusted? Developers and other team members often make errors of omission and commission in defining LOE for a task. (Dan Mitchell offers some insight into what may be left out of developer’s estimates on his Software Developer’s Guidebook blog). Some may be too optimistic—assuming all of their time will be dedicated to writing code when in reality the schedule needs to include time spent in meetings, unit testing, and working with temperamental hardware and software. Or, they may assume that the level of productivity is the same for all developers or IT staff, when the truth is that some developers are significantly more productive than others (usually based on experience or skill).

Finally, either through misplaced self preservation instinct or lack of knowledge, developers may over-estimate LOE believing that if the estimate is cut during its migration through senior management reviews, they will still be able to get the work done because they padded their initial estimate.  So you, the PM, must assess the estimates and try to get them to be as accurate as possible!  No one said this was easy.

What benefits does a project manager receive from a real predictive schedule?

  • Ammunition to define and defend resources needed to be successful
  • Knowledge of project status with sufficient time to avert disasters
  • The ability to answer status and planning questions from senior management
  • A final project that predicts cost and schedule throughout the project’s life

One last thought: predictive scheduling tells a PM what he or she needs to know, not what they may want to hear.

Please comment and share your thoughts on predictive schedules.

 

(If you want more on why you need predictive schedule check out the earlier post at http://fearnoproject.com/2009/02/13/why-your-project-needs-predictive-schedules/)

Follow

Get every new post delivered to your Inbox.

Join 383 other followers