RDP-assumption-template/insex.html at main · fangjui/RDP-assumption-template · GitHub

1
2
3
4
5
6
7
8
9
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
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>RDP EC Engagement Platform — Assumptions and evidence</title>

<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link href="https://fonts.googleapis.com/css2?family=Fraunces:opsz,wght,SOFT@9..144,300..600,30..100&family=IBM+Plex+Sans:wght@300;400;500;600&family=IBM+Plex+Mono:wght@400;500&display=swap" rel="stylesheet">

<style>
  *, *::before, *::after { box-sizing: border-box; margin: 0; padding: 0; }

  body {
    font-family: 'IBM Plex Sans', system-ui, sans-serif;
    background: #F5F3F0;
    color: #0E1B2C;
    -webkit-font-smoothing: antialiased;
  }

  .page {
    max-width: 860px;
    margin: 0 auto;
    padding: 56px 40px 80px;
  }

  /* ─── Section header ───────────────────────────────────────── */
  .eyebrow {
    font-family: 'IBM Plex Mono', monospace;
    font-size: 11px;
    letter-spacing: 0.12em;
    text-transform: uppercase;
    color: #6B7280;
    margin-bottom: 10px;
  }

  .section-title {
    font-family: 'Fraunces', Georgia, serif;
    font-variation-settings: "opsz" 72, "SOFT" 30;
    font-size: 38px;
    line-height: 1.15;
    font-weight: 400;
    color: #0E1B2C;
    margin-bottom: 12px;
  }

  .section-intro {
    font-size: 15px;
    line-height: 1.6;
    color: #2A3A52;
    max-width: 60ch;
    margin-bottom: 32px;
  }

  /* ─── Legend ───────────────────────────────────────────────── */
  .legend {
    display: flex;
    gap: 20px;
    flex-wrap: wrap;
    margin-bottom: 24px;
  }
  .legend span {
    display: inline-flex;
    align-items: center;
    gap: 7px;
    font-size: 13px;
    color: #2A3A52;
  }
  .dot {
    display: inline-block;
    width: 8px;
    height: 8px;
    border-radius: 50%;
  }
  .dot-in  { background: #2E4FA8; }
  .dot-inc { background: #ef9f27; }

  /* ─── Evidence cards ───────────────────────────────────────── */
  .ev-card {
    background: #FFFFFF;
    border: 1px solid #E2DDD8;
    border-left: 4px solid #2E4FA8;
    border-radius: 10px;
    overflow: hidden;
    margin: 18px 0;
  }
  .ev-card.incoming { border-left-color: #ef9f27; }

  .ev-card .ev-head { padding: 20px 24px 16px; }
  .ev-card .ev-label {
    font-family: 'IBM Plex Mono', monospace;
    font-size: 11px;
    letter-spacing: 0.12em;
    text-transform: uppercase;
    color: #6B7280;
    margin-bottom: 6px;
  }
  .ev-card .ev-claim {
    font-family: 'Fraunces', Georgia, serif;
    font-variation-settings: "opsz" 72, "SOFT" 30;
    font-size: 18px;
    line-height: 1.3;
    font-weight: 400;
    color: #0E1B2C;
  }

  .ev-card .ev-body {
    display: grid;
    grid-template-columns: 1fr 1fr;
    border-top: 1px solid #E8E3D3;
  }
  .ev-card .ev-cell { padding: 16px 24px; }
  .ev-card .ev-cell:first-child { border-right: 1px solid #E8E3D3; }

  .ev-card .ev-cell .cell-label {
    font-family: 'IBM Plex Mono', monospace;
    font-size: 10px;
    letter-spacing: 0.12em;
    text-transform: uppercase;
    color: #2E4FA8;
    margin-bottom: 8px;
  }
  .ev-card.incoming .ev-cell .cell-label { color: #854f0b; }
  .ev-card .ev-cell p { font-size: 14px; color: #2A3A52; line-height: 1.55; margin: 0; }

  .ev-card .ev-changed {
    padding: 14px 24px;
    background: #F5F3F0;
    border-top: 1px solid #E8E3D3;
  }
  .ev-card .ev-changed .cell-label { color: #993c1d; }
  .ev-card .ev-changed p { font-size: 14px; color: #0E1B2C; line-height: 1.55; margin: 0; }

  @media (max-width: 600px) {
    .ev-card .ev-body { grid-template-columns: 1fr; }
    .ev-card .ev-cell:first-child { border-right: none; border-bottom: 1px solid #E8E3D3; }
    .section-title { font-size: 28px; }
    .page { padding: 36px 20px 60px; }
  }
</style>
</head>
<body>
<div class="page">

  <div class="eyebrow">RDP EC Engagement Platform · Assumptions and evidence</div>
  <h1 class="section-title">What we assumed, what broke, what changed</h1>
  <p class="section-intro">From the research and testing session on 8 June 2026. These are the assumptions the platform has been running on, what the research found, and what we are changing as a result.</p>

  <div class="legend">
    <span><span class="dot dot-in"></span> In hand: from the 8 June session and prior sprints</span>
    <span><span class="dot dot-inc"></span> Incoming: to be resolved in next phase</span>
  </div>

  <!-- ─── Assumption A1 ─────────────────────────────────────── -->
  <div class="ev-card">
    <div class="ev-head">
      <div class="ev-label">Assumption A1 · Platform role</div>
      <div class="ev-claim">The engagement platform's job is to present information and let people draw their own connections.</div>
    </div>
    <div class="ev-body">
      <div class="ev-cell">
        <div class="cell-label">How we tested</div>
        <p>Research sessions with participants across the Don catchment. Post-engagement interviews asking whether the platform helped people see a connection between what they could see and what they could do.</p>
      </div>
      <div class="ev-cell">
        <div class="cell-label">What we found</div>
        <p>People couldn't see the link between individual action and collective outcome. The information was there; the pathway to action was not. The platform presented data but didn't help people move from noticing to doing.</p>
      </div>
    </div>
    <div class="ev-changed">
      <div class="cell-label">What changed</div>
      <p>The platform needs to make the pathway explicit: not just what is happening, but what can I do, and what changes as a result. Clarifying functionality before language is the priority.</p>
    </div>
  </div>

  <!-- ─── Assumption A2 ─────────────────────────────────────── -->
  <div class="ev-card">
    <div class="ev-head">
      <div class="ev-label">Assumption A2 · Digital value</div>
      <div class="ev-claim">People who care for the river will find a digital platform a useful companion to that care.</div>
    </div>
    <div class="ev-body">
      <div class="ev-cell">
        <div class="cell-label">How we tested</div>
        <p>Qualitative research and usability sessions with participants who already engage with the river in some way — walking, volunteering, swimming, monitoring.</p>
      </div>
      <div class="ev-cell">
        <div class="cell-label">What we found</div>
        <p>Some people said they didn't need a digital platform to care for the river. Others were already using tools like Merlin for personal knowledge — unidirectional, self-serving. The bar for a platform that demands something back is significantly higher.</p>
      </div>
    </div>
    <div class="ev-changed">
      <div class="cell-label">What changed</div>
      <p>The platform needs to demonstrate tangible worth before asking for contribution. The question is not how to explain it better, but what functional outcome makes people feel it is making a difference.</p>
    </div>
  </div>

  <!-- ─── Assumption A3 ─────────────────────────────────────── -->
  <div class="ev-card">
    <div class="ev-head">
      <div class="ev-label">Assumption A3 · Mission clarity</div>
      <div class="ev-claim">The strategic direction of the platform is clear enough to guide design priorities.</div>
    </div>
    <div class="ev-body">
      <div class="ev-cell">
        <div class="cell-label">How we tested</div>
        <p>Internal discussion across Hive, Opus, and DML in the 8 June session, alongside researcher feedback from the ground-level engagement work.</p>
      </div>
      <div class="ev-cell">
        <div class="cell-label">What we found</div>
        <p>The platform has a wide boundary goal (bioregional health) and a utility (decentralised stewardship), but lacks articulated strategic hunches — the specific bets about how change actually happens. Without those, design and communication decisions lack a stable basis.</p>
      </div>
    </div>
    <div class="ev-changed">
      <div class="cell-label">What changed</div>
      <p>Next step: Hive, Opus, and DML each work in parallel to articulate strategic hunches, then come together to prioritise the backlog of improvements against them. July 6 session is the convergence point.</p>
    </div>
  </div>

  <!-- ─── Assumption A4 ─────────────────────────────────────── -->
  <div class="ev-card">
    <div class="ev-head">
      <div class="ev-label">Assumption A4 · Scale of geography</div>
      <div class="ev-claim">A bioregional scale of data is the right entry point for most users.</div>
    </div>
    <div class="ev-body">
      <div class="ev-cell">
        <div class="cell-label">How we tested</div>
        <p>Platform design and user testing sessions, and discussion with James around the neighbourhood mapping work covering 147 areas across South Yorkshire.</p>
      </div>
      <div class="ev-cell">
        <div class="cell-label">What we found</div>
        <p>People locate themselves through neighbourhoods first, not bioregions. The existing neighbourhood data layer (already mapped) could help people locate themselves in relation to the catchment and to active groups nearby. Large stretches of the Don have no community engagement at all — a bioregional view risks reinforcing existing patterns of who engages.</p>
      </div>
    </div>
    <div class="ev-changed">
      <div class="cell-label">What changed</div>
      <p>Neighbourhood layer to be explored as an addition. Any new layer needs to answer: what does this give me, and what can I do with it? That question applies before adding data, not after.</p>
    </div>
  </div>

  <!-- ─── Assumption A5 ─────────────────────────────────────── -->
  <div class="ev-card">
    <div class="ev-head">
      <div class="ev-label">Assumption A5 · Participation logic</div>
      <div class="ev-claim">People will participate more if the platform captures their hunches, observations, and care actions in one place.</div>
    </div>
    <div class="ev-body">
      <div class="ev-cell">
        <div class="cell-label">How we tested</div>
        <p>Session discussion and Fang's proposal of a hunch framework: I am sensing this, my embodied experience is this, my hunch is we could do this together.</p>
      </div>
      <div class="ev-cell">
        <div class="cell-label">What we found</div>
        <p>The idea of capturing hunches resonated, but raised a harder question: is it the platform's job to hold hunches, or to bring people together to have the conversations that produce them? The two are not the same, and conflating them risks building the wrong thing.</p>
      </div>
    </div>
    <div class="ev-changed">
      <div class="cell-label">What changed</div>
      <p>Reframe: the platform is a point of connection that enables people to move along a journey — from noticing, to understanding, to collective action. It does not need to capture everything; it needs to facilitate the next step.</p>
    </div>
  </div>

  <!-- ─── Incoming ──────────────────────────────────────────── -->
  <div class="ev-card incoming">
    <div class="ev-head">
      <div class="ev-label">Incoming · next phase</div>
      <div class="ev-claim">What the next phase of work needs to resolve.</div>
    </div>
    <div class="ev-body">
      <div class="ev-cell">
        <div class="cell-label">Being worked on</div>
        <p>Hive and Opus: UX-level improvements backlog, scored and prioritised. DML: strategic hunches articulated, with new platform utility requirements derived from them. Researchers: qualitative analysis of workshop outputs completed.</p>
      </div>
      <div class="ev-cell">
        <div class="cell-label">Convergence point</div>
        <p>Joint session on 6 July. The output is a shared prioritisation of what the platform does next — both immediate UX fixes and the longer-term capability build — against a costed view of what is fundable within the current project and what needs a separate raise.</p>
      </div>
    </div>
    <div class="ev-changed">
      <div class="cell-label" style="color:#854f0b;">Why this matters</div>
      <p>The research window is closing. Julian leaves at the end of the academic year. The evidence gathered in this phase needs to feed directly into what the platform becomes next, and into the case made to future funders.</p>
    </div>
  </div>

</div>
</body>
</html>