.do
Enterprises

Organizational Design

Designing organizations for the Business-as-Code era

Traditional org structures were designed for manual work and human decision-making. Business-as-Code enables new organizational models optimized for speed, scale, and efficiency.

Traditional Structures

Functional Organization

Structure: Group by function (Sales, Marketing, Engineering, etc.)

Advantages:

  • Clear specialization
  • Efficient resource use
  • Centralized expertise

Disadvantages:

  • Silos and handoffs
  • Slow cross-functional work
  • Limited accountability

Automation Opportunity: Moderate - can automate within functions, but handoffs remain

Divisional Organization

Structure: Group by product, geography, or customer

Advantages:

  • Clear P&L ownership
  • Customer focus
  • Faster decision-making

Disadvantages:

  • Duplicated functions
  • Higher costs
  • Inconsistent processes

Automation Opportunity: High - each division can automate independently

Matrix Organization

Structure: Dual reporting (function + division)

Advantages:

  • Flexible resource allocation
  • Balanced perspectives
  • Shared expertise

Disadvantages:

  • Unclear accountability
  • Decision paralysis
  • High coordination overhead

Automation Opportunity: Low - complexity makes automation difficult

Business-as-Code Structures

Process-Centric Organization

Structure: Organize around end-to-end processes

Key Characteristics:

  • Process owners have full accountability
  • Cross-functional teams
  • Agent-augmented execution
  • Measured on outcomes

Example:

Order-to-Cash Team
├── Process Owner (1 human)
├── Sales Agents (AI)
├── Finance Agents (AI)
├── Operations Agents (AI)
└── Customer Success Agents (AI)

Advantages:

  • Clear accountability
  • No handoffs
  • Optimized end-to-end
  • Fully automated execution

Platform Organization

Structure: Core platform team + capability teams

Key Characteristics:

  • Platform provides foundation
  • Capability teams build on platform
  • Self-service for common needs
  • Centralized intelligence

Example:

Platform
├── Core Infrastructure
├── Data & AI Services
├── Integration Layer
└── Business Primitives

Capability Teams
├── Customer Acquisition
├── Product Delivery
├── Customer Success
└── Finance Operations

Advantages:

  • Scalable architecture
  • Consistent standards
  • Rapid capability development
  • Shared learnings

Agent-Native Organization

Structure: Humans as orchestrators, agents as workforce

Key Characteristics:

  • Minimal human headcount
  • Agents handle execution
  • Humans focus on strategy and exceptions
  • Continuous optimization

Example:

Enterprise (100 employees, 10,000 agents)
├── Executive Team (5 humans)
│   └── Strategy Agents
├── Operations (20 humans, 3,000 agents)
│   ├── Sales Agents
│   ├── Marketing Agents
│   └── Support Agents
├── Product (30 humans, 5,000 agents)
│   ├── Engineering Agents
│   ├── Design Agents
│   └── QA Agents
├── Finance (10 humans, 1,000 agents)
│   ├── Accounting Agents
│   └── FP&A Agents
└── Platform (35 humans, 1,000 agents)
    ├── Infrastructure Agents
    └── Data Agents

Advantages:

  • Extreme scalability
  • Low marginal cost
  • 24/7 operation
  • Rapid experimentation

Design Principles

Minimize Handoffs

Every handoff adds:

  • Latency
  • Error potential
  • Coordination overhead
  • Loss of context

Solution: Give teams/agents end-to-end ownership

Maximize Autonomy

Autonomous units can:

  • Move faster
  • Innovate more
  • Adapt quicker
  • Scale independently

Solution: Clear interfaces, minimal dependencies

Optimize for Learning

Organizations that learn faster win:

  • Capture all data
  • Measure everything
  • Experiment continuously
  • Share learnings

Solution: Built-in analytics and optimization

Design for Scale

Assume 10x-100x growth:

  • No human bottlenecks
  • Automated decision-making
  • Self-service where possible
  • Elastic resources

Solution: Agent-native architecture

Transformation Path

Phase 1: Automate Within

Keep current structure, automate tasks:

  • Each function automates its work
  • Handoffs remain manual
  • Humans still orchestrate
  • Gradual headcount optimization

Timeline: 6-12 months Headcount Impact: 20-30% reduction

Phase 2: Eliminate Handoffs

Restructure around processes:

  • Create end-to-end teams
  • Automate entire workflows
  • Reduce coordination overhead
  • Humans focus on exceptions

Timeline: 12-18 months Headcount Impact: 40-60% reduction

Phase 3: Agent-Native

Rebuild as agent-first organization:

  • Agents handle execution
  • Humans do strategy and oversight
  • Continuous optimization
  • Extreme scalability

Timeline: 18-36 months Headcount Impact: 70-90% reduction

Organizational Metrics

Traditional Metrics

  • Headcount
  • Span of control
  • Layers of management
  • Departmental budgets

Business-as-Code Metrics

  • Process cycle time
  • Automation rate
  • Agent:human ratio
  • Cost per transaction
  • Time to market
  • Customer satisfaction
  • Revenue per employee

Change Management

Communication

  • Clear vision and rationale
  • Transparency about impact
  • Regular updates
  • Two-way dialogue

Training

  • Upskill existing employees
  • Focus on high-value work
  • Agent collaboration skills
  • Continuous learning culture

Support

  • Career path clarity
  • Transition assistance
  • Mental health resources
  • Celebration of wins

Next Steps