The Problem
When I walked in, everyone was certain they were right. And they were.
The tech team knew what happened when the website went down. It landed on them. So they protected what they could control. The marketing team knew what every day of delay cost the business. So they pushed. Two teams. Both right. Both stuck. You could see it in every standup and every launch review: the same argument with new dates.
What I found wasn't a personality clash. It was Agile — or rather, the way Agile was being used. The tech team had figured out, intentionally or not, that if nobody could see the work or how long it took, nobody could challenge the priorities. Their board was always "in progress," their estimates always "fluid," their updates wrapped in jargon.
That's when I got excited. This was the mechanism.
So we built systems that made the work visible. Not to expose anyone — to give everyone solid ground. When the priorities were transparent, the fights stopped making sense. When the timeline was visible, the urgency became shared.
When the system works, so do the people.