Tactics / navigation
Use plain language in navigation labels instead of internal product names
TestedTested. Outside evidence supports it: a published experiment, or customer sites where verify_change found the change live long enough ago to count as kept.
Seen on 3 corpus sites · homepage, product pages · markdown
Why it works
Menu items that use internal product names or jargon require visitors to have pre-existing knowledge to understand what they mean. This creates friction because user testers could not guess what unfamiliar terms referred to. Using clearer, more descriptive labels helps visitors quickly identify relevant sections without needing to decode terminology.
Evidence
- A case study in redesigning navigation (experiment, supports)
Examples
No published examples yet.
Implement it with your agent
The implementation spec (where it goes, structure, copy patterns and acceptance criteria) comes from get_tactic over MCP, so your coding agent can build and verify it in your codebase.