I recently found out that iProfesional.com mentioned BlackBox Vision in an article about the four-day work week in Argentina. It caught me off guard — not because the topic is new to us, but because it reminded me how much has changed since we first made that call back in 2021.
If I'm not mistaken, we were one of the first companies in the country to actually implement it. Not as a PR move, not as a "trial period with an asterisk." We committed to it, ran it for a meaningful stretch, and learned a lot in the process — some of it good, some of it complicated.
This post is an honest look at what that experience taught us, where the broader conversation has gone since then, and why I think AI is about to make this debate irrelevant in ways most people aren't expecting.
Why we decided to try it
In 2021, the four-day work week was gaining traction globally. Companies in New Zealand, Iceland, and the UK were running pilots and publishing encouraging results. In Argentina, there was even discussion around a potential bill to reduce the standard work week.
At BlackBox Vision, we'd always been deliberate about how we think about work. We're a product studio — our output is measured in quality of thinking and execution, not hours logged. The idea that compressing the week could sharpen focus and reduce burnout wasn't just appealing in theory. It aligned with how we already believed knowledge work should function.
So we went for it. No half measures. We restructured schedules, set clear expectations with clients, and gave the team Fridays off.
What actually worked
Focus and energy improved noticeably
When people know they have four days instead of five, they naturally prioritize differently. Meetings got shorter. Low-value tasks got questioned. There was a tangible shift in how the team approached their work — less drift, more intention.
Retention and morale went up
This one is hard to quantify precisely, but it was real. People were genuinely happier. The extra day off gave them space to recover, pursue personal projects, or simply rest. In a market where developer talent is fiercely competitive, that mattered.
It forced us to get better at async communication
With one less day of overlap, we had to get more disciplined about how we communicated. Documentation improved. Handoffs got cleaner. Slack messages became more purposeful. These were improvements that outlasted the experiment itself.
What didn't work as well
Client expectations didn't always align
Not every client was comfortable with the arrangement. Some understood and supported it. Others — particularly those in more traditional industries or different time zones — found it harder to adapt. Managing that tension required constant communication and occasional compromises.
Not every role benefited equally
For engineers deep in focused work, the compressed week was a gift. For people in client-facing or coordination-heavy roles, it sometimes meant cramming five days of interaction into four. The pressure didn't disappear — it just got redistributed.
The "gray areas" were real
Life isn't binary, and neither was this experiment. Some weeks, the reduced schedule worked beautifully. Other weeks, deadlines or urgent issues meant people were quietly working on Fridays anyway. We tried to be honest about that rather than pretending everything was perfect.
Did the four-day work week fail?
No. But it wasn't a silver bullet either.
What it did was force us to confront fundamental questions about how we work: What actually creates value? How much of our time is spent on things that feel productive but aren't? What does sustainable performance look like for a team of knowledge workers?
Those questions turned out to be more valuable than the policy itself.
What happened to the movement in Argentina?
The proposed legislation to reduce the standard work week didn't move forward. But the conversation it sparked was meaningful. Several companies and NGOs continued pushing for reduced hours on their own terms — running experiments, developing new frameworks, and sharing data.
It stopped being a trend and became a real area of inquiry. That's a healthier place for it to be.
How does AI change this conversation?
Here's where things get interesting. When we ran our experiment in 2021, the productivity gains came entirely from behavioral changes — better prioritization, fewer meetings, sharper communication. The tools themselves hadn't changed.
Now they have. Dramatically.
AI is already compressing the time it takes to perform tasks that used to consume significant portions of the work week: drafting documents, reviewing code, synthesizing research, triaging support requests, generating reports. These aren't hypothetical future capabilities — they're happening right now, in real teams, at real companies.
Bill Gates recently suggested that if AI continues advancing at its current pace, the standard work week could shrink to two or three days. That's a bold prediction, but the underlying logic is sound: if AI can handle the work that doesn't require uniquely human judgment — but is still necessary for organizations to function — then the math on how many hours humans need to work changes fundamentally.
What does this mean for companies today?
It means the four-day work week debate is likely a transitional conversation. The real question isn't whether we should work four days or five — it's how we redesign work itself around a world where AI handles an increasing share of routine cognitive labor.
Companies that start thinking about this now — experimenting with AI-augmented workflows, redefining what "productive time" means, measuring output rather than hours — will be better positioned than those who wait for legislation or industry consensus to tell them what to do.
Practical advice for companies considering it
If you're thinking about testing a reduced work week, here's what we'd suggest based on our experience:
Start with an honest assessment
Look at how your team actually spends their time. If a significant portion goes to low-value meetings, context switching, or bureaucratic overhead, a compressed week might force the discipline to fix that. If your team is already stretched thin, compression will just increase pressure.
Set clear boundaries with clients
Don't spring it on them. Explain the reasoning, set expectations about availability, and over-communicate during the transition. The companies that struggle with this are usually the ones that treat it as an internal policy change rather than a partnership conversation.
Measure what matters
Track output quality, not hours. Look at delivery timelines, client satisfaction, team wellbeing, and retention. If you're only measuring whether people are "online," you're missing the point entirely.
Be honest about the gray areas
Some weeks will be harder than others. Some roles will benefit more than others. Acknowledge that openly rather than pretending the policy works equally well for everyone in every situation.
Consider AI as an accelerator
If you're implementing a four-day week in 2026, pair it with an intentional AI adoption strategy. Use the reduced schedule as motivation to identify and automate low-value tasks. The combination of compressed time and better tools is more powerful than either one alone.
The bigger picture
Looking back five years later, I don't think the most important thing we did was implement a four-day work week. The most important thing was that we were willing to question the default assumptions about how work should be structured.
That willingness to experiment — to try something, learn from it honestly, and adapt — is what defines companies that stay relevant. Whether the future of work is four days, three days, or something we haven't imagined yet, the companies that will thrive are the ones that keep asking the right questions.
The four-day work week was one answer. AI is opening up entirely new ones. The only mistake is refusing to explore them.
