Make 'In-Person' Meaningful

Rhiannon Gallagher • August 12, 2023

Because it's respectful

A group of people working around a table of drawings and pens.

How many times in the last couple of years have you travelled a long way for a meeting only to sit in a conference room ingesting status reports and presentation slides? Yes, everyone is ’together,’ at considerable expense, but looking at their own screens. Maybe there is lunch. But mostly, the entire meeting could have been done remotely.

In a dispersed world, where teams come together only occasionally:

If you are in-person, connect in ways that you can only do in-person.

Physical presence is very different than a virtual meeting, and deserves MORE respect and attention because it happens so rarely now, not less.

In-Person gatherings are perfect for:

  • brainstorming
  • one-on-one conversations
  • dialogue
  • creativity
  • creating trust and psychological safety

Because:

  • It’s possible to have multiple conversations simultaneously
  • It’s relatively easy to make the size and members of conversations fluid
  • People can read more body language, so they often (not always) feel psychologically more connected and less fatigued
  • You can use physical props to disrupt multi-tasking and get more of people’s brains engaged, increasing output and creativity

Imperfect meetings happen all the time.

We live in a rapidly evolving work world that is figuring out what hybrid means, what productive means, what autonomy means, what ablism and bias mean in a setting that is only sometimes physical.

One of the ways we start to define all this is honoring and honing the time we spend together, particularly physically. If we are taking people away from their homes and loved ones for a few days, we need to honor that sacrifice. It’s one way to show them how important they are to our work and how seriously we take the things that matter to them.

I spend a lot of time, energy, and expertise constructing activities, questions, and rhythms of both virtual gatherings and physical ones. At least 10-12 hours for every hour of face time.

I want every meeting to be more connective and/or constructive than people expect it to be.

I want them to accomplish something that moves the work forward, not just hear a report they could have read on their own in less time.


By Rhiannon Gallagher August 25, 2023
Notice and activate the team
By Rhiannon Gallagher July 18, 2023
A tribute to walkers
By Rhiannon Gallagher July 14, 2023
AKA Missing my mom
By Rhiannon Gallagher June 16, 2023
Murray wasn't happy. He was sure this new initiative would fail, just like all the others. 'I've been here for 31 years,' he'd say. 'They almost always fail.' But Murray was a planner, coordinating schedules and materials for teams across the entire organization. He talked to almost everyone, and he talked a lot. We had to get him on our side. Digital transformations succeed or fail for many reasons, big and small. Most of those reasons are people-related. But sometimes the reason is a person. One person. Or just a few people. People who, if you looked at them on a hierarchical chart, wouldn’t seem to have a bunch of power. But WOW, they have a lot of influence. We call these folks social nodes, and few actions will support your transformation success more than finding them, knowing them, honoring them, and getting them on the side of change. On factory floors, sometimes, they are social nodes because their role is so far-reaching. Planners, tooling designers, and in-process inspectors who talk to everyone and know everything are often social nodes. Union officers may be social nodes as well. But they could also be social nodes because they are simply people who connect well. The person who organized the chili cookoff or the person who always seems to be chatting in the breakroom. The person who reads all the company newsletters and emails and knows what’s happening outside the day-to-day. Social nodes often have strong opinions. They are loyal on multiple levels, but they’ve often been around for a few ‘transformations’ and can rattle off what went wrong in every one of them. Once we know who they are, we can build communication to support them. In various projects, I’ve given them special briefings, created a place in the project updates that comes from them, given them access to early information they could disseminate, or checked in with them regularly to learn how implementations are going. For Murray, we created a special column in the project newsletter called 'Murray's Musings' and recorded and transcribed a little interview every month. We asked about the problems with the old processes and checked in on new ones. We asked about his history with the company. We let him know that everyone, including the C-Level folks, was getting the newsletter and reading his words. Murray is retired now, but his stories are recorded as company history. And the initiative succeeded, partly because we recognized Murray as a social node and got him on board.