The Human Cost of Mobbing All Day Work (Part 5)
10 min read
What Better Collaboration Looks Like in Practice
In the first two parts of this series, I argued that some collaboration models carry costs their advocates rarely name clearly enough. On the human side, continuous managed availability can create chronic vigilance, bodily constraint, public diminishment, flattened expertise, and a workday in which a person is never fully allowed to settle into the problem. On the business side, the same model can reduce deep-work capacity, increase transition cost, misallocate senior talent, create shallow understanding, inflate ceremony cost, and quietly lower the return an organization gets from expensive technical labor.
That would be enough reason to reject the worst versions of the model.
It is not enough on its own.
A useful critique should also help people build something better.
The challenge is that Part 3 can go wrong in two opposite directions. Lean too far toward profit and it starts sounding like polished extraction language with better manners. Lean too far toward dignity in the abstract and it risks sounding like soft, sentimental idealism that serious leaders can safely ignore.
The truth is harder and more useful than either extreme.
A healthy organization must be commercially viable. A company that cannot serve its clients, sustain revenue, or continue operating cannot keep any of its promises for very long. At the same time, an organization that pursues profit as though people were disposable units of labor will eventually damage the very conditions on which good work depends: retention, trust, candor, institutional memory, thoughtful judgment, and the willingness of strong people to keep investing themselves in the mission.
Those are not competing obligations. They are mutually constraining ones.
A business must serve its clients in order to remain viable. A business must also serve the people who are willing to invest their time, energy, judgment, and skill into that business.
The practical question is what that balance looks like.
The circle has to hold
The image that comes to mind for me is a group of people standing shoulder to shoulder in a circle, each person leaning back just enough to be supported by the person behind them while also supporting the person in front of them.
That arrangement works because support is mutual:
- no one in the circle is only serving
- no one in the circle is only being served
- no one gets to treat everyone else as though their purpose is simply to absorb weight.
A healthy organization works much the same way:
- leaders serve clients
- leaders also serve teams teams serve clients
- the organization serves the people whose labor and judgment sustain the work. Those people, in turn, invest their effort, insight, and skill back into the organization
When that reciprocity is present, the structure holds. When it is absent, the structure may still stand for a while, though it becomes brittle, fearful, and extractive.
This is why I resist the language that treats people as though they were merely resources to be consumed in the service of delivery. A team is not healthy when some people do all the bearing and others merely extract output from them. It is healthy when people are supported strongly enough that they can give their best, and when those who give are themselves held by the system they are helping to sustain.
That is not sentimental. It is one of the conditions of long-term organizational strength.
Values that are not operationalized are only slogans
It is easy for an organization to say that it respects people.
It is harder to design work in a way that proves it.
If respect and dignity are going to mean anything in an engineering organization, they have to show up in the operating model. They have to influence how teams collaborate, how help is requested, how meetings are run, how specialists are used, how interruptions are handled, how truth is surfaced, and how different working styles are treated.
Otherwise they remain slogans on a values page while the daily experience of work communicates something else entirely.
That is why the rest of this part is concrete.
Not because rituals are magic or because any one team practice will solve everything; rather, because values become real only when they begin shaping the way people actually work.
1. Separate deep work from collaborative work
A healthy team does not force every kind of work through the same social channel. Some work genuinely benefits from fast feedback, shared debugging, and spoken problem-solving. Other work depends on quiet, continuity, and enough uninterrupted time for a person to build and hold a complex mental model. When those two modes are collapsed into one environment, one of them usually gets sacrificed. In many organizations, it is deep work that loses.
That is why teams should design distinct pathways for distinct kinds of work. In one environment, the expectation can be collaborative energy, questions, escalation, and rapid unblocking. In another, the expectation can be sustained concentration and interruption discipline. The exact implementation can vary. It may be two rooms, two time blocks, two channels, or two clearly stated team norms. The important thing is the honesty: collaboration and concentration are both real forms of work, and they should not be forced to compete for oxygen in the same space all day long.
What this looks like in practice:
- Create a clearly designated collaboration space and a clearly designated focus space.
- In person, this may literally be two rooms. Remote, it may be one standing "loud room" and one quiet channel or protected focus block.
- State the expectation out loud: questions, escalation, and debugging belong in one mode; sustained concentration belongs in another.
- Make it normal to say, "Take that to the loud room," or, "Let's move this to the collaboration block," instead of letting every question become ambient interruption.
- Protect the quiet mode socially. Do not treat people in the focus space as publicly available by default.
This kind of separation does more than improve comfort. It improves signal. People know where to bring confusion. They know where to protect focus. They know that asking for help does not require puncturing everyone else's concentration, and they know that deep work is not a private preference they must defend alone. That is one of the clearest ways an organization can show that it understands the difference between visible participation and meaningful contribution.
2. Create bounded norms for escalation and help-seeking
Teams work better when people do not stay stuck too long in silence. Teams also work better when every small moment of friction does not immediately become somebody else's interruption. A mature collaboration culture needs a middle path between private spiraling and instant dependency.
That is why bounded escalation norms are so useful. In one environment I found especially effective, the expectation was that if someone had spent more than a few minutes trying to answer a question and was still blocked, they were expected to bring it to the group. The number itself matters less than the principle. People should wrestle with a problem long enough to form a real question, though not so long that confusion turns into waste, shame, or a half-day lost in the weeds.
This kind of norm helps in several ways at once. It prevents newer or quieter people from disappearing into unproductive struggle. It encourages people to make a real attempt before escalating. It raises the quality of questions because the person has usually already tried something. It also turns one person's obstacle into shared learning for others. Most importantly, it makes help-seeking intentional. The goal is not to make people tougher by leaving them alone, nor softer by encouraging instant rescue. The goal is to help people develop discernment about when to keep wrestling and when to ask for help in a way that strengthens the whole team.
What this looks like in practice:
- adopt a lightweight team norm such as, "If you are still blocked after a few focused minutes, raise it"
- teach people to escalate with context: "I tried A and B, I checked the logs, and I think the problem is in this area"
- make the norm a guideline, not a stopwatch. Some problems deserve longer solitary effort. Some should be raised sooner
- encourage questions to be brought where they can help more than one person when appropriate, not only to a single private rescuer
- normalize language like, "I'm productively stuck" or, "I've reached the point where this is now team learning, not just my struggle"
That is collaborative maturity. It also illustrates a broader principle: better collaboration is not the same as more constant collaboration. The goal is not permanent shared presence. The goal is timely access to the right kind of support.
3. Treat working styles as an operational reality
One of the more constructive responses I made to a painful collaboration environment was to give a company-wide talk on collaboration expectations, then help found a Working Styles Guild. We met regularly to discuss how people with different neurological profiles and working patterns could work more effectively together and with the organization.
I think more teams should do something like that.
The point is that working styles should be treated as an operational topic rather than as personality trivia or private sensitivity.
Different minds really do incur different costs in different environments.
Some people shift modes cheaply. Some do not. Some think out loud. Some think before they speak. Some gain energy from live collaboration. Some steadily deplete under it. Some are comfortable competing for airtime in large group settings. Some have valuable things to say and are far less likely to say them unless the structure makes room for them. Some need strong sensory control to work well. Some tolerate ambiguity more easily than others.
These are not minor biographical details. They are facts about how work happens.
Once leaders grasp that, a lot of pseudo-neutral practices start to look less neutral. A collaboration model that seems perfectly reasonable to one nervous system may be painfully expensive for another. A workplace that ignores that reality will not become more objective by ignoring it. It will simply privilege the people whose costs are less visible.
What this looks like in practice:
- hold explicit conversations about working styles, not only about tasks and deadlines.
- ask useful operational questions: How do you prefer to get interrupted? What helps you stay focused? What kind of meeting makes it easier for you to contribute? What makes it harder?
- create a recurring forum, guild, or retro theme where the team can discuss how collaboration is actually landing on different people
- treat findings from those conversations as inputs to process design, not as side commentary
- make room for more than one kind of useful contributor. Do not assume that the fastest talker, quickest interrupter, or most visibly energetic collaborator is the model everyone else should emulate
Treating working styles as an operational topic is one of the most practical forms of respect an engineering organization can embrace. It helps teams make better decisions about collaboration windows, escalation paths, communication norms, role design, and support for deep work. It also helps move the conversation away from defensive language about accommodation and toward the more useful language of effectiveness.