Snapshots of Squirming Subjects

After 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 nonspecialists — 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

Your comments are welcome

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 Personal, Team, and Organizational Effectiveness:

Films Not About Project Teams: I

Here's part one of a list of films and videos about project teams that weren't necessarily meant to be about project teams. Most are available to borrow from the public library, and all are great fun.

Using the Parking Lot

In meetings, keeping a list we call the "parking lot" is a fairly standard practice. As the discussion unfolds, we "park" there any items that arise that aren't on the agenda, but which we believe could be important someday soon. Here are some tips for making your parking lot process more effective.

What Enough to Do Is Like

Most of us have had way too much to do for so long that "too much to do" has become the new normal. We've forgotten what "enough to do" feels like. Here are some reminders.

How to Reject Expert Opinion: II

When groups of decision makers confront complex problems, and they receive opinions from recognized experts, those opinions sometimes conflict with the group's own preferences. What tactics do groups use to reject the opinions of people with relevant expertise?

Internal Audits Without Pain

If adhering to established procedures is part of your job, you probably experience occasional audits. You can manage the pain of the experience by regarding audit preparation as part of the job. Because it is. Here are some tips for navigating audits.

See also Personal, Team, and Organizational Effectiveness and Personal, Team, and Organizational Effectiveness for more related articles.

Forthcoming issues of Point Lookout

Coming May 14: Working with the Overconfident

A cognitive bias known as the Overconfidence Effect causes us to overestimate the reliability of our judgments. Decisions we make based on those judgments are therefore suspect. But there are steps we can take to make our confidence levels more realistic, and thus make our decisions more reliable. Available here and by RSS on May 14.

And on May 21: Mismanaging Project Managers

Most organizations hold project managers accountable for project performance. But they don't grant those project managers control of needed resources. Nor do they hold project sponsors or other senior managers accountable for the consequences of their actions when they interfere with project work. Here's a catalog of behaviors worth looking at. Available here and by RSS on May 21.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenDJpmhgyaDTwBQXkhner@ChacmGoYuzfZpOvDQdRkoCanyon.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