Looking for something? Look here!
Want more unvarnished truth?
What you're saying...
What I'm saying now
I think tag clouds are pretty, and not to be taken overly seriously
##MoveWithGary #Home Inspection #MoveWithGary 111 Chop House 75 on Liberty Wharf 9/11 A Broth of a Boy ABCs Abiouness accountability activities alcohol Allora Ristorante Analysis Angry Hams ANSI/TIA 942 Anthony's Pier 4 Apple Application Armsby Abbey Arsenal Arturo's Ristorante Ashland AT&T Audio Automation baby Baby Monitor babysitting Back To School Bad News Bangkok Thai banks lending movewithgary Bar Bay State Common baystateparent BBQ BCP Bees BeeZers Before I die I want to... behavior Big Bang Bike Bill of Rights Bistro Black Box BlackBerry Boston Boston Marathon boundaries Boyston BPO brand Breakfast Bridge Bring Your Own Technology Budget Burlington Burn Burrito buyer BYOD Cabling Cambridge Camp Campaign career Casey's Diner Castle casual cCabling Cell Phone Central Square Change Management Cheers Chef Sun ChengDu Chet's Diner Children Chinese Christmas Christmas Families Holiday CIO Cloud coddle collage College College Acceptance co-lo Co-Location Co-Location Tier Power Cooling Comfort Food Control Country Country Kettle Crisis customer dad Dad Phrases damage daredevil Data Center Data Center Design Davios Day Care Dead Death declaration Del Frisco's Design Desktop Video dinner Disaster Recovery Divorce Do Epic Shit dodgeball downsizing Downtown Crossing DR driving Droid Easter Economic Kids Edaville Education Elbow Night Elevator Employee Engagement Erin Estate Planning Etiquette Evaluation events Exchange Expiration Dates Facebook Failing family Family Law Fatherhood Favorite things first time buyer Flash Flemings Fogo de Chão Food Hits and Misses Format Foundry on Elm Foxborough Frameworks fraternity Fraud French Fried Clams friends fun Fusion Generations germs Girl Scouts girls Global Go/No Go GPS Grafton Grandchild Grandpa Harry's hazing Healthcare Healthy Choices while Dining Out Help Desk Hisa Japanese Cuisine Historic holiday Home Home Inspection hope Horizons hose Hot Dog Hurricane IIT Assessment incident Indecision Indian Infrastructure Inn Innovation Insurance Internet Inventory Management iPhone IT IT Assessment IT Satisfaction Italian Jack Daniels Jakes Restaurant Janet Japanese Jazz Joey's Bar and Grill JP's Khatta Mitha kickball kids Laid off Lakes Region Lala Java Leadership Learning legacy Legal Legal Harborside Les Zygomates L'Espalier Liberty Wharf life transition lights out Linguine's loss Love Lucky's Cafe luxury luxury home M&M Macys Thanksgiving Day Parade mai tai Managed Application Services Managed Services managers Mandarin Manners Mark Fidrych marlborough marriage Mary Chung mass save Maxwell-Silverman Mediterranean meetings Memorial Day memory Mendon Mergers Mexican MiFi Migration Ming III miss MIT MIT CIO Symposium mmortgage Mobility Moes Hot Dog Truck MOM money mortgage Mother MoveWithGary Moving on Name nature neanderthal neighborhood Network new listing New York Marathon newborn Northborough Not Your Average Joe's Nuovo Nursing On-Call Operations Operators Oregon Club Organization Pancakes Pandemic Parental Control Parenting Patch Peeves People Perserverance UMASS growth Photography Play Plug and Run Predictable Pride Problem Process Production program Project Management propane PTA. PTO PUE QR Quick Response Rant re/max Real Estate Realtor Recognition Red Rock Resiliency Respect restaurant Restaurant Guy RFP ribs Ritual Root Cause Analysis rReal Estate Sam Adams Sandy Sapporo savings School Sea Dog Brewing Company Sea Dog Steak and Ale Seafood Seaport Security Sel de la Terra Service Service Desk Service Indicator Light sharing ShearTransformation SHIRO Shit Pump Shriners SHTF Simplification Skunk Works Skype Sleep sleepovers Sloan Smith & Wollensky soccer Son SOP sorority spanking Squarespace staffing staging Starbucks Status Reporting Steak Steve Jobs Storage Strategy stress Summer Sushi swimming Tacos Acalpulco teacher Technology Teen Telephony Temperature Strip Tenka terrorist Testing Texas BBQ Company Text Thai Thanksgiving in IT The Mooring Thomas Thought Leader Three Gorges III TIA 942 Timesheets Toby Keith Toddlers traditions Transition treehouse turnover TV Twitter unspoken moments Valentine's Day Value Vendor Venezuelan Verizon Vermont Video Vietnamese voice VoIP Watertown Wedding Westborough Korean Restaurant Westborough MA. StormCam WiFI Wi-Fi Wilbraham Wine Worcester work work life balance working Yama Zakura Zem Han Zitis

