How to implement almost anything

This diagram summarises (my own view of) how to roll out almost anything in IT that is not too technical – not a systems deployment, perhaps (which would be full of technical preparations and tests) but certainly a new process or function.

Implementation process

It’s quite obvious once you’ve nailed down the detail, but you may find it helpful. The steps for each of these tasks are summarised below:

  1. Stakeholder workshops
    • Scope
    • Goals
    • Impact
    • Process
    • Expectations
    • Participation
  2. Finalise key updates
    • Functions
    • Organisation
    • Products
    • Processes
    • Controls
    • Training
    • Intranet
  3. Project kick-off
    • Scope + goals
    • Budget
    • Team and organisation
    • Requirements
    • Sponsor and stakeholders
    • Mandate/Project definition
    • Issues and risks
    • Critical success factors + KPIs
  4. Communicate with stakeholders
    • Expectations
    • Impact
    • Budget
    • Alignment
    • Authority to proceed
  5. Identify audiences
    • IT stakeholders
    • Business stakeholders
    • Delivery managers
    • Development teams
    • Operations and support
    • Regulators & compliance
    • Cross-organisational teams
  6. Capture current status
    • Function mapping
    • As-is process/systems
    • Awareness & interests
    • Functional impact
    • Implementation impact
    • SWOT, risks & issues
  7. Validate roll-out process
    • Process walkthrough
    • Impact assessment
    • Participation requirements & plan
    • Risks & issues
    • Go/No Go decision
  8. Tailor roll-out packages
    • Local expectations and impact
    • Entry/exit points/processes/products
    • Current level of knowledge
    • Local implementation process
    • Local interfaces, access, reporting, etc.
  9. Communicate with SMEs & specialised functions
    • Expertise requirements
    • Participation in transition
    • Support during transition
    • Facilitation
  10. Train users
    • Functional objectives
    • Walk through solution
    • Metrics & standards
    • Participation in transition
    • Cutover impact
    • Supervision & support
  11. Train SMEs
    • As for Train Users.
  12. Brief stakeholders
    • Changes
    • Impact
    • Benefits/value
    • Transition process
  13. Roll out components
    • Access tools & privileges
    • Localisation
    • Local integration
    • Measurement tools
    • Support arrangements
    • Remove existing systems/materials
  14. Evaluate benefits
    • Take-up
    • Performance metrics
    • Quality metrics
    • User satisfaction
    • Transition costs
    • Stakeholder satisfaction
    • Compliance
  15. Close project
    • Validate against requirements
    • Project performance
    • Update support
    • Residual issues
    • Lessons learned
    • Project closure

Of course, this assumes that you have actually captured the requirements, modelled the process and designed the implementation components in advance, which isn’t always the case. But this process should at least tell you what you need to have done before you get to implementation.

By |2018-01-18T14:59:20+00:00Tuesday, May 8 2012|Categories: All, Change, Innovation, Management systems, Process and method, Quality|0 Comments

About the Author:

Chief Architect, Agile201.com.

Leave A Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Want to do more than just build systems?             
error: Agile201 is wholly copyright and copy-protected.