PMConnection

PMBOK 8th Edition and the new PMP Exam

BIG changes are underway at PMI!! Here is the TLDR version:

2. The 'PMI Code of Ethics and Professional Conduct' has been updated

3. The PMP Exam will change in July of 2026

1. PMBOK 8th Edition 2025

Watch short video HERE

A Guide to the Project Management Body of Knowledge (PMBOK® Guide)―Eighth Edition and The Standard for Project Management represents the most data-driven and community-informed update in the guide’s history.

🔍 𝗔 𝗴𝗹𝗼𝗯𝗮𝗹, 𝗲𝘃𝗶𝗱𝗲𝗻𝗰𝗲-𝗯𝗮𝘀𝗲𝗱 𝗲𝗳𝗳𝗼𝗿𝘁

The PMBOK 8th edition was built through four research phases involving thousands of practitioners worldwide:
- Qualitative sessions across seven countries.
- 3,400 responses to a survey about PMBOK 7.
- 9,000 public comments on the draft Guide during the first open consultation
- And 3,900 additional comments on the Standard second open consultation.

It is the most community-driven PMBOK ever produced.

1️⃣ 𝗣𝗠𝗕𝗢𝗞 𝟴 𝗯𝘂𝗶𝗹𝗱𝘀 𝗼𝗻 𝗣𝗠𝗕𝗢𝗞 𝟳 - absolutely not a "rollback".

PMBOK 8 keeps the principles and performance domains foundation of 7 but simplifies and clarifies them to make them more actionable and avoid the somewhat confusing overlap of some of them. There is also a higher focus on value, sustainability, AI, and quality integration. It recognizes Project Success as when Value exceeds Effort and Expense.

2️⃣ 𝗣𝗿𝗼𝗰𝗲𝘀𝘀𝗲𝘀 𝗮𝗿𝗲 𝗿𝗶𝗴𝗵𝘁-𝘀𝗶𝘇𝗲𝗱, 𝗮𝗻𝗱 𝗶𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗲𝗱

The five well-known process groups and 49 processes, were never gone but they had been debundled from PMBOK 7 and published separately. In 8, they are streamlined and embedded as flexible, non-prescriptive anchors that work across the continuum between predictive and Agile, and support the Performance Domains, making the articulation clearer.
Inputs, Outputs, and Tools & Techniques now appear as non prescriptive items in alphabetical order, covering various approaches and referenced across the Guide.

🌍 𝗣𝗠𝗕𝗢𝗞 𝟴 𝗰𝗼𝗻𝗻𝗲𝗰𝘁𝘀 𝘄𝗵𝘆 (𝗽𝗿𝗶𝗻𝗰𝗶𝗽𝗹𝗲𝘀), 𝘄𝗵𝗮𝘁 (𝗱𝗼𝗺𝗮𝗶𝗻𝘀), 𝗮𝗻𝗱 𝘄𝗵𝗲𝗻 (𝗳𝗼𝗰𝘂𝘀 𝗮𝗿𝗲𝗮𝘀) 𝗶𝗻𝘁𝗼 𝗼𝗻𝗲 𝗰𝗼𝗵𝗲𝗿𝗲𝗻𝘁 𝘀𝘆𝘀𝘁𝗲𝗺 𝗳𝗼𝗿 𝘃𝗮𝗹𝘂𝗲 𝗱𝗲𝗹𝗶𝘃𝗲𝗿𝘆.

In summary PMBOK 8th Edition, focuses on value, sustainability, AI, and quality integration. It is built on previous versions, but it's not a rollback. Instead, it clarifies and simplifies concepts to make them more actionable, with an emphasis on project success defined as value exceeding effort and expense.

Get PMBOK 8th Edition HERE

2. PMI Code of Ethics and Professional Conduct

This update was effective on November 17, 2025.

The Project Management Institute (PMI) Code of Ethics and Professional Conduct is a foundational document that guides the behavior and decision-making of project management professionals worldwide. As the profession evolves in response to technological, social, and regulatory changes, so too must its ethical standards. On 17 November 2025, PMI released a significant update to its Code of Ethics and Professional Conduct, marking the most comprehensive revision in over a decade.

Overview of the PMI Code of Ethics and Professional Conduct

The PMI Code of Ethics and Professional Conduct is designed to instill confidence in the project management profession by articulating the ethical expectations for PMI members, certification holders, applicants, and volunteers. The Code is structured around four core values—Responsibility, Respect, Fairness, and Honesty—which serve as the foundation for both aspirational and mandatory standards of conduct. These standards are intended to guide practitioners in making ethical decisions, particularly in complex or ambiguous situations where legal requirements may be insufficient.

The 2025 update reflects PMI’s commitment to ensuring that its ethical framework remains relevant and effective in addressing contemporary challenges. The revision process involved extensive consultation with global stakeholders, benchmarking against emerging trends, and a deliberate effort to provide clearer, more actionable guidance for real-world application.

Here’s a summary of the recent PMI Code of Ethics and Professional Conduct updates:

🔑 Core Values (Unchanged but Reframed)

Responsibility, Respect, Fairness, Honesty remain the foundation.
Language has been modernized to emphasize inclusivity, global applicability, and clarity in expectations.

📌 Key Updates

Expanded Guidance on Responsibility
- Stronger emphasis on sustainability, social impact, and accountability for project outcomes.
- Explicit call to consider long‑term effects on communities and the environment.
Respect Modernized
- Clearer expectations around diversity, equity, and inclusion (DEI).
- Guidance on avoiding bias and fostering psychological safety in teams.
Fairness Strengthened
- More detail on conflicts of interest, transparency in decision‑making, and equitable treatment of stakeholders.
- Explicit prohibition of favoritism and misuse of authority.
Honesty Clarified
- Reinforced obligation to provide accurate information and avoid misleading statements.
- New emphasis on truthfulness in digital communication and AI‑assisted work.

📖 Structural Changes

Simplified format: shorter, more direct statements for easier application.
Practical examples added to illustrate ethical dilemmas in modern project contexts (remote work, digital tools, AI).
Updated terminology to align with PMI’s global standards and evolving workplace norms.

💡 Expert Commentary

Why the changes?
- To reflect shifts in project environments: globalization, digital transformation, and DEI priorities.
- To ensure project managers are equipped to handle ethical challenges in hybrid and tech‑driven settings.
Implications:
- Greater accountability for social and environmental impact.
- Clearer guardrails for fairness and transparency in complex stakeholder landscapes.
- Reinforced trust in project management as a profession.

👉 In short: PMI kept the four values intact but sharpened them for today’s realities—adding sustainability, DEI, digital integrity, and practical examples to make the Code more actionable.

Access 'PMI Code of Ethics and Professional Conduct' HERE

3. PMI Announces Major Update to PMP® Exam, Launching July 2026

Watch video summary HERE

The Project Management Institute (PMI) has revealed that a new Project Management Professional (PMP)® exam is scheduled to launch globally in July 2026. This update is designed to keep pace with changing times and reflects the future of the profession. The new PMP exam will be a reimagined version built around real-world impact and value, with a sharper focus on the skills and mindsets that drive meaningful results in today’s world. PMI maintains its continued promise to uphold the PMP as the global gold standard for the project profession.

Key Changes Coming to the PMP Exam

The updated exam, which aligns with the new PMP Certification Exam Content Outline (2026), features significant adjustments to content, domain weighting, and the overall exam experience.

Content and Focus Areas

The revised content will add topics such as AI, sustainability, and stakeholder engagement. Furthermore, the exam will shift its focus more heavily toward outcomes and value.

Rebalanced Domains

To better balance leadership, technical, and strategic skills, the exam weighting across the three domains will be restructured:

Domain Current Weighting New Weighting (2026)

People	42%	33%
Process	50%	41%
Business Environment	8%	26%

Approach and Experience

The new PMP exam will cover predictive and agile methods, as well as hybrid applications, placing a greater emphasis on adaptive, real-world project dynamics.

In terms of testing logistics, the exam will consist of 185 questions and the duration will be 240 minutes. The format will be more interactive and scenario-based, reflecting real project environments.

Eligibility Updates

The eligibility requirements are being aligned globally across degrees, apprenticeships, and training programs. While the experience requirement remains 3–5 years, the eligibility period is being extended to 10 years.

Timeline and Preparation Options

Candidates currently preparing for the certification have clear paths to follow, depending on when they plan to take the test.

Date Event Details

15 December 2025	Pilot registration opens	Early access sign-up for interested candidates.
5–30 January 2026	Pilot exam window	Participants can take the new exam early and share feedback.
April 2026	Updated learning resources available	Includes on-demand prep, practice exams, PMI Study Hall®, and new instructor-led courses.
July 2026	New PMP exam available globally	Full rollout of the updated exam worldwide.

If you are currently preparing for the PMP, the core principles and approaches remain the same, and you can continue studying. You have the option to take the current exam any time until July 2026 (the exact cutoff date is yet to be confirmed). Candidates who wish to take the current version must pay for and take the test by July 2026.

If you wish to take the new exam, the updated PMP resources will be available starting in April 2026.

Participate in the PMP Pilot Program

PMI will run a limited pilot program in January 2026 for candidates interested in shaping the future of the exam. Pilot exams will run from 5–30 January 2026, with registration opening on 15 December 2025.

The pilot program details include:

It will be available in English only.
It must be administered in person at Pearson VUE test centers.
Participants will receive a 20% rebate for taking part.
Those who do not pass the pilot exam will receive a free exam retake when the new version officially launches in July 2026.

What is the difference between Agentic AI and Custom Chatbots

What is the difference between Agentic AI and Custom Chatbots

Listen to Deep Dive Podcast HERE

Digital assistants sit along a spectrum from scripted question–answer tools to autonomous systems that set goals and act across services. This article explains the practical and technical differences between agentic AI and custom chatbots, how each is built and used, the risks and governance considerations, and a short decision guide to choose between them.

Quick comparison table of attributes:

Attribute Agentic AI	Autonomy High	Planning & multi-step actions Yes	Integration depth Deep; orchestrates across systems	Typical development effort High	Best fit use cases Complex workflows, automation, decision support
Custom Chatbots	Low–Medium	Limited; scripted flows or LLM prompts	Shallow to moderate; API calls or embedded widgets	Low–Medium	Customer support, FAQs, guided tasks

Definitions and core distinction

Agentic AI describes systems that can take autonomous initiative: they interpret objectives, plan sequences of actions, interact with multiple tools or APIs, monitor outcomes, and adapt behavior over time. Agentic AI treats tasks as goals to be achieved rather than single-turn requests.

Custom chatbots are conversational interfaces built for a defined scope. They respond to user inputs using scripted flows, rules, retrieval-augmented generation, or single-turn LLM prompts. Custom chatbots are typically designed to answer FAQs, guide users through forms, or perform bounded tasks with human oversight.

Technical differences Architecture and components

Agentic AI: planner/manager, action modules (connectors to apps and APIs), stateful memory or context store, feedback loop for monitoring and learning.
Custom chatbots: intent/slot managers, dialogue flows, knowledge retrieval index or FAQ store, optional LLM layer for natural language generation.

Decision-making and control

Agentic AI uses explicit planning or reinforcement-style approaches to sequence steps and make trade-offs; it can interrupt, retry, and escalate when needed.
Custom chatbots follow deterministic flows or stateless prompt-response cycles; complexity grows quickly when attempting multi-step automation.

Data and integration

Agentic systems require deeper, secure integrations (enterprise APIs, credentials, workflow engines) and persistent state to coordinate tasks across systems.
Chatbots often rely on injected documents, knowledge bases, or light APIs and can be embedded into web or messaging channels with lower permissions and complexity.

