← Portfolio · ← Collaboration 2.0
2.5 · The adoption argument
Propose a transparency reform inside a low-trust organization and there is an obvious way to read it: management wants to watch us more closely. If that reading wins, the reform is dead no matter how well it is designed.
So the framework shipped with an argument attached, framed as a non-zero-sum game:
| What the organization gets | What the individual and the team get |
|---|---|
| Strategy alignment | More say in the work |
| Efficiency | Growth, and credit people can see |
| Long-term value | A better working day |
And three concrete “why should I like this” pillars, written from the reader’s side rather than the organization’s:
1 · Broaden our communications. One shared source of truth, so there is less to misunderstand. Clear roles, so planning gets better and each person is accountable because their work is visible, not because someone is supervising them. Less duplicated work. Less friction where teams hand work to each other, and faster handoffs.
2 · Utilise our intellectual assets. More people get to take part, so the organization reaches more ideas — and each person gets somewhere their competence can be seen. Bad decisions get caught in review. Motivation, creativity and confidence go up.
3 · Enhance strategic alignment and agility. Keep the roadmap where everyone can see it. Pass the organization’s vision, and what the stakeholders want, all the way down to the developers. The theory is stated openly: people who know why they are building something build it better.
The second pillar holds the real trade, and most reform proposals leave it unsaid. You accept that your contributions are visible. In exchange, your contributions become creditable.
Where credit was going to position rather than to work, that is a good trade for a strong engineer. And 4.1 names exactly who had to find it a good trade. The people with somewhere else to go are the ones for whom visible competence is worth something. They are also the first people you lose if the reform reads as supervision.
Where promotion comes into it. The framework never reassigned anybody’s role, and it was never meant to. What transparency creates is the condition under which a promotion becomes justifiable.
The precondition I asked of the sponsors was the reverse of what that sounds like. Team leads and coordinators had to be guaranteed that their own positions were secure. Someone who feels their position is threatened will work against the adoption, and no part of this design survives that.
Then let it run for a while — I was thinking of about a year. The knowledgeable people who had no channel start demonstrating what they can do, in public, on the shared platform. And a lead who holds the position without the competence underneath it becomes visible in the same way, because everyone can see the quality of the reasoning.
At that point a change in leadership stops being a political act. It becomes an obvious one, because the evidence is sitting in public view instead of behind a closed door.
That trade was also meant to become concrete rather than stay a promise. The longer plan was to bring performance evaluation itself onto the platform, so that visible contribution turned into scored contribution. 2.7 sets out what that would have looked like.
This argument was not built in a vacuum. I have never thought or analysed in empty space. I used to discuss my ideas with people across different teams and different levels of the organization, and that broad network — along with my multidisciplinary background — is one of the things that made Collaboration 2.0 possible. I was always collecting feedback from different people to refine and polish my thinking.
And the survey checked it. The instrument in 4.3 was written to look for exactly the surveillance reading this section is built against. It did not find it. One respondent named close monitoring as their biggest worry, and nobody feared documents being used against them. Three in ten named the extra workload instead (4.3). A sample this small cannot prove a fear absent. It can show that the instrument pointed at it and something else came back — and overhead needs a different answer than distrust does.
⟵ Up: Collaboration 2.0 · Previous: 2.4 · The collaborative authoring process · Next: 2.6 · Measurement, feedback and refinement →