Rigorous Futures: qualitative analysis of long-term thinking

Fast payoff: convert the HBR IdeaCast episode “How to Bring More Rigor to Your Long-Term Thinking” (Aug 19, 2025, Episode 1040) into repeatable qualitative evidence you can act on. Nick Foster lays out four lenses (could, should, might, don’t) that teams habitually use (and misuse) when they imagine futures. This post shows UX researchers, strategy teams, and policy analysts how to run a focused qualitative analysis of long-term thinking (primary keyword) across transcripts, meeting notes, and workshops, and how AI tools like www.evidano.com speed coding, cross-segment comparison, and scenario synthesis. Read the original HBR episode at www.hbr.org/podcast/2025/08/how-to-bring-more-rigor-to-your-long-term-thinking and use the 7-step workflow below to move from fuzzy futures talk to evidence-based decisions.

Findings Snapshot

Date	Metric / Item	Value	Note / Implication
Aug 19, 2025	Source	HBR IdeaCast; Episode 1040	Guest: Nick Foster (author of Could, Should, Might, Don’t)
Qualitative lens	Core concept	4, could / should / might / don’t	Use all four for balanced futures thinking
Organizational tip	Practical ask	Carve 10 minutes into meetings	Embed futures prompts across teams
Outcome for research	What to code for	Aspirations, certainties, scenarios, constraints	Map themes to adoption paths and mundane use

What the HBR episode says (plain English)

Nick Foster argues that most organizations default to one of four future-thinking modes (could (tech-utopia), should (data-certainty), might (scenarios), and don’t (constraints/risks)) and that rigor requires applying all four in parallel and at granular levels.

Why it matters: short horizons and siloed ‘futures labs’ produce brittle strategy that misses knock-on effects.
Key insight: ground long-term scenarios in the ‘future mundane’, how average users will actually use products in everyday contexts.
Practical barrier: ROI and timelines make senior teams stop at inspirational or defensive narratives instead of actionable implications.

Implications for researchers: qualitative analysis of long-term thinking

For UX & product researchers

Code for the four lenses across interviews and workshop transcripts (label verbatims as could/should/might/don’t).

Look for adoption inflection points: what ordinary users would need to change behaviour (Foster’s “future mundane”).

Output: evidence-backed experience maps that show plausible 2–10 year adoption steps.

For strategy & foresight teams

Use cross-segment frequency analysis to test which scenarios (might) have traction across customer cohorts and which ‘should’ narratives rest on thin data.

Translate scenario themes into decision triggers (e.g., if X reaches 15% adoption, release Y).

Output: scenario-to-decision matrix with confidence bands.

For policy and compliance analysts

Flag 'don’t' themes early and code negative externalities so mitigation shows up as measurable policy levers.

Compare narratives across stakeholder transcripts (citizens, regulators, industry) to surface misalignment.

Output: prioritized risk register tied to qualitative evidence.

Do this in Evidano: map HBR’s framework to AI-enabled qualitative workflows

Problem: fragmented transcripts and workshops → Solution: unified ingestion

Import interview transcripts, meeting notes, and slide decks into Evidano to create a single corpus for analysis.

Benefit: consistent baseline for coding across teams and projects.

Problem: inconsistent coding of futures talk → Solution: codebook + AI-assisted coding

Upload a codebook that defines could/should/might/don’t, then use Evidano’s AI-assisted coding to tag quotes at scale and refine with human-in-the-loop.

Benefit: reproducible thematic and frequency analyses with exportable code hierarchies.

Problem: comparing segments (persona, region, timing) → Solution: cross-segment analysis

Run cross-segment frequency and co-occurrence networks to see which scenarios resonate by cohort and where risks cluster.

Benefit: evidence for prioritizing which futures to operationalize or mitigate.

Problem: follow-up evidence needed → Solution: AI avatar interviews & chat over docs

Spin up AI avatar interviews to probe weak signals or run follow-ups autonomously; use Evidano’s chat to surface quotes and visualizations instantly.

Benefit: speed-to-insight and iterative validation without manual scheduling overhead.

Security & governance

Data is encrypted in Evidano and never used to train third-party models, important when dealing with sensitive strategy and participant data.

Benefit: compliant, research-grade environment for foresight work.

7-step checklist: from transcript to futures decision

Follow these steps to run a qualitative analysis of long-term thinking quickly and reproducibly:

1) Gather inputs: transcripts, workshop notes, slide decks, and surveys; note date (e.g., Aug 19, 2025 episode as reference).
2) Define codebook: create labels for could/should/might/don’t plus adoption, friction, ethics, and mundane-use.
3) Ingest into Evidano: upload documents and spreadsheets to a single project in www.evidano.com.
4) Auto-transcribe & normalize: run transcription/translation where needed; apply custom dictionary for domain terms.
5) AI-assisted coding + manual review: apply the codebook, review edge cases, and lock codes.
6) Analyze: run thematic, frequency, co-occurrence, and cross-segment comparisons to surface decision triggers.
7) Deliver: export a scenario-to-decision matrix, evidence-backed quotes, and visuals (word cloud / network) for stakeholders.

Common questions researchers ask

Q: How do I compare ‘could’ vs ‘don’t’ mentions reliably?

A: Use the codebook to tag each quote, then run normalized frequency by transcript length and by segment to avoid sample-size bias.

Q: How granular should scenario coding be?

A: Start with the four meta-lenses, then add 6–10 subcodes (e.g., adoption-barriers, regulation, cost, UX friction) so themes remain actionable.

Q: Is AI safe for sensitive strategy documents?

A: Choose platforms with encryption and no third-party model training. Evidano provides secure processing and tenant isolation for confidential corpora.

Wrapping up & next step (strong CTA)

Nick Foster’s Aug 19, 2025 HBR episode gives a usable lens: apply could/should/might/don’t across your qualitative corpus, ground scenarios in the future mundane, and convert narratives into decision triggers.

Ready to run a pilot? Import one transcript or 10 workshops into www.evidano.com, upload a simple codebook, and run the thematic + cross-segment analyses in under a day.
Start a two-week pilot to prove impact: map scenarios to 2–3 actionable triggers and present an evidence-backed roadmap to your leadership.

Try Evidano to compress weeks of manual synthesis into hours and keep your futures work rigorous, auditable, and secure: www.evidano.com.

Keep reading

Browse all articles