Capabilities and example use cases

Agentic AI
- Orchestrating multi-step processes (e.g., assess loan eligibility, order background checks, schedule follow-ups).
- Autonomous monitoring and remediation (detect issue → execute fix → verify outcome).
- Cross-system negotiation or coordination (book resources across calendars, adjust dependent systems).
- Use-case examples: automated operations agents, internal process orchestrators, complex customer service escalations requiring several backend changes.
Custom Chatbots
- Conversational FAQs and support triage.
- Guided data collection (surveys, order capture).
- Simple transactions (check status, reset password via guarded API calls).
- Use-case examples: website support widget, helpdesk triage, lead qualification flow.

Risks, governance, and operational considerations

Safety and trust
- Agentic AI can take actions with real-world impact, so stronger safeguards, explainability, auditing, and human-in-the-loop controls are required.
- Chatbots present lower action risk but can still surface incorrect or misleading information; monitoring and retraining matter.
Security and access control
- Agentic systems need fine-grained credentialing, least-privilege connectors, and strong secrets management because they act across systems.
- Chatbots usually operate with limited API scopes and can be deployed faster with fewer privileges.
Compliance and auditability
- Agentic AI needs detailed logging of decisions, actions, and reversibility paths for compliance and incident response.
- Chatbot interactions should also be logged, but the audit surface is smaller and easier to review.
Operational cost
- Agentic solutions typically require more engineering, continuous monitoring, and maintenance.
- Chatbots can be cost-effective for narrowly defined tasks and scale quickly across channels.

When to choose which (decision guide)

Choose Agentic AI when:
- You need autonomous, multi-step workflows that cross systems.
- The business value of automation outweighs the engineering, governance, and security investment.
- You require adaptive behavior, retries, or optimization across longer horizons.
Choose a Custom Chatbot when:
- You want a fast-to-market conversational interface for support, triage, or scripted guidance.
- Tasks are bounded, predictable, and do not require deep orchestration or decision planning.
- You prefer lower implementation cost and simpler security posture.
Hybrid approach
- Many organizations adopt a hybrid: a custom chatbot handles initial interaction and escalation; an agentic backplane handles complex orchestration when authorized. This lets teams balance speed, safety, and capability.

Implementation checklist

For Agentic AI:
- Define clear objectives and allowed action scope.
- Design planning and monitoring layers.
- Establish connector and credential governance.
- Implement comprehensive logging, explainability, and rollback mechanisms.
- Pilot with human oversight before broad rollout.
For Custom Chatbots:
- Map intents and conversation flows.
- Provide authoritative knowledge sources and fallback to humans.
- Instrument analytics for misunderstood queries and performance.
- Enforce rate limits and access controls for any APIs used.

Conclusion

Agentic AI and custom chatbots answer related needs on different parts of the automation spectrum. Agentic AI brings autonomy, planning, and deep cross-system orchestration at higher engineering and governance cost. Custom chatbots deliver conversational access to services quickly and cheaply but are limited in multi-step autonomy. Choosing between them — or combining both — depends on the required autonomy, integration depth, risk tolerance, and expected business value.

How to Automatically Mark Tasks as Complete in Smartsheet with a Checkbox

How to Automatically Mark Tasks as Complete in Smartsheet When a Checkbox Is Checked

One of the most common automation requests in Smartsheet is: “How can I make my task automatically show as Complete when I check the box?”

This workflow not only saves time but also helps maintain data consistency across your project sheets. In this article, we’ll walk step-by-step through how to configure your sheet so that checking a box updates the task’s Status column automatically.

Objective

When you check the “Done” (or “Complete”) checkbox in your Smartsheet:

The Status column automatically changes to “Complete.”
Optionally, you can also show a completion date or use conditional formatting to gray out the row.

Step 1: Set Up Your Columns

You’ll need at least these columns:

Column Name Column Type Purpose

Task Name	Text/Number	Describes the work item
Done	Checkbox	Used to mark task completion
Status	Dropdown (e.g., Not Started, In Progress, Complete)	Displays current task state
Completed Date (optional)	Date	Shows when the task was completed

Pro Tip: Keep your dropdown values in the Status column consistent across all sheets (e.g., “Not Started,” “In Progress,” “Complete”). This makes reporting and dashboards cleaner.

Step 2: Create an Automation Rule

This is where the magic happens.

Go to the Automation menu → Create a Workflow
Choose “When rows are changed” as your trigger
Set the condition: When [Done] changes to checked
Add an action:Change cell value → Column: Status → New Value: Complete
(Optional) Add another action: Record a date → Column: Completed Date → “Date when action is executed”
Name your automation something clear like: “Mark Task Complete When Checkbox Is Checked”

Your workflow should look like this:

When “Done” changes to checked
Then change “Status” to “Complete”
And record “Completed Date”

Step 3: Add Conditional Formatting (Optional)

If you want completed tasks to look complete:

Go to Format → Conditional Formatting
Create a new rule:
- If Status is Complete
- Apply formatting (e.g., gray text, strikethrough, or background color)
Save the rule

This visual cue helps your team quickly scan for what’s finished.

Step 4: Test the Automation

Now check the Done box on one of your tasks.
If configured correctly:

The Status column should automatically update to “Complete.”
If added, the Completed Date should populate with today’s date.
The row will format differently (if you applied conditional formatting).

Advanced Tip: Reverse the Rule

You can add a second automation that resets the status if someone unchecks the box:

When [Done] changes to unchecked
Then change [Status] to “In Progress”

This ensures your sheet stays accurate if someone accidentally marks a task as complete.

Why This Matters

Automating task completion in Smartsheet:

Saves time and reduces manual updates
Keeps team dashboards and reports always current
Standardizes project tracking across all sheets
Enhances visibility for project managers and stakeholders

Final Result

After setup, your Smartsheet workflow behaves like a lightweight project tracker:

Check the box → Task marked complete → Status and date updated automatically.

No manual edits. No missed updates. Just clean, consistent data.

Automating Task Movement in Microsoft Planner Using Power Automate

How to Automatically Move a Task in Microsoft Planner from "Bucket 1" to "Bucket 2" After 45 Days Using Power Automate

Microsoft Planner and Power Automate are integral components within the Microsoft 365 ecosystem, enabling both structured project management and powerful workflow automation. One frequent use case among project teams is the automatic progression of tasks between buckets (work stages) after a specific period—such as moving a task from "Bucket 1" to "Bucket 2" after it has resided for 45 days. Without automation, this time-based movement is manual, error-prone, and often neglected, especially in large-scale, long-running projects or recurring operational workflows.

This how-to article provides a comprehensive, step-by-step guide to achieve this automatic movement using Power Automate. It assumes you have basic familiarity with both Microsoft Planner and Power Automate. The tutorial covers essential configurations, required expressions, the critical actions involved, and highlights key limitations and considerations to ensure the automation is resilient, accurate, and maintainable.

Where applicable, the article references relevant official documentation, expert analyses, and active community forums to reinforce actionable steps and strategic recommendations. Screenshots and visual references are suggested for clarity but, where unavailable, instructions are described in precise detail for implementation. By the end of this article, you will have the necessary knowledge to confidently automate bucket movement in Planner, understand its operational boundaries, and adjust parameters to suit comparable use cases.

Section Overview

To fully address this how-to scenario, the following areas will be explored in depth:

Scheduling and Recurrence Triggers in Power Automate
Task Age Calculation With Expressions
Listing and Filtering Tasks in Planner
Retrieving Bucket IDs Programmatically
Updating Task Bucket Assignment
Time Zone and Daylight Saving Time Handling
Limitations of Power Automate and Planner Integration
Error Handling, Concurrency, and Permissions
Advanced Options with the Microsoft Graph API
Summary Table of Workflow Steps

Understanding the Automation Goal

The Task: Automatically move any task in "Bucket 1" to "Bucket 2" after it has spent 45 days in "Bucket 1".

This scenario is most useful for standardizing the lifecycle of tasks (e.g., progressing stagnating or overdue tasks) and freeing teams from routine administrative burden. Implementing this in Power Automate requires:

Scheduling the Flow: Ensuring the flow runs regularly (e.g., daily or weekly) to check for eligible tasks.
Identifying Relevant Tasks: Listing all tasks currently in "Bucket 1" and calculating whether their age exceeds 45 days.
Updating Task Bucket: Moving tasks to "Bucket 2" without losing essential details—such as checklists, notes, or attachments, and preserving business context.
Addressing Edge Cases: Handling permission requirements, API limits, and potential failures for flawless operation.

Key Steps and Their Purpose Step Number Workflow Action Purpose

1	Set up Flow with Recurrence	Ensure regular (e.g., daily) execution of the flow
2	Get Planner Plan and Buckets	Locate and identify "Bucket 1" and "Bucket 2" by their IDs
3	List All Tasks in the Plan	Retrieve all tasks for later filtering
4	Filter Tasks by Bucket and Age	Isolate tasks in "Bucket 1" older than 45 days
5	Move Tasks (Update Bucket)	Use Power Automate to move selected tasks to "Bucket 2"
6	Optional: Log/Notify Results	Maintain audit logs or notify users of automated moves
7	Error Handling/Monitoring	Ensure resilience against failures, API issues, or permission errors

The subsequent paragraphs will provide in-depth explanations, Power Automate specifics, relevant expressions, and critical considerations for each step.

Step 1: Setting Up a Scheduled Flow (Recurrence Trigger)

The core premise for scheduling in Power Automate is the Recurrence trigger. This built-in trigger allows the flow to execute at intervals of your choosing—typically once per day for task transitions.

When creating your flow, select Scheduled Cloud Flow in Power Automate. Here you can specify:

Frequency: Daily is generally appropriate for most task hygiene workflows.
Interval: Set to 1 (i.e., every day).
Start Time and Time Zone: For precision, specify the exact time, and always check the time zone setting to align with your operational hours.

Advanced Options:
You can further configure the recurrence trigger to run at a precise minute past the hour (e.g., 08:05 AM rather than "some time in the 8 AM hour") by using the “At these minutes” field in Advanced settings. This prevents unpredictable start times due to Power Automate's load balancing behavior, and can be important for business process timing.

Visual Reference:
Power Automate web interface:

Go to Create > Scheduled cloud flow
Enter a flow name, select a start date/time, and recurrence (e.g., Frequency: Day, Interval: 1).

Recommendations:

Avoid too frequent schedules (e.g., every few minutes) unless business-justified, as this can consume API quotas and may be throttled in lower-tier licenses.
Document the rationale for your chosen schedule frequency within the flow description.

Step 2: Getting Planner Plan and Bucket IDs

