Build community to create memorable experiences

Recently, my partner and I went on our first big long vacation since 2019. We went to Italy for two weeks, which was wonderful. Although we did plenty of things on our own, we did sign up for some tours of historic sites, of museums, of a region’s food. Some of the tours were great and some of the tours were…well, they weren’t horrible or anything. They were simply lacking.

What were they lacking?

My partner and I asked each other this, and we both came up with fairly similar answers. The tours and group activities we enjoyed most were the ones where we had the opportunity to build relationships with the other participants – even if only for a couple hours.

Table with a charcuterie board, a dish of olives, a bowl of bread, and a basket of fava beans. No one is sitting at the table yet,
We did a food tour in Florence, and it was not only enjoyable because of the food (sensory touchpoints), or what we learned, or the tour guide, but also because we got to share the experience of trying new food with other people, and we had the chance to share a table and get to know them and hear about their trips as well.

Of course, leave it to a service designer to want to mull on this a little more…

When designing for someone to have a positive experience, you’re often thinking about what the purpose is, what the desired outcome is, what is the person’s job to be done. A big part of this is meeting expectations and understanding what a positive outcome would be for the customer, event attendee, student, whoever is engaging with your product, service, class, tour, whathaveyou. (I get a bit annoyed at the constant talk of delight in the design process. It makes sense if you’re designing something fun, like game or makeup. When I am renewing my driver’s license, what would delight me is to not have to do it at all!)

In service design, a core question is how to create value for everyone involved—the customer and the business to be sure, but also the employees and others involved in or impacted by the service. While it might be focused on the humans using the service and their experience, it’s not sustainable if it burns out your employees nor if it detracts from the organization’s primary goals. (If a person’s goal is to ensure their kids are safe while they go run errands, perhaps that is not great if your organization is say, a museum, and not a childcare provider or otherwise set up to supervise children. And perhaps not great for the kids either.)

Through the framework of service design, we can break a service down into touchpoints (the things a customer is touching, so to speak, whether it’s packaging or an email), interactions between a customer and employee, and all the other layers of what happens (or is needed, infrastructure-wise) behind the scenes that allow us to deliver that service in that way.

Typically, when we think about what will make something a good experience, we think about touchpoints and interactions. Maybe we want our emails to have a friendly tone, or we want to make sure our staff are trained on how to work with disabled customers and provide various accommodations. Maybe we think about the relationships and try to have an assigned account representative for each client or good practices around entering data into a CRM so that any employee can assist any client smoothly with all of their details and history at their fingertips.

But how often, unless our service is explicitly about creating community, do we think about creating community within group experiences? How often do we consider the interactions between our clients, students, participants?

I’ve been a community manager—where my role was specifically to foster community and knowledge exchange among an evolving group of practitioners. (I still do this for fun in my creative pursuits!) But I’ve also used community building in other roles and in shorter terms.

When I was a technical instructor who was training new staff, I always started each training with an icebreaker. I would ask at least one question that was about us as people outside of work, and I usually tried to ask one question that related to the topic. I did this for a few reasons:

  1. Whatever people were doing before they came to the training, meeting, workshop, or other session you’re facilitating, it’s helpful to give people a way to shift their brains into what you’re about to do next.
  2. Most of the training I led was required onboarding, and it was all on using databases, which is a bit of a dry topic to dive directly into for many people. When it’s a topic that sometimes people dread, or that they’re a little worried will be difficult, it’s helpful to ground people in their existing knowledge. For example, during trainings on using the database to manage event attendees, I would ask people to share about an event they enjoyed and what made it a positive experience.
  3. Everyone in my trainings had recently joined the organization. I wanted to provide a low-stakes opportunity for them to practice introducing themselves with their new role and to get to know other new employees across the organization (a rare opportunity in most large organizations, as this was).
  4. I wanted to model what kind of space this was: a space where they could be seen as more than their job title, where they were invited to participate and use their voice from the start, and a space that, in its playfulness, hopefully felt more like a sandbox and less like a classroom.

Certainly, everyone was there to check the box as something they needed to perform their jobs. But I’d like to believe my efforts also helped reduce any anxiety (a thing in data/technology training) so that they could learn, helped new employees feel a little more seen and connected within such a vast organization, and made it easier for people to reach out to me for help in the future (many did). And that’s valuable to the training participants, it’s valuable to the organization, and it was valuable to me, as an instructional designer – to know what other learning needs there were after the training.

