The Four Day Work Week Experiment
We're doing more by working less; series of thoughts on our four-day work-week experiment.
At Visionect, we initiated a four-day workweek trial in early March. Despite ample media attention, I aim to share our unique insights through a series of short blog posts, detailing my perspective, the team's involvement, and the impact on those not directly participating in the experiment.
Today is week 3 of the experiment and for the first post, I would like to mention some of the details of the teams involved.
Our experiment includes three types of teams:
a team of software engineers with well-defined lean processes, active kanban board, grooming sessions, regular retrospectives and a good history of lean metrics,
a team of software engineers that will switch to kanban within this experiment and
the department management with weekly goals and lots of meetings and ad-hoc/unplanned tasks.
We purposefully included teams with different focus and organization to see how they adapt their work with one day less inside the work week. They all work for our software engineering department, so they interact often and must have some shared processes.
This concludes the first blog post. Now that you know the team structure, I will share with you our first observations on the second blog post next week.