Skip to content
hum

customersTidepool · 140 people, 62 engineers

We cancelled theMonday sync.

140 people building water sensors for city harbours replaced a 40-minute meeting with a 30-second read, and halved the pings each engineer gets.

Monday sync, gone
0 min
Fewer pings per engineer
0%
Alert to the right person
0 min
P
Priya RamanVP Engineering, Tidepool

“We used to start every Monday with a 40-minute sync. Now we read the catch-up over coffee and save the call for the one thing that needs it.”

Sixty engineers, three time zones, one Monday meeting

Tidepool's sensors sit in eleven harbours, from Rotterdam to Halifax. The firmware, cloud and app teams ship every week, and until this year every week started the same way: 62 engineers on a call at 9:00 Rotterdam time, which is 4:00 in Halifax, going team by team through what changed.

“The meeting existed because nobody could read the backlog,” says Priya Raman, who runs engineering. “Our old chat tool had 300 channels. People muted most of them and then asked in the meeting.”

What changed

  • One channel per release, archived when it ships. #launch-4-12 holds every decision for that week, threads hold the arguments.
  • Forge and Shipyard post where it matters: merges in the release channel, failing checks in #eng-alerts, review requests in the reviewer's DMs.
  • Beacon opens a room per incident and pages the person on call. The rest of the team hears about it when it's mitigated.
  • Catch-up replaced the meeting. Each engineer reads a summary of their channels on Monday morning, with links to the five messages that matter.

Can we skip the sync today? I've read the catch-up.

Same. Only open question is the Halifax firmware rollout.

Huddle at 9:30 for that, just the three of us?

#eng-leads, the Monday the sync was cancelled for good

Incidents, without the 2 a.m. group chat

Before Hum, an alert at night went to a channel with 40 people in it. Whoever was awake answered. Now Beacon pages the on-call engineer in a DM that gets through quiet hours, opens #inc-412 with the owners of the service, and keeps the timeline. The postmortem starts from that timeline and the huddle notes, not from memory.

“The first time the postmortem draft was already written when I woke up, I thought someone had stayed up all night. It was the huddle notes.”

Malik Haddad, Staff Engineer, Tidepool

Six months in

The Monday sync is gone. Status meetings across engineering went from 6.5 to 2 hours a week, and each engineer gets 58% fewer notifications. Tidepool now runs its weekly release review as a thread, and only calls a huddle when the thread passes twenty replies.

A week at Tidepool

  • Status meetings2.0 h

  • Notifications per engineer, per day40

  • Channels with a bot nobody reads2

  • Hours to the first incident update0.1 h

Run your team like Tidepool.

Bring the team, connect your tools, and let Hum keep everyone in the loop. Free for teams up to 10.