|
|
Like this article? PLEASE +1 it! |
|
Thrashing: The Productivity and Company Killer
Written by: Andy PiperArticle Overview: Every company struggles balancing long term strategy with achieving short term goals. But many companies easily fall into the trap of taking on too many short term projects. Taken too far, it can paralyze a company and keep you from achieving your goals. Learn to recognize signs of thrashing and how to keep it from draining the life out of your company.
![]() |
Free Download - Do You Have the Right Stuff to Partner with Microsoft HP or IBM By Andy Piper |
Thrashing: The Productivity and Company Killer
A struggling management team becomes completely reactive in every decision they make. They abandon long term plans for short term gains. Managers start taking resources away from established projects and putting them on special projects. Ultimately, the organization reaches a point where employees are spending more time moving from one project to another, causing projects to be cancelled before they can be completed. The team feels like they are just spinning their wheels. These are clear indications that the company is suffering from thrashing.
Thrashing is actually a computer term. It describes a scenario where a hard drive receives a series of requests and the device has to spend more time moving the read heads from one place of the disk to another than it does reading data from the disk. The overall productivity of the device is diminished and it takes longer to service the requests than if the requests were organized in order to minimize the amount of relocating that takes place.
Thrashing happens to organizations as well. It can have different disguises based on the type of organization. I experienced first-hand one start-up company with a nine month engineering project which ended up dragging out for 18 months. Sales opportunities were up, but close ratios were down. Support and sales organizations became confused over what the current priorities were and found themselves unable to properly prepare for anything that managed to get completed. The list of examples could go on and on.
There are four tips for avoiding thrashing within your organization. First, sell what you have. Most start-ups sell their product based on promises of a project. Keep these sales projects to an absolute minimum or make sure you can incorporate the functionality into the next planned release. As a believer in the 80/20 rule, you cannot afford to let these side projects consume more than 20 percent of your total engineering effort.
The second tip is to avoid one-off requests. Never solve a problem in a way that is specific to only one customer. Always make sure the solution you build solves the problem in a way that other customers will be able to use as well. That way, you only have to build the function one time.
Next, keep your projects small, focused and attainable. Even six- month projects can be broken down in to smaller, 2 week increments. It is always easier to hit short deadlines with small tasks. The team will be less likely to miss their small deadlines and that keeps the major targets in check.
Finally, beware of struggling managers who commonly see a short term fix of buying another solution to integrate with yours as a way to accelerate progress. In some cases, acquisition projects are perceived as easy, but some are quite difficult. The reality is that an acquisition is still just another project and will not solve the underlying problem of thrashing or help get the company back on track.
Once an organization enters a state of thrashing, it usually requires some radical changes in thinking to break the cycle. It is far easier to avoid this condition all together with a little preventative medicine. Have faith in your long term plans. Make them flexible enough to accommodate the needs of new customers. In doing so, my experience shows you can potentially achieve twice as much, and your company will rid itself of this expensive killer of companies once and for all.
Article Tags: absolute minimum, believer, computer term, disguises, engineering project, hard drive, management team, priorities, productivity, promises, ratios, reading data, sales opportunities, sales organizations, side projects, special projects, spinning their wheels, start up company, start ups, ups
|
About the Author: Andy Piper RSS for Andy's articles - Visit Andy's website Andy Piper is the author of Enterprise Readiness 101 and the founder of www.enterprise-readiness.com. For over ten years, he has worked with enterprise companies. He has developed applications and implemented solutions as a systems engineer. He spent several years at Microsoft as a sales engineer. Since 2004, Andy has been a product manager for different start up organizations such as Ardence and most recently Casenet. Click here to visit Andy's website Competetive Advantage Article Relational Software Eneterprise Readiness |
Related Forum Posts
Share this article with your friends. Fund someone's dream.
Leave a comment below or share on the left and you'll help support entrepreneurs in Africa through our partnership with Kiva. Over $50,000 raised and counting - Please keep sharing! Learn more.
Get advice & tips from famous business
owners, new articles by entrepreneur
experts, my latest website updates, &
special sneak peaks at what's to come!
Email us your ideas on how to make our
website more valuable! Thank you Sharon
from Toronto Salsa Lessons / Classes for
your suggestions to make the newsletter
look like the website and profile younger
entrepreneurs like Jennifer Lopez.



