top of page

How I use Microsoft Lists

I’d like to share three examples of how I use Lists at work - that help harness sanity and present valuable, managed information out to others. Note, the screenshots you see below are real (not demo), representing the unique, personalized nature of Microsoft Lists.


Microsoft Lists app within Microsoft 365; this shows the lists I’ve favorited and the prominent

“New list” button to create new lists.


Above is what I see when I click into the Lists app in Microsoft 365 (aka, when I click on the Lists icon in the Microsoft 365 app launcher (the upper-left ‘waffle’ icon; syrup please). In this first example, I’ll highlight the “Intrazone 🎙 Tracker” list we use to plan and manage our podcast.


Managing episodes for The Intrazone podcast

The Intrazone is our bi-weekly show about the Microsoft 365 intelligent intranet - with guests from inside and outside Microsoft. The list we use to manage the show was created pre-Microsoft Lists, aka - it was an existing SharePoint list that has grown over the years and recently improved with new features. Note: we didn’t need to move it, or perform any app update.


The Intrazone Tracker list as a tab in our General channel within Teams


A few key list highlights

  1. Our podcast producer is an external user and was invited as a guest to The Intrazone team in Microsoft Teams. She has full access to the list.

  2. Dates are important, and fluctuate. We use date-driven formatting on the AIR date column which makes it easy to see what’s coming and what has already aired.

  3. We work in Teams, thus can click one item (a row; an individual episode) and start a new chat thread linked to the item. We used the Lists app in Teams to bring this existing list in as a tab in Teams.

  4. We have three main show types: Regular, Roadmap and Partner - so we use a Choice column to list each episode for ease of grouping.


The Intrazone logo/banner: aka.ms/TheIntrazone.


Tracking 1st and 3rd-party events

When it’s time to get the word out, or amplify best practices, we turn to events - first and third party - throughout the year. Due to COVID, most are presented virtually these days (“You’re on mute!”), and that does not remove the need to plan content, work with event leads, and communicate the level of support per event. My team and I maintain this list so we know what the calendar looks like, prioritizing the ones we speak at, sponsor, and support. It also helps to have the information in a central location as we work with a large amount of presenters and coordinate across teams.


Microsoft Lists using Calendar view accessed via our CCM SharePoint team site.



A few key list highlights

  1. We set Calendar view as the default view to help everyone visualize each event’s Start date.

  2. I created a custom view for everyone to see only upcoming events, in Grid view.

  3. We use a Person column to identify which internal team member is our event lead per event.

  4. I created this list using the Event itinerary, ready-made template, then lightly configured it per our specific needs.


Getting items on the Microsoft 365 roadmap

I work with three distinct groups that design and develop Microsoft Lists, the SharePoint admin center, and our content migration offerings. Each team sets a schedule of new features and updates. We use the list to manage release timing and coordinate between marketing and engineering - across the lifecycle of disclosure. Once real coding begins, we layer in who owns each feature, update release status, and establish a target release date - especially when it changes. I meet regularly with each team and refine the list by updating title, description, ownership, dates - all to align and prep before we “go public” and beyond.


Microsoft Lists in “Group by” view off the Area column; visualize roadmap items by feature area.


A few key list highlights

  1. We use the Area column (a Choice column) to denote each area: Admin, Lists, or Migration.

  2. The Targeted Release (TR) date dictates when items land on the public Microsoft 365 roadmap.

  3. I created a rule that notifies me when an engineer marks the Status of an item to “Needs roadmap ID”; aka, we’re ready to talk about it publicly; an exciting milestone.

  4. Once published, I add the link to the public blog in the Blog column so everyone can see and share it.


Final thoughts…

I tread water best with Lists helping buoy my information management. It helps me stay connected across projects, products and people. And when someone comes asking me about something, I can point them to a list or a list item, which then becomes a place for them to check back in or start a conversation from.


Source: Paper.li


The Tech Platform

0 comments

Commenti


bottom of page