A leadership philosophy is written in three layers: values (three to five single words like quality or candor), principles (seven to twelve sentences that turn each value into a rule you can follow), and actions (observable behaviors that make each principle visible to your team). Start with a 30-minute written brain dump, sort it into the three layers, then review it quarterly.
Key takeaways
- A leadership philosophy exists for high-pressure moments. You build it when your thinking is calm so you can check decisions against it when it is not.
- Cap your values at five. Past five, they become too broad to remember and stop guiding decisions.
- A good principle is pointed at a real temptation you face, not a generic virtue.
- A value nobody can observe is a preference. Every principle needs an action your team can see.
- Write it down instead of thinking it through. The generation effect means self-produced material sticks far better.
What is a leadership philosophy?
A leadership philosophy is a written document that defines what you stand for as a leader and how that shows up in daily behavior. It is not a slogan on a wall or a journal exercise from an offsite. It is a document you open regularly, iterate on, and use to make decisions, show up consistently, and articulate to your team, your stakeholders, and new hires what kind of leader you are.
Most managers never define one. Others write one once and never use it, usually because they built it the wrong way: as a list of nice-sounding words with no connection to how they actually operate.
Why do managers need a leadership philosophy?
Because the moment that tests you will not announce itself. Sometime in the next few months, a decision will land on your desk that makes half the room unhappy. It will show up on an ordinary Tuesday in a week that was already full, and you will have about a day to decide.
When everything goes well, nobody tests your principles. I call these stretches sunshine leadership. The team performs, there is no reorg, no conflict in sight, and a leadership philosophy looks like a nice-to-have. Then something breaks. A decision gets contentious. A strong performer starts to slip, or quits. Two people you like want incompatible things. That is when you find out whether you have a philosophy or whether you shoot from the hip, make emotional calls, and justify them afterward.
The most expensive cost of skipping this work is trust. One of the fastest ways to erode trust with a team is to hold your principles only while things go well. You said transparency matters, then something went wrong and you went quiet. You said no last-minute deadlines, then a client pushed and suddenly the team worked Saturday. Your team notices the deviation immediately, and they quietly sort your stated principles into the real ones and the decorative ones.
There is a second payoff: a defined philosophy travels with you. You adapt maybe 20 to 40 percent of how you show up to each company and team. The core stays. Managers without one rebuild their entire approach with every job change, reacting to what the boss wants, what the culture dictates, and what the team asks for, until they are acting in service of everyone but themselves.
Why do borrowed leadership methods fail?
Most leadership content hands you a method. Run your one-on-ones this way. Give feedback in that format. Delegate using this checklist. A lot of it is good. But if you adopt a method without knowing what you actually believe, every technique stays borrowed. It is a script you are running. When the script does not quite fit, you conclude the script was wrong. Usually it was fine. It was just not anchored to anything of yours.
In our programs at Archova, I describe this as handing you a block of clay. The resource is the material. It is on you as the leader to shape it into something that fits your kitchen, your situation. When you are clear on your leadership philosophy, the question of what to do with the clay becomes much easier, because you are checking every decision against something you settled on when your rational thinking was at its best, not in a moment of pressure.
This is also where a philosophy sits inside leadership development as a whole. In Archova’s APS method, awareness (what you know about yourself and your people) and system (your visible operating structure: one-on-ones, planning, feedback loops) sandwich the middle layer, principles. The middle layer is the one managers skip, because awareness feels like reflection and systems feel like tactics, but principles feel like neither. The rest of this article is how to build that middle layer properly.
What are the three layers of a leadership philosophy?
Layer 1: Values
Values are single words or short phrases: quality, growth, candor, ownership. Two rules govern this layer.
First, cap it at five. Past five, values get so broad and hard to remember that they stop guiding your work. You end up with a list on a document that never justifies or guides a single decision, which is the same as having no list.
Second, do not generate them from a list of nice words. Generate them from your own experience. Think about the leaders you admired most and what they specifically stood for. Think about the leaders who were hard to work for, because they are equally good teachers, just in reverse. What did they do that you promised yourself you would never repeat? Add the books that shaped you and whatever is already working in how you lead today.
Layer 2: Principles
A principle is the sentence that turns an abstract value into a rule you can actually follow. If I told ten people on a team “I am an honest leader,” I would get ten different answers about what that means. That gap is the entire reason value posters on office walls do nothing.
Two examples from my coaching clients. An IT manager holds the value of quality. His principle: do the right thing, not the easy thing, and not the fast thing. His team is incentivized to close tickets quickly because speed looks good on a KPI, so that principle does real work every time a shortcut looks compelling. An accounting leader holds the value of growth. His principle: embrace change, because in a constantly changing environment, stagnation is decline.
Notice both principles point at a real temptation, not a generic virtue. When I do this work with executive coaching clients, we usually land between seven and twelve principles total, up to about three per value. That range is specific enough to cover what you deal with week to week and short enough to remember. Not all of them are for public consumption. Some you communicate explicitly because you want your team operating that way too. Others are private standards. Both belong in the document.
Layer 3: Actions
Actions are what people can actually see. If nobody can observe a principle, it is not operating. The IT manager spotlights a ticket in his weekly team meeting that got solved properly rather than closed fastest, names the person, and has them explain why it mattered. His team learns what he values from what gets recognized, not from hearing the word quality. The accounting leader makes “what are we changing, testing, or improving” a standing category in quarterly planning, a real line item for the team and every person on it.
Here is the test for this layer. If I followed you around for two weeks with no access to your stated values, could I reconstruct them from your behavior alone? If not, you either have no philosophy or you have a document that does not shape your day-to-day leadership. A value nobody can observe is a preference.
What if your values conflict with your career goals?
This is a trap worth checking. A client once named servant leadership, inclusivity, and empowerment as her values. Her top goal was to advocate for her own work and get more visibility with senior leaders. Every value she named pointed outward, toward other people. So when the moment came to speak up about her own contribution, the internal authorization was not there. She redirected the credit to her team, every time.
The fix is not dropping the value. It is bridging it. Her new principle: I do good work and I talk about it, because if people do not know what I am doing, they will not bring me into the work where I can serve the organization most. With that sentence, self-advocacy sits under servant leadership instead of contradicting it. Map your values against your stated goals, and wherever you find a conflict of interest, write the bridge.
How do you start writing a leadership philosophy?
Write it down. Do not think it through on a commute or a walk. Cognitive psychology calls this the generation effect: material your brain produces itself is retained substantially better than material it consumes. There is even research suggesting pen and paper beats typing for how deeply material gets processed, though any writing you will actually revisit works.
Block 30 minutes this week and put it on the calendar as a meeting. Do not structure anything at first. It is a brain dump: values, lessons learned, dos and don’ts, leaders you admire and why, what is working and what is not. Many people stall because they want the first draft organized, values first, then principles, then actions. That is not how I recommend starting. Get it all out, then sort it into the three layers, then mark which parts you want to communicate to your team, your manager, and even candidates in interviews. Telling a candidate “here is what kind of leader I am and what you can expect” builds trust before day one, and it lets people self-select.
How often should you review your leadership philosophy?
Quarterly, as a baseline, because your role and your team keep changing and some principles will need adjustment. In the beginning, while the document still includes aspirational items that are not yet second nature, read it weekly or even daily so you can recall your principles in the moments that count. The version you write this week is a first draft, not something set in stone.
Sports teams do not invent plays on game day, and businesses do not discover their strategy mid-crisis. The decision that tests your leadership is already on its way. You can build the compass before you need it, or you can make the call on instinct and hope.
Want to go deeper on this with structure and support? The Leadership Accelerator is our 12-week program for new and early-stage managers, and defining your leadership philosophy is part of the work.
Frequently Asked Questions
- q: “Should I share my leadership philosophy with my team?” a: “Share part of it. Some principles you communicate explicitly because you want your team operating that way too. Others are private standards about the kind of leader you are trying to be. Both are legitimate parts of the document.”
- q: “Does a leadership philosophy change when you switch companies?” a: “The core travels with you. Expect to adapt roughly 20 to 40 percent of how you show up to each company, culture, and team. If you find yourself rebuilding your whole approach with every job change, you are reacting to others instead of leading from your own philosophy.”
- q: “Is a leadership philosophy the same as a leadership style?” a: “No. Your style is your natural default, and it exists whether you examine it or not. A philosophy is deliberate: written values, principles, and actions you can check decisions against. Your natural style feels comfortable, but comfort and effectiveness are not the same thing.”
- q: “Should I write my leadership philosophy by hand or type it?” a: “Handwriting has a research edge for retention, but the bigger win is writing at all instead of just thinking about it. Use whichever format you will actually open, edit, and reread.”
- q: “What is an example of a leadership principle?” a: “An IT manager whose value is quality uses the principle ‘do the right thing, not the easy thing, and not the fast thing.’ It works because it targets a real temptation his team faces: closing tickets quickly to look good on a KPI.”
- q: “What if my leadership philosophy still feels aspirational?” a: “That is expected in a first draft. Read it weekly, even daily, until the principles become second nature, and treat the document as a draft you revise, not a monument.”