Entries in Status Reporting (1)


I don’t like Timesheets in IT. And I like them even less when they are forced to be incorrect. 

This post isn’t about timesheets per se.  It’s about the impact of companies not thinking through process and the desired business outcomes.

Those of you who know me can appreciate why I don’t like Timesheets.  I tend to work a lot of hours…sometimes because the business need is there and sometimes simply because I like what I do and it’s not “always” work to me.

I don’t mind getting the work accomplished, and either making progress or delivering on the mission.  It becomes “work” to me when it is ancillary to the process.

Take status reporting.  If someone wants to know what I’m doing, ask.  Having a painful process of putting together a (weekly) status report nobody reads is wasteful.  A fairly experienced team once called the status reporting exercise a “shit pump.”  At first I was offended, then I came to agree.  In this company, we put a lot of effort into producing a weekly report nobody read.  Literally, you could have the same update for weeks on end without question. There was even a formally developed weekly reporting system used. Senseless.

My current company does produce a weekly status, encouraged to be no more than one page.  In it, we articulate:

  • A simple “at a glance” summary

  • Accomplished this period (week ending xx/xx/xx) 
  • Plans for Next Period (week ending xx/xx/xx)
  • Critical Findings 
  • Issues Requiring Management Attention

It takes about 15 minutes to prepare, and we know our clients read them.

So…subtle message number one. 

 If you are going to force the organization to do something, use the results.

What does this have to do with Timesheets in IT?

Timesheets are used in some organizations for pay purposes.  Typically “non-exempt” or hourly staff record their time on timesheets to get paid.

Other organizations use the time for billing against a (capitalized) project, where knowing the total time is imperative for the financials.

What some organizations do is “force” the numbers based on some mis-guided view they are helping the organization.  The most common “force” is a 40 hour work week.

Telling an hourly paid person to put 40 hours on the timesheet irrespective of the workload is wrong…and illegal.  In some locales time over 40 hours is subject to mandatory overtime pay these staff members are entitled to by law.

The same thing can happen on projects.  “Keep the time at 40 hours, that’s all the budget allows.”  Well, if that’s all the budget allows why keep track of time?  You need to know when people are overallocated or not.  You need to know when someone has extra capacity.

In IT Operations the person reporting time is often doing the same thing for the day….ie…media management, monitoring, or help desk, to name a few.  Why do we ask them to record their time?  I see no purpose in this activity.

One defunct company used to record their IT time to the tenth of an hour.  People literally recorded bathroom time.  Really?  How was the company using this data?  Certainly an analysis of potty time would lead to an increased number of strategically located bathrooms.

By the way, telling people to record time wrong is telling them to lie.  We should not be telling our people to “lie” to force an answer…it’s the wrong message to give people.

While I understand the need to understand financial implications of time, there are fundamentally better ways of collecting this information on a satisfactory basis.

Subtle message number two. 

If an organization is going to record time, or do other administrative acts,  it should be generally accurate. 

The bottom line:  Companies need to understand the business outcome they are looking for from a process and ensure this is paramount in any process changes.

What’s your view?