Zachman Owner Row: Current State Business Operations Explained

The Owner row (Row 2) is the second perspective in the Zachman Framework matrix. It represents the business owner's perspective - the current state, how the business actually operates today. If Row 1 is "where do we want to go?", Row 2 is "where are we now?"

The Owner row is characterised by:

Current state focus: How the business operates today
Business owner's view: Understandable by operational staff, not just architects
Process-oriented: Detailed workflows, RACI matrices, business rules
Medium-term horizon: 1-2 years (subject to near-term change)
Tangible: Real processes, real people, real data flows

This row is critical for understanding the baseline before you can plan changes (Row 1 to Row 6).

What Does the Owner Row Cover?

The Owner row addresses all six interrogatives, from a business owner's perspective:

Interrogative	Owner (Row 2)	Example
What	Entity-relationship model (business view)	"Customers have many accounts; accounts have transactions"
How	Business process model (workflows)	Order-to-cash process with steps and decision points
Where	Operational geography	Primary data centre in New Jersey, DR in Virginia
Who	Organisational structure & RACI	Sales owns lead generation, Finance owns billing
When	Operational schedule	Orders cut off at 4:30 PM for next-day processing
Why	Business model & policies	"We charge per user per month; discounts limited to 20%"

The Six Columns in the Owner Row

Column 1: Owner/What - Entity-Relationship Model (Business View)

Question: How do business entities relate to each other?

Artefacts:

ER diagram with business entities (not technical)
Entity definitions with business attributes
Relationships and cardinalities
Business rules governing relationships

Characteristics:

5-15 pages including diagrams
Understandable by business stakeholders
Reflects current business model

Example:

text

Entities:

Customer: Person/organisation who buys from us
  - Attributes: Name, Email, Phone, Address, Segment (SMB/Mid-Market)
  - Lifecycle: Active, Inactive, Suspended

Account: Billing account (customer may have multiple)
  - Attributes: Account ID, Type (Monthly/Annual), Balance
  - Relationship: Customer has 1+ Accounts

Transaction: Payment or charge
  - Attributes: Amount, Date, Type (Payment/Charge), Status
  - Relationship: Account has 1+ Transactions

Relationships:
  - Customer --1:M--> Account (customer has many accounts)
  - Account --1:M--> Transaction (account has many transactions)

Business Rules:
  - A customer can have 0-unlimited accounts
  - An account must have at least 1 transaction within 12 months
  - A customer's accounts must all be in the same currency

Why: Ensures business stakeholders and IT agree on what data matters and how it relates.

Column 2: Owner/How - Business Process Model

Question: How does the business operate? What workflows exist?

Artefacts:

Business process diagrams (flowcharts, BPMN, swim lanes)
Narrative descriptions of key processes
Decision points and business rules
Actors and their roles in each process

Characteristics:

5-20 pages with diagrams and narratives
Understandable by operational staff
Reflects how things actually happen (not how they should happen)

Example (Order-to-Cash Process):

text

Order-to-Cash Process:

1. Sales rep receives customer request
2. Sales rep creates quote in sales system
3. Customer reviews and approves quote
4. Sales rep submits order
   - Business rule: Orders >$10k require manager approval
   - If requires approval:
     a. Manager reviews (usually within 24 hours)
     b. If approved → Continue; If rejected → Notify customer
5. Order submitted to Operations
6. Operations checks inventory
   - If available: Continue to step 7
   - If unavailable: Contact customer (backorder or cancel?)
7. Operations picks order from warehouse
8. Operations packs and labels shipment
9. Operations ships order (UPS, FedEx, DHL based on destination)
10. Customer receives tracking number
11. Finance department generates invoice
12. Finance sends invoice to customer
13. Customer pays (check, credit card, ACH, wire)
14. Finance receives payment
15. Finance records revenue (GAAP accounting rules apply)
16. Order marked as complete

Actors Involved:
  - Sales: Sales rep, Sales manager
  - Operations: Warehouse staff, Shipping coordinator
  - Finance: Billing specialist, Accountant
  - Customer: Buyer, Accounts payable

Decision Points:
  - Order amount >$10k? (approval gate)
  - Inventory available? (backorder decision)
  - Payment method? (different processing paths)

Timing:
  - Total time: 10-15 business days
  - Peak season: Can take 30+ days due to backlog

Why: Documents how business actually works so IT can design systems that support it.

Column 3: Owner/Where - Operational Geography

Question: Where are business operations located?

Artefacts:

Map showing offices, factories, warehouses, data centres
Connectivity between locations
Data residency requirements

Characteristics:

Simple map and description
Shows primary and backup locations
Identifies regional operations

Example:

text

Primary Operations:

Headquarters: New York, USA
  - Sales, Marketing, Finance, HR
  - Primary data centre (production systems)

