Rolling out an organisationwide MIS at WaterAid Petri Autio Systems Advisor Planning Monitoring Evaluation and Reporting WaterAid MERL Tech 20th February 2017 Context WaterAid UK has gone from having no MIS at all to a shared online system covering all country programmes and re ID: 580867
Download Presentation The PPT/PDF document "What have we learned about MIS and dashb..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
What have we learned about MIS and dashboards and the people using them?
Rolling out an organisation-wide MIS at
WaterAid
Petri Autio
Systems Advisor – Planning, Monitoring, Evaluation and Reporting, WaterAid
MERL Tech:
20th February 2017Slide2
Context
WaterAid
UK has gone from having no MIS at all to a shared, online system covering all country programmes and regions
WaterAid
has remade and harmonised the entirety of its planning, monitoring, evaluation and reporting processes (PMER)
What
choices did we make in selecting, configuring and deploying the
system, and why?Slide3
Our key drivers and decisions
Bespoke /
SaaS
Online /
Offline
Harmony
/ Flexibility
Have a
s
hared version of the truth
Project and programme managers in the driver’s seat
Simple / ComprehensiveSlide4
Organisational MIS timeline
+ 9 months
Pilot running
In-country roll-out & capacity building
Apr
2017 ->
+ 3 months
From choosing the system to pilot going live
+ 6 months
Trainer of trainers model
Project Center pilot in Southern Africa
Planning, Monitoring, Evaluation and Reporting overhaul
Rolling phase
Failed GPMIS project
2012-2014
Can be stop-and-start but that’s ok. What is the right scope?
With an off-the-shelf solution it’s possible to launch a pilot rapidly
Learning from pilot phase proved crucial in simplifying and streamlining the system
Putting process first and system second was very beneficial. Also allows us to give carrots!
Jun 2014
Decision to go with specific
SaaS
system
Many reasons:
Organisational hesitancy for large-scale projects
Failed regional MIS
Overambitious plan?
Setting up a dedicated team
Minimum requirements created from the bottom-up
System reconfigured to match new requirements including learning from pilot
> 170 data fields simplified away
+ 16 months
Making sure minimum requirements are adhered toSlide5
Organisational MIS overview
Country
Programme
Programme
Programme
Project
Project
Project
Plans and
updates
Plans and
updates
Results
framework
Activities
Outputs
Outcomes
Impact
Indicators
Free to create your own
Plans and
updates
Filtering key information to management
Budgets brought over from integrated finance systems
Separate system for tracking detailed monitoring data
A basic structure to build uponSlide6
Takeaways
+ Technology comes second, needs to align with processes
+ Configuring an off-the-shelf solution is a viable route, can lead to a rapid pilot
+ Don’t cram everything into the MIS when you do have one
+ Not just business as usual but this time with a system on top – what can you let go of to make a new system alluring to users?