Working Hard is not the same as working smart

Working Hard is not the same as working smart

Working Hard is not the same as working smart

Measuring how hard your team is working by counting the number of hours they work or what time they get in and leave is how amateurs run companies. The number of hours worked is not the same as how effective they (and you) are.

I had been invited by Rahul, one of my students from long ago, to stop in and see how his startup was doing.  Actually startup would be a misnomer as Rahul had built a great company, now over $50M in annual revenue with hundreds of employees.

We were scheduled for dinner, but Rahul invited me over in the afternoon to sit in on a few of his staff meetings, get some product demos, admire the furniture and the café, and get a feel of the company.

Before we left for dinner I asked about the company culture and the transition from a startup to a company. We talked about how he was on-boarding new employees, managing scale by writing operations manuals for each job function, and publishing company and department mission and intent (he said he got the idea from reading my blog posts on mission and the one on innovation culture). It was all impressive – until we got on the subject of how hard his employees worked. His response reminded me what an idiot I had been for most of my career – “Our team knows this isn’t a 9-5 company. We stay as long as it takes to get the job done.” I looked a bit dumbfounded, which I think he took for impressed, because he continued, “most days when I leave at 7 pm my employees are still hard at work. They stay all hours of the night and we often have staff meetings on Saturdays.”

Read Also:
Learn How to Build a Data Governance Dream Team

I cringed. Not because he was dumb but because for most of my career I was equally clueless about what was really happening. I had required the same pointless effort from my teams.

Our dinner was scheduled for 7:15 around the corner so we headed out at 7, announcing to his staff he was off to dinner. As soon as we got outside his building and into the full parking lot I asked Rahul if he could call the restaurant and tell them we were going to be late. I said, “Let’s just wait across the street from your company’s parking lot and watch the front door. I want to show you something I painfully learned way too late in my career.” He knew me well enough to patiently stand there.  At 7:05, nothing happened. “What am I supposed to be seeing?” he asked. “Just wait,” I replied, hoping I was right. At 7:10 still no movement at the front door.

Read Also:
Why nature is our best guide for understanding artificial intelligence

 



Data Innovation Summit 2017

30
Mar
2017
Data Innovation Summit 2017

30% off with code 7wData

Read Also:
Are you brave enough to change your Data Habits?

Big Data Innovation Summit London

30
Mar
2017
Big Data Innovation Summit London

$200 off with code DATA200

Read Also:
Why nature is our best guide for understanding artificial intelligence

Enterprise Data World 2017

2
Apr
2017
Enterprise Data World 2017

$200 off with code 7WDATA

Read Also:
How to ruthlessly use data like a boss without becoming inhuman

Data Visualisation Summit San Francisco

19
Apr
2017
Data Visualisation Summit San Francisco

$200 off with code DATA200

Read Also:
How This Entrepreneur is Democratizing Access to the World’s Data

Chief Analytics Officer Europe

25
Apr
2017
Chief Analytics Officer Europe

15% off with code 7WDCAO17

Read Also:
How This Entrepreneur is Democratizing Access to the World’s Data

Leave a Reply

Your email address will not be published. Required fields are marked *