Manufacturing Facilities:
  - US: Texas plant (primary), North Carolina (overflow)
  - International: Shanghai (China), Mexico City (Latin America)

Distribution:
  - East Coast warehouse: New Jersey
  - West Coast warehouse: Los Angeles
  - EU warehouse: Netherlands (Beneluxa hub)

Backup Infrastructure:
  - Disaster recovery data centre: Virginia, USA
  - EU data replica: Frankfurt, Germany (GDPR requirement)
  - APAC data replica: Tokyo, Japan

Regional Offices:
  - Sales: London (Europe), Singapore (APAC), São Paulo (LATAM)
  - Customer support: US, Europe, India (24/7 coverage)

Why: Identifies infrastructure constraints (e.g., GDPR requires EU data to stay in EU).

Column 4: Owner/Who - Organisational Structure & RACI

Question: Who owns what processes and decisions?

Artefacts:

Organisational chart (departments, reporting relationships)
RACI matrix (who's Responsible, Accountable, Consulted, Informed)
Department descriptions and headcounts

Characteristics:

5-10 pages including organisational chart
Shows reporting relationships
Clarifies accountability

Example RACI for Order-to-Cash:

text

              Sales    Ops    Finance   IT    Customer
Place order    A       -        -       -       R
Check inv      -       R        C       -       -
Pick/pack      -       R        C       -       -
Ship           -       A        C       -       -
Create inv     -       C        R       -       -
Process pmt    C       -        A       R       -
Revenue rec    I       -        A       -       -
Support issue  I       R        I       A       -

R = Responsible (does the work)
A = Accountable (final approval)
C = Consulted (provides input)
I = Informed (kept in loop)

Organisational structure:

text

Chief Operating Officer
  ├─ VP Sales (12 people)
  │   ├─ Sales Manager (5 reps)
  │   ├─ Sales Manager (5 reps)
  │   └─ Sales Operations Manager
  │
  ├─ VP Operations (45 people)
  │   ├─ Manufacturing Manager (20)
  │   ├─ Logistics Manager (15)
  │   └─ Quality Manager (10)
  │
  └─ VP Finance (18 people)
      ├─ Controller (accounting staff)
      ├─ Finance Manager
      └─ Billing Specialist

Why: Clarifies who makes decisions and who's accountable.

Column 5: Owner/When - Operational Schedule

Question: When do key business processes occur?

Artefacts:

Daily/weekly/monthly operational schedule
Peak periods and seasonality
Batch job schedules (nightly close, monthly reconciliation)
Maintenance windows

Characteristics:

Simple schedule
Shows timing and frequency of key processes

Example:

text

Daily Schedule:

08:00 - Sales team starts (order intake begins)
16:30 - Order cutoff (for next-day processing)
17:00 - Nightly batch begins
  - Orders picked from warehouse
  - Invoices generated
  - Payment processing
  - Data backup
22:00 - Nightly batch complete
23:00 - System ready for next day

Weekly:

Monday 06:00 - Full system backup (weekly)
Wednesday 14:00 - System maintenance window (2 hours)
Friday 17:00 - Weekly close processing
Friday 23:00 - Week-end archiving

Monthly:

1st of month: Payroll processed
5th: Accounts receivable aging review
Last day: Month-end financial close
First Friday: Executive reporting

Seasonal:

Q4 (Oct-Dec): Peak sales season
  - Order volume: 3x normal
  - Staff: Temporary hires for warehouse and customer support
  - Extended hours: Weekend processing

January: Post-holiday slowdown
  - Annual planning activities
  - System upgrades and maintenance
  - Training and team meetings

Why: Ensures IT understands when processes must run and prepares for peak capacity.

Column 6: Owner/Why - Business Model & Policies

Question: Why does the business operate this way? What are the business rules and policies?

Artefacts:

Business model (customer segments, revenue model, unit economics)
Pricing policy
Product/service policies (SLAs, warranties, returns)
Compliance requirements

Characteristics:

5-10 pages
Captures current business model and policies
Reflects actual practice (not wishful thinking)

Example:

text

Business Model:

Customer Segments:
  - Small/medium businesses (10-500 employees)
  - Geographic: North America, Europe, APAC

Pricing Model:
  - Monthly subscription: $99-$999/month (based on user count)
  - Annual subscription: 20% discount (customer pays upfront)
  - Implementation: $5,000-$50,000 one-time

Revenue Breakdown:
  - 70% recurring SaaS revenue
  - 20% implementation services
  - 10% professional services

Unit Economics:
  - CAC (Customer Acquisition Cost): $500 average
  - LTV (Lifetime Value): $12,000 average
  - Payback period: 2 months
  - Net revenue retention: 120%

Policies:

Payment Terms:
  - Monthly subscriptions: Monthly autopay (credit card only)
  - Annual subscriptions: Upfront payment (no refunds)
  - Payment methods: Credit card, ACH, wire transfer
  - Failed payment: Retry daily for 5 days, then suspend

Customer Support:
  - Free support included in subscription
  - SLA: 4-hour response time for critical issues
  - Support channels: Email, chat, phone
  - Hours: 24/7 (US, Europe, India coverage)

Compliance & Policies:
  - Data retention: 90 days after cancellation, then delete
  - GDPR: Mandatory for EU customers
  - SOC 2 Type II: Certification required
  - Data backup: Daily encrypted backups, replicated to disaster recovery

Why: Ensures IT understands the business rules that must be enforced in systems.

Current State Assessment

The Owner row is critical for understanding the current baseline:

What data do we have? (Column 1)
How do we currently operate? (Column 2)
Where are our operations? (Column 3)
Who does what? (Column 4)
When do things happen? (Column 5)
Why do we operate this way? (Column 6)

This baseline enables gap analysis: "Row 2 (current) vs. Row 1 (desired)" identifies what must change.

Owner Row in Practice

In a real enterprise architecture initiative:

Elicitation: Interview business owners, observe processes, document current state.
Validation: Get business owner sign-off: "Is this how we actually operate?"
Gap analysis: Compare Row 2 (current) to Row 1 (desired). Identify gaps.
Roadmap: Create phased plan to bridge gaps (transformation roadmap).
Design: Rows 3-6 describe desired future state and how to get there.

Owner Row vs. Designer Row

This is important to understand:

Owner (Row 2): "Here's how we currently operate" (as-is)
Designer (Row 3): "Here's what the system should do" (to-be, system-independent)

Row 2 describes current reality (often messy, manual, inconsistent). Row 3 describes the new system requirements (clean, well-defined, consistent).

Common Mistakes in the Owner Row

Describing wishful future instead of current reality: "If we could do X..." Instead, describe what's actually happening now.
Being too detailed: Row 2 should show important processes, not every step. That's Row 3.
Missing the messy reality: "Sales enters orders in Excel, Finance manually transfers to accounting system" - don't hide this. It's important.
No RACI: Leaving accountability unclear. Define who's responsible for what.
Ignoring compliance and policies: These are constraints on how IT designs Row 3.

Owner Row Best Practices

Document current reality, not desires: What's actually happening, not what should happen.
Include stakeholder interviews: Talk to salespeople, warehouse staff, finance team. They know the reality.
Create clear RACI: Ensure accountability is explicit.
Identify pain points: Where's the current process broken? This becomes the change case.
Validate with business owners: Get sign-off that this is accurate before moving to Row 3.

Example: Owner Row for E-commerce Platform

text

Current State (Owner Row):

What:
  - Customers, Orders, Products, Payments, Returns tracked in 3 separate systems
  - Data inconsistency issues (customer email different in each system)
  - Manual reconciliation weekly (error-prone)

How:
  - Sales: Manual quote tool (Excel), email to customer
  - Orders: Manual entry by sales into legacy system
  - Fulfillment: Warehouse picks from inventory (manual barcode scans)
  - Billing: Finance manually creates invoices (10+ days after shipment)
  - Payment: Customers send checks or wire transfers (slow, manual entry)

Where:
  - Headquarters: New York
  - Warehouse: New Jersey
  - Finance: outsourced to India (time zone challenges)

Who:
  - Sales: 5 people (create quotes and orders)
  - Warehouse: 8 people (pick, pack, ship)
  - Finance: 3 people in India (invoicing, collections)

When:
  - Order cutoff: 3 PM daily
  - Fulfillment: 24-48 hours after order
  - Invoicing: 10+ days after shipment
  - Collections: Manual follow-up (inefficient)

Why:
  - Business model: B2B e-commerce, 70% SaaS, 30% services
  - Revenue: $2M/year (target: $50M)
  - Constraint: Limited budget (bootstrapped, can't spend big)

Pain Points Identified:
  - 3x data entry (customer enters, sales enters, finance enters)
  - Slow billing (10+ days, customers complain)
  - Lost payments (check arrives, can't match to customer for days)
  - No visibility into pipeline or financial health

Key Takeaways

Owner row is current state baseline: How the business operates today.
It should describe reality, not aspirations: Document actual processes, even if messy.
RACI and accountability are critical: Clear who owns what decisions.
Gap analysis (Row 2 vs. Row 1) drives transformation: Identify needed changes.
Business owner sign-off is essential: "Is this accurate?" before proceeding to Row 3.

Next Steps

Explore Designer Row (Row 3) to see system requirements based on current state gaps.
Read Gap Analysis for how to bridge current (Row 2) and desired (Row 1) states.
Jump to Complete Matrix to see all perspectives together.

The Owner row is the foundation for understanding what needs to change. Master it, and you ensure transformation roadmap is grounded in reality.

Meta Keywords: Zachman Owner row, current state, business operations, business model, RACI matrix, process mapping.