Repositioning Without Pretending

A sentence under its first hard question

A senior product designer, six years into the field, sits down to write the sentence. The first version is the version a year of restlessness has been preparing.

"I design AI-native product experiences."

It feels right. It uses the words the field is using. It points at the work the designer has been pulling toward.

The first hard question arrives in a hiring conversation a week later. A startup founder asks: "Can you walk me through the AI-native part of your last project?" The designer describes the brief, names the model, talks about confidence visualization in the empty state. Halfway through, they hear themselves describing what is mostly a chrome change around a feature an engineer drove. The sentence is doing more work than the project supports. The founder is polite. The follow-up question never arrives.

The designer goes back to the doc. The honest version is narrower. They look at three projects that actually shipped: a notification redesign that spent most of its weight on what the system should not surface, a confidence model in the document review tool, a backoff rule for an assistant that kept interrupting. The sentence is not about AI. It is about the restraint surface around AI.

"I design the restraint surface for AI features — what the system does not surface, when it backs off, and how the user sees uncertainty."

It is less impressive on first read. It is also defensible. Each clause points at a concrete artifact. The designer can take any of the three projects and walk it line by line through the sentence, and the sentence will hold.

Two months later, a product lead at a different company sees the line in the designer's bio, recognizes it as an answer to a problem they have, and writes. The sentence routes a conversation the first version would not have. The conversation turns into the role. The designer's title still says "senior product designer." The work the designer is doing under that title is narrower than "AI-native" and bigger than "chrome around features." The sentence is what made the routing possible.

The discipline is to write the version that survives the first hard question, even when the version that does not survive sounds better in the headline. The rest of the chapter is about that discipline — what a credible reposition rests on, what pretending costs, and how to write a sentence the work can hold up.

What pretending looks like

Repositioning is the part of the role transition that gets attempted before the work is ready. It is the bio rewrite, the title bump, the new headline that runs ahead of the practice. Pretending feels efficient — language is fast, and the gap between the language and the work seems like it can be closed later by working harder. The trouble is that the language gets read first, and the gap gets discovered shortly after.

Pretending shows up in a small number of recognizable shapes. The bio that says "product strategist" attached to a person whose last three deliverables were screen mocks. The title that calls someone a head of something with no team and no remit. The framework borrowed wholesale from a deck — the same six-bullet model that is on a hundred LinkedIn posts this quarter — applied to nothing. The talk delivered with confidence about a problem the speaker has not actually shipped a solution to. Each of these is a debt taken out against a future version of the work.

The bills come due in conversation. The recruiter who reads the bio asks one specific question — "can you walk me through the strategy work on your last project" — and the answer is shaped like a deflection. The senior peer asked to refer the builder hesitates because the work and the language do not match. The customer hears the framework, asks how it applied to the last engagement, and the engagement turns out to have been a feature spec. The reposition that ran on language alone gets exposed in the first hard sentence.

The cost of pretending is not embarrassment in any one moment. It is that pretending teaches the people around the builder to discount the language they hear from the builder going forward. Once the discount lands, undoing it takes longer than the original pretense did. The reposition that lasts has to be priced in evidence the language can rest on, not language priced ahead of evidence.

The three legs of an honest reposition

A credible reposition rests on three things, and the framework that follows names them. Each one is necessary. None of them is sufficient. Removing any single leg collapses the position.

Real capability. The first leg is the work itself — the actual practice the builder does with their hands, in real conditions, on real deliverables. Capability is not learned from a book. It is built in the friction this kind of work involves: prototyping behavior, naming tradeoffs, modeling systems, refusing depth where depth would not change the call. The capability leg is the slowest to grow, and it is the one most repositions skip past.

Visible proof. The second leg is what others can see of that capability. It is the body of artifacts that demonstrate the role — the reframings, the tradeoff documents, the behavior models, the workflow redesigns — accumulated in places someone who is not the builder can find them. The proof leg is necessary because capability that lives only inside the builder's head registers, to everyone else, as a claim. A claim is not proof.

