Wednesday, October 9, 2024

What Your Mamma Never Told You About "Asking So Many Questions" - A Short Perspective By An Architect

Architects often exhibit a propensity for excessive questioning, a characteristic perhaps inherent to their training in making rational and informed decisions. However, their education frequently falls short in equipping them to navigate the VUCA (Volatile, Uncertain, Complex, and Ambiguous) landscape and the inherent ambiguity that often pervades project requirements. Consequently, architects tend to seek definitive answers based on known information, overlooking the potential value of questions that can significantly impact project outcomes.

Beyond technical expertise, architects should possess a broader perspective, capable of zooming in on intricate details while maintaining a holistic view of the project. This requires a diverse toolkit, encompassing not only experience and humor but also the ability to effectively communicate and collaborate with stakeholders across various levels of technical proficiency.



In the dynamic world of IT, effective communication between architects and stakeholders is crucial for successful project delivery. However, a common pitfall is the tendency for architects to demand excessive detail and clarity from stakeholders, often overlooking the nuances and complexities of their perspective.

Understanding Stakeholder Perspectives

It's essential to recognize that stakeholders may not possess the same level of technical expertise as architects. Their primary concern is often to achieve specific business outcomes, rather than delve into intricate technical details. Additionally, stakeholders may have varying levels of understanding of the project's scope and constraints.

The Importance of Contextual Understanding

Architects should strive to understand the broader context of the project, including the business objectives, constraints, and potential challenges. This will help them tailor their communication style and provide more relevant information.

Multiple Paths to the Same Goal

It's important to remember that there are often multiple ways to achieve a desired outcome. While architects may have a preferred approach, it's essential to consider other viable options and be open to different perspectives.

The Evolving Nature of Requirements

In today's rapidly changing business landscape, requirements can evolve over time. Architects should design solutions that are adaptable and can accommodate future changes.

Navigating Ambiguity and Uncertainty

Stakeholders may intentionally introduce ambiguity into requirements for various reasons, including fair play, commercial negotiations, or to foster creativity. Architects should be prepared to handle such situations effectively and seek clarification when necessary.

Effective Communication Strategies

To bridge the gap between architects and stakeholders, consider the following strategies:

  1. Active listening: Pay close attention to what stakeholders are saying and ask clarifying questions to ensure understanding.
  2. Plain language: Avoid technical jargon and use clear, concise language that stakeholders can easily understand.
  3. Visual aids: Use diagrams, charts, and other visual aids to illustrate complex concepts.
  4. Iterative approach: Involve stakeholders throughout the project lifecycle to ensure that their needs and expectations are met.
  5. Prioritize information: Focus on the most critical details and avoid overwhelming stakeholders with unnecessary information.

By adopting these strategies, architects can foster better communication with stakeholders, leading to more successful projects and improved outcomes.

Further Readings:

The Architect Elevator — Visiting the upper floors

When Asking Too Many Questions Undermines Your Leadership

How Mindfulness Can Help Engineers Solve Problems

Navigating Ambiguity: Creating Opportunity in a World of Unknowns

Mastering Uncertainty: How to Thrive in an Unpredictable World

Thinking In Bets

Thinking, Fast and Slow

Leading in Ambiguity: How to Transform Uncertainty into Possibilities

Six Simple Rules: How to Manage Complexity without Getting Complicated

Cracked it!: How to solve big problems and sell solutions like top strategy consultants

What's Your Problem?: To Solve Your Toughest Problems, Change the Problems You Solve 

Upstream: The Quest to Solve Problems Before They Happen

Monday, August 12, 2024

Book Review - Building Data Centers with VXLAN BGP EVPN: A Cisco NX-OS Perspective

 

If you are completely new to EVPN, this book might help you understand the basics. But interestingly enough the book is dedicated to VxLAN BGP EVPN spread across roughly 450 pages and still miss to cover following topics in details:


- BGP underlay & Overlay designs details and tradeoffs beside best practices

- No details of EVPN route types, their encoding, flooding scope & optimization

- No details of design choices & tradeoffs 

- Lot of repetition 

- Very condensed packing of contents

- EVPN MLAG/Multi-homing details are skipped

- EVPN Policies stitching details are missing between different BGP AFIs & potential issues in ref. to policy control and information loss

- Multi-pod and Multi-fabric designs are are briefly touched  with no details but just plain theory

- EVPN over DCIs (L2 vs. L3) are very briefly touched with no details at all

- VxLAN & EVPN OAM are completely skipped

- No complete end to end configuration examples and scenarios

- Dual Stack & IPv6 only DCs are completely skipped

- Open Stack integrations are skipped

- How to deal between Physical and Virtual VTEPs is not covered

