<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by The Solution Architect on Medium]]></title>
        <description><![CDATA[Stories by The Solution Architect on Medium]]></description>
        <link>https://medium.com/@TheSolutionArchitect?source=rss-a251717dc878------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*sP4h1eTMXJ7iFmWKrjVKag.jpeg</url>
            <title>Stories by The Solution Architect on Medium</title>
            <link>https://medium.com/@TheSolutionArchitect?source=rss-a251717dc878------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 13:04:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@TheSolutionArchitect/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Respect My Design Authoritah!]]></title>
            <link>https://medium.com/@TheSolutionArchitect/respect-my-design-authoritah-24521ae6ccf1?source=rss-a251717dc878------2</link>
            <guid isPermaLink="false">https://medium.com/p/24521ae6ccf1</guid>
            <category><![CDATA[design-review]]></category>
            <category><![CDATA[solution-architect]]></category>
            <category><![CDATA[stakeholder-management]]></category>
            <category><![CDATA[design-authority]]></category>
            <category><![CDATA[governance]]></category>
            <dc:creator><![CDATA[The Solution Architect]]></dc:creator>
            <pubDate>Mon, 03 May 2021 17:02:10 GMT</pubDate>
            <atom:updated>2021-05-03T17:02:10.114Z</atom:updated>
            <content:encoded><![CDATA[<p>Presenting solutions at Design Authorities and Review Boards can be a daunting task. After reflecting on my own experiences and also observing that of others, here are my tips on how to navigate such forums.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/781/1*Q0YF4533lAihUtOKMsVGwg@2x.jpeg" /></figure><h3>Avoid surprises in the room</h3><p>After watching me get a kicking several weeks running, a colleague more cultured than I quoted “Victorious warriors win first and then go to war, while defeated warriors go to war first and then seek to win” (Sun Tzu, The Art of War).</p><p>What they were encouraging me to do was to manage my stakeholders better – by only going into the war of a Design Authority if I knew there was a good chance of me leaving with the outcome I expected.</p><p>Identifying impacted stakeholders and engaging early to do design walk-throughs helps make actual Design Authority attendance more of a rubber stamping exercise.</p><h3>Get air cover</h3><p>Some of the more contentious solutions I have presented at Design Authorities have received strong challenge from senior stakeholders. This has been difficult to defend by myself.</p><p>To counter this, it is important to recognise the potential of strong challenge (based on some of the preparatory stakeholder management) and get the right support from people in the room to help fight your corner.</p><h3>Control the situation</h3><p>As with any type of meeting, Design Authorities can sometimes go off on a tangent (even with a good chair). This can be a real time waster and can be a major distraction from gaining approval of a design.</p><p>So setting the context, being clear what approval is being sought and structuring your presentation to limit deviation can help keep things focussed. Delaying relevant questions to the appropriate point of the presentation and sending out of context queries to the parking lot will maximise effective use of time.</p><h3>Don’t get defensive</h3><p>It can be difficult accepting challenge and critique of your work that is coming from people who have had considerably less involvement in the solution than you. This can be particularly difficult to swallow for solutions that have taken a significant amount of time to design, or have looming deadlines.</p><p>Remember, Design Authorities are there for a good reason, to ensure those accountable for solution design can gain confidence in what is being proposed and to provide an opportunity for stakeholders to have their say. As with anything, sometimes a fresh pair of eyes can also allow you to discover things you may not have previously considered – potentially improving the solution. Therefore, allowing others to perform their role and provide their opinions is important.</p><p>Moreover, others challenging your solution is not a bad reflection on you or your work – it is a crucial part of the process and if there weren’t ever any challenges, then there would be little value in holding these meetings.</p><h3>Learn from your experiences</h3><p>Most importantly, regular retrospection of your own personal Design Authority experiences and observing the style/approach that others take will probably not only help to pre-empt and prepare accordingly, but also make future designs more rounded.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24521ae6ccf1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t Hate, Mediate!]]></title>
            <link>https://medium.com/@TheSolutionArchitect/dont-hate-mediate-fbb64cb95515?source=rss-a251717dc878------2</link>
            <guid isPermaLink="false">https://medium.com/p/fbb64cb95515</guid>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[mediation]]></category>
            <category><![CDATA[solution-architect]]></category>
            <category><![CDATA[it]]></category>
            <category><![CDATA[requirements]]></category>
            <dc:creator><![CDATA[The Solution Architect]]></dc:creator>
            <pubDate>Tue, 20 Apr 2021 21:52:22 GMT</pubDate>
            <atom:updated>2021-04-20T22:02:54.777Z</atom:updated>
            <content:encoded><![CDATA[<p>Solution Architects sometimes need to wrestle with conflicting requirements from multiple stakeholders. Add the pressures of designing a solution that adheres to delivery constraints, they often find themselves in a situation where there is no viable solution that satisfies all requirements.</p><p>In order to avoid being blocked, they sometimes need to play the role of a mediator between stakeholders.</p><p>How do Solution Architects (and others in similar roles) approach mediation?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1001/1*YHW5JiUrpVZqoGQ3Ah0MfA@2x.jpeg" /></figure><h3>Is mediation actually required?</h3><p>By doing some basic checks upfront, sometimes the need to mediate can be removed:</p><ul><li><strong>Confirm the raw requirements </strong>– For example two conflicting requirements could be “As a driver, I want a diesel SUV” and “As a David Attenborough fan, I want to minimise my carbon footprint”. But does the first requirement reflect what the stakeholder actually wants, or do they mean “As a driver, I want a vehicle that is robust AND cost effective over 20k miles per year AND I want it to look expensive so I can feel socially accepted within my circle of rich friends”. By challenging how raw a requirement is, sometimes the need to mediate further can go away, as conflicts may disappear due to previously unconsidered solution options becoming available.</li><li><strong>Check for misinterpretation</strong> – when stakeholders have varying degrees of understanding of a given problem, there is a possibility they may ask for something that seems unreasonable. Therefore, re-iterating the problem statement and articulating it in multiple ways can help re-align understanding and potentially help dissolve conflicting requirements that have originated from misinterpretation.</li></ul><h3>Preparation</h3><p>Before presenting the problem to stakeholders, it is wise to stop and think whether there are likely to be difficult conversations.</p><ul><li><strong>Identify the decision makers</strong> – using a list of conflicting raw requirements and constraints to identify impacted stakeholders will help determine who the actual decision makers are. Targeting the decision makers and who or what they are influenced by can reduce wasted effort.</li><li><strong>Evidence </strong>– backing key differentiators between options with tangible evidence will provide decision makers with confidence and allow them to quantify the impact of a decision. This is particularly important when there is no clear “winning” option.</li></ul><h3>Presenting the problem</h3><p>Once the problem is understood and collateral has been prepared, it needs to be presented to decision makers.</p><ul><li><strong>Getting the ambience right </strong>– Depending on how confrontational stakeholders are likely to be about the decision being sought, an approach needs to be outlined as to whether mediating between all impacted parties should be done together at once from the outset, or whether there is benefit in separate walk-throughs to warm people up and set expectations.</li><li><strong>Options review</strong> – Presenting options to stakeholders should be done in an unbiased and neutral manner to ensure their needs are kept equal. This can be achieved by talking around an Options Matrix and providing opportunities for decision makers to talk and voice their opinions – which need to be heard. It is critical to listen at this point.</li><li><strong>Engage and acknowledge</strong> – When key stakeholders are not voicing opinions or are being overpowered by others, it may help to target them directly with questions or request affirmation of the opinion it is assumed they would hold based on their role. Acknowledging points that are being made can also help set the right tone – nobody likes being ignored.</li><li><strong>Recommendation</strong> – Although listening to the views of all stakeholders is of upmost importance, a Solution Architecture recommendation should also be declared – as chances are that nobody will understand the problem in as much depth and they ultimately need to buy into the solutions they design; this will need to be a balanced decision put forward based on facts.</li></ul><h3>Patterns of mediation</h3><p>Now that decision makers are level set and have declared their views, here comes the meat (or plant based alternative) of the MEdiATion (see what I did there). To soften the blow and improve chances of success, some of the following patterns can be considered:</p><ul><li><strong>Mitigation</strong> – For options that result in a solution being exposed to risk, an approach to help mediation could be to identify mitigating factors. This may relax the degree of flexibility around satisfying a given requirement but could still result in the need for sponsors to sign waivers to accept residual risks.</li><li><strong>Path to remediation</strong> – Commonly seen when conflicts relating to time based constraints take priority, an agreement to plan follow-up work to deliver a more strategic solution at a later date can help (where further budget is available).</li><li><strong>Compromise </strong>– Part of a successful negotiation is ensuring that all parties involved exit feeling as if they have got a good deal. So when dealing with conflicts with equal priority / strength, if neither stakeholder wants to give in, then finding common ground through suggesting some give and take can sometimes loosen a deadlock situation.</li><li><strong>Use the flex</strong> – Using the priority/ranking associated with requirements and constraints to judge which solution options should take precedence can sometimes help too. If a solution is being held up because of a conflicting requirement that brings little benefit, then is there value in using precious time to consider it any further.</li></ul><h3>Summary</h3><p>To avoid solution design from being blocked, there is sometimes the need to mediate. Determining whether mediation is actually required can save time, but if there is no alternative, then preparation and presentation are key.</p><p>Whilst mediating, it is good to remember that nobody wants to exit the process feeling like they have lost out or haven’t been considered; so listening and promotion of equality are the skills required to achieve a good outcome in the form of a balanced decision.</p><p>Problem Solved!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fbb64cb95515" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Translator Game]]></title>
            <link>https://medium.com/@TheSolutionArchitect/the-translator-game-192555a1f841?source=rss-a251717dc878------2</link>
            <guid isPermaLink="false">https://medium.com/p/192555a1f841</guid>
            <category><![CDATA[solution-architect]]></category>
            <category><![CDATA[games]]></category>
            <category><![CDATA[business-english]]></category>
            <category><![CDATA[translation-services]]></category>
            <category><![CDATA[it]]></category>
            <dc:creator><![CDATA[The Solution Architect]]></dc:creator>
            <pubDate>Thu, 01 Apr 2021 23:03:58 GMT</pubDate>
            <atom:updated>2021-04-01T23:03:58.019Z</atom:updated>
            <content:encoded><![CDATA[<p>Since inception of the role, Solution Architects have been responsible for articulating complex paradigms to non-technical stakeholders in plain Business English. They have also been responsible for defining technical solutions based on requirements usually in the form of desired end user features.</p><p><strong>Solution Architects can be seen as <em>translators</em>.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UpChurXYGZtDeM4Y1kmRJg.jpeg" /><figcaption>Wouldn’t life be easier if you could Google Translate between “Technical Jargon” and “Business English”?</figcaption></figure><p>Translating “Technical Jargon” into “Business English” isn’t something one can do with a dictionary, or Google Translate; it’s something that is learned through experience and practice.</p><p>But how can a Solution Architect enhance their translation skills? Using concepts from games and puzzles to target the learning style of a given stakeholder may help…</p><h3>Articulate!</h3><p>Playing a game of <a href="https://www.drumondpark.com/articulate_cards">Articulate!</a> is comparable to situations a Solution Architect will inevitably find themselves in – when they are asked to explain a technical concept to a non-technical stakeholder with little or no notice. When the imaginary egg-timer starts, the Solution Architect is pressured into translating on the fly and they somehow need to formulate a comprehensible response without any jargon – before they lose their credibility (OK, maybe that’s a bit harsh). Observing how Articulate! players go about their business to describe words, Solution Architects could increase their translation success by using:</p><ul><li><strong>Synonyms:</strong> Articulate! players often start their sentence with “It’s another word for…”. Likewise, replacing technical terms with similar, more accessible, simple words the audience will be comfortable with will improve chances of them understanding.</li><li><strong>An Analogy:</strong> During UK Government Covid-19 pandemic briefings, <a href="https://www.gov.uk/government/people/jonathan-van-tam">Prof Jonathan Van-Tam</a> would often use analogies. Assuming he would be an damn good Articulate! player that starts his descriptions with “It’s like the… equivalent of…”, he has demonstrated that using parallels of commonly understood real world concepts can allow stakeholders to map complex paradigms to a relatable model. Using this in a technical translation is something that can really grab an audience and can be used to effectively cascade a translation onwards to stakeholders of stakeholders.</li><li><strong>No shortcuts: </strong>Acronyms/abbreviations/initialisms are rarely used during Articulate!, but they appear frequently in conversations in IT departments. Declaring the fully expanded form of these terms up-front to avoid confusion can reduce the effort a listener needs to put into translating themselves. Particularly when there are new starters in the audience, who may not feel confident to speak up and ask what terminology (which may be specific to a business) actually means.</li></ul><p>Although a Solution Architect’s ability to articulate can get them a long way, not everyone will be receptive to an Auditory style, and it therefore helps to add another dimension to translations for audience members not engaged by words.</p><h3>Pictionary</h3><p>Similar to the Articulate scenario, playing <a href="https://www.mattelgames.com/en-us/family/pictionary">Pictionary</a> can also be comparable to situations Solution Architects will find themselves in – the difference being they have access to either a whiteboard, scrap paper, or even better a presentation deck with a pre-baked translation. Like Pictionary, this can result in the focus of the audience being taken away from the drawers body language (<em>drawers</em> of the artistic kind, not the underpants or furniture used for storage kind) – which can be a useful distraction for Solution Architects of the blagging variety to cook up some words. The Visual dimension allows a translation to be delivered with:</p><ul><li><strong>Animation: </strong>As Pictionary enforces a picture to be drawn live, this allows drawers to use movement for emphasis and to maintain focus on certain words or syllables. Putting a detailed diagram in front of people will often result in audience members tuning out or trying to shortcut / read ahead to derive their own interpretation of the picture (de-valuing the accompanying words used to articulate). Whereas, live drawing, or making use of animated slides, allow presenters to dictate the pace and keep audience members in sync – providing more control of the situation and focussing attention on the part of the diagram actually being discussed at any given moment.</li><li><strong>Context Setting:</strong> Although delving right into the detail with a diagram may appear to be optimal, making sure an audience is level-set through a pre-amble – defining where in the bigger picture a given diagram fits in can provide a useful warm-up, whilst also reducing confusion. Just like a Pictionary player drawing a circle to represent a tyre would benefit from drawing the basic outline of a car to give the circle context, a Solution Architect likewise needs to show where in the IT or business landscape their solution is situated.</li><li><strong>Range of Detail: </strong>Drawing a single diagram that spans many levels of detail can often result in left field questions being asked as audience members are overwhelmed with the wealth of information being presented. Persisting at a single level of detail at a time, and “zooming-in” to boxes represented in separate sub-diagrams can once again help to control the conversation. Extending on the example of a Pictionary player drawing a tyre, they may be trying to actually draw a tyre valve or tyre tread; representing this proportionally on the same diagram as a car will clearly be difficult, and this is where they may leverage a “zoom-in” view. Similar to Context Setting, this ensures the presenter isn’t getting taken down a rabbit hole with conversations that are not relevant to the level of detail intended to be working at.</li><li><strong>Notation:</strong> Working as a team during a game of Pictionary, both the drawer and guessers benefit from being on the same wavelength to the extent they perhaps have a shorthand for how things like a “zoom-in to next level of detail” is represented. Likewise, having consistency within diagrams with a common style or theme can improve alignment in interpretation. For example, what do the direction of arrows on informal architecture diagrams represent — is it Data Flow or Requestor-Receiver or Route of Traffic? Using defined styles of lines with a legend and descriptions can help solve this. Also, having common attributes for boxes such as names and a one sentence description assist in improving understanding whilst reducing ambiguity and follow up queries.</li></ul><p>With regards to Range of Detail (Abstraction) and Notation, this is something that the <a href="https://c4model.com/">C4 Model</a> promotes a team to define; adopting a framework like this can drive standardisation not just for the diagrams of an individual, but for a whole team – which will also benefit stakeholders who just need to learn how to read one style of diagram.</p><h3>Lego</h3><p>If an attempt to articulate something with words (Auditory) or pictures (Visual) really hasn’t engaged an audience, there may be a need to explore something more hands-on (Kinesthetic). This can be likened to playing <a href="https://www.lego.com/en-gb">Lego</a>:</p><ul><li><strong>Prototypes: </strong>As Lego players will often go through a discovery phase where they will build a basic no-frills example to allow them to determine whether it fits their vision, the same also happens in Solution Architecture. A prototype can be used as a tangible sample of the problem being translated, which stakeholders can use to more accurately assess benefits and determine downstream impacts (such as alignment to Customer Experience or quality goals).</li><li><strong>Examples:</strong> Lego players may buy sets to ensure they have the requisite pieces to complete a pre-defined model they are building, or they may view pictures of what other Lego players have built for inspiration. Likewise, if there are existing real-world instances of a solution being translated (e.g. similar implementations within the industry or by competitors), they can often be used to shortcut the need for a prototype.</li><li><strong>Skip the English: </strong>Since Lego is a universal language in its own right, players do not need to use mortal words to get their point across. When translating from Business English into Technical Jargon, it can help to demonstrate ideas as pseudo code, or even a proof-of-concept for an implementing team to understand a solution.</li></ul><p>It is however only worth going through the effort of this if there is sufficient value in doing so. If something can be easily articulated with words or simple diagrams, is there any need to go beyond this with additional artefacts?</p><h3>Summary</h3><p>Through observing how game and puzzle players approach translation, Solution Architects can enhance their own skills to increase success in conversations with stakeholders.</p><p>Using a range of techniques across learning styles is also important to maintain accessibility, but this needs to be balanced with the value in the effort burned to translate (only over-engineer a translation if there is benefit in a stakeholder understanding it).</p><p>But the biggest take-away is… to play more Lego! Problem solved.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=192555a1f841" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>