A department of nearly a hundred technologists had stopped talking. In five weeks, I built a facilitation program to bring the problems back into the open.

The VP of Engineering asked me one question: why is nobody talking to him about the issues this department is having?
He knew something was wrong. Delivery was inconsistent. Morale was visibly low. Decisions were not getting made. Stand-ups were quiet, and one-on-ones produced nothing he could act on. He ran a department of nearly a hundred technologists and received nearly no info from inside it. He asked me for a perspective because I had been embedded across the department as Lead Researcher.
He wanted better information flow. I told him the information flow was not the problem.
The teams knew exactly what was wrong. They were not comfortable talking.
The VP was diagnosing communication. Better tools, cadences, and one-on-ones would have made sense if the department had been quiet because it had nothing to say. It was quiet for a different reason.
Waves of company-wide layoffs taught people that raising a problem could mark them as the problem.
Teams worked around dysfunction instead of calling it out. Communication gaps, broken handoffs, and blocked decisions stayed out of sight.
The teams had labeled surveys, town halls, and open-door speeches as risky.
The VP could fix what he could see, and what he could see was severely limited.
The fix had to show everyone, in public, that speaking up was safe. Someone had to be willing to take the risk first, and the demonstration had to repeat until people believed it.
Developers, designers, QA, and product managers had watched colleagues lose their jobs. They needed a safe way to speak up.
They had their own fears. They needed their own room.
He needed the communication to start again.
I proposed the plan, and the VP agreed to the format in advance. I described exactly how I would run each session, including the live interview with his feet to the fire and that he needed to respond openly and honestly. He agreed to it before the first workshop.
I split the department into four groups of about twenty-five people. Management had its own group. In each group, I ran a modified Agile Coffee workshop on a digital whiteboard. Everyone listed the issues they saw from their role. We clustered similar issues, and the group voted to rank them. The top issues from each group went into one consolidated set.
I ran the same process with middle managers. A manager I recruited facilitated that group.
I scheduled a company-wide meeting and interviewed the VP in front of everyone, using the consolidated issues as my script. I asked the questions as my own, not as the team's. A private chat window, visible only to me, let the group send follow-up questions in real time. The teams watched me put hard questions to the VP. They watched him answer. Then they watched what happened to me afterward.
Nothing bad happened to me afterward. I came back the next week and ran it again. The team needed to see it.
I ran the interview three times across five weeks. The first time, the teams watched. The second time, a few people added their own questions. By the third session, I was mostly facilitating. The teams spoke to the VP directly, raised issues in their own voices, and received answers in real time. I had modeled the behavior and then stepped out of the way.
After the third session, I told the teams to bring their issues directly to the VP. We held an open monthly forum for two more months while the new pattern set. Then it dissolved into normal operating rhythm.
Some of them wanted to join, and I learned later that others did too.
The call center and sales had the same issues, and nobody addressed them.
Some people felt uncomfortable that management could see into Teams if it chose to, and it has happened at Nu Skin before. This is the change I would make first.
After the workshops, several issues got addressed. Each one removed a blocker that people had been working around, and the fixes compounded because people were speaking up.
The communication shift held after the formal sessions ended. Teams brought issues directly to leadership. Months later, informal health checks showed the change had stuck. People felt more comfortable, and they kept talking.
The health checks also surfaced fears. Some people warned me I would get fired. Others called the workshops a stunt and doubted that leadership was sincere. I raised these concerns with leadership without naming anyone. I encouraged people who wanted to speak up, and I told them when to raise an issue privately and when to raise it in the workshop.
Not every underlying issue got fixed. That work belonged to the VP. The fear did not disappear entirely, and in a company that has been through waves of layoffs, it rarely does. But talking about what was not working was the start.
Tell me where the route got unclear. We'll find the way together.