Yesterday, Seth Godin made a post that seemed aimed at a few of the companies and organizations I have volunteered or worked for/with throughout my life. He addressed the importance of understanding the critical path to achieving a goal. He defined critical path as “The longest string of dependent, non-compressible tasks.”
He uses wanting to create a garden as an example.
“For example, in your mind’s eye, the garden has a nice sign in front. The nice sign takes about a week to get made by the sign guy, and it depends on nothing. You can order the sign any time until a week before you need it. On the other hand, you can’t plant until you grade and you can’t grade until you get the delivery of soil and you can’t get the delivery until you’ve got a permit from the local town.”
He notes the logical step is to take care of that permit first. “And yet most organizations focus on shiny objectives or contentious discussions or get sidetracked by emergencies instead of honoring the critical path.”
He discusses how important it is to identify the parts of a process that end up being the choke points of the critical path. He gives an example of how a company he worked for used color coded buttons to identify the people who were important points along that path for a project upon which the success of the company hinged. Everyone not identified as part of that potential choke point, including the president of the company, knew not to impede the progress of those who were.
This resonated with me because I recently discovered that the piece of software I use for tracking my task list has a pull down menu with “Waiting on Someone Else” as an option. When I started using that option to keep the list from periodically squawking that those tasks were overdue, I realized that nearly every task was waiting on action from the same two offices. At least in terms of the functions of my operations, those offices were part of my critical path.
As I read Godin’s post, I was reminded of the oft heard statement: fast, cheap, quality, choose any two. There are staff members that are frequently given tasks with competing priorities and are left to ask which of the crucial tasks are slightly less crucial.
Analyzing the critical paths by general project types would assist decision making about resource and time management within the organization. One notable thing about Godin’s example is that the project, rather than the organization chart, determined who were the most important staff members. If it took the president fetching coffee for the graphic designer to make the project succeed, that is what happened.
The president does play a crucial role in the organization and can’t be spending all their time fetching coffee, but their work may not represent a crucial juncture in the overall process upon which other activities depend. (Except for signing payroll, of course!)
Think about the critical paths in your organization. It may surprise you to learn what your critical paths are and may reveal some awkward truths about where resources really need to be allocated to meet the mission of your organization.
Though remember that this is more than just needing a lot of hands to help out with a process, it is about a chain of events that definitely depend on the prior step being completed. Needing 10 people to stuff envelopes on Wednesday isn’t part of the critical path if having six people start on Monday will accomplish the same goal of getting it all out by Friday. It is, however, if you are mailing out W-2 tax forms which, by law, need to go out by January 31 and the forms can’t be printed out until Tuesday because the payroll data isn’t available until Monday, because…