Collaboration Now: Unity

In the November 2020 Collaboration: Unity livestream, I asked Ailiana Denis, Brent Darnell, Dr. Giovanna Brasfield, Felipe Engineer-Manriquez, and Rex Miller how people could keep learning, listening, and collaborating while apart. Their methods were different, but they pointed toward the same practical lesson: empathy becomes real when a team turns good intent into choices about attention, participation, safety, and follow-through.

The archive preserves the full livestream, an introduction, and five guest-specific clips across three related pages. Read together, they offer a practical set of patterns for project teams that want empathy to shape the work, not simply the mood in the room.

Why empathy gets stuck at good intentions

When a difficult project conversation stalls, it is tempting to diagnose an attitude problem: someone lacks empathy, resists change, or refuses to be vulnerable. That diagnosis is too thin to guide the next move. It does not tell an accountable owner how the conversation was opened, whose risk was overlooked, whether participation was genuinely voluntary, or what happened after people spoke.

Several guests described project environments that rewarded task completion and toughness while making struggle harder to reveal. Brent Darnell discussed the cultural cost of asking for help and the different penalties women could face for showing vulnerability. Felipe Engineer-Manriquez described emotion as present on project teams even when the culture pretended otherwise. Rex Miller contrasted task-first habits with the deliberate work of seeing each participant as an individual.

The issue is not whether empathy is desirable. It is whether the team has a practice that helps people stay curious, distribute voice, interpret resistance, and carry what they learn into a decision. Without that practice, empathy can remain a warm word attached to the same meeting design.

Four ways to make empathy operational

Curiosity needs a review point

Ailiana Denis offered curiosity as an entry into a difficult exchange. She also supplied the important warning: a person can ask questions and route every answer back through the worldview they already hold. Her proposed interruption was small. Pause while listening, notice the impulse to shut down, and wonder about what is being heard before settling on an interpretation.

That makes curiosity less like a personality trait and more like an in-conversation control. The useful question is not only, “Did we invite another perspective?” It is, “What would cause us to revise our own?” A facilitator can make that review point visible by asking participants to name what they learned, what assumption moved, and what remains unresolved.

Ailiana put the pause into plain language: “If you pause and say, ‘I wonder,’ even while you’re listening, that can be powerful to keep you engaged too.”

Safety cannot be declared into existence

Brent Darnell described origin-story exchanges as a way to create connection across difference. Rex Miller described beginning team sessions with a low-risk personal-story format before moving into shared language and pressure scenarios. Both accounts point toward structured participation rather than an unbounded request for people to disclose something personal.

The limits matter. Before asking people to share personal experiences, a team should decide what participation means, what remains confidential, and when the conversation needs support beyond the facilitator's role. Brent also described unequal consequences for vulnerability across gender and project culture. A leader cannot ask for openness, call the room safe, and assume the risk is shared evenly.

Listening needs an owner and a handoff

Dr. Giovanna Brasfield connected listening to organizational and project choices. In her account, company listening informed questions about recruitment, retention, growth, and business strategy. Project-level listening led toward community resources, training, engagement, and partnership. Her examples make an essential distinction: listening was intended to create an input to work, not a ceremonial pause before business resumed.

Felipe Engineer-Manriquez added a useful view of resistance. While facilitating groups of roughly 10 to 50 people, he said he tried to understand each person's state rather than treating the room as one mass. In one story, a skeptical participant later chose to continue talking and disclosed a history of broken trust. Felipe listened without prescribing a solution. That experience suggests that resistance can carry information about prior experience, not merely rejection of a method.

If listening is supposed to affect the work, someone must own the handoff. Who turns a recurring concern into a change? Who explains what will not change and why? Who checks whether the response addressed the condition people described?

Participation needs rehearsal, not just invitation

Rex Miller described effective meetings as ones in which dominant voices do not consume the conversation and quieter participants have a route in. He also argued that knowledge alone does not determine what a team will do under pressure. The response has to be practiced. A team can understand a principle and still fail to enact it when the stakes rise.

The guests also connected facilitation capacity to personal preparation and recovery. Their routines were personal, not universal prescriptions. The narrower lesson is practical: do not place a high-stakes conversation into an overloaded calendar and expect attention, patience, and judgment to appear automatically.

A five-step empathy loop for project teams

A facilitation practice works better when its terms are visible before the meeting: purpose, participation, recording, confidentiality commitments, and escalation routes. In high-stakes or regulated settings, those terms need current specialist guidance.

Empathy is part of the operating system when it changes how a team prepares, participates, responds, and learns. A lightweight practice can make five handoffs visible:

1. Invitation: Name the operating question, the accountable owner, and the terms of participation.
2. Preparation: Identify whose experience is represented, whose is missing, and which topics require a different kind of support.
3. Conversation: Watch the distribution of voice, pause interpretations, and distinguish an observation from an assumption.
4. Response: Assign each supported action, explain each deferral, and protect confidential detail from becoming meeting exhaust.
5. Review: Return to the group with what changed, what did not, and whether to continue, revise, partner, defer, or stop.

This does not make every difficult conversation easy. It gives the team a repeatable way to turn empathy into action.

Use the practice, then look for change

These practices are starting points. A practical way to learn whether the practice helps your team is to establish a starting point, name the change you hope to see, protect participants, and follow up.

That follow-up matters because a conversation can feel productive without changing the work. The useful signal is what happens next: whether a concern receives an owner, whether a decision changes, whether quieter participants gain a route into the discussion, and whether the team returns to explain what it learned.

Test the practice in one recurring meeting

If you want to test the practice in one meeting, choose a recurring meeting where people may leave feeling unheard or where the same resistance returns. Before the next session, write down six answers:

• What decision are we trying to improve?
• Whose experience is represented in the room, and whose is not?
• What does speaking candidly risk for each participant?
• What is voluntary, confidential, or out of scope?
• Who owns the response after the conversation?
• What observable change would justify continuing the practice?

Run the smallest useful version, then review the handoffs. Do not judge the meeting only by whether it felt empathetic. Ask whether the team learned something it could responsibly act on.