Zachman Planner Row: Strategic Scope and Executive Vision Explained

Zachman Planner Row: Strategic Scope and Executive Vision Explained

The Planner row (Row 1) is the first perspective in the Zachman Framework matrix. It represents the executive planner's perspective - the strategic, long-range view of the enterprise. If Rows 2-6 answer "how do we build it?", Row 1 answers "why are we building it and what's the scope?"

The Planner row is characterised by:

• Scope-focused: Defines what's in-scope vs. out-of-scope
• Strategic horizon: Long-term view (3-5 years or more)
• Executive vocabulary: Business terms only, no technical jargon
• Stable: Rarely changes month-to-month (strategies typically persist for years)
• Abstract: High-level; focuses on "what" and "why", not "how"

This row is often overlooked, but it's critical: poor scoping at Row 1 leads to massive waste downstream (building features nobody wanted, optimising for wrong metrics).

What Does the Planner Row Cover?

The Planner row addresses all six interrogatives, but at the strategic, scoping level:

The Six Columns in the Planner Row

Column 1: Planner/What - Entity Scope List

Question: What entities and objects does the business deal with?

Artefacts:

• Simple entity list (one or two pages)
• Brief one-sentence description of each entity
• Scope boundaries

Example:

Entities:
1. Customer: A person or organisation who purchases products
2. Order: A request from a customer to purchase products
3. Product: An item we sell
4. Account: A billing account associated with a customer
5. Invoice: A bill sent to a customer
6. Employee: A person who works for us
7. Supplier: A company from which we purchase inventory
8. Inventory: Products held in our warehouses

Why: Establishes shared language across business and IT. Everyone must agree on what "customer," "order," "product" mean.

Column 2: Planner/How - Function List

Question: What high-level functions does the business perform?

Artefacts:

• High-level function list (one to two pages)
• Brief description of each function
• Which functions are core vs. support

Example:

Core Functions:
1. Sales  -  Generate leads, quote customers, process orders
2. Operations  -  Manufacture products, manage inventory, fulfil orders
3. Finance  -  Account for transactions, report results, manage cash

Support Functions:
4. HR  -  Recruit, manage compensation, train employees
5. IT  -  Manage systems, support users, ensure security
6. Marketing  -  Create campaigns, generate brand awareness

Why: Clarifies "what business are we in?" and separates core from support.

Column 3: Planner/Where - Geographic Scope

Question: Where does the enterprise operate geographically?

Artefacts:

• World map showing business locations
• Geographic footprint description
• In-scope vs. out-of-scope regions

Example:

Global Presence:

Headquarters: New York, USA
Regional Offices: London (Europe), Singapore (APAC), São Paulo (LATAM)

Customer Base:
  - In-scope: 45 countries across 6 continents
  - Out-of-scope: Iran, North Korea, Syria (sanctions)

Manufacturing:
  - In-scope: US, UK, China, Mexico, Poland
  - Out-of-scope: Countries with high political risk

Support Operations:
  - 24/7 coverage: US, Europe, Asia-Pacific

Why: Identifies geographic constraints (GDPR in EU, shipping limitations, tax implications).

Column 4: Planner/Who - Organisational Scope

Question: What organisational units and stakeholders matter?

Artefacts:

• High-level organisational chart (C-suite, major departments)
• Key external stakeholders (board, customers, regulators)
• Governance bodies

Example:

Organisational Scope:

Executive Leadership:
  - CEO, COO, CFO, CTO, Chief Commercial Officer

Major Departments:
  - Sales & Marketing
  - Operations
  - Finance
  - HR
  - IT & Technology

External Stakeholders:
  - Board of Directors
  - Major customers (top 10 accounts)
  - Key suppliers
  - Regulatory bodies (SEC, EPA)

Why: Identifies whose buy-in is needed and who makes decisions.

Column 5: Planner/When - Business Calendar

Question: When do key business events occur?

Artefacts:

• Annual business calendar
• Recurring events (board meetings, quarterly business reviews)
• Peak periods and seasonality
• External deadlines (tax filings, regulatory reports)

Example:

Business Calendar:

Annual Rhythm:
  - Q1: Financial planning, budget season
  - Q2: Mid-year review, new product launches
  - Q3: Strategic planning, market analysis
  - Q4: Peak sales season, year-end close

Key Events:
  - Monthly: Board meeting (1st Friday)
  - Quarterly: Earnings announcement (within 45 days of quarter end)
  - Annually: Strategic offsite (September), Annual conference (June)

Regulatory Deadlines:
  - April 15: Tax filings (US)
  - June 15: Estimated quarterly taxes (US)
  - Quarterly: SEC 10-Q filings (if public)

Why: Identifies busy seasons, planning cycles, and timing constraints.

Column 6: Planner/Why - Strategic Objectives

Question: Why does the enterprise exist and what does it want to achieve?

Artefacts:

• Mission statement
• Vision statement (3-5 year target)
• Strategic objectives (SMART goals)
• Competitive positioning

Example:

Strategic Intent:

Mission:
  "Provide affordable, high-quality SaaS tools enabling SMBs to compete."

Vision (2030):
  "Become the #1 cloud platform for companies with 10-500 employees."

