Architecture Practice Setup: From One-Person Shop to CoE

Key Takeaways

• Architecture practice maturity follows five distinct stages, each requiring different capabilities and governance approaches
• The transition from individual contributor to small team (Stage 2-3) represents the most critical scaling challenge
• Establishing standardized deliverables and methodologies early prevents chaos as the practice grows
• Executive sponsorship and clear value demonstration are essential for securing resources needed for CoE establishment
• Measuring practice impact through business outcomes, not just architectural outputs, drives sustainable funding and support

Stage 1: The Solo Practitioner - Building Your Foundation

Every successful architecture practice starts with one person who sees the bigger picture. As a solo practitioner, your primary challenge isn't scope—it's credibility and impact.

The solo practitioner stage is characterized by high energy, broad scope, and limited formal structure. Your success hinges on three critical factors: choosing the right initial projects, developing repeatable methodologies, and building influential relationships. Focus on high-visibility, low-complexity initiatives where you can demonstrate clear value quickly. This might involve capability mapping for a specific business unit, stakeholder analysis for a major transformation, or value stream optimization for a customer-facing process. During this stage, resist the temptation to tackle enterprise-wide initiatives. Instead, perfect your craft on bounded problems while building a toolkit of templates, frameworks, and visualization standards. Document everything—your future team will thank you. Most importantly, become a storyteller. Business architecture's power lies not just in the models you create, but in the insights you communicate and the decisions you influence.

• Establish relationships with 3-5 key business stakeholders who can champion your work
• Develop standard templates for capability maps, value streams, and stakeholder analyses
• Focus on 2-3 high-impact projects rather than trying to solve everything
• Create a personal brand around business insight, not just technical expertise
• Document your methodology decisions and lessons learned

Stage 2: The Dynamic Duo - Adding Your First Team Member

Adding your first team member marks a critical transition point. You're no longer just doing architecture—you're leading it.

The move from one to two practitioners fundamentally changes your operating model. Suddenly, you need coordination mechanisms, knowledge sharing processes, and quality standards that ensure consistency across different workstreams. This stage often reveals gaps in your methodology that weren't apparent when working alone. The ad-hoc approaches that worked for a solo practitioner must evolve into repeatable, teachable frameworks. Your first hire should complement your skills while sharing your vision for business architecture's potential. If you're strong in business strategy, consider someone with deep process expertise. If you excel at stakeholder management, look for analytical depth. Regardless of their background, invest heavily in onboarding. Create a 90-day learning plan that includes shadowing existing stakeholder meetings, reviewing past deliverables, and co-developing new artifacts. This investment in knowledge transfer will pay dividends as you scale further.

• Establish weekly collaboration sessions to share insights and align approaches
• Create a shared repository for templates, models, and project documentation
• Develop role definitions and responsibility matrices (RACI)
• Implement peer review processes for major deliverables
• Begin standardizing your visual modeling conventions and notation

Stage 3: Small Team Formation - Specialization and Structure

With 3-5 team members, you can begin developing specialized roles and tackling more complex, multi-dimensional challenges.

The small team stage introduces the possibility of specialization without losing the agility that characterizes smaller practices. You might have one person focused on capability architecture, another on information architecture, and a third on stakeholder engagement and change management. This specialization allows for deeper expertise while maintaining cross-training to ensure coverage during absences or peak periods. Governance becomes critical at this stage. Establish regular team meetings with structured agendas, standardized project intake processes, and formal quality gates for deliverables. Create role definitions that clarify not just what each person does, but how they collaborate. Implement lightweight project management disciplines—you don't need enterprise PMO overhead, but you do need visibility into workload, dependencies, and deadlines. This is also when you should begin developing formal relationships with other enterprise functions. Establish regular touchpoints with enterprise architecture, strategy, PMO, and process excellence teams. These relationships will be crucial as you scale toward CoE status.

• Define specialized roles while maintaining cross-functional capability
• Establish formal project intake and prioritization processes
• Create quality assurance standards and peer review requirements
• Develop regular reporting rhythms for stakeholders and leadership
• Begin building formal partnerships with related enterprise functions

Stage 4: Formal Practice - Structure, Standards, and Scale

The formal practice stage represents a significant maturation point where your architecture capability becomes a recognized enterprise function with dedicated budget, formal governance, and clear service offerings.

