{"id":3866,"date":"2020-12-23T03:28:30","date_gmt":"2020-12-23T00:28:30","guid":{"rendered":"http:\/\/data-stars.com\/technology-trends-for-governments-2021-2\/"},"modified":"2021-02-19T01:07:05","modified_gmt":"2021-02-18T22:07:05","slug":"dont-automate-bureaucracy","status":"publish","type":"post","link":"https:\/\/gpm-suite.com\/?p=3866","title":{"rendered":"Don\u2019t automate BUREAUCRACY!!"},"content":{"rendered":"
<\/div>

GPM Center for Government Transformation<\/span><\/h1><\/header>
<\/div>
<\/p>\n

Don\u2019t automate BUREAUCRACY!!<\/strong><\/span><\/h1>\n
Why governments insist on automating the old \u201cunproductive\u201d processes?<\/em><\/h6>\n

Process transformation, before automation<\/strong><\/span><\/h3>\n

When an organization initiates a transformation strategy, the only way to understand the current maturity is to \u201cASSESS\u201d. Moving without clear understanindg of the current processes may lead to watsed time and resoucrs across with big financial impact, that sometimes even governments can not afford.<\/p>\n

There are some reasons behind the failure of process reengineering initiatives, and they have been listed by the Software Engineering Institute as following:<\/p>\n

    \n
  1. The organization inadvertently adopts a flawed or incomplete reengineering strategy.<\/li>\n
  2. The organization makes inappropriate use of outside consultants and outside contractors.<\/li>\n
  3. The work force is tied to old technologies with inadequate training programs.<\/li>\n
  4. The organization does not have its legacy system under control.<\/li>\n
  5. There is too little elicitation and validation of requirements.<\/li>\n
  6. Software architecture is not a primary reengineering consideration.<\/li>\n
  7. There is no notion of a separate and distinct \u201creengineering process.\u201d<\/li>\n
  8. There is inadequate planning or inadequate resolve to follow the plans.<\/li>\n
  9. Management lacks long-term commitment.<\/li>\n
  10. Management predetermines technical decisions.<\/li>\n<\/ol>\n

    Reengineering Work:
    \nDon\u2019t Automate, Obliterate<\/strong><\/span><\/h3>\n

    In his bold insights around Process Reengineering, Micheal Hammer has mentioned, in an insight at HBR[1]<\/a>, that:<\/p>\n