Turning around a firefighting team doesn't happen in Trello.
The ping lands at 6:47 p.m. It says it's urgent. There's no context, no decision, no plan, just the word.
Teams with low operational maturity wear people out in a particular way. Volume is part of it, and so is the sense that nothing fits together: a lot of effort, little predictability. Status stays green until the day it blows up, and the surprise is genuine because nobody had the data to see it coming. Decisions get made at 6:47 p.m. because nobody made them earlier.
The turnaround happens on more than one front.
The visible front: what has to change day to day
Process the team can run on a hard day. Documentation that gets used because it was designed to be useful, rather than to protect someone in a postmortem. Rituals that cut noise instead of adding ceremony.
On a team I joined midstream, the documentation was a folder of 47 files with names like Versão_final_agora_vai_3 (Portuguese for "final_version_for_real_this_time_3"). The team was disorganized for a reason that had nothing to do with habit: nobody had designed a simple structure covering what needs to exist, where it lives, who updates it, when, and why. Without a clear path, everyone improvises. Improvisation at scale becomes a method, only a bad one.
Real accountability takes a name, a boundary, and the authority to decide. The abstract version, "everyone is an owner," doesn't amount to it. When those three are missing, what looks like collaboration turns out to be distributed paralysis: everyone does the work, and no one answers for it.
The less obvious front: managing the transformation as a project
This is where most attempts fail, and the reason is simple: team transformation doesn't get the rigor that any delivery project gets.
A team improves for two or three weeks. Then a critical delivery comes up, the sponsor gets anxious, and someone asks for an exception just this once. The team falls back into firefighting mode. The relapse came from the transformation being treated as a good intention instead of being managed, rather than from weakness.
Transformation without management is an intention. With management, it stands a chance of becoming structure. That means a change plan with defined stages, an improvement cadence separate from the delivery cadence, and team development treated as a deliverable, with a deadline, tracking, and course correction when it drifts. The environment will always pull toward the shortcut. The job of whoever leads the change is to uphold the standard when that's hard, not when it's convenient.
Every just-this-once exception teaches the team that the old system is still the real one.
What the turnaround looks like from the inside
It arrives without a big announcement, and without a single week when everything changes.
There are fewer surprises, and more clarity about what's going on. Status that's accurate before it's presented in a meeting. Risk raised early, while there's still room to act. The person who would have sent the ping at 6:47 p.m. sent it at 2:30 p.m., with a question instead of an emergency.
Recurring heroics are a sign that the system needs work. They don't add up to a culture.