Kristina Halvorson

In my experience, there's a big difference between brochure sites (owned by marketing typically) vs. product sites or apps. I think of the latter as "the primary thing that the user wants" vs "the place where you learn about the thing." News/info sites are the weird exception.

The other weird exception is for tech enabled products like Uber where the mobile app is not really the product people want, but it's more like a product since it acts as the main interface to what users want. Ecommerce sites...become problematic in this definition tho!

Seems to me the problem is the fixation on the container and not the words that go into the container. I'm trying hard to figure out why you wouldn't roll product content strategy into the web given the only reason to have a website is to be your 24x7 storefront.

If you're a SaaS company your website is a lot more than a storefront.

“The Product CS gets to be in a team.” This lines up with my experience, with a product CS generally pairing with a designer and writing actual copy for a feature, while a web CS operates at a higher perspective, above specific features...

So I can see why they’d be 2 separate roles w/ different skills (writing & usability testing vs. setting a vision & governance) if the org can afford that level of specialization, but agree it can lead to the web CS getting isolated if the focus is on churning out new stuff...