Name it at work: saying the hard thing without the drama

At work, the hardest thing to say is usually the most useful one. So it stays unsaid, until it comes out all at once.

I've done both. I've sat through months of meetings without saying that a project was in trouble. And I've said it far too late, too loudly, with all the stored-up frustration in my voice. Neither helped anyone.

What helps is naming it early, plainly, and without drama. It's the same idea as name it, tame it, used out loud and in front of colleagues.

Scrum teams meet for fifteen minutes every working day in what's called the Daily Scrum. The Scrum Guide says its purpose is "to inspect progress toward the Sprint Goal", and that these meetings "identify impediments." An impediment is simply something in the way.

I love that word. It takes the blame out of the sentence. "I'm blocked because I still don't have access to the data" is not an accusation. It's a fact, said early, while it's still cheap to fix.

At the end of each sprint there's a Retrospective. The guide says the team "discusses what went well during the Sprint, what problems it encountered, and how those problems were (or were not) solved." It's an agreed time to name things. That matters. When there's a set place for hard truths, they don't have to leak out everywhere else.

And SAFe, the Scaled Agile Framework for many teams working together, holds a bigger version every few months called Inspect and Adapt. It focuses on "what has actually happened" rather than "what was supposed to happen", and ends in a problem-solving workshop where the first job is to agree on the problem.

Scrum names five values: commitment, focus, openness, respect and courage. The guide says team members "have the courage to do the right thing, to work on tough problems."

I notice that openness and respect sit right next to courage. Courage alone can come out as drama. With respect, it comes out as a clear sentence someone can actually hear.

When I need to say something difficult at work, I prepare it on paper first, in four short lines. It's the Name it sheet, turned outward.

• What happened. Facts only. "The release date moved twice this month."
• What I notice. My part, owned. "I'm worried we're promising dates we can't keep, and I've been quiet about it."
• What's in our hands. "We can agree a smaller first piece and date that one."
• One next step. "Can we take ten minutes after this meeting to look at it?"

No adjectives about people. No "always" or "never". No speech. Said this way, the hard thing usually takes under a minute, and it often comes as a relief to everyone in the room.

Sometimes the thing to name is my own: I'm out of my depth, I've made a mistake, I'm afraid my role is changing. Those are the hardest of all to say at work.

The same four lines still work. And it helps to remember that my worth at work was never only my job title. There's what I know how to do, the people who trust me, what I've lived through. I wrote about those kinds of wealth in The Eight Forms of Capital, Revisited.

The Bible says it simply: "Speaking the truth in love" (Ephesians 4:15). Truth without love turns into drama. Love without truth turns into silence. Work needs both.

Saying it isn't the end. Write down what was agreed, and check back. Scrum calls this adapting: changing course as soon as you learn something. If nothing changed, name that too, calmly, next time.

For the first move once a problem is on the table, see After you name it: how to find one sensible next step. For naming it well in the first place, see Name the problem before you solve it. The words I use are in the glossary.

I'm not a doctor, and this isn't therapy. It's a way of seeing that helps me. If you are struggling, please talk to someone you trust or a professional.

Say it early, say it plainly, say it kindly. Then it's a problem the team can carry together.