What is it like to be a Solution Architect at Agile Architects? What support do you receive, what challenges do you face, and what makes this role so rewarding? To find out, we spoke with Leander Fransoo, one of our experienced Solution Architects.
How Does Agile Architects Support You as a Consultant?
Agile Architects provides strong support in multiple ways, including training and certification opportunities. Since joining last year, I’ve had the chance to follow two specialized training courses: Agile Architecture and TOGAF. These courses help me stay aligned with market and customer requirements. The company also actively supports obtaining certifications, ensuring that we stay at the forefront of architectural best practices.
What Is Your Personal Win in Working for These Clients?
I’ve had the opportunity to work for FOD Justitie, among others. Just last week, we successfully delivered the first release of an important project. The work I do there is socially relevant—it gives me the feeling that I’m contributing to something bigger.
At FOD Justitie, I collaborate closely with a team of developers and project managers. In my opinion, it’s crucial to avoid working in an ivory tower and instead keep short, direct lines of communication with developers and stakeholders. We spend two days a week on-site, which fosters strong collaboration between different teams.
Of course, we also coordinate with external teams. Depending on the project’s progress, I set up synchronization meetings to ensure that everyone is aligned. This also helps in prioritizing tasks effectively. Most importantly, I believe in speaking the language of your audience—whether it’s developers, project managers, or business representatives. Each group has its own perspective, and understanding those perspectives is key.
What Is Your Personal Win in Working as a Consultant for Agile Architects?
At Agile Architects, I appreciate the balance between independence and support. We are encouraged to take initiative while knowing that we can rely on a strong network of colleagues for guidance. Our monthly knowledge-sharing sessions and weekly project syncs ensure that we continuously learn from each other’s experiences.
How Do You Ensure Effective Communication and Collaboration Between Internal Teams and Yourself?
Good communication is more than just meetings—it’s about building trust and alignment. I ensure this by:
- Keeping communication lines short and direct with both developers and stakeholders.
- Spending two days a week in the office, which naturally fosters teamwork.
- Organizing synchronization meetings with external teams to maintain a shared vision.
- Adapting my language and approach to different stakeholders—whether it’s business, IT, or management.
By focusing on clear and structured communication, we create an environment where everyone works toward the same goal.
How Do You Handle Resistance to Change When Proposing Architectural Changes or Agile Practices?
Resistance to change is natural, but the reasons behind it can vary. Sometimes it’s mistrust, conflicting priorities, lack of communication, or personal ambitions. The key is to listen and understand what is causing the resistance.
Transparency plays a huge role. People are more likely to embrace change when they see that architectural decisions are based on business needs rather than theoretical ideals. I also believe that technical credibility is important—when stakeholders see that you truly understand their world, they are more likely to trust your guidance.
How Do You Ensure That the Solutions You Implement Remain Adaptable to Future Business Changes?
Businesses constantly evolve due to internal and external factors. That’s why it’s critical to design agile architectures that can adapt to change. Agile is sometimes seen as a buzzword, but at its core, it means being flexible and future-proof.
A strong architecture allows organizations to respond proactively rather than reactively. To achieve this, I focus on principles such as:
A strong architecture allows organizations to respond proactively rather than reactively. To achieve this, I focus on principles such as:
- Domain-Driven Design to ensure modularity and business alignment.
- Product teams that own and evolve their solutions over time.
- Roadmaps that guide long-term evolution.
- Integration standards and API-first design to enable smooth interoperability.
- Reusable building blocks to support future scalability and innovation.
By structuring architectures with adaptability in mind, we prevent firefighting and instead enable long-term innovation.
Conclusion
Being a Solution Architect at Agile Architects means designing solutions that are technically sound, business-aligned, and future-proof. It’s a role that requires deep technical expertise, strong communication skills, and the ability to manage change. Most importantly, it’s a job where you’re always learning, collaborating, and making an impact.
Are you someone who enjoys building sustainable IT solutions? Then this might be the perfect role for you! 
