← SkillSafe
Operating Rhythm

Meetings make decisions or get cancelled

Operating RhythmEvery recurring meeting on one week: keep, tighten, redesign, make async or drop

List the meetings your company runs, or drop in a calendar export. The page puts them on one week, gives each a call from the five-level meeting architecture, finds the levels your headcount needs but lacks, and adds up the hours they take and the hours that come back. Free, in your browser.

Try a sample:

1 Your company and its meetings free

Drop a calendar export (.ics) or Recurring weekday events become rows. The file stays in your browser.

    2 The week, the calls and the hours free

    Not worked out

    keep tighten redesign make it async drop what the call cuts dashed: every two weeks, dotted: monthly

    MeetingNowCallAfterWhy

    Missing for this size

      Clashes in your week

        3 Write the fixes

        One run writes what to change in each meeting and a timed agenda for every meeting that still meets, proposes each missing level, and gives each slow decision a type, a decider and a speed. The calls, the hours and the verdict stay as the page worked them out.

        Pricing as soon as the session is ready...

        The fixes - none yet

        -

          First move

          Look again

          4 Saved rhythms

          How the page decides

          The levels your size needs. Under 30 people: weekly functional reviews and a weekly all-hands - you see everything, and you are the leadership. 30 to 100: all five levels - daily standups, weekly functional reviews, a weekly all-hands, leadership alignment every two weeks and quarterly planning. 100 and up: all five plus monthly skip-level reviews. A level is missing when no meeting at that level survives its call.

          The calls, first match wins. Drop: a standup or leadership meeting under 30 people, or a skip-level under 100. Make it async: it rarely decides and is mostly status. Redesign: it rarely decides, or decides only sometimes and is mostly status. Tighten: it runs past its level's length (standup 15 min, functional review 60, all-hands 60, leadership 90, quarterly 480, skip-level 60, any other 60), holds more people than its level's mark (standup 10, functional 10, leadership 10, skip-level 12, any other 8), has no named decider, or decides only sometimes. Keep: none of those.

          The hours. A meeting's person-hours a week are its length × how often it meets (every weekday 5, weekly 1, every two weeks 0.5, monthly 12/52, quarterly 4/52) × its people ÷ 60. After a call, a meeting that still meets runs at most its level's length with at most its level's people; one made async or dropped takes none. The difference is the hours that come back. Your hours count the meetings you tick as yours.

          The verdict, first match wins. Overloaded: you sit in more than 10 hours of these a week, or at least half the meetings are made async, redesigned or dropped. Needs work: any call other than keep, or a missing level. Sound: otherwise.

          Decisions. Type 1 decisions are hard to reverse and high stakes: a short written proposal, then one leadership meeting to decide, within 1-2 weeks. Type 2 decisions are easy to reverse: the owner decides the same day or the next, tells the people affected and adjusts.