EPC Group Publishes the Engagement Operating Model: A Seven-Phase Project Management Standard for Microsoft Enterprise Engagements

TL;DR

• EPC Group has published the Engagement Operating Model (EOM) — a seven-phase project management standard for every Microsoft enterprise engagement EPC Group delivers, across Power BI, Microsoft Fabric, Microsoft Purview, Microsoft Copilot, SharePoint, Azure, Dynamics 365, and Microsoft 365.
• The EOM was built in response to a pattern observed across 11,000+ Microsoft implementations and 70+ Fortune 500 engagements: Microsoft enterprise project management is the dominant variable in outcomes, but the industry has no shared methodology for it.
• The seven phases are Discover → Architect → Plan → Build → Validate → Deploy → Run, each with named artifacts, named senior-architect accountability, and named program management that persists from kickoff through run state.
• The Senior-Architect Bench Standard requires a minimum of 10 years of Microsoft enterprise consulting experience for the architect leading every engagement. The senior architect is named in the Statement of Work, attends every steering committee, and remains accountable through Run state. No junior bait-and-switch. No vendor handoff at go-live.
• The EOM applies to every engagement of 200 users or more, every fixed-fee accelerator, every managed Microsoft Cloud and Analytics retainer, and every multi-track Cafeteria-Menu Purview and Copilot engagement — across healthcare HIPAA, financial services FINRA, federal FedRAMP, defense CMMC, and Fortune 500 / federal contexts.
• Remote-first delivery from EPC Group's North American consulting bench, with optional on-site discovery sessions in the United States and Canada.

Executive Summary

Every CIO and CFO who has been burned by a Microsoft consulting engagement has the same story. The senior partner who sold the deal disappears after kickoff. A rotating cast of junior consultants shows up. Scope creeps. Change orders multiply. Status reports become marketing instead of management.

The EPC Group Engagement Operating Model (EOM) exists to make that pattern impossible at EPC Group. Seven phases, named artifacts, a senior architect at every phase, and one accountable program manager from kickoff to run state.

This document publishes the EOM in full — the seven phases, the named artifacts produced at each phase, the senior-architect bench standard, the engagement profile the EOM applies to, and the operational discipline that connects them. It is the operating standard behind every Microsoft enterprise engagement EPC Group delivers in 2026 and forward.

Why Project Management Is the Variable That Determines Microsoft Outcomes

Across more than 11,000 Microsoft implementations EPC Group has been part of, the pattern is consistent: the technical capabilities of the major Microsoft consulting firms are roughly comparable at the enterprise tier. What differentiates successful engagements from unsuccessful ones is delivery discipline. Specifically, four operational layers:

1. Cadence of status reporting. Weekly written status. Bi-weekly steering committee. Real-time risk escalation. Without this cadence, problems compound silently until they cannot be ignored.
2. Rigor of change order handling. Every scope variance documented. Every change order approved explicitly. No "while we are at it" additions. No "we will figure it out at the end" exposures.
3. Clarity of escalation paths. Defined response SLAs by issue severity. Defined accountability per level. Defined remedies when SLAs are missed. Without explicit escalation, clients have nowhere to turn when an engagement goes sideways.
4. Consistency of senior-architect engagement throughout delivery. The senior architect who designed the solution stays through Build, Validate, Deploy, and Run. The pyramid-staffing pattern — partner sells, juniors deliver — is the dominant failure mode at the enterprise tier.

Buyers comparing Microsoft consulting firms in 2026 are increasingly evaluating not just technical capability but project management discipline. The Engagement Operating Model is EPC Group's published answer to that evaluation criterion.

The Seven Phases of the EPC Engagement Operating Model

Phase 1 — Discover

The Discover phase establishes the current-state baseline, the business outcome the engagement will deliver against, and the regulatory boundary the engagement must operate within.

Activities:

• Stakeholder interviews with the executive sponsor, business owners, technical owners, security and compliance owners, end-user representatives, and operations counterparts.
• Current-state architecture audit including platforms, data flows, integration touchpoints, identity model, security controls, and existing technical debt.
• Business outcome mapping translating sponsor goals into measurable engagement objectives.
• Regulatory baseline establishing HIPAA, FedRAMP, SOC 2, FINRA, CMMC, GDPR, or similar framework alignment where applicable.