Every Planner plan and bucket is identified uniquely by a GUID, not just their user-friendly names. Within Power Automate, Planner connector actions require Group ID (usually Microsoft's Teams group or Office 365 Group), Plan ID, and Bucket ID.

How to Retrieve Bucket IDs:

Use the List Buckets action in the Planner connector.
Provide the Group ID and Plan ID.
Power Automate returns a JSON array with all buckets—each containing name, id, and other attributes.
Use a Filter Array or Condition action to get the ID for "Bucket 1" and "Bucket 2" by matching the bucket's name property.

Example:
In an "Apply to each" loop over the buckets:

Condition: item()?['name'] == 'Bucket 1' Capture: item()?['id'] (Store as Bucket1Id variable) Repeat for 'Bucket 2'

Why This Matters:
Hardcoding bucket IDs is brittle; buckets can be renamed or deleted over time. By dynamically locating bucket IDs each run, your automation is robust to changes.

Reference:
[Power Automate: Planner - List Buckets Action - Manuel T. Gomes (2021)]
[Planer : Move completed tasks between buckets with original checklist (2024/2025)]

Step 3: Listing All Tasks in the Plan

The List Tasks action retrieves all tasks within a given plan. In current versions, this returns all tasks across all buckets for the specified plan; tasks can then be filtered to only those in "Bucket 1".

Action: List Tasks
Parameters: Group ID, Plan ID
Output: Array of tasks with properties such as id, title, bucketId, createdDateTime, dueDateTime, etc.

Important Note:
You cannot use Planner’s List Tasks action to directly filter by bucket; you must manually filter after the initial retrieval.

Optimizing Performance:
While the List Tasks action returns up to 100 records at once, large plans may require reconfiguration (parallelization, pagination) to avoid missing tasks or performance lags.

Step 4: Filtering Tasks by Bucket and Age (Calculating Task "Stale" Status)

4.1. Bucket Filtering

Within your flow (inside an "Apply to each" loop or via a Filter Array action):

Compare each task's bucketId to the value you've retrieved for "Bucket 1".
Pass only tasks in "Bucket 1" to subsequent steps.

4.2. Age Filtering (Tasks Older Than 45 Days)

Power Automate provides flexible datetime expressions for filtering:

The task's age is calculated from the createdDateTime property.
To check if a task is older than 45 days, compare its createdDateTime to "today minus 45 days".

Expression Example:
In the Filter Array or Condition action:

@lessOrEquals(items('Apply_to_each')?['createdDateTime'], addDays(utcNow(), -45))

utcNow() returns the current UTC date/time.
addDays(utcNow(), -45) returns the date 45 days ago.
lessOrEquals(date1, date2) evaluates true if date1 is earlier than or equal to date2.

Key Tips:

Ensure the comparison values are in the same format (ISO 8601 date strings; Planner returns dates as “2024-05-19T08:15:00Z”).
Always check for null values; tasks may lack createdDateTime in rare import/migration scenarios.
If you want age based on a custom field (e.g., "Date moved into Bucket 1"), you need to set and maintain this elsewhere, as Planner does not natively track "time since in this bucket".

Reference(s):

Step 5: Updating the Planner Task (Moving to Bucket 2)

With a filtered list of eligible tasks, the movement to "Bucket 2" is done via the Update a task (V2) action in Power Automate:

Action: Update a task (V2) (Planner connector)
Task Id: Dynamic content from the filtered task
Bucket Id: ID value corresponding to "Bucket 2"

Key Points:

The Update Task action changes the bucket in-place. The task retains its notes, checklist, attachments, progress, etc.—since you are not deleting-and-recreating the task.
If you want to update any additional fields (priority, dates, assignments), you may do so in this step.
Optionally use the Update task details action in combination if you need to edit checklists or descriptions specifically.

Example Power Automate block inside Apply to each loop:

Condition: If task is in Bucket 1 and older than 45 days
Action: Update a task (V2) (set new Bucket Id to Bucket 2)

Reference: [Power Automate: Planner - Update a task Action - Manuel T. Gomes (2021)]

Step 6: Optional — Logging, Notification, or Audit

For best practices and future troubleshooting, it is highly recommended to include a logging or notification action at the end of each successful move. Options include:

Send an email to an admin or team (e.g., "Task X has been moved to Bucket 2 by automation").
Write to a SharePoint list, Dataverse table, or a file to create an audit trail for compliance or review.
Post a message to Teams channel using the Teams connector for visibility.

Notifying key stakeholders about automated movements provides users with transparency and helps build trust in automated workflows.

Step 7: Error Handling, Monitoring, and Flow Resilience 7.1. Flow Duration and Retention

Power Automate cloud flows have a [maximum run duration of 30 days]. Since this flow is scheduled daily and performs finite actions, it is highly unlikely to approach this limit. However, if you implement waiting or delay actions, be mindful that waiting actions exceeding 30 days will timeout and the flow run will fail.

7.2. Error Handling

Add Scope containers within your flow to group actions and set explicit error-handling logic. For example, when an action fails (e.g., updating a task due to permission denial), handle it by logging the error and sending a notification.

Use Configure Run After settings to define actions on failure or timeout pathways.
Combine with alerting through email or Teams, so issues surface promptly.

7.3. Permissions

You must have edit rights, typically member or owner permissions, to move tasks within a Planner plan.
If using a service account ("system" user), ensure the account remains licensed, active, and has not exceeded flow ownership limits.

7.4. Concurrency Control

By default, Power Automate can process actions in parallel. However, when updating tasks—especially if modifying the same task from multiple flows—consider enabling Concurrency Control and setting the "Degree of Parallelism" to 1 to avoid race conditions and data inconsistency.

Reference:
[Optimize Power Automate triggers – Power Automate | Microsoft Learn]

Special Considerations and Limitations Planner and Power Automate API Limitations

No Server-Side $filter Support: The Planner REST API and Power Automate’s Planner connector do not support OData ($filter) queries for fields like createdDateTime or percentComplete. All filtering must occur after retrieving all tasks for a plan.
Batch Update Limits: Each flow action and API call counts toward your organization's service limits. Monitor and optimize for both action count per run and API quotas.
Data Retention: Planner’s List Tasks and Power Automate’s run retention default to 30 days, so logging outside the platform may be needed for long-term auditing.
Attachment and Checklist Consistency: While the Update Task action preserves existing details, modifications to checklists or references (attachments, links) must be performed through the Update Task Details action, if needed.
Plan, Bucket, and Task Scope: Moving a task between buckets of the same plan is natively supported. Moving to a different plan or group has more limitations and may drop certain metadata, such as labels or assignments, depending on membership overlap.
New Premium Plans: As of the latest update, moving/copying tasks to/from “Premium” plans in Planner may not be supported by all API endpoints or automation tools.

Flow Design and Execution

Do Not Use Delay Actions for 45-Day Waits: Power Automate's Delay actions are designed for short-term waiting (minutes, hours, rarely days), and flows longer than 30-day states risk timeout and resource waste. Instead, rely on scheduled recurrence to check age daily.
Date Calculation Basis: This approach calculates age since "createdDateTime". If a task is moved back to "Bucket 1", the 45-day timer resets. If you need age-in-bucket logic, you must custom-track entry timestamps (e.g., update a custom field when entering the bucket). This is not built-in.
Time Zone Handling: All datetime values in Planner are UTC by default. Use Power Automate’s Convert Time Zone action or the convertTimeZone() expression to display times in business-appropriate local timezones and properly interpret "midnight rollovers" around DST transitions.

Advanced: Using Microsoft Graph API for Planner

For advanced users, the Microsoft Graph API offers further customization, error details, and metadata access over what the Planner connector exposes.

Graph permits direct calls for task, plan, and bucket operations: e.g., GET, PATCH, POST on /planner/tasks, /planner/plans, /planner/buckets.
Permissions for Graph API use are strict and require both sufficient application registration and user/group membership.
As of 2025, OData filters such as $filter=createdDateTime le 2024-01-01 on /planner/tasks are not supported; client-side filtering is still mandatory.
API behavior may vary depending on plan type (Basic vs. Premium), licensing, and organizational AAD security settings.

Retaining Task Details During Moves

When moving tasks between buckets in the same plan via Power Automate:

All core task details (Title, Description, Due Dates, Checklist, Attachments, Category labels—if within plan) are retained.
If you move the task between plans, some items (like labels, attachments, assignments) may be dropped if the destination plan/group does not have the same users or categories, or users lack permissions.

If your workflow depends on checklists, attachments, or custom fields, always test on a sample data set to confirm what is preserved and what (if anything) is lost across movements or plan changes.

Example Power Automate Flow: Visual Schematic

Trigger: Recurrence: every day at 8:00 am UTC
Action: Get Group, Plan, and Bucket IDs
- [List Groups → Filter group by displayName]
- [List Plans for group → Filter plan by title]
- [List Buckets → Filter buckets for "Bucket 1" and "Bucket 2", store IDs]
Action: List Tasks in the Plan
- [List Tasks in plan]
Filter Array:
- Input: value from List Tasks
- Condition: task.bucketId == Bucket1Id and task.createdDateTime <= addDays(utcNow(), -45)
Apply to Each:
- Input: Filtered array
  - [Action] Update a task (V2):
    - Task Id: current item id
    - Bucket Id: Bucket2Id
(Optional): Log moved tasks (e.g., compose array, append to SharePoint, send email).

Common Troubleshooting and Edge Cases

Tasks Without CreatedDateTime: Edge cases where imported or legacy tasks lack this field will need to be filtered out or skipped explicitly in the flow logic.
Permission Errors: Always confirm that the flow’s connector account is a member (not just owner) of the group, as certain actions require membership-level permissions, not just admin roles.
API Throttling: If you process many tasks at once, respect service limits (API calls per user per minute/hour/day). Monitor flow failures and adjust concurrency as needed.
Flow Turned Off Due to Errors: Flows that error repeatedly for 14+ days may be auto-disabled; ensure error paths do not result in silent looping failures.

Table: Key Power Automate Actions and Expressions for This Workflow Action/Expression Purpose Example/Key Syntax

Recurrence Trigger	Run flow on set schedule (daily, etc.)	Frequency: Day, Interval: 1
List Groups	Retrieve all Microsoft 365 groups	Filter on Name to find Group ID
List Plans for Group	Get Planner plans for Group	Filter on Title to find Plan ID
List Buckets in Plan	Enumerate buckets, find IDs for "Bucket 1" and "Bucket 2"	Filter: item()?['name'] == 'Bucket 1'
List Tasks in Plan	Retrieve all tasks in plan for filtering	Output: array of all tasks
Filter Array	Select only relevant tasks	@and(equals(item()?['bucketId'], Bucket1Id), lessOrEquals(item()?['createdDateTime'], addDays(utcNow(), -45)))
Update a Task (V2)	Move task by setting new Bucket Id	Task Id: current task, Bucket Id: Bucket2Id
addDays(), utcNow()	Date calculation for aging tasks	addDays(utcNow(), -45)
Convert Time Zone	If needed, localize times for business context	convertTimeZone(utcNow(),'UTC','Eastern Standard Time','yyyy-MM-dd')
Error Handling (Scope)	Group try/catch actions and alert of failures	'Scope' action, Run After set to 'has failed'
Log/Notify	Optional auditing or operational transparency	Send Email, Teams Message, SharePoint row

Each step above is integral to a resilient, accurate, and maintainable workflow. Take care to configure IDs dynamically, validate all expressions, and provide clear commenting within your flow for future maintainers.

Final Recommendations and Best Practices

Always dynamically retrieve bucket and plan IDs to prevent flow breakage after administrative changes.
Document each action in Power Automate (preferably in the "Notes" field) for future reference.
Test on non-production data to confirm all details (checklists, assignments, dates) remain accurate after movement.
Monitor the flow health regularly via Power Automate analytics to catch permission or throttling errors early.
Export and back-up your flows regularly, especially for critical automation, using solutions or packages within Power Automate.
Educate your team about automated behaviors to avoid “surprise” task movements and to increase adoption confidence.

Conclusion

Automating the movement of tasks between buckets in Microsoft Planner based on elapsed time (e.g., after 45 days) is both achievable and reliable using Power Automate’s scheduled flows, careful filtering, and in-place Update Task actions. This solution not only streamlines project management but also frees up teams to focus on value-driving work rather than routine administration.

By adhering to the best practices and considerations outlined—especially around date-handling, permissions, and service limitations—as well as proactively monitoring flow runs, you can ensure this automation is both robust and flexible for evolving business needs.

For more advanced requirements—such as moving tasks between plans, capturing additional audit metadata, or integrating with external systems—the Microsoft Graph API offers extended capabilities but introduces additional security, coding, and administration requirements.

Embrace automation in Microsoft Planner not as a nicety, but as a necessity for scale and consistency in modern project management. With the correct design, configuration, and oversight, Power Automate becomes your digital operations teammate—never tired, never late, always precise.

Further Reading and Tutorials:

[Move Planner Tasks Between Buckets in Power Automate (YouTube Video)]
[Create a Task in Microsoft Planner Using Power Automate (SPGuides)]
[Planner - Connectors Documentation (Microsoft Learn)]
[Delay, Recurrence, and Time Handling in Power Automate (EnjoySharePoint, Power Platform Community)]
[Microsoft Planner and Power Automate Community Solutions (Forums)]

For ongoing updates, frequent enhancements, and troubleshooting, always consult Microsoft's official documentation and actively engage with the Power Automate and Planner user communities.

The Value of the CAPM Certification

The Value of the CAPM Certification

Listen to Deep Dive Podcast HERE

The Value of the CAPM Certification Introduction

The field of project management plays a pivotal role in driving success across industries ranging from IT and construction to healthcare and finance. As organizations seek to maximize efficiency and deliver value, the demand for skilled project managers...and, by extension, project management certifications...has surged worldwide. Among the most prominent entry-level qualifications is the Certified Associate in Project Management (CAPM®), administered by the Project Management Institute (PMI®). This globally recognized credential provides a robust foundational framework for aspiring project professionals, setting them on a path for career advancement, industry recognition, and greater earning potential.

CAPM Exam Prep Training Course. Online, Self-Paced.

This article explores the true value of the CAPM certification, outlining its core purpose, benefits, and the direct and indirect ways it impacts professionals’ careers. We will examine who should pursue the CAPM, discuss employer perceptions, draw salary insights, and compare CAPM to other popular project management certifications like PMP® and PRINCE2®. In addition, we will review eligibility requirements, exam structure, costs, and preparation resources, and offer perspectives on industry demand and future trends. In doing so, this article provides a comprehensive view of whether CAPM is “worth it” for early-career and transitional professionals seeking a foothold—and eventually a competitive edge—in the realm of project management.

Overview of the CAPM Certification

The Certified Associate in Project Management (CAPM) is an entry-level project management credential offered by PMI, the world’s leading project management professional organization with over 1.7 million certification holders globally. The CAPM is designed specifically for individuals new to project management, those seeking to formalize their project management knowledge, or those considering a transition into project-based roles. Unlike advanced certifications that require substantial work experience, CAPM focuses on validating a solid understanding of fundamental project management methodologies, principles, and terminology as encapsulated in PMI’s Project Management Body of Knowledge (PMBOK® Guide).

PMI positions CAPM as a crucial stepping stone towards more advanced certifications, particularly the Project Management Professional (PMP®), which demands more rigorous experience criteria. CAPM is not only a standalone credential that signals foundational competence but also a way to bridge the gap for those not yet ready or eligible for PMP certification. It covers predictive (waterfall) as well as agile methodologies, aligning with today’s diverse project environments. CAPM is recognized and accepted across various industries and geographies, emphasizing skills that are universally transferable and in high demand.

The core value proposition of the CAPM certification is its demonstration of an individual’s commitment to professional development in project management, assurance of standardized knowledge, and credibility in the eyes of employers and stakeholders.

Eligibility Requirements and Application Process

One of CAPM’s strongest appeals is its accessibility, making it suitable for a broad audience that includes students, recent graduates, professionals changing careers, and current project team members. Unlike the PMP, the CAPM does not require hands-on project management experience, making it an optimal starting point for those at the entry-level.

Eligibility criteria for the CAPM (as of 2025) are as follows:

Educational Background: A secondary diploma (high school, GED, or global equivalent).
Formal Project Management Education: Completion of 23 contact hours of project management education prior to sitting for the exam.

Candidates are expected to provide information about their educational background and details of their project management training during the application. These education hours may be earned through various channels including PMI-authorized courses, online or in-person bootcamps, university offerings, or even some employer-sponsored training programs. Importantly, the contact hours can be accumulated over any period as long as the requirements are met by the exam date.

The application process itself is straightforward:

Register an account on the PMI Certification Portal.
Enter educational details and the 23 hours of project management coursework.
Submit the application for review.
Once approved, pay the exam fee and schedule the test at a Pearson Vue Testing Center or as an online proctored exam.
Candidates are allowed up to three attempts in one year.
If audited, candidates must provide supporting documentation.

This low barrier to entry is key to the CAPM’s popularity among those who do not yet have access to advanced project roles but seek to formalize and signal their skills.

Exam Content and Structure

The CAPM exam is designed to rigorously test candidates on the essentials of project management, blending both theoretical knowledge and its practical application. In 2023, PMI updated the exam to reflect the latest trends, incorporating business analysis and agile content in addition to predictive methodologies, making it more relevant to the realities of modern project work.

Exam Structure:

Number of Questions: 150 (multiple choice, drag-and-drop, and visual formats)
Time Allotted: 180 minutes (3 hours), usually with a 10-minute break
Languages Available: English, Arabic, Brazilian Portuguese, French, German, Italian, Japanese, Spanish

Domains Covered:

The exam evaluates candidates in the following key knowledge domains:

Project Management Fundamentals and Core Concepts (36%)
Predictive, Plan-Based Methodologies (17%)
Agile Frameworks and Methodologies (20%)
Business Analysis Frameworks (27%)

Topics Spanned:

Integration Management (overseeing all project components)
Scope, Schedule, and Cost Management (defining deliverables, tracking milestones, budgeting)
Quality, Resource, and Communication Management (ensuring standards, allocating resources, stakeholder communication)
Risk, Procurement, and Stakeholder Engagement (identifying/mitigating risk, contracting, managing expectations)

This wide scope ensures that CAPM holders not only understand the what and how of project management, but are also conversant in terminology and best practices that are critical for effective project delivery across industries.

Benefits of Earning the CAPM Certification

The CAPM certification delivers multifaceted career benefits to new entrants, career-switchers, and even experienced project team members seeking credibility.

1. Career Entry and Mobility

CAPM serves as a launchpad for entry-level roles such as project coordinator, project analyst, assistant project manager, and project administrator. These positions are common starting points for later advancement to more senior titles such as project manager or program manager. CAPM provides a baseline of industry-vetted knowledge and assures employers that the holder can speak the “language of projects” effectively.

2. Skill Validation

The certification validates structured knowledge in project management methodologies and tools, raising a professional’s credibility both internally with their current employer and externally in the job market. As global economies increasingly rely on projectized work, the demand for credible, certified project management practitioners continues to grow—PMI estimates that by 2035, up to 30 million more “project professionals” will be needed worldwide.

3. Job Market Differentiation

In highly competitive markets, especially where many candidates might have similar educational backgrounds but lack specialized credentials, CAPM stands out on a resume. Recruiters and hiring managers often seek candidates who demonstrate initiative, commitment to the field, and a willingness to invest in professional growth. CAPM is widely recognized across markets in North America, Europe, APAC, and the Middle East.

4. Pathway to Advanced Certifications

CAPM “counts” toward eligibility for PMP and other advanced PMI certifications, providing a logical progression as professionals gain more project experience. Many organizations sponsor or encourage CAPM as a preliminary step to developing robust in-house project management talent.

5. Industry and Employer Recognition

PMI certifications (CAPM and PMP) are perceived by employers as evidence of international standards adherence. CAPM certification’s global recognition ensures holders are considered for roles in organizations that subscribe to PMBOK standards, regardless of regional best practices. It is especially valuable in sectors where project management maturity is greater, such as IT, construction, healthcare, finance, manufacturing, and defense.

6. Higher Salary Potential

Several industry surveys and salary reports consistently show that certification—especially from PMI—can meaningfully enhance salary prospects, even at the entry level. We examine the salary impact more closely later in this report.

7. Personal and Professional Development

Preparation for the CAPM exam fosters improved organization, critical thinking, and communication skills, which are widely transferable—even for those who later decide not to stay in formal project management roles.

Career Opportunities and Advancement

Earning the CAPM certification unlocks a variety of career pathways. The spectrum of jobs available to CAPM-certified professionals is broad and growing. Several roles are directly aligned to project support and coordination, but with experience, CAPM holders often transition up the career ladder.

Examples of roles commonly available to CAPM holders include:

Project Coordinator
Junior Project Manager
Project or IT Project Administrator
Project Analyst
Project Assistant
Associate Project Manager
PMO Technical Project Manager
Business Analyst

Data from Indeed and other job boards routinely show a substantial number of vacancies open to or requiring the CAPM, particularly in major urban centers and multinational corporations. For instance, Indeed tracked over 600 CAPM-related job listings in early 2025 in the U.S. alone, with a notable presence in Europe, the Middle East, and Asia-Pacific.

Key Sectors and Industries:

Information Technology (IT/Software)
Construction & Engineering
Healthcare & Pharmaceuticals
Finance & Banking
Government & Defense
Consulting Services

CAPM certification also facilitates lateral movement within organizations, allowing professionals to seek secondments or rotational programs into project-based teams. For example, a business analyst or operations specialist with a CAPM credential is more likely to be considered for a project coordination or team lead role than a peer without it.

Long-term, the credential establishes a pipeline for:

Advanced project manager roles
PMO leadership positions
Portfolio/program management
Transition into specialized certifications (e.g., Agile, PRINCE2, CSM)

Employer Perceptions and Industry Recognition

The perception of the CAPM certification among employers and industry decision-makers has grown increasingly favorable, especially in organizations that prize formalized project management processes.

Key Markers of Employer Value:

Assurance of Standardized Knowledge: CAPM ensures that candidates possess a PMI-backed understanding of processes, terminology, and practical frameworks—traits often preferred over experiential claims alone.
Commitment to Professionalism: Candidates who invest in achieving CAPM show seriousness about their careers, persistence, and the soft skills needed for long-term success.
Global Applicability: Because CAPM is rooted in global best practices (the PMBOK Guide), it is recognized in North America, Europe, Asia-Pacific, and the Middle East, making it valuable for multinational and globally distributed teams.
Talent Development Pathways: Many employers use CAPM as an onboarding or upskilling benchmark. It is seen as a feeder for more experienced project management roles and advanced certifications.
Client/Stakeholder Confidence: In client-facing industries, having CAPM-certified staff can assure external stakeholders of competency, enhancing organizational reputations.

Employer testimonials and HR leader quotes reinforce the perspective that CAPM is “a huge asset on the resume” and can be the difference-maker in hiring decisions for both entry-level and mid-tier project roles.

Salary Impact and Return on Investment Global and U.S. Salary Insights

The salary premium for CAPM holders is well-documented across various sources:

According to PMI, CAPM-certified project managers earn an average of $70,000–$74,000 per year in the United States, with mid-level and senior roles reaching up to $120,000 annually for those with additional experience.
Forbes Advisor reports that CAPM holders can earn up to 20% more than their non-certified peers at the entry level.
Coursera cites ranges from $75,000–$92,000 for CAPM-certified professionals in 2025, depending on industry, geography, and experience level.
ProjectManagement.com and Indeed estimate median salaries for project coordinators and junior project managers (frequent CAPM roles) at $54,000–$67,000, with upside as professionals advance.

Return on Investment (ROI):

While the direct costs (exam, training, renewal) range from $300 to $1,000+ (see next section), these are often offset within the first year or two of post-certification employment due to higher starting salaries and the expanded pool of career opportunities. Long-term, CAPM serves as a valuable credential for gaining advanced roles, negotiating promotions, or qualifying for the PMP, which carries even greater salary potential (average PMP salaries approach $118,000–$120,000+).

Key Factors Affecting Salary and ROI:

Industry Sector: Tech, consulting, and engineering often pay higher premiums.
Geographic Region: Salaries are higher in North America and Western Europe than in many other regions.
Supplemental Experience: Combining CAPM with relevant work experience or additional education unlocks more advanced job titles and higher pay grades.
Organization Size: Multinationals and global consultancies tend to offer higher starting salaries.

It is also worth mentioning that PMI certifications are increasingly used as criteria for promotion and lateral moves, representing indirect financial benefits.

Cost and Maintenance of CAPM Certification

The cost structure for CAPM certification is transparent and relatively low compared to advanced credentials, reflecting its focus on accessibility for early-career professionals.

Cost Component PMI Member Non-Member

Exam Fee	$225	$300
Re-examination Fee	$150	$200
PMI Membership (Annual)	$139 ($10 app fee)	Not applicable
Renewal Fee (every 3 years)	$60	$150
Training (23 hours req.)	$200–$500	$200–$500
Study Materials (varies)	$50–$250	$50–$250

Total Initial Outlay: Typically between $500–$900, considering exam, training, and study resources.

Examination Retakes and Maintenance

Candidates may attempt the exam up to three times in a one-year window. Recertification is required every three years, accomplished by completing 15 Professional Development Units (PDUs) and paying the renewal fee. PDUs can be gained through formal learning, volunteering, or teaching project management topics.

Training and Preparation Resources

Preparation for the CAPM exam is a crucial step and is supported by a wide array of training options and materials, including this course; CAPM Exam Prep Training Other options include:

PMI Authorized On-Demand Exam Prep: Self-paced or instructor-led programs that fulfill the 23 formal contact hours requirement.
Online Courses and Bootcamps: Platforms like Coursera, Udemy, and specialized training companies offer tailored CAPM bootcamps ($200–$500). PMConnections Online course HERE
Practice Exams and Question Banks: Many providers and PMI resources offer sample questions matching the exam’s logic, rigor, and domain focus. FREE CAPM Exam Prep Questions
Study Groups and Forums: Peer learning and support are available through local and online PMI chapters, LinkedIn groups, and organizational communities. LinkedIn Facebook
PMBOK Guide Access: PMI members receive complimentary downloads of the latest PMBOK editions, a critical study resource.

Preparation timelines vary, with most successful candidates recommending two to three months of structured study. Official statistics regarding pass rates are not published, but anecdotal data suggests a high success rate for those who complete formalized study and follow PMI best practices.

Comparison with PMP, PRINCE2, and Other Project Management Certifications

CAPM vs PMP vs PRINCE2: At a Glance

Feature CAPM PMP PRINCE2

Target Audience	Entry-level, newcomers	Experienced professionals	Foundation: Beginners; Practitioner: Experienced
Experience Req.	None	3–5 years + 35 education hrs	Foundation: None; Practitioner: PRINCE2 Foundation cert
Education Req.	High school + 23 education hrs	Four-year degree or equivalent + experience	None required for Foundation
Exam Length	150 questions (3 hrs)	180 questions (3h 50m)	Foundation: 60 mins; Practitioner: 150 mins (UK standards)
Cost (USD)	$225 – $300 (+ training)	$405 – $575 (+ training)	Foundation: ~$600-800; Practitioner: varies by region
Content Focus	PMBOK; PM Fundamentals, Agile	PMBOK, Leadership, Agile, Strategy	PRINCE2 methodology (UK standard, waterfall focus)
Renewal	Every 3 years (PDUs + fee)	Every 3 years (PDUs + fee)	Foundation: perpetual; Practitioner: 3-5 years
Avg. Salary (US)	$70K–$92K	$110K–$120K+	$65K–$100K (varies with experience/region)
Global Recognition	High	Highest	High, esp. in UK, EU, APAC
Career Impact	Entry, coordinator, analyst	Project manager, leader, program manager	Project manager, especially in EU/UK

Detailed Comparison CAPM vs PMP

The PMP is considered the “gold standard” in project management and signals not just knowledge, but also extensive experience, leadership, and strategic ability. While the CAPM focuses on foundational concepts and entry-level skills, the PMP is for those who have spent years leading projects. PMP holders command higher salaries and greater job mobility. Nonetheless, CAPM is frequently used as a stepping stone to PMP, especially for professionals who do not yet meet the rigorous experience requirements.

CAPM vs PRINCE2

PRINCE2 (Projects in Controlled Environments) is a methodology-oriented certification extensively adopted in the UK, EU, and Commonwealth countries. PRINCE2 is available both at Foundation (no experience required) and Practitioner (requires Foundation certification). The CAPM, by contrast, provides a broader view supported by the PMBOK standards, focusing on general project management principles applicable worldwide. While PRINCE2 is project lifecycle-focused and methodology-driven, CAPM imparts flexibility and prepares candidates for a range of project contexts, including agile and hybrid approaches.

CAPM vs Other Certifications

Other notable certifications include:

CSM (Certified ScrumMaster): Focuses on agile project management and Scrum methodology. Favored in software/tech, but less industry-general than CAPM.
PMI-ACP (Agile Certified Practitioner): Advanced agile focus, requires practical experience.
CompTIA Project+: General, less rigorous and recognized than PMI certifications.
Associate in Project Management (APM): Entry-level, less global recognition than CAPM.
PRINCE2 Foundation: Focused on methodology, strong in UK government and businesses.

Each certification serves different professional goals, industries, and career stages, but CAPM’s unique strength is its broad recognition, foundational rigor, and entry-level accessibility.

Industry Demand and Future Trends Rising Demand for Project Professionals

According to PMI projections and industry data, the global economy will demand nearly 30 million additional project professionals by 2035. Driving forces include digital transformation, globalization, and the increasing complexity of business ecosystems. These trends make project management skills more critical in sectors such as IT, construction, government, financial services, and healthcare.

Growing Prominence of Certifications:

Entrepreneur Media, Forbes Advisor, and other reputable sources consistently rank CAPM as one of the most in-demand certifications for early-career professionals.
Employers, particularly in regions with mature project management ecosystems, increasingly require or prefer candidates with PMI or PRINCE2 certifications for even lower-level project roles.

Integration of Agile and Hybrid Approaches:

Recent updates to the CAPM exam reflect the necessity for project managers to be skilled in both predictive (waterfall) and adaptive (agile/hybrid) methodologies. As organizations continue to pursue digital initiatives, candidates with broad-based, cross-methodology training will remain in high demand.

Remote Work and Digital Skills:

The rise of remote and hybrid work has accelerated demand for professionals who are adept at virtual team coordination, digital collaboration tools, and online project management platforms—skills that are embedded in many CAPM preparation programs and exam domains.

Conclusion

The Certified Associate in Project Management (CAPM) remains one of the most valuable entry-level project management certifications globally, offering a clear pathway to career entry, advancement, and mobility. Its low barrier to entry, robust curriculum, and broad employer recognition make it an ideal starting point for students, career changers, and early-career professionals. The CAPM credential validates not only knowledge of project management fundamentals but also a professional’s commitment to the field—key attributes that positively influence employer perceptions and hiring decisions.

Productivity gains, project success rates, and stakeholder confidence are just a few of the indirect benefits that organizations realize by hiring CAPM-certified staff. For individuals, the certification leads to quantifiable salary premiums, greater job security, and new avenues for professional development. Compared to other certifications, CAPM delivers unique advantages: accessibility, scalability (as a step to PMP), and international recognition.

As the project management profession continues to expand and evolve, investing in a CAPM certification is likely to remain a wise career move—offering a strong foundation for long-term growth in a world where structured, effective project execution is more valuable than ever.

Change Management & Artificial Intelligence

Change Management & Artificial Intelligence: Bridging Mindsets in the Digital Transformation Era

Listen to the Deep Dive Podcast from HERE

In today’s volatile landscape, organizations aren't just adopting new technologies, they're reshaping cultures, redefining workflows, and reimagining leadership. One of the most disruptive forces in this shift is Artificial Intelligence. But deploying AI isn't merely a technical upgrade, it’s a human endeavor. Enter change management.

Why Change Management Still Reign:

AI may offer unprecedented automation and insight, but without effective change management:

Stakeholders resist new tools.
Teams fall prey to “pilot purgatory.”
Value gets lost in translation from strategy to execution.

Change management ensures adoption, mitigates resistance, and anchors transformation in human behavior. It translates complex digital shifts into tangible action.

Where AI Meets Change Managemen:

Artificial Intelligence isn’t just a challenge, it’s an enabler of change management itself. Here's how:

AI Capability Change Management Impact:

Predictive analytics	Identifies resistance pockets before they emerge
Natural language processing (NLP)	Analyzes sentiment from surveys, emails, and feedback
Automation & chatbots	Streamlines stakeholder communication and training
Machine learning	Refines engagement strategies based on behavioral data

When AI is woven into change frameworks, like Kotter’s 8 steps or the ADKAR model, it allows practitioners to forecast adoption risks, tailor messaging, and track progress in real time.

Integrating Agile Delivery & AI-driven Change

For organizations using Agile methodologies, AI enables:

Real-time velocity tracking and sprint effectiveness analysis.
Automated backlog grooming insights.
Enhanced retrospectives via sentiment analytics.

The result? Change initiatives become iterative and insight-driven—mirroring the Agile ethos of continuous improvement.

Key Takeaway:

AI is not a silver bullet—it’s a catalyst that amplifies strong change management.
Effective integration requires synergy between digital tools and human leadership.
Organizations that pair AI with adaptive change frameworks will not just implement innovation—they’ll institutionalize it.

AI Adoption: A People-First Change Management Journey for PMO Leaders

AI Adoption: A People-First Change Management Journey for PMO Leaders

AI adoption is not just another tech upgrade – it’s fundamentally a people-focused change. In fact, many organizations find that integrating Artificial Intelligence (AI) into operations succeeds or fails based more on human factors than on the technology itself.

This reality makes AI adoption closer to an Organizational Change Management (OCM) challenge than a straightforward Digital Transformation project. For Program/Project Management Office (PMO) leaders, recognizing this distinction is critical to guiding AI initiatives to success.

Understanding Key Concepts:

AI Adoption – “the strategic integration of artificial intelligence technologies into organizational operations to enhance efficiency, productivity, and innovation,” according to a recent definition. It goes beyond mere installation of AI tools; it entails embedding AI into workflows and daily processes so that employees actually use these tools effectively in their work.

Organizational Change Management (OCM) – “the systematic approach and application of knowledge, tools and resources to deal with change,” involving defining and adopting new strategies, structures, and processes to transition from a current state to a desired future state. In practice, OCM focuses on guiding people through change – aligning stakeholders, communicating the vision, training employees, and mitigating resistance – to ensure changes are embraced and sustained.

Digital Transformation (DT) – “the process of using digital technologies to create new – or modify existing – business processes, culture, and customer experiences to meet changing business and market requirements,” as defined by Salesforce. It is a broad initiative that fundamentally rethinks how an organization delivers value by leveraging technologies (cloud, data, mobile, AI, etc.). Digital transformation often involves enterprise-wide modernization and cultural shifts toward digital-first mindsets.

AI Adoption vs. Digital Transformation: Scope and Focus

Digital Transformation is broad and technology-driven, encompassing end-to-end modernization of processes and business models using various digital tools. For example, a bank’s digital transformation might include moving to cloud infrastructure, launching mobile apps, and using data analytics to improve decision-making. The goal is comprehensive change in how the organization operates and delivers value. While digital transformation does require change management (e.g. rethinking processes and securing company-wide buy-in for new ways of working), its focus is on leveraging technology to drive strategic outcomes.

AI Adoption is narrower in scope but deeper in impact on roles and workflows. It can be seen as one component or offshoot of digital transformation – specifically focusing on deploying AI capabilities (like machine learning models, AI assistants, or predictive analytics) within the business. Unlike general digital upgrades, AI systems often take on decision-making or automated tasks that were previously done by humans. For instance, implementing an AI chatbot in customer service or an AI diagnostic tool in healthcare introduces a tool that learns and makes recommendations, not just a tool users manually operate. This means AI adoption can fundamentally alter job duties, workflows, and how decisions are made, even if the overall business processes remain the same. As a result, the cultural and employee-facing challenges in AI adoption are particularly pronounced.

Crucially, AI adoption doesn’t equate to instant transformation success. Many organizations discover that deploying AI technology is the “easy” part; getting people to use it correctly and confidently is much harder. If treated purely as a tech install, AI projects can falter. Installing an AI system without preparing the workforce often leads to low usage and wasted investment.

In contrast, organizations that approach AI projects with a people-first, change-centric mindset see far better outcomes. In summary, digital transformation provides the strategic umbrella under which new technologies (like AI) are introduced, but AI adoption itself demands intense focus on the human side of change.

Why AI Adoption is Essentially a Change Management Challenge

Adopting AI is about changing people’s work, not just IT systems. Prosci’s research highlights that while “AI implementation” is the technical deployment, “AI adoption…is about people” – it’s the process of ensuring the technology is actually embraced in daily work. This makes AI adoption akin to leading a major organizational change. Key reasons why AI initiatives align closely with OCM principles include:

Behavioral Change Required: AI must become a “natural, effective part of everyday work”. Achieving this means employees must alter their routines, learn new skills, and trust new tools. Such behavior change is exactly what OCM practices are designed to facilitate. Like any large change (e.g. adopting a new process or policy), it requires communication, training, and gradual buy-in.
Human Factors Dominate Success: Studies show human factors are the primary barriers in AI projects – fear of job displacement, lack of training, and mistrust of AI outputs are common issues. Employees may worry an AI system will make their role obsolete or may distrust algorithmic decisions. These concerns can lead to hesitation or resistance. Traditional digital transformations certainly encounter resistance too, but AI touches a sensitive nerve: it challenges the very role of human judgment and expertise in a workflow. Over 60% of organizations report people-related issues as the top challenge in AI initiatives, far outweighing technical hurdles.
Need for Communication and Trust: Organizational change management emphasizes transparent communication and stakeholder engagement. This is vital for AI adoption. Employees need to understand why the AI is being introduced, how it will affect their jobs, and what support they will receive. Clear messaging can dispel myths (“AI is here to help you, not replace you”) and build trust in the new tools. Without deliberate change management, rumors or fears can fester, undermining adoption.
Training and Skill Development: A cornerstone of OCM is equipping people with needed skills for the future state. AI adoption often reveals skill gaps – for example, staff may lack knowledge in interpreting AI recommendations or in data-driven decision-making. In fact, insufficient training in AI tools accounts for about 38% of adoption challenges in enterprises. A robust change management approach will include targeted training programs and upskilling initiatives so that employees feel confident and capable using AI. When people feel competent and empowered, they are far more likely to embrace the change instead of resisting it.
Leadership and Sponsorship: No major change succeeds without leadership buy-in and sponsorship – another parallel between OCM and successful AI projects. Executive support provides vision and resources, and signals to the organization that the change is important. Lack of this support is a known failure factor (about 43% of AI adoption failures are attributed to insufficient executive sponsorship). In practice, PMO leaders should ensure an executive champion visibly backs the AI initiative, communicates its strategic value, and addresses high-level concerns. This top-down reinforcement aligns with change management best practices for securing organizational alignment.

In essence, AI adoption lives or dies by how well people adapt to working with AI. The technology may be cutting-edge, but the implementation plan must address human psychology, team dynamics, and corporate culture. This is why treating AI rollouts as change programs – with change managers or OCM frameworks involved – significantly increases success rates. It’s a lesson many digital transformation efforts learned the hard way: even the smartest technology will underdeliver if the people aren’t on board and proficient.

Learning from Examples

Real-world examples underscore how AI adoption thrives with change management (and struggles without it):

Healthcare: A large hospital implemented an AI-powered diagnostics system (IBM Watson for Oncology) to assist clinicians. Initially, doctors were hesitant to trust the AI’s recommendations. The hospital brought in change management consultants to engage the medical staff in the process. They provided hands-on training, adjusted workflows in collaboration with doctors, and maintained open forums for feedback. As a result, the AI tool became an accepted part of the workflow. The outcomes were striking: diagnostic error rates dropped by ~30%, and report turnaround times were cut in half after AI integration. Without the change management effort, those AI tools might have been ignored or under-utilized; with it, the hospital achieved a significant improvement in care quality and efficiency.
Financial Services: A global bank introduced AI-driven analytics to its lending process. When rolled out, loan officers felt threatened by the “black box” algorithms. Recognizing this as a change management issue, the PMO led an initiative to demystify the AI. They held workshops explaining how the AI model worked, framed it as a decision-support tool (not a decision-maker), and gradually introduced it alongside existing processes. The bank also adjusted performance metrics to reward effective use of AI insights, not just loan volume. Over time, adoption climbed. The AI flagged subtle risk indicators that humans often missed, leading to better loan portfolio performance. The key was humanizing the change – making staff co-owners of the AI adoption journey.
When Tech-Only Approach Fails: Contrast these successes with organizations that took a purely technical approach. In some cases, companies have invested in sophisticated AI platforms that technically function well, but users simply bypass them. One common story is an enterprise that launched an AI knowledge base intended to help employees find information quickly – but without proper change management, most employees continued asking colleagues or using old systems out of habit. The AI tool languished with low uptake, and the expected productivity gains never materialized. This “shelfware” outcome can often be traced back to missing OCM elements: users were not convinced of the tool’s value, not trained adequately, or not supported through the change curve. Such examples reinforce that adoption must be nurtured, not assumed.

Implications for PMO Leaders:

For PMO leaders steering AI projects, the takeaway is clear: manage your AI adoption like a change program. This involves combining classic project management rigor with OCM strategies. Here are key recommendations and best practices:

1. Kickoff with Clear Vision and Sponsorship: Ensure there is a well-defined purpose for the AI initiative tied to business outcomes (e.g. “reduce response time by 50% with an AI assistant” or “improve forecast accuracy using machine learning”). Secure an executive sponsor who will champion this vision. A compelling vision from leadership helps rally stakeholders and gives the project authority and priority. Communicate the “why” of the AI adoption early and often.
2. Integrate Change Management into the Project Plan: Treat “people readiness” as a workstream in the project. Conduct a change impact assessment upfront – identify which roles, processes, and teams will be most affected by the AI introduction. Develop a structured plan to manage that change: this should include a communication plan (what messages, to whom, how frequently), a training plan (skills needed and how to develop them), and a resistance mitigation plan (how to gather feedback and address concerns). Leverage OCM frameworks like ADKAR or Prosci’s methodology to structure these activities. For example, if rolling out an AI analytics tool, plan user training sessions and perhaps a pilot phase where feedback is collected and the approach refined. Make the change management tasks as explicit as technical tasks in your AI project schedule.
3. Engage Stakeholders and End-Users Early: Don’t build the solution in a vacuum. Involve representatives of the end-user community in the AI project from design through implementation. This might mean including business SMEs or front-line employees in requirement definition, prototype reviews, and testing. Early involvement creates ownership – users feel heard and are more likely to support the outcome. It also surfaces practical issues early (e.g., if an AI recommendation interface is confusing, you learn this in pilot and can fix it). Some organizations use “AI champions” or early adopters in each department: these are tech-savvy volunteers who try the AI tool early, give feedback, and later advocate its benefits to peers. This peer influence can significantly smooth adoption.
4. Communicate, Educate, Communicate: You cannot over-communicate during an AI adoption effort. Develop clear, tailored messaging for different groups (executives, managers, end-users) about what the AI tool is, why it’s being introduced, and how it will affect them. Address the elephant in the room – if people might fear job loss or reduction of responsibilities, have leadership acknowledge these fears candidly and explain how the organization plans to handle them (e.g., “Our AI will augment your work, not replace you. We are retraining our team to work alongside these tools.”). Share success stories and quick wins as the project progresses to build confidence. Also, educate users not just on how to use the AI, but on basic AI concepts if needed – for instance, if using a machine learning model, explain its accuracy metrics and limitations to manage expectations and foster trust.
5. Provide Training and Ongoing Support: Training isn’t one-and-done for AI. Offer initial training sessions (workshops, e-learning, hands-on labs) to get users comfortable with the AI tool before it’s fully rolled out. Given that 38% of AI adoption challenges come from lack of proficiency, this is a critical investment. Make training role-specific where possible (so people see how AI applies to their job). After go-live, ensure there is a support structure: help desks, “AI coaches,” or an online forum where users can ask questions as they start using the AI in real scenarios. This echoes the change management principle of reinforcing the change. Celebrate those who embrace the AI and share their positive outcomes – it encourages others to follow.
6. Monitor Adoption and Adapt: PMOs are used to tracking project KPIs; for AI adoption, include adoption metrics as success criteria. For example, measure the usage rate of the AI system, the number of transactions or decisions it’s supporting, or user satisfaction levels with the tool. If adoption is below targets, treat it as an issue to be addressed, not an end-user “failure.” Investigate why – perhaps a specific department didn’t get sufficient training, or the AI insights are not as useful in practice and the model needs tuning. Be ready to adjust the rollout plan or provide additional change interventions (like refresher trainings or tweaking the AI’s integration into workflow). Continuous improvement is part of both agile project management and change management; use feedback loops to ensure the AI genuinely becomes part of the new normal.
7. Balance AI Adoption with Other Initiatives: Many PMO leaders juggle multiple transformation initiatives simultaneously. When introducing AI into a portfolio of projects, ensure it aligns with the broader digital strategy. AI adoption shouldn’t happen in a silo; for instance, if you have a digital transformation roadmap, slot the AI project into that roadmap with clear dependencies and contributions to larger goals. Coordinate resources so that the AI project doesn’t starve other critical projects (or vice versa). It’s about integration, not competition: position AI as enhancing ongoing digital efforts (e.g., AI analytics augmenting an existing data transformation program). Also, be mindful of change saturation – if the organization is already undergoing significant change, time the AI rollout in a way that employees aren’t overwhelmed by too many new tools at once. Sometimes a phased approach is better, or bundling training for multiple new systems together if they are related.
8. Leverage Lessons from Broader Digital Transformation: PMO leaders who have managed digital transformations likely learned valuable lessons about change (for example, the importance of leadership messaging or the pitfalls of under-training). Apply those lessons here. However, also recognize AI might present new challenges – for instance, ethical considerations and policy requirements (data privacy, AI bias) could require additional governance work. Ensure the project plan covers these aspects (e.g., involve legal or compliance teams early when deploying AI that affects customers or sensitive data). By handling such concerns proactively, you prevent last-minute roadblocks and build trust in the AI’s outcomes (people are more willing to use an AI if they know it’s been vetted for fairness and privacy).

In summary, PMO leaders should act as both project strategists and change champions for AI adoption. It’s not enough to deliver an AI system on time and budget; true success is realized only when the organization is utilizing AI and gaining value from it. That outcome lies in the realm of people’s behavior and acceptance. As a PMO leader, treat your AI project’s Go-Live as the beginning of the change, not the end. Plan for the post-implementation adoption phase as diligently as you plan the development phase.

By viewing AI adoption through an OCM lens, PMO leaders can ensure that the technology’s potential is fully realized. When employees are prepared, supported, and bought into the change, AI integration can lead to impressive performance gains – from efficiency improvements to new insights – as evidenced by companies that have done it right. On the other hand, approaching AI purely as a tech rollout risks underutilization. AI adoption is a human journey. For PMOs guiding their organizations into this new era, success will come from leading the change, not just the project. Embrace your role as a change leader, and you will help unlock AI’s true value for your business.

Microsoft AI Agents - CLARIFIED!

Listen to Deep Dive Podcast HERE

At this moment in time, Microsoft has the normal person confused!

They are consistently using the term AI Agent as if it is one thing.

When in reality, there are three different kinds of Agents you can create depending upon what license (if any) you have.

1. SharePoint Agents

2. M365 Copilot Agents

3. Microsoft Copilot Studio Agents

Hopefully this list will bring some clarity

What are Agents
- Duration: 4 minutes
- Source: Microsoft - Video
- Output: Knowledge
- Link: https://learn.microsoft.com/en-us/shows/mastering-copilot-studio/what-are-agents
What are SharePoint Agents
- Duration: 2 minutes
- Source: Microsoft - Video
- Output: Knowledge
- Link: https://www.youtube.com/watch?v=G4T7_9t0u0I&t=125s
How to Create a SharePoint Agent
- Duration: 30 minutes
- Source: Microsoft Article
- Output: Knowledge
- Link: https://techcommunity.microsoft.com/blog/microsoft365copilotblog/ignite-2024-sharepoint-agents-now-in-general-availability/4298746
How to Add the Out of the Box AI Agents in Copilot
- Duration: 3 minutes
- Source: YouTube
- Output: Knowledge
- Link: https://www.youtube.com/watch?v=EReIJvNVq4k&list=PLldwp8u2aiE1Lk_ctdnnY8SuoSbHNcJo8&index=47
How to Create a Custom AI Agent in Copilot
- Duration: 7 minutes
- Source: YouTube
- Output: Knowledge
- Link: https://www.youtube.com/watch?v=LXoisdiXUw0&list=PLldwp8u2aiE1Lk_ctdnnY8SuoSbHNcJo8&index=48
How to Build an AI Agent in Copilot Studio from Scratch
- Duration: 40 minutes
- Source: YouTube
- Output: Knowledge
- Link: https://www.youtube.com/watch?v=25Gv19pFUTU
Create and Publish Agents with Microsoft Copilot Studio (Custom Chatbot)
- Duration: 5 hours
- Source: Microsoft – Learning Path (6 Modules)
- Output: Trophy
- Link: https://learn.microsoft.com/en-us/training/paths/work-power-virtual-agents/?source=learn
Create Agents in Microsoft Copilot Studio (Agent Flow)
- Duration: 8 hours
- Source: Microsoft – Learning Path (9 Modules)
- Output: Trophy
- Link: https://learn.microsoft.com/en-us/training/paths/create-extend-custom-copilots-microsoft-copilot-studio/
- PMConnection Copilot is built using Microsoft Copilot Studio. Give it a try!
Microsoft Applied Skills: Create Agents in Microsoft Copilot Studio
- Duration: 2 hours – Hands-on Lab
- Source: Microsoft – Online Assessment (Prerequisite: #4)
- Output: Credential
- Link: https://learn.microsoft.com/en-us/credentials/applied-skills/create-agents-in-microsoft-copilot-studio/

Consolidating Multiple Smartsheet Trackers and Managing Action Items

Consolidating Multiple Smartsheet Trackers and Managing Action Items

Managing multiple project trackers in Smartsheet can be streamlined by organizing them in a single workspace and using consistent structures for related sub-sheets (like action item logs). This guide covers how to do four different things, 1) consolidate sheets into one workspace, 2) how to organize main trackers and sub-sheets, 3) setting up automatic reminders for action items, and 4) ways to sync or extract action items to Google products (Docs and Sheets). Each section provides clear steps and best practices for implementation.

