Reader situation
You know your field well, and you want other members to know it too. Writing about expertise is awkward. Understate it and no one knows to ask you. Overstate it and people stop trusting what you say, or bring you questions you can’t answer well.
Central idea
Credible expertise is specific. It names the problems you have worked on, the part you played and the conditions under which your experience holds. When you also say where your knowledge stops, readers trust the rest of what you say, and they can judge whether you are the right person for their question.
Practical steps
- Choose an expertise area. Pick one or two areas where you would welcome questions, not every topic you have touched. “Pricing for B2B software” is a usable area. “Strategy” is too broad to help anyone decide whether to approach you. If you have several areas, describe the one most relevant to the people who will read this first.
- Identify supporting experience. List the specific situations that taught you what you know: projects, decisions, recurring problems, roles. For each, note the context. Industry, company size, region and stage all matter, because experience in a 40-person startup and in a global enterprise rarely transfers unchanged. Pick the two or three examples that best represent the expertise you claim.
- A useful test is whether you could talk about each example for ten minutes, including what went wrong. If you could only describe it at a high level, it may support a broader claim than your experience allows. Recent examples usually carry more weight than older ones, because practice in most fields changes over time.
- Describe outcomes accurately. Say what happened and what your part was. “I led the pricing review” and “I was part of the team that reviewed pricing” describe different roles; use the one that is true. If an outcome had many causes, say so. If you can’t share figures because of confidentiality, describe the direction and scale in general terms rather than inventing precision.
- Avoid words that claim more than you can show, such as “proven,” “world-class” or “transformed.” They ask the reader to take your word for it. A plain account of what you did and what changed lets the reader draw their own conclusion, which is more persuasive.
- State boundaries. Name what you don’t know, or know only secondhand. “I’ve worked mostly with subscription pricing and have little experience with usage-based models” saves the reader from asking the wrong question. Boundaries also include what you are not qualified to give, such as legal, tax or medical advice.
- Stating boundaries can feel like weakening your case. In practice, it does the opposite. Readers tend to trust a description that admits limits, and the questions you receive are more likely to match what you actually know.
- Adapt for a profile. Turn your notes into three or four sentences: the area, the experience behind it, an honest note on its limits and what kinds of questions you welcome. Keep the longer version for conversations where someone wants detail.
- Read the short version as a stranger would. Could they tell what to ask you about, and what not to? If the description would fit dozens of other people in your field, add one specific detail that only your experience includes.
Worked example
Fictional example
Before
Pricing expert. Proven track record of driving revenue growth across multiple industries.
After
I’ve spent eight years working on pricing for B2B software companies with 50 to 500 employees, first as an analyst and then leading pricing for two companies. Most of my experience is with annual subscription plans and moving customers between tiers. I’ve done much less with usage-based pricing or consumer products. I’m happy to talk through packaging decisions, price increase communication or how to structure a pricing review.
The second version is longer, but every sentence helps the reader. They know the context, the role, the limits and the questions to bring. A founder planning a first price increase can see at once that this person is worth asking. Someone designing pricing for a consumer app can see that they should probably look elsewhere, which saves both people time.
Boundaries
- Don’t claim results that belonged to a team as your own, or round up your role.
- Keep confidential client and employer details out, including names, figures and unannounced work.
- Credentials and titles can support a description, but they don’t replace saying what you actually did.
- Update the description when your work changes. Expertise you haven’t used for years may no longer reflect current practice.
One action to try with a professional peer
Write your expertise description using the five steps, then ask a colleague who has worked with you: “Is anything here overstated or missing?” Revise based on what they say.
Discussion prompt
When you read someone’s description of their expertise, what makes you trust it?