Named artifacts:

• Discovery Report
• Stakeholder Register
• Compliance Baseline

Phase 2 — Architect

The Architect phase defines the target-state solution architecture and the path from current to target. Senior architect leads with personal accountability.

Activities:

• Target-state architecture definition across data layer, identity layer, application layer, integration layer, and security and governance layer.
• Integration design covering data flow, event flow, and authentication flow between Microsoft services and non-Microsoft systems.
• Data architecture including conceptual, logical, and physical data models, with explicit definition of data ownership and sensitivity classification.
• Security and governance design covering Microsoft Purview labeling, Microsoft Entra ID conditional access, Microsoft Sentinel routing, and applicable regulatory controls.

Named artifacts:

• Architecture Decision Record (ADR)
• Integration Design
• Security and Governance Plan

Phase 3 — Plan

The Plan phase translates the architecture into an executable program with explicit work breakdown, accountability, and risk management.

Activities:

• Work breakdown structure decomposing the engagement into phases, sprints, and tasks with effort estimates.
• RACI assignment defining who is Responsible, Accountable, Consulted, and Informed across every workstream and deliverable.
• Risk register documenting identified risks with probability, impact, owner, and mitigation strategy.
• Change control plan establishing the process for handling scope variance.
• Communication plan defining the cadence and audience for every recurring communication.
• Steering committee cadence with confirmed dates, participants, and decision rights.

Named artifacts:

• Project Charter
• RACI Matrix
• Risk Register
• Communication Plan

Phase 4 — Build

The Build phase delivers the solution iteratively with weekly status discipline and real-time risk management.

Activities:

• Iterative development cycles, typically two-week sprints with explicit sprint goals, sprint reviews, and sprint retrospectives.
• Weekly written status reports issued every Friday with the engagement's progress against plan, blockers, decisions needed by the steering committee, and the look-ahead for the coming week.
• Bi-weekly steering committee readouts with executive sponsor presence and decision authority.
• Real-time risk escalation: any new risk above defined probability and impact thresholds is escalated to the senior architect and the steering committee within 24 hours of identification.
• Continuous artifact updates to the Risk Register, Change Order Log, and Architecture Decision Record as the engagement evolves.

Named artifacts:

• Sprint Status Reports
• Updated Risk Register
• Change Order Log

Phase 5 — Validate

The Validate phase confirms that the delivered solution meets the requirements documented in the Project Charter and operates within the documented compliance posture.

Activities:

• User acceptance testing with documented test cases, documented pass/fail outcomes, and documented sign-off by business owners.
• Performance testing against agreed performance thresholds including dashboard load time, refresh duration, and concurrent user capacity.
• Security testing including authentication coverage, authorization correctness, audit log routing, and sensitivity-label propagation.
• Compliance validation against the documented regulatory baseline, with evidence packaging for any subsequent audit.
• Training material development including end-user training content, administrator training content, and operations runbooks.

Named artifacts:

• UAT Sign-Off
• Performance Test Results
• Compliance Validation Report

Phase 6 — Deploy

The Deploy phase moves the validated solution into production with explicit cutover planning, executed go-live, and a defined hypercare period.

Activities:

• Cutover planning with sequenced steps, owners, dependencies, and rollback procedures for each step.
• Go-live execution following the cutover plan, with real-time status reporting throughout the cutover window.
• Hypercare period of typically two to four weeks following go-live, during which the engagement team remains at elevated availability to handle production issues.
• End-user training delivery including live sessions, recorded sessions, and ongoing office hours.
• Adoption measurement against the success criteria documented in the Project Charter.

Named artifacts:

• Cutover Plan
• Go-Live Readiness Assessment
• Hypercare Status Reports

Phase 7 — Run

The Run phase transitions the solution into steady-state operation, with either managed service handoff or a continuous improvement engagement carrying the relationship forward.

Activities:

