> ## Content Index
> Fetch the complete content index at: https://presenceoverpolish.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# A Confession: The Time I Got It Wrong
- URL: https://presenceoverpolish.com/a-confession-the-time-i-got-it-wrong/
- Published: 2026-08-18T12:00:13.000Z
- Updated: 2026-08-18T12:00:13.000Z
- Author: Stacy McWhorter

I got promoted, and I panicked quietly.

Not the kind of panic anyone could see. I still ran the meetings. I still hit the numbers. But underneath it, I was terrified someone would notice I didn't actually know how to do this yet.

So I did what a lot of engineers-turned-leaders do. I went back to the thing I was already good at. I rewrote my team's reports before they went out the door. I sat in on calls I didn't need to be on. I asked for one more pass on analysis that was already solid, because I could always find something to tighten. I told myself this was diligence. I told myself I was being a helpful leader, still hands-on, still adding value.

I was not being helpful. I was being scared, and I was making it everyone else's problem.

Here's the part I didn't see happening in real time: my best engineer stopped bringing me his problems. Not dramatically. She just quietly started solving things on her own and only telling me after the decision was made. At the time I read that as growth. Look at her, getting more independent. It took me embarrassingly long to understand what it actually was. She'd learned that bringing me a half-formed idea meant it would come back covered in my fingerprints. So she stopped bringing them. She went around me instead of through me, and I don't blame her for it.

A year and a half later, she left. In her exit conversation, she was kind about it, which somehow made it worse. She said something like, *I never felt like you trusted me with the hard stuff.* I remember nodding like I understood, and driving home not understanding at all. I thought I'd been generous with my time. I thought I'd been thorough. What she experienced was a boss who couldn't let go of the wheel.

**Performing competence costs you the very trust it's supposed to earn.**

I wanted my team to see a leader who had it handled. What they actually needed was a leader who trusted them enough to let them handle it, including the parts where they'd get it wrong and figure it out. Every report I "improved," every call I sat in on that wasn't mine to sit in on, was me telling them, without saying it out loud, *I don't think you've got this.* I never meant to say that. I said it anyway, in the language leaders actually speak, which isn't words. It's where you put your hands.

The fix wasn't a framework. It was smaller and harder than that. It was letting a deliverable go out with a typo in it because it wasn't my deliverable to fix. It was sitting in a meeting and not speaking for the first twenty minutes to see what happened without me. It was, more than once, saying *I don't know, what do you think* to a question I absolutely could have answered myself. 

I think about that engineer more than she'd probably guess. Not with guilt exactly. Compassion, maybe, for the version of me who thought control was the same thing as care. She wasn't a bad leader. She just hadn't learned yet that the polish she was so carefully applying was the exact thing standing between her and the people she was trying to lead.

If you're in the stretch of leadership where you feel like you have to have every answer, you don't. You have to have the trust. Those aren't the same skill, and only one of them actually holds a team together.

If this one landed, I write about moments like this every week, the real ones, not the highlight reel. You can get them in your inbox, or if you're navigating your own version of this right now, I'd love to talk. [Join the newsletter](#) or [reach out about coaching](#) — either door is open.