-
Notifications
You must be signed in to change notification settings - Fork 118
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #7733 from MicrosoftDocs/Judy-Weiner-360-competencies
Create 360-competencies.md
- Loading branch information
Showing
4 changed files
with
109 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,109 @@ | ||
--- | ||
title: Viva Glint 360 competencies and reporting | ||
description: Competencies are verifiable characteristics and skills, which enable and improve the efficiency of performing work. Learn to develop your competency model. | ||
ms.author: JudithWeiner | ||
author: JudyWeiner | ||
manager: MelissaBarry | ||
audience: admin | ||
f1.keywords: NOCSH | ||
keywords: | ||
ms.collection: | ||
- m365initiative-viva | ||
- selfserve | ||
search.appverid: MET150 | ||
ms.topic: article | ||
ms.service: viva-glint | ||
ms.localizationpriority: high | ||
ms.date: 5/24/2024 | ||
ROBOTS: NOINDEX, NOFOLLOW | ||
--- | ||
|
||
# Viva Glint 360 competencies and reporting | ||
|
||
> [!NOTE] | ||
> This feature is available to preview customers only. Features described here are subject to change. | ||
This section covers program competencies, survey guidance, report access and timing, and global reporting guidance. | ||
|
||
:::image type="content" source="../../media/glint/setup/360-competencies-reporting-access.png" lightbox="../../media/glint/setup/360-competencies-reporting-access.png" alt-text="Screenshot how to access Competencies & Reporting in Cycle Settings."::: | ||
|
||
## Competencies | ||
|
||
Competencies are a set of verifiable characteristics and skills that enable and improve the efficiency of performing work. | ||
|
||
- A Glint 360 cycle can include a maximum of 150 competencies. | ||
- The typical number is in the range 3-10. | ||
- Except for the Competency Name and Description, competencies can't be added or deleted once a cycle is live. | ||
- Competencies map only to ratings questions. | ||
- The Glint Manager 360 template includes 13 competencies mapped to template rating questions. | ||
- To go live, a cycle must have at least one competency-question mapping. Each competency must map to at least one question. | ||
|
||
## Develop a competency model | ||
|
||
Develop a competency model which is relevant to the success criteria for your organization. Follow these recommended steps: | ||
|
||
- Collect information on what is considered success behaviors. | ||
- Draft critical behavioral statements. | ||
- Validate the competency model by comparing 360 results to desired business outcomes. | ||
|
||
Repeat this process for each major demographic. | ||
|
||
## Question mapping | ||
|
||
To maximize the reporting experience, map all ratings questions to at least one competency. Although a competency can map to more than one rating question, a rating question can map to only one competency. | ||
|
||
Procedure to map a competency to a question that is already mapped to another competency: | ||
|
||
1. Go to the other competency and remove its mapping to that question | ||
1. Return to the other competency to map the question. | ||
|
||
### Customizing a competency and mapping it to a question | ||
|
||
:::image type="content" source="../../media/glint/setup/360-competencies-reporting.png"alt-text="Screenshot how to access Competencies & Reporting in Cycle Settings."::: | ||
|
||
Repeat this procedure until you have mapped all competencies to at least one question: | ||
|
||
1. In Cycle Settings, select **Competencies & Reporting**. The *Competencies & Reporting* page opens. The Competencies section shows the number of questions mapped to each competency. | ||
2. Select the competency to be customized or mapped. | ||
3. Assign values to the Competency Name and Competency Description fields. This text is used in reports | ||
4. Select at least one question to map to the competency. To search for a question, begin entering the question label in the *Search Question* field. | ||
5. Select **Save Changes.** | ||
|
||
### Adding a competency | ||
|
||
To add a competency to a cycle: | ||
|
||
1. In Cycle Settings, select **Competencies & Reporting**. | ||
2. In Competencies, select **Competency**. The *Add Competency* window opens. | ||
3. Assign values to the Competency Name and Competency Description fields. | ||
4. Select at least one question to map to the competency. | ||
5. Select **Save Changes.** | ||
|
||
### Removing a competency | ||
|
||
To remove a competency from a cycle: | ||
|
||
1. In *Cycle Settings*, select **Competencies & Reporting**. | ||
2. Go to **Competencies**. | ||
3. Hover over the competency to be removed. | ||
4. Select the **trash can symbol** next to the competency. | ||
5. Select **Delete** in the confirmation dialog box. | ||
|
||
## Survey guidance | ||
|
||
Glint offers standard program and report guidance templates. | ||
|
||
1. Toggle Survey Guidance to **ON** to reveal the *Select a content resource* dropdown menu. | ||
1. **Key in 360 in the search bar** to access the standard templates. | ||
|
||
:::image type="content" source="../../media/glint/setup/360-survey-guidance.png"alt-text="Screenshot of the dropdown menu to select guidance in Cycle Settings."::: | ||
|
||
>[!TIP] | ||
> We recommend using **360 _Survey_Guidance** for the Survey Guidance. Review and edit the guidance from within *Content Resources*. | ||
|
||
|
||
|
||
|
||
|
||
|
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.