Update people and communities competency

[mrsbeata]

Category

• Content fix
• New article

Related issues

• None

Contents of the Pull Request

This PR updates the People and Communities Competency article with significant structural and content improvements to enhance clarity, consistency, and practical guidance.

Key improvements:

• Added User Experience sections to all levels (100-500) for consistency across the article
• Standardized Impacts sections with "At this level you can expect the following:" format and detailed bullet points
• Reorganized Process sections into clear subcategories:
  • Profile Management
  • Communities & Groups
  • Expertise Discovery
  • Communication Channels
  • Mentorship & Development
• Enhanced content with mentor-like tone, practical examples, and dry but kind humor
• Improved Scenarios, Cost & Benefit, and Conclusion sections with real-world examples and practical ROI considerations

Specific additions:

• Communications department responsibilities for Viva Engage, channel strategy, mass emails, living communities, leadership corner, and coaching managers
• HR ownership of dynamic groups based on profile attributes for targeted messaging and access control
• IAM systems explanation with HR as master for personnel data and automated synchronization to Microsoft 365
• Reduced AI content by changing "AI & Expertise Discovery" to "Expertise Discovery" and removing detailed Copilot information
• Updated examples including Excel spreadsheets as useful during IT incidents
• Removed "Delve" from the Common Microsoft 365 Toolsets list

Level-specific enhancements:

• Level 100: Added Excel spreadsheets example and improved User Experience section
• Level 300: Added "This is where things start to click" introduction
• Level 400: Added detailed Communications and HR ownership sections with sparkles (✨) for critical points
• Level 500: Added "This is where you want to be" introduction

Guidance

This update improves the article's consistency with other competency articles in the Maturity Model, provides clearer practical guidance for organizations at different maturity levels, and clarifies ownership and responsibilities for profile management, channel strategy, and dynamic groups. The changes emphasize the strategic roles of HR and Communications departments in enabling effective people and communities capabilities.

[learn-build-service-prod]

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

[learn-build-service-prod]

Learn Build status updates of commit 801d4d8:

💡 Validation status: suggestions

File	Status	Preview URL	Details
Community/microsoft365-maturity-model--people-and-communities-competency.md	💡Suggestion	View	Details

Community/microsoft365-maturity-model--people-and-communities-competency.md

• Line 8, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'mrsbeata' is not a valid Microsoft alias.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

[github-actions]

@VesaJuvonen
You've been added as a reviewer to this pull request because you're listed as a Content Lead for the product area or feature covered by one or more articles in this PR.

Before this PR can be merged, a Content Lead needs to add the Sign off label to it. Only one of the listed reviewers needs to add the Sign off label. Before you sign off a PR, confirm the following:

• Article content has been checked for technical accuracy.
• There are no errors or warnings in build validation.
• There are no severity 1 or 2 PoliCheck issues.
• All articles have a minimum Acrolinx score of 80.
• All required PR checks at the bottom of the PR are passing.

After you've confirmed the above, do the following to sign off:

1. Select the gear next to Labels.
2. Select Sign off from the label list.
3. Click away from the label list.

After you've signed off, our operations (PubOps) team will review the PR for issues that may impact formatting and the customer experience. If any changes are needed, they will return
the PR to the submitter with required changes. After they've completed those changes, you need to sign off again.

When the PR passes PubOps review, they'll merge the PR. If the PR is merged into the main branch, changes will go live within the next couple hours.

If you think you were incorrectly added as a reviewer, have questions about this process, or need help signing off on this PR, post a message to https://aka.ms/tcphelp.

[learn-build-service-prod]

Learn Build status updates of commit 726cdda:

💡 Validation status: suggestions

File	Status	Preview URL	Details
Community/microsoft365-maturity-model--people-and-communities-competency.md	💡Suggestion	View	Details

Community/microsoft365-maturity-model--people-and-communities-competency.md

• Line 8, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'mrsbeata' is not a valid Microsoft alias.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

[learn-build-service-prod]

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

[sympmarc]

@mrsbeata - You'll need to bring this PR up to date with the base branch. You should see a button to do that.

[learn-build-service-prod]

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

[learn-build-service-prod]

Learn Build status updates of commit a15b615:

💡 Validation status: suggestions

File	Status	Preview URL	Details
Community/microsoft365-maturity-model--people-and-communities-competency.md	💡Suggestion	View	Details

Community/microsoft365-maturity-model--people-and-communities-competency.md

• Line 8, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'mrsbeata' is not a valid Microsoft alias.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

[JithuGiit]

@mrsbeata. The build shows an invalid "ms.author" name. Please create another PR to fix this issue.

[sympmarc]

@JithuGiit - If you can do it for us, please set it to ms.author: pamgreen