Return Home

Nu Skin: Rebuilding trust after layoffs

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.

Role
Lead Researcher, Culture Consultant
Scope
Culture, communication, and facilitation across engineering
Team
Nearly 100 technologists, plus management and middle managers

The problem

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.

What I started with

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.

Fear

Waves of company-wide layoffs taught people that raising a problem could mark them as the problem.

Workarounds

Teams worked around dysfunction instead of calling it out. Communication gaps, broken handoffs, and blocked decisions stayed out of sight.

Trust

The teams had labeled surveys, town halls, and open-door speeches as risky.

Visibility

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.

Who it serves

Engineering teams

Developers, designers, QA, and product managers had watched colleagues lose their jobs. They needed a safe way to speak up.

Middle managers

They had their own fears. They needed their own room.

The VP of Engineering

He needed the communication to start again.

How I worked with the VP

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.

The approach

Step 1: Collect the issues

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.

Step 2: Run the middle managers separately

I ran the same process with middle managers. A manager I recruited facilitated that group.

Step 3: Interview the VP live

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.

Step 4: Repeat, then step back

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.

Step 5: Hold the new habit

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.

The decisions

  • Four groups, with management separate

    Options
    One department-wide session, or smaller groups.
    Gave up
    A single shared room for every issue at once.
    Why
    Middle managers had their own version of the fear, so each level needed its own room. Any workshop with that many people will drown out most of the voices and become chaos.
  • The live interview

    Options
    A written report to the VP, or a live interview in front of everyone.
    Gave up
    A controlled, private conversation with the VP.
    Why
    The teams needed to see hard questions asked and answered in public.
  • Questions framed as my own

    Options
    Frame the questions as coming from the team.
    Gave up
    A shield for the team.
    Why
    Asking in my own voice kept individual team members out of the line of fire and retained trust.
  • Three repetitions, then a monthly forum

    Options
    One session, or a repeated format that handed off over time.
    Gave up
    A quick finish.
    Why
    The teams needed to see the format work more than once, and the new pattern needed time before it could run without me. Trust is earned over time.

What I would do differently

  • Include some of the other upper management

    Some of them wanted to join, and I learned later that others did too.

  • Run the same format in other parts of the organization

    The call center and sales had the same issues, and nobody addressed them.

  • Make the moment to speak up clearer in the first session

  • Create a way for people to talk outside Teams chat

    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.

The outcome

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.

Building something that needs a clear map? Let's talk.

Tell me where the route got unclear. We'll find the way together.