Susan Schweitzer shared a grounded, real-world story of leading an organization into Flow — not just as a buzzword, but as a lived, evolving capability. The journey, captured through milestones and learning moments, sheds light on what truly makes Flow adoption stick.
Like many organizations, the team began with symptoms: missed commitments, unclear ownership, and siloed delivery. But rather than jumping into tools or frameworks, they took a more reflective approach — asking how work flowed, where it stalled, and what outcomes actually mattered to their customers.
Started with observation: They mapped current state workflows before proposing change.
Built a shared language: Teams across business and tech aligned on what “value” and “flow” meant in their context.
Tackled mindset first: Change management wasn’t an afterthought — it was the entry point.
Over-indexing on metrics without context
Failing to connect leadership vision with team-level execution
Underestimating the time required to shift cultural habits
But through retrospection and iteration, they managed to create momentum that outlasted individual projects. What started as a way to fix delivery became a platform for better decision-making and healthier teams.