I am co-founder of a 5 year old tech startup with 50 staff that introduced a 4dww / 32hr work week a little over 2 years ago.<p>Since are a lot of questions surrounding 4dww - Thought I might be able to offer some insights.<p>1. “four days but actually working longer” or “four days with reduced hours”.<p>-- We offer 32hrs work week, rather than the standard 40hrs in our home country. This is generally taken as 4 days, but some work 5 days with less ours (especially those with school aged children).<p>2. "What employers want to know is not what happens in poorly managed offices, but what happens in well managed offices where employee workload was already optimised."<p>-- I am going to be biased but we spent 3 year with standard work week, and I think we were highly productive as an organisation, our internal metrics, output and surveys agreed with this assessment. After 2 years, we haven't seen any noticeable / measurable decrease in output or performance compared to 5dww, or since we started.<p>3. "Do these companies close on a week day, like they just don’t open on a Monday."
-- We generally allow people to choose any day off they want, put have them put it in ~4 weeks before hand. Most people take either Monday or Friday, which means we always have some staff covering the days others have off. In smaller teams that speak with customers (sales/cs) they agree among the team who takes what days, and can trade, as long as we always have coverage.<p>4. "4 days week sounds great, if you hate your job and you already earn less than you deserve."
-- We pay top percentile as other startup/tech companies in our country's HQ. Anyone joining us shouldn't feel they are being paid any less than someone on 5dww -- and that is because we expect their output to match those of others working 5dww.<p>Overall we've found the move to be extremely successful at attracting and retaining talent with I believe helps us be significantly more productive than other startups I know doing 5dww.<p>We have a few things that I think help with our 4dww, include remote async with very flexible hours, hiring worldwide, transparent salaries and virtually no meetings in engineering.<p>One thing this flexibility allows us to do is ask our staff to be 'switched on' when they are working -- if for any reason they aren't being productive, we encourage them stop working, do something else, and come back later. We expect our staff aren't reading reddit, posting on hacker news, etc during work-time -- in return for the 32hrs we want to see it (almost) all productive.<p>I believe this, along with staff dropped the least important work gives us a similar/same output as 40hrs. With the benefit that we've been able to attract talent that otherwise may have gone elsewhere, with a turnover of virtually 0%.<p>Happy to answer any specifics about how we've implemented thing, or what I've seen as a co-founder leading a small (16 people) engineering team.