What 20 Years in Solutions Architecture Taught Me About Building Products
The Secrets of Building Great Products: Lessons from 20 Years in Solutions Architecture
What does it really take to build products that stand the test of time? Is it cutting edge technology? A flawless design? Or perhaps a team of genius developers? After spending two decades in solutions architecture and leading a digital innovation company, I've learned this: success rarely hinges on any one factor. Instead, it's about an intricate dance between people, processes, and technology - all aligned toward solving real problems.
At Digiovations, we’ve spent years designing and building digital solutions for industries like healthcare (with a particular focus on the NHS), enterprise organizations, and beyond. Along the way, we’ve discovered insights that apply universally, whether you’re creating a custom app, deploying Microsoft 365, or rolling out a cloud-based infrastructure on Azure.
In this article, I’ll share the key lessons I’ve learned over 20 years of building products that don’t just work but make a real impact.
Lesson 1: Always Start with the Problem, Not the Technology
One of the biggest mistakes teams make is starting with the solution rather than the problem. It’s easy to get swept up in the allure of the latest tech trend, be it AI, blockchain, or some other buzzword. But unless you’re clear on why your product needs to exist, you’ll end up building something that might be innovative but not inherently useful.
What I've Learned:
- Ask the hard questions upfront: Who is this product for? What pain point does it solve? Why does this problem matter?
- Empathy is key: In our work with the NHS, for example, we don’t just look at technical requirements. We immerse ourselves in understanding the day-to-day challenges faced by clinicians, administrators, and patients. This ensures the solutions we deliver actually address their needs, not just what we think they need.
- Technology is a tool, not the answer: Whether it’s Microsoft 365 or Azure, the tools we use are only as good as the problems they solve. The best solutions start with a deep understanding of the challenge at hand.
Lesson 2: Simplicity Scales, Complexity Crumbles
As a solutions architect, I’ve seen countless projects fail because they were too complex. Complexity might feel impressive in the moment - it can make a product feel “robust” or “sophisticated.” But over time, complexity becomes the enemy of scalability, usability, and maintenance.
What I've Learned:
- Design for the user, not the engineer: In one of our healthcare projects, we noticed that clinicians were struggling to navigate convoluted interfaces in their software. By simplifying the design and focusing on the tasks that mattered most, we greatly improved adoption rates and reduced training time.
- Avoid feature bloat: Just because you can build something doesn’t mean you should. A successful product often does a few things exceptionally well, rather than trying to do everything.
- Think about the future: Every line of code and every decision you make should be evaluated with scalability in mind. It’s not just about solving today’s problem - it’s about creating a foundation for tomorrow’s growth.
Lesson 3: Collaboration is the Cornerstone of Innovation
The myth of the lone genius is just that, a myth. The best products emerge from collaboration, not isolation. This is especially true in solutions architecture, where projects often involve a diverse range of stakeholders, from developers to designers to end-users.
What I've Learned:
- Communication is everything: In our work with Microsoft 365 implementations, we’ve found that success often hinges on communication not just within the development team but across the entire organization. Everyone needs to be aligned on goals and expectations.
- Break down silos: At Digiovations, we emphasise cross-functional collaboration. Developers, designers, and business stakeholders all have a seat at the table because great ideas can come from anywhere.
- Listen more than you talk: Some of the best innovations in our projects have come from listening to the people we’re building for - whether it’s a nurse in an NHS trust or a frontline employee at an enterprise client.
Lesson 4: The Right Tools Can Accelerate Innovation
While technology isn’t the starting point, choosing the right tools can make or break a project. Over the years, I’ve seen how the right platform or framework can accelerate development, improve performance, and reduce long term costs.
What I've Learned:
- Invest in the ecosystem: Microsoft 365 and Azure have been game-changers for our clients because they offer a robust, scalable ecosystem. They’re not just tools; they’re platforms that integrate seamlessly with existing systems and provide a foundation for growth.
- Don’t reinvent the wheel: When building custom apps, we often leverage existing frameworks to save time and reduce risk. The goal isn’t to build everything from scratch — it’s to deliver value as quickly as possible.
- Prioritize security and compliance: This is especially critical in industries like healthcare, where data protection is non-negotiable. Azure’s built-in security features have been invaluable in ensuring our NHS clients meet compliance requirements without sacrificing usability.
Lesson 5: Measure, Learn, and Iterate
No product is perfect on day one. In fact, the best products are those that evolve over time based on real-world feedback. This iterative approach has been a cornerstone of our work at Digiovations.
What I've Learned:
- Launch early, learn fast: Many of our most successful app development projects started with a minimum viable product (MVP). By getting a basic version into users’ hands quickly, we were able to gather invaluable feedback and make improvements before scaling up.
- Data is your friend: Use analytics to measure what’s working and what’s not. For example, when implementing Microsoft 365, we track adoption metrics to understand how users are engaging with the platform and where additional training might be needed.
- Don’t fear failure: Not every iteration will be a success, and that’s okay. What matters is learning from mistakes and using those insights to improve.
Lesson 6: Trust is the Most Underrated Ingredient
At the end of the day, technology is only part of the equation. Trust is what makes or breaks a product - trust between team members, trust between you and your clients, and trust between your product and its users.
What I've Learned:
- Transparency builds trust: In one Local Government project, we made it a point to keep stakeholders updated at every stage, even when things didn’t go as planned. This transparency helped us build a strong relationship and a better product.
- Deliver on your promises: Nothing erodes trust faster than overpromising and underdelivering. Be realistic about timelines, features, and outcomes.
- Focus on user experience: A product that’s reliable, intuitive, and secure fosters trust with users. This is especially important in industries like healthcare, where lives can literally be on the line.
Looking Ahead: Building the Future, Together
Two decades in solutions architecture have taught me that building great products is as much about people and processes as it is about technology. It’s about asking the right questions, embracing simplicity, fostering collaboration, choosing the right tools, and committing to continuous improvement. Most importantly, it’s about building trust.
As Digiovations continues to partner with organisations across industries, we remain committed to these principles. Whether we’re working with the NHS to modernize healthcare technology or helping enterprises maximize their Microsoft 365 investment, our focus is always on solving real problems and delivering lasting value.
Are you ready to build something that makes an impact? Let’s start a conversation. Contact Digiovations today and take the first step toward creating products that truly matter.
Meta Title: 6 Lessons from 20 Years in Solutions Architecture
Meta Description: Discover the key lessons from 20 years of solutions architecture experience, including how to build impactful products, foster collaboration, and create scalable solutions.