Skip to content

A method for modern teamwork

Continuous Coordination is a lightweight methodology for teams that distills lessons learned from 50+ years running knowledge work teams into a set of concrete practices centered on two structured coordination loops – a big-picture loop to connect plans and progress, and a ground-level loop to keep teammates in sync.

The goal is simple; increase productivity & work quality by eliminating daily alignment-work drudgery and empowering teams with the context they need to work autonomously. Each practice is powerful individually, but together they’re a rigorous, field-tested plan for building high-performance teams.

Continuous Coordination Visualized

At its core, knowledge work is about making decisions — and making good decisions requires context. Not just the what of who’s doing what and where things stand, but the why that drives the work of individuals and the business as a whole.

The problem is that modern tools are great at breaking work down into small parts and producing metrics, but terrible at assembling context from all those parts. So contributors and managers spend their days in a constant scavenger hunt — piecing together updates from project management tools, chat threads, emails, wikis, and meetings to make the hundreds of daily decisions their jobs require. Worse, teams often arrive at different versions of context, driving expensive efforts in multiple directions.

The result: productivity down, work quality down, people burned out.

Continuous Coordination flips the script. The two coordination loops replace the scavenger hunt with a steady flow of shared context, keeping teams in sync day to day and the whole org aligned on what matters. The remaining practices are embedded in those loops — from communicating intent so people can work autonomously, to leading with context so decisions happen faster, to writing things down so knowledge persists and scales. We recommend reviewing them in order, starting with Keep a steady beat.

  1. 01: Keep a steady beat

    Ad-hoc approaches to keeping everyone aligned & informed are inefficient, inconsistent, and incomplete. Replace them with automated, structured coordination loops to create a steady beat that keeps everyone in sync without effort and interruptions.

  2. 02: Lead with context

    “Butts in seats” management is an engagement killer, and a non-starter when you can’t see actual butts in actual seats. Instead, give people the context and coaching they need to make independent decisions that move the business forward. High-autonomy teams are high-functioning teams.

  3. 03: Work in the open

    Working in the open builds trust, a prerequisite for high-performance teams. Working in the open turns bottom-to-top information funneling into autonomy-enabling information sharing. Working in the open keeps stakeholders and adjacent teams up to speed without asks and interruptions.

  4. 04: Tell the future

    You can learn from history, but you can change the future. That makes communicating intent across your org an actual superpower. When contributors do it, leaders can course-correct before days/weeks/months get burned. When leaders do it, contributors can drive progress autonomously.

  5. 05: Spare the meetings

    The answer to everything can’t be “have a meeting.” Zoom fatigue is real, and people need big blocks of time to do deep work. Save meetings for the high-value stuff — collaborating, team-building — and use async tools for the rest.

  6. 06: Write it down

    Writing helps you clarify your thoughts and ideas before you share them. Writing makes your thoughts and ideas digestible for others. Writing doesn’t require everyone showing up at the same time. Writing is accessible. Writing is searchable. If it “could have been an email”, by all means. Default to writing.

  7. 07: Track output, not input

    When it comes to knowledge work, real productivity isn’t measured by hours clocked, meetings attended, how long a lunch break was, or number of emails sent. Set clear goals, and focus on output and outcomes instead.