The fluorescent light in the briefing room flickered with a rhythmic, percussive hum that felt like it was drilling directly into my temple. I was leaning against the edge of a mahogany table that cost more than my first car, watching the cursor on the screen blink with mocking regularity. I’d been awake for 22 hours straight. My eyes felt like they had been rubbed with coarse salt, a direct result of my failed attempt to go to bed early, which instead turned into a midnight spiral of adjusting the kerning on slide 102. I was ready. Or I thought I was. I had the data, the projections, and the architectural breakdown of the new system. Then Marcus, the vice president of some department whose name I could never quite remember, leaned back, tented his fingers, and delivered the killing blow.

The meeting ended 12 minutes later. No specific directions were given. No metrics for ‘sizzle’ were defined. I was left standing in a cooling room with a 92-page deck that was apparently lacking in ‘pop.’ It is a specific kind of corporate hell, a purgatory where clear objectives go to die and are replaced by the aesthetic whims of people who are too anxious to actually lead. We are told from our first day in a cubicle that feedback is a gift, a precious stone we should cradle and admire. But most of the time, the gift is a box of wet hair. It’s not meant to help you; it’s meant to help the person giving it feel like they’ve contributed without having to do the heavy lifting of thinking.

The Contradictions We Tolerate

This lack of precision is a disease. I’ve spent 42 hours this month alone trying to decode ‘I want it to feel more premium’ and ‘Can we make the UX more intuitive but also more complex?’ These are contradictions masquerading as insight. I once worked with a developer who received 32 different ‘urgent’ feedback points on a Friday afternoon. Not one of them included a technical requirement. They were all emotional reactions to a prototype that the stakeholders hadn’t even bothered to test. We are drowning in the ‘how’ because no one has the courage to define the ‘what.’

I’m guilty of it too. Last Tuesday, while running on 2 hours of sleep, I told a junior designer that a layout felt ‘a bit crowded.’ As soon as the words left my mouth, I felt the phantom sting of Kendall B.-L.’s disapproval. ‘Crowded’ is useless. I didn’t tell her which elements to prune, or why the white space was failing the hierarchy. I just dumped my vague discomfort into her lap and expected her to fix it. I was tired, I was irritable, and I used feedback as a weapon to get her out of my office so I could stare at the wall in peace. It’s a cycle of laziness that we’ve dressed up in the language of professional development.

The Recipe for Clarity

True guidance requires a level of intimacy and effort that most people aren’t willing to invest. It requires you to actually understand the work as well as the person who created it. It’s the difference between telling someone to ‘cook better’ and giving them the exact smoke point of an oil to prevent a sear from turning into a burnt mess.

On sites like coconut oil for cooking, you don’t find articles telling you to ‘make the food taste more vibrant.’ You find technical, definitive breakdowns of how heat interacts with different lipids. That is the clarity we are missing in our professional lives. We want the result without the recipe. We want the ‘wow’ without the work of defining what ‘wow’ actually means in a functional context.

In the 12 years I’ve been navigating these waters, I’ve realized that the most successful teams are the ones that have banned the word ‘feeling’ from their review sessions. They use numbers that end in 2, they use specific references, and they acknowledge when they don’t know what they’re looking for. There is an incredible power in a manager saying, ‘I don’t like this, but I don’t know why yet, so don’t change it until I figure it out.’ That is trust. That is the opposite of the ‘sizzle’ mandate.

Chasing Shadows

I think back to that meeting with Marcus. If I could go back, I’d ask him to define ‘pop’ using only nouns. I’d ask him which of the 52 slides failed the ‘wow’ test and what specific metric we were using to measure it. But I didn’t. I nodded, went back to my desk, and changed the font size by 2 points on every header. I added a few more gradients. I wasted another 12 hours of my life chasing a shadow. And the worst part? When I presented the ‘popping’ version a week later, he loved it. I hadn’t changed the strategy, the data, or the logic. I had just changed the costume.

Kendall B.-L. used to say that if you can’t explain why an argument is wrong in 12 words or less, you don’t understand the argument. We should apply that to our feedback. If you can’t point to a specific line, a specific pixel, or a specific data point that needs to change, then you aren’t giving feedback; you’re just making noise. You are managing your own relevance at the expense of someone else’s sanity.

Demanding Reality

I’m still tired. I still haven’t caught up on that sleep from 2 days ago. But I’m looking at my inbox now, and there are 22 new comments on my latest report. Half of them use the word ‘synergy.’ One of them asks if we can make the charts ‘breathe more.’