You are a senior MEAL specialist with expertise in complexity-responsive evaluation approaches. Your task is to create a Developmental Evaluation (DE) design for "program name" (from the material, if given) following Michael Quinn Patton's framework.
The program is "program description" (from the material, if given). It operates in a complex adaptive system characterized by "complexity features" (from the material, if given). Traditional evaluation approaches are insufficient because "reason" (from the material, if given).
Develop the following components:
-
DE Rationale and Positioning:
- Why Developmental Evaluation is the appropriate approach (vs. formative or summative evaluation)
- The eight principles of DE and how each applies to this program
- Relationship between the evaluator and the program team (embedded evaluator model)
- Boundaries: What DE will and will not provide
-
Complexity Mapping:
- Map the key elements of the complex system the program operates within
- Identify feedback loops, leverage points, and emergent properties
- Distinguish between simple, complicated, complex, and chaotic elements of the program (Cynefin framework application)
- Identify which program components are suitable for DE vs. traditional M&E
-
Emergent Learning Architecture:
- Initial framing questions (5-8 questions that guide the DE, acknowledging they will evolve)
- Question evolution protocol: How and when framing questions will be revisited and updated
- Rapid sensemaking cycles: Design a recurring cycle (e.g., "cycle length" (from the material, if given)) that includes:
- Data collection burst (what data, from whom, how)
- Sensemaking session design (who participates, facilitation approach, duration)
- Insight documentation template
- Adaptation recommendation format
- Decision tracking log
-
Real-Time Feedback System:
- Data streams to monitor continuously (quantitative dashboards, qualitative pulse checks, environmental scanning)
- Trigger thresholds: What signals indicate the program needs to adapt
- Communication channels between evaluator and program team
- Rapid reporting formats (1-page insight briefs, visual dashboards, verbal briefings)
-
Innovation Tracking Tools:
- Innovation log template: Track what is being tried, why, what happened, what was learned
- Pivot documentation: When the program model changes, how to document the before/after and the reasoning
- Adaptation timeline: A living document showing the evolution of the program model over time
- Failure and learning documentation: How to capture and value productive failures
-
Utilization Strategy:
- How DE findings will be integrated into program decision-making in real-time
- Decision rights: Who can act on DE insights and at what level
- Learning culture building: How the DE process itself strengthens organizational learning
- Stakeholder engagement: How different stakeholders access and use DE outputs
-
DE Evaluator Role Description:
- Core competencies required
- Time commitment and embedding arrangement
- Relationship management with program team
- Independence safeguards within the embedded model
-
Transition Planning: How the DE will evolve as the program matures, including criteria for transitioning from developmental to formative or summative evaluation.
Output Format:
Deliver all components as clearly labeled sections. Include templates for the innovation log, insight brief, and decision tracking log as formatted tables. The complexity map should be described in enough detail to be visualized.
Where the material is silent, write "Not in the material" rather than guessing.
Source material: Attached, or pasted below. Base everything above on it and do not invent details that are not in it.