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



Many people think because we’re an online business, with technology at the heart of everything we do, we’d be better placed than many to make the transition from in-person meetings to virtual meetings during the pandemic. Whilst we have made that leap and made it work well, it’s not because we’re au fait with tech and the latest tools, it’s quite the opposite. For me, it’s all been about forgetting tools and technology, and instead thinking about people and their needs.
The key is to stop thinking about it being a remote meeting; think about what things made meetings work when we were all in the office and try to implement them. I’m going to walk you through the best ways to create more efficient and effective remote meetings, whether they’re on Zoom, Slack, Teams, or by a simple old-school phone call, so you can get the most out of your time.
We know that good mental health and support were vital during 2020 and with lockdowns in the UK and much of Europe still in place, we need a renewed effort on the mental health front for 2021.
Routine and structure are important, so our stand-ups happen each morning at the same time, and just as we would in the office, we make everyone stand-up and have their videos on. I’ve heard in many companies meetings are simply audio, but with this, you lose that important interaction of seeing other people’s expressions, of getting visual cues and feedback, of knowing people are listening to you which are all vitally important.
In terms of managing time, we review every 3 months or so whether the regular meetings we have are still needed. Are they effective? Do they have a goal? Who should be at that meeting? We all want to avoid Death by Zoom – so no meetings should be put in the diary for the sake of it, or where they simply repeat other calls.
So once you’ve decided a regular meeting is needed, as in real life, make sure everyone gets there on time. It’s important the etiquette that we have in real life is felt in remote meetings as well; the meeting should always start on time. So that means if someone is late, they’ll arrive with everyone having started. This tends to be more effective in stopping repeated lateness as it’s embarrassing to arrive when everyone has started, more than it is if your colleagues are simply waiting for you.
Starting our meetings at odd times – e.g. 9.57am seems to be a really effective way of getting people to meetings on time. For whatever reason, it’s far better than 10am or say 10.15am!
For regular stand-up meetings, we manage time by keeping it to 15 minutes only. We change the leader of the meeting each time, and the person talking then passes the baton to the next person. Having the baton pass rather than sticking to the same order each time, encourages everyone to listen to each other rather than simply waiting for their turn. To keep the meeting effective we limit everyone to 1-2 minutes only, and everyone knows that they have to address the 3 questions – in a stand-up for example:
As well as clear questions we also have a system whereby we challenge anyone, including management, if they go off on what I call storytelling or problem-solving. If a 2nd person agrees then we move on. It’s also important in this way to quickly decide when something is off-topic or needs taking into another meeting. It’s the same should you wish to communicate a crisis during a stand-up, this might not need the whole team or department’s input so you should decide if this would be better placed in a different meeting.
In terms of ad hoc meetings these have to meet the same tests:
I hope these top tips for remote work meetings help you to become a more efficient and collaborative team! Remember to always plan ahead of meetings, have any data or reports you need to hand, remain enthusiastic and engaged and always create an environment where everyone feels able to voice their opinions, concerns, or ideas!
Share this
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
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.
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
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,
5 min read In a recent post, I argued that AI doesn’t fix weak engineering processes; rather it amplifies them. Strong review practices, clear ownership, and solid fundamentals still matter just as much when code is AI-assisted as when it’s not. That post sparked a follow-up question in the comments that’s worth sitting with: With AI speeding things
4 min read Why strong reviews, accountability, and monitoring matter more in an AI-assisted world Artificial intelligence has become the latest fault line in software development. For some teams, it’s an obvious productivity multiplier. For others, it’s viewed with suspicion. A source of low-quality code, unreviewable pull requests, and latent production risk. One concern we hear frequently goes
Find out everything you need to know in our new uptime monitoring whitepaper 2021