Purpose of the Module

The Lean LxD (Learning-by-Doing) Module provides a practical approach for continuous improvement within Community Engagement (CE) and Routine Immunization (RI) systems. It was developed based on earlier LxD field deployment and supervision experiences, where teams needed simple ways to listen, adapt, and improve without disrupting routine work.

It supports teams to:
  • Learn from routine implementation
  • Make small evidence-informed adjustments
  • Strengthen delivery without creating parallel structures
It is designed to:
  • Use existing roles, meetings and supervision cycles
  • Introduce few, clearly defined tools
  • Separate listening, decision-making and evaluation
  • Support government ownership and sustainability

NOTE: The emphasis is on small, continuous improvements rather than large, one-off changes

The Lean LxD Cycle

Lean LxD is anchored within Community Engagement (CE) and Routine Immunization (RI) supportive supervision and microplanning structures. It is designed to strengthen how teams listen, adapt, and review performance as part of routine implementation. It follows a short, repeatable cycle aligned to routine work:

LxD
1  Community Interaction
(KIIs + Shadowing)
2  Empathy Tool
(reflects shadowing observations)
3  Learning Log
(documents signals from KIIs and shadowing)
4  Change Log
(records decisions and adjustments)
5  After-Action Review (AAR)
(evaluates outcomes)

Lean Learning-By-Doing Template

Template 1: Key Informant Interviews (KII)

Role: Structured listening

Description

Key Informant Interviews are used during routine Community Engagement (CE), Routine Immunization (RI), and supportive supervision activities to understand perspectives, experiences, and constraints from caregivers, frontline workers, supervisors, and community stakeholders.

Note: KIIs are conducted to listen and understand, not to assess performance or provide correction.

Subject:
Observer/Interviewer:
Activity:
Date:
Usability / experience
How easy/difficult was it to do the task?
Which part helped the most?
Which is most confusing/difficult?
Why 1:
Why 2:
Why 3:
Why 4:
Why 5:
Feedback Loop and Responsiveness
Which of your previous suggestions have been acted upon?
How did the change affect your work?
Workload & motivation
On average, how many households/visits are you able to make in a day/wk/mn?
What makes it easier/difficult to cover as much/little?
Gender & community dynamics
Can you tell me how gender affects your work?

Template 2: Shadowing (Day-in-the-Life)

Role: Observation of real practice (Observe the subject real time without interference)

Description

Shadowing involves observing CE or RI activities in real time without interference. It is used to understand how work is actually done, rather than how it is expected to be done.

Subject:
Observer/Interviewer:
Activity:
Date:
The Task (What she/he did):
The Pain Points (Where she/he struggled):
Adaptations (How she/he solved it):
The opportunities for improvement:

Template 3: Empathy Map (Your subjectʼs experience)

Role: Reflection on lived experience.

Description

The Empathy Tool is completed after shadowing, using observations and interactions from the activity. The Empathy Tool translates observation into human insight and ensures decisions remain grounded in lived experience.

Subject:
Observer/Interviewer:
Activity:
Date:
FEEL: (Emotions)
DO: (Actions, body language)

Template 4: Learning log (What the session teaches us)

Role: Signal capture

Description

The Learning Log is immidiately completed internally after KIIs and shadowing activities while observations are still fresh.. It documents what the field is telling us, based on direct observation and interviews.

Note:The Learning Log does not evaluate performance or assess feasibility. It records signals to
inform later decisions

<
Cycle/Date Issue Observed Root cause User Suggestion Feasibility of implementation (1-3) Empathy Insight

Template 5: Change log (Modifications made from learning log)

Role: Decision tracking

Description

The Change Log documents decisions taken in response to learning captured in the Learning Log. The Change Log ensures accountability and preserves institutional memory across cycles.

Date Reported Description of change Reason for change Status Date Completed Outcome of change

Template 6: After Action Review (Evaluate performance for next cycle)

Role: End-of-cycle evaluation

Description

The After-Action Review is conducted at the end of an implementation cycle to assess whether changes implemented led to the intended outcomes.

Cycle / Date Change Implemented Expected Outcome Actual Outcome Why (Context / RCA)
TOP