A day in the life of a product manager using Microsoft Loop

7:45 AM

While commuting on the bus to work, Awa receives a Loop
component in Teams chat
that outlines a new feature review, which Awa contributes to from her phone.

8:30 AM

At her desk, Awa opens her Loop workspace, which includes a Loop page for each feature review. She duplicates a Loop page to copy the previous template, then updates with the new feature details.

Awa copies and pastes the Loop component from her commute onto the page to keep all the information in one place.

9:00 AM

She @ mentions her Product Manager team for their input on the review. Asynchronously, they contribute ideas on how to improve the feature with pros and cons via a voting table on the Loop page.

11:30 AM

The top improvements have been voted on and are ready to implement! Awa copies the voting table component and pastes it in a Teams channel for the engineering stakeholders to advance the sprint.

12:30 PM

Ahead of an upcoming product feature ideation meeting, Awa jots down new feature options on her Ideas page in Loop.

Awa adds her ideas page to the Product Roadmap Loop workspace and starts the discussion on different feature ideas with her team.

To structure the brainstorming discussion, Awa adds columns in the table such as feature description, investment needed, and impact to metrics.

3:00 PM

After the team has provided their input async, Awa adds a priority column in the table and prioritizes top features for the next semester.

4:00 PM

After the team is aligned, Awa converts the table into Loop component and adds it to an Outlook email to the relevant stakeholders to keep them updated.

Stakeholders review the component directly from their inbox and insert emojis and comments to highlight their thoughts and keep the work moving forward.