EUC applications should not be evolved by accident, but there should be a defined EUC strategy.<ref>{{cnCite web|dateurl=Mayhttps://www.clusterseven.com/end-user-computing-risk-management/|title=What 2016is End User Computing? {{!}} EUC Risk Management|website=ClusterSeven|language=en-US|access-date=2020-01-29}}</ref> Any [[Application Architecture]] Strategy / IT Strategy should consider the white spaces in automation (enterprise functionality not automated by [[Enterprise resource planning | ERP]] / [[Enterprise Grade Applications]]). These are the potential areas where EUC can play a major role.{{cn|date=May 2016}} Then ASSIMPLER parameters{{which?|date=May 2016}} should be applied{{by whom?|date=May 2016}} to these white spaces to develop the EUC strategy. (ASSIMPLER stands for availability, scalability, security, interoperability, maintainability, performance, low [[cost of ownership]], extendibility and reliability.<ref>
Compare: {{cite web
|last1= Vanarse|first1= Mandar|title= Business Value Assurance during the transformation journey.