- Controller vs. Controller less designs are skipped

- Programmable fabric scalability details are not covered 

- Platforms specific details and limitations are not addressed 

- EVPN control plane security options are left for you to explore


HTH...

A Tech Artist ðŸŽ¨

Tuesday, April 16, 2024

Why Enterprise IPv6 Never Took Off - A Short & Crisp Business Perspective (For Sanity)


 

It's been only 30 years or so when the first IPv6 IETF draft probably came out (Was called IP-NG <Next Generation> back then, there was IPv5 too which You can't find in most book today). 

Ever since then, the network engineering community seems to have fallen in love with the newest blue angel. There are probably 100s of books, Video/Classroom trainings,  Podcasts that have been released covering it from all different technical perspectives (Apps., Services, Infra etc.). Everyone of those have been claiming that one should start embracing IPv6 sooner than later or else Your IT would become irrelevant and Your CIO and You will be thrown under the bus. So start now...

To fuel this trend further, they predicted that with IOT (Internet of Things) taking over the world, You will soon run out of time very quickly and not knowing IPv6 will make You irrelevant because of big demand of new IP addresses.  


I in fact came across "WhyNoIPv6" recently which seems to be a fancy protest forum against companies not offering their consumers to connect through IPv6. 
But why the businesses are yet not keen to put money into it for the most part ?

Imagine you are the virtual CIO of the company and You got to convince Your IT stakeholder about why they should pour some money into this. Just try to answer following questions.

1. What business value does it really add ?

2. What would the implications/opportunity lost, if we don't do this ?

3. Do we know what my business competition is doing about it ?, If Yes - What benefits have they achieved or costs they have saved ?

4. What is the best case vs. worst case scenario for by when our beloved Telcos/CSPs will run out of IPv4 address space in reference to our projected growth and requirements which will impose requirements for more IPv4 addresses. 

5. Throw some $$$ internally or hire an external IPv6 consulting firm, ask them to put together a planning document that covers - IT wide IPv6 readiness, Roadmap, Tentative Cost (Adoption Curve, HW/SW, Licensing, Deployment, Migration, Integrations, Support, Training, Highlighting Current IT Maturity and maybe - The Pitfalls/Lessons Learned by Industry).

BTW... IPv6 does offer some amazing technical benefits as well as has got some amazing new drawbacks/complexities to deal with, which of course You can solve as long as your are committed...fully. Picking up on IPv6 should only take few weeks.

Until then - Trust God, Trust NAT & other stuff which many would tell you are so ugly solutions, and politely ignore such warning:

HTH...

A Tech Artist ðŸŽ¨

Thursday, February 8, 2024

Consulting Myth Busting - They are very good problem solvers

 


Though Consulting and Enterprise Architects comes in many shapes and sizes, one of the common misconceptions I often hear and have to address is - "They are better problem solvers, specially if problems are complex in nature".
 
I politely disagree.
 
They are often people who are better "Problem Framers" beside "System Thinkers".
 
Few things for You to consider:
 
  1. You may still be solving the wrong problem.
  2. You are still forcing yourself to solve problem which might be multi-dimensional/discipline in nature. So you can at max fix your part of the problem only. (Outputs not outcomes). Many just unintentionally do it to grow their pride and be seen as heroic.
  3. There are only probably 2 books in the market You can find on problem framing, you can still find 100s on problem solving.
  4. You really need to practice hard to win against your own conscious/unconscious bias.
  5. You need to fight against the status quo (Your environmental needs to be successful).
  6. You got to be expert at everything and yet you are not an expert at anything. (You will only get this point if You have lived through it for real).
If you are deeply in love with any particular discipline or is passionate about, You are not really a consultant. Find a better word for yourself and your identity.  
 
More on problem framing and why It doesn't really matter in 99% cases in the future post maybe.

HTH...

A Tech Artist ðŸŽ¨

Monday, September 11, 2023

The Data Centre Networking (DCN) Ref. Frame - Expanding MONAF Part 1

Your Data Centre Network (DCN) essentially is a stretch that cuts across SaaS, PaaS, Public Clouds, Hybrid Clouds & the Modern Day Multi-Cloud.

If You look underneath, it's essentially a set of technical capabilities, combined together to deliver business outcomes.

But what should be Your starting point to have a well structured conversation with business as well as the technical folks around DCN ?

Well, if we expand the DCN frame under the MONAF umbrella, it exactly does that to offer You are a very detailed and a firm structure by segmenting those capabilities into well defined and structured layered approach. (Essentially following the famous MECE consulting approach).

Let me know if there is any questions that comes in your mind around DCN that this frame couldn't fit into one of it's layers.


HTH...

A Tech Artist ðŸŽ¨