Mastercard FoundationConcept Development
Back to Home
Step 2

Concept Development

Shapes promising ideas into a coherent program concept by articulating the intended change aligned to country or platform roadmap, key pathways, and feasibility.

Role of the Impact Delivery (ID) Team

Facilitate (light-touch) the translation of the idea into a coherent concept by supporting an initial Theory of Change, clarifying pathways and assumptions, and prioritizing learning questions. Review the concept note for coherence and feasibility and recommend key refinements before proposal development.

ID support covers

  • Concept Note Development

The ID team supports the development of the concept note by facilitating Theory of Change and impact-oriented program design guidance. This includes alerting ELI to landscaping, rapid reviews, or other studies required; supporting articulation of evidence needs and development of Terms of Reference; supporting programs in the use of landscaping and rapid reviews in refining the concept note; and supporting development of high-level Theory of Change and Impact Pathways. Light-touch MEL support is provided to avoid over-engineering at this stage.

ID Team Activities

  • Facilitate Theory of Change and impact-oriented program design guidance (capacity strengthening)
  • Alert ELI to landscaping, rapid reviews, or other studies required
  • Support articulation of evidence needs and development of Terms of Reference
  • Support programs in the use of landscaping and rapid reviews in refining the concept note
  • Support development of high-level Theory of Change and Impact Pathways
  • Light-touch MEL support to avoid over-engineering at this stage (quality assurance)

Key Tools & Resources

Impact Orientation Modules 1 & 2Guide to Shared Measures Framework 2.0 and annexesToC GuidelinesGuidance on Counting Youth in WorkYouth in Work FAQ

Foundation Requirements

An initial Theory of Change showing impact pathways and assumptions is required. Areas where evidence is weak or missing for effective design must be explicitly called out. Preliminary consideration of partner MEL feasibility and risks.

  • A documented high-level Theory of Change must exist before proposal development
  • Learning questions must be defined prior to moving forward