How to build Service As Software

Welcome to Behind Automation, where we are embarking on a journey to build automatic services or “Services as Software” as they are better known.

Our aim is to build, or more presicely, design how to build a Service as Software. This does not mean that we are automating a given business process and serving it to our customer, but rather automating a business process and the whole service organization around it.

While much of the current focus remains on how AI will affect coding practices and project organization. Primarily the early stages of the software development lifecycle. We are looking further ahead. We aim to prepare for the major shift. The emergence of automated service layers, or fully automated service organizations, and how they will transform the industry.

An automated service with all the related processes. As in an automatic service that delivers on business needs and integrates to your change management process. Think of a service with ISO 20000 stamp attached to its side but fully automated. So yes, I’m talking about the kind of service that will make your colleagues fear for their jobs.

Having said that.. It might be that we need to cut some corners and make a few mistakes along the way. As we’re here to learn, not to be perfect at every step. I am posting these thoughts as an invitation to think and discuss.

Will this be a purely theoretical journey, or will we see some “hands on” action aswell? Time will tell. The whole point is to understand how these services could actually work. So I bet we will need to do some actual coding at some point. Maybe run a few agent swarms here and there?

I Hope you join us on our journey.