The Question Most People Get Wrong
Simon Sinek's model for finding your Why is deceptively simple. Gather your stories. The moments when you felt most proud, most yourself, most alive. Bring a trusted person into the room. Not a spouse or family member, someone who can listen without an agenda. Share the stories. Look for the patterns. Draft a statement in the form: to blank so that blank.
Most people approach this like a job posting. They think the " why " is something they need to construct, something aspirational and polished that can go on a resume or an about page. They sit down and try to invent it.
That is not how it works.
Your Why is not invented. It is uncovered. It was already operating in your life before you had language for it, before you could articulate it, before you thought to look. The stories are not raw material for building something new. They are evidence of something that has always been true about you. The work is not creation. It is an excavation.
I did not understand this when I started the process. I understood it about halfway through, sitting with a folder full of stories and feeling something shift. Not a revelation exactly. More like recognition. Like finding a word for something I had been trying to describe for years.
What the Stories Had in Common
The process asks you to review your stories and identify themes. Not in what happened, but in the role you played. What did you contribute? What did you create for others? What is the consistent impact across all of it?
I wrote about the Land Cruiser: my father teaching me to read a negotiation the same way he taught me to box, question by question, jab by jab, until the moment to close arrived. I wrote about driving a pickup across Nevada at fourteen, tossed the keys with no ceremony and a quiet expectation that I would rise to it. I wrote about painting an entire Victorian office building that summer, brush in hand, friends honking from cars headed to the lake, because that was the deal I had made and I was going to see it through.
I wrote about coaching my son's basketball team, about the Dads Campout, about rebuilding teams through two career crossroads, three companies, and a decade of enterprise sales. About the moments that felt most like me: bringing people together around something that mattered, pushing them further than they thought they could go, making sure they knew I had their back while I did it.
Five themes surfaced throughout it. Building connection and belonging. Designing environments where people can thrive. Showing up strongest in adversity. Developing people to reach their potential. Protecting and passing forward the lessons that shaped me so they outlast the moment.
The pattern was not subtle once I saw it. It had been there my whole life. I just had not named it.
The Statement
My Why: to build people and teams through trust, challenge, and example, creating environments where they belong, grow beyond their limits, and become who they are meant to be.
When I read it back, it felt accurate in a way that surprised me. Not because it was new, but because it was true. It described every moment I had felt most myself. It explained every career decision that had felt right and every one that had felt wrong. It fit.
A Why statement is not a mission statement. It is not a goal, a strategy, or a brand. It is a description of how you are already wired, expressed clearly enough to be useful. When you have it, you can hold any opportunity up to it and ask, "Does this let me do this thing?" When the answer is yes, you feel it. When the answer is no, you know that too, even when the opportunity looks right on paper.
I have used it that way since. In hiring decisions, in the way I run team meetings, in the conversations I choose to have, and the ones I choose to leave. It does not make every decision easy. It makes it honest.
With Eyes Open
There is a version of the Why I drafted first, and another I live with now. The difference is four words I added later: without losing myself in the process.
I have a few traps I fall into when I am not paying attention. The achievement trap: measuring my worth by my last result, working to prove something rather than build something. The image trap: performing a version of success rather than living the real one. The people-pleasing trap: saying yes to everything, taking on other people's emotions as my own, avoiding the hard conversation that needs to happen. The efficiency trap: moving so fast that I optimize for tasks and lose the people inside them.
None of these traps feels like a trap when you are in them. They feel like commitment, or responsibility, or competence. They feel like the right thing. That is what makes them worth naming.
I can build impressive results while slowly losing myself in the process. I can look like I am thriving while actually burning out. I can create a sense of belonging for everyone around me, yet feel disconnected from my own life. When I am in the achievement trap long enough, my team starts to fear disappointing me more than they trust that I have their back. That is the opposite of what I am here to build.
So now I run a check. Not on my results. On my alignment. Am I being my real self in this role, including my mistakes and my uncertainty? Am I excited about the work itself, or just the recognition that comes with it? Will I leave with people developed, not just numbers achieved? Would I be proud to tell my kids about this work in twenty years?
The Why has not changed. What changed is that I am living it with my eyes open.
What It Asks of You
Finding your Why is not a one-afternoon exercise. The two hours you spend gathering stories and drafting a statement are the beginning, not the destination. The harder work is everything that comes after: learning to use it, learning to notice when you have drifted from it, building the practices that bring you back.
The people I have walked through this process with have found the same thing I did. The why was not a surprise. It was a recognition. They already knew it, in the way you know something you have never stopped to say out loud. The process just gave it language.
And language matters. When you can say clearly what you are here to build, you can recognize it when it is present and notice when it is absent. You can make decisions from it instead of around it. You can lead from it rather than perform around it.
Finding your Why is the work of finally knowing what you have been carrying all along.