# How Engineering Firms Lose Years Waiting for Principal Approval **By Dan Cumberland** · Published November 5, 2026 · Categories: AI Strategy ![Featured image for How Engineering Firms Lose Years Waiting for Principal Approval](https://cms.dancumberlandlabs.com/uploads/featured_image_8bdc4c232d.webp) Illustration: Dan Cumberland Labs with Gemini. > Your project manager came to you twice this week about the same scope change. She knows the answer. Your engineering firm organizational structure says she... Your project manager came to you twice this week about the same scope change\. She knows the answer\. Your engineering firm organizational structure says she still has to come to you\. That's how firms get stuck: not from a shortage of talent or clients, but from decision authority that never moved as the firm grew\. When a principal still approves every contract modification at 40 people, the firm runs like it did at 12\. The frustration surfaces on the floor before it surfaces in a strategy meeting\. Staff in practitioner forums describe it in almost identical terms across firm sizes and cities: "nobody is in charge of deciding\." The structure is broken, and leadership is the last to call it\. As Zweig Group research confirms[1](#ref-1), A/E firms rarely grow on a smooth curve— they hit distinct management breakpoints where the people, processes, and technology that once worked begin to break down\. Structure choice directly affects overhead costs, firm culture, and the ability to respond to market shifts[2](#ref-2)\. This article maps five structural models, three inflection points, and where decision authority sits in each— the question that determines whether the structure works at the firm's current size\. To understand why this keeps happening, start with where most engineering firms sit and how few ever move\. ## The Four Stages Where A/E Firms Get Stuck Zweig Group tracks four growth stages for A/E firms, and the numbers reveal the problem clearly: 65% of firms never leave Stage 1[1](#ref-1)\. Most engineering firms are still running the structure they started with\. ```html-table
StageEmployees% of FirmsStructure Demand
Stage 11–565%Founder-driven; no formal structure needed
Stage 25–2020%Informal teams; leadership managing operations
Stage 320–10010%Leadership specialization required
Stage 4100+5%Governance frameworks and enterprise analytics
``` The survival rate tells the real story\. Only 20% of A/E firms reach Stage 2, 10% reach Stage 3, and just 5% reach Stage 4[1](#ref-1)\. The barrier at each transition is the same thing in a different form: the structure that worked at the previous stage can't hold the volume at the next one\. Stage 1→2: The founder can't stop managing operations long enough to build a business\. Stage 2→3: Leadership specialization becomes non\-optional— the firm needs discipline heads who own their domains, not generalists who check every decision\. Stage 3→4: Governance frameworks become essential; ad hoc coordination that felt like efficiency is now a liability\. Crossing the chasm from Stage 2 to Stage 3 is where most firms lose years— not because growth stopped, but because the structure didn't follow\. As Zweig Group puts it[3](#ref-3), leadership must embrace strategic delegation, scalable systems, and the development of others— the hands\-on model of Stage 1 becomes a constraint rather than a strength\. For firms at Stage 4 managing enterprise\-level complexity, [AI governance becomes a priority in its own right](/blog/ai-governance-strategy) as decision structures multiply\. ## Five Structural Models— And Where Decision Authority Actually Sits Engineering firms use five primary organizational structures— horizontal, functional, matrix, studio, and market\-sector— and each places decision authority in different hands[2](#ref-2)\. The right choice depends on firm size and the complexity of the work\. **Horizontal \(Flat\)\.** Under 15–20 people, the principal makes most decisions directly[4](#ref-4)\. Decision\-making is fast, collaboration is natural, and there's no coordination overhead\. But principals become bottlenecks as the firm grows past that threshold— the structure that made them effective stops working the moment more than one project requires their attention simultaneously\. **Functional\.** Groups engineers by specialty— structural, MEP \(Mechanical, Electrical, Plumbing\), civil— with discipline heads controlling approval chains[5](#ref-5)\. This deepens departmental expertise but routes all cross\-functional decisions through formal management layers, slowing work that crosses department lines\. The tradeoff is technical quality against coordination speed\. **Matrix\.** Integrates a "two\-way flow of authority and responsibility of project managers \(horizontally\) and specialist engineer managers \(vertical\)"[6](#ref-6)\. Discipline heads own technical quality; project managers control budget, schedule, and day\-to\-day client communication[7](#ref-7)\. This maximizes resource deployment across projects but generates competing priorities without clear role design— the structure's strength and its most common failure mode are the same feature\. **Studio\.** Semi\-autonomous sub\-groups organized by project type, client, or principal leader[2](#ref-2)\. Develops specialized expertise and strong team culture but risks inconsistent standards across studios— each studio can drift from firm\-wide quality benchmarks if no one is watching the seams\. **Market\-sector\.** Organizes the firm around client types— healthcare, transportation, government, commercial— rather than engineering disciplines\. Sector leaders hold P&L accountability for their client groups\. This is where the largest AEC firms land \(more in the market\-sector section below\)\. The table below shows where authority actually sits in each model: ```html-table
StructureBest ForWho Approves Scope ChangesWho Controls BudgetKey Tradeoff
HorizontalFirms <20Principal directlyPrincipalSpeed vs. scalability
FunctionalFirms 20–50Discipline headsPrincipal/ownerQuality depth vs. slow cross-functional decisions
MatrixFirms 30–75PM (day-to-day) + Discipline Head (quality)PM for project budgetResource efficiency vs. conflicting priorities
StudioVaries by studio sizeStudio leaderStudio leaderSpecialization vs. inconsistent firm standards
Market-sectorFirms 100+Sector leaderSector leader (P&L)Growth alignment vs. implementation complexity
``` The diagram below shows how reporting lines and authority flows differ across the three most commonly compared structures: **Engineering Firm Structural Models: Decision Authority Flows** Three side-by-side diagrams comparing horizontal, functional, and matrix engineering firm structures, with authority flows shown by arrows and color coding. Dark blue boxes indicate decision-making authority holders; light blue boxes indicate staff. Orange arrows in the matrix panel show project manager budget authority crossing discipline lines. ## The Three Inflection Points That Force Structural Change AEC firms experience structural breaking points at three predictable sizes: around 20–30 employees, again at 50–75, and again at 75–100[8](#ref-8)\. At each threshold, informal coordination collapses and what replaced it in the previous stage isn't enough\. - **20–30 employees:** Informal coordination fails\. The first management layer becomes non\-optional— without it, the principal spends the majority of their time coordinating rather than doing technical work or business development\. This is where discipline heads earn their role for the first time\. - **50–75 employees:** Functional silos emerge\. Discipline heads start acting like fiefdoms\. Cross\-disciplinary project coordination becomes a source of project friction— and when a functional manager must run all decision\-making through a managerial bureaucracy, overall productivity suffers[9](#ref-9)\. - **75–100 employees:** The founder\-operator model fully breaks\. One person cannot hold all the client relationships, technical oversight, and business development threads simultaneously\. Executive team formation becomes essential— the only path through Stage 3[8](#ref-8)\. Connect these back to Zweig's data and the pattern becomes clear: the firms that never escape Stage 2 aren't lacking ambition\. They felt these breaking points and never responded structurally, attributing the friction to individual performance when the problem was structural design\. ## Principal\-in\-Charge vs\. Project Manager— The Role Split That Matters The principal\-in\-charge holds contractual authority and owns the client relationship\. The project manager controls the work plan, budget, and schedule[10](#ref-10)\. These roles only work when the authority transfer is real— not just a title change\. ```html-table
PIC ResponsibilitiesPM Responsibilities
Contractual signatoryWork plan oversight
Client relationship holderBudget control
Escalation point for disputesSchedule management
Technical quality sign-offDay-to-day client communication
Business developmentMargin protection
``` The common failure mode: firms create PM titles but principals still approve everything\. The PM has no authority to enforce decisions or protect margin— they're a project admin with a better name on the door[11](#ref-11)\. Most small firms hand one person both titles and only find out what that costs when an invoice goes out late[11](#ref-11)\. Span of control is part of this\. In most A/E firms, once a principal is managing more than six direct reports or four active projects, the PIC role becomes incompatible with real oversight— there's too much surface area for one person to cover[10](#ref-10)\. Firms navigating both transitions at once— restructuring AND building AI capacity— face the same span\-of\-control question at the AI leadership level\. The analysis of [where technical oversight should sit](/blog/fractional-ai-vs-cto) applies directly\. ## Market\-Sector Structure— The Proven Path for Scaling AEC Firms Market\-sector structure organizes the firm around client types— healthcare, transportation, government, commercial— rather than engineering disciplines\. Decision authority shifts to sector leaders accountable for specific client groups, which aligns how the firm is organized with how clients actually hire\. According to Zweig Group[12](#ref-12), clients predominantly hire AEC firms based on their experience working with other similar organizations\. That's the core logic: if buyers select by sector expertise, the firm should be organized by sector\. Structure follows buyer behavior, not internal discipline preference\. Carter & Burgess offers the clearest proof case\. According to Zweig Group's historical analysis[13](#ref-13), Carter & Burgess grew from 250 to 3,000\+ employees largely through implementing market\-sector structure in 1986, eventually becoming an acquisition target for Jacobs Engineering\. The growth wasn't accidental— the structural change created the accountability and market alignment that fueled it\. Three advantages stand out: - **Eliminates internal competition:** Prevents different offices or departments from bidding against each other on identical projects, protecting firm reputation and client relationships[12](#ref-12) - **Client alignment:** Sector leaders become genuine experts in their client type— how those clients buy, how their procurement cycles work, what matters in their sector - **Operational accountability:** Sector leaders hold P&L accountability for their client groups, which CSE Magazine[14](#ref-14) describes as typically providing "a better structure for the firm to grow in its existing markets, penetrate new markets, and instill operational accountability" The honest caveat: market\-sector structure requires critical mass of clients in each sector\. A 30\-person firm is still building toward that sector volume\. Zweig Group's four\-step transition path starts with minimal change and lightweight sector accountability, moves to a hybrid matrix with sector profit centers, and arrives at full client\-serving unit integration[15](#ref-15)\. This is a destination, not a starting point\. The same structural logic— that the right alignment creates velocity— applies to technology adoption, not just client growth\. ## How Organizational Structure Shapes Technology Adoption Here's the part most engineering firms discover too late: the same structure that creates a bottleneck at scope\-change approval creates an identical bottleneck at AI adoption decisions\. That's why technology initiatives in engineering firms stall at the same rate they stall everywhere else: when decision authority for the new tool is unclear, no one moves\. The pattern is consistent across structure types: - **Functional:** Every technology decision requires discipline\-head approval across multiple departments\. A new project management tool for the structural team needs the structural head's sign\-off; a scheduling tool for civil needs the civil head's sign\-off\. Adoption is slow and inconsistent because the approval chain was never designed for firm\-wide change\. - **Matrix:** Project managers can adopt tools for project delivery independently of discipline heads— faster at the project level, but no firm\-wide standard emerges without someone who owns the cross\-discipline decision\. The structure's dual\-authority design that works for client delivery creates an ambiguity gap for technology\. - **Market\-sector:** Sector leaders own technology decisions for their client groups, which means accountability is clear: if the healthcare sector adopts a tool and it doesn't deliver, that sector leader owns the outcome\. Adoption velocity is highest in market\-sector firms because the person closest to the client problem is also the person with authority to solve it\. When a firm redraws its org chart without shifting who actually owns the yes, the structure changes on paper and the authority\-vacuum stays exactly where it was\. This is the third structural layer most firms never build: a champion network— peer\-led adoption that sits beneath the formal org chart\. One champion per 15–25 employees, selected by peer respect, not seniority, and operating with 5–10% of their time[8](#ref-8)\. "Structure without the third layer is dead architecture[8](#ref-8)\." [Building that adoption culture inside an engineering firm](/blog/building-ai-culture) requires more than a mandate— it requires designated people whose job is to make the new thing work, not just to announce it\. Firms navigating both a structural evolution and an AI strategy benefit from outside perspective— an [AI strategy partner](/services/ai-strategy/) can map where your structure is constraining adoption and where it can accelerate it\. ## Warning Signs You've Outgrown Your Current Structure The firm usually knows first\. Leadership is the last to call it\. Staff describe it as "nobody is in charge of deciding"— a consistent signal from the authority\-vacuum problem that surfaces on practitioner forums long before it surfaces in a principals' meeting\. Eight warning signs worth checking against your own firm: 1. The principal approves every scope change regardless of size or dollar amount 2. Project managers cannot protect margin without escalating to ownership 3. Discipline departments compete for the same resources or bids 4. New hires can't get decisions in time to meet client deadlines 5. The firm wins work but can't deliver it without principal personal involvement 6. Culture is inconsistent across projects or offices— 69% of AEC firms report struggling to preserve cohesion through growth[3](#ref-3) 7. Technology tool adoption depends entirely on one person's enthusiasm 8. Turnover spikes at the associate and PM level— high performers leave when authority never reaches them[3](#ref-3) Any cluster of three or more signals a structural fit issue— the firm has outgrown the model it was built on\. These signals don't require a wholesale reorg\. But they do require an honest look at whether the structure matches the firm's current size— or the size it was three years ago\. Most firms that see the signs early find the structural fix smaller than they feared\. ## FAQ ### What are the main types of engineering firm organizational structures? Engineering firms use five primary structures: horizontal \(flat\), functional, matrix, studio, and market\-sector\. Each places decision authority at a different level and suits firms at different growth stages\. Horizontal works under 20 people; functional handles 20–50 with discipline\-based authority; matrix distributes authority between project managers and discipline heads for firms of 30–75; studio creates semi\-autonomous sub\-groups by project type; market\-sector organizes around client types and suits firms of 100 or more[4](#ref-4)[5](#ref-5)\. ### When should an engineering firm reorganize? The clearest signals appear at three employee thresholds: around 20–30 \(first management layer needed\), 50–75 \(functional silos emerge\), and 75–100 \(the founder\-operator model breaks\)[8](#ref-8)\. If the principal approves every scope change and project managers cannot protect budget, the firm has already passed a breaking point\. Structural change rarely feels urgent until it's overdue\. ### What is the difference between a matrix and functional structure? A functional structure groups engineers by specialty, with discipline heads controlling approval chains\. A matrix adds project manager authority running horizontally across those disciplines— PMs control budget and schedule while discipline heads control technical quality[5](#ref-5)[6](#ref-6)\. The tradeoff is resource efficiency versus conflicting priorities when roles aren't clearly defined\. Structures Insider describes it as "a two\-way flow of authority and responsibility"[6](#ref-6)— one that works when role boundaries are precise and breaks when they're not\. ### What is market\-sector structure? A market\-sector structure organizes the firm around client types— healthcare, transportation, government, commercial— rather than engineering disciplines\. Sector leaders hold P&L accountability for their client groups, aligning how the firm is organized with how clients actually hire[12](#ref-12)\. It's the proven model for scaling past 200\+ employees and the structure Carter & Burgess used to grow from 250 to 3,000\+[13](#ref-13)\. ### Who makes decisions in an engineering firm— the principal or project manager? It depends on the structure\. In a horizontal firm, the principal makes most decisions\. In a functional firm, discipline heads hold approval authority for their departments\. In a matrix, decision authority is split: PMs control day\-to\-day project decisions; principals retain contractual and client relationship authority[10](#ref-10)\. The most common dysfunction is a matrix or functional firm that calls project managers by title without actually transferring authority— which makes the PM a bottleneck's assistant, not a decision\-maker[11](#ref-11)\. ## Conclusion Engineering firm organizational structure is about where decisions sit, and whether the people closest to the work have the authority to make them\. Org charts describe reporting lines; structure determines who can say yes\. The stage\-to\-structure\-to\-decision\-authority alignment is what breaks at every growth inflection\. Your project manager came to you twice this week\. She has the capability\. The structure routes that decision back to you\. That's a solvable problem\. But it requires naming the structure first, then deciding whether it still fits\. If your firm is approaching one of these inflection points and you're not sure whether the structure is limiting your growth or your AI adoption, [working with a strategy partner](/services/ai-strategy/) can help clarify the path\. ## References 1. Zweig Group, "The Breakpoints That Shape Firm Growth" \(2024\)— [https://zweiggroup\.com/blogs/the\-zweig\-letter/growth\-breakpoints\-architecture\-engineering\-firms](https://zweiggroup.com/blogs/the-zweig-letter/growth-breakpoints-architecture-engineering-firms) 2. Open Exam Prep, "2\.2 Firm Organizational Models— ARE Practice Management Study Guide" \(2024\)— [https://open\-exam\-prep\.com/study\-guides/are\-pcm/practice\-management\-of\-the\-firm/firm\-organizational\-models](https://open-exam-prep.com/study-guides/are-pcm/practice-management-of-the-firm/firm-organizational-models) 3. Zweig Group, "Leadership Must Evolve with Scale" \(2024\)— [https://zweiggroup\.com/blogs/news/leadership\-must\-evolve\-with\-scale](https://zweiggroup.com/blogs/news/leadership-must-evolve-with-scale) 4. Open Exam Prep, "2\.2 Firm Organizational Models— ARE Practice Management Study Guide" \(2024\)— [https://open\-exam\-prep\.com/study\-guides/are\-pcm/practice\-management\-of\-the\-firm/firm\-organizational\-models](https://open-exam-prep.com/study-guides/are-pcm/practice-management-of-the-firm/firm-organizational-models) 5. Open Exam Prep, "2\.2 Firm Organizational Models— ARE Practice Management Study Guide" \(2024\)— [https://open\-exam\-prep\.com/study\-guides/are\-pcm/practice\-management\-of\-the\-firm/firm\-organizational\-models](https://open-exam-prep.com/study-guides/are-pcm/practice-management-of-the-firm/firm-organizational-models) 6. Structures Insider, "Functional vs Matrix Organization Structure in Engineering Firms" \(2024\)— [https://www\.structuresinsider\.com/post/functional\-vs\-matrix\-organization\-structure\-in\-engineering\-firms](https://www.structuresinsider.com/post/functional-vs-matrix-organization-structure-in-engineering-firms) 7. CSE Magazine, "Organization Structure: Beyond the Boxes" \(2024\)— [https://www\.csemag\.com/organization\-structure\-beyond\-the\-boxes/](https://www.csemag.com/organization-structure-beyond-the-boxes/) 8. Dan Cumberland Labs, "The Champion Network Design That Scales With AEC Firm Size" \(2024\)— [https://dancumberlandlabs\.com/blog/design\-firm\-architecture/](https://dancumberlandlabs.com/blog/design-firm-architecture/) 9. Arkansas State University, "Organizational Structure in Engineering" \(2024\)— [https://degree\.astate\.edu/articles/engineering/organizational\-structure\-in\-engineering\.aspx](https://degree.astate.edu/articles/engineering/organizational-structure-in-engineering.aspx) 10. PSMJ Resources, "Are You a Project Manager or Project Admin?" \(2024\)— [https://go\.psmj\.com/blog/are\-you\-a\-project\-manager\-or\-project\-admin](https://go.psmj.com/blog/are-you-a-project-manager-or-project-admin) 11. Monograph, "Project Manager vs Project Engineer: Key Differences in Roles and Responsibilities" \(2024\)— [https://monograph\.com/blog/project\-manager\-vs\-project\-engineer](https://monograph.com/blog/project-manager-vs-project-engineer) 12. Zweig Group, "Market Sector\-Based Organization Structures" \(2024\)— [https://zweiggroup\.com/blogs/the\-zweig\-letter/market\-sector\-based\-organization\-structures](https://zweiggroup.com/blogs/the-zweig-letter/market-sector-based-organization-structures) 13. Zweig Group, "Market Sector\-Based Organization Structures" \(2024\)— [https://zweiggroup\.com/blogs/the\-zweig\-letter/market\-sector\-based\-organization\-structures](https://zweiggroup.com/blogs/the-zweig-letter/market-sector-based-organization-structures) 14. CSE Magazine, "Organization Structure: Beyond the Boxes" \(2024\)— [https://www\.csemag\.com/organization\-structure\-beyond\-the\-boxes/](https://www.csemag.com/organization-structure-beyond-the-boxes/) 15. Zweig Group, "Client\-Driven Organization Structures" \(2024\)— [https://zweiggroup\.com/blogs/the\-zweig\-letter/client\-driven\-organization\-structures](https://zweiggroup.com/blogs/the-zweig-letter/client-driven-organization-structures) --- **How we made this article:** We use AI in our research and writing so our small team can share more of what we learn. We verify the sources and take responsibility for every article we publish. [Read how we use AI.](https://dancumberlandlabs.com/how-we-use-ai/) --- ## About the author **Dan Cumberland** — Founder, Dan Cumberland Labs Dan Cumberland helps engineering and construction firms see where they stand with AI and decide what to build first. He created Pacemark, the AI maturity model used in every Dan Cumberland Labs engagement, built from published research on more than 400 named firms and organizations. - Take the assessment: https://pacemark.ai/signal/assessment/?track=aec&utm_source=dcl-site&utm_medium=link&utm_campaign=pacemark-assessment - Book a call: https://book.dancumberland.com/ai-strategy --- Source: https://dancumberlandlabs.com/blog/engineering-firm-organizational-structure/