I spent my first year as a manager wearing another man's clothes.
My first proper boss ran a room like a stage act. Loud, funny, quick with a decision, quicker with a one-liner. People followed him out of the building and into the pub. When I got my own team, I did the only sensible thing I knew: I copied him. The pauses. The jokes. The march to the whiteboard mid-sentence.
Six weeks in, one of my engineers stopped me in a corridor and asked if something was wrong at home. Nothing was wrong at home. Something was wrong at work, and it was me. I was doing an impression, and the audience had noticed.

The business shelf sells costumes
Walk past the leadership section in any bookshop. Servant leader. Radical Candor boss. Founder-genius. Extreme ownership. Each one arrives with a full costume and a set of lines to deliver.
The costumes sell because they promise a shortcut. Someone else did the hard thinking, ran the experiment, survived the fallout, and wrote it down. You get the polished output without the scar tissue.
Trouble is, a playbook is a record of what worked for one person, with one team, in one context, at one moment. Strip out the person, the team, the context and the moment, and what remains is a script. Scripts read badly when the room asks an unscripted question.

Herminia Ibarra named my exact problem
Years after my corridor moment, I read Herminia Ibarra's The Authenticity Paradox in Harvard Business Review, and winced my way through it.
She splits leaders into two groups. Chameleons try styles the way you try new clothes, adapting to whatever the room wants. They rise fast and risk looking hollow. True-to-selfers hold their line no matter what the room needs. They keep their integrity and stall out, sticking with comfortable behavior long past the point where it fits the job.
I had been a bad chameleon: doing the costume without the conviction. Worst of both.
Her cases stung too. One leader, Cynthia, ran on radical transparency, then found the same openness gutted her authority in a bigger role. Her line stuck with me: being authentic does not mean you get held up to the light so people see right through you.
The trait you copy is rarely the trait you need
Here is the deeper problem with borrowing a style off someone you admire. You copy what you noticed. What you noticed is usually what got them promoted, not what made them good.
Tomas Chamorro-Premuzic has been banging this drum for years: organizations mistake confidence for competence, and reward the person who performs leadership over the person who does it. He also argues, in When Authentic Leadership Backfires, the opposite of what most of us assume. Adjusting your behavior to fit the situation tends to make you seem more trustworthy, not less.
So the loud, decisive boss I copied? The loudness was never the engine. Underneath the performance he was doing three quiet things I failed to see at 26: he made a call within a day, he told people the reasoning, and he took the blame in public. None of those need volume. All of them need spine.
I copied the volume.
My research says most of us live with the results
I ran a survey on bad bosses. 99.5% of respondents told me they have had one or more types of bad boss. Not a rounding artifact. Near enough everybody.
Sit with the arithmetic for a second. Almost nobody escapes. And most of those bad bosses were not villains. They were people running a borrowed playbook badly, in a context where it never fit, with nobody willing to tell them.
The costs show up in the engagement numbers. My partners at Step It Up HR point at the latest Gallup figure: 21% of employees engaged at work. Four out of five people are switched off, and a fair chunk of the reason wears a lanyard and holds a one-to-one with them every fortnight.
The Army handed me a playbook once
I learned my first leadership system in the US Army. Clear chain of command. Clear orders. Say it once, say it loud, expect it done. For eighteen-year-olds carrying heavy things in the rain, the system works. It is tested, and it saves lives.
I brought a watered-down version of it into a software company at 3pm on a Friday, aimed at a senior engineer with twenty years on the tools and a strong view about my architecture. The system did not work. She did not need orders. She needed me to stop talking and ask her what she saw.
Two good playbooks. Wrong room.
Write your own. In an actual notebook.
Ibarra's answer to all this is what she calls outsight: you get the perspective by doing, not by sitting still and introspecting. Try the behavior, watch the result, keep the evidence.
Mine takes the form of a notebook. Physical one, because typing lets me pretend I am thinking.
The method is simple:
- One page per rule. Write the rule in your own words, not the author's.
- Note where it came from. A book, a boss, a disaster of your own making.
- Log what happened when you used it. Date, situation, outcome. Two lines.
- Cross out what fails. Twice failed, gone. No sentiment.
- Review it every quarter. Ten minutes. Most rules survive. Some quietly stopped being true a year ago.
Over time the notebook stops being a collection of other people's ideas and turns into a record of your own behavior under pressure. Nobody else has your version, because nobody else ran your experiments.

A few pages from mine
Say the number. "Soon" and "high priority" are noise. Give the date, the cost, or the risk percentage, and let people argue with something solid.
Ask twice. The first answer is the polite one. The second answer, after you sit through the silence, is the true one. I learned this from a QA lead who told me a release was "fine" and then, forty seconds later, told me what was broken.
Bad news goes up before it goes sideways. My team learned they never got punished for early bad news. They got punished for late bad news. One rule bought me more visibility than any dashboard I ever built.
Silence is a tool, not a weapon. Borrowed this from a boss who used it well, then watched a different boss use the same silence to make people squirm. Same behavior, opposite intent. Context decides everything.
Do the impression check. If I hear myself sounding like someone else, I stop and say the plain version instead.
Five rules. None invented from scratch. Every one of them earned a page by surviving contact with a real team.
Steal freely, copy nothing
None of this argues against reading. Read all of it. Take Ibarra's outsight, take Radical Candor, take whatever your own bad boss taught you by counterexample.
Take the parts. Leave the costume.
The leaders I trust most have all done the same thing: assembled something odd and specific out of borrowed pieces, tested against their own teams, and revised when it stopped working. Their playbooks look nothing like each other. Not one of them came off a shelf.
So, what is on page one of yours? And when did you last cross something out?