1. Consolidating Multiple Sheets into One Workspace

A Smartsheet Workspace is a container that can hold multiple sheets, reports, and dashboards, making it easier to organize and share your project trackers. Consolidating your sheets into a single workspace offers a central place for your team to access all trackers. Here’s how to do it:

Create a New Workspace: In Smartsheet, click the Solution Center (plus icon) and select Create Workspace. Give the workspace a descriptive name (e.g., “Project Portfolio Workspace”). This will serve as the central folder for all your trackers. Watch this VIDEO
Move Existing Sheets into the Workspace: For each of your tracker sheets, right-click the sheet name (in the Home or Sheets directory) and choose Move to Workspace, then select the new workspace. This groups all trackers under one umbrella for easy access. Watch this VIDEO
Organize with Folders (Optional): Inside the workspace, you can create folders to further organize content. For example, create a folder per project or category, and place the main tracker and its sub-sheets (like action items) in that folder. Use clear naming conventions for folders and sheets so that related items are easily identifiable.
Manage Sharing and Permissions: Share the workspace with your team (or specific folders/sheets as needed) to grant them access to all trackers at once. This is more efficient than sharing individual sheets one by one. If a user is shared to the workspace, they inherit access to all contained sheets. Watch this VIDEO
Use a Portfolio Report or Dashboard: To get a consolidated view of all projects’ status, consider creating a Smartsheet Report that pulls key info from all tracker sheets. You can configure a report to include rows from multiple sheets (e.g. all tasks across projects or high-level milestones). For example, a Smartsheet report can aggregate data from multiple sheets into one view. This is similar to Excel’s multiple tabs with a summary, and it allows you to see all tracker data in one place without merging the sheets into one. You can then add this report to a dashboard for at-a-glance status across projects.
Buiding a Report VIDEO
Building a Dashboard VIDEO

