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.
Field notes tagged "product-strategy" — observations from the trenches.
Why I integrated ActivityPub into ryanw.eu, adopted a POSSE publishing model, and treat the Fediverse as distribution infrastructure rather than rented audience.
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.
A Zendesk case study in customer feedback prioritization: how a simple weighted scorecard separated signal from noise, surfaced hidden issues, and changed the roadmap.
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.
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.