ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
2

The Data-Need Matrix is a facilitation tool part of the operability workshops (refer to worksheet 3.2 for more details) to explore what datasets or technical components are available, reusable, or missing for a given service idea. It helps participants assess feasibility and identify gaps.
3
Step 1. Formulating User needs
-> Each column represents a Need (e.g., “Urban Heat,” “Water Management,” “Biodiversity”).
-> Needs can be formulated with varying levels of granularity: Broad themes, specific problems, explicit functionalities
-> Cluster the needs based on the service scope or user priorities identified in previous workshops.
4
5
Step 2. Evaluating the potentiel use of each component to address each need
-> This is done by filling the intersections of rows and columns in the matrix, where each row represents a component and each column represents a user need
-> Depending on the desired level of detail, intersections can be marked in multiple ways:
Binary indicator: A simple checkmark or cross indicates that the component is relevant, while an empty cell indicates no relevance.
Graded scale: Use categories such as none, low, medium, high, or mandatory to indicate varying levels of relevance.
Descriptive evaluation: Provide a concise explanation of how the component contributes to satisfying the need, including potential limitations or caveats.
6
Step 3. Documenting component details
Where needed, add short notes (e.g., on data quality, licensing, or access).
7
Step 4. Organizing the matrix
-> Reorganize the matrix (move columns and rows) to make patterns, clusters, and key components more visible
-> Discuss which components are strong assets, which need partnerships, and which represent critical gaps.
8
9
Step 5. Developing a design path and action plan
-> Identify shared components and sketch up an initial concept for the service architecture.
-> Assess critical gaps (components that are immature, unavailable, or limited in functionality).
-> Prioritize development based on the service’s objectives, component commonality, availability, and critical gaps
-> Engage critical partners who can provide missing components, co-develop solutions, or address technical gaps, ensuring the plan is feasible and accelerating implementation.
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100