At the time, I didn’t think of it as building community. I thought of it as holding and shaping a space, for that time when we were all together, and creating an atmosphere within that space where we would all be primed for what we were about to do together—so that we may get the most value out of it.

The ability to connect as humans with everyone experiencing the same thing I am in the moment always make things a little brighter, and a little deeper. Growing up in NYC, sometimes we would have blackouts in the summer. And the neighbors emerge from their homes, and we’d sit outside together and talk, creating our own light in the dark.

Build community, even if it’s ephemeral.

It doesn’t matter whether it’s for an hour-long workshop, or a three-hour tour, or if the people will ever see each other again. Sure, having one instructor train 20 new employees is more efficient than training everyone 1:1. But it’s not the only reason to do it.

I’d like to call out that, first of all, it’s far less awkward. Isn’t a little silly to act as if everyone is in their own little bubble and can’t see or hear the other participants? Rather than leaving people to navigate the ambiguous social situation by themselves, we could (as facilitators, hosts, tour guides, et al.) create a starting point for intentional connection.

More importantly, creating opportunities for human creation is another way to add value to the experience. It is human to crave connection. If you’ve ever experienced something and suddenly wished that a specific person was there to share it with you – you know that an experience is different when you’ve shared it with someone. The same way that adding a dash of salt deepens the taste of caramel or that sprinkling in some red pepper flakes near the end of cooking intensifies the other flavors in a dish, that connection makes an experience feel fuller, as if you yourself, in opening up to others, have more fully opened up to that experience.

While you may not build a community that outlasts the event, human connections are the foundation. So why is this post about community rather than about connections? Simply trying to connect people to each other ends up being some sort of transactional speed-dating situation that leaves everyone unsatisfied. But if you think about it in terms of building community, and leave it open to each member to contribute what they will, you create something much better together.

My heart is full of food for thought from 22NTC

Looking at a desk from the point of view of person sitting at it: There is a laptop positioned below an external monitor; both have things on the screen.  There is a mic to the left and some printed papers between photographer and laptop.  There is another large monitor to the right, off.  And a tabby cat is standing to the right looking towards the left.
This year I volunteered backstage (assisted by my cat, Amelia) in addition to presenting.

Once upon a time I went to NTEN’s annual Nonprofit Technology Conferences and came away with all sorts of innovative, savvy, practical tips that I could take back and apply at work—sometimes that week.

These days I do a lot less operational work in my day-to-day and more strategic work (let me know if you need help figuring out any blob shaped problems!).  So, while NTCs are still jampacked with practical knowledge exchange and lots of strategic content as well, I find myself reflecting most on the takeaways and questions posed that strike at the soul, why we do what we do and how that should inform what we do, whom we partner with, and the way in which we do our work.

Here are the things that struck me or resonated, and that I am still chewing on.

We have been lied to, and there are people who benefit from us internalizing these lies.

There was an excellent session (with Aki Shibuya, Bettina Sferrino, Vanice Dunn, and Tristan Penn) taking a systemic look at imposter syndrome.  This is something I’ve long struggled with, always wondering when someone was going to find me out, and I really appreciated a look at the systems that perpetuate this experience and who benefits/is hurt by the belief that this something that people like me need to fix internally. 

Are there ways in which we all benefit from learning to trust our own voices and judgment, from gaining experience and the confidence that can come with it?  Sure.  However, the panel also dug into the organizational practices and dynamics that require we feel inadequate – so that we buy into the idea that we must work more hours to make up for what we lack, so that we question our own judgment while accepting the judgment of others in power, so that we strive harder and harder to reach goal posts being moved further and further away because we were never meant to reach them.  These can be practices like not having clear and consistent expectations for performance, and “accountability” that is applied unevenly.  And while there are more ways to make a shift if you are a manager who has positional power, anyone can model things like, acknowledging when you don’t know something, and using one’s own privilege where you can.  

