302. Positioning: who we are, who you are

A page can name a drawing tool, a font format and three rendering engines before it has said whose problem they solve. The information may be accurate. The reader is still left to assemble the invitation.

Positioning begins by choosing the work this page addresses and the supported difference that makes the product worth considering for it. That choice gives the writer a subject, a sequence and a reason to leave some perfectly good facts for another page.

The result should be easy to say plainly: what the product helps this reader do, why that matters in this context, and what evidence supports the claim. A memorable phrase can come later. It needs somewhere factual to stand.

Choose a task before describing an audience

An occupational label is a starting point, not a complete account of need. Two type designers may be drawing different kinds of families, working at different stages, and trying to solve different problems. A maker's equipment and intended output may matter more than the word maker.

Describe the job and relevant constraint. What is the person trying to produce, inspect, decide or change? What makes their current approach awkward? What product behavior could alter that situation?

Use evidence from actual work where available: interviews, questions, supported use cases, observed workflows or customer accounts. Mark hypotheses as hypotheses. Do not invent a deadline, fear or buying motive because a persona worksheet contains a field for one.

The audience becomes useful to the writer when it changes the first explanation, the evidence selected and the terms that need a gloss. If the same paragraph would be sent unchanged to every group, the audience list has not yet made a writing decision.

Separate fit from exclusivity

A product difference does not have to be unique in the world to matter to a reader. It must be relevant, supported and stated at the right scope.

A page can explain how several capabilities work together for a task without claiming that no other tool can perform any of them. A familiar category name can help a reader place the product. The next sentences should explain the particular fit.

If exclusivity, superiority or a comparison is part of the intended claim, gather evidence for it. A feature name alone does not establish that the feature is better, faster or more reliable than an alternative.

Avoid reducing positioning to one mandatory adjective. A concise idea can help people remember the offer, but the page still needs enough substance to distinguish professional use, supported workflows and relevant limits. “Professional” is a word to explain through the work, not a substitute for explaining it.

Let the reader's question choose the entrance

An engineer seeking an exact output contract may want formats, fields and conditions immediately. A designer encountering the feature for the first time may need the visible result before the mechanism. Neither order is inherently more respectful.

Introduce technical terms according to the task and likely knowledge. A short gloss can keep a newcomer with the explanation. Repeating elementary definitions on a specialist page can delay the answer.

The paragraph can develop from an object the reader recognizes: a pair of proofs, a family of masters, a source image or a file arriving in another application. Then explain the behavior that changes the work. The detail earns attention because it belongs to the task.

Do not turn a broad category into an assumed emotional state. An expert can be unfamiliar with one feature; a beginner can have a precise production requirement. Address the actual question before applying the persona's costume.

Use FontLab and Vexy tasks at their real scope

FontLab's potential audiences include people drawing type, engineering fonts, turning lettering into a font, and learning the relevant tools. These are useful working categories, not evidence that every member values the same feature or has the same purchasing motive.

For a drawing task, an editable contour or a way to compare masters may be the relevant detail. For an engineering task, the exported contract or a repeatable operation may matter more. Verify the feature and its conditions before making it the page's proof.

Vexy Lines can be explained through the relation between source images, patterns and resulting artwork. Different intended outputs raise different questions: visual treatment, file format, line structure, or preparation in a receiving application. The question determines which verified behavior to lead with.

Do not turn “exports a supported vector format” into “runs on your machine without cleanup.” The second claim includes a receiving system, settings, material and production process that the format name does not establish. Likewise, a tool that helps inspect correspondence does not promise a finished variable font without further checks.

A broad product page can provide several clear routes. Give each route its own task and evidence instead of making one sentence carry every possible audience.

Build the claim from the mechanism

Trace the proposed benefit back to what the product actually does. Which action, state or output makes the benefit possible? Which part remains the reader's judgment or work?

An observed mechanism can support a practical consequence. A measured outcome requires the measurement and its conditions. A claim about customer preference requires evidence about those customers. Keep these kinds of support distinct.

For an explicitly fictional review tool:

• It places two selected proofs side by side.
• It marks differing text passages.
• It does not choose which version to approve.
• No review-time saving has been measured.

A supported position for a reviewer is:

Compare two proofs in one view and find the differing passages. The approval decision stays with you.

The product does a specific part of the task and leaves a specific part to the reader. That boundary makes the invitation clearer. A claim that it halves review time or eliminates mistakes would be another proposition, requiring another source.

Give the same facts different useful shapes

The fictional packet can meet several readers without becoming several products.

A reviewer checking revisions

Put the two proofs beside each other and inspect the passages that differ. The change is easier to locate; deciding whether to keep it remains your work.

An editor coordinating approval

The comparison view identifies text differences between two selected proofs. It does not approve either version.

Someone new to proof comparison

Choose the two proofs you want to compare. The tool displays them side by side and marks differing text, giving you a place to begin the review.

Each entrance selects a relevant relationship and level of explanation. None adds an approval workflow, a customer testimonial or a measured result.

Notice the cadence in the first version. A connected setup leads to a short boundary in the thought. The effect comes from attention to the division of work. It does not require a slogan about limitless control.

Develop recognition through particulars

A concrete detail helps a reader recognize the situation. “Review efficiency” is abstract. Two proofs with a changed sentence give the explanation something to point to.

