Structure

Structure

Overview

Structure in digital transformation refers to how organizations arrange their teams, reporting relationships, and governance mechanisms to support transformation initiatives. The right organizational structure enables effective communication, resource allocation, and decision-making during process transformation.

ELI5

Structure is like deciding how to organize your lemonade stand crew:

Pure Project Structure = Dedicated team

• Everyone works ONLY on lemonade stand
• You report to the lemonade boss
• Like a pit crew — only one job!

Functional Structure = Everyone stays in their department

• Squeeze lemons in lemon dept
• Count money in finance dept
• A coordinator talks between them
• Like a school — math teacher, English teacher, etc.

Matrix Structure = Two bosses!

• You report to lemonade boss AND finance boss
• Like having a homeroom teacher AND subject teachers

Work Breakdown Structure (WBS) = Breaking big job into small tasks

• “Run lemonade stand” → too big!
• Break down: Buy lemons → Squeeze → Mix → Sell → Count money
• Each small task is easier to manage!

Memory: “WBS = What Breaks down Scope”

Core Concept

Structure determines how work is organized, who reports to whom, and how decisions are made during transformation. Key structural considerations include:

Centralized vs. Decentralized:

• Centralized structures provide consistency and economies of scale
• Decentralized structures enable faster local decisions and flexibility

Cross-functional Integration:

• Breaking down silos is essential for end-to-end process transformation
• Teams must span traditional functional boundaries

Governance Layers:

• Steering committees set strategic direction
• Project sponsors provide resources and remove obstacles
• Execution teams implement changes

Components / Framework

Structural Element	Description	Source
Pure Project Structure	Team members dedicated solely to project; report to project manager	Chapter4.pptx [Slide 6]
Functional Project Structure	Team members remain in functional departments; project coordinator liaises across functions	Chapter4.pptx [Slide 6]
Matrix Structure	Hybrid approach; team members report to both functional manager and project manager	Chapter4.pptx [Slide 6]
Work Breakdown Structure (WBS)	Hierarchical decomposition of project scope into manageable work packages	Chapter4.pptx [Slide 10-13]
Organize Around Outcomes	Combine specialized tasks into single job; eliminates handoffs	MGH_book.pdf [p.685]
Treat Dispersed Resources as Centralized	Use IT to link geographically separate units while maintaining flexibility	MGH_book.pdf [p.685]
Decision Point at Work Location	Put decision-making where work is performed; build controls into process	MGH_book.pdf [p.686]

Example

From Slides:

• Project management structure showing hierarchy with milestones and work packages [Chapter4.pptx, Slide 11-13]
• WBS example demonstrating how major deliverables break into subtasks and work packages [Chapter4.pptx, Slide 12]

Real-World Examples:

• Digital Transformation Office (DTO): Centralized structure coordinating all transformation initiatives, typically reporting to CEO or COO
• Spotify’s Agile Squad Model: Autonomous squads, tribes, chapters, and guilds enable rapid iteration while maintaining coordination
• Matrix in Banking: IT staff report to both CIO (functional) and transformation program manager (project)
• Case Worker Model: Single employee handles entire customer process from start to finish, eliminating handoffs [MGH_book.pdf, p.685]

Implications

For Organizations:

• Wrong structure creates bottlenecks, delays, and communication breakdowns
• Matrix structures require strong conflict resolution mechanisms due to dual reporting
• Pure project structures are faster but more expensive due to dedicated resources

For Transformation Success:

• Structure must align with transformation scope and complexity
• Cross-functional teams essential for end-to-end process redesign
• High executive involvement improves reengineering outcomes [MGH_book.pdf, p.686]

Trade-offs:

• Centralization = efficiency but slower response
• Decentralization = faster response but potential inconsistency
• Matrix = best of both but requires strong coordination

Related Concepts

• Business Process Reengineering (BPR): Radical restructuring requiring new organizational structures [MGH_book.pdf, p.685]
• Business Process Transformation (BPT): 8-step methodology requiring structural alignment [Ops - Workshop Deck, Slide 2-3]
• Organizational Change Management: Cultural and behavioral aspects of restructuring
• Governance Models: Decision rights, accountability frameworks, escalation paths

Quick Summary

Structure = Who does what + Who reports to whom + How decisions are made

Key Points:

• Pure Project = dedicated team, single boss
• Functional = stay in departments, coordinator liaises
• Matrix = two bosses (functional + project)
• WBS = hierarchical task breakdown (“What Breaks down Scope”)
• Organize around outcomes, not tasks [MGH_book.pdf, p.685]
• Put decision point where work is performed [MGH_book.pdf, p.686]

Exam Tips:

• WBS questions ask about task hierarchy and work packages
• Matrix structure = dual reporting (common exam topic)
• Pure project = fastest but most expensive
• Functional = cheapest but slowest due to coordination needs

Sources

• Chapter4.pptx [Slide 6, 10-13]
• Ops - Workshop Deck.pptx
• MGH_book.pdf [p.685-686]