Drafting a content design skill framework<\/h2>\n\n\n\n
We have had a skill framework for user experience and user interface design since early 2023. Since the summer of 2024, we have also had one for user research. That leaves about 23% of our user-centred design colleagues uncovered. Neither content nor communication design has a substantial description of the skills and experiences they should have at what level. As the next bigger discipline, Torsten and I reserved time to take a first tab on it.<\/p>\n\n\n\n
From the start, we wanted the structure to follow the existing skill frameworks for the other sub-disciplines. There, we have 12 skills in 4 skill areas. Half of the skill areas and skills inside are similar to almost identical \u2013 grouped as \u2018communicate and collaborate\u2019 and \u2018supporting people and change\u2019. We focussed on the remaining other half first.<\/p>\n\n\n\n
In 2 workshop sessions, we collected activities and higher-level tasks of content designers. To get started, we skipped the levels of complexity along seniority, wrote and . Our skill framework describes the 12 skills on \u2018awareness\u2019, \u2018working\u2019, \u2018practitioner\u2019, and \u2018expert\u2019 level. We will get to the differentiation in a bit.<\/p>\n\n\n\n
Our first draft of skill headings include:<\/p>\n\n\n\n
- \n
- Identify and evaluate existing content with a focus on users<\/li>\n\n\n\n
- Plan and conduct content-focussed research activities<\/li>\n\n\n\n
- Synthesize findings and translate insights into opportunities<\/li>\n\n\n\n
- Deliver user-centred content that works for everyone<\/li>\n\n\n\n
- Develop content along users\u2019 journeys iteratively<\/li>\n\n\n\n
- Establish standards and processes for good content creation<\/li>\n<\/ul>\n\n\n\n
These points will change. Things might be missing. And we will rewrite and refine them.<\/p>\n\n\n\n
In the coming 2 weeks, we should finish a solid version that is good enough to share with all content designers at Digital Service for review. And I will also let my UK colleagues take a look.<\/p>\n\n\n\n
Then, I swiftly will have to continue with the communication design skill matrix. Eventually, I want us to publish all of our skill matrices for user-centred design roles either on GitHub, OpenCode or as part of the updated Service Standard manual. These materials should be valuable for other digital units across government, too.<\/p>\n\n\n\n
Plotting the path forward for the updated Service Standard<\/h2>\n\n\n\n
After a little break, the Service Standard sounding board got together again. They received an update on all the things that happened in recent weeks and what\u2019s left to make the updated standard mandatory. It was a highly appreciative hour.<\/p>\n\n\n\n
![\"A](\"https:\/\/verwaltungsgestaltung.de\/notizen\/wp-content\/uploads\/2025\/02\/Servicestandard-Soundingboard-1024x769.jpg\")
<\/figure>\n\n\n\nOtherwise, in the Service Standard team, we tried to figure out where Service Standard, its manual and other touchpoints should live and how they best interrelate with each other. We sketched timelines until summer and also looked at technical setups.<\/p>\n\n\n\n
To stretch out our necks and link things up, we also had an exchange with Isabell from\u00a0KERN Design System<\/a>\u00a0on how things they do overlap with what we do and plan to do. There are plenty of overlaps, and KERN today includes guidance that could similarly sit in guidance close to the Service Standard. We plan to have further collaboration sessions shortly.<\/p>\n\n\n\n
Wrapping up Demo Day<\/h2>\n\n\n\n
The comms team is finishing the final Demo Day activities. Some team members are just recovering from the intensity of the efforts around it. The German public sector tech press covered the event<\/a> quite extensively. <\/p>\n\n\n\n
The videographer we worked with did a brilliant job dynamically capturing the afternoon and evening. The different formats are well visible, and our ministerial partners get a well-deserved spotlight.<\/p>\n\n\n\n