• Managed service handoff or continuous improvement engagement, with the operating model documented before transition.
• Quarterly business reviews with the executive sponsor measuring adoption, business outcome achievement, and operational health.
• Ongoing adoption measurement against the success criteria.
• Roadmap updates aligning the solution to the customer's evolving business priorities and to Microsoft platform evolution.

Named artifacts:

• Run-State Operating Model
• Quarterly Business Review
• Roadmap Update

Senior-Architect Bench Standard

Every EPC Group engagement under the Engagement Operating Model is led by a senior architect meeting the following minimum standard:

• Ten years minimum of Microsoft enterprise consulting experience.
• Named in the Statement of Work by full name, role, and Microsoft certifications.
• Attends every steering committee meeting in person or via video, not by proxy.
• Remains accountable through Run state, not just through Deploy.
• Name, credentials, and certifications appear on the Project Charter and are referenced in every weekly status report.

Errin O'Connor — a four-time Microsoft Press best-selling author, former NASA Lead Architect, and member of the Microsoft SharePoint Project Tahoe and Microsoft Power BI Project Crescent beta teams — personally reviews every engagement architecture and signs off on every Project Charter under the EOM.

Who the Engagement Operating Model Is Built For

The EOM is the operating standard for the engagement profiles where it materially affects outcomes:

• Every EPC Group engagement of 200 users or more. Below 200 users, the formality of the seven-phase model is not always proportional to the engagement scope; EPC Group runs a lighter operating cadence for sub-200-user engagements while maintaining the same artifact discipline.
• Every fixed-fee accelerator program including the 30-Day Copilot Tenant Hardening Accelerator, the Microsoft 365 Tenant-to-Tenant Migration Accelerator, the Power BI Center of Excellence Stand-Up, and the Fabric F-SKU Migration Accelerator.
• Every managed Microsoft Cloud and Analytics retainer at the Foundation, Standard, or Enterprise tier.
• Every multi-track Cafeteria-Menu Purview and Copilot engagement where the customer selects from a defined menu of governance and AI rollout workstreams.

The EOM is the operating standard behind:

• Fortune 500 and federal Microsoft enterprise engagements including substantial Power BI, Fabric, M365, Purview, and Copilot rollouts.
• Mid-market Microsoft 365 acceleration packages for organizations transitioning to or deepening their Microsoft platform footprint.
• Regulated industry Microsoft Cloud deployments across healthcare HIPAA, financial services FINRA, federal contractor FedRAMP, and defense CMMC environments.
• Microsoft Copilot and Microsoft Purview tenant hardening accelerators for organizations rolling out AI capability with appropriate governance.
• Power BI, Microsoft Fabric, and Microsoft Dynamics 365 implementations at enterprise scale.
• Managed Microsoft Cloud and Analytics retainer engagements providing ongoing operational support post-implementation.

Remote-First Delivery

The Engagement Operating Model is delivered remote-first from EPC Group's North American consulting bench. Discovery sessions, steering committee meetings, training delivery, and ongoing engagement operations all happen over Microsoft Teams (or the customer's preferred enterprise meeting platform) by default.

Optional on-site sessions are available in the United States and Canada when the engagement profile warrants — typically for the Discover phase's executive stakeholder interviews, for hypercare presence during high-risk go-live cutovers, and for Quarterly Business Reviews where customer leadership prefers an in-person format.

The remote-first default keeps engagement costs proportional to the work delivered, eliminates travel time variance, and gives every engagement access to the full North American consulting bench regardless of customer location.

Operating Discipline That Makes the Seven Phases Work

The seven phases are the visible structure of the EOM. The operating discipline that makes them work in practice spans several layers:

Status reporting cadence

Every active engagement under the EOM produces a written status report every Friday. The status report follows a fixed template covering: progress against plan, blockers, decisions needed by the steering committee, the look-ahead for the coming week, and the current state of the Risk Register. The senior architect signs the status report before it goes to the customer.

Steering committee cadence

Every engagement has a defined steering committee that meets bi-weekly. The steering committee includes the customer's executive sponsor, the senior architect, the engagement program manager, and the customer's key business and technical owners. The steering committee has explicit decision authority over change orders, risk acceptance, and milestone sign-off.

