[MEASUREMENT]

How might we convert the reporting moment into a learning moment for sector teams?

 

Why does this matter?

Gender teams work with a compliment of sector experts and development generalists to implement gender related programs. They must rely on the reporting they receive from sector teams to understand the effectiveness of programs and build the evidence case for Gender Mainstreaming.

It is important that sector teams understand why and what they are reporting and ensure they are reporting accurately, but the reporting process can be cumbersome and they often lack the fundamental understanding of gender actions and processes.

Who is this meant for?

A program officer who is getting ready to complete her quarterly reporting on the programs and projects that her team implemented. In the past, though she was unsure, she responded to the best of her knowledge, but she is beginning to realize that her responses determine how budget is allocated and how gender is prioritized in programs. This time she wants to be as accurate and thorough as possible, but worries she lacks the gender knowledge required to do so.

WHAT ARE YOU BUILDING? (The prototype)

Design a reporting tool with a learning component that is delightful and intuitive to understand and provides sector teams with contextual understanding to improve the quality of their gender reporting.

 
CONSTRAINTS TO DESIGN FOR
  • Focus on the experience of reporting for sector teams and the form factor of the reporting tool itself (i.e. the HOW and the WHY, not the What). 

  • Should be intuitive and easy to comprehend for sector teams’  with limited understanding about gender.

  • Should simplify the reporting process

  • Should have a learning component

  • Should be applicable across different contexts and organizations.

Inspiration.

Getting started

 

Questions to get started

Consider these as you brainstorm ideas.

  • How can we help sector teams understand “what good looks like” for different levels of requirements to improve accuracy of reporting?

  • What additional information do sector experts need to understand better what they are reporting on?

  • How could the tool help the person reporting understand if they have completed it correctly? (e.g. validation moments, checks, etc)

  • How might we use game dynamics to encourage quality completion of reports? E.g. rewards, feedback, time pressure, etc. 

  • How could the tool improve the presentation and interpretation of the results? (e.g. data visualization)

 

Your prototype might look like

Some initial ideas to get you going…

  • A gamified assessment that is more approachable for users

  • An on-demand helper or tutorial embedded in the reporting tool

  • A set of videos that show what good looks like for different levels of gender requirements

 

Session Recordings

  • Day 1: Brainstorming

    Watch the recording from our brainstorming session here

  • Day 3: Design Research

    Watch the recording from our design research and iteration session here

  • Day 5: Finalize Prototype

    Watch the recording from the final day of the sprint here

Finally, we captured our process, key questions, and design hunches at the end of each day in a postcard.

See Postcards