Have your say Level: Foundation
Get involved
This portal is built in the open, and anyone can help: use it and tell us what works, test it, suggest and vote for ideas, improve the content, review it as an expert, or champion it in your own team. Every way of taking part is recognised with a badge.
In brief
- 9 ways to take part, from 2 minutes to an ongoing role.
- A toolkit of emails, posts and a walk-through to bring your team in.
- 6 badges for your profile and signature.
Easy read summary
- There are many ways to help.
- Pick the one that suits you.
- You can get a badge to show you helped.
Ways to take part
2 minutes
Use it and tell us
Use the portal for real work, then use 'Was this page useful?' at the foot of any page, or the private feedback form.
About 20 minutes
Test it
Try the tasks for your role on Help us test and say how each went.
5 to 90 minutes
Take part in research
Sign up for a survey, interview, usability or accessibility session.
5 minutes
Suggest and vote for ideas
Post an idea in Discussions, vote for others, and add evidence in comments.
As long as you like
Improve the content
Report a problem, suggest a change to a page, add a source, or propose a sector supplement. Changes go through a reviewed pull request.
About an hour a month
Review as an expert
Join the review panel to check drafts, such as sector supplements, before they are published.
1 to 2 hours a month
Champion it in your team
Introduce the portal to your team, run a short walk-through, and pass on what your team needs.
As agreed
Be an ambassador across organisations
Present the portal at a community, network or working group, and bring back what you hear.
Varies
Join a community or network
Join the government data communities and networks listed on Boards, councils and networks.
Rules of engagement
- Follow the code of conduct. Be kind, assume good faith and stay on topic.
- Nothing above OFFICIAL, no personal data, and no email addresses anywhere.
- Name roles, not people. Credit is given by GitHub username, only if you choose.
- Every fact needs a source and a provenance label (see How sources are labelled).
- Anyone can suggest a change. The owner reviews every change before it is published, and nobody is added as a collaborator except by the owner's invitation.
- Decisions are made in the open, through the roadmap and the decisions log on Have your say.
Improve the content
- Small fix or question: use "Report a problem with this page" at the foot of any page, or the contact form.
- Change a page: select "Suggest a change" at the foot of a page. GitHub makes your own copy, you edit the content file, and you open a pull request. The owner reviews it.
- New topic or sector supplement: post it as an idea first, so others can add evidence.
- Check a capability flag: on the capability model, select "Check this flag" on any capability.
Read the contributing guide and code of conduct first.
Champions and ambassadors
Champions bring the portal into their own teams; ambassadors carry it across organisations. About 1 to 2 hours a month for a champion. Stop at any time.
What a champion does
- Share the portal with your team using the toolkit below
- Run a 15 minute walk-through at a team meeting
- Collect your team's feedback and ideas and post them
- Encourage colleagues to take part in research
- Tell us when your organisation's practice differs from the portal, so we can fix it
What you get
- Early sight of what is coming on the roadmap
- A Champion badge for your GitHub profile and email signature
- Your organisation's needs reflected in the roadmap
- Recognition by GitHub username on the portal if you choose
What an ambassador does
- Everything a champion does
- Present the portal at a community, network or working group
- Bring back what other organisations need
- Help shape the roadmap at a review panel
Become a champion Tell us privately instead
Toolkit: bring others in
Ready-made text for email, Microsoft Teams, Slack, Viva Engage, your intranet and a team meeting. Copy it, change what you like, and send it from your own account. Nothing here contains anyone's contact details.
Email to your team
Subject: Practical help with the Data Asset Management Policy Hello team, The DAM capability playbooks are a prototype website that turns the Data Asset Management Policy into practical steps for data governance, cataloguing and quality, by role. Have a look: [this portal's address]/ Start with "Your role": [this portal's address]/personas.html It is a prototype, not official GOV.UK guidance, and the team wants feedback. You can test it, take part in research, or suggest and vote for ideas: [this portal's address]/research.html [Your name]
Microsoft Teams post
**Practical steps for the DAM Policy** The DAM capability playbooks turn the Data Asset Management Policy into steps by role, for governance, cataloguing and quality. Prototype, open for feedback. Try it: [this portal's address]/ Have your say: [this portal's address]/research.html
Slack post
:bulb: *DAM Policy, made practical.* The DAM capability playbooks show the steps for your role in data governance, cataloguing and quality. It's a prototype and wants feedback. Try it: [this portal's address]/ Suggest and vote for ideas: [this portal's address]/research.html#ideas
Viva Engage or intranet community post
Are you a data owner, steward or catalogue manager? The DAM capability playbooks set out what the Data Asset Management Policy asks of your role and how to do it. It is a prototype built in the open. Try a task, then tell the team what works: [this portal's address]/test.html
Intranet news item
Headline: Help shape practical guidance for the Data Asset Management Policy
The DAM capability playbooks are a prototype website that helps organisations meet the Data Asset Management Policy. It sets out the steps for each role in data governance, data cataloguing and data quality, with templates, a capability model and links to GOV.UK guidance.
The team is looking for people to test it, take part in research, and suggest ideas. Find out more: [this portal's address]/research.html
It is not official GOV.UK guidance. Where it repeats GOV.UK, the GOV.UK page is the authority.
15 minute walk-through at a team meeting
1. (2 minutes) What the DAM Policy asks of us: [this portal's address]/dam.html 2. (5 minutes) Pick one role in the room and open its route: [this portal's address]/personas.html 3. (5 minutes) Try one task together from Help us test: [this portal's address]/test.html 4. (3 minutes) Agree one idea or problem to post: [this portal's address]/research.html#ideas
Email signature line
DAM capability playbooks champion · Help shape practical guidance for the DAM Policy: [this portal's address]/research.html
Badges
Every way of taking part earns a badge you can show on your GitHub profile, on social media or in your email signature. Badges recognise help with a prototype. They are not an official government credential or qualification.
| Badge | How to earn it | How to get it |
|---|---|---|
Explorer | Used the portal for real work and gave feedback. | Self-declared: display it once you have done it. |
Tester | Completed at least three testing tasks, or took part in a research session. | Self-declared: display it once you have done it. |
Contributor | An idea, report or change of yours was accepted onto the backlog or published. | Claim it, with a link to the idea, issue or pull request. |
Reviewer | Reviewed a draft as part of the review panel or an expert review. | Claim it, with confirmed by the service owner. |
Champion | Introduced the portal to your team and ran a walk-through or passed on your team's feedback. | Claim it, with a short note of what you did, with no names. |
Ambassador | Presented the portal at a community, network or working group, or championed it across organisations. | Claim it, with the community or event, with no names of attendees. |
Claims are public GitHub issues that show your GitHub username only. Do not include your name or anything above OFFICIAL. No GitHub account? Use the private feedback form and say which badge.
Add a badge to your profile or signature
Explorer: code for your profile and signature
GitHub profile (Markdown):
[]([this portal's address]/involve.html#badges)
Email signature or web page (HTML):
<a href="[this portal's address]/involve.html#badges"><img src="[this portal's address]/badges/explorer.png" alt="DAM capability playbooks Explorer" height="20"></a>
Plain text signature:
DAM capability playbooks Explorer · [this portal's address]/involve.html
Downloads: SVG · PNG for social media and email
Tester: code for your profile and signature
GitHub profile (Markdown):
[]([this portal's address]/involve.html#badges)
Email signature or web page (HTML):
<a href="[this portal's address]/involve.html#badges"><img src="[this portal's address]/badges/tester.png" alt="DAM capability playbooks Tester" height="20"></a>
Plain text signature:
DAM capability playbooks Tester · [this portal's address]/involve.html
Downloads: SVG · PNG for social media and email
Contributor: code for your profile and signature
GitHub profile (Markdown):
[]([this portal's address]/involve.html#badges)
Email signature or web page (HTML):
<a href="[this portal's address]/involve.html#badges"><img src="[this portal's address]/badges/contributor.png" alt="DAM capability playbooks Contributor" height="20"></a>
Plain text signature:
DAM capability playbooks Contributor · [this portal's address]/involve.html
Downloads: SVG · PNG for social media and email
Reviewer: code for your profile and signature
GitHub profile (Markdown):
[]([this portal's address]/involve.html#badges)
Email signature or web page (HTML):
<a href="[this portal's address]/involve.html#badges"><img src="[this portal's address]/badges/reviewer.png" alt="DAM capability playbooks Reviewer" height="20"></a>
Plain text signature:
DAM capability playbooks Reviewer · [this portal's address]/involve.html
Downloads: SVG · PNG for social media and email
Champion: code for your profile and signature
GitHub profile (Markdown):
[]([this portal's address]/involve.html#badges)
Email signature or web page (HTML):
<a href="[this portal's address]/involve.html#badges"><img src="[this portal's address]/badges/champion.png" alt="DAM capability playbooks Champion" height="20"></a>
Plain text signature:
DAM capability playbooks Champion · [this portal's address]/involve.html
Downloads: SVG · PNG for social media and email
Ambassador: code for your profile and signature
GitHub profile (Markdown):
[]([this portal's address]/involve.html#badges)
Email signature or web page (HTML):
<a href="[this portal's address]/involve.html#badges"><img src="[this portal's address]/badges/ambassador.png" alt="DAM capability playbooks Ambassador" height="20"></a>
Plain text signature:
DAM capability playbooks Ambassador · [this portal's address]/involve.html
Downloads: SVG · PNG for social media and email
Recognition
People who claim Contributor, Reviewer, Champion or Ambassador badges can be listed here by GitHub username, if they choose. None yet: be the first.
See also Have your say for research, the roadmap and ideas, and Boards, councils and networks for government communities to join.
Was this page useful? Tell us Tell us privately, without GitHub