Cross-team work without a shared roadmap — note 138

I keep returning to a simple test: after a week of work on cross-team work without a shared roadmap — note 138, can someone outside the room explain what changed and who owns it?

The cheapest alignment tool is still a short doc with a decision and a date. Meetings are for conflict, not for status karaoke.

Cross-team collaboration fails when interfaces are social instead of technical: Slack threads instead of contracts, heroes instead of owners.

Cross-team collaboration gets easier when you publish interfaces: who consumes what, what “done” means, and how failures are communicated. Ambiguity is expensive; clarity is a kindness.

When two teams disagree, treat the disagreement as a design input. Resolve it in the interface, not in personality.

Write the boundary as if it were an API: inputs, outputs, latency expectations, and who gets paged.

In practice that means shorter cycles: decide, ship a thin slice, review what broke, coach the pattern into the next person. Long programs without those loops become status machines.

On cross-team work without a shared roadmap — note 138, the leadership move is to make the invisible visible: ownership, verification, and the path for the next person.

Mentorship scales when seniors narrate tradeoffs in writing. A one-paragraph decision record teaches more than a hallway conversation that evaporates.

I prefer written decisions over verbal ones. Memory is a poor archive, and AI tools make fluent improvisation cheap — which raises the value of durable context.

None of this requires a new framework brand. It requires attention, a short feedback loop, and the humility to change process when agents join the workflow.

Coaching is the mechanism. Process is the memory. Tools are leverage — only when ownership stays human.