by Rick Brenner
To solve problems, we change existing policies or processes, or we create new ones. We try to make things better and sometimes we actually succeed. More often, we create new problems — typically, for someone else.
When we solve one problem by creating other problems somewhere else, we're Dumping. Most of the time, we dump problems without the permission of the people who end up receiving them. Some examples:
- Finance announces a lower maximum for petty cash purchases — $50. Some purchases that formerly came from petty cash must now use the requisition process.
- To expand employee parking, visitor parking is eliminated. When you expect visitors, explain to them which part of the Fire Lane to park in while they run inside for a visitor pass that lets them into the employee parking area.
- I say we ship the product as it is. Let Customer Service deal with the bug reports until the bug-fix release.
Why do we dump?
Shortcomings in accounting systems insulate problem-solvers from the problems they dump. For example, many organizations know the cost of processing requisitions, but few know the cost of preparing them. Since these costs lie outside the Finance department, Finance rarely knows the impact of lowering the petty cash limit, which might actually increase organizational expenses.
In the parking lot example, the gain of spaces is lower than it seems, because visitors now use the employee lot. And since cars now park temporarily in the Fire Lane, there's more risk of fire damage and injury. Unrecognized costs make the parking change less attractive than it seems, but we don't know by how much.
In the product release example, Marketing is free to press for premature shipment, because the increased cost of customer complaints comes not from Marketing but from Customer Service.
from the problems
they dump on othersSometimes there's a positive incentive to dump. In the petty-cash example, we can expect an increase in purchase requisitions, which lowers the average cost of processing them. Cynical financial managers can thus improve their own organizational performance by depressing the performance of their internal customers.
Here are three ways to deal with dumping.
- Don't dump
- When you devise solutions to problems, avoid dumping. Collaborate. If others play a role in the solution, they should play a role in devising that solution.
- Educate others about dumping. When everyone understands the concept, problem solutions are less likely to involve dumping.
- Require impact statements
- Require authors of procedural changes to prepare impact statements that estimate total organizational costs. Shift the focus from local departmental accountability to global impact.
- Compensate dumpees
- When costs shift, adjust budgets. You might have to be a manager or executive to do this, but if you are, recognize your responsibility. Don't permit one part of your organization to shift burdens to others without paying for the privilege.
If you can control dumping, dumping gains no advantage. This lets the steam out of much of organizational politics — and we all know how much time we spend on politics. Top Next Issue
Is every other day a tense, anxious, angry misery as you watch people around you, who couldn't even think their way through a game of Jacks, win at workplace politics and steal the credit and glory for just about everyone's best work including yours? Read 303 Secrets of Workplace Politics, filled with tips and techniques for succeeding in workplace politics. Order Now!
Your comments are welcome
Would you like to see your comments posted here? Send 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
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.
More articles on Workplace Politics
- The Costs of Threats
- Threatening as a way of influencing others might work in the short term. But a pattern of using threats to gain compliance has long-term effects that can undermine your own efforts, corrode your relationships, and create an atmosphere of fear.
- Obstructionist Tactics: Part I
- Teams and groups depend for their success on highly effective cooperation between their members. If even one person is unable or unwilling to cooperate, the team's performance is limited. What tactics do obstructors use?
- What Is Workplace Bullying?
- We're gradually becoming aware that workplace bullying is a significant deviant pattern in workplace relationships. To deal effectively with it, we must know how to recognize it. Here's a start.
- On Advice and Responsibility
- Being asked for advice can be an affirming experience, but actually giving advice can sometimes entail risk. How can this happen, and what choices do we have?
- Managing Non-Content Risks: Part I
- When project teams and their sponsors manage risk, they usually focus on those risks most closely associated with the tasks — content risks. Meanwhile, other risks — non-content risks — get less attention. Among these are risks related to the processes and politics by which the organization gets things done.
See also Workplace Politics and Problem Solving and Creativity for more related articles.
I offer email and telephone coaching at both corporate and individual rates.
Contact me for details at rbrenner@ChacoCanyon.com
or (617) 491-6289, or toll-free in the continental US at (866) 378-5470.
Get the ebook!
Past issues of Point Lookout
are available in six ebooks:
Reprinting this article
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 words in your inbox in one hour. License any article from this Web site. More info
- The Race to the South Pole: Ten Lessons for Project Managers
- On 14 December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough, but to project managers, the story is fascinating. Lessons abound. Read more about this program. Here's an upcoming date for this program:
- The Race to the South Pole: The Power of Agile Development
- On 14 December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough. Lessons abound. Among the more important lessons are those that demonstrate the power of the agile approach to project management and product development. Read more about this program. Here's an upcoming date for this program: