Skip to main content
← All Field Notes
product-strategy 5 notes

Field notes tagged "product-strategy" — observations from the trenches.

Interconnected publishing network representing an owned website syndicated across federated channels
Essays · · 7 min

Protocols, Not Platforms: Why I Wired My Site Into the Fediverse

Why I integrated ActivityPub into ryanw.eu, adopted a POSSE publishing model, and treat the Fediverse as distribution infrastructure rather than rented audience.

Layered architectural blocks with misaligned seams representing domain drift across teams
Applied Strategy · · 8 min

Domain Bugs Cost More Than Code Bugs

Domain-Driven Design, ubiquitous language, and bounded contexts matter because product teams ship the wrong workflow when legal, product, and engineering mean different things by the same word.

Weighted scoring spreadsheet used to separate customer signal from noise and rank roadmap themes
Applied Strategy · · 6 min

Signal to Noise: The Spreadsheet That Changed What We Shipped

A Zendesk case study in customer feedback prioritization: how a simple weighted scorecard separated signal from noise, surfaced hidden issues, and changed the roadmap.

Brass balance scale with geometric blocks and weighted trade-offs representing nuanced prioritisation
Applied Strategy · · 9 min

Why Raw RICE Fails on Internal Platforms

RICE still works as a shared prioritisation language. On internal platforms, the failure starts when teams treat raw reach math as the answer instead of adding a domain-risk pass and documenting the rationale.

Aerial view of city intersection with competing light trails converging
Applied Strategy · · 6 min

The Loudest Request Is Rarely the Most Important

Product teams drown in feedback: tickets, sales calls, NPS, stakeholder opinions. Without a scoring system, the loudest voice wins. Here's what replaces gut feeling.