I Spent Thirty Years Making Sure the Room Noticed Me. This Week the Job Was Making Sure It Didn't.
Tuesday I wrote "I'm no attention getter" in my journal. Wednesday I wrote almost the same sentence again. Two nights in a row, unprompted, like my hand kept circling back to check if it was still true.

Part 17 of an ongoing series. [Start from Part 1.]
For thirty years, getting noticed was the job. You don't survive as a Creative Director by doing quiet, competent work in the corner and hoping someone finds it. You survive by being in the room when the account gets pitched, by defending the idea when the client wants to gut it, by making sure your name is attached to the win before someone else's is. I got good at that. Not always likeable while doing it, but good. Being the loudest, most confident voice in the room wasn't a personality quirk — it was load-bearing. It's how the work got made and how you got paid.
This week I'm an intern doing pentesting by cross-referencing. Startup findings against Expert findings, Expert against Startup, back and forth, making sure nothing contradicts and nothing got missed. I wrote up tickets. I documented. Tuesday night I sat down to reflect and typed: I'm no attention getter. Wednesday, without remembering I'd already said it, I wrote it again, plus the follow-up — I keep my mouth shut, I don't need to make myself more important than I are. Grammar wrong, point exactly right.
I don't think that's a coincidence and I don't think it's small. That's thirty years of one operating system getting quietly overwritten by a different one, and my own hand kept flagging it before my brain caught up.
Here's the part that's actually interesting, not just the confession part: the new operating system is working. Tuesday's entry didn't stop at "I'm no attention getter." It kept going — I can work in fast-moving, fast-changing environments, and then, almost like I didn't fully believe it as I wrote it: I deliver more than the other interns, I think. That "I think" is doing a lot of work in that sentence. It's not false modesty. It's a guy who spent three decades being told, loudly and often, exactly how good his work was, now sitting in a Tuesday-night journal entry not sure if he's allowed to say it about himself anymore.
Same day, I gave the heads-up on something — I don't even remember what triggered it, just that I flagged it — and I noted afterward that I seemed to be the only one who did. Not "I was the hero." Just: I noticed, I said something, nobody else did. That's not a Creative Director move. A CD notices something and calls a meeting about it. An intern who's actually paying attention just quietly says the thing and goes back to the ticket queue.
Wednesday added the detail that made the whole week click into place: Oumayma's system went down for over five hours. Not mine — someone more senior, someone I'd have every reason to assume has this more figured out than I do. And it stuck with me enough that I wrote it down as the moment of the day. Not because I was glad someone else struggled. Because it was proof, plain and logistical, that competence in this field doesn't mean things don't break. It means you handle it when they do, and you don't need the room's attention to do that either.
By Thursday the mantra had arrived fully formed — slow is smooth and smooth is fast — right alongside document everything and a small, strange line I want to keep: your muse wants to meet you at work. Not at the pitch. Not in the room where everyone's watching you perform the idea. At the actual desk, doing the actual cross-referencing, where nobody's clapping.
I keep looking for the moment where the advertising instinct and the security instinct fight each other, and this week I think I found where they actually agree instead. The old job taught me that the work has to survive scrutiny before you defend it publicly — you proof it, you check it, you make sure it holds before you put your name on it in the room. I just spent thirty years applying that principle to headlines and campaign decks. Now I'm applying it to tickets nobody outside a small team will ever read, and the instinct to get it right before anyone sees it is identical. The difference is I used to need the applause afterward. This week I didn't get any, and the work still felt finished when I closed the laptop.
I'm not going to pretend I've fully made peace with being invisible. The guy who used to need the room to notice him doesn't evaporate because I decided cybersecurity requires humility now. Some nights this week I caught myself half-performing competence for an audience that wasn't there — explaining a finding out loud to nobody, the way you'd rehearse a pitch. Old habits don't die, they just lose their room.
But I'll take "I deliver more than the other interns, I think" over thirty years of certainty I didn't always earn. The "I think" is honest. I'd rather be quietly right about that than loudly wrong about anything else.
About the author
- 30 years in creative leadership (in the ad industry as a Creative Director) taught me one core skill: dissecting complex systems and finding the flaw before someone else does. My tech roots run back to 8-bit machine code on a C64 (yeah – 80s, baby!) Today, I’m combining that legacy hacker curiosity with modern threat detection and offensive security. BATTLE-TESTED LOGIC: Decades of high-pressure problem solving and systems analysis. HACKER MINDSET: I don't just follow playbooks; I reverse-engineer how the attack path actually works. CONTINOUS SKILL-UP: CompTIA Security+ certified (among other certs), building home labs, and constantly training for L1 ops to future Pentesting.
Comments
Join the discussionNo comments yet. Be the first to comment.





