The inquiry
What are we trying to understand?
Can participants move from an initially assumed explanation of a community problem toward a more contextual, evidence-informed problem definition? Can they explain how the evidence changed their reasoning, identify what remains uncertain and work with others to propose a proportionate next step?
Primary question
What evidence indicates that participants are becoming more capable of framing a complex local problem before proposing a solution?
Assessment boundary
What the Field Lab would and would not assess
It can examine
- observable changes in how a team defines a problem
- the relevance and diversity of evidence gathered
- how claims are connected to evidence
- whether assumptions and uncertainties are made visible
- how participants respond to critique
- how responsibility and judgment are shared
It cannot establish
- a universal score of intelligence or potential
- how a participant will perform in every context
- the cause of change without an appropriate research design
- that a polished final presentation reflects every member's capability
- that short-term performance will persist
- that capability alone guarantees opportunity
Capability trace
How the inquiry moves from purpose to learning
- 01
Purpose
Understand whether a short, team-based community challenge helps participants strengthen evidence-informed problem framing and collaborative judgment.
- 02
Learning design
A four-week sprint combines local observation, stakeholder interviews, team analysis, critique and a public recommendation.
- 03
Activity
Participants investigate a recurring community water-access problem and propose a small, testable response.
- 04
Evidence
Facilitator observations, interview plans, field notes, decision logs, draft models, peer critiques, final recommendations and participant reflections.
- 05
Human interpretation
Two trained reviewers examine the evidence against shared criteria, record alternative explanations and identify where evidence is insufficient.
- 06
Opportunity
Participants receive targeted feedback and may be invited to refine the proposal with community partners. No employment or funding decision is made from this sprint alone.
- 07
System learning
The programme team reviews which activities produced useful evidence, where the rubric failed and what should change before another sprint.
Evidence plan
Evidence is collected across time and perspectives
| Evidence source | What it may reveal | Important limitation |
|---|---|---|
| Initial problem map | Starting assumptions, causal reasoning and missing perspectives | May reflect prior familiarity with mapping tools |
| Interview plan and field notes | Question quality, listening and attention to context | Access to stakeholders may vary across teams |
| Decision log | How evidence changes or fails to change team decisions | Written records may omit informal reasoning |
| Peer critique and response | Ability to evaluate claims and revise work | Social dynamics may affect candour |
| Final problem frame and proposal | Coherence, proportionality and evidence use | A team artifact cannot establish each member's capability |
| Individual reflection | Metacognition, uncertainty and perceived contribution | Self-report is evidence, but not independent verification |
Illustrative findings
What the Field Lab might discover
Pattern 1: Broader problem framing
Five of six teams moved from a single-cause explanation toward a problem frame containing infrastructure, household practices, institutional coordination and seasonal constraints. This supports a cautious inference that the inquiry activities helped teams attend to interacting causes.
Confidence: moderate. The artifact change is clear, but the example design does not isolate which activity produced it.
Pattern 2: Uneven use of evidence
Four teams cited stakeholder evidence when revising their proposals. Two teams collected relevant observations but retained their original solution with little explanation. This challenges any claim that evidence collection alone leads to evidence-informed judgment.
Confidence: moderate. Reviewer agreement was strong, but team decision logs were incomplete.
Pattern 3: Participation was not evenly distributed
Presentation quality improved across all teams, yet observation records suggest that a small number of members shaped most decisions. The final team product therefore provides insufficient evidence about each participant's collaborative capability.
Confidence: preliminary. More individual evidence and participant validation would be needed.
Interpretation
What can responsibly be concluded?
The illustrative evidence supports a narrow conclusion: structured inquiry, critique and revision may help teams produce more contextual problem frames. It also reveals a design weakness. Team artifacts can conceal uneven participation and should not be treated as complete evidence of individual capability.
The Field Lab would keep observation, evidence and interpretation distinct. Reviewers would record confidence, disagreements and alternative explanations. Participants would have an opportunity to correct factual errors and add context without being asked to accept every interpretation.
Claims that should not be made
- Participants became universally better problem solvers.
- The sprint caused every observed change.
- The strongest presentation came from the most capable team.
- Participants who spoke less had less capability.
- The same design will work in another setting without adaptation.
System learning
What should change before the next sprint?
- Add brief individual evidence checkpoints before and after team decisions.
- Ask teams to mark which evidence changed a claim and which evidence did not.
- Invite participant review of observation summaries before interpretation is finalized.
- Train facilitators to document participation without equating visibility with contribution.
- Test whether the rubric works consistently across languages and communication styles.
Safeguards
Conditions for responsible use
- Participation and evidence use are explained in accessible language.
- Only evidence required by the inquiry purpose is collected.
- Protected participant records remain separate from public learning outputs.
- Reviewers document uncertainty and potential bias.
- No automated system makes a consequential decision about a participant.
- Participants can question factual accuracy and understand how evidence is used.
- Retention, access and deletion rules are established before evidence collection.
The value of the Field Lab
Assessment becomes a disciplined learning process.
A Field Lab does more than produce a result. It makes the relationship between purpose, activity, evidence, interpretation, opportunity and system learning inspectable. Its most useful discovery may be that the original question, activity or assessment was incomplete.