💼 Monday Business

How I'm Integrating Sustainability into IT Project Management (My 2026 Goals)

February 23, 2026

Three professional development goals for 2026: AI-driven PMO efficiency, GPM P5™ implementation on live IT projects, and a pilot to prove sustainable practices reduce costs and cycle time.

Why This Matters

Sustainability in project management is not about planting trees or buying carbon offsets. It’s about eliminating waste—wasted time, wasted resources, wasted budget, wasted effort. Every inefficient process, every redundant manual check, every over-provisioned resource is waste. Cutting that waste is good for the environment AND good for the bottom line.

I’ve spent years managing enterprise IT projects—through various contract and consulting roles, at Expedia, at Microsoft, and now at Kwik Trip. I’ve seen how much time gets burned on manual compliance checks, how much budget gets lost to inefficient resource allocation, and how much organizational energy gets wasted on processes that could be streamlined or automated. In 2026, I’m tackling that waste head-on with three professional development goals focused on sustainable project management practices.

This post documents my plan. I’ll report back throughout the year with real results, lessons learned, and templates you can use. Transparency matters—I’m not claiming I have all the answers. I’m documenting the journey from planning to implementation to results.

Here’s what I’m working on in 2026.

Goal 1: AI-Driven PMO Efficiency

The Goal: Develop a concept and prototype for an AI-driven solution that enhances PMO efficiency and governance. The solution will streamline compliance checks, improve data accuracy across project systems, and provide actionable insights to project managers for better decision-making. Deliver a phased implementation plan and demonstrate how AI can reduce manual effort and improve consistency in PMO processes.

The Problem I’m Solving

Every IT PMO I’ve worked in has the same bottlenecks:

  1. Manual compliance checks: Project managers spend hours verifying that project documentation meets governance standards, PMO requirements, and company controls (scope statements, risk registers, budget tracking, stakeholder lists, approval workflows). Most of this is checklist work—tedious, error-prone, and time-consuming.

  2. Data accuracy across systems: Project data lives in multiple places (project management tools, financial systems, time tracking, resource management). Keeping data consistent across systems requires manual reconciliation. When data doesn’t match, it takes hours to track down the source of truth.

  3. Insight extraction: Project managers are drowning in data but starved for insights. Dashboards show status, but they don’t answer questions like “Which projects are at risk based on historical patterns?” or “Where are we over-allocating resources?”

The AI Opportunity

AI—specifically large language models and pattern recognition—can address all three problems:

  • Automated compliance checks: AI can read project documentation and flag missing elements, inconsistencies, or incomplete sections. Instead of manually reviewing every project charter, the AI does the first pass and highlights what needs attention.

  • Data reconciliation: AI can compare data across systems, identify mismatches, and suggest corrections. It can also learn patterns (e.g., “When resource hours are entered in System A but not System B, 90% of the time it’s because the project code was mistyped”).

  • Actionable insights: AI can analyze historical project data to identify risk patterns, predict where bottlenecks will occur, and recommend interventions before problems escalate.

What Success Looks Like

By the end of 2026, I want to deliver:

  1. A working prototype using Copilot to automate data gathering for status reports, stakeholder registers, and potentially other project artifacts
  2. A phased implementation plan that shows how to scale the solution across the PMO
  3. Measurable impact: Reduction in manual effort (hours saved per project) and improvement in consistency (fewer compliance violations, fewer data errors)

I’m not aiming for perfection—I’m aiming for proof of concept. Can AI reduce the manual work that PMO teams currently do? If yes, what’s the ROI? What are the risks? What are the implementation challenges?

If projects are not completed by year-end, progress will be documented with lessons learned.

I’ll document the answers as I go.

Goal 2: M.O.R.E. (Integrating Sustainability into Live IT Projects)

The Goal: Lead 2 IT projects (e.g., Intune, AvePoint) to integrate sustainability using GPM P5™ or PMI templates. Apply standards in planning and execution, implement at least 2 sustainability actions per project (e.g., cut resource use by ≥10%, engage stakeholders on sustainability impact), include impact summary in all project closeouts, and share lessons learned to drive adoption.

Why GPM P5™?

GPM P5™ (Green Project Management P5 Standard for Sustainability in Project Management) is a framework developed by GPM Global that integrates sustainability principles into traditional project management. The “P5” stands for five impact areas:

  1. Product (what the project delivers)
  2. Process (how the project is executed)
  3. People (stakeholders, teams, communities)
  4. Planet (environmental impact)
  5. Prosperity (economic value and long-term viability)

