Superheroes don’t work 90-hour weeks
bbc.co.uk
bbc.co.uk
Head space was an experiment where every fortnight, at Friday noon it was tools down and do what ever you want. You were encouraged to go away from the office. Ride your bike, have lunch with your wife/husband or family. What ever you thought was giving you head space.
Heads down days were every Tuesday and Thursday of every week. This meant, on those days no meetings. Work from where ever you want. Turn off Slack. Close your email client. The idea here is "planned" uninterrupted time so you get into the zone for a long stretch of time.
Edit: Oh. Forgot about this. The other Friday afternoon every fortnight we would do "refactor" afternoon. It's were the dev team would come together and refactor parts of the code base as a team. You would get to see parts of the code you'd normally never work on and some really great discussions came out of that.
Head-space is great. On Friday afternoons people are usually tired and mess around anyway, so why not do something useful with that time instead of hanging around to do your 40 hours.
Honestly, this has always been table stakes for me. I hope I never work at a place where I'm judged on "hours my butt is in a seat" instead of "actual productivity". Particularly for creative work, it's just not how the human brain works.
Not really: this is just the streetlight bias in action. A high-precision estimate of a useless metric isn't better than a lower-precision estimate of a relevant metric.
I've only worked at places well-run enough (at least in that regard) that people are competent enough at their jobs to measure overall productivity: it doesn't generalize to an automatic rubric like "# of commits" or "lines of code", but it is doable.
I’m going to talk to my senior about trying this out tomorrow. They love stuff like this
"People who like meetings would have nothing to do" is so stupid yet a hilariously plausible reason why this would fail.
I'm super human by all honest measures, but management without fail starts giving me guff about going to the gym and having lunches away from my desk. I can venture into justifying that I don't use social or anything on the clock which creates clear head space, etc etc, but it'd fall on deaf ears... I'm old school like that.
But the calendar creates an attack surface. I don't want to work at such companies, it's not always been that way, but it's been consistent across shit rung startups.
Management wants me at my desk 12 hours a day and always on call, and makes "jokes" about anything that I mark as time I want away from my desk. Often 2 hours discussions start 15 minutes before I have an outside event noted.
I quit these jobs when the abuse threshold is crossed, but the departments are made up of mostly people on visas etc so they're not so lucky. It should never strike management as a surprise when I leave, but I get the impression they're used to dishing out abuse to "non-compliant" programmers. The bros thrive, the meek get beat down and go home to lonely apartments full of cats where they passionately code themselves to sleep with Netflix.
In both jobs I've had, the opposite has been encouraged. At my current job, we go out for a team lunch most days (sadly not paid for by the company). I'd lose my shit if I sat at my desk for 9 hours straight.
At my old job, I used to go to the gym at lunch, and it had to be at a set time due to classes. I blocked it out in my calendar indefinitely and made sure everyone knew. I also made my displeasure very apparent the few times it was booked over.
As far as I was concerned, going to the gym was more productive than any meeting I could participate in, my productivity was at its peak right after the gym.
Taking a breath, zooming out, and creating mental space to switch tasks is still work.
The people that claim to work 90 hour weeks are generally entrepreneurs who include lunch meetings and things like thinking about strategy outside of the office, in those hours. If you own the business you never really stop thinking about it, but that is a completely different measure than for an employed individual contributor.
At least, it used to be. It seems a lot of people have forgotten these lessons.
I never once heard them complain about my output.