Skip to main content

Manage OKRs Seamlessly in Microsoft Teams with Rhythms

A guide to installing the Rhythms app in Microsoft Teams for streamlined OKR management

Updated over a month ago

Introduction

Stay in the flow of work—use Rhythms directly in Teams to review OKRs, get updates, and submit check-ins without switching context, while receiving AI-generated summaries and action items right where your team already collaborates. This integration streamlines OKR management, fostering collaboration and alignment within your daily workflow.

In this guide, we will walk you through the process of installing the Rhythms application in Microsoft Teams. Rhythms application will be available in Microsoft Teams app directory shortly. In this guide, we will be using the Rhythms app provided to you by Rhythms team. You will be importing the Rhythms app zip file in the Microsoft Teams Admin Center.

Note that installing the application requires admin privileges in Microsoft Teams to manage applications and admin privileges in Rhythms to configure organization-wide settings.

Step 1: Identify Deployment Scope for the Rhythms App

Depending on your Rhythms deployment status, you will either guide specific users to discover and use the app in Teams for testing, or follow a plan to roll out to everyone in the Rhythms workspace. Both deployment scopes will involve ensuring everyone you want to have access to Rhythms through Teams is a user in your workspace.

Choose the deployment scope that fits your needs to ensure a smooth rollout.

Step 2: Install Rhythms App for Workspace Members

As an administrator in Rhythms, you can enable Rhythms for all team members by logging into the Rhythms portal, accessing the 'Admin' option, and clicking on 'Collaborations.' This gives you the ability to install the Microsoft Teams app from the Rhythms portal for all members who are part of the Rhythms workspace by clicking on 'Install' next to Microsoft Teams.

You should be redirected to a page to set up and proceed with installation of Rhythms in Microsoft Teams.

Step 3: Verify the Installation

Once you have installed Rhythms in Teams, check the Teams app directory or a user’s Teams client when confirming the Rhythms app is installed and available. The app should appear under "Apps" for users to add to their Teams workspace—test by searching for Rhythms in Teams to ensure successful integration.

Step 4: Configure Permissions Based on Deployment Scope

Based on your current deployment scope, configure permissions to access Rhythms in Microsoft Teams.

For Testing with a Limited Group:

For testing with a limited group, share instructions with specific users when you want to control access during a trial phase. Guide them to discover the Rhythms app in the Teams App directory by searching for it under "Apps" and clicking "Open" to access it—send these instructions via email or chat to ensure a smooth user setup.

After guiding your group of test users to open the Rhythms app through Teams, ask them to right click on the Rhythms icon in the sidebar while the app is open, and click the 'Pin' button. This will place the Rhythms app on the sidebar for easy discoverability throughout the testing phase.

For Organization-Wide Deployment:

If deploying Rhythms to all users in your OKR program, follow these steps to make the roll-out user-friendly. To maximize adoption and allow everyone in your OKR program to easily access Rhythms through Teams, go into "Permissions", and choose the "Auto-Pin" feature to automatically place the Rhythms app on the sidebar for easy discoverability. Auto-pinning at launch is a best practice to maximize adoption, keep OKRs highly visible, and help embed the discipline of OKRs into your company’s culture and daily work rhythms.

Step 5: Conclude Set-up

There it is! The Rhythms app is now available for your team to access. If you're deploying Rhythms to everyone in your organization's full OKR program, you're all set. If you're deploying it to a select group of users for testing, refer to Step 4 when you're ready for organization-wide deployment.

Did this answer your question?