Choose particulars from the source or identify an invented scenario. A filename, annotation or repeated action can carry more interest than several adjectives. Do not add a Friday deadline or an anxious customer merely to make the scene feel inhabited.

Understatement works when the fact already carries the implication. In the fictional comparison tool, “The approval decision stays with you” is a useful limit and a modest acknowledgment of the human work. It is stronger than claiming the product understands every editorial intention.

A longer paragraph can let the reader discover why the difference matters. Keep consequential conditions before the decision they govern. The invitation can unfold; the price or limitation must not become the surprise at the end.

State the offer's limits where they affect the choice

Fit includes supported platforms, input and output constraints, required work, availability, pricing and eligibility when those facts matter to the next action. Use the actual terms supplied for the offer.

A clear limitation can help the right reader assess the promise. It need not be turned into a compulsory “who should leave” sentence. A product may serve several tasks, and the available evidence may not justify advising a whole profession to choose another tool.

Avoid false exclusions too. If a product includes several methods, do not define it by claiming it cannot do one of them merely to sharpen the headline. A position selects the relevant capability; it does not rewrite the capability list.

A demo, trial, upgrade and purchase are different actions. Do not invent a trial duration or imply that a demo includes unrestricted export unless the offer establishes it. Name the next step and any consequential condition before asking for commitment.

Compare at an evidenced scope

A comparison can concern a previous version, another product or another workflow when the task calls for it and the evidence supports it. Preserve applicable house policy for the publication; do not invent a universal rule that all comparisons must target one kind of alternative.

Compare like conditions. A measured improvement over a prior version needs the input, versions and relevant test conditions. A feature comparison needs current sources for each side. A difference in available controls does not by itself establish better output or lower effort.

Do not mock another tool or its users. Someone considering the product may have good reasons for their existing choice. Explain the difference that matters to the task and let the evidence do the persuasive work.

If a comparison remains unverified, remove or narrow it. Replacing an unsupported competitor attack with an unsupported numerical boast has improved neither the position nor the reader's decision.

Keep a short message brief

Before drafting the page, write the practical decisions in working notes:

Question	What the answer controls
Who is reading, and what are they doing?	The entrance, vocabulary and examples
Which supported difference matters here?	The main claim
What can the reader inspect?	The demonstration or evidence
What could make the offer unsuitable?	Conditions and limits
What happens next?	The action and destination

Add uncertainties explicitly. A useful brief can reveal that the page needs more evidence before it needs a better headline.

There is no fixed number of proof points. Use enough to support the proposition and answer the relevant uncertainty. A named tool is evidence that the tool exists only when its existence is established; its name does not prove every benefit the paragraph attaches to it.

Keep secondary claims in order of relevance. This prevents a page from becoming a storage place for every department's favorite sentence.

Handle pressure to broaden the promise

“Can we make it broader?” may identify a useful second audience. Ask what task and evidence the addition brings. It may deserve a separate section or route without changing the first claim.

“Can we say production-ready?” requires a definition of readiness: for which output, receiving system and conditions? If those are not established, use the supported result instead.

“Can we say it saves time?” requires either a bounded explanation of a removed action or a measured outcome, depending on the wording. Be precise about which one the evidence provides.

These questions should improve the draft, not create a review ritual. Resolve the concrete claim, write the strongest supported version, and continue.

Review the position before polishing the headline

Ask what a reader can understand from the opening: product, task, relevant difference and next route. Then inspect whether the evidence answers the doubt the claim creates.

Read the page as a whole for shifts in scope. A careful heading can be undone by a broad image caption. A clear limitation can disappear in the short social version. Related surfaces should preserve the same offer even when their openings differ.

Test with suitable readers when possible. Ask what they understand the product to do, which terms remain unclear and what they would need to assess the offer. Record their actual responses. Silence does not establish rejection, and a positive comment does not establish purchase intent.

A positioning hypothesis becomes more useful when evidence changes it. Keep what the readers' work supports; revise the attractive idea that the work does not support.

Practice: change the entrance, preserve the offer

Use the fictional comparison-tool packet. Write one opening for a reviewer looking for changed text and one for an editor concerned about approval. Let each develop through the concrete proofs and the division of work.

Then write a one-sentence position that both could understand. It need not carry every detail, but it must not imply automatic approval or a measured saving.

For the second pass, remove the automatic marking of differing passages. The tool still places two proofs side by side. Revise every claim about locating changes: the comparison remains available, but the software's marking is gone.

Finally, add a supplied offer condition: the demo displays comparisons but does not save them. Write a next-step invitation that makes that boundary clear before the action. Keep it plain even if the preceding paragraph has a dry turn.

For a cadence check, underline the sentence that establishes the work, the one that explains the mechanism and the one that leaves a decision with the reader. Try combining the first two and shortening the last. Keep that arrangement only if the thought becomes easier to follow; emphasis is not improved by giving every sentence the same abrupt ending.

Checklist

• The audience is defined by relevant work rather than a decorative persona.
• The main difference is supported and matters to that task.
• Technical detail enters at the level the reader needs.
• Concrete observations create recognition without invented experience.
• Benefits retain the mechanism, remaining human work and evidence scope.
• Limits, terms and the next action remain visible.
• Comparisons are fair, current where needed and supported at the claimed scope.
• The message brief records uncertainty and excludes unsupported promises.
• Related surfaces preserve the same offer while varying their treatment.
• Reader feedback is reported as observed, without invented conclusions.