4

I'm finding myself in a position where I am the SME (Subject Matter Expert) on the area I work in. I don't mind coworkers coming to me with questions, but I would strongly prefer to answer them only once in a team context as opposed to one-on-one several times, for the following reasons

  • I want to ensure that any concerns are aired in a team settings so if there is a flaw in my understanding or plan of action I want to get inputs from the most people possible.
  • I want to ensure that everyone is onboard with the same plan (I don't want to revise it in one-on-one meeting 3 of 5, so two people are out of the loop)

I've tried soliciting feedback in meetings, but there are 2 possible scenarios:

1.) Either people need to dig into the problem to know what questions to ask

2.) Or they're too shy and don't want to appear ill-informed.

I get the first one, I do that regularly, but how can I get people to understand the second is a corporate anti-pattern?

If someone has a doubt, it's probable other team members do as well.

2
  • 2
    Are they approaching you in person or via email? Personally if I want to clarify some technical details I will do it via email so I can refer back to it at a later date rather than forgetting details that were discussed in a meeting. Commented Jan 3 at 12:03
  • 2
    The second one is only a corporate anti-pattern for you, if the corporation tends to look down on people that don't have all the answers in a group, it is an effective pattern for the asker. Whatever your attempted solutions include, it only takes one roll of the eyes when "X is asking another question" for everyone in the group to get the message of "no questions, please". As you go forward with your attempts to fix this, you need to welcome the questions in the meeting, or your efforts (with any approach) will fail.
    – Edwin Buck
    Commented Jan 3 at 16:44

3 Answers 3

11

Some solutions:

1: Let people know that for the next meeting, you will be collecting questions, then addressing the submitted questions in the meeting itself. The downside is if it's an urgent question, there's a delay in response - but otherwise, this can work.

2: Once the Person has been given their answer, make them present the problem/solution to the group. "I had this problem, after discussing it with SME, we came up with this solution" - not only does it share the knowledge, but presenting helps solidify the understanding.

3: At the end of the meeting, do a Round Table: "What are you working on, any road blockers?" - This way, people who are normally quiet have to speak up and give an answer to the question.

4: If you have questions that are being asked more than once, then the answers need to be documented in a KB article somewhere and people need to be encouraged to use said KB.

2
  • 1
    I like the idea of the first one -- we have daily stand-ups with 16th minutes, I'll have to discuss with my lead if it's ok to block people for a duration of time, (if not I might still direct them to ask the question in the team chat vs direct), but it puts the onus on the asker. This might encourage them to just ask up front.
    – Sidney
    Commented Jan 2 at 18:46
  • 1
    You have hit on what I was going to say, between meetings also use team chat and redirect DM questions into it. You get the benefit of shared knowledge while making it easier on those nervous about talking in the group meeting.
    – mxyzplk
    Commented Jan 3 at 14:27
5

I'm surprised written communication has not been suggested in the answers. Instead of presenting your plan in a group meeting, write a document and invite your team members to review it and leave comments. That way:

  • People can take as much time as they need to understand the plan and ask questions.
  • People hopefully feel more comfortable about asking questions in written form rather than during a multi-person meeting.
  • The answers you provide are written down and can be reviewed by your teammates at a later point. If someone reaches out to you and asks the question you've already answered - simply point them to the answer.
  • All the discussion is assembled in one place - the document, so you don't run into the problem of discussing something with half of the team and leaving the other half out of the loop.

You can still schedule in-person meetings to discuss, but make sure to update the document based on the outcome of those discussions.

1
  • This is a really good answer, even for in-person teams. There are a lot of people who will silently nod their head in agreement to nearly anything that's said out loud in a meeting, but object if they saw it in plain text later. Everything written down is the real way to run and manage a team, particularly if it's a remote one! Commented Jan 5 at 18:49
3

The are a number of "presentation skills" techniques that could be useful here. You might want to investigate that topic anyway. But a few in specific:

You can, and should, pause at appropriate points and ask "Any questions?" That provides a window for those who are hesitant to interrupt.

You can start by explicitly saying that your preference is to have people as questions as you go rather than holding them for the end or afterwards. "If you have a question, odds are that someone else has the same question and is just too shy to ask."

This does require also learning the related art of "Great question. I think I'll get to that a bit later; if I don't, please remind me."

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .