The Position Problem

You finish the page, the pitch, the proposal. You’ve read it a dozen times. Something feels off but you can’t name it. You send it to someone who hasn’t seen it. In ten minutes they say: “this line sounds generic” or “I don’t know what you’re asking me to do.” You immediately see it. Of course. It was right there.

Almost everyone draws the wrong conclusion from this. The assumption is that the person who spotted it has better taste. What actually happened is that they had better position.

Taste and position are not the same thing. Taste is the capacity to distinguish what works from what doesn’t. Position is where you’re standing when you try to use that capacity. You can have excellent taste and terrible position at the same time. When that happens, your taste becomes functionally inaccessible. The blind spot isn’t a deficit in judgment. It’s a deficit in vantage point.

This distinction matters because the two problems have different solutions. If you lack taste, you need exposure and training. If you lack position, you need distance and perspective. Treating a position problem as a taste problem is a long detour.

To see clearly, two things have to work at once: a wide reference library, and enough distance from your own work to use it.

The reference library question is whether you’ve seen enough examples to recognize patterns. Design taste at a practical level is pattern-matching against things you’ve seen. When “we’d love to hear about your challenges” appears in copy, someone with a wide reference library immediately recognizes it as the same sentence on ten thousand other sites. Without that exposure, it reads as normal. There’s no category to match against. You can’t see a pattern you’ve never learned to name.

The distance question is harder, because distance goes to zero as you work. The first time a reader encounters your work is the only time that matters for their first impression. You’ve read yours a hundred times. The surprise is gone, the ambiguities have resolved, the gaps have filled in with what you already know. When you wrote “Engineering Partner” you knew what you meant: deep embedding, operator-level work, real outcomes. A business leader at an inflection point reads it as “dev shop.” You couldn’t see the gap because the meaning was already loaded in your head before you read the words.

What makes position problems hard to fix is that they’re invisible from inside.

The first thing to understand is that your judgment didn’t fail. It was working on a different object than the reader’s. You were evaluating what you meant to say. They were evaluating what was actually on the page. These are not the same read.

The second thing is that proximity accumulates invisibly. Every revision pass uses up a little more of your first-read capacity. By the time you think you’re done, you’re not reading anymore. You’re remembering. You see the version in your head, not the version on the screen.

The third thing is what you might call the addition trap. Builders add. You add a section, then a supporting point, then icons to make it look finished. Subtracting feels like losing work. But the move that would make the thing better is often removal. The insight that four icons on a services card make it feel like a template runs counter to the instinct of someone who spent time adding those icons. From inside the work, addition feels like progress. From outside, it often reads as noise.

The fourth thing is that the gap between what you know and what you’ve said is always larger than you think. You know the thinking behind your positioning. You know why the headline works. You know what the bold claim is grounded in. The reader knows none of that. They only have what’s on the page. The question isn’t “does this make sense to me?” It’s “what does this say to someone who knows nothing about me?”

The fifth thing is that perspective is manufacturable. Reading as a stranger, printing the page and looking at it from across the room, leaving days between drafts, asking someone you respect to tell you what they think it’s about. None of this requires talent. It requires the discipline to recognize that you’ve lost your first-read capacity and to go get it from somewhere else.

A few questions help test whether you’re reading your own work or remembering it. Can you say what the reader would think before they reach the next line, or do you only know what you intended? If someone who didn’t know you read only the headline, what would they conclude you do? When a line sounds fine, are you evaluating it or filling in the meaning from context? How many times have you read this without changing anything?

This gets complicated at the edges. Distance can become an excuse. “I need more perspective” can mean “I’m avoiding the discomfort of shipping.” There’s a version of this framework that justifies endless revision by dressing it up as taste. The goal isn’t infinite distance. It’s one more honest read from outside your own head.

The framework also breaks down when proximity is actually useful. Deep familiarity with your domain prevents obvious errors that a fresh reader wouldn’t catch. A doctor editing a medical paper benefits from knowing things the general reader doesn’t. The position problem is specific to communication, where the reader’s first-read experience is what you’re optimizing for. If you’re optimizing for accuracy, closeness is an asset.

The most expensive creative blind spot isn’t lacking taste. It’s lacking the position to use the taste you already have.