|
To be clear (if you only read the headline :)), not entirely remote. Solo work at home, collaborative work in "studios", basically reimagining the offices into collaborative/convening spaces that you go into from ~once/week to once a quarter depending on team/role. Remote-only cuts out the in-person experience entirely, which is problematic for building teams and culture; and ad hoc "WFH whenever you feel like it" gets a sort of worst-of-both-worlds situation where you neither get the same kind of flexibility nor the sense of community you typically get from an office (since a large percentage of the team isn't there on any given day, and folks that come in the office less tend to be at a disadvantage in terms of visibility & recognition). |
I’m forgetting their name for them, but IBM has been doing this for decades now. They buy up office space in every major city, and then, rather than permanently stationing any teams there, essentially make all such spaces into private-access coworking spaces.
In these IBM offices, there’s cubicles, hot desks, and meeting rooms, all set up with runs of Intranet-accessible Ethernet + wi-fi + softphones; and you can either just drop in to work, or freely reserve any amount of these from the office’s concierge for days/weeks/months at a time — for yourself, or for your entire team, if you’ve brought your whole team with you to another city/country to do a high-touch customer deployment or something.
At least in the office I went to (Burnaby BC), it was almost entirely empty most of the time. So there was plenty of spare “capacity” in this network for any random need a team or individual might have.
It’s a very nice model. Slap an API on it and you could call it “elastic office-space IaaS.” :)