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
Would you like to see your comments posted here? rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.comSend 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.
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:
- The Zebra Effect
- If you're feeling overwhelmed by all the items on your To-Do list, and if you start on one only to realize
that you have to tackle three more you didn't know about before you can finish that one, you could be
experiencing the Zebra Effect.
- Coaching and Haircuts
- Lifelong learners use a variety of approaches, usually relying heavily on reading. Reading works well
for some ideas and techniques, especially for those with limited emotional content. For adding other
skills and perceptions, consider a personal coach.
- Asking Clarifying Questions
- In a job interview, the interviewer asks you a question. You're unsure how to answer. You can blunder
ahead, or you can ask a clarifying question. What is a clarifying question, and when is it helpful to ask one?
- Twenty-Three Thoughts
- Sometimes we get so focused on the immediate problem that we lose sight of the larger questions. Here
are twenty-three thoughts to help you focus on what really counts.
- Seven Ways to Get Nowhere
- Ever have the feeling that you're getting nowhere? You have the sense of movement, but you're making
no real progress towards the goal. How does this happen? What can you do about it?
See also Personal, Team, and Organizational Effectiveness and Personal, Team, and Organizational Effectiveness for more related articles.
Forthcoming issues of Point Lookout
- Coming January 22: Storming: Obstacle or Pathway?
- The Storming stage of Tuckman's model of small group development is widely misunderstood. Fighting the storms, denying they exist, or bypassing them doesn't work. Letting them blow themselves out in a somewhat-controlled manner is the path to Norming and Performing. Available here and by RSS on January 22.
- And on January 29: A Framework for Safe Storming
- The Storming stage of Tuckman's development sequence for small groups is when the group explores its frustrations and degrees of disagreement about both structure and task. Only by understanding these misalignments is reaching alignment possible. Here is a framework for this exploration. Available here and by RSS on January 29.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.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
Follow Rick
Recommend this issue to a friend
Send an email message to a friend
rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed
- Your stuff is brilliant! Thank you!
- You and Scott Adams both secretly work here, right?
- I really enjoy my weekly newsletters. I appreciate the quick read.
- A sort of Dr. Phil for Management!
- …extremely accurate, inspiring and applicable to day-to-day … invaluable.
- More