Transitioning to a formal practice requires developing enterprise-grade operating models. This means creating standard service catalogs that clearly articulate what business architecture delivers, how long it takes, and what resources are required. Your ad-hoc project selection evolves into formal intake processes with defined criteria, business case requirements, and portfolio management disciplines. You'll need to establish formal training programs, career progression pathways, and performance management systems that recognize the unique nature of architecture work. At this stage, measurement becomes paramount. Develop a balanced scorecard that tracks both leading indicators (stakeholder engagement, project pipeline health) and lagging indicators (business outcomes achieved, value delivered). Create regular reporting rhythms that communicate your practice's impact in business terms, not architectural jargon. CFOs and business unit leaders need to understand how your work translates into improved decision-making, reduced risk, and faster execution. Formalization also requires investment in tools and infrastructure. While solo practitioners can manage with desktop tools and shared drives, formal practices need enterprise-grade repositories, modeling tools, and collaboration platforms. This infrastructure investment should support not just current needs but anticipated growth toward CoE status.

• Establish formal budget allocation and resource planning processes
• Create standardized service offerings with effort estimates and deliverable templates
• Implement practice performance measurement and reporting systems
• Develop formal training curricula and competency frameworks
• Invest in enterprise-grade tooling and collaboration infrastructure

Stage 5: Center of Excellence - Enterprise Impact and Innovation

The CoE stage represents the pinnacle of business architecture maturity, where your practice becomes a strategic differentiator and innovation catalyst for the entire enterprise.

A true business architecture Center of Excellence transcends traditional consulting models to become a strategic partner in enterprise transformation. CoEs are characterized by proactive rather than reactive engagement, thought leadership rather than just service delivery, and enterprise-wide influence rather than project-based impact. Your team becomes the go-to source for strategic business questions, the facilitator of cross-functional collaboration, and the guardian of architectural standards and principles. CoE-level practices typically serve multiple functions simultaneously: they deliver architecture services, develop enterprise capability, drive innovation in business design, and often lead major transformation initiatives. This requires a more complex organizational model with multiple specialization tracks, formal partnerships across the enterprise, and often a hybrid structure that combines dedicated architects with embedded practitioners in major business units. The measurement framework for a CoE extends beyond individual project success to encompass enterprise-wide outcomes. You'll track metrics like strategic initiative success rates, time-to-market for new capabilities, and cross-functional collaboration effectiveness. The CoE becomes accountable not just for architecture deliverables, but for improving the organization's overall ability to execute strategy and adapt to change.

• Establish thought leadership through research, publication, and industry engagement
• Develop enterprise-wide architecture principles and governance frameworks
• Create formal partnership models with business units and other enterprise functions
• Build innovation labs or incubators for business model and process experimentation
• Implement comprehensive talent development programs including external certification

Critical Success Factors Across All Stages

While each maturity stage has unique challenges, certain success factors remain constant throughout the journey from solo practitioner to CoE.

Executive sponsorship stands as the most critical success factor at every stage. Without genuine support from senior leadership, architecture practices struggle to secure resources, gain access to strategic initiatives, and drive meaningful change. This sponsorship must be actively cultivated through regular communication, clear value demonstration, and strategic alignment. Your executive sponsors should be able to articulate the value of business architecture in their own words and actively champion your work in leadership forums. Value demonstration evolves across maturity stages but never loses importance. Solo practitioners demonstrate value through individual project success, while CoEs demonstrate value through enterprise-wide transformation outcomes. Regardless of stage, your practice must maintain a clear line of sight between architecture work and business results. This requires developing measurement capabilities, storytelling skills, and business acumen that extends far beyond technical architecture expertise. Cultural integration represents another persistent challenge. Business architecture often requires changes in how organizations think about problems, make decisions, and execute solutions. Successfully scaling your practice means becoming a change agent who helps the organization evolve its operating model, not just its architecture artifacts.

• Maintain active executive sponsorship through regular value demonstration
• Invest continuously in team capability development and external learning
• Build strong relationships with related enterprise functions and avoid territorial conflicts
• Focus on business outcomes and organizational capabilities, not just architecture artifacts
• Develop change management and communication skills alongside technical architecture expertise

Pro Tips

• Start building your executive advisory board early—even solo practitioners benefit from business unit sponsor relationships that provide guidance and championing
• Invest in storytelling and visualization capabilities as much as technical skills—your ability to communicate insight often matters more than the depth of analysis
• Create formal knowledge management processes from day one—the intellectual capital you build becomes your competitive advantage as you scale
• Develop relationships with peer practices in other organizations—external benchmarking and best practice sharing accelerates your maturity journey
• Focus on building business architecture literacy across the organization, not just delivering architecture services—sustainable success requires broad organizational capability