Loading…

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Like this presentation? Why not share!

Monitoring and evaluating APIs

on

  • 893 views

 

Statistics

Views

Total Views
893
Views on SlideShare
893
Embed Views
0

Actions

Likes
0
Downloads
4
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Monitoring and evaluating APIs Monitoring and evaluating APIs Presentation Transcript

    • What difference did it make? Penelope Beynon Date: 15 Nov 2010
    •  
    • Evaluating an Open API
      • Who should benefit from an Open API?
      • How will they benefit? Ie what will be different if the Open API is successful?
      • How will you know if those benefits are realised?
    • How are we evaluating MK4D?
      • Monitoring outputs – what did we do?
        • webstats, finance, publications, reach figures
        • Event reports
      • Evaluating outcomes – what difference did it make?
        • Principles of outcome mapping
        • Interviews, Surveys, ‘tests’, data analysis
      • Improvement - what lessons did we learn?
        • Event reports
        • Learning labs
    • Principles of outcome mapping
      • OM was developed by International Development Research Centre (IDRC) in the late 1990s – an online user group is run by Overseas Development Institute (ODI) http://www.outcomemapping.ca/
      • OM is a methodology for planning, monitoring and evaluation.
        • OM focuses on outcomes rather than outputs
        • OM acknowledges the limit to your influence
        • OM is people-focussed
        • OM looks for contribution rather than attribution
      • In IDS we are exploring use of OM for understanding the research uptake process, and evaluating research uptake work
    • Three stages of outcome mapping Intentional Design
      • What are you trying to achieve? (vision)
      • How are you going to do it? (mission)
      • Who do you need to influence? (boundary partners)
      • How will other people behave if you have been successful? (outcome challenge)
      • What changes do you hope to see in other people along the way? (progress markers)
      • What will you do to achieve the mission? (strategy maps)
      • How will you behave if you are working well? (organisational practices)
      Outcome and Performance Monitoring
      • How will you make monitoring manageable ? (monitoring priorities)
      • How will you record changes in other people ? (outcome journals)
      • How will you record changes in what you are doing ? (strategy journal)
      • How will you record changes in your own behaviour ? (performance journal)
      Evaluation Planning
      • What will you explore in-depth ? (evaluation plan)
      (adapted from Earl et. al. 2001)
    • Spheres of control, influence, interest Project team Outputs: Inputs, activities Partners/actors Outcomes: Changes in attitudes/awareness/behavior Beneficiaries Impact: Changes in economic, physical and social wellbeing Context Context Context Sphere of control Sphere of influence Sphere of interest
    • Evaluating an Open API
      • Who should benefit from an Open API?
      • How will they benefit? Ie what will be different if the Open API is successful?
      • How will you know if those benefits are realised?