Resource hub

Category

Operating model

Our operating model — build, ship, measure, keep-or-kill — plus low-overhead operations, the free-first ad-supported model, and honest retrospectives on the products that did not fit.

15 articles

  1. Scattered feedback inputs from support, reviews, analytics, and messages flowing into a cluster of themes, then sorted into a roadmap with now, next, and later lanes

    Operating model · Jun 9, 2026

    From scattered feedback to a roadmap, without a PM

    A practical method for turning scattered feedback into a roadmap when you have no PM: getting all the inputs into one place, clustering raw requests into underlying themes, weighing each theme by frequency and pain against effort and fit, and sorting the result into build now, watch, or decline — across multiple products without drowning.

    Novus Stream Solutions (hub)

  2. A pre-launch runbook with grouped checks — build and assets, metadata and previews, performance, monitoring, and rollback — leading to a ship gate

    Operating model · Jun 8, 2026

    A go-live runbook for a serverless browser app

    A practical, ordered go-live runbook for an app with no backend: verifying the build and assets, confirming metadata and share previews, checking performance and the offline path, making sure analytics and error reporting are live before traffic arrives, and knowing exactly how to roll back. Less a philosophy than a checklist that has earned its place.

    Novus Stream Solutions (hub)

  3. A single product name covering several distinct apps that each needed dedicated time and focus

    Operating model · Jun 7, 2026

    Why we shelved Novus Stream Studio: a second-screen idea that was really several apps

    A kill-decision retrospective: how an appealing single product turned out to be a bundle of apps, and why that made it the wrong thing to keep building solo.

    Operating model

  4. Generic utilities that function correctly but are interchangeable with many existing tools

    Operating model · Jun 7, 2026

    Why we retired Novus Stream Tools: generic utilities that didn't earn their place

    A kill-decision retrospective on building utilities that work fine but have no real reason to exist, and the test that should have caught it sooner.

    Operating model

  5. A product whose constant real-time data refresh created an always-on cost incompatible with a near-free operating model

    Operating model · Jun 7, 2026

    Why we killed our sports-odds project: the real-time data bill we couldn't make cheap

    A kill-decision retrospective on a product that was structurally incompatible with our cost model — the data had to be fresh every minute, and fresh-every-minute is expensive.

    Operating model

Browse every topic in the resource hub