In the chat for another session, there was a beautifully open exchange between several attendees about the use of identity-first (e.g., disabled people) vs. person-first (e.g., people with disabilities) language.  The discussion was around whether it was a way to reclaim “disabled” from being a bad word that we must euphemize, or, whether we should recognize that there are people with disabilities who prefer person-first language.  (All of the people involved in this thread of discussion identified as disabled or as having a disability.) One person who grew up hearing it used negatively against them (as someone with a disability), preferred person-first language. Another person questioned the need to remind anyone that they are a person first. It ended with some folks deciding they needed to reflect some more on whether this might be internalized ableism and people acknowledging there may be generational differences and people may be in different places in their journeys.

“Normal is a scam.”

– Alice Wong

The first keynote was a conversation between Amy Sample Ward and Alice Wong, who runs the Disability Visibility Project (which includes a podcast and book of the same name).  There was a lot of discussion how access is love, about survival, and about how normal is a scam. 

I’ve been working with a coach for my own personal development, and one of the things I’ve been working is on is not judging how I feel, what I want, and generally things about myself.  To declare something (or someone) normal or abnormal is both to participate in this judging and to perpetuate the myths about how the things that make us who we are, that these are things that are wrong (or right) with us.  Who gains from that? 

What do we gain when we accept all of who we are and who others are?  I think only then we can imagine the world that Amy invites us in to build together:

There is no community without accountability—nor without grace.

One of the things I really appreciate about the NTEN community and the Nonprofit Technology is that we a.) keep it real, and b.) thinking critically about technology and the role it plays in creating a more equitable world.

Now, lots of people and organizations throw around the word “community” and don’t always back it up with systems and practice.  So I loved what keynote speaker Angelica Ross said about community:

Now accountability and grace are not mutually exclusive.  But sometimes, when we want people to do better and we know that they can, we can be frustrated and impatient.  However, we can’t control what other people will do or think or feel—even as we feel the urgency of helping others see what we can see from where we sit.

And of course, the penultimate is to actually put our values into practice, and not surprisingly an event full of nonprofit techies is ready to dive in:

Saeed Jones reminded us that there are people in our community who notice how we speak up—or don’t.  Are we learning about the struggles of others?  How will they know they are safe with us?  This can be a form of accountability we practice within ourselves.

Speaking of accountability and actively practicing our values, Ken Montenegro asked a really important question during his session with Colin Boyle about planning for failure:

They were talking about the context of a crisis and how sometimes the person making the decision is simply the person who happens to be there in that moment—and how it’s worth pausing to ask whether this decision should be made by this interim person or whether to gather the right people to make this decision first.  Although this was about IT disasters, this too can be applied much more broadly.  Are the people making the decision the people who understand the implications and who will be impacted by them?

Stories are powerful because of what they allow us to imagine.

I’ve been thinking a lot lately about the stories we tell about ourselves and that we tell ourselves (and others) about the world.

One really powerful story we often tell is about failure.  Do we tell it as a story of catastrophe, of how we have become failures?  Or do we view it as falling down while learning to ride a bike, part of the process of learning how to do new things?  Is it a pathway to confidence?

(One of these days they’ll allow you to edit tweets, but “earning” is a typo that was supposed to be “learning.”)

There are, of course, also the stories we do not tell:

Related to the stories we tell (or don’t tell) about failure are the stories we tell ourselves about what we are capable of, and what’s possible.  Are we honoring the full potential of who we are?

Speaking of “the full potential of who we are,” the U.S. political divides have lately centered a lot on the power of stories and language and which ideas are okay or not okay.  (Judging again!)  People are demanding that school boards ban teaching Critical Race Theory, ban saying the word “gay” in schools, and banning books that make them feel uncomfortable.  (There are of course, many far more restrictive and persecutive laws being proposed passed across the country—and books and stories and language are part of this broader discourse.  There are others who can speak to that better than I can.)

Who gets to see themselves and be seen?  Who gets to imagine the future of their dreams?

And stories can be incredibly powerful when we feel alone and disconnected.

And, as Saeed Jones pointed out, many people will say they’re “not poetry people” while still pulling out poems for special occasions.

Imagine if we gave ourselves that gift.  (Thank you, Bettina Sferrino, for that lovely prompt.)

An effective meme can function like a poem as a shortcut to that spark of recognition.

That’s me paraphrasing something said by Saeed Jones in the closing keynote conversation with Amy Sample Ward.  There were a lot of gems and I finally managed to gather myself enough to draw sketchnotes for this one! 

On that note, I’ll let these roll around my brain some more, but drop a line if any of these gems resonated with you as well.