|
Last week, we talked about how using a pull system helped us get more work done. This week, we’re making that idea tangible by showing you how to build a simple Kanban board in Microsoft Planner, a tool you likely already have if you subscribe to Microsoft 365. 1. Open Microsoft Planner
2. Create a New Plan
3. Create Kanban Columns (Buckets)Buckets represent Kanban columns.
4. Add Tasks to Each Column
Next week, we will dive into the scorecard we use to assess work before it gets put in the Doing column. PS: Leaders shouldn’t have to know every tool Microsoft provides as part of their subscriptions. The Outlier Team is here to help you learn what you could be using in your subscription, and eliminating other expensive technologies that duplicate what you’re already paying for. For a free assessment, simply reply to this email. |
We help small businesses with technology, strategy, and leadership and have a passion for sharing what we have learned. Subscribe to our newsletter to get helpful weekly content.
The Cost of Silence Several years ago, I went through one of the most difficult experiences of my professional career. A few weeks before Christmas, our CEO informed my boss that an outside IT consulting firm would be coming in to help evaluate our technology operations. At the time, I was the IT manager. The announcement raised a lot of questions. Why were they being brought in? What were they evaluating? What would happen afterward? Unfortunately, very few answers were provided. Weeks went...
Over the last two weeks, we’ve discussed meetings that run the business and improve the business. Today, let’s examine the third category: meetings that build the team. Before we do, I’d like to share a story. One summer morning at 2:00 AM, our team received an email that would turn into one of the largest technology incidents the world had ever experienced. Nearly every server and computer at our organization and others throughout the world would not power on. As people woke up, they began...
Meetings That Improve the Business Several years ago, our team was dealing with a frustrating login issue. About one person each week would be affected, and the disruption typically lasted only a few minutes. The team responsible for resolving the issue was actively working with the vendor. We held problem-solving sessions, investigated possible causes, and provided daily updates through email and Teams messages. The work was being done. People were understandably frustrated and wanted the...