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.

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:

Holey Grails

How much of the time and energy you spend in meetings goes to finding the best way? or a better way? It's of questionable value unless you first agree on what you mean by "better" or "best."

The Hypothetical Trap

Politicians know that answering hypothetical questions is dangerous, but it's equally dangerous for managers and project managers to answer them in the project context. What's the problem? Why should you be careful of the "What If?"

In the Groove

Under stress, we sometimes make choices that we later regret. And we wonder, "Will I ever learn?" Fortunately, the problem usually isn't a failure to learn. Changing just takes practice.

How to Foresee the Foreseeable: Recognize Haste

When trouble arises after we commit to a course of action, we sometimes feel that the trouble was foreseeable. One technique for foreseeing the foreseeable depends on recognizing haste in the decision-making process.

Performance Issues for Non-Supervisors

If, in part of your job, you're a non-supervisory leader, such as a team lead or a project manager, you face special challenges when dealing with performance issues. Here are some guidelines for non-supervisors.

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

Forthcoming issues of Point Lookout

Coming June 20: Managing Dissent Risk

In group decision making, dissent risk is the risk that dissents about important decisions will be rejected without due consideration. As a result, group decision quality can suffer, and some groups will actually eject dissenters. How can we manage dissent risk? Available here and by RSS on June 20.

And on June 27: Interrupting Others in Meetings Safely: I

In meetings we sometimes feel the need to interrupt others to offer a view or information, or to suggest adjusting the process. But such interruptions carry risk of offense. How can we interrupt others safely? Available here and by RSS on June 27.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenrZUPIIpauiMMRzCaner@ChacCrbddnMWcXJigdfdoCanyon.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, USD 11.95)
• Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
• Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
• Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
• Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
• Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)

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 words in your inbox in one hour. License any article from this Web site. More info

Public seminars

The Race to the South Pole: The Power of Agile Development

On 14 December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough. Lessons abound. Among the more important lessons are those that demonstrate the power of the agile approach to project management and product development. Read more about this program. Here's a date for this program:

• Ohio National Insurance, 1 Financial Way, Blue Ash, OH: July 17, Monthly Meeting, Cincinnati chapter of the International Institute of Business Analysis. Register now.
   

The Power Affect: How We Express Our Personal Power

Many people who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program.

• A recording of a program presented 6:00 PM June 29 (Eastern Time), Monthly Webinar, Technobility Webinar Series. You can earn 1.0 Category 'A' PDU by viewing this program. View this program now.