A team that stopped patching
Example case · Organisation
A team that stopped patching
A communications team wanted to reach people, not tie systems together.
01
The question
Website here, sign-ups there, the newsletter somewhere else, a course in yet another system. Every update cost an afternoon, every new colleague a week of training. The team wanted to tell a story, but was mostly patching.
Four systems, one story that was not told.
02
What we did together
-
The story first
Two conversations about whom they want to reach and what those people need to know. The technology came after.
-
One place
Pages, forms, events, a short scan and a learning path for new volunteers, in one place and in two languages.
-
In the driving seat
The team changes texts and photos itself, without a developer and without plug-ins.
03
What came of it
- 4 → 1
- systems to one place
- 2
- languages, one page
- 0
- plug-ins to keep up
“We make content again instead of maintenance.”
[Name], communications adviser
04
What lasts
A website is not a goal. It is the front door of a community. Whoever gets their time back spends it on people. And the knowledge stays in the team, even when someone leaves.
Time back for people.
05
Is your team stuck in loose systems too?
This story is an example: it shows what a collaboration looks like. Real stories follow, with the permission of the people they are about.
