Loading...
  • Customer Experience
    Customer Experience
  • Employee Experience
    Employee Experience
  • Brand Experience
    Brand Experience
  • Product Experience
    Product Experience
  • Core XM
    Core XM
  • Design XM
    Design XM

Action Planning Basic Overview (EX)

What's on This Page:


Was this helpful?


This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

The feedback you submit here is used only to help improve this page.

That’s great! Thank you for your feedback!

Thank you for your feedback!


Qtip: This page describes functionality available to Engagement and Lifecycle projects. For more details on each, see Types of Employee Experience Projects.

About Action Planning

Action Plans are initiatives you can create based off your lowest areas of engagement. They allow you to assign tasks and plan resolutions to some of your company’s biggest issues with employee experience. For example, if employees disagreed that they were adequately trained, a larger-scale action plan could be to implement a new training program.

However, there are several steps to action planning, when you take into account who is involved and what reports to build. In general, you will need to complete the following steps:

  • Make sure the right people have permission to create action plans.
  • Customize the fields on your action plans and other such settings (optional).
  • Use guided action planning to create action plans.
  • Create an action planning page to perform aggregate reporting on action plans.
Qtip: Would you like to try the new action planning experience? As the name implies, guided action planning lets you provide guidance for your users every step of the experience. Make sure you set up your users and role correctly using the Permissions section of this page, then head on over to Guided Action Planning for further instructions.

Permissions

Before your team can create their own action plans, you need to make sure the right participants are able to edit action plans by changing their permissions. Permissions can be directly applied to a participant, or to an entire role. Roles are very useful when you need a large group of people to have the same permissions.

Attention: Only Brand Administrators have access to action planning by default. All other users must be assigned a dashboard role and given action planning permissions, even if they are the dashboard owner.

Global Permissions

Permission in a participant info window

Under the Permissions header are the following options.

  • Edit All Action Plans: Gives the participant administration/editing rights to any action plan in the dashboard.
  • Use Action Plans: Allows the participant to use action plans in the dashboard. This permission allows the participant to edit any Action Plans they’ve created or are the owner for. The participant will also be able to view, but not edit, any Action Plans accessible to them by their org hierarchy data restrictions.

To restrict what action plans people can edit and use, add a dashboard and modify the dashboard data restrictions by clicking View All Data and selecting Restrict Data. See example below.

On a persons permissions, under dashboard permissions, second option is the described dropdown

Dashboard Permissions

Separate from giving a participant the ability to create or use action plans, you can restrict which aggregate reports on action plans they are allowed to see. Reports compiled on action plans vary from dashboard to dashboard.

After you have added a dashboard to a role or participant, look under Action Plan Reporting. Click the View All Data dropdown to instead select Restrict Data.

Dashboard action plan restrictions

You can then choose to restrict data by org hierarchy or org hierarchy units.

Org Hierarchy Restriction

Attention: Lifecycle has action planning, but no hierarchies or hierarchy-based data restrictions. That means that when reporting on action plans in a Lifecycle project, this data is not restricted by place in the hierarchy, and so every user with access to action planning will see this data. As such, be careful who you give access to action planning.

Aforementioned restriction

The Current Unit is the specific unit the dashboard user belongs to.

Let’s say the user belongs to the Web Design team of the Digital Marketing Department – the current unit would be Web Design. If you don’t want your teams to know the action plan data for the unit above them, use current unit.

The Parent Unit is the unit above the dashboard user. To use the same example, this would be all of Digital Marketing.

Parent unit is useful if you have smaller teams within departments with unique action plans, but want all the data readily visible. Parent unit is also a useful option if you want a larger unit of people to work towards a common goal – for example, you’re not worried about action plans for just Web Design or the Email Marketing teams, but the whole of Digital Marketing.

Org hierarchy restrictions are perfect for widely defined roles that are not department or hierarchy specific.

Org Hierarchy Units Restriction

Attention: Lifecycle has action planning, but no hierarchies or hierarchy-based data restrictions. That means that when reporting on action plans in a Lifecycle project, this data is not restricted by place in the hierarchy, and so every user with access to action planning will see this data. As such, be careful who you give access to action planning.

Aforementioned restriction

When limiting action plan access by org hierarchy units, you can choose a specific unit of the hierarchy. Then you can decide if you want the dashboard user to view plans in a selected unit, or in and below it.

Org hierarchy unit restrictions are best when applying permissions to specific participants or when making roles that pertain to specific parts of your org hierarchy (e.g., not a hierarchy-wide “Manager” role, but maybe a “Digital Marketing Manager” role).

Action Plan Dashboard Settings

While none of the steps in this section are required, they give you the opportunity to customize your action plans as needed to best fit your company’s employee experience program.

You can add additional fields that will appear on your action plans. For example, is there a quality control question all your employees must answer before closing an issue? Would you like to note departments responsible? See the Available Fields page for more on how to customize these in the dashboard settings.

