Over my 14-year career, I’ve taken on various roles, from Software Engineer to Architect, across several organizations. In addition to this, I’ve had the opportunity to mentor and support several startups, helping them accelerate their business growth. I’ve also contributed as a freelance architect for various organizations. These experiences have given me insight into how companies operate at both the startup phase and as established enterprises, as well as how they transition from one to the other.
In this article, I aim to share how architectural landscape transitions happen, hoping they will be valuable to those who read it.
Theoretically, This is how TOGAF describes the enterprise architecture landscape.
The image is a simple flowchart that explains the hierarchy of roles and processes in a technology organization.
The diagram is a hierarchy chart that shows who creates what in a technology organization.
- At the top are “Enterprise Architects” who make a “Meta Model.”
- Below them are “Software Architects” who use the “Meta Model” to create a “Model.”
- At the bottom are the “Tech Lead & Dev Team,” who use the “Model” to create “Applications.” Each level supports the next, and there is an expectation to follow (or “comply with”) the plans from the level above.
Let’s map it to the modern practice with intentional architecture and emergent/agile teams.
In addition to the roles and processes, the diagram includes three levels on the right side, labeled as “Enterprise — C,” “B,” and “Startup — A.” These represent different stages of organizational technical maturity or technical growth phases in a company’s lifecycle:
- Startup — A: This is the beginning stage where a company is just starting. It’s typically a smaller, more agile environment where the “Tech Lead & Dev Team” is very hands-on in creating applications.
- B: This middle stage suggests a transitional phase where a company is growing. It’s where the influence of “Software Architects” is more proactive as they create specific “Models” or forecasts for projects, by looking at the big picture where the organization leads.
At level B, the stakes are high — it’s a critical phase. This is when architects need to step up, taking on more responsibility to drive technical and business excellence. Their foresight ensures the product can reach a broader audience and remain adaptable for the future.
This stage often brings a wave of new hires, including agile coaches and managers. However, they must align with the company’s vision. A hard, by-the-book approach doesn’t cut it; they’re here to cultivate technically skilled individuals into strategic thinkers.
Product owners also need to broaden their perspective, tailoring requirements not just for immediate needs but for the wider market, beyond individual customer requests.
- Enterprise — C: This is the mature stage of a company. The “Enterprise Architects” are in place, suggesting a large, established company with a broad vision. They create the “Meta Model,” which sets the standards and guidelines for everything else the company does in terms of technology and the business roadmap.
The levels imply that as a company grows from a “Startup — A” to an “Enterprise — C,” its structures become more complex, with additional layers of planning and compliance needed to manage that complexity.
Here’s a simplified explanation and some tips on growing from a startup to an enterprise.
Roles:
- Enterprise Architects: They are like city planners, designing the overarching structure for how technology and technical landscape should be used in the company’s business architecture.
- Software Architects: These are the architects of individual buildings, focusing on the design of specific systems and aligning them to the technical landscape defined by Enterprise Architects.
- Tech Lead & Dev Team: This group is like the construction team, building the actual software based on the designs.
Processes:
- Meta Model/Business and Tech View Points of the Organization: This is the master blueprint. It’s a high-level plan that guides the overall structure of the technology landscape in the company.
- Model/Technical Excellence and Individual Business Models/modules: These are more detailed blueprints derived from the Meta Model, used for building specific systems.
- Applications: These are the finished buildings, or in this case, the software that the company uses or sells.
Growth Tips from Startup to Enterprise:
- Foundation: Start with a solid Meta Model. Even if you’re small, know where you want to go. Think big picture.
- Standardization: As you grow, create Models that standardize your software design process, ensuring consistency, quality, and scalability aspects.
- Scaling the Team: Develop your team’s skills. Your Tech Lead & Dev Team need to grow with your architecture. Invest in training and brainstorming.
- Processes and Tools: Implement robust processes and tools that can handle the increased complexity as you grow.
- Iterate: Continuously refine your Meta Model and Models as you learn from building Applications.
- Feedback Loops: Listen to feedback from your development teams and customers to improve your architectural designs.
- Invest in Tech: Technology is a key growth driver. Invest in new tools, technologies, and talent.
- Compliance and Governance: Ensure your Applications comply with your Models, which in turn should align with your Meta Model. Good governance with proper flexibility becomes increasingly important as you scale.
- Adaptability: Be prepared to evolve your architecture as you face new challenges and opportunities.
- Vision: Keep your enterprise vision in mind at all times and make sure your technology aligns with the business goals.
The journey of transitioning from a startup to an enterprise is like growing a garden. Start with a plan, plant according to the seasons, tend carefully, and be prepared to adapt to changing conditions. It’s all about planning well, picking the right team, and learning as you go. If you liked this guide and feel ready to grow your business tree, go ahead and give us some claps. Let’s get planting!