Personal Brand Statement

A 38-year-old director of product at a healthcare startup has a genuinely distinctive career: she started in clinical research, moved into user experience, and has spent the last five years building product from the ground up at two companies. She cannot tell the same story twice. In networking conversations she emphasizes different things depending on who's asking. On LinkedIn her headline says 'Product Director | Building at the intersection of health and technology' — a statement that describes the industry but nothing about her. She came to coaching because she's been passed over for two VP opportunities and received the same feedback both times: 'We weren't sure what you'd bring to this role specifically.' The brand statement worksheet structures her inventory and produces a 2-3 sentence statement that holds across contexts.

Frame this as ending the multiple-version problem. 'You've been telling different stories to different audiences, which means no one is hearing the full picture — they're hearing the version you thought they wanted. The brand statement worksheet walks through six prompts: your professional values, what you do best, who you serve, the problems you solve, what makes your approach distinctive, and where you're headed. Those six answers, taken together, produce a draft statement in 2-3 sentences that works in a networking conversation, a cover letter, and a LinkedIn headline — without changing based on who's in the room.' The driving force prompt is the one to slow down on: 'I want to understand what motivates the work across all three chapters of your career — the clinical, the UX, and the product. There's a thread running through all of it that the people interviewing you haven't seen yet.'

Watch for the six-prompt inventory to produce answers that are all output-framed — 'I build products,' 'I design experiences,' 'I manage roadmaps' — rather than impact-framed. The statement works when it describes what happens differently because she's in the room, not just what she does. Also watch for the driving force to be answered with the industry ('I care about healthcare') rather than with the underlying motivation that connects clinical research to UX to product. The industry is context; the driving force is what she's trying to accomplish within it. The draft statement usually fails when the driving force hasn't been identified — it reads like a job description rather than a professional identity.

Start with the six prompts before touching the draft statement: 'Read me your answer to the distinctive approach prompt. Not the statement — just that one answer.' Then: 'If someone who worked with you three years ago heard that description, would they recognize you in it?' That question tests whether the inventory is aspirational or grounded in observed behavior. Then go to the draft statement: 'Read me the 2-3 sentences you wrote. Is the distinctive thing about you visible in that statement — or does it sound like it could describe someone else in your field?' Close with the session starter: 'Think about the last time someone asked what you do and your answer felt exactly right. What made it land?'

A 47-year-old senior data scientist at a large telecommunications company has been at the same organization for twelve years. His internal reputation is strong — he's been promoted twice, leads a team of six, and is consistently brought in on high-stakes analytical projects. He has never had to sell himself externally. He is now considering a move following a restructuring and has sent five applications with no response. When asked to describe his professional value in two sentences, he produces a list of technical skills and tools. He came to coaching to 'figure out what to do next.' The personal brand statement worksheet is introduced to convert internal reputation into externally legible value — translating the context-specific reputation that insiders understand into language that means something to someone who has never worked with him.

Frame this as translation work, not reinvention. 'Your value isn't the problem — the language is. Inside your organization, people know what you've built and what happens when you're on a project versus when you aren't. Outside it, you're describing a tool stack, which looks identical to fifty other data scientist resumes. The brand statement worksheet takes the same underlying value and puts it in language that works for someone who has never seen your work.' The driving force prompt is key: 'Twelve years at one company means you stayed for a reason — or several. I want to understand what that reason was, because it's usually connected to what you'd want from the next place. That's part of the statement too.' The produces section is what to anchor the session on: six-prompt inventory, then a draft statement in 2-3 sentences that works without context.

Watch for the inventory to produce answers that depend on insider context — 'I built the churn prediction model that reduced customer attrition by 18%' is impressive to someone who knows what that model replaced, but inert to someone who doesn't know the starting state. Push for the statement to work without the backstory: what is the pattern of problems he solves, across different contexts, using different tools? Also watch for the distinctive approach prompt to be answered with technical methodology ('I use ensemble methods') rather than with the behavioral or strategic pattern that makes him effective — how he frames problems, how he works with non-technical stakeholders, what he does that the tool documentation doesn't require.

Start with the driving force prompt: 'Read me what you wrote. Why did you stay for twelve years?' Let him answer. Then: 'Is that same thing available in the kind of role you're looking for — or is this a pivot as well as a search?' That question tests whether the brand statement needs to include a directional element or can stay descriptive. Then go to the draft statement: 'If a hiring manager in [target industry] read this statement, without knowing your company or your twelve years of context — what question would they want to ask next?' A good brand statement produces the right next question. A generic one produces silence. Close with: 'Before we jump in, take a moment to think about the last time someone asked what you do and your answer felt exactly right. What made it land?'

A 43-year-old former nonprofit executive director is moving into organizational consulting. She has fifteen years of running complex organizations, managing boards, building coalitions, and executing change in resource-constrained environments. She has identified the consulting firms she wants to approach. She cannot write a one-page version of her value that a consulting partner would recognize as relevant. She frames her nonprofit background as a liability rather than a differentiator — she believes she needs to apologize for it before claiming credibility in the new space. She came to coaching to work on the transition. The brand statement worksheet is introduced to reframe the nonprofit experience as evidence of the consulting competencies the target audience cares about.

Frame this as building the bridge, not hiding the river. 'You've been treating your nonprofit background as a credential deficit. I want to reframe it: fifteen years of running an organization without margin for error, with a board, in a resource-constrained environment — that's a harder context than most consultants have ever worked in. The brand statement worksheet asks you to identify your distinctive approach. I want that answer to be specific about what running organizations in hard conditions actually develops, because that's the differentiator, not the liability you've been carrying.' The six-prompt inventory is the core work: 'I want the problems you solve prompt to be answered in language a consulting partner would recognize — not nonprofit language, not organizational management language, but the language of the problem they're selling to their clients.'

Watch for the inventory to continue using nonprofit framing even after being asked to translate — 'I run strategic planning processes' rather than 'I help leadership teams make consequential decisions under uncertainty and resource constraint.' The translation isn't about pretending the nonprofit work didn't happen; it's about naming the competency the work demonstrated rather than the sector it happened in. Also watch for the draft statement to include an apology or a distancing phrase — 'While my background is in the nonprofit sector...' — which signals to the reader that she thinks the background is a problem. The statement works when the nonprofit origin is implicit context and the consulting value is explicit foreground.

Start with the problems you solve prompt: 'Read me your answer. Is that the problem description a consulting firm's client would recognize as their problem — or is it the problem description of a nonprofit executive?' That question tests the translation directly. Then: 'Now read me the draft statement. Does it include any version of 'although' or 'despite' or 'while my background is'?' If it does, that phrase is where the apology lives — it needs to come out. Then go to the driving force: 'What is it about organizational change that you've spent fifteen years doing this work to accomplish?' Close with the session starter: 'Think about the last time someone asked what you do and your answer felt exactly right. What made it land?'