(Note: Smartsheet’s “WorkApps” is another native feature that can create a custom app-like interface to combine multiple sheets and reports in one view. This is a premium option that might be useful for a large portfolio.)

2. Organizing Trackers and Related Sub-Sheets (Action Items)

For each main tracker (e.g., a project plan or task tracker), it’s helpful to maintain separate sub-sheets for detailed logs such as Action Items, Risks, or Issues. Here are best practices for organizing these related sheets:

Use Separate Action Item Sheets per Tracker: If the action items or to-do lists are too detailed to live on the main project sheet, create a dedicated Action Items sheet for each project. This keeps the main tracker focused on high-level tasks while the action log captures granular follow-up items. As one Smartsheet expert suggests, “You could have a separate Action List sheet for each project”. Name each action item sheet clearly (e.g., Project A – Action Items) so it’s associated with its project. Watch this VIDEO on how to combine multiple sheets
Alternatively, Use a Master Action Items Sheet: If you prefer a single list of all action items, create one master action item sheet and include a column (dropdown or text) for Project Name or ID. Team members would select which project each action item belongs to. This way, all actions reside in one sheet and can be filtered by project. An expert notes that you can also maintain “a master Action List where you select which project it is”. This approach simplifies reporting on all action items across projects, but it requires discipline in tagging each item with the project.
Link or Reference Between Main Tracker and Action Log: Maintain clear traceability between a project tracker and its action items:

