Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021
“Let’s get a meeting in the calendar.”
What’s the obsession with meetings? I’ve never understood this or been a fan of meetings. My experience, and it’s not just at large corporates, is that they’re called without a clear agenda, too many people pulled into them – with the approach of let’s just block out an hour or more; “just in case”, rather than a fixed twenty minutes that focuses the mind and the need to reach an outcome.
If you need a whole room of people there; if the agenda is not set and unfocused, or if you need several hours to go through everything, then you’re using the wrong tool for the job. It’s not a meeting you need at that point in time.
Meetings should be focused on two or three points only. They should be no longer than 20 minutes. Any longer than this and not only does attention start to wander – phones get picked up and emails start getting replied to – but beyond this point conversations tend to become circular. It becomes a zero sum game.
At StatusCake we do things differently. Just as product and features are developed in an agile environment, we like to think on our feet when it comes to meetings. A meeting is that final stage where quick and fast decisions need to be made. And because we never sit still in anything we do, meetings are on the go with a brisk 10-15 minute walk. By the time we get back to HQ a decision has been made. No one sits back down at their desk without those points having been resolved resolved.
The walking meeting is important. It not only gets everyone away from their computers (phones are left back at base!), but taking ourselves out of the office environment, you’ll find that without email, PowerPoint or other crutches, everyone needs to be pretty sharp in what they’re saying. There is no fancy slide-deck or pivot-table to hide behind. Everything is more human, more real, more honest. After all if you can’t explain what the issue is without prompts or aids you really don’t understand the issue well enough yourself yet alone be able to explain to anyone else.
But before a meeting becomes a good walk spoiled, stop. Think. Do you even need a meeting in the first place?
James Barnes
Co-Founder StatusCake.com – Uptime Monitoring
P.S. – As a bonus you’ll get fit & stay focused this way as well!
James Barnes
Share this
More from StatusCake
Alerting Is a Socio-Technical System
3 min read In the previous posts, we’ve looked at how alert noise emerges from design decisions, why notification lists fail to create accountability, and why alerts only work when they’re designed around a clear outcome. Taken together, these ideas point to a broader conclusion. That alerting is not just a technical system, it’s a socio-technical one. Alerting
James Barnes
February 25, 2026
Designing Alerts for Action
3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams
James Barnes
February 18, 2026
A Notification List Is Not a Team
3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years
James Barnes
February 11, 2026
Alert Noise Isn’t an Accident — It’s a Design Decision
3 min read In a previous post, The Incident Checklist: Reducing Cognitive Load When It Matters Most, we explored how incidents stop being purely technical problems and become human ones. These are moments where decision-making under pressure and cognitive load matter more than perfect root cause analysis. When systems don’t support people clearly in those moments, teams compensate.
James Barnes
February 4, 2026
The Incident Checklist: Reducing Cognitive Load When It Matters Most
4 min read In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already
James Barnes
January 28, 2026
When Things Go Wrong, Systems Should Help Humans — Not Fight Them
3 min read In the previous post, we explored how AI accelerates delivery and compresses the time between change and user impact. As velocity increases, knowing that something has gone wrong before users do becomes a critical capability. But detection is only the beginning. Once alerts fire and dashboards light up, humans still have to interpret what’s happening,
James Barnes
January 21, 2026