Unlike environmental certifications that focus only on the planet, GPM P5™ recognizes that sustainability is about balancing all five dimensions. A project that reduces environmental impact but destroys team morale or blows the budget is not sustainable. A project that delivers on time and on budget but wastes resources or over-provisions infrastructure is not sustainable either.

For IT projects, GPM P5™ is particularly relevant because:

  • Process efficiency directly impacts cost and cycle time
  • Resource optimization (compute, storage, licenses) reduces waste and budget
  • Stakeholder engagement on sustainability builds organizational buy-in
  • Long-term viability matters more than short-term delivery (technical debt is a sustainability problem)

What I’m Testing

I’m leading two IT projects in 2026 (specific projects TBD, but likely involve Intune device management or a Data Loss Prevention (DLP) project). For each project, I’ll:

  1. Apply GPM P5™ or PMI sustainability templates during project planning (scope, schedule, budget, risk, stakeholder management)
  2. Implement at least 2 sustainability actions per project, such as:
    • Cut resource use by ≥10% (e.g., right-size cloud infrastructure, reduce over-provisioned licenses)
    • Engage stakeholders on sustainability impact (e.g., include sustainability metrics in status reports, discuss trade-offs in steering committee meetings)
    • Reduce technical debt or improve long-term maintainability
    • Optimize process efficiency (reduce cycle time, eliminate rework)
  3. Include impact summary in project closeouts, documenting:
    • What sustainability actions were taken
    • Measurable outcomes (resource reduction %, cost savings, time saved)
    • Lessons learned and recommendations for future projects
  4. Share lessons learned with the broader PMO to drive adoption

What Success Looks Like

By the end of 2026, I want to:

  1. Deliver 2 IT projects with documented sustainability integration
  2. Demonstrate measurable impact (≥10% resource reduction or equivalent)
  3. Create reusable templates that other PMs can apply to their projects
  4. Share lessons learned internally and externally (including blog posts throughout the year)

If projects are not completed by year-end, progress will be documented with lessons learned.

The goal is not to make sustainability a separate workstream—it’s to integrate it into existing project management practices so seamlessly that it becomes the default way of working.

Goal 3: Sustainable Practices Pilot (PMO Process Improvement)

The Goal: Lead a PMO pilot to improve IT project management efficiency. Select 1–2 key processes (e.g., intake, resource allocation), apply GPM P5™ principles, and track at least 2 outcomes (cycle time, cost, stakeholder satisfaction). Document results, share lessons learned, and present recommendations for broader adoption.

The Problem: PMO Processes Are Wasteful

Every PMO I’ve worked in has processes that burn time and effort without delivering proportional value. Two of the most common culprits:

  1. Project intake: The process of submitting, reviewing, and approving new project requests often involves multiple handoffs, unclear criteria, and long wait times. Projects sit in “pending approval” for weeks while stakeholders wait for decisions. The delay costs money (missed opportunities, delayed benefits) and frustrates everyone involved.

  2. Resource allocation: Assigning people to projects often involves manual coordination, over-allocation (people assigned to more work than they can handle), and poor visibility into capacity. The result: Projects start late, people burn out, and resource conflicts create bottlenecks.

Both problems are sustainability issues. Wasted time is wasted cost. Over-allocation burns people out (not sustainable for the team). Delayed projects mean delayed benefits (not sustainable for the business).

What I’m Testing

I’ll select 1–2 PMO processes (likely project intake and/or resource allocation) and apply GPM P5™ principles to improve efficiency. Specifically:

  1. Map the current state: Document how the process works today, identify bottlenecks, measure baseline performance (cycle time, cost, stakeholder satisfaction)
  2. Apply GPM P5™: Analyze the process through the P5 lens (Product, Process, People, Planet, Prosperity) to identify waste and improvement opportunities
  3. Pilot improvements: Implement changes on a small scale, track results, iterate based on feedback
  4. Measure outcomes: Track at least 2 metrics (e.g., cycle time reduction, cost savings, stakeholder satisfaction improvement)
  5. Document and share: Create before/after comparison, lessons learned, and recommendations for scaling

What Success Looks Like

By the end of 2026, I want to:

  1. Deliver measurable improvement in at least one PMO process (e.g., reduce project intake cycle time by 20%, improve resource allocation accuracy by 15%)
  2. Document the approach so other PMOs can replicate it
  3. Present recommendations for broader adoption across the IT PMO
  4. Share templates and tools that worked (or didn’t work)

