---
reference_type: Principle
reference_id: P07
name: Tailor Based on Context
version: "1.0.0"
status: Deprecated
edition: PMBOK7
pmbok8_source: "PMBOK8 Standard §3.7 — Tailor Based on Context"
authority: PMI-derived
---

# P07 — Tailor Based on Context
**Type:** Principle
**PMBOK8 Source:** PMBOK8 Standard §3.7 — Tailor Based on Context
**Version:** 1.0.0

## Definition
Tailoring, as defined in PMBOK 8 Standard §3.7, is the deliberate adaptation of the project approach — including processes, methods, templates, tools, and governance structures — to fit the unique context of each project. No single methodology or process framework is appropriate for all situations. The tailoring practitioner evaluates project characteristics (size, complexity, novelty, strategic importance, team capability, regulatory environment, stakeholder needs, and delivery cadence) and makes conscious choices about what to apply, what to modify, and what to omit. Both over-application and under-application of standards are recognized as risks. Tailoring is not a one-time decision at project initiation — it is an ongoing, reflective practice.

## Key Characteristics
- **Context-driven selection:** Every tailoring decision flows from an honest assessment of project context, including organizational culture, industry constraints, team maturity, and risk profile (§3.7).
- **Proportionality:** Governance and documentation effort must be proportionate to the project's size, strategic significance, and complexity — heavier governance for complex, high-risk work; lighter governance for routine, low-risk work (§3.7).
- **Ongoing reassessment:** Tailoring is not finalized at project start; as context evolves (scope changes, team changes, regulatory updates), the approach is revisited and adapted (§3.7).
- **Value orientation:** The purpose of tailoring is to increase the likelihood of value delivery — processes are selected or omitted based on whether they add value in the given context, not because they appear in a standard (§3.7).
- **Integration with delivery approach:** Tailoring determines the appropriate balance between predictive, iterative, incremental, agile, and hybrid delivery models for the specific project (§3.7).
- **Organizational enablement:** Effective tailoring requires organizational permission and support — governance bodies, PMOs, and sponsors enable or constrain the practitioner's ability to tailor (§3.7).

## Relationship to Other Principles
| Principle | Relationship |
|---|---|
| P05 — Systems Thinking | Tailoring requires understanding the project as a system within a broader organizational and environmental context; systems thinking informs what contextual factors matter for tailoring decisions (§3.5, §3.7) |
| P04 — Focus on Value | Tailoring serves value — the selection of methods and processes is justified by whether they contribute to value delivery in the given context (§3.4, §3.7) |
| P11 — Embrace Adaptability and Resiliency | Tailoring is a foundational expression of adaptability; choosing adaptive or hybrid delivery approaches is a key tailoring output (§3.7, §3.11) |
| P09 — Navigate Complexity | Complex project contexts demand more sophisticated tailoring choices — simplistic, template-driven approaches are insufficient when complexity is high (§3.7, §3.9) |

## Artifact Connections
| Artifact | Connection |
|---|---|
| A06 — Tailoring Decision Record | Primary artifact for this principle; documents the rationale, decisions, and contextual factors that drove each tailoring choice on the project |
| A05 — Context Register | Supplies the primary inputs to tailoring — stakeholder landscape, organizational environment, delivery constraints, regulatory requirements, and team characteristics |
| A14 — Integrated Project Management Plan | The IPMP reflects the tailored approach in practice; it is the output of applying tailoring across planning processes |
| A35 — Governance Record | Documents the tailored governance model, including which review gates, decision rights, and oversight mechanisms apply to this specific project |

## Skill Connections
| Skill ID | Skill Name | Connection |
|---|---|---|
| SKL-03-02 | Develop Project Management Plan | The first major application of tailoring — the IPMP is built by selecting and adapting the planning components appropriate for the project context |
| SKL-03-17 | Tailor the Approach | The dedicated skill for this principle; involves structured assessment of context, selection of delivery model, and documentation of tailoring rationale |
| SKL-05-01 | Monitor and Control Project Work | Ongoing monitoring creates the feedback that triggers reassessment of the tailored approach when project conditions change |

## Questions to Ask in Practice
1. What are the key contextual factors (size, complexity, risk, regulatory constraints, team maturity) that should shape the project approach — and how have they been documented?
2. Is the current level of process and governance documentation proportionate to the project's actual complexity and strategic significance, or are we applying more formality than the situation warrants?
3. Have we reviewed the delivery approach (predictive, hybrid, agile) against the nature of requirements — are requirements stable and known, or do they need iterative discovery?
4. What is the organization's governance appetite, and have we obtained explicit permission to tailor standard processes where deviation is warranted?
5. When project conditions change significantly, do we have a process to revisit and update the tailored approach, rather than continuing to execute a plan that no longer fits?

*Authority: PMBOK8 Standard §3.7 — Tailor Based on Context · Source type: PMI-derived*
*Repository: https://github.com/fakhruldeen/PMOSkills*
