Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revert "Dsm 323 and 324 community pages (#197)" #199

Merged
merged 1 commit into from
Jun 7, 2024
Merged

Revert "Dsm 323 and 324 community pages (#197)" #199

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions src/your-community/ask-for-and-give-feedback.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,9 +3,7 @@ layout: "layouts/guidance.njk"
section: "Community"
title: "How to ask for and give feedback"
description: "Get tips on asking for feedback in community sessions and check how Defence expects you to give feedback."
dateUpdated: 2024-06-06
dateUpdated: 2024-05-05
main
eleventyNavigation:
key: "Content"
url: "/content/"
Expand Down
65 changes: 45 additions & 20 deletions src/your-community/product.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,49 +1,74 @@
---
layout: "layouts/guidance.njk"
section: "Community"
title: "Product"
description: "Anyone in a product management role in Defence can join the community. Find out how to get involved."
datePublished: 2024-06-06
title: "Content"
description: "Anyone creating content for digital services in Defence can join the content community. Find out how to get involved."
dateUpdated: 2024-03-05
eleventyNavigation:
key: "Your community"
url: "/your-community/"
key: "Content"
url: "/content/"
---

Anyone working on digital services in Defence is welcome to join the product community.
Anyone creating content for digital services in Defence can join the content community.

## Who you will meet

In this community, you will meet:

- product managers
- service owners
- agile business analysts
- people interested in product management
- content designers
- content strategists
- technical writers
- graphic designers
- other people creating content across Defence

## Community calls

Join the product community call every second Monday at 2pm.
Join the content community call every second Thursday at 2:30pm.

Calls are no longer than 1 hour. We discuss product management techniques and approaches. We share what we’re working on and often have guest speakers.
We discuss the latest content news and updates. We share insights, issues and what we’re working on.

{{ component('inset-text', {
html: 'You must only share OFFICIAL information on community calls.<br><a href="/security-classifications/">Check how to classify information</a>.'
html: 'You must only share OFFICIAL information. <a href="/security-classifications/">Find out about security classifications</a>.'
}) }}

### Ask for an invitation

You need to work in the Ministry of Defence to join community calls.
You need to work in Defence to join the community calls.

Using your Ministry of Defence email, send a message to: [[email protected]](mailto:[email protected]?subject=Join%20content%20community%20calls).

Include your full name, your role and the project you’re working on.

## Ask for feedback

Community calls are a great place to ask for feedback on your service, a feature or an issue. Here are a few things to remember.

### Set the context

Without taking too long, tell the story of your service. Start with what your service does, who your users are and what they are trying to do.

### Say what kind of feedback you want

Tell people what you want to find out. For example, if there are existing patterns you can reuse or how close you are to meeting the GOV.UK Service Standard.

### Do not be defensive

Using your Ministry of Defence email, send a message to: [[email protected]](mailto:[email protected]?subject=Join%2productUCD%20community%20calls).
Feedback is about your service, not you. Avoid deflecting questions, it is okay to say that you are not sure. Take notes so that you do not need to respond to every point.

Include your full name, your role and the project you are working on.
## How to give feedback

## Get feedback or lead a session
You are expected to give feedback in a kind and respectful way.

On product community calls, you can share your successes, tools and approaches. You can ask the community for ideas on dealing with product management challenges.
### Give specific and actionable feedback

Anyone in the product community can volunteer to lead a call.
All feedback should be constructive. Include details of what you are thinking, what you would change and why. Avoid phrases like "I don't like it" or "That never works".

Check [how to ask for and give feedback](/your-community/ask-for-and-give-feedback).
### Be kind and respectful

You can be honest and specific without using hurtful or aggressive language. Start sentences with phrases like “Have you considered”, “You might like to try” or “Think about”.

### Keep an open mind
Everyone has different experiences and opinions. Remember that your feedback is just one perspective. Be willing to consider feedback that differs from your own.

### Be present
The team presenting their service deserves your full attention. Try not to be distracted by other work. In remote sessions, have your camera on and show that you are actively listening.
Loading