MS Planner: Personal, Shared & Premium

Key insights

• Plan
  In Microsoft Planner a plan is a container for tasks, buckets, labels and views that help you organize work.
  It supports individual tasks and team projects in one place.
• Personal vs Shared
  Personal plans suit one person and are created by leaving the Microsoft 365 group field blank.
  Shared plans connect to a Microsoft 365 group so members can collaborate, assign tasks, and view progress together.
• Basic vs Premium
  Basic plans offer core features like Board, Grid, Schedule, Charts, assignments, checklists and recurring tasks.
  Premium adds advanced management, reporting, automation and AI features and requires the appropriate license.
• Create a Personal Basic plan
  Leave the group selection empty, name the plan, then add tasks, due dates, checklists and labels.
  Use My Tasks and Microsoft To Do to keep personal work visible across apps.
• Create and share a Basic plan
  Attach the plan to a Microsoft 365 group, add members, then assign tasks and set due dates.
  Use Board, Grid or Schedule views to track progress and coordinate work.
• Choose the simplest plan
  Start with Basic when work needs are straightforward; upgrade to Premium only when you need advanced reporting, automation or AI assistance.
  Pick the option that covers the work without extra complexity.

Overview of the video

Vlog #2 | Creating Plans in Microsoft Planner by Nenad Trajkovski – Copilot & Planner walks viewers through the decision points involved when creating plans in Microsoft Planner. The short tutorial clarifies two commonly confused choices: whether a plan is Personal or Shared, and whether it should use Basic or Premium capabilities. Consequently, the video focuses on practical steps and concrete examples so users can choose the simplest plan that supports their work. It also touches on when upgrading makes sense and how to assign tasks and add members for collaboration.

The presenter demonstrates plan creation in a live interface, showing how a personal plan can be created without a Microsoft 365 group and how a shared plan connects to a group for teamwork. He highlights core Planner features such as views, tasks, assignments, and integration points like Microsoft To Do and Teams. In addition, the video explains what extra features a Premium plan adds compared with a Basic plan. As a result, viewers leave with an understanding of both the steps and the rationale behind each configuration choice.

Creating plans: step-by-step guidance

The video first walks through creating a Personal Basic plan by leaving the Microsoft 365 group field empty, which keeps the plan tied to one person’s tasks and workflows. Then, the presenter shows how to create a Shared Basic plan by connecting it to a group, adding members, and assigning tasks so the team can track progress together. These demonstrations help viewers understand the user interface choices that determine access and collaboration options.

He also demonstrates common actions after plan creation, such as adding buckets, setting due dates, using labels and checklists, and switching between Board, Grid, Schedule, and Charts views to monitor work. The presenter assigns tasks to team members and explains how those tasks appear in personal task areas, which keeps individual responsibility visible while supporting team oversight. Overall, the step-by-step approach reduces friction for new users and clarifies where simple clicks produce meaningful differences in plan behavior.

Personal vs Shared: deciding who collaborates

Choosing between a Personal and a Shared plan is primarily about who needs access and how the work should be coordinated. A personal plan works well when one person manages deliverables, recurring duties, or experimental tasks that do not yet require team input, whereas a shared plan supports departmental work and cross-functional projects by allowing task assignments and shared views. Thus, the decision affects visibility, accountability, and where tasks surface in users’ personal task lists.

That choice also carries tradeoffs: personal plans are simpler and reduce governance concerns, but they limit collaboration and can fragment tracking when teams grow. Conversely, shared plans increase coordination but require more planning around membership, privacy settings, and naming to avoid duplicated or orphaned plans. Therefore, organizations should balance ease of use with the need for team visibility and set basic naming or ownership rules to minimize confusion.

Basic vs Premium: balancing features and cost

Basic plans deliver the core capabilities most teams need, including multiple views, task assignments, due dates, checklists, labels, exporting, and recurring tasks, which usually suffice for everyday workflows. In contrast, Premium plans provide advanced features—such as richer reporting, finer controls, or additional integrations—that support complex projects and enterprise reporting needs. As a result, deciding whether to upgrade involves weighing feature value against licensing cost and administrative overhead.

The presenter emphasizes choosing the simplest capability level that supports the work, because starting simple reduces training needs and lowers the risk of unused paid features. However, he also notes scenarios where premium functions pay off, for example when teams need robust analytics, governance controls, or additional project-management tools that basic plans don’t provide. Thus, the tradeoff comes down to complexity and cost versus the need for advanced oversight and scaling capabilities.

Practical tradeoffs and governance challenges

One ongoing challenge is avoiding plan sprawl as teams create many small plans that overlap or duplicate work, which can fragment information and complicate reporting. To address this, organizations should set light governance rules around plan ownership, naming conventions, and when to link a plan to a Microsoft 365 group so that shared work remains discoverable and manageable. Moreover, regular cleanup and an agreed process for migrating personal plans to shared plans can reduce duplication over time.

Another common tension arises between privacy and visibility: private plans protect sensitive work but limit discoverability and cross-team learning, while public shared plans promote transparency at the cost of tighter controls. Training staff on the differences and maintaining clear policies about when to use each option will reduce mistakes. Finally, coordination with IT and licensing teams helps ensure that users who need Premium capabilities can access them without introducing unnecessary expenses.

Recommendations and final takeaways

The video’s clear takeaway is practical: start with the simplest plan that meets your needs and only upgrade or convert a plan when your work demands more collaboration or advanced features. By contrast, rushing to complex configurations can create administrative friction and increase costs without delivering immediate value. Therefore, teams should prioritize clarity, assign ownership, and keep plans aligned with actual work patterns.

In summary, Nenad Trajkovski – Copilot & Planner offers a concise and useful primer on creating plans in Microsoft Planner, focusing on the real-world tradeoffs between personal versus shared and Basic versus Premium choices. His step-by-step demonstrations and emphasis on choosing the simplest effective option leave viewers with actionable guidance on organizing tasks, adding members, and deciding when to scale up features. Ultimately, this practical approach helps users and teams adopt Planner in a way that balances simplicity, collaboration, and cost.

Keywords

Microsoft Planner tutorial, Creating plans in Microsoft Planner, Personal vs shared Planner plans, Microsoft Planner basic features, Microsoft Planner premium features, How to create a plan in Planner, Planner tips and best practices, Microsoft Planner vlog