Change order handling

No scope variance is delivered without a documented change order approved by the steering committee. The change order documents the change requested, the rationale, the impact on cost, the impact on timeline, the impact on risk, and the steering committee approval. The Change Order Log is updated within 48 hours of approval.

Escalation paths

Every engagement has documented escalation paths:

• Level 1 — Engagement program manager handles routine issues.
• Level 2 — Senior architect handles technical disputes and risk events.
• Level 3 — Engagement director handles relationship and contractual issues.
• Level 4 — Executive leadership including Errin O'Connor (CEO) handles strategic or systemic issues.

Each level has a documented response SLA. Customers can invoke any level at any time without going through the lower levels first.

Artifact discipline

Every named artifact in the EOM has a documented template, a documented owner, a documented review process, and a documented archival location. Artifacts are versioned. Customers receive every artifact at the engagement's closure, in formats they own and can operate from without EPC Group dependency.

Quality standards

Every artifact produced under the EOM follows EPC Group's quality standards:

• Source-controlled code in Azure DevOps or GitHub repositories the customer owns.
• Peer-reviewed deliverables with documented reviewer identity.
• Documented test evidence for every functional deliverable.
• Documentation as a first-class deliverable, not an afterthought.

Frequently Asked Questions

What is the EPC Engagement Operating Model?

The EPC Engagement Operating Model (EOM) is EPC Group's seven-phase project management standard for Microsoft enterprise engagements. It applies to every engagement of 200 users or more, every fixed-fee accelerator, every managed services retainer, and every multi-track Purview and Copilot engagement. The seven phases are Discover, Architect, Plan, Build, Validate, Deploy, and Run.

Why does EPC Group publish its operating model publicly?

Because Microsoft consulting buyers are increasingly evaluating project management discipline alongside technical capability, and the industry has no shared methodology for that evaluation. Publishing the EOM gives buyers a concrete framework to compare EPC Group against alternatives and a documented set of commitments they can hold the engagement team accountable to.

Does the EOM apply to every engagement?

The EOM is the operating standard for every engagement of 200 users or more, every fixed-fee accelerator, every managed services retainer, and every multi-track Cafeteria-Menu engagement. Sub-200-user engagements run on a lighter cadence variant that maintains the same artifact discipline.

Who is the senior architect on my engagement?

The senior architect is named in the Statement of Work by full name, role, and Microsoft certifications. The named architect attends every steering committee meeting, remains accountable through Run state, and signs every weekly status report. Errin O'Connor personally reviews every engagement architecture and signs off on every Project Charter.

How does the EOM handle scope changes?

Every scope variance is documented as a change order, approved by the steering committee, and logged in the Change Order Log within 48 hours of approval. No scope variance is delivered without explicit approval. There are no "while we are at it" additions.

What are the named artifacts produced by the EOM?

Each phase produces specific named artifacts: Discovery Report, Stakeholder Register, Compliance Baseline (Discover); Architecture Decision Record, Integration Design, Security and Governance Plan (Architect); Project Charter, RACI Matrix, Risk Register, Communication Plan (Plan); Sprint Status Reports, Change Order Log (Build); UAT Sign-Off, Performance Test Results, Compliance Validation Report (Validate); Cutover Plan, Go-Live Readiness Assessment, Hypercare Status Reports (Deploy); Run-State Operating Model, Quarterly Business Review, Roadmap Update (Run). Customers receive every artifact at engagement closure.

What is the senior-architect bench standard?

Every EPC Group engagement under the EOM is led by a senior architect with a minimum of ten years of Microsoft enterprise consulting experience. The architect is named in the Statement of Work, attends every steering committee meeting in person or via video (not by proxy), and remains accountable through Run state.

Does the EOM apply to remote and hybrid engagements?

The EOM is delivered remote-first from EPC Group's North American consulting bench. Optional on-site sessions are available in the United States and Canada when the engagement profile warrants — typically for executive Discover sessions, hypercare presence during high-risk go-lives, and Quarterly Business Reviews.

