DulyNoded
Team
Internal KB: Support Patterns & Fixes
Common issues, best fixes, and the small UX changes that reduce tickets.
supportbugsuxknowledge base
Emily Hart
Tessa Williams
Sam Rivera
Mara Kim
Emily (Owner) · Tessa (Design) · 2 more
MEDIAVerified
Worth it for minutes 5–8
Why it matters: This is a high-signal constraint.
Curated by Tessa · · · Saves & Shares (146)
MEDIAVerified
Worth it for minutes 10–14
Why it matters: This is a high-signal constraint.
Curated by Sam · · · Saves & Shares (168)
MEDIAVerified
Worth it for minutes 12–18
Why it matters: This is a high-signal constraint.
Reliability: Medium confidence
Curated by Mara · · · Saves & Shares (190)
DATAMust Read
Key number
42%
YoY
Key number with short context.
Why it matters: This shifts what we’d do next.
Curated by Mara · · · Saves & Shares (395)
DATA
Key number
42%
YoY
Key number with short context.
Why it matters: This shifts what we’d do next.
Source: Low confidence
Curated by Emily · · · Saves & Shares (395)
CLAIMKey Claim
Claim
This claim should be treated as testable, not inspirational.
Source says: Source says…
Why it matters: This shifts what we’d do next.
Curated by Sam · · · Saves & Shares (438)
CLAIMTo Verify
Claim
This claim should be treated as testable, not inspirational.
Source says: Source says…
Why it matters: This shifts what we’d do next.
Reliability: High confidence
Curated by Tessa · · · Saves & Shares (438)
QUESTIONDraftResolved
Question
What are we trying to answer?
Working answer: collect 2–3 proof points.
Why it matters: This shifts what we’d do next.
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 shifts what we’d do next.
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 shifts what we’d do next.
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 13 nodes
Added by Tessa · · · Saves & Shares (269)
NOTEDraft
Working note
A short working note that captures the board’s current stance (mock).
Why it matters: This makes the board’s thesis more concrete.
Added by Sam · · · 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 is a high-signal constraint.
Curated by Emily · · · Saves & Shares (438)
QUOTEVerified
A quotable line that fits the board’s theme.
Why it matters: This shifts what we’d do next.
Curated by Sam · · · Saves & Shares (534)
MEDIATo Verify
Worth it for minutes 12–18
Why it matters: This is a high-signal constraint.
Curated by Sam · · · Saves & Shares (454)
DATA
Key number
Key metric
A key number with short context.
Why it matters: This shifts what we’d do next.
Curated by Mara · · · Saves & Shares (395)