In this episode, we welcome Finnish enterprise architect and author Eetu Niemi to explore what it means to make enterprise architecture (EA) “lightweight”—practical, collaborative, and relevant in the real world. From frameworks to fiction writing, from ivory towers to coffee-fueled collaboration, this conversation dives into how to make EA actually work for organizations.With over 16 years of experience in architecture consulting at CGI, Coala, and Accenture, Eetu has guided more than 45 private and public organizations in transforming their business and IT landscapes. He specializes in enterprise and solution architecture, helping organizations align technology with strategy, improve EA practices and tools, and strengthen information security.A published author and recognized thought leader, he wrote the first EA book in Finnish and two bestsellers on IT consulting and frequently shares insights through blogs, newsletters, and speaking engagements. Holding a PhD in enterprise architecture benefit realization and an MSc (Econ.), his cross-industry work spans finance, telecom, manufacturing, and the public sector—delivering results in EA modeling, governance, and tool implementation with platforms such as BiZZdesign, Ardoq, and Sparx EA.In this episode of the podcast, we talk about:Eetu’s background — Author, architect, and advocate for democratizing enterprise architecture so it’s accessible beyond the ivory tower.Rethinking EA’s relevance — Success comes when EA shifts from being “nice diagrams” to being indispensable guidance that helps organizations plan, adapt, and reduce risk.Defining “lightweight EA” — It’s all about communication and cooperation, using models as tools for dialogue, not as ends in themselves.Avoiding EA’s common traps — Filling every box in a framework or modeling everything down to cables and servers misses the point. EA should focus on solving real business problems.Where to draw the line — Model at the logical level (applications, processes, data) — not every internal detail. EA is the layer above IT and process modeling, not a replacement for them.Kickstarting EA right — Start small, plan with stakeholders, and document goals and methods early. Collaboration beats over-engineering every time.Who to talk to first — Don’t wait for the C-suite; start where you have access, build trust, and work your way upward.Quick wins matter — Focus on tangible outcomes like system maps for upcoming projects — those early wins open doors and earn invitations “to the next party.”Light tools for light EA — Begin with approachable modeling tools instead of overcomplicated platforms. Save the big systems for when you truly need them.Governance without the grind — Keep EA blueprints current but concise. A handful of well-maintained diagrams is better than hundreds of forgotten files.Collaboration is key — EA succeeds through engagement: creating models with people, validating them with people, and helping those people make better decisions.Selling the value — Show how EA helps others succeed — whether that’s IT planning, compliance, or transformation — and you’ll overcome “I have no time for this” resistance.EA + AI = opportunity — Complexity is growing, not shrinking. AI can help classify, visualize, and assist — but architects still provide the judgment and storytelling.Making EA stick — Keep the practice alive through persistence and visibility. Even when budgets tighten, lightweight EA thrives by staying practical, connected, and useful.You can reach Eetu on LinkedIn here: https://www.linkedin.com/in/eetuniemiphd/ Please reach out to us by either sending an email to [email protected] or signing up for our newsletter and getting informed when we publish new episodes here: https://www.whatsyourbaseline.com/subscribe/.

Ask this episode

“What did the council decide on item 42?” — answered with the speaker and the moment.

Transcript

Related