In addition, you can limit the survey items that action plans can be linked to. Learn more about this on the Available Items page.

Qtip: Would you like to add guidance or resources on the survey items you’ve decided to include? Try adding some tips!

Action Plans Approvals

You have the option to allow action plans approvals. If this feature is enabled, then every new action plan will be marked as “Not approved” by default. Anyone who does not own the action plan, but has visibility to see the action plan, may then change it from “Not approved” to “Approved”. To turn on action plans approvals, enable the Action plans must be approved option in your action plans settings.

the allow action plans to be approved toggle in action plan settings

Once enabled, action plans will have a toggle for other users to approve the action plan. Usually, this is the manager of the person who created the action plan, but it can be anyone who has access to the action plan.

the approved / not approved field on an action plan

Qtip: Please note that this toggle is for internal approval only, and does not limit the action plan in any way.

Guided Action Planning

Guided action planning allows dashboard users to create action plans based on survey results. This feature is vital to creating and editing action plans to report on. Guided action planning allows you to close the loop with employee feedback, giving every leader and manager the power to drive impact in areas employees care about most. To create your action plans, see Guided Action Planning.
Action plans top-right and left-bottom

Reporting on Action Plans

Once you have used guided action planning to make action plans, you can start reporting on action plans. For example, you can create a chart that breaks out according to the roles of people assigned action plans, or a table that shows the statuses of all action plans.

A dashboard reporting on actions plans

Attention: Lifecycle has action planning, but no hierarchies or hierarchy-based data restrictions. That means that when reporting on action plans in a Lifecycle project, this data is not restricted by place in the hierarchy, and so every user with access to action planning will see this data. As such, be careful who you give access to action planning.

Creating an Action Planning Page

Before you can start reporting on your action plans, you will need to make an action planning page on your dashboard.

Qtip: Action planning pages do not copy over page filters created on other pages.
  1. Click Add Page.
    Adding an action planning page on the left side of the dashboard
  2. Select Action Planning Page.
  3. Click Page Options.
    Renaming a page in the upper-right

    Qtip: Steps 3-6 aren’t required, but explain how to rename your page so you can easily find which one is for action planning.
  4. Click Rename.
  5. Type a name in the field.
    Typing a name in the small window that appears
  6. Click Save.

Widgets Available

You’ll notice that when you click Add Widget on your action planning page, there are fewer widgets than you’d find on a regular page. This is to optimize the page for action plan reporting.

Qtip: The purpose of the action planning is described on the guided action planning page.
Qtip: Rich text editor and image widgets are not for reporting, but to help you customize your page with instructions, logos, and any other details you feel will clarify your data or make it aesthetically pleasing.

Action Planning Fields

When you start to customize widgets on your action planning page, you will notice that action plan-specific fields will appear in the list instead of the contents of your dashboard data.

Since Action Planning fields are not included in your dashboard data, they are automatically assigned field types for optimum reporting. Below, each field is listed by its type. For more on what field types mean and the widgets they are compatible with, see the Field Types support page.

Open Text:

Text Set / Multi-Answer Text Set:

  • Owner IDs: Owner IDs are internal Qualtrics IDs assigned to the owners of action plans.
  • Status: The status of the action plan. These are assigned using guided action planning. Statuses include not started, on hold, in progress, closed, and canceled.
  • Survey Item Names: The exact text of the survey item this action plan was created for.
  • Survey Items: An ID for the survey item this action plan was created for.

Number Set:

  • Approved: This field always has a value of 0 or 1.
  • Progress: This is the exact percentage that the action plan is completed.

Date:

  • Creation Date: The date the action plan was created.
  • Due Date: This is the due date given the action plan in guided action planning.
  • Last Modified: The date someone last edited the action plan. This includes status and percentage changes, but not the addition of comments.

Misc. Field Types:

  • Owner Metadata: You will be able to select from a list of metadata for the people the action plans have been assigned to. For example, let’s say the metadata you uploaded with your participants is Department, Start Date, and Office Location. You would see the options Owner: Department, Owner: Start Date, and Owner: Office Location.
  • Creator Metadata: You will be able to select from a list of metadata for the creator of the action plan. For example, let’s say the metadata you uploaded with your participants is Department, Start Date, and Office Location. You would see the options Creator: Department, Creator: Start Date, and Creator: Office Location.
    • Field type of the metadata depends on how the original is mapped in the dashboard data.
      Example: If Department is mapped as a Multi-Answer Text Set, then Owner: Department and Creator: Department will also be Multi-Answer Text Sets.
  • Action Plan Fields: The fields you set in your action plan settings will also be available for reporting. For example, let’s say you create a field called “Responsible Departments” referring to departments who will need to be involved to resolve this action plan. You’d be able to report on this data by selecting “Responsible Departments” from the list of fields.
    • Text fields are Open Text
    • Dropdowns are Text Set, unless set to Multi-Answer Text Sets
    • Checkboxes are Text Set, unless set to Multi-Answer Text Set
    • Dates are Date