Age of Invisible Machines

CHAPTER 14The Process of Hyperautomating

If you've worked in neighborhoods adjacent to software design, then likely Agile is no stranger to you. Though it's often misrepresented as a process, Agile is actually a cultural mindset within an organization—one that embraces discovery through shared experimentation, failure, and iteration. Hyperautomation represents the evolution of software design; accordingly, the process that brings it to life requires a mindset and culture that are even more agile than Agile.

Even certified scrum masters might be surprised by how quickly we sprint while creating and iterating in pursuit of hyperautomation. Whereas, if Agile is something you've never applied, the hyperautomation process will feel like massive upheaval. Either way, the key is to internalize the true nature of hyperautomation. This isn't a software design scenario with weekly or monthly product milestones; this process allows you to experiment on active skills, continuously improving them while also activating new skills, multiple times, every day. Part of what makes this possible is an analytics-and-reporting paradigm that provides user data and feedback in real time. Beyond seeing how people are interacting with your conversational interface as those interactions unfurl, you'll also be able to see what kinds of functionalities they're asking for that don't currently exist. These are the kinds of insights that would take weeks (or even longer) to ferret out of a GUI—and they'll ...