Work should only take up 25% of our time. These three steps make that happen.
Work for only 3 hours a day, but everyday | plumshell
I am an indie iPhone developer, and I've been working for 3 hours everyday for almost 2 years now. It may not work for everybody, but I started this habit in early 2014, and I have continued to do it since have I found that this is the most productive way to work for me.
People don't work as much as you think
There is a persistent idea that people work 40 hours a week. They don't, and if you try to do this it will break you. Here are some more reasonable guidelines.
How I got to 200 productive hours a month
A tested approach to improve your focus and productivity
How I got to 200 productive hours a month
A tested approach to improve your focus and productivity
Work less, get more: New Zealand firm's four-day week an 'unmitigated success'
Reduced hours for same pay increased successful work-life balance management, cutting stress levels and boosting commitment
Making 20% Time Work | begriffs.com
Following Google’s lead many companies have instituted “20% time” for their employees. This is one day per week in which employees can work on projects of their own choosing. The practice keeps developers motivated and sharp, produces tools to solve company problems, and in the best case creates open source which builds prestige and helps recruitment.
Doing nothing at work
Many engineers should be doing less work. I don’t necessarily mean producing less code or fewer changes, but literally working fewer hours in the day. When they do work, they should be working at a slower pace. I like to aim to be running at 80% utilization by default: unless I have a high-pressure project going on, I spend 20% of my workday away from the computer.
Here’s a metric that I bet you aren’t using… I want you to check it out, and start using it. It could be a real wake up call about how inactive your users are. I’m talking about the XD28 metric. A… | Moe Ali | 17 comments
Here’s a metric that I bet you aren’t using… I want you to check it out, and start using it. It could be a real wake up call about how inactive your users are. I’m talking about the XD28 metric. A lot of teams have never bothered to collect this data - but you can get started after 28 days. Here’s how the metric works👇 This metric looks at a user and determines how many days they used your product/feature in a 28 day cycle. If your user used your product just once in the last 28 days, they’re identified as 1D28. If they use it 5 days out of 28, they’re categorized as 5D28 and so on… Then you create a bucket with each number of days and how many users used the product for each number of days. For example, 17 users belong in the 5D28 bucket and 500 users belong in the 24D28 bucket. You can use this to create a distribution chart. You should be using these figures to calculate the average AND median number of days that users are using the product in a given 28 day cycle. Ideally you want people to be moving from a lower number of days to a higher number. E.g. If your average number of XD28 is 5 days, you want to aim for 15 days in a year’s time. This is an interesting metric because often you will find users at one extreme of this distribution curve. And it can be a real wake up call for Product Managers. | 17 comments on LinkedIn
Why working fewer hours would make us more productive
A shorter working week could improve our mental and physical health and even mitigate climate change, research shows
Opinion | You Don’t Need More Free Time (Published 2016)
Well, you might. But that’s not the real key to finding work-life balance.
Running A Software Business On 5 Hours A Week | Kalzumeus Software
Running A Software Business On 5 Hours A Week | Kalzumeus Software
You can code only 4 hours per day. Here’s why.
Most of us have felt it: after a few solid hours of coding, your brain starts shutting down.
How the Six-Hour Workday Actually Saves Money
A Swedish experiment may have missed the bigger picture of how shorter days can mean long-term profit.
Is full-time work bad for our brains?
If you’re over 40, working more than 25 hours a week could be affecting your intelligence, new research suggests
Opinion | 5-Hour Workdays? 4-Day Workweeks? Yes, Please (Published 2019)
Sick of round-the-clock work emails and Slack messages? Here’s some hope.