Strategic Objectives (5-year):
  1. Achieve $100M annual recurring revenue (ARR)
  2. Expand to 15 new international markets
  3. Build 500+ partner ecosystem
  4. Achieve 95%+ customer satisfaction
  5. Become carbon-neutral

Competitive Positioning:
  - Differentiation: Best user experience, lowest TCO
  - Target: SMB segment (underserved)
  - Advantage: Fast implementation, excellent support

Why: Ensures all downstream architecture aligns with business strategy.

Common Planner Row Outputs

1. Scope statement: "In-scope: Customers in 45 countries. Out-of-scope: Custom development, on-premises deployment."

2. High-level entity list: ~20-50 major entities the business tracks.

3. Function decomposition: ~10-20 major business functions.

4. Stakeholder map: Who has interest, who makes decisions.

5. Strategic goals: 3-5 major objectives for the next planning period.

6. Business model canvas: Customer segments, value propositions, revenue model.

Role of the Planner in Practice

In a real enterprise architecture initiative:

1. Kickoff: Executive steering committee (CEO, CFO, CTO) defines Planner row scope.
2. Alignment: Business and IT agree on entity list, function list, stakeholders.
3. Validation: TOGAF/Zachman team reviews Row 1 for completeness and realism.
4. Cascade: Row 1 outputs become inputs to Rows 2-6 (Owner, Designer, Builder, etc.).
5. Review: Annual or multi-year review of strategic objectives; adjust if needed.

The Planner row is the "north star." Downstream work should constantly reference it: "Does this architecture support our strategic objectives?"

Planner Row vs. Other Rows

• Planner vs. Owner: Planner is "what business do we want to be?" Owner is "how do we currently operate?"
• Planner vs. Designer: Planner is "strategic scope" Designer is "system requirements from scope."
• Planner vs. Builder: Planner is "why?" Builder is "how do we implement?"
• Planner vs. Sub-Contractor: Planner is "vision" Sub-Contractor is "executable code."
• Planner vs. Enterprise: Planner is "intended" Enterprise is "actual" (often different!).

Common Mistakes in the Planner Row

1. Scope creep: "We'll do everything for everyone" → No scope boundaries. Result: Unfocused, diluted efforts.

2. No strategic objectives: Defining scope but not objectives. Result: Nobody knows what success looks like.

3. Too detailed: Getting into technical minutiae in Row 1. Result: Confuses business stakeholders, looks like it belongs in Row 3 or 4.

4. Ignoring stakeholders: Not identifying key decision-makers. Result: Wrong people in the room, decisions made without necessary buy-in.

5. Stale plans: Defining in Year 1, never revisiting. Result: Architecture pursues outdated objectives.

Planner Row Best Practices

1. Get executive alignment first: Don't proceed to Row 2 until CEO, CFO, CTO agree on Row 1.

2. Make it measurable: Strategic objectives should be SMART (Specific, Measurable, Achievable, Relevant, Time-bound).

3. Revisit annually: Even if strategy doesn't change, validate that we're still pursuing it.

4. Use for prioritisation: When evaluating new initiatives, ask "Does this support our Row 1 strategic objectives?"

5. Be realistic about scope: Ambitious is good; delusional is not. Scope should be achievable in 3-5 years.

Example: Planner Row for E-commerce Platform

In-Scope:
  - Direct-to-consumer e-commerce (not B2B)
  - US and Canada only (not international initially)
  - Mobile and web channels
  - Products and subscriptions (not services)
  - 3 major integrations: Shopify, BigCommerce, WooCommerce

Out-of-Scope:
  - International (EU, APAC)  -  considered for Year 3+
  - Custom development  -  each platform handles their own
  - On-premises deployment  -  cloud-only
  - Business-to-business (B2B) channels

Strategic Objectives:
  1. Achieve $50M ARR by 2028 (growing from current $8M)
  2. Serve 2,000+ merchant customers (growing from 400)
  3. Process $10B in annual transaction volume
  4. Build to 500+ integrated partners/plugins
  5. Achieve NPS >50 (currently 38)

Key Success Metrics:
  - Net revenue retention: >130% (expansion revenue / existing revenue)
  - Customer acquisition cost (CAC): <$500
  - Lifetime value (LTV): >$50,000
  - LTV/CAC ratio: >100x
  - Monthly churn: &lt;%

Key Takeaways

1. Planner row is about strategic scope and vision: Defines what the enterprise wants to become.

2. It's the "north star" for downstream work: Rows 2-6 should constantly reference Row 1 to ensure alignment.

3. Executive alignment is critical: If C-level doesn't agree on Row 1, downstream efforts will be chaotic.

4. Measurable objectives are essential: "Become the best" is meaningless; "Achieve 95% customer satisfaction" is clear.

5. Revisit annually: Markets change, strategy evolves; re-validate annually.

Next Steps

• Explore Owner Row (Row 2) to see current state business operations.
• Read Strategic Alignment for how to link Planner row to business strategy.
• Jump to Complete Matrix to see all perspectives together.

The Planner row is where enterprise architecture begins. Master it, and you ensure all downstream architecture decisions support business success.

Meta Keywords: Zachman Planner row, strategic scope, business vision, executive perspective, enterprise architecture, strategic objectives.