Top 3 Tips to Be a Great Cloud Architect

Key Concepts

• Communication: The ability to effectively convey information and understand others.
• Seeking to Understand: Going beyond surface-level requests to grasp the core requirements and business drivers.
• Curiosity & Experimentation: A continuous drive to learn, test, and explore how technologies work.
• T-Shaped Knowledge: Possessing broad knowledge across many areas and deep expertise in a few.
• Business Impact: Understanding how technological solutions affect business outcomes.
• Trust: Building and maintaining credibility with customers and stakeholders.
• Systems & Capabilities First: Prioritizing the underlying needs and functionalities before selecting specific services.

Top Three Tips for Being a Great Cloud Architect

This video outlines three key tips for aspiring to be a great cloud architect, differentiating them from merely "okay" or "good" architects. The speaker, with 25 years of enterprise architecture experience, including 10 focused on cloud, emphasizes that these principles remain consistent.

1. Communication

Effective communication is paramount for understanding customer needs and articulating solutions.

• Active Listening and Adaptation: The initial step involves observing and listening to understand the customer's communication style, technical proficiency, and language. The architect should then adjust their own communication to match the customer's comprehension level.
• Dialogue over Presentation: Interactions should be conversational and collaborative, not a one-way presentation. The goal is to foster a natural dialogue, avoiding an "inquisition" feel.
• Asking Probing Questions: To uncover core requirements, architects should ask questions like "Have you considered this alternative?" or "What drove you to this current solution?" This acknowledges that the architect may not have all the historical context.
• Partnering and Trust: The architect's role is to be a partner, not to embarrass or show off. Building trust across all stakeholder levels is crucial.
• Leveraging Personal Style: Architects should lean into their comfortable communication style, whether it's whiteboarding (combining visual and auditory senses for confirmation) or using presentations. Comfort leads to better communication.
• Focus on Understanding: The emphasis is on understanding what the customer truly cares about and wants to achieve.

2. Seek to Understand

This involves delving deeper than the stated request to uncover the underlying business drivers and core requirements.

• Uncovering Root Requirements: Instead of simply mapping a customer's request to a cloud solution, architects must understand why the solution is desired and what it aims to achieve.
• Challenging Assumptions: The stated ask might be correct, but it could be based on outdated requirements or misunderstood needs. Architects should be open to more efficient or alternative solutions.
• Thinking Outside the Box: Avoid pre-conceived notions about specific solutions. The process involves listening, understanding requirements, identifying necessary capabilities, and then selecting services that meet those capabilities.
• Positioning Possible Futures: Architects can help customers envision potential solutions and futures, prompting them to question and engage in dialogue.
• Considering Business Impact: All technological decisions must be evaluated for their impact on the business. Technology should not be pursued for its own sake.

3. Curiosity and Experimentation

A continuous drive to learn and explore is essential in the rapidly evolving cloud landscape.

• Hands-On Learning: The best way to understand how things work (and don't work) is through experimentation and hands-on practice.
• Addressing Imposter Syndrome: It's impossible to know everything about even one cloud. Experienced architects often face imposter syndrome, but the reality is that broad knowledge is more achievable and valuable than attempting to be an expert in everything.
• T-Shaped Knowledge Model: Architects should aim for a broad understanding of many technologies (what they do, problems they solve, how they interact) and then develop deeper knowledge in specific areas. This includes understanding fundamental capabilities like networking, identity, security, governance, resiliency, scalability, and automation.
• Community Engagement: Participating in communities allows for sharing learnings (both successes and failures) and learning from others.
• Open-Mindedness: Avoid pre-committing to specific technologies (e.g., Kubernetes). Instead, focus on understanding requirements, identifying necessary capabilities, and then selecting appropriate services. The approach should be "systems and capabilities first."

Fundamental Principle: Do the Right Thing for the Customer

Beyond the three tips, a core principle is to always act in the best interest of the customer to build and maintain trust.

• Earning and Maintaining Trust: Trust is paramount and should never be compromised for a transaction.
• Addressing Misalignments: If there's a disagreement between what the architect believes is the right solution and what an account team or salesperson proposes, this discussion should happen away from the customer.
• Integrity in Practice: The speaker shares instances of pushing back or refusing to engage partners when it doesn't align with customer interests.
• Being a Decent Human Being: Ultimately, being genuine, owning mistakes, and correcting them, with the primary goal of helping the customer move forward and solve problems collaboratively, is the foundation of great architecture.

Conclusion

The video concludes by reiterating the three core tips: great communication, seeking to understand, and maintaining curiosity through experimentation. The overarching message is to prioritize the customer's needs and act with integrity, fostering a collaborative approach to finding the best possible solutions.