In the main tracker sheet, you might include a column or link that points to the action items sheet (e.g., a cell with a hyperlink to “Open Action Items Sheet”). This provides quick navigation for users reviewing the project plan.
In the action item sheet, include a reference back to the main project or specific task (for example, a column for “Related Task ID/Name”). This context ensures everyone knows how the action item ties into the bigger project.
Cross-sheet formulas or cell linking can be used to roll up information. For instance, you could use a COUNTIFS formula to count how many open action items exist for a given task or project and display that on the main sheet. Smartsheet allows cell links across sheets, so you could link a status or count from the action log into the main tracker. In practice, setting up such connections often involves “a combination of cell linking and cross-sheet formulas”.

Consistent Column Structure: Keep your action item sheets consistent in design. Common columns include Action Item Description, Owner/Assignee (contact column), Due Date, Status (e.g., Not Started, In Progress, Completed), and any priority or category fields needed. Consistency makes it easier to manage automation and to create a report that covers all action item sheets.
Use Reports for Aggregate Views: If you maintain separate action item sheets per project, you can build a Report that pulls all action items assigned to a particular person or due in the next week across all projects. This is useful for managers or team members who want a single to-do list. Because Smartsheet reports can aggregate rows from multiple sheets with the same columns, you can see all action items in one place without merging sheets.
Templates and Reusability: If you frequently create new projects, consider making a template set: a main project sheet template and an action items sheet template. That way, each new project’s sheets are created consistently. Placing all these in one workspace (as above) keeps them organized.

