How to Run a Business Architecture Program with a Team of Two
Most business architecture guidance is written for mature practices with dedicated teams, executive sponsors, established tooling, and a multi-year program mandate. Most organizations attempting business architecture in practice have none of those things. They have one or two people who were given an architecture mandate alongside their existing responsibilities, a request from the CIO or a transformation lead to "do business architecture," and limited clarity on what that means for an organization that has never had an architecture function before.
The question this post addresses is practical: if you have two people and a mandate to build and run a business architecture program, what do you actually do? What do you do first, what do you defer, and what do you not do at all? The answer is different from what a mature practice would do, and applying the full architecture framework to an under-resourced starting position produces documentation nobody uses rather than analysis that changes decisions.
The Principle That Changes Everything at Small Scale
A business architecture program with two people cannot be comprehensive. Attempting comprehensive coverage of the organization's full capability landscape, full process model, full application portfolio, and full operating model with two practitioners will produce a partially complete model that is out of date by the time it reaches the level of completeness that would make it useful. The coverage attempt consumes the team's time without producing the decision-enabling output that would justify the investment.
The principle that makes a small architecture practice viable is selectivity: doing fewer things completely rather than more things partially. A capability map that covers three capability domains with full strategic importance assessment, current maturity scores, and investment implications is more valuable than a capability map that covers all twelve domains at a high level without the analytical depth that makes it a decision-making tool.
Selectivity requires a clear answer to the question that drives the selection: which architecture work produces the most value for the organization's current priorities? For most organizations with a new or small architecture practice, that answer comes from the transformation program, the AI agenda, or the cost reduction mandate that generated the architecture mandate in the first place. The architecture work that directly informs those priorities gets done. The architecture work that would be valuable in a mature practice but does not connect to current priorities gets deferred.
What to Do in the First Six Months
The first six months of a small architecture practice should produce three things: organizational credibility, a scoped capability model covering the highest-priority domains, and at least one investment decision that the architecture work directly influenced. Organizational credibility is the prerequisite for everything else: an architecture practice that is not visibly contributing to decisions the organization cares about will not receive the stakeholder engagement, executive sponsorship, or expansion investment that a sustainable practice requires.
Credibility comes from connecting early architecture work to a specific decision that someone with budget authority needed to make. The most efficient path is to identify the highest-stakes technology or operating model decision currently in flight, assess what architecture analysis would make that decision more defensible, and produce that analysis quickly. The analysis does not need to be comprehensive. It needs to be useful to the decision-maker who is trying to make a specific choice with better evidence than they currently have.
The scoped capability model should cover the three to five capability domains most relevant to the organization's current strategic priorities. Assess each capability on strategic importance and current maturity using the four-dimension framework described in the capability maturity assessment post, but scope the assessment to domains and data sources accessible with the team's available time. The output should be an investment prioritization recommendation that connects specific capability gaps to specific transformation priorities: a direct recommendation about where to invest, grounded in evidence rather than intuition, expressed in terms a business leader can evaluate and act on.
The AI Tools That Change the Economics
The AI-augmented modeling capabilities now embedded in Bizzdesign, Ardoq, and equivalent platforms reduce the time required to produce architecture artifacts significantly. Model generation from descriptions, consistency checking against existing documented decisions, and automated impact analysis for proposed changes each reduce the manual effort that previously constrained how much a small team could produce and maintain.
For a two-person practice, the most valuable AI tooling investments are in documentation automation rather than in analysis. The analysis work, stakeholder engagement, capability assessment, and investment recommendation, requires human judgment and relationship context that AI tools cannot replace. The documentation work, producing readable descriptions of capability definitions, maintaining currency of model elements, and generating reports that make architecture artifacts accessible to stakeholders who will not read raw model outputs, can be substantially automated. A small team that automates documentation overhead redirects recovered time to the stakeholder engagement and analytical work that produces organizational influence.
The Stakeholder Model That Works at Small Scale
A small architecture practice cannot maintain deep engagement with every part of a large organization. Concentrate engagement with the stakeholders who are making the decisions the architecture program is supposed to inform, and maintain awareness rather than deep engagement with the rest. The three relationships that matter most are the executive sponsor who legitimizes the practice's authority to engage across organizational boundaries, the transformation or program leads making the investment and operating model decisions that architecture should inform, and the two or three business unit leaders whose domains are in the current analytical scope.
The relationship investment that produces the most durable credibility is being the person who makes hard decisions easier rather than the person who produces comprehensive documentation. Speed and relevance to current decisions matter more at small scale than coverage and comprehensiveness.
What to Defer and What to Skip Entirely
Defer comprehensive process modeling until there is a specific analytical need that process-level detail would address. Skip the architecture repository tooling investment until the practice has sufficient model content and stakeholder engagement to justify it. Enterprise architecture platforms are expensive, require significant setup and configuration time, and produce their value when the model is comprehensive enough and current enough that stakeholders will use it directly. A practice in its first year with a scoped capability model covering three domains is better served by well-maintained shared documents than by a full EA platform that requires months to configure and adopt.
Skip framework certification programs at the expense of stakeholder engagement and analytical output. TOGAF and BIZBOK certification is valuable background for practitioners building a mature practice over multiple years. For a two-person team in a new practice, the time invested in certification is time not invested in the stakeholder relationships and analytical work that determine whether the practice survives long enough to benefit from that background.
Talk to Us
ClarityArc's business architecture practice works with organizations at every stage of architecture maturity, including those just establishing the function with limited resources. If you are building a business architecture practice with a small team and want a realistic approach to producing organizational value before you have built out the full program, we are ready to help you design it.
Get in Touch