Dsm 323 and 324 community pages (#197)

* Update community pages

- new product page
- moved feedback guidance onto a separate page
- edited the UCD community page

* Added new page on feedbcak

* Corrected published dates

* Edits

src/your-community/ask-for-and-give-feedback.md

@@ -3,7 +3,9 @@ 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/"

src/your-community/product.md

@@ -1,74 +1,49 @@
 ---
 layout: "layouts/guidance.njk"
 section: "Community"
-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
+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
 eleventyNavigation:
-  key: "Content"
-  url: "/content/"
----
+  key: "Your community"
+  url: "/your-community/"
 
-Anyone creating content for digital services in Defence can join the content community. 
+Anyone working on digital services in Defence is welcome to join the product community.
 
 ## Who you will meet
 
 In this community, you will meet:
 
-- content designers
-- content strategists 
-- technical writers 
-- graphic designers
-- other people creating content across Defence
+- product managers
+- service owners
+- agile business analysts
+- people interested in product management
 
 ## Community calls
 
-Join the content community call every second Thursday at 2:30pm.
+Join the product community call every second Monday at 2pm.
 
-We discuss the latest content news and updates. We share insights, issues and what we’re working on. 
+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.
 
 {{ component('inset-text', {
-  html: 'You must only share OFFICIAL information. <a href="/security-classifications/">Find out about security classifications</a>.'
+  html: 'You must only share OFFICIAL information on community calls.<br><a href="/security-classifications/">Check how to classify information</a>.'
 }) }}
 
 ### Ask for an invitation
 
-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
+You need to work in the Ministry of Defence to join community calls. 
 
-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.
+Using your Ministry of Defence email, send a message to: [[email protected]](mailto:[email protected]?subject=Join%2productUCD%20community%20calls). 
 
-## How to give feedback
+Include your full name, your role and the project you are working on.
 
-You are expected to give feedback in a kind and respectful way.
+## Get feedback or lead a session
 
-### Give specific and actionable feedback
+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. 
 
-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".
+Anyone in the product community can volunteer to lead a call.    
 
-### Be kind and respectful
+Check [how to ask for and give feedback](/your-community/ask-for-and-give-feedback).
 
-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.