
Flames can be beautiful. We can become fascinated by their beauty. So it is with "organizational flame." Some people actually enjoy emergencies.
Some of us have been in firefighting mode so long that getting far enough ahead of the fires to carve out some time to make sensible plans can seem like an unattainable goal. But by changing the way we deal with urgent problems, we can increase the likelihood of returning to routine. Here are four suggestions for breaking out of firefighting mode by changing how we address the fires.
- Triage the problems
- Instead of letting the order of discovering problems determine their priority, set priorities consciously. Designate a small team — two or three people are usually enough — to assign a priority to each problem as it arrives. Let them decide who is available to work each problem when its time comes.
- This is the group that must occasionally make the hard decisions to "let some fires burn." (See "How to Get Out of Firefighting Mode: I," Point Lookout for January 25, 2017) Such decisions will stick only if the members of this group have the respect of the team and their management.
- Empower the problem solvers
- Concentrating decision-making authority in the hands of a few carries a risk of creating bottlenecks, which then compromise a team's ability to get ahead of fires.
- With regard to problem solving, push decision making out onto a larger circle of problem-solvers by creating authority boundaries that enable more people to solve problems with autonomy. Some tactics that help:
- Specify classes of problem solutions that can be implemented at lower levels.
- Assign problems to the lowest level available team members who are qualified to deal with those problems.
- Provide expert advice and support to less-expert problem solvers rather than dedicating experts to solving problems.
- Search for common causes
- Sometimes Concentrating decision-making
authority in the hands of a
few carries a risk of
creating bottlenecksproblems that appear to be unrelated are actually different sets of consequences of the same underlying problem. When this happens, solving problems independently wastes resources. Worse, independent "solutions" are unlikely to succeed, and might even conflict. - Keep in mind the possibility that a single issue can manifest itself differently in different contexts. Before investing significant time and resources in solving two problems independently, seek convincing evidence that they really are independent.
- Include firefighting in risk plans
- If your organization has much experience with firefighting mode, planning for firefighting risk can reduce the likelihood of fires, and reduce fire lifetime when fires erupt.
- A firefighting risk plan could include criteria for declaring and terminating states of fire danger. Three levels of fire danger are probably sufficient. Define routine procedures for each level. Examples:
- Level 3: Elective paid time off is suspended
- Level 2: Triage team is activated
- Level 1: Triage team deactivated and elective paid time off is encouraged
Study the tactics and strategies of wildland firefighters and emergency incident responders. There's no need to re-invent what has already been invented. First issue in this series
Top
Next Issue
Projects never go quite as planned. We expect that, but we don't expect disaster. How can we get better at spotting disaster when there's still time to prevent it? How to Spot a Troubled Project Before the Trouble Starts is filled with tips for executives, senior managers, managers of project managers, and sponsors of projects in project-oriented organizations. It helps readers learn the subtle cues that indicate that a project is at risk for wreckage in time to do something about it. It's an ebook, but it's about 15% larger than "Who Moved My Cheese?" Just . Order Now! .
Your comments are welcome
Would you like to see your comments posted here? rbrenubcqSvusyBsQaEDwner@ChacfhuriyFKgDguTpuYoCanyon.comSend me your comments by email, or by Web form.About Point Lookout
Thank you for reading this article. I hope you enjoyed it and
found it useful, and that you'll consider recommending it to a friend.
This article in its entirety was written by a human being. No machine intelligence was involved in any way.
Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.
Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.
Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.
Related articles
More articles on Project Management:
Restarting Projects
- When a project gets off track, we sometimes cancel it. But since canceling projects takes a lot of courage,
we look for ways to save them if we can. Often, things do turn out OK, and at other times they don't.
There's a third choice, between pressing on with a project and canceling it. We can restart.
Geese Don't Land on Twigs
- Since companies sometimes tackle projects that they have no hope of completing successfully, your project
might be completely wrong for your company. How can you tell whether your project is a fit for your company?
Team Risks
- Working in teams is necessary in most modern collaborations, but teamwork does carry risks. Here are
some risks worth mitigating.
Ten Approaches to Managing Project Risks: III
- Project risk management strategies are numerous, but these ten strategies are among the most common.
Here are the last three of the ten strategies in this little catalog.
Just-In-Time Hoop-Jumping
- Securing approvals for projects, proposals, or other efforts is often called "jumping through hoops."
Hoop-jumping can be time-consuming and frustrating. Here are some suggestions for jumping through hoops
efficiently.
See also Project Management and Project Management for more related articles.
Forthcoming issues of Point Lookout
Coming June 4: White-Collar Contractor Sabotage
- Modern firms in competitive, dynamic markets draw on many types of employer/employee relationships, including contractors. By providing privileges and perks preferentially among these different types, they risk creating a caldron of resentments that can reduce organizational effectiveness. Available here and by RSS on June 4.
And on June 11: More Things I've Learned Along the Way: VI
- When I gain an important insight, or when I learn a lesson, I make a note. Example: If you're interested in changing how a social construct operates, knowing how it came to be the way it is can be much less useful than knowing what keeps it the way it is. Available here and by RSS on June 11.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenubcqSvusyBsQaEDwner@ChacfhuriyFKgDguTpuYoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.
Get the ebook!
Past issues of Point Lookout are available in six ebooks:
- Get 2001-2 in Geese Don't Land on Twigs (PDF, )
- Get 2003-4 in Why Dogs Wag (PDF, )
- Get 2005-6 in Loopy Things We Do (PDF, )
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
- Get 2009-10 in The Questions Not Asked (PDF, )
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )
Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500-1000 words in your inbox in one hour. License any article from this Web site. More info
Follow Rick
Recommend this issue to a friend
Send an email message to a friend
rbrenubcqSvusyBsQaEDwner@ChacfhuriyFKgDguTpuYoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed
