Thoughts
1. Productized service is a whole spectrum between service and product
2. At least at the start of that spectrum, it's simply a marketing/positioning shift. The work may stay very similar to before
(cont)
1. Productized service is a whole spectrum between service and product
2. At least at the start of that spectrum, it's simply a marketing/positioning shift. The work may stay very similar to before
(cont)
3. "Following the same steps each time" != "Doing the same thing each time". i.e. you can systemetize and standarize the process you use each time, and offer the same "end result" to each client, while the implementation remains totally bespoke. That's already productization ...
3/ ... But, as a developer, you'll inevitably see the inefficiencies / duplication across each implementation and end up automating/productizing further. I'd argue that devs will travel QUICKER along the S->P spectrum than many others bc they spot the opportunities to DRY ..
4/ And that one of the big challenges is making sure NOT to jump spectrum too quickly. How many devs have you seen jump straight to building SaaS without understanding anything about the problem space?!
5/ You get that domain knowledge more effortlessly in (productized) services, because you're forced to speak with customers by default, than in a product business where you have to force yourself to speak with customers
6/ As for examples, many have just been given by bigger and brighter minds than mine 😀 Restaurant Engine is a great one. This image serves as such a good lens into developer productized service vs service 🤤 
