Trust Pyramid Teardown: Three Developer Touchpoints
Objective: Given 3 synthetic developer-facing specimens (a docs homepage, a quickstart page, and a Discord channel history), identify the trust-pyramid violations in each and correctly ignore the plausible-but-harmless distractors.
You're the developer marketing lead at Coinbase reviewing three touchpoints a prospective integrator hits before writing a line of code, checking each against the lesson's trust pyramid before a launch review.
Read each specimen, list the real defects with severity and why they matter, and correctly exclude the distractors that look suspicious but aren't actual trust violations.
Before you start
What you'll need
Free path (everything below is enough to finish)
Free, shareable, and enough structure to log defects, severity, and lesson references before a launch review
The process
Specimens to review
What in this homepage would make a developer stop evaluating before they ever open the quickstart?
API docs homepage banner: 'Enterprise-Grade Payments API — Trusted by Fortune 500.' Below it, a 'View on GitHub' button links to a repo whose last commit was 14 months ago, with 340 open issues and 0 closed in the last 6 months. There is no CONTRIBUTING.md. The Community tab still reads 'Coming soon.'
Specimen: synthetic, realistic
A developer lands on this quickstart intending to make their first API call in the next 10 minutes. What stops them?
Quickstart page: 'Our API enables seamless integration with your payment stack. Simply authenticate and start making calls.' No code block appears anywhere on the page. A 'See full reference' link leads to a downloadable PDF.
Specimen: synthetic, realistic
Does this channel read as an active developer community, or as a broadcast feed nobody reads anymore?
Discord #announcements channel: 47 messages in the last 90 days, all authored by 'CommunityBot' or the marketing account, with zero replies from anyone carrying an 'Engineering' role tag. The pinned message reads 'v4.2 released! Read the changelog.' Twelve unanswered developer questions sit below it.
Specimen: synthetic, realistic
Final deliverable
A defect log across all 3 specimens with severity ratings, why-it-matters notes, and distractors correctly excluded.
See a reference example
Wise developer docs teardown (excerpt) Specimen 2 — Quickstart page Defects found: (1) zero working code samples — critical; (2) reference is a static PDF — moderate; (3) 'seamless integration' language — cosmetic Distractors correctly excluded: reference link label wording, page load speed
Success criteria
You're done when you can:
- Identifies all real defects per specimen with a defensible severity rating
- Does not flag either listed distractor as a defect
- Ties each defect to the specific trust-pyramid layer it violates