Clear language. The third leg is the words the builder uses to describe what they do. Sharp, accurate, narrow enough to be defensible, broad enough to be useful. Clear language is the leg most builders skip — partly because it feels like marketing and partly because the temptation is to use the most flattering language available rather than the most accurate. Clear language without capability is bluster. Capability without clear language is invisible. Both legs need the third.

The three legs hold each other up. Capability gives the language something to stand on. Language makes the capability legible. Proof keeps the language honest by connecting it to the body of work. Pull any one out and the position falls. Most attempts at repositioning fail at one specific leg — usually language for the people who have done the work, usually capability for the people who have done the language, usually proof for the people who have done both but kept the work private.

Naming the role you can defend now

The hardest part of an honest reposition is naming the role you can defend now, not the role you want in two years. The aspirational name is always available; it costs nothing to write and it sounds better in the headline. The defensible name is harder to write because it is narrower, less impressive on first read, and more accurate to the work that has actually shipped.

This chapter is not asking for another proof artifact. That was the previous move. This one is about language: the sentence that lets the proof route the right work toward you without inflating what the proof can support.

The defensible name is usually one role transition narrower than the aspirational one. The builder who has shipped two reframings and one tradeoff document is not yet a strategic product builder; the defensible role might be product builder who frames the problem before solving it, which is a more accurate sentence and a less impressive sentence. The builder who has shipped a behavior model, a workflow redesign, and one decent tradeoff doc is not yet a product strategist; the defensible role might be product builder who designs the system, not just the screen. Less impressive. More true.

The discipline is to write the defensible sentence and live inside it for the months it takes for the next layer of evidence to arrive. The aspirational sentence will keep being available. The aspirational sentence will continue to be one or two artifacts away. Holding the defensible sentence — declining to inflate it, declining to round up — is the move that produces the trust the eventual reposition will rest on.

There is a counterintuitive thing about narrower sentences: they land harder. The hiring manager who reads "product builder who frames the problem before solving it" and recognizes the sentence in the work attached to it pays more attention than the one who reads "strategic product leader" and discounts the headline. Specificity is what makes a sentence defensible. A defensible sentence is a sentence with a body of work behind every word.

The sentence by role

The designer's case at the top of the chapter is one shape. The discipline holds across roles. Three short examples, each in the same voice as the designer's rewrite.

The frontend engineer does not need to become "AI product strategist." A more credible sentence is narrower: the engineer who designs recoverable interface behavior for uncertain systems, backed by working examples where state, failure, and undo were treated as product material.

The design engineer does not need to become "full-stack product architect" because the phrase sounds larger. The stronger claim is the builder who turns ambiguous product logic into working concepts that survive contact with failure.

The founder does not need to claim a category. The evidence can say something clearer: this is the person who authors the workflow the category has been wrapping.

Each sentence is narrower than the inflated version, which is why it is easier to believe — and why it routes the right work toward the builder instead of the wrong work.

Holding the position in conversation

The position is not held on the profile. It is held in conversation, every time someone asks what you do.

The phrase you reach for first is the position. The example you choose to illustrate it is the position. The framing you decline — "oh, not exactly that" — is the position. The work you do not call your own is the position. Most of the discipline of repositioning lives in those four moments, repeated across hundreds of small conversations.

The phrase has to be one sentence, learned by heart, and attached to one piece of work that demonstrates it in concrete terms. Together the sentence and the example form a tight unit. They leave the listener with a specific picture of what the builder does.

The test is not whether the sentence sounds impressive. The test is whether it helps the right work find you.

A useful position changes routing. It makes a manager ask for your help before the brief hardens. It makes a founder bring you into the workflow conversation, not only the interface review. It makes a client understand why your artifact starts with behavior before it starts with screens.

The other half of the conversational discipline is the willingness to let the position be small. The first version of the sentence the builder learns to repeat will sound modest compared to the aspirational one. The second version, six months later, will be sharper but still narrower than the long-term ambition. The third version will start to match the aspiration. The reposition that lasts is the one that grew this way — sentence by sentence, conversation by conversation, with the work always slightly ahead of the language.