Make Sure I Am Prepared

2026-10-12By Archivios Engineeringcareersoftware-architectureleadershiptechnical-breadthtrade-off-analysiscertification

Moving into software architecture requires more than technical knowledge. I need to understand the business problems behind the solutions, work effectively with people, and guide teams through difficult decisions. This is my checklist for assessing whether I am prepared and identifying the areas where I need to grow.

Make Sure I Am Prepared

  1. Do I have a passion for creating solutions to business problems? I need to understand not only the solutions but also the business problems behind them.
  2. Do I only enjoy sitting at home or in the office and coding? If so, this position will be challenging.
  3. Do I enjoy interacting with people, negotiating, and developing my soft skills? If not, this position is not for me.
  4. Am I willing to remain technical and maintain technical breadth without always going deeper?
  5. Am I willing to mentor, coach, and lead teams?
  6. Do I understand the core responsibilities of a software architect and what the organisation expects from the role?

The role also requires me to:

  1. Maintain technical breadth.
  2. Make architectural decisions within the team.
  3. Analyse technology trends.
  4. Ensure architectural compliance, including quality attributes.
  5. Work across diverse technologies and understand at least one business domain, such as banking or finance.
  6. Understand company politics and learn how to navigate them.

Develop My Personal Roadmap

Learn Architectural Styles and Patterns

I need to build a stronger understanding of architectural styles and patterns, then learn when each is appropriate.

Focus on Trade-off Analysis

For each architectural decision, I need to:

  1. Identify the available options and constraints.
  2. Analyse the benefits, risks, and trade-offs.

Develop Soft Skills

I want to become a go-to person for my team by:

  1. Acting as a facilitator.
  2. Developing leadership skills by guiding architectural decisions and mentoring the team.

Build Relationships With Business Stakeholders

I need to make my work visible to business stakeholders and develop the negotiation skills required to connect technical decisions with business priorities.

Certification

As a short-term goal, I would like to evaluate which areas of architectural practice I should work on. One route I want to investigate is certification through The Open Group. This is separate from TOGAF certification, and I still need to confirm whether the process has changed.

My current understanding of the process is:

  1. Download the certification document template.
  2. Complete each topic in my own words.
  3. Submit the completed document to The Open Group.
  4. The Open Group evaluates whether my knowledge is sufficient. If it is not, they provide feedback on the areas that need improvement.
  5. If the written submission is satisfactory, it is forwarded to a review board of architects.
  6. The board evaluates me in an interview.
  7. If the interview is not satisfactory, I receive further feedback.
  8. If it is satisfactory, I become an Open Group Certified Architect, which is different from being TOGAF certified.

My first goal is to understand the areas in which I need to improve. I will read the certification document, identify those areas, and make working on them my next goal.

Maintain Technical Breadth Throughout My Career

Technical breadth is not a one-time milestone. I need to keep learning across technologies, architectural approaches, and business domains throughout my career. The goal is not to know everything in depth, but to maintain enough breadth to ask the right questions, understand the trade-offs, and help teams make sound decisions.