If projects are not completed by year-end, progress will be documented with lessons learned.

The goal is to prove that sustainable practices aren’t just good for the environment—they’re good for efficiency, cost, and stakeholder satisfaction.

Why I’m Documenting This Publicly

Most professional development goals stay private. You set them in your annual review, work on them quietly, and report results to your manager at year-end. No one else sees the process—just the outcome.

I’m doing this differently. I’m documenting my goals, approach, and results publicly because:

  1. Accountability: Stating my intentions publicly creates pressure to follow through. If I say I’m going to integrate sustainability into 2 IT projects and then don’t, it’s visible. That’s a good thing—it keeps me honest.

  2. Transparency: I don’t have all the answers. I’m figuring this out as I go. Sharing the process—not just the results—helps others learn from my mistakes and adapt the approach to their context.

  3. Knowledge sharing: If I develop useful templates, tools, or insights, they’re more valuable when shared. Keeping them internal benefits one organization. Sharing them benefits everyone working on similar problems.

  4. Building credibility: I’m building a sustainability consulting business based on real experience. Documenting my work as I do it—with real results, real challenges, and real lessons learned—is more credible than writing about it years later with selective memory.

What I’ll Share Throughout 2026

As I work on these goals, I’ll share:

  • Planning documents and templates (e.g., GPM P5™ project charter template, sustainability impact summary template)
  • Progress updates (what’s working, what’s not, what I’m learning)
  • Real results (metrics, before/after comparisons, ROI calculations)
  • Lessons learned (what I’d do differently, what I’d replicate, what surprised me)
  • Tools and resources (AI prototypes, process maps, measurement frameworks)

This blog will be the primary channel for those updates. Look for Monday business posts tagged with #SustainablePM and #2026Goals.

How This Connects to My Broader Work

These goals aren’t separate from my sustainability consulting work—they’re the foundation of it.

I electrified our 1866 brick home with solar, geothermal, and EVs. I manage that project the same way I manage enterprise IT projects: Break it into phases. Sequence the work. Manage the vendors. Validate the results. A future Monday post—How I’d Project-Manage Your Zero-Emissions Home (coming soon)—will share that experience in detail.

Now I’m applying the same rigor to sustainability in organizational project management. The credibility comes from doing the work—not theorizing about it, not cherry-picking case studies from other companies, but actually implementing GPM P5™ on live IT projects and documenting what happens.

By the end of 2026, I’ll have:

  • Real data on whether AI can reduce PMO manual effort
  • Proof (or disproof) that GPM P5™ integration reduces resource waste by ≥10%
  • Before/after metrics on PMO process efficiency improvements

That’s not theory. That’s evidence.

The Bottom Line: Sustainability Is Efficiency

If you hear “sustainable project management” and think “tree-hugging compliance overhead,” you’re missing the point.

Sustainable project management is about eliminating waste:

  • Wasted time (inefficient processes, manual work that could be automated)
  • Wasted resources (over-provisioned infrastructure, unnecessary licenses, redundant work)
  • Wasted budget (projects that don’t deliver value, technical debt that costs more to fix later)
  • Wasted people (burnout from over-allocation, poor stakeholder engagement, lack of clarity)

Every IT PMO I’ve worked in has all four types of waste. In 2026, I’m tackling them systematically with AI, GPM P5™, and process improvement pilots. I’ll measure the results. I’ll document the lessons. I’ll share the templates.

And I’ll report back throughout the year with what actually works.

What’s Next

If you’re working on similar goals—integrating sustainability into IT projects, applying GPM P5™, using AI to improve PMO efficiency—I’d love to hear from you. What’s working? What’s not? What questions do you have?

Follow along in 2026 as I document the journey from planning to implementation to results. Look for:

  • February 2026: GPM P5™ Primer (What it is, why I’m using it, how it applies to IT projects)
  • Q1 2026: AI + PMO Prototype Update (Problem statement, concept, initial testing)
  • Q2 2026: First IT Project Update (Sustainability actions implemented, early results)
  • Q3 2026: PMO Process Pilot Results (Before/after metrics, lessons learned)
  • Q4 2026: Year-End Retrospective (What worked, what didn’t, what I’d do differently)

This is the start of a year-long experiment in sustainable project management. The results will be real, the lessons will be honest, and the templates will be shareable.

Let’s see what happens when you apply enterprise PM rigor to sustainability.

Professional development goals aren’t just checkboxes for annual reviews—they’re opportunities to test ideas, measure impact, and build knowledge that benefits everyone. In 2026, I’m making mine public.