problem definition
How a need, task or desired outcome is framed before choosing an intervention.
Where the boundary lies
A technology capability without an articulated need is not problem definition.
See an example →Research edition · Recorded claims, context and disagreements · About the collection ↗
THE EVENT TAXONOMY
Putting ideas to work
How do tools fit the workflow, context and continuing capacity of real organisations?
workflow integration
Embedding tools, evidence and actions in an operational sequence.
Where the boundary lies
Standalone model capability does not establish usable organisational integration.
See an example →capacity
Staff time, skills, organisational resources or complementary capability required to act.
Where the boundary lies
A rule assigning responsibility does not establish capacity to fulfil it.
See an example →maintenance
Resources and practices needed to keep a system useful and safe after launch.
Where the boundary lies
A rapid first build or one-off pilot is not maintained service.
See an example →contextual adaptation
Modification or limits required by local language, setting, sector or task.
Where the boundary lies
Repetition of the same product across sites is not evidence of adaptation.
See an example →adoption
Actual uptake, sustained use or the gap between attention and useful use.
Where the boundary lies
Publicity and volunteer enthusiasm are not equivalent to customer transactions.
See an example →reliability
Whether systems function consistently under intended conditions.
Where the boundary lies
Technical functioning alone does not establish fair institutional purpose.
See an example →implementation path
Concrete routes or open operational questions about moving from proposal to practice.
Where the boundary lies
An aspiration without a practical route remains normative framing.
See an example →automation
Replacement or augmentation of tasks through robots or AI and the organisational response.
What the comparisons suggest.
Better information changes outcomes only through people and institutions able and willing to act.
The event repeatedly names a missing step between producing an answer and changing a decision. Evidence may reveal conflicting priorities without resolving them.
Follow the evidence →Device ownership and expressed interest are incomplete measures of effective access.
Charging, installation costs, household relations, usable language and trusted intermediaries determine whether a service reaches people. Starting with current users can hide exclusion.
Follow the evidence →A working pilot is only one step toward sustained institutional use.
Permanent monitoring, operational expertise, context and a stable funding horizon must accompany technical capability. Early attention or fundraising is not an impact result.
Follow the evidence →Watch and question.
All passages in this theme →
1:01Draw the decision before choosing the tool
Start with the workflow, human decisions and intended benefit.
Likely speaker
1:18Who funds safety after the pilot?
A practitioner challenges short grants that leave nobody to monitor deployed systems.
Likely speaker
Unidentified audience participant
1:47Match the evidence to the question
Why trials, qualitative knowledge and institutional analysis answer different questions.
Likely speaker
2:23Interest is not the same as access
The adoption gap starts before installation: devices, data cost and household control.
Likely speaker
3:11An ethical promise still needs user value
Fairbnb’s publicity did not solve marketplace density and matching problems.
Likely speaker
2:57Where cooperative ownership stops
Overseas subsidiaries expose the limits and conditions of a shared-ownership model.
Likely speaker
Themes can overlap. Counts describe this collection; they do not measure importance, agreement or prevalence outside the event.