Your client wants a non-standard design in System Architecture. How do you navigate this challenge?

Remember that usually the client doesn't care how you implement something, the request is usually their interpretation based on their understanding of how things should be done. If you can take the conversation out of the architecture plane into a more business/value conversation - you'll find it much easier to come to a mutual agreement. There are probably dozens of ways to deliver the same value to the customer so it's important to understand what value they want instead of what design they want.

Contemporary cloud native microservice based solutions hardly have a single globally accepted standard, so this request may not be as unusual as it sounds. First step is to understand what motivates the customer to make such request. Do they know what do they want or what they don't want? What do they think the standard is and why doesn't it suite their needs. Then we need to make sure that customer understands the implications of the diviation, especially if there are long term consequences. The analysis must cover functional and non-functional aspects of the entire architecture and specifically address the diviation part. After that, the customers should get what they want...

Engage in detailed discussions with the client to grasp their specific requirements and the reasons behind their preference for a non-standard design Once you have a clear understanding of the client's needs, assess the feasibility of the non-standard design. Conduct a cost-benefit analysis to determine whether the benefits of implementing the non-standard design outweigh the costs. Propose alternative solutions that might achieve similar outcomes while adhering to more standard architectural practices. :)

A thing to consider is what the client thinks will come of the choice to use a non-standard design. The client could think that they will gain the respect of their peers through being innovative but that could blind them to the fact that this could lead to what are considered unnecessary delays or lack of reliability. They should consider that this will affect their reputation negatively.

Deep Dive: Begin by thoroughly understanding your client's specific needs and motivations for wanting a non-standard design. What are their pain points with existing solutions? What unique features or functionalities are they seeking? Clarify Goals: Ensure you have a clear understanding of the project's overall objectives and how this non-standard design will contribute to achieving them. Prioritize Requirements: Collaborate with your client to prioritize the most critical requirements of the design, both functional and non-functional. Example: A client may want a system that integrates with a niche software they use, which requires a custom API. Understanding why this integration is crucial is essential to tailor the design effectively.

Identify Potential Issues: Non-standard designs can introduce potential risks, such as increased development time, higher costs, integration challenges, and potential maintenance complexities. Identify and assess these risks upfront. Mitigate Risks: Develop strategies to mitigate identified risks. This could involve prototyping, risk analysis, or contingency planning. Transparent Communication: Be transparent with your client about the potential risks and discuss mitigation strategies to ensure they are fully informed and prepared. Example: A custom-built component might lack vendor support. Discuss this with the client and propose alternatives like open-source solutions or building redundancy into the design.

It is important at this stage to really spend time understanding the implications of every design choice. At the early stage we can become blinded to the 'coolness' of bringing something innovative to the world. This is the time though where we need to sit down and write down what are the impacts in various dimensions. - Time to delivery - Do we have enough individuals that can work with this technology, do we need to hire specialists in this area? - How can we prove that what we are doing is the right choice at every stage, can we do quick prototypes? can we observe it working in production? - How easy will it be to maintain, or extend the functionality

Hybrid Approach: Consider if a hybrid approach could satisfy the client's needs. This could involve combining standard components with custom-built elements to strike a balance between customization and practicality. Off-the-Shelf Solutions: Research if any existing off-the-shelf solutions can be modified or customized to meet the client's requirements, even partially. Consult Experts: Seek input from colleagues, industry experts, or consultants to gain insights and explore creative solutions. Example: Perhaps a standard cloud platform can be augmented with custom scripts or integrations to achieve the desired functionality.

Prototyping: Develop prototypes or mockups to visualize the design and gather feedback from the client early on. This allows for adjustments and refinements before committing to the final design. Continuous Feedback: Maintain open communication with the client throughout the design process. Regularly seek their feedback and incorporate it into the design iterations. Flexibility: Be prepared to adapt the design as needed based on feedback, testing results, or changing project requirements. Example: Create a wireframe of the user interface for the client to review and provide input on its functionality and layout.

The client is presumably inviting that you give your expert opinion when presenting the non-standard system architecture. When you are the expert in the room it is important to meet everyone where they are and potentially explain concepts from basic building blocks. This may be difficult at first, especially if you think that it may appear as if you are speaking down to others. But I remind everyone that in this industry we stand on the shoulders of giants and the giants need to play their part in bringing everyone to their level.

In my view, mastering communication is as crucial as technical skills for architects: • Bridges the gap between technical and business worlds • Prevents misunderstandings that can derail projects • Builds trust and credibility with stakeholders • Facilitates smoother decision-making processes • Enables more effective collaboration across teams

Transparent Communication: Keep the client informed of your progress, challenges, and any trade-offs made during the design process. Documentation: Thoroughly document the design, including its architecture, components, interfaces, and any custom elements. This will serve as a reference for future development and maintenance. Education: Educate your client about the technical aspects of the design, explaining why certain choices were made and how they will benefit the project. Example: Regularly schedule meetings or progress reports to discuss design updates and address any questions or concerns the client may have.

Phased Implementation: Consider breaking down the implementation into manageable phases, starting with the most critical components. This allows for early testing and feedback. Thorough Testing: Rigorously test the system throughout the development and implementation process to identify and resolve issues early on. Post-Implementation Support: Offer ongoing support and maintenance to ensure the system functions as expected and can be adapted to future needs. Example: After deploying the initial version of the system, monitor its performance, collect user feedback, and make necessary adjustments to optimize its functionality.