visibility and collaboration

Software engineering is collaborative whether I like it or not.

Take the classic split: I am on the backend, someone else is on the frontend. We can work in parallel, but only while each of us knows what the other is doing. The moment that breaks, we both slow down.

I have seen two ways of fixing it. Management enforces process: standups, syncs, status. Or the team builds a culture that does it without being asked. They look similar and they are not. Management wants visibility so it can check in. I want visibility so I can get the work done. In my experience only the second one survives a reorg.

How the good teams I have been on coordinate

The best teams I have worked on did not need a daily standup. People shared what they were doing continuously, in writing, somewhere the rest of us could find it later.

The trick, as far as I can tell, is this. Write like someone else will need to understand what you are building. From day one, not when it is finished.

What that looks like for me

• I open the pull request on day one. Empty is fine. Commit small and often, let CI run, link the ticket, paste the failing test, leave notes as I go
• I create the document on day one. Name it, share it, call it a draft. Wrong is fine, half-empty is fine
• I try to write continuously rather than write more. Clear and honest beats long

Collaboration was never about talking more, at least not for me. It is about making my work visible so other people can move with me, or around me, without having to ask first.

The teams I trust show it in visible work, not frequent meetings. I try to write like someone else depends on understanding what I am building. Usually they do.