๐Ÿ› ๏ธ Engineering managers

A meeting timer for engineering managers

Protect your team's deep work. HuddlePace keeps design reviews and post-mortems inside the time you set, and shows you how long your calls really take.

  • RFC and post-mortem splits
  • 30-day report
  • 0% audio recorded

RFC and design review

For a 30-minute review, run /pace and split the time into three modules.

15%4 min 30 s

Problem context

State the problem and its constraints so the proposal is judged against them.

50%15 min

Architecture proposal

Walk through the design. Half the time goes here because this is what the review is for.

35%10 min 30 s

Questions and objections

Collect objections while the design is fresh and decide which ones block approval.

Incident post-mortem

For a 40-minute post-mortem, the split shifts toward the root cause.

25%10 min

Incident timeline

Agree on what happened and when before anyone proposes a cause.

45%18 min

Root cause

The longest block, because root causes take the most discussion.

30%12 min

Prevention plan

Leave with an owner and a date for each change.

Why reviews overrun

1

Context eats the proposal

A long preamble leaves too little time for the part people came for.

2

Objections arrive in the last minute

Reserved time for questions makes them part of the plan.

3

The timeline turns into a root-cause debate

A separate timeline block keeps facts and theories apart.

4

Nobody can show what meetings cost

A 30-day report gives you numbers to bring to planning.

Run it in three steps

  1. 1

    Open the modal

    Type /pace in the channel where the review happens.

  2. 2

    Choose a split

    Pick the RFC or post-mortem split above, or enter your own. The modules must add up to 100.

  3. 3

    Save it as a template

    Tick Save as template and start the next review from it in one click.

What the team sees in the Huddle thread

  • Live progressThe bar updates every 30 seconds with the current block and the time left.
  • Private nudgesThe presenter gets a Slack DM at the midpoint and with one minute left.
  • Controls for speakersOnly designated speakers see the operational buttons. Everyone else can read the agenda.

See where the time goes

Run /pace report 30 to see timebox adherence and session logs for the last 30 days. It gives you data for a conversation about meeting load.

Before the call

Share the document first

When people have read the RFC beforehand, the context block can stay short.

Protect the questions block

If the proposal runs long, cut the walkthrough before you cut the objections.

Questions from engineering managers

Can I use a different split for each meeting type?

Yes. Save one template per meeting type, for example an RFC review and a post-mortem.

What does the report show?

Timebox adherence and session logs for the period you choose, 30 days by default.

Who can edit a scheduled session?

Only designated speakers, and only while the session has not started.

Does HuddlePace record audio?

No. It records 0% audio and stores no transcripts. It keeps only the timestamps and the agenda modules it needs to run the timer.

Keep your reviews inside their slot

Install HuddlePace, run /pace and save your RFC and post-mortem splits as templates.

Install to Slack

Early access, free today. Pricing will be per workspace, never per user, and the features available today stay free.