I feel like it's worth pointing out that Steve Jobs was still running Apple when this building was designed. I don't work for Norman Foster so I have no way to know how much changed internally after he died, but I doubt the balance shifted too wildly given the logistical constraints of massive construction projects.
As an aside - and I don't mean this in reference to office layouts - were I in charge of a global consumer products company that competes in multiple cutthroat markets, I'd want to foster a corporate culture of extreme openness and collaboration inside the walls but absolute silence outside. That's not exactly what Apple is today, obviously, but it's within the realm of possibility that it's their goal.
> According to Jobs’ recent biography, the [Pixar] headquarters was to be a place that “promoted encounters and unplanned collaborations.”
> Pixar’s campus design originally separated different employee disciplines into different buildings – one for computer scientists, another for animators, and a third building for everybody else. But because Jobs was fanatic about these unplanned collaborations, he envisioned a campus where these encounters could take place, and his design included a great atrium space that acts as a central hub for the campus.
> Brad Bird, director of The Incredible and Ratatouille, said of the space, “The atrium initially might seem like a waste of space…But Steve realized that when people run into each other, when they make eye contact, things happen.”
> And did it work? “Steve’s theory worked from day one,” said John Lasseter, Pixar’s chief creative officer “…I’ve never seen a building that promoted collaboration and creativity as well as this one.”
https://officesnapshots.com/2012/07/16/pixar-headquarters-an...
Perhaps it spurs creativity and innovation, but only few programming activities are highly creative and innovative. Rather to me, programming is about writing bug-free code. In this sense, I tend to compare programming activities with Air Traffic Control.
In my past jobs working on tools and infrastructure, the best results usually come from sitting next to the people who use the tools or at least watching them use them. The traditional model used by the teams I've helped typically was partitioned off and people tossed things over the wall, but I always got significantly improved results by actually collaborating with the users.
You can compare programming with Air Traffic Control but in that case you need to realize that ATCs are in constant communication with their customers (i.e. pilots) in order to deliver the best results for passengers. If ATCs behaved like programmers in monolithic organizations they'd simply issue flight plans without talking to pilots at all and they'd be ill-equipped to respond to emergencies and sudden changes in flight situations.
For these really hard problems, long hours of completely undisturbed concentrated working are the key to success.
Strong collaboration ("bumping into each others") is rather helpful if the "problem" is not that the problem is hard, but it is unclear what problem is even to solve, e.g. you don't know what the customer wants.
Addendum: My comparison with ATC is rather meant the way that it is of central importance to avoid mistakes (bugs in software, plane crashing in ATC) and the work environment should be centrally concern itself around this theme.
Open space offices are entirely othogonal to this idea.
So we'd need more information to know whether or not Apple is best optimized in all these, and more, dimensions. Way more information than we'd ever get from one person or team. (Definitely way more than Apple would ever give out.)
As long as your group makes a conscious effort to bounce ideas around and ask each other for advice, what's the difference between sitting at a table wearing headphones or in an office with the door shut? Or, for that matter, everyone being remote?
I can kind of see how you could make a case that open-plan offices change the dynamic of communication, i.e. they make people less willing to "bother" their coworkers, but collaboration can (and probably should, most of the time) happen asynchronously over slack or email or post-it note anyway.
Aspiration driven design it is so ...
EDIT ... with no consideration for the practicalities of what it takes to achieve those aspirations.
SJ was hard and had a lot of stupid ideas, but he also made sure to hire people that knew when to fight him on that. And I think keyboardgate would have been addressed earlier if he had been around.
> “Many employees don’t like Apple Park [the company’s new headquarters] because it has very few private offices.
... nice one Jony ... design a brave and “beautiful” open plan workspace for a paranoiacally secretive organisation.
Says it all really.