3. Setting Up Automatic Reminders for Action Items

One of Smartsheet’s strengths is its Automation engine, which can send alerts and reminders based on criteria such as dates. To ensure action items don’t slip through the cracks, set up automatic reminders for upcoming and overdue tasks. Follow these steps:

Open the Action Items Sheet: Go to the specific Action Items sheet (or master action log) where you want reminders.
Create a New Automation Workflow: Click on the Automation menu and select Create a Workflow (or Manage Workflows to create a new one). Smartsheet offers a template gallery for common automations; you might see a template like “Remind Assignees about tasks due soon” which you can use. Otherwise, start from scratch.
Configure the Trigger (Date-Based): Set the workflow’s trigger to “When a date is reached.” In the trigger settings, choose the Date column (e.g., the Due Date column on your action items). Then choose when to trigger. For example, you can select “Run once, 2 days before” the due date (or 1 week before, etc.). Smartsheet allows you to pick a number of days before or after the date. (You may need to scroll in the date dropdown to find options like “1 week before”.) By setting “2 days before Due Date”, the workflow will trigger on each row two days prior to its due date.
Set Conditions (Optional): You can refine which rows send reminders. For example, add a condition: Status is not Complete (so that only incomplete items trigger alerts). You might also add “Assigned To is not blank” to ensure only tasks with an owner send alerts.
Define the Action (Alert or Reminder): Choose an action such as “Alert someone”. In the alert settings:

Under “Recipients”, select “Send to contacts in a cell” and choose the Assignee/Owner column. This ensures the notification goes directly to the person responsible.
Customize the message if desired. For instance: “Reminder: Action item "{{Action Item}}" is due on {{Due Date}}. Please update the status or complete this item.”
You can also CC additional people or set it to send to a fixed email or contact list (e.g. the project manager) if needed.

Save the Workflow: Name it clearly (e.g., “Due Date Reminder – 2 Days Before”) and turn it on. Smartsheet will now automatically email or notify the assignee two days before their task is due, including a link to the row.
Setup Additional Reminders (Best Practice): Often, one reminder isn’t enough. Consider adding:

