Personal branding when you cannot show your work
Almost every piece of personal-branding advice assumes you have a portfolio. Engineers, product managers, doctors and financial advisers mostly do not, for four different reasons. Here is what replaces it.
Nearly all advice about building a personal brand contains an unexamined assumption: that you have something to show. Post your work. Share your process. Build in public. Let the portfolio do the talking.
For a large fraction of skilled professionals this advice is not merely unhelpful, it is inapplicable, and the failure is silent. Nobody writes "this guide assumes you can publish what you make." So the reader concludes the problem is them — that they are insufficiently disciplined about posting — when the actual problem is that there is nothing they are permitted to post.
While building fifteen profession pages we had to work out what each one's real constraint was, and this turned out to be the thing several of them shared. It is worth separating, because "I cannot show my work" is not one problem. It is four, and they need different answers.
The four reasons work goes invisible
1. It is legally confidential. A commercial lawyer's best work is a contract nobody else may read. A financial adviser's is a plan belonging to one household. The output exists, is excellent, and disclosing it is a breach.
2. It belongs to an employer. A software engineer has years of work inside private repositories, under NDA, credited to a team. It exists and it is not theirs to publish. This is close to unique among skilled trades: a designer has a portfolio, a writer has clippings, an architect has buildings — the engineer has a commit history nobody outside the company can see.
3. There is no artefact at all. This is the strangest one. A product manager produces decisions, and a decision looks like nothing afterwards because the alternative was never built. The counterfactual is where the value was, and the counterfactual is invisible by construction. You cannot photograph the thing that did not get shipped.
4. Showing it would be a violation of a different kind. A doctor's work is a person's medical care. There is no anonymised, tasteful version of that which is also true.
These need different responses, and lumping them together as "just share more" is why the advice fails.
What replaces the portfolio
The move in every case is the same in shape and different in content: stop trying to exhibit the output, and publish the judgement that produced it.
A portfolio is evidence of capability. It is not the only kind. The other kind is demonstrated reasoning: showing how you decide, on problems whose particulars you are free to discuss, in a way that a reader with the same problem can evaluate.
This is not a consolation prize. In several of these professions it is strictly better evidence, because a portfolio shows what you did once with a team behind you, while reasoning shown repeatedly across many cases shows something closer to what hiring someone actually gets you.
For confidentiality (lawyers, advisers)
Publish the general shape of a problem you have solved many times, with all particulars stripped, and be specific about the trade-offs rather than the parties. "Here is the clause people get wrong in a first commercial lease, and here is why the wrong version looks reasonable" is publishable, useful, and gives away nothing. It also demonstrates more than a redacted contract would.
For employer ownership (engineers)
The material is the class of problem, not the codebase. You cannot publish the migration. You can publish what you learned about migrations of that kind: what the plan assumed, where the assumption broke, what you would check first next time. None of that is your employer's property, and it is the part another engineer wants.
The trap is that this feels like giving away the interesting part. It is not. The interesting part was never the code — it was knowing which of five reasonable approaches would survive contact with production, and that is exactly what this format shows.
For no artefact (product managers)
The response is the hardest and the highest-return: publish the decisions, including the ones you got wrong.
A PM's public record is almost never a product. It is a body of writing about how choices were made, what was traded away and what happened next. And the ones you got wrong are not a liability here, they are the credibility, because a record of only good calls reads as selection rather than judgement — every reader knows nobody is right that often.
For the ethical bar (doctors)
Move up one level: publish about the field, not the case. What patients consistently misunderstand, what the evidence actually says versus what circulates, how to read a study. No individual appears, and the expertise is fully visible.
The thing that makes this hard, and it is not the writing
Here is the part most advice skips. In every one of these four situations, the work you can publish is not the work you are best at. It is a secondary artefact — an explanation of judgement rather than an exercise of it.
Which means it will feel like a poor substitute, and the internal objection is always the same: this is not what I actually do. True. It is the visible shadow of what you do. Nobody outside your employer was ever going to see the thing itself, so the shadow is not competing with the real work. It is competing with silence.
Consistency matters more here, not less
One more asymmetry worth naming.
When you have a portfolio, inconsistency in how you write about it is survivable, because the work carries the impression. When the writing is the evidence, every drift in voice, formality or subject dilutes the only signal you have. A body of work that reads as five different people is not a reputation, it is five weak ones.
That is the failure we call brand drift, and it is worse in this situation than any other, because there is no artefact underneath holding the impression together. The defence is boring: decide what you sound like and what you refuse to say, write it down, and check the archive rather than the individual post. We wrote about the mechanism in how to catch brand drift, and about the vocabulary that makes it hard to discuss in six branding words used to avoid a decision.
Where to start
Pick the closest of the fifteen profession pages — each one starts from the structural fact about that job rather than from generic advice, and each carries a real generated persona for it. If yours is not there, the four categories above will tell you which of them you are in, and the answer for your profession is almost certainly the answer for the category.
Then write the first piece about a decision, not a result. The result is the part you are not allowed to show. The decision is the part that was always yours.
The three pillars each profession page carries are pillars rather than topics, and the difference decides whether they generate anything: content pillars are not content categories.

