How to Spot AI-Sounding Language in Your Portfolio

A portfolio can sound professional and still feel unconvincing. I notice this most when every sentence is smooth, but none of them help me understand what the designer actually decided. The writing is not bad. It is just too easy to swap into any other project.

The first signal: broad claims without a specific moment

Watch for sentences like “I improved the user experience through research-driven design.” The sentence sounds acceptable, but it does not tell the reader what changed. A stronger sentence points to a moment: “After two test participants missed the delivery fee, I moved the cost explanation before address confirmation.”

The second signal: repeated portfolio phrases

Some phrases are not wrong once. They become weak when they appear in every section. “User-centered,” “seamless,” “intuitive,” “clearer journey,” and “better experience” all need support. Replace them with what you observed, what you changed, and why that change mattered.

The third signal: perfect confidence

Real projects usually contain uncertainty. A case study that has no constraint, no rejected option, and no unresolved question can feel artificial. You do not need to make the project messy on purpose. Just be honest about the decisions that were not obvious.

Replace claims with evidence

A claim says the design was better. Evidence helps the reader understand why. Evidence can be a research insight, usability observation, stakeholder constraint, metric, support ticket theme, or design comparison. The best evidence is not always numerical. It only needs to be real and connected to the decision.

Use your own working language

Before making a section polished, write what happened in plain words. For example: “People did not trust the price because the fee appeared late.” That sentence may not be final, but it is useful. It has a sharper core than “I created transparency across the checkout journey.”

A quick review checklist

Read one section and ask: could this paragraph belong to any UX project? If yes, add the missing context. Which user? Which moment? Which constraint? Which decision? Which result? A good case study does not need fancy language to be credible. It needs traceable thinking.

Frequently Asked Questions

Is AI-sounding language always bad? Not always, but it can make your work feel generic if the wording hides decisions.

What words should I avoid? Avoid unsupported words like seamless, intuitive, user-centered, and impactful when they are not tied to a concrete example.

How can I make portfolio writing sound more natural? Start with plain notes, then edit for clarity. Do not polish before the reasoning is clear.

Should I remove every mention of AI? No. The point is not to hide tools. The point is to keep your own decisions visible.

What is the fastest fix? Replace broad claims with one specific design moment and the reason behind it.