Product Naming Carries Political Weight — "Employee" vs "Talent"

evaluation client naming process

1 What happened

The factory initially used "digital employee" as the product term. During early client conversations, the term triggered concerns about AI replacing human workers — HR departments flagged it, and one prospect explicitly said the term would prevent internal approval. Switching to "digital talent" reframed the product as augmentation rather than replacement. The terminology was formalized in TFD-0003 and enforced via a PreToolUse hook.

2 What we learned

Product naming in AI is politically loaded in ways that pure technology evaluation misses. Terms that are technically accurate ("employee" — it does the work of an employee) can be commercially toxic if they trigger replacement anxiety. The naming decision should be treated as a market positioning choice, not a technical description. Enforcement matters too — a naming convention that isn't automated will drift. The PreToolUse hook catches violations before they reach deliverables.

3 Applies to

  • All client-facing communications — "digital talent" is the only approved term