Question: We use Digital Workforce’s RPA right now. Nenad / Ilmarinen: Without going into too much detail – the cases in question were a very good fit for the API-first approach supported by the existing and custom-made Power Automate connectors. I would be interested in what the Finnish insurance company has implemented with Power Automate concretely? Their composite value then remains limited (unless the scale is really large), as they each have only incremental value, are all done in different ways and with a lot of duplicate work. The other way around (starting with a citizen model with a lot of freedom) one might end up with a lot of innovative but siloed/pocket applications mainly for one’s own use. ![]() In this way citizen development acts as a catalyzer for scalable innovation which builds on reusability but has sustainable levels of maintenance. Once the citizen-made application crosses the business criticality and/or usage scale threshold it is anyway time to polish it (or even rebuild it from scratch) according to the enterprise model standards for e.g. We can probably never expect the citizens to strictly adhere to all the enterprise model components, but the closer the better. The citizens can then be constantly guided to operate towards that model by e.g. ![]() ![]() Nenad / Ilmarinen: IMHO having an enterprise model first is a prerequisite for moving to a citizen model.
0 Comments
Leave a Reply. |