Writing

Notes from the messy middle.

I write about streaming video products, digital media operations, and the behind-the-scenes workflows that shape what viewers actually experience. Some are product thoughts. Some are workflow observations. Some are me trying to make sense of why a "simple" video product needs a six-system diagram.

In the queue

Posts I'm drafting

Coming soon. If something here catches your eye, ping me and I'll prioritize.

Coming soon

The CMS is part of the product

Most viewers will never think about the CMS behind a streaming app, and that's probably a good thing. But anyone who has built one knows the CMS is not just an internal tool. It shapes what viewers see, how quickly teams can publish, and how painful support becomes when something breaks.

Coming soon

Streaming products are more operational than people think

A working streaming product is a content pipeline, a CMS, a metadata model, a feed, an app, a player, an auth layer, a CDN, and a support team. The product team can ship a feature in a sprint. Making it operationally real takes longer.

Coming soon

Live video is not just a player

Live looks simple to viewers: open the app, tap the channel, see a stream. Behind that is fallback logic, availability handling, metadata, rights windowing, support paths, and a long list of "what happens when" questions that don't get asked until production.

Coming soon

From motion graphics to product management

A career arc through creative, then operations, then product. The thing nobody tells you is that the layers don't stack neatly. You keep doing all of them.

Coming soon

Why edge cases belong in product requirements

The hardest part of a product spec is not what happens when everything works. It's what happens when the stream fails, the metadata is missing, or the user navigates somewhere unexpected. Edge cases are where product decisions actually show up.

Coming soon

The restaurant metaphor for digital content operations

Viewers are guests. Content is the food. Producers and editors are the cooks. The CMS is the kitchen line. Analytics are guest feedback. The dining room only works if the kitchen and the line and the expediter all do.

Want to talk about one of these?

Trade notes.

If you work on this stuff and want to compare notes, send me a message. The best writing usually starts as a conversation with someone who has been in it.

Say hello