Teamwork & Cooperation

The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

What I’ve always felt that a team of people doing something they really believe in is like, is like when I was a young kid, there was a widowed man that lived up the street. He was in his 80’s, and a little scary looking, and I got to know him a little bit — I think he paid me to cut his lawn or something — and one day he told me, “come into my garage, I want to show you something.”

And he pulled out this dusty old rock tumbler. It was a motor and a coffee can and a band between them. And he said “come out here with me,” so we went out to the back and we got some rocks, just some regular old ugly rocks and we put them in the can with a little bit of liquid and a little bit of grit powder, and he turned the motor on and said “come back tomorrow,” as the tumbler was turning and making a racket.

So I came back the next day and what we took out were these amazingly beautiful and polished rocks. The same common stones that had gone in — through rubbing against each other, creating a little bit of friction, creating a little bit of noise — had come out as these beautiful polished rocks.

And that’s always been my metaphor for a team working really hard on something they’re passionate about. It’s that through the team, through that group of incredibly talented people bumping up against each other, having arguments, having fights sometimes, making some noise, and working together, they polish each other, and they polish their ideas. And what comes out are these really beautiful stones.

The innovative designer also likes, perhaps needs, to work with a small team of committed co-workers who share the same passions and dedication.

There is a legend at Cooper of one team who found pairing with each other so powerful and fruitful that when they left that company, they sought out opportunities and even interviewed at other organizations as a pair.

In hand and brain chess, each team has two players: a “brain” and a “hand.” At the beginning of each turn, the “brain” tells the “hand” which piece to move, and the “hand” then has to move that piece, but can move it wherever they think it should go. No other communication is allowed.

This was not meant to be like Bell Labs; there were no expectations that the clerical workers would run into their managers in a “serendipitous encounter” and produce a new innovation. The ideas was rather to create a workplace in which status barriers seemed to dissolve, in which participation and friendliness all around made the work environment look less like the white-collar factory it was.

The cubicle had the effect of putting people close enough to each other to create serious social annoyances, but dividing them so that they didn’t actually feel that they were working together. It had all the hazards of privacy and sociability but the benefits of neither. It got so bad that nobody wanted them taken away; even those three walls offered some kind of psychological home, a place one could call one’s own. All these factors could deepen the frenzied solitude of an office worker.

In an empowered product team, the product manager is explicitly responsible for ensuring value and viability; the designer is responsible for ensuring usability; and the tech lead is responsible for ensuring feasibility. The team does this by truly collaborating in an intense, give and take, in order to discover a solution that work for all of us.

However, in a feature team, you still (hopefully) have a designer to ensure usability, and you have engineers to ensure feasibility, but, and this is critical to understand: the value and business viability are the responsibility of the stakeholder or executive that requested the feature on the roadmap.

Systematic design excluding intuition yields pedestrian follow-ons and knock-offs; intuitive design without system yields flawed fancies. How to weld intuition and systematic approach? How to grow as a designer? How to function in a design team?

In Chicago, formal chains of influence and authority are entirely overshadowed by the ad hoc lines of control which arise naturally as each new city problem presents itself. These ad hoc lines depend on who is interested in the matter, who has what at stake, who has what favors to trade to whom.

This structure, which is informal, working within the framework of the first, is what really controls public action. It varies from week to week, even from hour to hour, as one problem replaces another. Nobody’s sphere of influence is entirely under the control of any one superior; each person is under different influences as the problems change. Although the organization chart in the Mayor’s office is a tree, the actual control and exercise of authority is semilattice-like.

When work isn't shared, the instruments of cooperation – listening, taking note, adjusting – atrophy like muscles that are no longer in use.

"Bob's rapport with the workers is extraordinary. Reminds me of something Noguchi once pointed out about Bernini during the days he was building St. Peter's in Rome: how what made him so special, aside from his own obvious gifts, was his ability to extend himself through the work of others, to get them on his side and working in his direction."