Product Brief
Kindle's north star is simple: make reading on a screen feel as natural and enjoyable as reading on paper or better. The brief calls for crisp text, true-to-life images, and an experience comfortable enough for hours of immersion without eye fatigue.
Before jumping to solutions, a good PM asks the right questions. The discovery focused on five lenses: display technology, user feedback, competitive landscape, target audience, and technical constraints, covering everything from E Ink limits to how a sharper display affects battery and BOM cost.
Defining the goal
The goal isn't 'better pixels' , it's to build a device people prefer to a phone or tablet when they want to read. That breaks down into four traits:
- → A display sharp and comfortable enough for multi-hour sessions
- → Customisation that lets every reader shape the experience
- → Responsive, distraction-free interaction that gets out of the way of the story
- → A device light and long-lasting enough to travel everywhere
User segments
Kindle serves a broad audience. Understanding each segment is essential before recommending a single feature change.
| Segment | Who they are | What they need |
|---|---|---|
| 01 — Casual Readers | Read occasionally for leisure | Comfort and simplicity — no fiddling with settings |
| 02 — Avid Readers | Read daily for hours | Advanced features: annotations, dictionary, premium display |
| 03 — Students & Scholars | Use Kindle for research and PDFs | Annotation tools and broad format compatibility |
| 04 — Travellers | Read on the move | Lightweight, durable, long battery, offline-friendly |
| 05 — Accessibility Users | Need inclusive defaults | Adjustable fonts, high contrast, text-to-speech |
| 06 — Professionals | Read business and technical docs | Robust PDF support and cloud sync |
01 — Casual Readers
- Who they are
- Read occasionally for leisure
- What they need
- Comfort and simplicity — no fiddling with settings
02 — Avid Readers
- Who they are
- Read daily for hours
- What they need
- Advanced features: annotations, dictionary, premium display
03 — Students & Scholars
- Who they are
- Use Kindle for research and PDFs
- What they need
- Annotation tools and broad format compatibility
04 — Travellers
- Who they are
- Read on the move
- What they need
- Lightweight, durable, long battery, offline-friendly
05 — Accessibility Users
- Who they are
- Need inclusive defaults
- What they need
- Adjustable fonts, high contrast, text-to-speech
06 — Professionals
- Who they are
- Read business and technical docs
- What they need
- Robust PDF support and cloud sync
Pain points by segment
Mapping pain before jumping to solutions is one of the most important habits in product thinking.
Casual Readers — eye strain after short sessions, limited font and background customisation, non-intuitive navigation, battery that drains before a long weekend.
Avid Readers — uneven screen illumination, clunky bookmarks and annotations, page-turn lag, painful library management at scale.
Students & Scholars — afterthought highlighting, poor PDF rendering, no access to research databases, unreliable cross-device sync of notes.
Travellers — heavy in a packed bag, mid-flight battery death, fragile screens with no rugged option, weak offline content controls.
Accessibility Users — narrow font range, limited contrast options, unnatural text-to-speech, physical controls hard to use with motor limitations.
Professionals — slow rendering of complex layouts, missing markup tools, no Notion/Drive/Dropbox integration, weak support for rarer formats.
Proposed solutions
Every pain point above maps to a concrete, buildable fix. These aren't blue-sky ideas each is grounded in what's feasible and commercially sensible for an e-reader manufacturer.
- → Casual — high-res anti-glare E Ink, expanded type controls, redesigned home with recommendations, adaptive brightness for longer battery
- → Avid — uniform front-lit display with warm/cool slider, native annotation toolkit, flicker-free page turns, smart library with collections and sync
- → Students — full PDF reflow engine, structured note export to Notion/Docs, in-app gateway to JSTOR / arXiv / PubMed, versioned multi-device sync
- → Travellers — aerospace-grade aluminium frame, IPX8 water resistance, six-week battery with ultra-low-power mode, offline-first download queue
- → Accessibility — 8–72 pt type range and dyslexia-friendly font, WCAG-AA contrast and inverted themes, neural TTS, configurable gesture and button shortcuts
- → Professionals — optimised PDF/DOCX/EPUB3 renderer, stamps and freehand markup, Dropbox/Drive/OneDrive/Notion integrations, MOBI/CBZ/DjVu/XPS support
RICE prioritisation
Not everything ships in the next release. RICE : Reach, Impact, Confidence, Effort , turns a wish-list into a sequenced roadmap.
| Segment | Reach | Impact | Confidence | Effort | Priority |
|---|---|---|---|---|---|
| Casual Readers | High | High | Medium | Medium | P1 — Must have |
| Avid Readers | Medium | High | High | High | P2 — Should have |
| Students & Scholars | Medium | High | Medium | High | P2 — Should have |
| Travellers | Medium | Medium | High | Medium | P3 — Nice to have |
| Accessibility Users | Medium | High | High | High | P2 — Should have |
| Professionals | Low | Medium | Medium | Medium | P4 — Low priority |
Casual Readers
- Reach
- High
- Impact
- High
- Confidence
- Medium
- Effort
- Medium
- Priority
- P1 — Must have
Avid Readers
- Reach
- Medium
- Impact
- High
- Confidence
- High
- Effort
- High
- Priority
- P2 — Should have
Students & Scholars
- Reach
- Medium
- Impact
- High
- Confidence
- Medium
- Effort
- High
- Priority
- P2 — Should have
Travellers
- Reach
- Medium
- Impact
- Medium
- Confidence
- High
- Effort
- Medium
- Priority
- P3 — Nice to have
Accessibility Users
- Reach
- Medium
- Impact
- High
- Confidence
- High
- Effort
- High
- Priority
- P2 — Should have
Professionals
- Reach
- Low
- Impact
- Medium
- Confidence
- Medium
- Effort
- Medium
- Priority
- P4 — Low priority
What ships first
"Casual Readers are the P1, they have the widest reach, and display improvements deliver high impact at medium effort. Accessibility belongs in the same release: it's a high-impact bundle that lifts the experience for every other segment too."
Success metrics
Good product work is measurable. Eight metrics form a balanced scorecard across satisfaction, performance, accessibility, and business health.
- → CSAT — post-update in-app survey targeting a 15%+ lift in 4–5★ ratings
- → Average reading session length — +20% vs baseline via Kindle app analytics
- → Display clarity rating — blind A/B test on pixel density and legibility
- → Battery life — continuous-read test at 50% brightness, target ≥6 weeks
- → Error & crash rate — page-turn failures and renders per 1,000 sessions
- → Accessibility compliance — full WCAG AA audit plus testing with 3 cohorts
- → Feature adoption — % of active users engaging with new features in 30 days
- → Customer retention — 12-month renewal rate; healthy display UX is the strongest retention lever
Key takeaways
The framework matters more than the answer. Anyone can copy this for the next consumer-hardware product.
- → Start with the user, not the feature — every improvement was derived from a real need, not a trend
- → Prioritisation is product strategy — RICE forced trade-offs and surfaced Casual Readers as the highest-leverage first move
- → Accessibility is not optional — larger fonts, higher contrast, clearer navigation help everyone, not just users with disabilities
- → Measure what matters — defining success metrics upfront keeps the team shipping things that move the needle