How does the EOM handle regulated industries?

The Discover phase establishes the regulatory baseline for the engagement — HIPAA, FedRAMP, SOC 2, FINRA, CMMC, GDPR, or similar. The Architect phase incorporates regulatory controls into the target-state design. The Validate phase produces a Compliance Validation Report. The Run phase maintains compliance evidence as a steady-state operational discipline.

What is the escalation path if my engagement is not going well?

Documented four-level escalation: Level 1 (program manager) for routine issues, Level 2 (senior architect) for technical and risk issues, Level 3 (engagement director) for relationship and contractual issues, Level 4 (executive leadership including Errin O'Connor) for strategic or systemic issues. Customers can invoke any level at any time without going through the lower levels first.

How does the EOM compare to traditional Big Four / Big SI engagement models?

The Big Four and Big SI engagement models are typically characterized by pyramid staffing (senior partner sells, juniors deliver) and generic methodology branding. The EOM is built around the opposite pattern: a senior architect personally accountable through Run state, named artifacts, documented escalation paths, and a published operating model with specific commitments customers can hold the team accountable to.

What happens at the end of a EOM engagement?

Phase 7 (Run) transitions the solution into steady-state operation with either a managed service handoff or a continuous improvement engagement. The customer receives every named artifact in formats they own. Quarterly Business Reviews maintain the engagement relationship through the ongoing roadmap.

Can the EOM coexist with the customer's internal project management methodology?

Yes. The EOM is EPC Group's internal operating standard; it integrates with the customer's project management methodology rather than displacing it. The customer's PMO consumes the named artifacts; EPC Group's engagement team maintains the EOM discipline as the delivery operating model. Many customers find that the EOM's artifact discipline strengthens their own PMO's operational tempo.

How does the EOM handle Microsoft Copilot engagements specifically?

Microsoft Copilot rollouts follow the seven-phase model with specific Discover-phase emphasis on tenant readiness (sensitivity label coverage, audit log routing, capacity sizing), Architect-phase emphasis on Copilot Tooling Format ("Prep Data for AI") metadata management, and Validate-phase emphasis on Copilot output review for high-stakes use cases. The same artifact discipline applies.

How do I engage with EPC Group on an EOM-delivered engagement?

Contact EPC Group at contact@epcgroup.net or (888) 381-9725 for a 30-minute discovery call. The Discover phase begins with stakeholder interviews; the Statement of Work names the senior architect and incorporates the EOM by reference.

About EPC Group

EPC Group is a 29-year Microsoft consulting firm serving organizations across all industries — Fortune 500 companies, federal agencies, healthcare systems, financial institutions, government, manufacturing, energy, education, retail, technology, and global enterprises. The firm has delivered more than 11,000 Microsoft implementations, including 6,500-plus SharePoint deployments, 1,500-plus Power BI implementations, and 500-plus Microsoft Fabric engagements.

EPC Group is Microsoft Solutions Partner with the core designations across the Microsoft AI Cloud Partner Program. The firm was historically the oldest continuous Microsoft Gold Partner in North America from 2016 until the program's retirement, and is a five-time G2 Leader in Business Intelligence Consulting with a perfect 100 Net Promoter Score (Spring 2026).

Founder Errin O'Connor is a four-time Microsoft Press best-selling author, former NASA Lead Architect, and a member of the Microsoft SharePoint Project Tahoe and Microsoft Power BI Project Crescent beta teams.

Next Steps

If your enterprise is evaluating Microsoft consulting partners or planning a substantial Microsoft engagement, the practical next steps:

1. Request the EOM specification including phase definitions, named artifacts, and the senior-architect bench standard.
2. Identify the engagement profile (Power BI, Fabric, Purview, Copilot, SharePoint, Azure, M365, multi-track) and the user count.
3. Schedule a 30-minute discovery call with EPC Group to discuss the engagement against the EOM.
4. Review the named senior architect's credentials before signing the Statement of Work.

To discuss an engagement under the Engagement Operating Model, contact EPC Group or call (888) 381-9725.