A day-of-due-date reminder: Create another automation: Trigger “When a date is reached -> run once on the due date (0 days before)” with similar conditions, to ping the owner on the due date if still not complete.
An overdue alert: Trigger “When a date is reached -> 1 day after” (or use a condition like due date in the past) to notify assignee or escalate to a manager that the item is overdue.
Weekly digests or recurring reminders: Smartsheet can also do recurring date triggers. For example, you can set a workflow trigger to “Run every Monday at 9:00 AM” and then as conditions include all rows where Status is not Complete and Due Date is in the past week or coming week. This would send a weekly summary or batch of reminders. (This approach requires a bit more setup with conditions or helper fields, but can be useful for summary notifications. In a community example, a user scheduled a workflow for every Thursday and used conditions to catch items due in a week.)

Test the Automation: It’s wise to test with a sample row. Set a due date a day or two from now and ensure the assigned person (maybe yourself in a test) receives the email at the expected time. Adjust timing or messaging as needed.
Watch this VIDEO

Tips:

Reminders from Smartsheet will appear as emails (or push notifications in the app) listing the row details. Encourage users to update the sheet when they get a reminder (you can even use the “Request an Update” action instead of a simple alert – this way the email contains an Update Form for that row).
Smartsheet automations are row-based, meaning each row’s date will trigger its own alert when criteria are met. Only the assignee of that row (and whoever else you designate) will get the email, not everyone in the sheet.
Be careful not to spam users with too many emails. It’s best to plan a couple of key reminders (e.g., one a few days before due, one on due date) rather than daily pings, unless truly needed for critical items.

4. Extracting or Syncing Action Items from Smartsheet to Google Products

Sometimes you may want to generate a document (or a portion of a document) that lists action items – for example, a weekly status report in Google Docs that includes all open action items. Smartsheet doesn’t natively sync to Google Docs in real-time, but there are both native tools and third-party integrations that can help you export or sync data from Smartsheet to a Google Doc.

Option 1: Smartsheet for Google Docs (Add-on)

Smartsheet provides a Google Docs add-on called “Smartsheet for Google Docs” which allows a form of mail-merge from Smartsheet to a Docs template. With this add-on, you can take your Smartsheet data and automatically insert it into a Google Doc format. According to Smartsheet’s description, “Smartsheet for Google Docs is a Google Docs add-on that allows you to create invoices, form letters, envelopes, or other documents from your Smartsheet data”. In practice, you would:

Install the Smartsheet for Google Docs add-on from the Google Workspace Marketplace (it’s free and built by Smartsheet).
In Google Docs, design a template document with placeholders for your Smartsheet fields (for example, a table or bullet list structure for action items, using placeholder tags like <>).
Use the add-on to connect to your Smartsheet and select the sheet (or report) containing action items. You can then generate a Google Doc that replaces the placeholders with actual Smartsheet data, essentially creating a snapshot of the action items.
This is useful for creating a one-time or periodic document (e.g., a meeting minutes doc that includes the latest action items). It’s not an auto-sync; you would run the merge whenever you need an updated doc. However, it automates the tedious copy/paste process by pulling live data at the time of generation. It’s like a mail merge, allowing you to “create multiple Google documents in a snap” from Smartsheet data.

Use case: For instance, before a team meeting, you could run the add-on to generate a Google Doc agenda that contains a section listing all open action items from Smartsheet. This Google Doc can then be shared or further edited for the meeting.

Get Smartsheet for Google Docs add-on from HERE

Option 2: Automated Integration with Zapier or Make

Watch this VIDEO

For a more continuous or automated sync between Smartsheet and Google Docs, third-party integration platforms like Zapier or Make (Integromat) are very effective. These services can watch for changes in Smartsheet and update a Google Doc accordingly, with no manual intervention after setup. Here are a couple of approaches using these tools:

Append to a Google Doc for each new action item: Using Zapier, you can set up a “Zap” with Smartsheet as the trigger and Google Docs as the action. For example, trigger “New Row in Smartsheet” (or “New or Updated Row”) on your Action Items sheet. For each new action item, have the Zap append text to a specific Google Doc. Zapier’s Google Docs integration provides an action called “Append Text to Document” which will add text to an existing doc. You could format the appended text to include key fields (e.g., “Project X – Task Y – Owner: John – Due: 5/30/2025”). Over time, the Google Doc will build a running list of all action items added. This effectively creates a log in Docs that mirrors your Smartsheet.
Create a new Google Doc from a template for each row or update: Alternatively, use Zapier to generate separate documents. Zapier has a action “Create Document from Template” in Google Docs. For instance, “whenever a new row is added in Smartsheet, a document is instantly created from a template in Google Docs”. You prepare a Google Doc template with placeholders (like {{ActionItem}}, {{DueDate}}), and Zapier will make a copy of that template for the new action item, populating those fields. This might be overkill for every single action item (it would create many documents), but it could be useful for certain workflows (like generating an individual task briefing or ticket).
Scheduled syncs or summaries: With Make.com (or even Zapier’s scheduling), you could set up a scenario that runs every day or week, pulls all “open” action items from Smartsheet via its API, and then writes them into a Google Doc (either replacing the content or appending). Make tends to allow more complex logic (like clearing a doc then adding a fresh list each time).

Tip: When using these integrations, ensure you have the proper access tokens/API connections set up for Smartsheet and Google. Zapier and Make provide a no-code interface: you authenticate both accounts, then define triggers and actions. Keep in mind Zapier’s free plan checks for new data every 15 minutes (which is usually fine for action items). Make can run scenarios on schedules or triggers as well.

The result of an integration is a near-real-time reflection of Smartsheet data in Google Docs. For example, as soon as an action item is added or marked done in Smartsheet, the linked Google Doc could update to add or update that item (depending on how the Zap is configured). This is great for dynamic documentation or for stakeholders who prefer Google Docs over Smartsheet.

Option 3: Using the Smartsheet API (Custom Solution)

For those with technical resources, the Smartsheet API gives full access to read sheet data and even update Google Docs via Google’s API. A custom script (in Python, JavaScript, etc.) could extract action items and push them to a Google Doc. This approach is highly customizable:

You might write a Google Apps Script that periodically pulls data from Smartsheet (using Smartsheet’s API and an API token) and writes to a Google Doc or Google Sheet.
Or use a scripting environment (AWS Lambda, Google Cloud Function, or a simple script on a schedule) to generate a Google Doc report from Smartsheet data.

This method is powerful but requires coding. It may be unnecessary if Zapier or the Google Docs add-on covers your needs, but it's good to know it's possible. (For example, an API script could compile all open action items, sort them by project or owner, and format a Google Doc with tables or lists exactly as you want.)

Learn more HERE

Option 4: Export/Manual Methods (for completeness):

If an automated sync is not critical, you can always export your Smartsheet data and use it in Google Docs:

Simply export the Action Items sheet to Excel or Google Sheets (Smartsheet has a “Export to Google Sheet” option if you have linked your Google account). Once in Google Sheets, you can copy/paste or use the Google Sheets → Google Docs linking (e.g., copy a table from Sheets to Docs with a link for updating).
Or copy rows from Smartsheet and paste into a Google Doc table. This is manual but quick for one-off needs.
These manual methods work for static reports or one-time documentation (like an end-of-month report that lists all action items closed this month).

Option 5: Smartsheet to Google Sheets

Watch this VIDEO

Summary of Integrations: The native Smartsheet for Google Docs add-on is excellent for generating polished documents from Smartsheet data using templates (similar to mail merge). Zapier and Make provide automated, ongoing syncing – for instance, appending each new Smartsheet row to a Google Doc is a straightforward Zapier workflow. When choosing an approach, consider how often you need the sync and who the audience is. For collaborative, real-time needs, a live Smartsheet or a published Smartsheet report might even suffice. But if the audience lives in Google Workspace, the above methods will bridge Smartsheet to Google Docs effectively.

Conclusion

Bringing multiple Smartsheet trackers into one workspace is a foundational step to better manage projects – it centralizes resources and simplifies sharing. Each project tracker can be paired with sub-sheets (like action logs) for detailed tracking, either kept separate per project or consolidated in a master log, depending on your workflow. Smartsheet’s automation capabilities then ensure nothing falls through the cracks by sending timely reminders to owners about upcoming or overdue action items. Finally, while Smartsheet excels at tracking internally, you have options to push or pull that data into Google Docs for reporting or collaboration outside of Smartsheet. Using the Smartsheet for Google Docs add-on or integration tools like Zapier/Make, you can automate the extraction of action items into documents, saving time and reducing manual effort.

By following these structured steps and best practices, you’ll set up a robust system where project information is organized, actionable, and easily shareable, leveraging the strengths of Smartsheet’s native features alongside the flexibility of external integrations. Good luck with your setup, and enjoy a more streamlined project tracking experience!

7 Powerful Features of Perplexity That Set It Apart

7 Powerful Features of Perplexity That Set It Apart

Watch video HERE

In the ever-evolving landscape of artificial intelligence tools, Perplexity stands out as a versatile and powerful platform that can enhance productivity, streamline research, and foster innovation. Here, we outline seven compelling features of Perplexity that make it a must-have tool for anyone looking to harness the power of AI effectively.

NOTE: Some of these features require the Pro version but many are available from the free version.

1. Multi-Model Access

One of the standout features of Perplexity is its ability to provide access to multiple AI models. Unlike other platforms that restrict users to a single model, Perplexity allows you to choose from a variety of top AI large language models (LLMs), including its own Sonar fast model, Claude, ChatGPT 4.1, Gemini 2.5 Pro, and Grok 3.0. This flexibility means you can select the best model for your specific needs, whether it’s for writing, coding, or research.

2. Automatic Model Selection

Perplexity takes the guesswork out of choosing the right model for each task. With its "best model" feature, the platform automatically selects the most suitable AI model based on your query. This means you can focus on your work without worrying about which tool to use, saving both time and money by consolidating multiple subscriptions into one.

3. Comprehensive Source Selection

The platform's sources button allows users to customize where their information is sourced from. You can toggle between web searches, academic papers, social discussions, and SEC filings. This feature enables you to conduct targeted research, ensuring that you gather the most relevant and credible information for your projects.

4. Deep Research Functionality

Perplexity excels in deep research capabilities, allowing users to ask complex questions and receive detailed answers. You can specify the sources you want to include in your research, making it easy to gather insights from specific areas, such as social media or academic literature. This feature is particularly useful for entrepreneurs and researchers looking to validate ideas or identify market gaps.

5. AI-Powered Project Development

The platform includes a unique "labs" feature that enables users to collaborate with AI agents to develop business plans, brand identities, and even minimum viable product (MVP) features. By inputting your ideas, Perplexity can generate comprehensive project outlines, market opportunities, and competitive analyses, streamlining the process of bringing your concepts to life.

6. Image Generation Capabilities

Perplexity integrates image generation directly into its platform, allowing users to create visuals alongside their text-based queries. This feature is particularly beneficial for content creators and marketers who need to produce graphics quickly and efficiently. The ability to generate images in conjunction with text makes Perplexity a comprehensive tool for various creative projects.

7. Custom Spaces and Automation

The "spaces" feature allows users to create custom projects tailored to their specific needs. You can add instructions, files, and links to provide context for your AI interactions. Furthermore, Perplexity offers automation capabilities, enabling users to set up tasks that deliver relevant content at scheduled times. This feature is ideal for keeping track of trends and ensuring that you receive timely updates on topics of interest.

Conclusion

Perplexity is more than just an AI tool; it’s a comprehensive platform designed to enhance productivity and streamline research. With its multi-model access, automatic model selection, and deep research capabilities, it empowers users to tackle complex projects with ease. Whether you’re an entrepreneur, researcher, or content creator, the powerful features of Perplexity can help you achieve your goals more efficiently. Embrace the future of AI with Perplexity and unlock your full potential today!