Evidano is an AI-powered qualitative data analysis platform that supports AI-enabled workflows for turning qualitative inputs into usable decision tools. On 10 June 2026 a Nature article, “Building user-driven climate adaptation products” (Chaudhry et al.), reviewed how user-centred design strengthens co-production for climate adaptation. If you run interviews, workshops, or pilot products, this piece explains what to measure and how to convert qualitative inputs into usable decision tools. Read the full review at Nature. This post shows how to run a focused qualitative analysis of climate services and maps each step to AI-enabled workflows in Evidano (see Evidano) so teams can cut synthesis time and improve uptake.
Key Takeaways
Chaudhry et al. (Nature, 10 Jun 2026) show that combining co-production with iterative user-centred design produces more usable climate adaptation products. Qualitative researchers should adopt reproducible codebooks, cross-segment comparisons, and usability testing to convert interviews and workshop notes into actionable product requirements.
- Source: Nature.
- Use reproducible codebooks and explicit segment definitions to make qualitative findings actionable for product design and impact monitoring.
- Add iterative usability testing and cross-segment analysis to increase uptake, trust, and measurable impact of climate services.
Fast take: why the review matters for qualitative researchers
Chaudhry et al. (Nature, 10 Jun 2026) synthesise literature on co-production and user-centred design to identify barriers to usable climate services and practical design patterns to overcome them. Key signals are: engagement modality matters, usability testing is underused, and metrics for co-production impact are inconsistent.
- Source: Building user-driven climate adaptation products, Nature
- Audience payoff: concrete targets for qualitative analysis (usability, trust, inclusion) and a replicable workflow for converting interviews and workshop notes into product requirements.
- Short win: apply thematic plus cross-segment analysis to identify mismatches between producer assumptions and user needs.
Findings snapshot
| Item | Value / Note | Why it matters |
|---|---|---|
| Publication | Nature, 10 Jun 2026; Chaudhry et al. | High-impact synthesis of co-production and UX literature |
| Focus | User-centred design integrated with co-production | Explains gaps between climate data supply and practical use |
| Common gaps identified | Low usability testing; unclear impact metrics; power imbalances | Targets for qualitative analysis and stakeholder engagement |
| Recommended outputs | User journeys, personas, co-produced requirements, evaluation metrics | Directly map to product design and impact monitoring |
What happened (plain English)
The authors performed a systematic review and analysis of literature on climate services, co-production, and user-centred methods. The authors cross-referenced case studies and methodology papers to distil practical recommendations for developing adaptation products that users adopt.
- The review emphasises mixing co-production (shared decision-making) with iterative UX methods, such as usability tests, prototypes, and personas.
- The review flags recurring qualitative research pain points: inconsistent participant selection, missing codebooks, and weak cross-segment comparisons.
- The authors argue that rigorous, repeatable qualitative workflows will improve trust, usability, and measurable impact of climate services.
So what for qualitative researchers and UX teams?
For researchers
Researchers should prioritise reproducible codebooks and explicit segment definitions, specifying who counts as a user and what decisions they make. Researchers should use triangulation: interviews, workshop notes, and observational logs to validate themes the review highlights, such as trust, actionable guidance, and timeliness.
For UX / product teams
UX and product teams should translate themes into measurable usability tests and prototype acceptance criteria, for example confirming whether users can find forecast thresholds within 60 seconds. UX and product teams should design for inclusion and document power dynamics raised by the review, adapting recruitment and facilitation accordingly.
For policy & program teams
Policy and program teams should define impact metrics for co-production, including engagement quality, decision uptake, and operational change, and they should capture qualitative evidence to explain why decisions changed. Policy and program teams should report both process indicators (who was engaged and how often) and outcome indicators (policy adjustments and resource allocation).
Do more, faster with Evidano (map to the review)
Overview
Evidano helps teams operationalise the review’s recommendations by ingesting qualitative inputs, supporting reproducible coding, and generating stakeholder-ready outputs.
Ingest interviews, workshops, and reports
Evidano accepts transcripts, PDFs, or survey sheets for analysis. The platform supports transcription with custom dictionaries, which is useful for preserving local place names and domain terms highlighted by the review.
Build a reproducible codebook and run thematic analysis
Evidano lets teams import or create a single codebook and apply it across the corpus to show theme frequencies and co-occurrence networks, enabling tracking of trust, usability, and inclusion themes the Nature review prioritises.
Compare segments and validate claims
Evidano supports cross-segment frequency analysis, for example by role, region, or vulnerability cohort, so teams can test whether themes are universal or specific, directly addressing the review’s call for clear segment comparisons.
Speed stakeholder-ready outputs
Evidano can generate visualizations such as word clouds, hierarchical code-to-subcode trees, and co-occurrence graphs, and export clickable quotes for briefs, shortening the path from qualitative insight to design decision.
Secure, auditable research workflow
Evidano stores data with encryption and does not use customer data to train third-party models, which is helpful when co-production involves sensitive community information as the review warns.
Checklist: 7-step workflow to reproduce the review’s recommendations
This 7-step checklist converts qualitative inputs into an operational climate service aligned with the review’s recommendations.
- 1) Define segments and decision contexts, specifying who, what decision, and timeframe.
- 2) Collect mixed qualitative inputs, including interviews, workshop notes, and surveys.
- 3) Transcribe with a domain dictionary and redact PII as needed.
- 4) Import to Evidano and create or import a codebook reflecting trust, usability, and inclusion nodes.
- 5) Run thematic and cross-segment frequency analyses, and inspect co-occurrence to find friction points.
- 6) Prototype UI and communication changes, run lightweight usability tests, and capture short qualitative feedback rounds.
- 7) Produce stakeholder-ready visual reports and an impact log that includes process and outcome indicators.
FAQ: qualitative analysis of climate services
How do I compare themes across regions reliably?
Predefining segment labels provides a reliable basis for comparisons across regions. Ensure consistent transcription and code application, then use cross-segment frequency and simple statistical summaries to show differences and overlaps.
What if participants speak many local languages?
Use translation with custom dictionaries to preserve technical terms and place names. Evidano supports translation with glossary controls to avoid term drift and to keep domain-specific terminology consistent.
How do we measure co-production impact?
Measure co-production impact with a combination of qualitative indicators and process metrics. Combine quotes showing decision influence with measures such as participation depth and prototype iterations, and track changes in decisions or operations over time.
Wrapping up: next moves
Chaudhry et al.’s 10 June 2026 review makes a clear case that co-production combined with disciplined UX methods yields more usable climate adaptation products. For teams doing qualitative analysis, reproducible codebooks, cross-segment tests, and rapid prototyping tied to measurable outcomes are practical next steps.
- Try the 7-step workflow above on a pilot corpus (one project or region) and iterate.
- See how Evidano maps each step: Evidano.
- Ready to convert interviews into product requirements? Try Evidano for free.