Pragmatic architecture
The quiet superhero in your next project. In the bustling metropolis of digital transformation, where challenges lurk around every corner, a quiet hero emerges to save the day - pragmatic architecture. With the power to bring order to the most complex projects, this unsung superhero ensures that every mission is a success.
The origin story
Born from the need for practical solutions and efficient designs, pragmatic architecture possesses the unique ability to balance innovation with feasibility.
Architects play a critical role in IT projects to envision, design, govern, and drive robust, fit-for-purpose solutions. Good architecture provides the critical foundations of a delivery; it should never determine the outcome; but it must enable it. Pragmatic architecture respects the core MVP principles of cost, time, quality, and scope.
Beware the evangelist architect
I am sure we have all come across the ‘evangelist architect’. Evangelists design highly innovative but impractical solutions, motivated more by ego and self-importance than by business outcomes.
Evangelists pose a significant risk for project teams. Their unfounded self-assurance risks designing a solution which fails to address core business needs. And their tendency to over-engineer a solution adds no value and only serves to blow out the core MVP principles.
The role of the pragmatic architect
The superpower of a pragmatic architect is their ability to actively listen to the business, filtering the needs and wants of many stakeholders with technological, financial, and environmental considerations.
They must make critical governance-level decisions on patterns, technologies, and approach. And most importantly, they must ensure their solution aligns with the business’ transformation needs. They aim to slightly over-deliver on the current release with sufficient flexibility to continually evolve as needed.
While they may not attract the same amount of attention as the evangelist, the pragmatic architect is the real superhero in the story.
What makes architecture pragmatic?
Pragmatism in architecture is achieved through flexibility, scalability, and an ability to predict the future. It builds on the programming principles of ‘composable architecture’ - polymorphism, encapsulation, data abstraction, and inheritance. These principles enforce simplicity; they ensure code is re-usable, extensible, and limits unnecessary re-work.
When applied to architecture, these principles drive lightweight, connectable, diverse, and reusable architecture patterns which deliver the ability to change direction as required without having to rearchitect the complete solution.
Architecture should never be carved in stone. Pragmatic architecture is pliable, mouldable, and responsive to the needs of business.
Tips for designing pragmatic architecture
Plan for the future - The solution must meet the needs of MVP + 1 phase of delivery. Keep one eye on the delivery roadmap and the other on the horizon n+1.
Stay flexible - Opt for loosely coupled, composable architecture to ensure your deliveries remain lean, agile, and flexible.
Be inclusive - Connecting your architect with the business and delivery teams will drive knowledge sharing and understanding. Listen, challenge, and build consensus to deliver a better outcome.
Embrace ArchOps - Unite IT architecture and operations functions to design, implement, and manage infrastructure which serves user and business needs. Break down silos, think agile, and ‘shift left’ to accelerate design and delivery cycles.
Let’s create solutions that deliver and last
Work with an experienced team to plan, design and deliver secure, user-centred solutions. From modernising services to improving efficiency and solving complex challenges, we help you achieve results that matter.