| July 31, 2002 | Volume 2, Issue 31 |
| Recommend this issue to a friend Join the Friends of Point Lookout HTML to link to this article… |
Archive: By Topic
By Date
Links to Related Articles Sign Up for A Tip A Day! |
| Create a perpetual bookmark to the current issue
| |
by Rick Brenner
Today we use data as a management tool. We store, recall and process data about our operations to help us manage resources and processes. But this kind of management data is often scattered, out of date or just plain incorrect, and taking a snapshot doesn't work. There is a better way.
fter 20 minutes of struggling with the arcane language of the auditor's memo, Patricia was finally beginning to understand what she needed to know. She asked Geoff, "And how many projects have people who've been on site over 180 days?"
"Hard to say," he replied. "I'd guess that most do, but only the project managers know for sure."
"OK, can you have a summary by tomorrow at Two? We have to know our exposure."
"I doubt it," said Geoff. "We'd have to find out who the project managers are first. The regional offices keep that sort of information — there's no central repository."
"Well, OK, do what you can for tomorrow," said Patricia. "But meanwhile, I can't believe that we don't know who the project managers are. Can't the regions just send us the basics on every project?"
Geoff and Patricia are about to enter a world that seems strange to non-specialists — the world of electronic Database Management. In that world, our paper-based intuition misleads us. Although it's counter to our intuition, it would be a mistake for Patricia to take a "snapshot" — to collect the project manager data and keep it around until she needs it. By then, it will be out of date.
Organizations are in
constant motion.
They don't pause
for snapshots.Although photographic snapshots do capture all the elements of a scene simultaneously (or nearly so), we can't collect management data that way. If the organization is large enough or scattered enough, no team of practical size can gather simultaneous data from across the organization. The phone tag alone prevents it. But even if it were possible, the data is volatile. People are reassigned, projects begin or end, and phone numbers change. As soon as the data is collected, it's out of date in unknown ways. Snapshots don't work because the subject can't sit still.
Centralized databases work, but since data owners typically don't have write access, the data must still be collected. The price of central databases is agility and flexibility.
Often, a better solution is to leave the data in the hands of its "owners," and compile summaries on demand using automation. Most large organizations are networked, so it's possible to give the owners of the data the responsibility for maintaining up-to-date local versions in standard form on their own file servers. Then, using the organizational Intranet, anyone can use automated network software to poll the local data stores, compiling an organizational summary whenever they need one.
We don't think of doing things this way because our mental models of how we work haven't caught up to our networked reality. We imagine looking up what we need in a continuously updated central data store, analogous to a Rolodex or paper ledger. But in the networked organization, where data is constantly changing, we gain an advantage if we automatically compile data just in time — on demand.
Top
Next Issue
The article you've been reading is an archived issue of Point Lookout, my weekly newsletter. I've been publishing it since January, 2001, free to all subscribers, over the Web, and via RSS. You can help keep it free by donating either as an individual or as an organization. You'll receive in return my sincere thanks — and the comfort of knowing that you've helped to propagate insights and perspectives that can help make our workplaces a little more human-friendly. More info
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.
Past issues of Point Lookout are available in four e-books:
Available in early 2009: 2007-2008.
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. Check it out!
add value to your Web sites quickly and easily. Pick up the HTML to link to this article in a choice of formats.
Are you fed up with tense, explosive meetings? Are you or a colleague targets of a bully? Read 101 Tips for Managing Conflict to learn how to make peace with conflict. Check it out!
Are your projects always late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips & techniques for organizational leaders. Check it out!
A Tip a Day arrives by email each business day. It's 20 to 30 words at most, and gives you a new perspective on the hassles and rewards of work life. Most tips also contain links to related articles. Free!
Save a bundle and even more important save time! Order the Combo Package and download all 21 ebooks and tips books at once, for one low price of USD 161.95 vs. USD 317.97, a savings of over 49% compared to ordering them separately.