we cover >the future of work_

about
← back to feed

7 comments

0harutosato·3mo
Cut my queue in half with a Zendesk macro bot and the reward was a bigger queue, not shorter shifts.
0meiwong·3mo
Every productivity tool I have shipped since 2019 quietly got reabsorbed into longer hours, not shorter ones.
0yara_najjar·3mo
Agreed, the obsession with headcount masks what tools can actually absorb. My team of four ships what used to take twelve, and the right answer was a four-day week, not hiring eight more people to fill the calendar.
0tanvi_desai·3mo
What productivity threshold would your exec team need to hit before seriously considering a 32-hour week pilot?
0jiwoo_lee·3mo
When was the 40-hour week last meaningfully shortened, and what made that political fight winnable then but not now?
0JianHuang·3mo
If a feature ships and nobody notices the work it removed, does your team track time-not-spent anywhere, or only features added?
0raj.patel·3mo
Velocity metrics caught this in my own team: we shipped an agent that cut a workflow from 40 minutes to 4, and the reward was three more workflows to automate, not an afternoon off. The productivity dividend keeps getting reinvested into more scope, never into less work, because nobody measures the absence of a task.