At Agile Architects, growth is more than a buzzword—it’s a journey. Yara’s story is a perfect example of how curiosity, adaptability, and drive can take you from one impactful role to the next.
Starting as a Business Analyst, Yara has recently stepped into the role of Solution Architect. While the transition may seem swift, it was also a natural evolution shaped by her goals and mindset. In this blog post, she shares her path, what motivated her, the skills she developed, and the lessons learned along the way.
Tell us a bit about your journey. You started with us as a Business Analyst but have now transitioned into a Solution Architect role. Was this a planned path?
Yara: “It wasn’t exactly planned for me to take on the role of Solution Architect this quickly, but I did intentionally start as a Business Analyst because the skills required for that role align well with what’s needed as a Solution Architect.
The main difference is that the latter requires a deeper understanding of the technological aspects and how to translate business analysis into technical components that fit within a specific enterprise landscape.
So while the transition wasn’t scheduled in terms of timing, the path from Business Analyst to Solution Architect was definitely a conscious one. I’m very grateful to have been given the opportunity to make that step so soon. It also feels like a natural progression—one role building logically on the other.”
What motivated you to move into architecture roles from a business analyst background? What do you enjoy most about working in architecture compared to your earlier role?
Yara: “What motivated me most was the opportunity to be technically challenged and to deepen my knowledge in that area. What I enjoy most is being the go-to person for proposing different solution scenarios, weighing their pros and cons, and advising on the most feasible option based on available resources and budgets. While a Business Analyst focuses on analyzing processes and identifying potential areas for improvement, as a Solution Architect, I also get to help shape how those improvements can be technically realized and supported.”
What skills from your BA role helped you succeed as an architect?
Yara: “The most important skill for both roles is strong communication—being able to talk to all kinds of stakeholders across the organisation.
As a Business Analyst, I had the opportunity to interview people from different departments to build a comprehensive analysis. Many of those same people are involved again in architectural work. While the BA role focuses more on engaging with business stakeholders, as a Solution Architect, you also frequently collaborate with technical profiles to assess technological feasibility. So it’s key to have a broad understanding and be able to communicate effectively across both business and technical domains.”
What new skills did you have to develop to step into EA and SA roles?
Yara: “I had to deepen my understanding of the technological aspects within a business context. As a Business Analyst, it’s important to understand how an organisation operates functionally. But in an EA or SA role, it’s equally important to grasp how it works technically—what standards and guidelines are in place, and how to design solutions that align with them. Another key skill I developed is the confidence to ask questions. I learned not to hesitate when something isn’t clear—asking questions, even repeatedly if needed, is how you truly learn and gain confidence in your understanding.”
How do the roles differ in terms of mindset or focus?
Yara: “The main difference lies in the focus area of each role. Because you’re looking at different parts of the organisation, your perspective shifts and you often collaborate with different types of people.
Still, the core goal remains the same: supporting the organisation in identifying opportunities for innovation and digital transformation—functionally as a Business Analyst, or technically as an Architect.”
What was the most challenging part of transitioning into each new role?
Yara: “Since it was my first time stepping into a Solution Architect role, the biggest challenge was figuring out what was actually expected of me. I also didn’t yet have deep technical knowledge, which was a bit intimidating at first. But by staying up to date and continuously asking questions to understand how things work, I gradually built a clearer picture.
Another challenge was defining the boundary between the Business Analyst and Solution Architect roles. It took some alignment and discussion to really figure that out and be able to work effectively as a tandem.”
How does your background in business analysis give you a unique perspective as a solution architect today?
Yara: “Having spent a lot of time talking to people on the business side, I’ve gained a strong understanding of their common concerns and how to adapt my communication style to match theirs. It also gave me insight into what they typically know well—and what they often don’t—which helps me clarify questions more efficiently and quickly connect with the right people.”
What’s one misconception people have about these roles that you’d like to correct?
Yara: “One common misconception is that roles like Business Analyst or Solution Architect are purely technical or purely business-focused. In reality, both roles require a strong blend of business insight and technical understanding. You need to be able to communicate effectively with both sides and translate between them. It’s not about being just a tech expert or just a business person—it’s about bridging the gap to deliver real value.”
What are you excited to learn or tackle next in your role as a Solution Architect?
Yara: “I look forward to being actively involved as a Solution Architect throughout project trajectories and helping to represent the solution approach.
Besides, doing this across multiple domains and industries is what makes the consultant role so challenging and interesting.”
Do you see yourself staying in architecture long-term — or exploring even more domains?
Yara: “Absolutely. I find that the combination of the social aspect and the technical challenges means this role still has many facets for me to explore.
It offers plenty of room for growth and continuous learning. It really feels like a role made for me, and I look forward to applying it across different domains, each with their own complexities.”
From the outside, Yara’s career path may look like a leap—but in reality, it’s a step-by-step evolution grounded in intention, adaptability, and a drive to learn. Her story is a great reminder that roles in tech aren’t always linear, and that the bridge between business and technology is one of the most strategic places to grow.
If you’re considering a similar transition, take it from Yara: the best way to prepare is to stay curious, ask questions, and keep learning.
