Pulse Meeting

What is a pulse meeting?

A pulse meeting is a short, frequent, and focused check-in to share status updates on a team or project. Most teams hold them daily or weekly. The format started in Agile and Scrum and is now used wherever teams need to stay aligned without long meetings.

The tone is informal. The aim is to give team members a place to raise blockers, share wins, and ask questions, while managers listen and respond.

How often should a pulse meeting happen?

Cadence depends on how fast work moves and how much coordination it needs:

• Daily (10–15 min): Engineering, support, and operations teams use a daily stand-up when work changes day-to-day.
• Weekly (20–30 min): Most cross-functional teams settle here. Long enough to surface issues, short enough not to consume the week.
• Bi-weekly: Suitable for stable teams where a daily or weekly cadence creates more noise than signal.
• Quarterly (extended): Some frameworks (notably EOS) add a quarterly "Meeting Pulse" of a half-day to revisit priorities.

The right cadence is the one that catches problems early without becoming meeting overload. Start more frequent and pull back if the value drops.

What is the agenda of a pulse meeting?

A workable pulse-meeting agenda is short and consistent. Each member answers the same three questions:

• What did I do since the last pulse? Quick summary of the work completed.
• What am I working on next? Stated as a near-term commitment, not a long list.
• What is blocking me? Issues that need help or a decision today.

Many teams also reserve a few minutes for one shared topic — a customer issue, a priority change, or a win worth recognising. Anything that needs more than a quick answer is taken offline.

What are the benefits of pulse meetings?

• Faster problem-solving: Blockers surface early instead of sitting unresolved for days.
• Stronger alignment: Everyone hears the same updates at the same time.
• Built-in accountability: Saying out loud what you will do tomorrow tends to make it happen.
• Fewer side-channel pings: Status questions land in one forum rather than 14 individual messages.
• Better visibility for managers: A weekly read on what is actually happening, not a curated monthly update.
• Early signs of burnout: Patterns in updates — repeated blockers, missed commitments — surface stress before it becomes a crisis.

What are the disadvantages of pulse meetings?

• Meeting fatigue: Daily check-ins can feel like a tax when work has not changed.
• Surface-level updates: The format favours short, breadth-first updates and discourages depth.
• Wrong fit for some work: Deep individual work or research-heavy roles often do not benefit from a daily cadence.
• Time-zone strain: Distributed teams may need async written pulses rather than synchronous calls.
• Performance theatre: When the meeting becomes a performance for the manager, the honest signal disappears.

What is an HR pulse meeting?

An HR pulse meeting is a short, regular check-in HR runs to get a real-time read on how employees are doing — different from a project pulse meeting, which tracks task status. The focus is people signals: engagement, workload, retention risk, policy questions, and how a recent change is landing.

HR pulse meetings are typically weekly or fortnightly, often paired with quick pulse surveys (5–10 questions sent the same day). The combination gives HR both a qualitative and a quantitative read on what is happening across the company.

How do you run an effective pulse meeting?

• Hard-cap the time: 15 minutes for a daily stand-up. 30 minutes for a weekly. If the meeting runs over, the format is wrong.
• Same agenda every time: Predictability is what makes the meeting short. Pulse meetings are not the place to invent a new structure each week.
• Stand up if possible: The "stand-up" name comes from the practice — physical discomfort shortens the meeting.
• Take detail offline: Anything that turns into a two-person discussion gets a follow-up. The meeting is not the resolution forum.
• Rotate facilitation: Different people running the meeting prevents it from becoming a manager monologue.
• Cancel when it stops working: If updates are stale and no blockers come up for a month, the cadence is wrong. Adjust rather than continue out of habit.