Pod Insights The Agile Daily Standup - AgileDad Make Remote Work More Human - The Meetings About this episode Make Remote Work More Human - The Meetings For what it’s worth, I don’t think that remote work sucks. I think remote work is great. I am a fan. Please, never make me go back to an office. But yeah, Westenberg has a point — the way we design for remote work often forgets that we are human people with bodies and brains and not just work-input-cogs. We work on machines; we are not the machines. How to connect with AgileDad: - [website] https://www.agiledad.com/ - [instagram] https://www.instagram.com/agile_coach/ - [facebook] https://www.facebook.com/RealAgileDad/ - [Linkedin] https://www.linkedin.com/in/leehenson/
Transcript 0:16 Speaker 00 Let's talk for a moment about remote work. It's become part of our everyday lives, but I've often said in my trainings that we need to use a more pragmatic, humanized approach, a psychology-driven approach to making work more sustainable. Someone brought to my attention an article that came out about making remote work more human, and I thought we'd take a look at it and see where it takes us. It appears to have some good insights, so let's get started. Last week, I read a story from tech writer J.A. Westenberg called "Modern Work Sucks." There's another word there, I'm not going to read, but it describes a nightmarish state of remote work: waking up to Slack notifications, jumping back and forth between 20 different
0:59 Speaker 00 systems, and inexhaustible onslaught of Zoom meetings. This sounds like a day in the life of most people who are working in a hybrid environment right now. At least, that's what I see, right? When I go in and I coach teams, I'm taking a look at how they're behaving and what's happening, and some of the, how shall I say it, waste, if you will, is coming from too many meetings, from drudgery of feeling like you have to be involved in so many different things. And what we're seeing is a rejuvenation period where people are literally taking a chance to breathe working from home and going and doing things, which is breaking their work up, which is making it take longer. It's an endless loop, it's a cycle, right? And I'm not seeing people break that cycle.
1:42 Speaker 00 As someone who thinks a lot about work culture, the story felt like a rallying cry, a tidy articulation of what not to do. How do we create something that feels the opposite of this? That's a good question. For what it's worth, I don't think that remote work in and of itself sucks. I don't think it's a bad thing. I think remote work is great. I'm a fan for the most part, as long as people have the right balance. Sometimes people say, please don't make me go back to the office. But there's a point. There's a point we need to talk about here. The way we design for remote work often forgets that we're human people
2:26 Speaker 00 and that we have human bodies and brains and not just work input cogs and output cogs. We work on machines, but we're not machines. And I think sometimes that gets over understated. So sometimes when I think about my job as an agile coach, I often think to myself, how can we make this a humans first approach? How can we humanize what we're trying to do? And even though there's so many workplaces in the world that are offering remote opportunities, there's no single playbook to follow on how to do remote work successfully. Nobody's come up with a playbook. I mean, I've come up with a really good Scrum Master and Product Owner playbook, but there's no clear remote work playbook. What works for one company isn't going to work for another company.
3:11 Speaker 00 What we experiment with, some's going to fail and some's going to succeed. And we have to take that in. We just have to acknowledge and live with that reality. We try new things, we gather feedback, we pivot or adjust. And I think that we can all come to terms when we find something good that we can do together. But the big crux of what I've been thinking about with regards to hybrid and remote environments is meetings. Meetings are the number one complaint. The number one complaint of agile teams that are working remotely is too many meetings, closely followed by an inability to decompose work in such a way that it's easy to consume and provides value. Right? Those two run neck and neck and flip flop between number one and number two.
3:54 Speaker 00 So for the past year or two, or I should say longer than that, ever since COVID, actually, I've been trying to find different techniques or different ways to make work more human, to change the way we do meetings. And one of those rules right away, right out of the bat, is a rule regarding chat.
4:14 Speaker 00 So chat is an incredible function if you're doing an all-day workshop or a training seminar. But if you're doing just an online work meeting, you should have a no-chat rule. If you're in a Zoom meeting, you're trying to pay attention and it's just side chatter, just going on in chat. Right? It's so distracting. It's the same as Slack or Teams, right? As soon as there are comments in the chat, or worse, full-on conversations, I've seen that happen too, the attention becomes split between both things. So now you're trying to pay attention to the chat, you're trying to pay attention to what's going on, and you just can't do this. It's just, we struggle. We struggle with attention disorder just trying to keep up with what's going on
4:57 Speaker 00 in one place, much less in multiple places. So when you start dividing what's happening, you're losing out on inclusivity, you're losing out on... You're creating bias. So for small-team meetings, we should always say, "No-chat rule." No one has a lot of the posts in the chat, maybe for sharing a link to a doc or something like that perhaps. But if you have something to say, say it in a meeting. This doesn't need to be a rule for every meeting, like an all-hands-company meeting. But, you know, the side chat in those types of meetings is a fun way to keep people engaged. But for the right-sized meeting and purpose, we shouldn't be leveraging the chat to do those things. We should be just speaking what we have to say.
5:42 Speaker 00 Okay, here we go. Sticking with that, just close your Slack. If you're in a meeting, close your Slack. There's a book called 4,000 Weeks. It's a time-management book. It's kind of an anti-productivity culture while also being very much a productivity book. In the book, Burtman, the author, explains that the reason we drift into distraction, say, checking your Slack DMs while you're in a Zoom meeting, is not because you're bored. It's because paying attention is hard.
6:14 Speaker 00 It's just that distraction is easy. Paying attention is our distraction is easy. So the cognitive work of actually thinking deeply or better actively listening is harder than scanning your email or applying to a Slack thread. Those things are easy. Your impulse to keep tabs on Slack isn't productivity or boredom driven. It's your brain's way of saying, please don't make me work this hard. Please just let me do the easy thing. Let me do the thing that's coming right to me. So in a recent team retrospective that I facilitated, I asked everyone right away to do one favor for me to please close Slack all the way. Take off your Apple watch. Turn your phone upside down. Whatever other ways notifications are going to reach you.
6:58 Speaker 00 Don't let it creep into your space. And that meeting that was scheduled for an hour ended up taking about 35 minutes and it was way more productive than any other meeting we've ever had. What I'm trying to say here is we can pivot and adjust. We can change the way we do things. We just need to make minor modifications. Right? Okay. So how about this one? I wanted to set aside and reserve certain mornings where there were no meetings. And I don't want to do like no meeting Friday. You know, that sounds great on the service, but no one ever honors that. But if you pick a couple of days out of the week, like maybe Tuesday or Thursday, and you say, we're not going to have any morning meetings on those days.
7:41 Speaker 00 Because a lot of people like myself are more productive in the morning. So if you're more productive in the morning and you take away those morning meetings, that's going to feel so much better. It's going to allow you to focus. Excuse me. It's going to allow you to focus on what you can do. So if you have no meeting mornings, like on a Tuesday and Thursday, you have time to do the things that you need to do that are extra. For example, I could be recording this podcast episode on a no meeting Thursday, no morning meeting Thursday. Right? And that would provide a great opportunity for people to have these little windows on their calendar that are like sanctuaries where they can peel away and do things they need to do. They can escape the frenzy of all the manic things that are going on in the office.
8:26 Speaker 00 They can escape the drama. They can get into and actually do things that are productive and know that that time set aside specifically for them.
8:35 Speaker 00 Sometimes a next step for a project is to always say, oh, let's schedule a meeting. But it's helpful to clearly set the expectation as to what type of meeting it is. What are we trying to do? When people have different expectations on whether a meeting is to get work done or to plan to get work done, frustration abounds. So one of the things that I talked about in a previous podcast called The RATS, R A T S, which is one of the most listened to podcast episodes, includes the agenda, state explicitly whether a meeting is to get work done or plan to get work done. A team sync or check in is a good example of plan to get things done meetings.
9:16 Speaker 00 These should be efficient and focused on information sharing, but essentially at the end of it, you break to go do the work. A get work done meeting is where you're there to build something together and there's a tangible result expected as an output. As an example, that works well. I needed to get with a coworker to build a new item. And we could have either met to make a plan about how we're going to do it in a short meeting, or met to actually do it, which will probably be a little bit longer meeting. But because it was a collaborative effort, we decided to go with a get work done meeting. And I even titled the meeting, A and B are going to build the C. And we built what we needed and it took under an hour and it was great because we each blocked
10:00 Speaker 00 out that time and set aside all other interruptions to get that work done. And if you can do that, that's a powerful way, especially if you're working in a remote or hybrid environment, to pair or peer and do the things you need to do to get things pulled together.
10:17 Speaker 00 This is a really small tip, but I'm going to throw this tip out there too. A lot of times if you are going to leverage chat, I often go in there and say, if you're in a Zoom meeting and you're taking what time with, who wants to go first? Okay, who wants to go next? And you're waiting for people to respond or, you know, can anyone hear Tom? Tom's on me. Oh my goodness, it just drives me crazy, right? It makes me, it makes me just batty. It's so awkward. So when it makes sense in the chat, I'll put what order people are going to go in. I'll put a lineup, just like in baseball, you're teeing off, you're going second, you're third, right? And that works really, really well. So this way, if you're brand new and you don't know when to go, or you don't know what to say,
11:02 Speaker 00 everything is there and it takes the anxiety away from people deciding, should I speak now? Should I wait for Shelley to speak? What do I need to do? It takes away that stress and gives you the ability to talk in turn.
11:16 Speaker 00 I know of another one that I thought of. And with a new year, it's probably time for us to start thinking about scheduling an hour that I call like a working hour with a team. And I'm going to try this as an experiment.
11:34 Speaker 00 In lieu of a plan to get things done meeting, this is a more side by side collaborative time. Where you sit next to someone who you know is working on something similar and chatting with them a bit while you're working or looking up to get the next question or feedback answered without having to schedule a whole meeting about it. So instead of scheduling a whole meeting to discuss things, if you block out an hour to peer or pair with someone so that you can work together side by side, that's a great way to get things done. And I can tell you now, one of the biggest things I talk about is the effectiveness of pairing and pairing. Because those things, when you swarm or mob to get things done, that's when you're going to follow Little's Law. And you stop starting new stuff and start finishing the things you've begun.
12:18 Speaker 00 And it's going to help you achieve with a limited work in progress. It's going to help you achieve those goals that are going to give you the best outcome and impact for the end consumer. So now that we've got all that out of the way, that's a whole litany of different things you can try to help make your meetings better. I hope that it helped you as much as it helped me. If you have a topic you want to discuss, learn more at agiledad.com. We'd love to hear from you. And as always, we encourage you to stay healthy, stay well, and stay agile, my friends. Until next time, do take care. Bye now.
13:12 Speaker 00 Let's talk for a moment about remote work. It's become part of our everyday lives, but I've often said in my trainings that we need to use a more pragmatic, humanized approach, a psychology-driven approach to making work more sustainable. Someone brought to my attention an article that came out about making remote work more human, and I thought we'd take a look at it and see where it takes us. It appears to have some good insight, so let's get started. Last week, I read a story from tech writer J.A. Westenberg called "Modern Work Sucks." There's another word there I'm not going to read, but it describes a nightmarish state of remote work, waking up to Slack notifications, jumping back and forth
13:54 Speaker 00 between 20 different systems, and inexhaustible onslaught of Zoom meetings. This sounds like a day in the life of most people who are working in a hybrid environment right now. At least, that's what I see, right? When I go in and I coach teams, I'm taking a look at how they're behaving and what's happening, and some of the, how should I say, waste, if you will, is coming from too many meetings, from drudgery of feeling like you have to be involved in so many different things. And what we're seeing is a rejuvenation period where people are literally taking a chance to breathe, working from home and going and doing things, which is breaking their work up, which is making it take longer. It's an endless loop. It's a cycle, right?
14:36 Speaker 00 And I'm not seeing people break that cycle. As someone who thinks a lot about work culture, the story felt like a rallying cry, a tidy articulation of what not to do. How do we create something that feels the opposite of this?
14:52 Speaker 00 That's a good question. For what it's worth, I don't think that remote work in and of itself sucks. I don't think it's a bad thing. I think remote work is great. I'm a fan for the most part, as long as people have the right balance. Sometimes people say, please don't make me go back to the office. But there's a point.
15:17 Speaker 00 There's a point we need to talk about here. The way we design for remote work often forgets that we're human people and that we have human bodies and brains and not just work input cogs and output cogs. We work on machines, but we're not machines. And I think sometimes that gets over understated. So sometimes when I think about my job as an agile coach, I often think to myself, how can we make this a humans first approach? How can we humanize what we're trying to do? And even though there's so many workplaces in the world that are offering remote opportunities, there's no single playbook to follow on how to do remote work successfully. Nobody's come up with a playbook. I mean, I've come up with a really good Scrum Master and Product Owner playbook,
16:02 Speaker 00 but there's no clear remote work playbook. What works for one company isn't going to work for another company. What we experiment with, some's going to fail and some's going to succeed. And we have to take that in. We just have to acknowledge and live with that reality. We try new things, we gather feedback, we pivot or adjust. And I think that we can all come to terms when we find something good that we can do together. But the big crux of what I've been thinking about with regards to hybrid and remote environments is meetings. Meetings are the number one complaint. The number one complaint of agile teams that are working remotely is too many meetings, closely followed by an inability to decompose work in such a way
16:41 Speaker 00 that it's easy to consume and provides value, right? Those two run neck and neck and flip flop between number one and number two.
16:50 Speaker 00 So for the past year or two, or I should say longer than that, ever since COVID, actually, I've been trying to find different techniques or different ways to make work more human, to change the way we do meetings.
17:04 Speaker 00 And one of those rules right away, right out of the bat, is a rule regarding chat. So chat is an incredible function if you're doing an all-day workshop or a training seminar. But if you're doing just an online work meeting, you should have a no-chat rule. If you're in a Zoom meeting, you're trying to pay attention and it's just side chatter, just going on in chat. Right? It's so distracting. It's the same as Slack or Teams, right? As soon as there are comments in the chat, or worse, full-on conversations, I've seen that happen too, the attention becomes split between both things. So now you're trying to pay attention to the chat, you're trying to pay attention to what's going on, and you just can't do this.
17:47 Speaker 00 It's just, we struggle. We struggle with attention disorder just trying to keep up with what's going on in one place, much less in multiple places. So when you start dividing what's happening, you're losing out on inclusivity, you're losing out on... You're creating bias. So for small-team meetings, we should always say, "No-chat rule." No one has a lot of the posts in the chat, maybe for sharing a link to a doc or something like that perhaps. But if you have something to say, say it in a meeting. This doesn't need to be a rule for every meeting, like an all-hands-company meeting. But, you know, the side chat in those types of meetings is a fun way to keep people engaged.
18:30 Speaker 00 But for the right-sized meeting and purpose, we shouldn't be leveraging the chat to do those things. We should be just speaking what we have to say. Okay, here we go. Sticking with that, just close your Slack. If you're in a meeting, close your Slack. There's a book called 4,000 Weeks. It's a time-management book. It's kind of an anti-productivity culture while also being very much a productivity book. In the book, Burtman, the author, explains that the reason we drift into distraction, say, checking your Slack DMs while you're in a Zoom meeting, is not because you're bored. It's because paying attention is hard.
19:10 Speaker 00 It's just that distraction is easy. Paying attention is hard. Distraction is easy. So the cognitive work of actually thinking deeply or better actively listening is harder than scanning your email or applying to a Slack thread. Those things are easy. Your impulse to keep tabs on Slack isn't productivity or boredom driven. It's your brain's way of saying, please don't make me work this hard. Please just let me do the easy thing. Let me do the thing that's coming right to me. So in a recent team retrospective that I facilitated, I asked everyone right away to do one favor for me to please close Slack all the way. Take off your Apple watch. Turn your phone upside down.
19:51 Speaker 00 Whatever other ways notifications are going to reach you, don't let it creep into your space. And that meeting that was scheduled for an hour ended up taking about 35 minutes and it was way more productive than any other meeting we've ever had. What I'm trying to say here is we can pivot and adjust. We can change the way we do things. We just need to make minor modifications. Right? Okay. So how about this one? I wanted to set aside and reserve certain mornings where there were no meetings. And I don't want to do like no meeting Friday. You know, that sounds great on the surface, but no one ever honors that. But if you pick a couple of days out of the week, like maybe Tuesday or Thursday and
20:34 Speaker 00 you say, we're not going to have any morning meetings on those days. Because a lot of people like myself are more productive in the morning. So if you're more productive in the morning and you take away those morning meetings, that's going to feel so much better. It's going to allow you to focus. Excuse me. It's going to allow you to focus on what you can do. So if you have no meeting mornings, like on a Tuesday and Thursday, you have time to do the things that you need to do that are extra. For example, I could be recording this podcast episode on a no meeting Thursday, no morning meeting Thursday, right? And that would provide a great opportunity for people to have these little windows on their calendar that are like sanctuaries where they can peel away and do things they need to do.
21:17 Speaker 00 They can escape the frenzy of all the manic things that are going on in the office. They can escape the drama. They can get into and actually do things that are productive and know that that time set aside specifically for them.
21:32 Speaker 00 Sometimes a next step for a project is to always say, oh, let's schedule a meeting. But it's helpful to clearly set the expectation as to what type of meeting it is. What are we trying to do? When people have different expectations on whether a meeting is to get work done or to plan to get work done, frustration abounds. So one of the things that I talked about in a previous podcast called The RATS, R A T S, which is one of the most listened to podcast episodes,
22:02 Speaker 00 includes the agenda, state explicitly whether a meeting is to get work done or plan to get work done. A team sync or check in is a good example of plan to get things done meetings. These should be efficient and focused on information sharing, but essentially at the end of it, you break to go do the work. A get work done meeting is where you're there to build something together and there's a tangible result expected as an output. As an example, that works well. I needed to get with a coworker to build a new item. And we could have either met to make a plan about how we're going to do it in a short meeting, or met to actually do it, which would probably be a little bit longer meeting. But because it was a collaborative effort, we decided to go with a get work done meeting. And I even titled the meeting,
22:49 Speaker 00 A and B are going to build the C. And we built what we needed and it took under an hour and it was great because we each blocked out that time and set aside all other interruptions to get that work done. And if you can do that, that's a powerful way, especially if you're working in a remote or hybrid environment, to pair or peer and do the things you need to do to get things pulled together.
23:14 Speaker 00 This is a really small tip, but I'm going to throw this tip out there too. A lot of times if you are going to leverage chat, I often go in there and say, if you're in a Zoom meeting and you're taking what time with, who wants to go first? Okay, who wants to go next? And you're waiting for people to respond or, you know, can anyone hear Tom? Tom's on me. Oh my goodness, it just drives me crazy, right? It makes me, it makes me just batty. It's so awkward. So when it makes sense in the chat, I'll put what order people are going to go in. I'll put a lineup, just like in baseball, you're teeing off, you're going second, you're third, right? And that works really, really well. So this way, if you're brand new and you don't know when to go, or you don't know what to say,
23:58 Speaker 00 everything is there and it takes the anxiety away from people deciding, should I speak now? Should I wait for Shelley to speak? What do I need to do? It takes away that stress and gives you the ability to talk in turn.
24:13 Speaker 00 I know of another one that I thought of.
24:16 Speaker 00 And with a new year, it's probably time for us to start thinking about scheduling an hour that I call like a working hour with a team. And I'm going to try this as an experiment.
24:30 Speaker 00 In lieu of a plan to get things done meeting, this is a more side by side collaborative time. Where you sit next to someone who you know is working on something similar and chatting with them a bit while you're working or looking up to get the next question or feedback answered without having to schedule a whole meeting about it. So instead of scheduling a whole meeting to discuss things, if you block out an hour to peer or pair with someone so that you can work together side by side, that's a great way to get things done. And I can tell you now, one of the biggest things I talk about is the effectiveness of pairing and pairing. Because those things, when you swarm or mob to get things done, that's when you're going to follow Little's Law. And you stop starting new stuff and start finishing the things you've begun.
25:15 Speaker 00 And it's going to help you achieve with a limited work in progress, it's going to help you achieve those goals that are going to give you the best outcome and impact for the end consumer. So now that we've got all that out of the way, that's a whole litany of different things you can try to help make your meetings better. I hope that it helped you as much as it helped me. If you have a topic you want to discuss, learn more at agiledad.com. We'd love to hear from you. And as always, we encourage you to stay healthy, stay well, and stay agile, my friends. Until next time, do take care. Bye now.
Previous Why Scrum Product Owner Certifications ARE Worth It.. Next 10 Tips To Reduce Communication Gaps at Work Page updated November 7, 2026 · transcript and summary are machine-generated