Taming the Time Card

At some point, most of us have been required to submit time cards. To most professionals the task often seems maddeningly trivial, especially when the card is due in ten minutes, we've forgotten how we actually spent our time for a few days, and the whole thing is just a piece of fiction.

In accounting or law, where time spent determines client billing, time reporting is obviously necessary. For many other professions, expended-effort data seems to have no real purpose. But expended-effort data can be an indispensable management tool for project-oriented organizations.

Why is this data so important? Projects are supposed to end. Often there's much more project work to be done than people to do it, which creates pressure to complete successfully any existing projects. That's one reason why project sponsors always ask, "When will it be done?"

To answer such questions, project managers need to know roughly how long each task should take, and how much effort has been expended so far. They estimate the former and measure the latter.

Management would rather estimate than guess time to completion. Lacking historical effort data, estimates cannot be based on data; lacking current effort data, actuals are little more than hunches. By tracking the time of project team members, project managers can control projects better because they can base their estimates on real data.

The primary requirements
of any time-card system
for professionals:
respect their time
and respect themIf your organization is project-oriented, and you don't yet collect expended-effort data, you might consider starting. But whether a system is in place, or you're considering one, take care that it meets your needs without burdening or insulting professionals. A well-designed system can be minimally intrusive and still yield useful data.

Here are some criteria for a time card system that doesn't put the corporate culture at risk:

• Gather effort data only from the people who work on projects.
• Include all overtime.
• Don't bother with supervisor's signatures. Any professional inept enough to get caught lying that way is not to be trusted with important project work.
• Collect data weekly. This helps keep people fairly current.
• Don't try to account for 100% of a person's time — focus on the time spent on project work.
• Put the system on the Intranet. Make it easy to use from anywhere.
• Provide a separate account for each project task, so you can compare actuals with estimates.
• Pick a minimum resolution: 15 minutes or more. Any finer than that is fiction.
• Report all work done, no matter where — even at home or on travel.

If people understand the need for the data you collect — and if you use that data — your time reporting system will be a tool, not a target.  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:

Don't Worry, Anticipate!

Dramatic changes in policy or procedure are often challenging, especially when they have some boneheaded components. But by accepting them, by anticipating what you can, and by applying Pareto's principle, you can usually find a safe path that suits you.

Snapshots of Squirming Subjects

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.

Make Space for Serendipity

Serendipity in project management is rare, in part, because we're under too much pressure to see it. If we can reduce the pressure, wonderful things happen.

Finding Work in Tough Times: Infrastructure

Finding work in tough times goes a lot more easily if you have at least a minimum of equipment and space to do the job. Here are some thoughts about getting that infrastructure and managing it.

How We Waste Time: II

We're all pretty good at wasting time. We're also fairly certain we know when we're doing it. But we're much better at it than we know. Here's Part II of a little catalog of time wasters, emphasizing those that are outside — or mostly outside — our awareness.

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