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
Would you like to see your comments posted here? rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.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:
- Games for Meetings: I
- We spend a lot of time and emotional energy in meetings, much of it engaged in any of dozens of ritualized
games. Here's Part I of a little catalog of some of our favorites, and what we can do about them.
- Bonuses
- How we deal with adversity can make the difference between happiness and something else. And how we
deal with adversity depends on how we see it.
- Finding Work in Tough Times: Strategy
- If you're out of work and discouraged — or getting there — you're in great company.
Better than ever before. Getting back to work starts with getting to work on finding work. Here's a
collection of strategies for the job of finding work.
- The Retrospective Funding Problem
- If your organization regularly conducts project retrospectives, you're among the very fortunate. Many
organizations don't. But even among those that do, retrospectives are often underfunded, conducted by
amateurs, or too short. Often, key people "couldn't make it." We can do better than this.
What's stopping us?
- Disjoint Awareness
- In collaborations, awareness of how our own work might interfere with the work of others is essential.
Unless our awareness of others' work — and their awareness of ours — matches reality, the
collaboration's objective is at risk.
See also Personal, Team, and Organizational Effectiveness and Personal, Team, and Organizational Effectiveness for more related articles.
Forthcoming issues of Point Lookout
- Coming December 11: White Water Rafting as a Metaphor for Group Development
- Tuckman's model of small group development, best known as "Forming-Storming-Norming-Performing," applies better to development of some groups than to others. We can use a metaphor to explore how the model applies to Storming in task-oriented work groups. Available here and by RSS on December 11.
- And on December 18: Subgrouping and Conway's Law
- When task-oriented work groups address complex tasks, they might form subgroups to address subtasks. The structure of the subgroups and the order in which they form depend on the structure of the group's task and the sequencing of the subtasks. Available here and by RSS on December 18.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.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
rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.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