DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

Ditch the Timesheet and Pick Up a Ball

Let's think about what's important here. First of all, we all constantly put off timesheets. Secondly, we shouldn't be multitasking that much, anyway.

Evan Leybourn user avatar by
Evan Leybourn
·
Jan. 23, 17 · Opinion
Like (2)
Save
Tweet
Share
3.50K Views

Join the DZone community and get the full member experience.

Join For Free

I have a personal hatred for timesheets. I think we all do. I know why they’re important and why we keep them, yet I always find myself putting them off. When I do get around to them, I get so frustrated with the level of detail required. So, here’s an idea: Ditch the timesheet.

But Evan, didn’t you just say they were important?

I did, but let’s think about what’s important. You want to know how much time you spent on which project or client, right? So, how about this? Ditch the timesheet and pick up a ball.

Set up a couple of bins by the door and label each one with the name of the project or client that you’re tracking. Twice a day, at lunchtime and closing, people toss a ball into the bin of the primary project they were working on (they can’t leave until they get it in — let’s improve that hand-eye coordination while we’re at it!) Then just count the balls in each. There’s your timekeeping done.

But what about hourly or minutely (is that a word) timekeeping?

First, read this article by Paul Graham on maker time versus manager time. We shouldn’t be multi-tasking. We should be working in half day blocks at least. Any less and you’ll lose at least 15-25% effectiveness. If it’s an email here or a phone call there, that’s OK. Just ignore capturing that time; it’ll balance out.

This does a couple of things: it gets the timesheet done on time, it forces you to work in half-day blocks, and it’s fun.

What do you think? Let me know below.

Blocks IT Label

Published at DZone with permission of Evan Leybourn. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • How to Secure Your CI/CD Pipeline
  • Secrets Management
  • Apache Kafka vs. Memphis.dev
  • Continuous Development: Building the Thing Right, to Build the Right Thing

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: