Weekly Wonder: Managing Tough Questions: Facilitating Discussions on Pain Points and Gaps

[#1]

Hi CUG Leaders! This week’s Weekly Wonder is about one of the most important (and sometimes most uncomfortable) parts of community leadership: managing tough questions. When members raise pain points, product gaps, frustrations, or unmet needs, the moment can feel tense. But with the right facilitation approach, those conversations can become some of the most valuable experiences your CUG offers.

Tough questions are often a sign that members care. They want to be heard, they want clarity, and they want a productive place to compare experiences with peers. Your role is not to have every answer on the spot. Your role is to create the conditions for a thoughtful discussion: one that acknowledges the concern, keeps the room constructive, and turns frustration into shared learning or actionable follow-up.

Below are five tips to help you facilitate discussions on pain points and gaps with confidence, empathy, and purpose.

---

1. Welcome the question without absorbing all the pressure

When a member raises a tough issue, your first response sets the tone. Acknowledge the question directly and thank them for naming it. Phrases like “That’s a really important point,” “I’m glad you brought that up,” or “I suspect others may be wondering the same thing” can help lower the temperature and show that the conversation is welcome.

At the same time, remember that welcoming a question does not mean you are responsible for solving it immediately. CUG leaders are facilitators, not product spokespeople or support desks. It is perfectly appropriate to say, “I may not have the full answer today, but let’s capture the concern and explore what we can learn from the group.” This keeps the discussion open while protecting you from being put on the spot.

2. Separate the pain point from the person

Strong emotions often come from real friction. A member may be frustrated because a workflow is slowing their team down, a feature gap is creating extra work, or a recent change disrupted a process they relied on. Instead of reacting to the intensity of the delivery, listen for the underlying need.

Try reframing the concern in neutral, specific language: “It sounds like the challenge is that your team needs a clearer way to manage approvals across tools,” or “I’m hearing that the gap is less about awareness and more about day-to-day usability.” This helps the group move from venting toward problem definition, which makes the conversation easier for others to join constructively.

3. Use the room as a resource

You do not have to facilitate tough questions as a one-to-one exchange between you and the person asking. One of the strengths of a CUG is the collective experience in the room. After acknowledging the concern, invite others to contribute: “Has anyone else run into this?” “How are other teams handling it today?” or “What workaround has been most effective for you?”

This approach validates the original question while turning it into peer learning. It may surface practical solutions, reveal that the issue is widespread, or show that different teams are approaching the same gap in creative ways. Even when there is no perfect answer, members often leave feeling better because they know they are not alone.

4. Keep the discussion constructive and bounded

Open discussion is valuable, but tough topics can easily expand beyond the time available or become circular. Set gentle boundaries so the conversation stays productive. You might say, “Let’s spend five more minutes gathering examples, then we’ll capture follow-ups,” or “I want to make sure we hear the concern without losing the rest of today’s agenda.”

Constructive boundaries are not about shutting people down. They are about honoring the concern while protecting the overall experience for the group. If the topic needs deeper attention, offer a next step: a follow-up thread, office hours conversation, survey question, or future session focused specifically on that pain point. Members are more likely to accept boundaries when they can see the issue will not disappear.

5. Capture themes and close the loop

The most effective tough-question discussions lead somewhere. During or after the meeting, capture the themes you heard: what is causing friction, who is affected, what workarounds exist, and what questions remain unresolved. Even a simple summary can help transform scattered comments into a clearer community signal.

Then, close the loop where you can. Share resources, point members to support channels, invite additional examples, or bring the theme into a future agenda. If you are able to relay aggregated feedback through the appropriate Atlassian channels, be clear about what you can and cannot promise. Closing the loop does not require an immediate fix, it just means members can see that their input was heard, organized, and treated with care.

---

Managing tough questions is not about avoiding discomfort. It is about guiding discomfort into a conversation that is respectful, useful, and grounded in community learning. When CUG leaders acknowledge pain points, invite peer perspectives, set healthy boundaries, and capture themes, they help members feel heard without letting the discussion lose focus.

The next time a difficult question comes up, treat it as a Weekly Wonder opportunity: a chance to uncover what your members are really experiencing and to strengthen trust through thoughtful facilitation. The answer may not always be immediate, but the way you hold the conversation can make your CUG stronger.

---

Public Resources You Can Share with Your Group

• Atlassian University – Free Training & Tutorials 

  • Short, product-focused courses that can serve as inspiration for your series topics or pre-work for attendees.

• Work Life by Atlassian – Teamwork & Collaboration Articles 

  • Practical articles on team rituals, facilitation, and collaboration that can inform how you structure your recurring sessions.

• Atlassian Team Playbook 

  • Ready-to-use plays for running retrospectives, health monitors, and other team activities that make excellent recurring series formats.

[zoltanersek _outpostlabs_dev_]

usually someone else in the room has faced the same issue and can shared what worked and what didn't, so it's great to treat pain points as discussion starters, those discussions are more valuable than a single correct answer

[Anwesha Pan]

Thanks @Blake Hall for sharing this article.