Tuesday, November 07, 2006

"Vanishing Technology" (continued)

Mike HaydenIn my previous blog, I asked, "Why does Vanishing Technology happen repeatedly."

The plain truth…

Most people hate to write documentation. For most people, writing documentation is hard, tedious work that demands a lot of time, discipline, and rigorous attention to detail.

I'm sure you recognize that the problem of Vanishing Technology is not new. Imagine the frustration of watching companies sink like leaky ships. You point to the leaks. But, their crews say,
"We have no time to patch leaks. We're too busy sailing for the gold."
When you suffer Vanishing Technology, your company is like that sinking ship. And you know you cannot sail a leaky ship ... very far. To develop a "seaworthy" business, you - or someone - must write the right stuff to help you build your business like a leak-proof hull.

Documenting your business is the work of "business development."

Yet, when business booms people say...
"We don't have time to write ... too many projects ... it is not a priority now... we'll get to it later... yada... yada... yada..."
But, have you noticed when there's a business bust, people have plenty of time to write CYA Memos and resumes? Bottom line: Nobody writes the documents vital to your business!

That's why you see Vanishing Technology happen repeatedly.

What can you do?

To prevent Vanishing Technology, you must develop your business to survive hard times.

This means you must curtail dependence on "key people" and their tacit "tribal knowledge." (If your business needs exceptional people, you cannot hope to produce consistent results.)

This means you - or someone - must write down your key business processes! This means you must work ON your business as you work IN your business. As they say, "Publish or perish!"

You must develop and document a result producing system -- a SYSTEM that amplifies ordinary skills and abilities into extraordinary results. Profitable Venture Tactics can help you create the right documentation to integrate four steps to success:
1. Organizing,
2. Planning,
3. Developing, and
4. Operating your business.
Summary

Are you risking the loss of your most valuable assets ... your people ... your business processes ... your intellectual property? The plain truth is most people hate to write documentation ... And this leads directly to Vanishing Technology!

When you suffer Vanishing Technology, your company leaks like a sinking ship. By applying the business development techniques I call "Profitable Venture Tactics," you can protect yourself from Vanishing Technology and build your business like a leak-proof hull.
Documenting your business is the work of "business development." This means you must work ON your business as you work IN your business.
Don't let Vanishing Technology stunt the growth of your business!

============================================================
EXERCISE FOR THE SERIOUS ORGANIZATION BUILDER.
Download an updated (FREE) version of the Business
Builder Outline (PDF file)

============================================================

HELP Profitable Venture Tactics help your colleagues.
This eZine relies on subscriber's participation. So, it stands to reason, the more subscribers, the more participation. You can expand the circulation by telling your colleagues about Profitable Venture Tactics.

Your business and management colleagues will thank you for being so thoughtful.
What did you learn today that you found most beneficial?
How will you apply what you have learned at work?
Please email your comments

Best Regards,

Mike Hayden, Principal/Consultant
Your partner in streamlining business.

PS. If you're not on our P V T Roster, click here PVT sign up (FREE)
PPS. Click here to sign up for the PVT Forum (FREE).


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
(c) 2006 Mike Hayden, All rights reserved. You may use
material from the Profitable Venture Tactics eZine in
whole or in part, as long as you include complete
attribution, including live website links and email link.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *