The document discusses the evolution of a civic tech app aimed at enabling community monitors to report issues and progress, detailing changes made through various versions based on user feedback. Key learnings reveal challenges with qualitative data and a shift towards simpler, more structured question formats to enhance user experience and data comparability. Ultimately, the goal is to gather relevant and actionable data while considering accessibility and multilingual complexities.

1. Civic tech for
smartphone
beginners:
Is the future
binary?
Arran Leonard,
Techology Manager
Integrity
Action

2. Civic tech for
smartphone
beginners:
Is the future
binary?
Arran Leonard,
Integrity Action
integrityaction.org

5. In
practice
: A promise is made to a community

6. In
practice
:
Monitors use our App to report Progress & Problems
A promise is made to a community

7. In
practice
:
Monitors use our App to report Progress & Problems
A promise is made to a community
Duty bearers are informed and take action

8. In
practice
: A promise is made to a community
Duty bearers are informed and take action
Problems are fixed
Monitors use our App to report Progress & Problems

9. In
practice
: A promise is made to a community
Duty bearers are informed and take action
Communities benefit
Problems are fixed
Monitors use our App to report Progress & Problems

10. The Types of data we’ve collected and
what we’ve learned

11. Version 1
Objective:
Provide end users the
ability to report
problems how they see
them in their own words
Give ownership of the
project to those
monitoring
Key Learnings
 High Qualitative data
 No required fields
resulted in non
comparable data
 Difficult to make
conclusions and
resolve issues

12. Version 2: Update
Change:
• Everything was made
mandatory
• Free text & Open ended
questions kept
Key Learnings
 Better ability to compare
answers
 We were not being considerate
of monitors time

13. Version 3
Change:
• Effort conduct on
simplifying & streamlining
• Less required fields
• Large shift to yes/no
answers
Key Learnings
 Better monitoring experience
 More monitoring
 More Data
 Some feedback lacked depth
 We had to go back to
monitors for
clarification

14. DevCheck V1-V3: Insights & Lessons
learned
The Bottom line:
• Restricted metrics make for simple analytics
Free Text:
• Can be accessibility barrier
• Multilingual & varying alphabets introduce considerable
complexity

15. Our Objective: Relevant & Actionable Data
Open Process:
• Working closely with partners to
define:
• Desired Metrics
• Data use cases
• Question Sets
Closed questions:
• With defined specific questions
can be asked

16. Version 4
Change:
• All questions are changed to selectable
answers / yes & no
• With the option to add
comments
• Option to include
additional Media

18. https://www.facebook.com/IntegrityAction
https://twitter.com/Act4Integrity
https://www.instagram.com/integrity_action/
https://www.linkedin.com/company/integrity-action/