Name the Pattern — Give Recurring Value a Name People Can Remember
A pattern becomes powerful when it can be named. Naming is not slogan-making; it compresses recurring evidence into language others can understand, remember, and verify.
An unnamed pattern is difficult to remember
People may sense a connection across Projects, but without language they struggle to carry that perception forward.
Do not start with a slogan
Start with evidence: recurring Problems, Judgment, Principles, and Results. Discover the name from the work.
Pattern → Language → Compression → Proof → Recall
What repeats? Which words are accurate? Can the idea be compressed? Which Projects prove it? Can others remember and repeat it?
Name value, not only skill
“UI Design” is a capability. “Turning complex systems into clear decisions” describes recurring transformation.
Avoid language that is too broad
Generic labels such as “problem solver” create little differentiation. Strong patterns need specificity and boundaries.
Use verbs
Simplify complexity. Build trust. Make invisible work visible. Turn ambiguity into structure. Verbs reveal movement.
Proof-test the name
Place the name beside three to five Projects. If they need excessive explanation to fit, the name may be aspirational rather than earned.
Let the market refine the language
Notice how clients, teammates, recruiters, and partners independently describe your value.
A naming test
A useful name is specific, evidence-backed, bounded, repeatable, and broad enough to grow while narrow enough to differentiate.
Conclusion
Do not only ask what your headline should say. Ask what language can compress your proven pattern into a signal others can carry.