DulyNoded
AboutRegisterTry DN ProNEW
Team
Microcopy & Product Language Library
Approved phrases, patterns, and the tone we ship.
onboardingempty stateserror copy
Tessa Williams
Mara Kim
Jun Park
Emily Hart
Sam Rivera
Tessa (Owner) · Mara (Editor) · 3 more
NOTE
Tone rules (what we ship)
We write like: - calm - specific - non-performative We avoid: - gamification - shame language - hype metaphors
Added by Tessa · · · Saves & Shares (272)
HIGHLIGHT
Empty states should explain the *benefit*, not the feature.
Takeaway: Good empty copy is a promise, not instruction.
Linear App ↗
Curated by Tessa · · · Saves & Shares (561)
QUOTE
An error message is the product meeting reality.
Notion SO ↗
Curated by Tessa · · · Saves & Shares (427)
MEDIAVerified
Worth it for minutes 5–8
Why it matters: This is trust language, not marketing.
Used in: Internal brief
YouTube ↗
Curated by Emily · · · Saves & Shares (146)
MEDIAVerified
Worth it for minutes 10–14
Why it matters: This is trust language, not marketing.
Used in: Internal brief
YouTube ↗
Curated by Sam · · · Saves & Shares (168)
MEDIAVerified
Worth it for minutes 12–18
Why it matters: This is trust language, not marketing.
Used in: Internal brief
Reliability: High confidence
YouTube ↗
Curated by Tessa · · · Saves & Shares (190)
DATAMust Read
Key number
42%
YoY
Key number with short context.
Why it matters: This is trust language, not marketing.
Referenced in: Internal brief
IEEE Spectrum ↗
Curated by Tessa · · · Saves & Shares (395)
DATAMust Read
Key number
42%
YoY
Key number with short context.
Why it matters: This is trust language, not marketing.
Referenced in: Internal brief
Source: Low confidence
IEEE Spectrum ↗
Curated by Mara · · · Saves & Shares (395)
CLAIMTo Verify
Claim
This claim should be treated as testable, not inspirational.
Source says: Source says…
Why it matters: This will show up in onboarding behavior.
Theverge ↗
Curated by Jun · · · Saves & Shares (438)
CLAIMKey Claim
Claim
This claim should be treated as testable, not inspirational.
Source says: Source says…
Why it matters: This will show up in onboarding behavior.
Reliability: Medium confidence
Theverge ↗
Curated by Emily · · · Saves & Shares (438)
QUESTIONDraftResolved
Question
What are we trying to answer?
Working answer: collect 2–3 proof points.
Why it matters: This is trust language, not marketing.
Added by Sam · · · Saves & Shares (217)
QUESTIONDraftOpen
Question
What are we trying to answer?
Working answer: collect 2–3 proof points.
Why it matters: This is trust language, not marketing.
Added by Tessa · · · Saves & Shares (217)
QUESTIONDraftOpen
Question
What are we trying to answer?
Working answer: collect 2–3 proof points.
Why it matters: This is trust language, not marketing.
Added by Mara · · · Saves & Shares (217)
DECISIONVerified
Decision
Decision: document the tradeoff
  • Choose the constraint that sets the timeline.
  • Avoid scope creep; keep the artifact legible.
  • Align on what evidence would change this.
Supported by 10 nodes
Used in: Internal brief
Added by Tessa · · · Saves & Shares (269)
NOTEVerified
Working note
A short working note that captures the board’s current stance (mock).
Why it matters: This will show up in onboarding behavior.
Used in: Internal brief
Added by Jun · · · Saves & Shares (219)
HIGHLIGHTTo Verify
A concise notable: what changed and why it matters.
Takeaway: Takeaway: assign an owner and a next step.
Why it matters: This will show up in onboarding behavior.
Used in: Internal brief
BBC ↗
Curated by Sam · · · Saves & Shares (438)