<?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 Jethro Sloan on Medium]]></title>
        <description><![CDATA[Stories by Jethro Sloan on Medium]]></description>
        <link>https://medium.com/@jdksloan?source=rss-d0ea8d6ffc29------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*hiY0wOB6wD1d3OkllFi8ZQ.png</url>
            <title>Stories by Jethro Sloan on Medium</title>
            <link>https://medium.com/@jdksloan?source=rss-d0ea8d6ffc29------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 19:18:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jdksloan/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[SIMPLE Solutions]]></title>
            <link>https://medium.com/@jdksloan/simple-solutions-022636334858?source=rss-d0ea8d6ffc29------2</link>
            <guid isPermaLink="false">https://medium.com/p/022636334858</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-design]]></category>
            <category><![CDATA[solution-architecture]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-architecture]]></category>
            <dc:creator><![CDATA[Jethro Sloan]]></dc:creator>
            <pubDate>Tue, 08 Jul 2025 13:25:17 GMT</pubDate>
            <atom:updated>2025-07-08T13:25:17.086Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nEcFMzR0HohfN0Fe5gNzIQ.jpeg" /></figure><h3>Introduction</h3><p>In modern software principles we often hear the word simple, keep it simple stupid (<a href="https://en.wikipedia.org/wiki/KISS_principle">KISS</a>) for example, but what does “simple” really mean? I decided to research this topic and hosted a discussion to find out what the industry thinks the meaning of a simple solution is in todays climate. From my own experience, research, and discussions, I have come up with a working definition of simple, packaged into an acronym as we all know the software industry loves a good acronym.</p><h3>SIMPLE</h3><p><strong>S</strong> — Straightforward</p><p><strong>I</strong> — Iterative</p><p><strong>M</strong> — Manageable</p><p><strong>P</strong> — Single Purpose</p><p><strong>L</strong> — Legible</p><p><strong>E</strong> — Extensible</p><h4>Straightforward</h4><p>The simpler it is to explain, the simpler it is to understand. Any ambiguity in the requirements will lead to ambiguity in the implementation. Solutions are always a journey from point a to point b. Think in terms of modern software development which mostly involves receiving data, transforming it, and sending it to the next part of the system. The more difficult the journey is to explain, the harder it will be to keep track of. Defining a concise, direct, and confined solution within the correct boundaries will lead to a better implementation.</p><h4>Iterative</h4><p>Once you have a straightforward description of the problem and solution, seek the minimum viable product (<a href="https://en.wikipedia.org/wiki/Minimum_viable_product">MVP</a>). Reducing the barrier of entry means you can deliver value faster. How often do we see great ideas with real business value get diluted by scope overload? What begins as a simple idea soon becomes an unreachable utopian mess of grand delusion. Iterative also refers to the way in which you do something. Solution design is more than just writing software. Working in a way that you can repeat consistently, builds confidence in the process and help to keep it transparent within the organisation.</p><h4>Manageable</h4><p>When designing a solution, the more transparent it is within your organisation, the simpler it is to maintain. A simply managed solution encompasses more than just code or infrastructure. As seen over the years, people, transparency, and technological choices are overlooked in favour of what is currently trending or easy. A great example of this is the overuse of micro-service architecture. When thinking about micro-services it’s easy to think about how smaller pieces would be less complicated to reason about, I mentioned that exact point above, or how parallelising workflows would increase performance but what about the management of those smaller services? If you have a team of only a few people, does having a large amount of services make sense? From my experience it does not. I see many teams struggle to create value because they are tied down to maintenance. I myself fell into this exact trap when I created a micro-service architecture.</p><h4>Single Purpose</h4><p>Solutions need to have a purpose in order solve a problem. In my experience when a new feature or system is being designed, it usually starts off as this big idea with no boundaries or clarity. What is often seen with these situations is that a great idea is presented, and after a few sessions we’ve lost the original purpose of the idea and now we have multiple different purposes. Ideas create other ideas which is healthy and expected and there is nothing wrong with new ideas being generated out of others. The problem comes in when you take on multiple ideas in the same solution space. Rather have more than one solution in this instance and keep each one confined to its original purpose. When you reach this point, the solution becomes clear and simple to manage.</p><h4>Legible</h4><p>Readability is subjective, especially in the software industry. Different programming, domain, and business languages add to our cognitive complexity. A simple solution should be easy to read and understand in the context of the domain. The goal of Domain Driven Development (<a href="https://en.wikipedia.org/wiki/Domain-driven_design">DDD</a>) is to create ubiquitous language around a domain, I suggest going further and extending this to solution design as well. When describing the solution high level everyone should be able to understand what it means. When choosing what programming language or technology to use for the solution, it’s easy to get pulled into using the latest trends. While new tools might provide good solutions overall, if your organisation doesn’t use that programming language or doesn’t have the means to buy-in to the new technology, this will lead to a greater level of complexity. When designing the software itself, using well known patterns will increase the readability of the code, thusly reducing the amount of cognitive load needed to reason about its functionality.</p><h4>Extensible</h4><p>There are many schools of thought around what state we should leave a solution in to consider it complete. Being extensible doesn’t mean it should be in the extended state, rather keep it open to be extended. If there is a clear path to extend a solution in the future, then there is an easy way to reason about evolution. Not all evolutions are obvious from the beginning so rather than extending it for the sake of extending, we should aim to never close the door on an evolutionary path. This does not mean an inventory service should be able to evolve into a login service, it simply means that inventory might change in the context of the domain over time and we don’t want to inhibit the natural evolution of that domain. Extensible over extendable because we never know how business requirements evolve over time.</p><h3>Investigation</h3><p>I recently hosted a session at Xebia Knowledge Exchange and asked a group of 24 people in our industry this question. I divided them into groups of 6 using the liberating structures format. From this, I found the following words were used to describe what simple meant to them in the context of solution design space.</p><h4>Group 1</h4><ul><li>Effective/Efficient</li><li>Low rules/cognitive-load</li><li>Contextual</li></ul><h4>Group 2</h4><ul><li>Understandable</li><li>Intuitive</li><li>Compact</li></ul><h4>Group 3</h4><ul><li>No unused functionality</li><li>Low interaction</li><li>Cohesive</li></ul><h4>Group 4</h4><ul><li>Follows pattern</li><li>Small</li><li>Explainable</li></ul><h4>Group 5</h4><ul><li>Simple ≠ easy</li><li>Adaptable</li><li>Atomic</li></ul><h4>Group 6</h4><ul><li>Uncluttered</li><li>Structured</li><li>Straightforward</li></ul><p>This session proved to be a really interesting discussion because the general consensus was very close to my own ideas and everyone had some definition they understood and used. The main takeaway for the group was that simple ≠ easy. Secondly, the biggest discrepancy between my own ideas and the groups was that they didn’t have any iterative idea about breaking up the problem into smaller repeatable pieces.</p><h3>Conclusion</h3><p>I can conclude that although we all use different words to describe “simple”, we all have a very similar idea about what it means. There is however, a lack of a strong definition. The above definition represents a line in the sand to bring focus to what we really want to consider simple, how that translates to our industry and how we all should strive to create simple solutions. The main issue with using language to describe language is we can pick each word and dive into its meaning, language is subjective. So instead of thinking too much about each word, the acronym I have provided serves as a reference point. Each word is based on experiences I have had in the solution landscape and think that many others share these experiences. I believe that using this as a foundation will yield better solutions for the future.</p><p><em>This idea started out as an investigation and discussion therefore I encourage anyone who reads this to leave a comment. I would love to hear what you think “simple” means?</em></p><p>Photo by <a href="https://unsplash.com/@julianhochgesang?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Julian Hochgesang</a> on <a href="https://unsplash.com/photos/brown-wooden-quote-wall-decor-XFoVaOxv8LU?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Unsplash</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=022636334858" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Unwritten Playbook: Leading Without a Title]]></title>
            <link>https://medium.com/@jdksloan/the-unwritten-playbook-leading-without-a-title-50c5a7a19a00?source=rss-d0ea8d6ffc29------2</link>
            <guid isPermaLink="false">https://medium.com/p/50c5a7a19a00</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[consulting]]></category>
            <category><![CDATA[advice]]></category>
            <category><![CDATA[software-consulting]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Jethro Sloan]]></dc:creator>
            <pubDate>Mon, 07 Jul 2025 09:42:05 GMT</pubDate>
            <atom:updated>2025-07-07T09:42:05.968Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0j9TfihVuUsPxaxTeIfSQw.jpeg" /></figure><h3>Leading Without a Title: The Consultant’s Guide to Stealth Influence</h3><p>“Why should we listen to you?” the grizzled IT director asked bluntly, leaning back in his chair. “You’ve been here three weeks. Some of us have been running these systems for fifteen years.”</p><p>Twenty faces turned to watch my response. As the consultant brought in to lead a critical transformation programme, I had responsibility for outcomes but absolutely no authority over the people who would determine success or failure.</p><p>It was a fair question — one that gets to the heart of the consultant’s paradox. We’re hired to drive significant change within organisations where we have no formal power, no place on the org chart, and often, as this IT director pointedly noted, far less institutional knowledge than the people we’re trying to influence.</p><p>Welcome to the fifth instalment of “The Unwritten Playbook,” where I’m sharing the consulting truths they don’t teach you in formal training. Today, we’re exploring perhaps the most crucial consulting skill: how to lead effectively when you have responsibility without authority.</p><h3>The Authority Illusion: Why Formal Power Is Overrated</h3><p>One of the most liberating realisations in my consulting career came when I understood that formal authority — the kind that comes with a title and direct reports — is far less powerful than it appears.</p><p>I’ve watched senior executives issue directives that were quietly ignored. I’ve seen CEOs announce transformations that never materialised beyond the town hall meeting. Conversely, I’ve witnessed junior staff members with no formal authority drive substantial change through their influence skills.</p><p>The authority illusion persists because:</p><ol><li><strong>Organisational charts measure reporting lines, not influence flows</strong><br>→ Who someone reports to rarely determines who they actually listen to<br>→ Expertise and trust often trump positional authority</li><li><strong>Compliance is not commitment</strong><br>→ Authority can compel behaviour but not engagement<br>→ Forced actions without buy-in typically produce malicious compliance</li><li><strong>Authority creates resistance</strong><br>→ Formal directives often trigger defensive reactions<br>→ The more authority is asserted, the more creative the resistance becomes</li><li><strong>Authority is contextual</strong><br>→ Most power is domain-specific (technical, business, political)<br>→ Authority in one domain rarely transfers effectively to others</li></ol><p>I once consulted for a manufacturing firm where the CIO issued a mandate for all departments to adopt a new enterprise system. Six months later, most departments had nominally “implemented” the system — but continued to run parallel shadow processes that rendered the official system a glorified data entry exercise. Authority had produced compliance without commitment.</p><p><strong>Unwritten Rule 1️⃣:</strong> The most effective leaders in organisations are not necessarily those with the most impressive titles, but those with the most extensive influence networks.</p><h3>Influence Currency: What You Can Trade When You Can’t Give Orders</h3><p>If authority is an overvalued asset, what alternative currencies can consultants use to influence outcomes? This question led me to develop what I call the “influence currency” framework — the five forms of capital consultants can accumulate and spend.</p><ol><li><strong>Expertise Capital</strong><br>→ Built through: Demonstrating relevant knowledge, solving problems, offering insights<br>→ Spent by: Providing guidance, offering options, explaining implications<br>→ Strengthened when: Your expertise helps others succeed<br>→ Depleted when: You overstate your knowledge or apply it inappropriately</li><li><strong>Relationship Capital</strong><br>→ Built through: Active listening, demonstrating empathy, following through on commitments<br>→ Spent by: Asking for support, requesting information, seeking advocacy<br>→ Strengthened when: You invest in others’ success without immediate return<br>→ Depleted when: You take more than you give or violate trust</li><li><strong>Process Capital</strong><br>→ Built through: Creating clarity, facilitating effectively, managing complexity<br>→ Spent by: Defining approaches, establishing frameworks, structuring decisions<br>→ Strengthened when: Your processes make progress visible and inclusive<br>→ Depleted when: Your processes become bureaucratic or self-serving</li><li><strong>Outcome Capital</strong><br>→ Built through: Delivering results, creating business value, solving meaningful problems<br>→ Spent by: Setting direction, raising standards, challenging the status quo<br>→ Strengthened when: You connect actions to meaningful outcomes<br>→ Depleted when: You prioritise activity over impact</li><li><strong>Political Capital</strong><br>→ Built through: Understanding stakeholder motivations, aligning with strategic priorities<br>→ Spent by: Navigating resistance, securing resources, gaining senior support<br>→ Strengthened when: You help others achieve their objectives alongside yours<br>→ Depleted when: You create win-lose situations or ignore political realities</li></ol><p>The art of influence is knowing which currency to use in which situation. With the sceptical IT director I mentioned earlier, I built expertise capital by asking thoughtful questions about their systems before suggesting changes. I accumulated relationship capital by acknowledging their team’s historical achievements. Only then could I spend outcome capital by painting a compelling picture of future benefits.</p><p><strong>Unwritten Rule 2️⃣:</strong> Consultants without authority must consciously build and strategically spend multiple forms of influence currency.</p><h3>Decision Mapping: Finding Where Decisions Really Happen</h3><p>To influence effectively, you must first understand how decisions actually flow through an organisation — which is rarely how they’re supposed to flow on paper.</p><p>On a government transformation programme, I spent my first three weeks creating a decision map that revealed:</p><ul><li>The published governance structure showed all technology decisions flowing through the CTO</li><li>In reality, most decisions were pre-determined in unofficial “pre-meetings”</li><li>The true decision gateway was the CTO’s technical architect, who filtered what reached the CTO</li><li>Business stakeholders had veto power through an informal escalation to the COO</li></ul><p>This mapping exercise completely changed my influence strategy, shifting focus from formal committee presentations to the informal networks where decisions were actually shaped.</p><p>To create your own decision map:</p><ol><li><strong>Identify the critical decision types for your project</strong><br>→ Technical approach decisions<br>→ Resource allocation decisions<br>→ Timeline/priority decisions<br>→ Scope change decisions<br>→ Risk acceptance decisions</li><li><strong>For each type, document the formal and informal processes</strong><br>→ Who initiates<br>→ Who consults<br>→ Who influences<br>→ Who decides<br>→ Who ratifies<br>→ Who implements</li><li><strong>Look for patterns across recent similar decisions</strong><br>→ Where did they originate?<br>→ Where did they stall?<br>→ Where were they modified?<br>→ Who had effective veto power?</li><li><strong>Identify the decision accelerators and blockers</strong><br>→ Which individuals can move decisions forward?<br>→ Which groups can delay or derail decisions?<br>→ What unstated criteria determine outcomes?</li></ol><p>The resulting map becomes your influence navigation system, showing where to invest your time and which relationships to prioritise. Often, the most important person to influence isn’t the highest-ranking, but the one with the most connections to other decision nodes.</p><p><strong>Unwritten Rule 3️⃣:</strong> Formal decision processes tell you who approves decisions; informal networks tell you who shapes them. Focus your influence efforts on the latter.</p><h3>The RAPID Revelation: Clarifying Decision Rights Without Offending Anyone</h3><p>One of the most common sources of project failure is unclear decision rights. People wait for approvals no one is authorised to give. Decisions made in meetings get unmade afterwards. Multiple groups believe they have final say over the same issues.</p><p>The RAPID framework (Recommend, Agree, Perform, Input, Decide) creates clarity without challenging the existing authority structure. Rather than reorganising power, it simply makes existing power flows explicit.</p><p>I introduced RAPID to a financial services client where decision paralysis was delaying a critical system replacement. The executive team believed they were empowering their managers to make decisions, while the managers were waiting for executive approval. Meanwhile, compliance and risk teams weren’t clear on when they had veto rights versus advisory input.</p><p>The breakthrough came when we visualised the current decision process for system changes:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*WbgTJW1pMS9i2oe2h0-YLA.png" /></figure><p>By explicitly mapping who had which role in which types of decisions, we created clarity without directly challenging anyone’s authority. The CIO could still be the final decision-maker, but everyone understood what that meant and didn’t mean.</p><p>The power of RAPID is that it feels like a process improvement rather than a power redistribution, making it palatable even in highly political environments.</p><p><strong>Unwritten Rule 4️⃣:</strong> Unclear decision rights cause more project failures than technical issues. Clarify who plays which role without challenging the underlying authority structure.</p><h3>Influence Strategies: The Six Paths of Persuasion</h3><p>While authority relies primarily on compliance, influence works through multiple channels. Research in social psychology has identified six primary influence strategies that work without formal authority:</p><ol><li><strong>Rational Persuasion</strong><br>→ Leveraging data, logic, and evidence<br>→ Most effective with: Analytical personalities, technical experts, risk-focused stakeholders<br>→ Example technique: “The three key factors that support this approach are…”</li><li><strong>Inspirational Appeal</strong><br>→ Connecting to values, aspirations, and purpose<br>→ Most effective with: Senior leaders, vision-focused stakeholders, change champions<br>→ Example technique: “This approach allows us to finally deliver the customer experience we’ve always aspired to…”</li><li><strong>Consultation</strong><br>→ Involving others in shaping the approach<br>→ Most effective with: Implementation teams, detail-oriented stakeholders, potential resistors<br>→ Example technique: “Before finalising this, I’d like to get your input on how this would work in practice…”</li><li><strong>Relationship Building</strong><br>→ Creating trust and personal connection<br>→ Most effective with: Long-term stakeholders, relationship-oriented cultures, influence gatekeepers<br>→ Example technique: “I understand this is challenging given what happened with the last project. What would make you comfortable this time?”</li><li><strong>Exchange</strong><br>→ Finding mutual benefit through trading value<br>→ Most effective with: Resource controllers, pragmatic stakeholders, competing priorities<br>→ Example technique: “If we prioritise this component first, how could we help address your department’s reporting needs?”</li><li><strong>Coalition Building</strong><br>→ Mobilising support from multiple stakeholders<br>→ Most effective with: Distributed decision environments, consensus cultures, complex stakeholder landscapes<br>→ Example technique: “Both the operations team and finance have identified this as their top priority…”</li></ol><p>The most skilled influencers adapt their approach to the specific stakeholder and context. When I work with technical teams, I lead with rational persuasion. With executives, I emphasise inspirational appeals tied to strategic goals. With potential resistors, consultation often defuses opposition before it forms.</p><p>On a particularly challenging healthcare project, I mapped each key stakeholder to their preferred influence channel:</p><ul><li>Clinical Director: Rational persuasion focused on patient outcomes</li><li>Operations Manager: Exchange that addressed operational pain points</li><li>IT Security: Consultation that acknowledged their expertise</li><li>Finance: Rational persuasion with clear ROI calculations</li><li>Nursing Staff: Inspirational appeal to improved patient care</li></ul><p>This targeted approach helped secure support across diverse stakeholder groups without relying on formal authority.</p><p><strong>Unwritten Rule 5️⃣:</strong> Match your influence strategy to the stakeholder’s values, thinking style, and position. The right approach with the wrong person is still the wrong approach.</p><h3>Becoming Indispensable: The Art of Solving Problems No One Else Can</h3><p>The ultimate form of influence without authority comes from making yourself indispensable by solving problems that nobody else can or will address.</p><p>I learned this lesson from a junior consultant who had remarkable influence despite her lack of seniority. While the rest of us focused on our assigned workstreams, she consistently identified and solved integration problems that fell between defined responsibilities. She became the unofficial “fixer” that everyone — including executives — turned to when facing complex challenges.</p><p>To position yourself as indispensable:</p><ol><li><strong>Identify the gaps between formal responsibilities</strong><br>→ Look for problems that cross organisational boundaries<br>→ Pay attention to issues everyone complains about but no one addresses<br>→ Notice the “white space” in project plans where assumptions hide</li><li><strong>Develop integrative expertise</strong><br>→ Build knowledge that connects technical and business domains<br>→ Learn the languages of different specialisations<br>→ Understand how systems interact, not just how they function individually</li><li><strong>Cultivate your unique contribution</strong><br>→ What perspective do you bring that others don’t?<br>→ What problems are you particularly good at solving?<br>→ What difficult conversations can you facilitate that others avoid?</li><li><strong>Create visibility for “invisible” problems</strong><br>→ Articulate unspoken risks or assumptions<br>→ Connect symptoms to systemic causes<br>→ Translate between stakeholder viewpoints</li><li><strong>Deliver disproportionate value in unexpected areas</strong><br>→ Solve small but irritating problems that create goodwill<br>→ Produce insights that help others succeed<br>→ Create tools or frameworks that outlast your involvement</li></ol><p>On a troubled SAP implementation, I built influence not through my assigned role leading the technical work-stream, but by creating a cross-functional issue resolution process that no one had asked for but everyone needed. This unofficial contribution became more valuable than my formal deliverables, creating influence that extended far beyond my nominal responsibility.</p><p><strong>Unwritten Rule 6️⃣:</strong> Authority comes from above, but indispensability grows from below — by solving problems others can’t or won’t address.</p><h3>Stealth Leadership: Influencing Without Fingerprints</h3><p>Sometimes the most effective leadership is invisible. The highest form of influence is when others believe the ideas were theirs all along.</p><p>I worked with a masterful consultant who never presented his own ideas directly. Instead, he would say, “I was thinking about what John mentioned last week…” or “Building on Sarah’s approach…” He would carefully seed concepts in one-on-one conversations, then publicly attribute elements to different stakeholders when presenting the synthesised solution.</p><p>The art of stealth leadership includes:</p><ol><li><strong>Planting seeds rather than fully-grown plants</strong><br>→ Share partial ideas that others can complete<br>→ Ask leading questions that guide thinking<br>→ Offer options rather than recommendations</li><li><strong>Distributing ownership broadly</strong><br>→ Give credit generously and specifically<br>→ Create opportunities for others to contribute visibly<br>→ Position yourself as the integrator, not the originator</li><li><strong>Leading from behind</strong><br>→ Create frameworks for others to fill<br>→ Facilitate rather than direct<br>→ Ask the questions that need asking</li><li><strong>Making others the heroes</strong><br>→ Ensure key stakeholders receive recognition<br>→ Prepare others to present successfully<br>→ Focus attention on team achievements, not your contribution</li></ol><p>The most elegant use of stealth leadership I’ve witnessed was during a contentious ERP implementation. The lead consultant never once directly advocated for her preferred approach. Instead, she created a series of workshops where stakeholders “discovered” the solution she had envisioned from the beginning — but with full buy-in because they believed they had created it themselves.</p><p><strong>Unwritten Rule 7️⃣:</strong> The most powerful influence often leaves no fingerprints. True leadership success is when others don’t need to be reminded who led them.</p><h3>Case Study: Turning Around a Failing Programme Through Influence</h3><p>Let me share a real example that integrates these principles:</p><p>I joined a government digital transformation programme that was significantly behind schedule and facing potential cancellation. As an external consultant with no formal authority, I needed to influence a complex stakeholder environment that included:</p><ul><li>A defensive programme team convinced their approach was correct</li><li>Frustrated business owners who had lost confidence</li><li>A governance board ready to pull the plug</li><li>Technical specialists working in silos</li><li>External suppliers protecting their contracts</li></ul><p>Rather than pushing my recommendations immediately, I applied systematic influence:</p><ol><li><strong>First, I created a decision map</strong><br>→ Identified the true decision-makers (not the nominal ones)<br>→ Mapped the informal influence networks<br>→ Located the respected voices in each stakeholder group</li><li><strong>Next, I built targeted influence currency</strong><br>→ With technical teams: Expertise currency through thoughtful questions<br>→ With programme leadership: Process currency by facilitating better governance<br>→ With business owners: Relationship currency through dedicated listening sessions<br>→ With governance board: Outcome currency by refocusing on business value</li><li><strong>Then, I applied tailored influence strategies</strong><br>→ For analytical stakeholders: Rational persuasion with data on current trajectory<br>→ For operational teams: Consultation on implementation challenges<br>→ For senior leaders: Inspirational appeal to original programme vision<br>→ For resistant middle management: Exchange that addressed their pain points</li><li><strong>Finally, I practised stealth leadership</strong><br>→ Created a collaborative recovery planning process<br>→ Ensured each stakeholder group contributed visibly<br>→ Positioned myself as integrator rather than saviour<br>→ Distributed credit for the turnaround widely</li></ol><p>The programme successfully reset without finger-pointing or dramatic personnel changes. Within three months, we had rebuilt confidence and established a new baseline for delivery. Key stakeholders who had been calling for cancellation became advocates for the refreshed approach — and most believed the solution had emerged from their collective expertise rather than from external intervention.</p><h3>Conclusion: The Quiet Power of Influence</h3><p>Leadership without authority isn’t just a consulting skill — it’s the future of leadership itself. As organisations become more networked and less hierarchical, the ability to influence across boundaries becomes more valuable than the ability to direct from above.</p><p>For consultants, this shift plays to our natural advantages. We’ve always operated without formal authority, relying instead on expertise, relationships, and the value we create. The techniques that once seemed like compensatory skills for our lack of authority are now the primary toolkit for modern leadership.</p><p>The most successful consultants I’ve known share a paradoxical quality: they drive significant change while leaving minimal evidence of their personal influence. They don’t need to be the loudest voice or the named authority. They measure their success not by how indispensable they become, but by how effectively the organisation can sustain positive change after they leave.</p><p>As you develop your consulting career, invest consciously in your influence capabilities. Map decision networks, build diverse influence currencies, tailor your approach to different stakeholders, and practice the art of invisible leadership. These skills will serve you not just in consulting, but in any leadership role you may take on.</p><p>In the next post in this series, I’ll explore “The Modern Consultant’s Arsenal: Tools, Techniques and AI Superpowers” — the unwritten rules of working smarter with the technologies and methods that multiply your effectiveness.</p><p>Until then, remember that true influence isn’t measured by how many people do what you tell them, but by how many important changes happen because you were there.</p><p><em>What influence challenges have you faced as a consultant without formal authority? Share your experiences in the comments below!</em></p><p>Photo by rob walsh on Unsplash</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=50c5a7a19a00" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Unwritten Playbook: Winning as a Team]]></title>
            <link>https://medium.com/@jdksloan/the-unwritten-playbook-winning-as-a-team-a18b89927f77?source=rss-d0ea8d6ffc29------2</link>
            <guid isPermaLink="false">https://medium.com/p/a18b89927f77</guid>
            <category><![CDATA[advice]]></category>
            <category><![CDATA[software-consulting]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[consulting]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Jethro Sloan]]></dc:creator>
            <pubDate>Mon, 30 Jun 2025 08:56:10 GMT</pubDate>
            <atom:updated>2025-06-30T08:56:10.553Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZvWLZt3Mv5iy_txS-Q5fpQ.jpeg" /></figure><h3>Team Whispering: Navigating the Human Dynamics No One Prepared You For</h3><p>“We’ve gone through three project managers already,” the client director told me casually as we walked to my first team meeting. “The team can be… challenging. But I’m sure you’ll be fine.”</p><p>My stomach tightened. The technical brief had mentioned nothing about team problems — only a seemingly straightforward system migration that was now six months behind schedule.</p><p>When I entered the room, the temperature seemed to drop ten degrees. Twenty pairs of eyes assessed me with expressions ranging from scepticism to outright hostility. One developer was pointedly wearing headphones. Two architects sat as far from each other as the room allowed. The business analyst was frantically documenting everything as if preparing evidence for a future trial.</p><p>No technical challenge could explain why three PMs had already failed. This was about human dynamics — the aspect of consulting they never adequately prepare you for.</p><p>Welcome to the fourth instalment of “The Unwritten Playbook,” where I’m sharing the consulting truths learned through hard-won experience. Today, we’re exploring the hidden skill of “team whispering” — how to read, navigate, and positively influence the human systems that ultimately determine project success.</p><h3>Team Temperature Reading: Spotting Phase Indicators in the First Meeting</h3><p>While technical consultants meticulously assess system architectures, we often miss the equally critical architecture of human dynamics. The ability to quickly diagnose a team’s developmental stage gives you an immediate advantage.</p><p>In my first decade of consulting, I misdiagnosed team dynamics repeatedly. I’d mistake polite formality (forming) for healthy collaboration (performing), or interpret passionate debate (storming) as dysfunctional conflict. These misreads cost me dearly in credibility and effectiveness.</p><p>Through painful experience, I’ve developed a “team temperature” assessment that I now conduct in my first interactions with any client team:</p><p><strong>Physical Indicators:</strong></p><ul><li>Seating arrangements (clustered or dispersed?)</li><li>Body language (open or defensive?)</li><li>Eye contact patterns (who looks at whom?)</li><li>Energy level (engaged or withdrawn?)</li><li>Who arrives together and leaves together</li></ul><p><strong>Communication Patterns:</strong></p><ul><li>Who speaks first and last?</li><li>Who interrupts whom?</li><li>Which topics create tension or animation?</li><li>Are disagreements expressed directly or through passive aggression?</li><li>How are decisions actually made versus how they’re supposed to be made?</li></ul><p><strong>Team Artefacts:</strong></p><ul><li>State of documentation (collaborative or protective?)</li><li>Email communication styles (inclusive or selective?)</li><li>Meeting structures (rigid or flexible?)</li><li>How success is measured and discussed</li></ul><p>For example, in that challenging team I mentioned earlier, I quickly observed:</p><ul><li>Technical staff sat on one side, business staff on the other</li><li>Eye contact happened within subgroups but rarely across them</li><li>Technical discussions created animated debate while timeline discussions were met with silence</li><li>Documentation was extensive but focused on protecting individual responsibilities</li></ul><p>These indicators told me this team was stuck in storming phase, with tribal divisions and trust issues that no amount of technical expertise alone would solve.</p><p><strong>Unwritten Rule 1️⃣:</strong> Your first job at any client is to diagnose the team’s developmental stage — this determines everything from how you introduce ideas to how you handle disagreements.</p><h3>The Four Faces of Teams: Recognising Development Phases in the Wild</h3><p>Theoretical models of team development are clean and linear. Real teams are messy, often displaying characteristics of multiple phases simultaneously or regressing under pressure.</p><p>Here’s what these phases actually look like in consulting environments:</p><p><strong>Forming: The Polite Facade</strong></p><ul><li>Excessive deference to authority figures</li><li>Over-reliance on formal processes</li><li>Limited volunteering or initiative</li><li>Superficial agreement that masks uncertainty</li><li>Private conversations after meetings where real concerns emerge</li></ul><p><em>Consultant Approach:</em> Create safety through structure, facilitate introductions that go beyond roles to include expertise and interests, make your expectations explicit, model appropriate vulnerability.</p><p><strong>Storming: The Battlefield</strong></p><ul><li>Factions forming around different approaches</li><li>Passive-aggressive behaviour in meetings</li><li>Excessive documentation to “cover” oneself</li><li>Bypassing formal channels to get things done</li><li>Complaints about other team members to you</li></ul><p><em>Consultant Approach:</em> Acknowledge tensions without taking sides, create decision-making frameworks that depersonalise disagreements, redirect energy toward external challenges, establish ground rules for constructive conflict.</p><p><strong>Norming: The Community</strong></p><ul><li>Inside jokes and shared references</li><li>Comfortable challenging ideas without challenging people</li><li>Spontaneous collaboration outside formal structures</li><li>Problems raised directly rather than triangulated</li><li>Team members speaking about “we” instead of “I” or “they”</li></ul><p><em>Consultant Approach:</em> Reinforce positive behaviours, help codify effective practices, introduce tools to enhance collaboration, gradually reduce your facilitation as the team self-regulates.</p><p><strong>Performing: The Orchestra</strong></p><ul><li>Fluid role exchange based on needs</li><li>Problems solved at the appropriate level without escalation</li><li>Continuous improvement without prompting</li><li>Productive conflict that leads to better outcomes</li><li>Mutual accountability rather than top-down control</li></ul><p><em>Consultant Approach:</em> Focus on optimisation rather than fundamentals, provide advanced challenges that stretch the team, document their effective practices to sustain after you leave, begin preparing for your eventual transition.</p><p>I once worked with a financial services team that appeared to be performing beautifully in technical discussions but reverted to forming behaviours whenever executives joined the room. Understanding this contextual regression was crucial to effectively navigating governance discussions.</p><p><strong>Unwritten Rule 2️⃣:</strong> Teams rarely exist in a single development phase — they often display different phases in different contexts or around different topics. Map these variations to navigate effectively.</p><h3>The Outsider’s Advantage: Using Your External Position Strategically</h3><p>Being an outsider to established team dynamics is commonly seen as a disadvantage. In reality, it can be your greatest asset if leveraged properly.</p><p>As a new consultant to a team with established patterns, you have unique advantages:</p><ul><li>No historical baggage or allegiances</li><li>Permission to ask “naive” questions</li><li>Temporary immunity from political consequences</li><li>A fresh perspective on entrenched problems</li><li>The ability to speak truths insiders can’t safely voice</li></ul><p>I once joined a government project where a fundamental architectural decision was causing significant implementation problems, but the team couldn’t address it because the architect who had made the decision was now the programme director. As the external consultant, I could question this decision by framing it as “helping me understand the context” rather than challenging authority. This opened a conversation no internal team member could have initiated.</p><p>To leverage the outsider advantage:</p><ol><li><strong>Use the “fresh eyes” period deliberately</strong><br>→ Document observations and questions during your first two weeks<br>→ Ask fundamental questions before you’re socialised into the team’s assumptions<br>→ Look for patterns that team members may no longer notice</li><li><strong>Create safety through neutrality</strong><br>→ Avoid being pulled into pre-existing conflicts<br>→ Demonstrate that you can hold multiple perspectives simultaneously<br>→ Acknowledge the validity of different viewpoints before offering alternatives</li><li><strong>Bridge between subgroups</strong><br>→ Identify “translators” in each faction who can work constructively<br>→ Create mixed working groups around neutral topics<br>→ Highlight complementary strengths across divided groups</li><li><strong>Introduce external perspectives strategically</strong><br>→ Use “I’ve seen similar situations where…” rather than “You should…”<br>→ Present alternative approaches as options to consider, not corrections<br>→ Reference external standards or best practices to depersonalise suggestions</li></ol><p>The outsider advantage diminishes over time as you become part of the team system, so use it deliberately and early.</p><p><strong>Unwritten Rule 3️⃣:</strong> Your initial outsider status is a wasting asset — use it strategically before you become embedded in the team system.</p><h3>Storming Weather: Surviving When You Become the Lightning Rod</h3><p>Despite your best efforts, there will be times when you become the focus of a team’s storming behaviours. This is especially common when you’re brought in to drive change or when your role challenges existing power structures.</p><p>On a digital transformation project, I became the target of a coordinated undermining campaign from a group of technical leads who saw our new approach as threatening to their status. They questioned my expertise in meetings, withheld critical information, and created back-channels to senior leadership.</p><p>Strategies that helped me weather this storm:</p><ol><li><strong>Recognise it’s rarely personal</strong><br>→ Team resistance to consultants often reflects past negative experiences<br>→ Opposition may be to what you represent, not who you are<br>→ Understanding the fear or threat behind resistance helps address the real issue</li><li><strong>Document meticulously but discreetly</strong><br>→ Keep records of agreements, decisions, and action items<br>→ Follow up verbal conversations with written summaries<br>→ Create audit trails without appearing defensive</li><li><strong>Find allies without creating more divisions</strong><br>→ Build relationships across organisational boundaries<br>→ Identify respected team members who can validate your approaches<br>→ Create coalitions around outcomes, not personalities</li><li><strong>Address issues directly but privately</strong><br>→ When faced with undermining behaviour, address it one-on-one first<br>→ Focus on the impact on project outcomes, not your feelings<br>→ Offer face-saving ways to change behaviour</li><li><strong>Maintain your centre</strong><br>→ Remember your value and purpose<br>→ Establish support systems outside the client environment<br>→ Know when to escalate versus when to adapt</li></ol><p>The most powerful response to becoming a lightning rod is to remain consistently professional, outcome-focused, and non-reactive. Nothing defuses opposition like delivering results while refusing to be drawn into political battles.</p><p><strong>Unwritten Rule 4️⃣:</strong> When you become the target of team storming, the winning strategy is rarely direct confrontation — it’s consistent delivery combined with patient relationship building.</p><h3>Accelerating Trust: Techniques to Fast-Track Acceptance</h3><p>The challenge for consultants is that we don’t have the luxury of time to build trust naturally. We need to accelerate trust-building to be effective quickly.</p><p>When I joined a telecommunications client for what was supposed to be a six-week engagement, I knew I had days, not months, to establish enough trust to influence their technology decisions.</p><p>Fast-trust techniques that have proven effective:</p><ol><li><strong>Demonstrate competence quickly but humbly</strong><br>→ Show relevant expertise through specific, applicable examples<br>→ Acknowledge the limits of your knowledge transparently<br>→ Learn the client’s terminology and use it appropriately</li><li><strong>Find low-risk opportunities for early wins</strong><br>→ Identify small, valuable contributions you can make immediately<br>→ Solve annoying problems that have been neglected<br>→ Make someone else look good through your support</li><li><strong>Practice consistent reliability in small things</strong><br>→ Be punctual for every meeting<br>→ Follow through on every commitment, no matter how small<br>→ Respond to communications predictably and promptly</li><li><strong>Demonstrate understanding before solution</strong><br>→ Articulate the team’s challenges in their own terms<br>→ Reference the history and context of issues accurately<br>→ Connect your proposals to their priorities and values</li><li><strong>Personalise relationships appropriately</strong><br>→ Learn and remember personal details without overstepping<br>→ Find authentic common ground beyond the project<br>→ Respect the personal/professional boundary of each team member</li></ol><p>The most powerful trust accelerator I’ve found is appropriate vulnerability — admitting what you don’t know, asking for help when needed, and sharing relevant challenges from past experiences. This counterintuitive approach signals confidence and authenticity more effectively than projecting infallibility.</p><p><strong>Unwritten Rule 5️⃣:</strong> Trust formation follows a predictability equation: (Credibility + Reliability + Intimacy) ÷ Self-Orientation. Maximise the numerators and minimise the denominator to accelerate trust.</p><h3>Cross-Cultural Team Dynamics: The Invisible Dimension</h3><p>An often overlooked aspect of team dynamics is how cultural differences create invisible currents that influence team development and interaction patterns.</p><p>On a global banking project spanning teams in London, Singapore, and Mumbai, I naively applied my Western-centric understanding of team development. This led to misinterpreting the Singapore team’s deference to hierarchy as lack of initiative (when it was actually respect) and the Mumbai team’s indirect communication as evasiveness (when it was conflict avoidance).</p><p>Dimensions of cultural difference that impact team dynamics:</p><ol><li><strong>Power distance</strong> — How comfortable people are with questioning authority</li><li><strong>Uncertainty avoidance</strong> — Tolerance for ambiguity and risk</li><li><strong>Individualism vs. collectivism</strong> — Personal recognition vs. group harmony</li><li><strong>Direct vs. indirect communication</strong> — Explicit statements vs. contextual understanding</li><li><strong>Task vs. relationship orientation</strong> — Focus on deliverables vs. connections</li></ol><p>When working with cross-cultural teams, successful consultants:</p><ul><li>Establish explicit team norms that bridge cultural differences</li><li>Create multiple channels for input to accommodate different comfort levels</li><li>Adjust facilitation styles based on cultural contexts</li><li>Discuss communication preferences openly</li><li>Use cultural differences as team strengths rather than obstacles</li></ul><p>I now begin international projects with a simple exercise where team members share their cultural preferences for feedback, decision-making, and conflict resolution. This pre-emptive discussion prevents countless misunderstandings.</p><p><strong>Unwritten Rule 6️⃣:</strong> Cultural differences add an invisible layer to team dynamics that can accelerate or impede development depending on how consciously they’re managed.</p><h3>The Departure Paradox: How to Leave Teams Stronger Than You Found Them</h3><p>The final test of a consultant’s impact on team dynamics isn’t how the team functions while you’re there — it’s how they function after you leave.</p><p>The departure paradox is that the more central you become to a team’s success, the more difficult and potentially damaging your eventual departure will be. This creates a tension between being valuable now and ensuring sustainability later.</p><p>I learned this lesson painfully when a project I thought was a tremendous success collapsed within months of my departure. I had become the central node in the team’s communication network, the primary decision-maker, and the conflict resolver. When I left, these functions left with me.</p><p>To leave teams stronger than you found them:</p><ol><li><strong>Build systems, not dependencies</strong><br>→ Create processes that don’t rely on your presence<br>→ Document decision-making frameworks, not just decisions<br>→ Establish communication patterns that will outlast you</li><li><strong>Distribute your knowledge deliberately</strong><br>→ Identify who needs to know what after you’re gone<br>→ Create learning opportunities through delegation<br>→ Document not just what to do but why and how</li><li><strong>Develop internal champions</strong><br>→ Identify who will carry forward key initiatives<br>→ Invest in their capability development<br>→ Give them visibility and credit with leadership</li><li><strong>Plan for your obsolescence from the beginning</strong><br>→ Define explicit success criteria for your role<br>→ Create transition plans early, not as an afterthought<br>→ Gradually reduce your involvement in routine functions</li><li><strong>Engineer a proper handover</strong><br>→ Create formal knowledge transfer sessions<br>→ Introduce overlaps with replacements when possible<br>→ Remain available for limited consultation after departure</li></ol><p>The most successful project transitions include a “fading out” period where your involvement gradually decreases rather than stops abruptly. This allows the team to adapt incrementally to your absence.</p><p><strong>Unwritten Rule 7️⃣:</strong> Your ultimate success is measured by how unnecessary you’ve made yourself by the end of the engagement.</p><h3>Case Study: Transforming a Dysfunctional Team</h3><p>Let me return to that challenging team I mentioned at the beginning — the one that had burned through three project managers before my arrival.</p><p>After my initial assessment, I realised several dynamics were at play:</p><ul><li>A historical conflict between two technical leaders that had created tribal divisions</li><li>Business stakeholders who felt ignored and had withdrawn from meaningful participation</li><li>A culture of documenting failures rather than solving problems</li><li>Lack of psychological safety leading to information hoarding</li><li>No shared definition of success beyond individual deliverables</li></ul><p>Rather than diving into technical solutions, I focused first on team dynamics:</p><ol><li>I established a simple team charter that defined shared success criteria</li><li>I created mixed working groups that deliberately crossed tribal boundaries</li><li>I introduced a decision-making framework that required input from both technical and business perspectives</li><li>I held one-on-one conversations with key players to understand their concerns</li><li>I modelled constructive conflict by openly discussing tensions rather than avoiding them</li></ol><p>The turning point came when I facilitated a retrospective focused not on the project but on how the team worked together. By creating a safe space to acknowledge the elephants in the room, team members began to see each other as people rather than obstacles.</p><p>Progress wasn’t linear — we had setbacks and difficult moments. But over three months, the team moved from dysfunctional storming to productive norming. The project that was six months behind eventually delivered successfully.</p><p>The most gratifying moment came a year later when I returned for a different project and found the team still functioning effectively, having maintained the practices we established long after I had gone.</p><h3>Conclusion: The Human Operating System</h3><p>Technical consultants often focus obsessively on technology systems while neglecting the human operating system that ultimately determines success. We analyse database performance in minute detail but miss the team dynamics that are causing delivery bottlenecks.</p><p>The reality is that in consulting, technical challenges are rarely the true limiting factor. Human dynamics — trust, communication, conflict, and collaboration — almost always determine whether a project succeeds or fails.</p><p>Developing your ability to read and influence these dynamics isn’t a soft skill — it’s a core consulting competency. The best technical solution implemented by a dysfunctional team will fail. A good solution implemented by a high-functioning team will succeed and evolve.</p><p>As you progress in your consulting career, invest as much in understanding team psychology as you do in understanding technology. Learn to recognise team development phases, navigate political currents, build trust quickly, and leave sustainable team systems behind.</p><p>Because ultimately, your technical implementations will be updated or replaced, but the human impact of how you helped teams work together can last for years.</p><p>In the next post in this series, I’ll explore “Leading Without a Title: The Consultant’s Guide to Stealth Influence” — the unwritten rules of how to lead and influence when you have responsibility but no authority.</p><p>Until then, remember that the most powerful technology you’ll ever work with is the human operating system. Learn to debug it as carefully as you would any code.</p><p><em>What team dynamics challenges have blindsided you in your consulting work? Share your experiences in the comments below!</em></p><p>Photo by Hannah Busing on Unsplash</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a18b89927f77" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Unwritten Playbook: Agile in the Real World]]></title>
            <link>https://medium.com/@jdksloan/the-unwritten-playbook-agile-in-the-real-world-9053bdb3272b?source=rss-d0ea8d6ffc29------2</link>
            <guid isPermaLink="false">https://medium.com/p/9053bdb3272b</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[consulting]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-consulting]]></category>
            <category><![CDATA[advice]]></category>
            <dc:creator><![CDATA[Jethro Sloan]]></dc:creator>
            <pubDate>Tue, 24 Jun 2025 11:09:23 GMT</pubDate>
            <atom:updated>2025-06-24T11:09:23.861Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gH0Iwjo6HRppbtxKLF-f1Q.jpeg" /></figure><h4>Agile in the Real World: Beyond the Textbook</h4><p>“We’re fully Agile,” the client’s delivery director assured me on my first day. By the end of the week, I’d discovered their version of “fully Agile” meant:</p><ul><li>Two-month “sprints”</li><li>A 400-page requirements document that couldn’t be changed</li><li>Daily stand-ups that routinely lasted 45 minutes</li><li>A product owner who needed five layers of approval to make decisions</li></ul><p>This wasn’t the exception — it was the norm. In over a decade of consulting, I’ve never encountered a client environment that perfectly matched the Agile methodologies described in training courses or certification programmes.</p><p>Welcome to the third instalment of “The Unwritten Playbook,” where I’m sharing the consulting truths they don’t teach you in formal training. Today, we’re tackling the gap between Agile theory and client reality, and how to deliver value when nothing matches the textbook.</p><h3>Agile Theatre vs. Agile Value: Recognising the Difference</h3><p>Many organisations have adopted the ceremonies of Agile without embracing its principles. They’re performing what I call “Agile Theatre” — going through the motions without reaping the benefits.</p><p>I once joined a project where the team proudly showed me their Kanban board with perfectly arranged columns and colour-coded cards. Yet when I asked how often cards moved across the board, the awkward silence told me everything. The board was updated only for sprint reviews — essentially a static presentation tool rather than a living workflow management system.</p><p>The difference between Agile Theatre and Agile Value lies in outcomes, not activities:</p><p><strong>Signs of Agile Theatre:</strong></p><ul><li>Ceremonies held religiously but without purpose</li><li>Extensive documentation of “user stories” that function as traditional requirements</li><li>Sprint plans that never change during execution</li><li>Retrospectives where the same issues arise repeatedly without resolution</li><li>Product backlogs managed exclusively by project managers, not product owners</li></ul><p><strong>Signs of Agile Value:</strong></p><ul><li>Frequent delivery of working software</li><li>Genuine customer feedback influencing priorities</li><li>Team empowerment to make technical decisions</li><li>Visible improvement in processes over time</li><li>Focus on outcomes rather than output</li></ul><p>As consultants, we’re often caught in a difficult position: clients hire us to implement Agile but aren’t prepared for the organisational changes required for success. I’ve found the most effective approach is to focus on incremental value delivery rather than methodological purity.</p><p><strong>Unwritten Rule 1️⃣:</strong> Don’t fight for Agile purity; fight for the principles that deliver value in your client’s context. One real improvement is worth a hundred textbook implementations.</p><h3>Translating Methodologies: Matching Agile Approaches to Client Cultures</h3><p>Not every organisation is ready for the same flavour of Agile, and forcing a mismatch creates resistance rather than results.</p><p>I learned this lesson working with a government agency with strict governance requirements. Our initial attempt to implement Scrum failed spectacularly because the two-week sprint cycle conflicted with their monthly steering committee structure. When we adapted to a more Kanban-style approach with monthly demonstration points aligned to their governance, we suddenly made progress.</p><p>Assess your client’s Agile readiness across these dimensions:</p><p><strong>Organisational Structure:</strong></p><ul><li>Hierarchical → Self-managing</li><li>Siloed → Cross-functional</li><li>Centralised → Distributed decision-making</li></ul><p><strong>Planning Horizon:</strong></p><ul><li>Annual budgeting → Continuous funding</li><li>Fixed scope → Flexible priorities</li><li>Detailed upfront → Progressive elaboration</li></ul><p><strong>Risk Tolerance:</strong></p><ul><li>Risk-averse → Risk-balanced</li><li>Process-focused → Outcome-focused</li><li>Failure-punishing → Learning-oriented</li></ul><p>Then select and adapt your approach accordingly:</p><ul><li><strong>For traditional organisations:</strong> Consider Scrumban with longer cycles aligned to governance</li><li><strong>For regulatory environments:</strong> Emphasise documentation and traceability within iterative delivery</li><li><strong>For hierarchical structures:</strong> Implement clear escalation paths and decision frameworks</li><li><strong>For risk-averse cultures:</strong> Start with low-risk areas to demonstrate success</li></ul><p>I’ve found that a “principles-first” approach works better than a “practices-first” approach. When clients understand and buy into the <em>why</em> of Agile (faster feedback, reduced risk, increased adaptability), they become more open to adapting their processes to achieve those benefits.</p><p><strong>Unwritten Rule 2️⃣:</strong> Meet clients where they are, not where the Agile manifesto thinks they should be. The path to true agility is itself incremental.</p><h3>The Fixed-Price Paradox: Agile in Non-Agile Commercial Models</h3><p>Perhaps the greatest contradiction in consulting is being asked to implement Agile within the constraints of fixed-price, fixed-scope contracts. This fundamental tension creates challenges that no certification course prepares you for.</p><p>On a digital transformation project, my team was contracted to deliver a specific set of features for a fixed price. The client wanted “Agile delivery” but wasn’t willing to adjust scope as we learned more about user needs. We were caught between contractual commitments and Agile principles.</p><p>Here’s how to navigate this paradox:</p><ol><li><strong>Separate the commercial model from the delivery model</strong><br>→ The contract may be fixed, but the implementation approach can still be iterative<br>→ Create a “scope buffer” by identifying lower-priority items that could be traded</li><li><strong>Define outcome-based acceptance criteria</strong><br>→ Shift from “building features” to “solving problems”<br>→ Create space for discovery while maintaining commercial boundaries</li><li><strong>Use tiered scope classifications</strong><br>→ Must-have requirements (contractually binding)<br>→ Should-have capabilities (implementation flexibility)<br>→ Could-have enhancements (if time/budget permits)</li><li><strong>Implement rolling wave planning</strong><br>→ Detail near-term work while keeping future work flexible<br>→ Regular re-prioritisation within the overall scope boundary</li><li><strong>Establish change threshold agreements</strong><br>→ Define what constitutes material change requiring commercial adjustment<br>→ Create lightweight change processes for smaller adjustments</li></ol><p>The most successful approach I’ve used is to frame Agile as a risk-reduction strategy for fixed-price work. By delivering incrementally and gathering feedback early, we reduce the risk of building the wrong thing — a benefit to both client and consultant.</p><p><strong>Unwritten Rule 3️⃣:</strong> Fixed-price contracts and Agile delivery can coexist if you separate what must be fixed (commercial terms) from what should be flexible (implementation approach).</p><h3>Ceremonies That Actually Work: Cutting Through Ritual to Create Value</h3><p>Agile ceremonies often degrade into meaningless rituals that teams endure rather than benefit from. As consultants, we need to revitalise these practices to deliver their intended value.</p><p>I joined a project where the daily stand-up had devolved into a 40-minute status report to the project manager. Team members were disengaged, checking emails or multitasking during the call. By restructuring the stand-up around impediments rather than status updates, we cut it to 12 minutes and dramatically improved collaboration.</p><p>Here’s how to transform the core ceremonies from rituals to value-creators:</p><p><strong>Daily Stand-ups:</strong></p><ul><li>Focus on blocking issues, not status reports</li><li>Use a physical or virtual board as the central point, not people</li><li>Implement the “walk the board” approach rather than the three questions</li><li>Schedule technical discussions immediately after, but separate from the stand-up</li></ul><p><strong>Sprint Planning:</strong></p><ul><li>Do preparation work before the session (refinement)</li><li>Focus on outcomes, not just task breakdown</li><li>Include explicit discussion of risks and dependencies</li><li>End with a team commitment, not just assignment</li></ul><p><strong>Reviews/Demos:</strong></p><ul><li>Make them interactive, not presentational</li><li>Focus on business value, not technical completion</li><li>Include affected stakeholders, not just the product owner</li><li>Capture feedback systematically for action</li></ul><p><strong>Retrospectives:</strong></p><ul><li>Vary the format to maintain engagement</li><li>Focus on actionable improvements, not just discussion</li><li>Track implementation of previous retro actions</li><li>Create safety for honest conversation</li></ul><p>The most effective Agile teams I’ve worked with treat the ceremonies as tools, not obligations. They constantly adjust the format, duration, and frequency based on team needs and project context.</p><p><strong>Unwritten Rule 4️⃣:</strong> The purpose of Agile ceremonies is to solve problems and improve delivery, not to follow a script. If a ceremony isn’t adding value, change it or drop it.</p><h3>The Consultant’s Secret Weapon: Incremental Value in Traditional Environments</h3><p>Even in the most traditional, waterfall-oriented client environments, we can introduce Agile principles that deliver immediate benefits without requiring wholesale methodology changes.</p><p>While working with a financial services client committed to their stage-gate process, I still managed to transform their approach by introducing three Agile principles that didn’t threaten their governance:</p><ol><li><strong>Demonstrable increments</strong><br>→ Breaking large deliverables into smaller, demonstrable pieces<br>→ Creating review points within phases, not just between them</li><li><strong>Feedback loops</strong><br>→ Involving end users earlier in the process<br>→ Creating mockups and prototypes for validation before full development</li><li><strong>Visible workflow management</strong><br>→ Making work and blockers visible<br>→ Tracking actual vs. planned progress visibly</li></ol><p>The client maintained their familiar process while gaining many Agile benefits. Later, as they saw the value, they became more open to broader methodology changes.</p><p>Some of my most successful “Agile transformations” never used the word Agile. Instead, I focused on specific pain points:</p><ul><li>“Let’s reduce the risk of misunderstanding by showing working software earlier”</li><li>“We can identify integration issues sooner by testing components incrementally”</li><li>“A visual workflow board will help us spot bottlenecks before they delay the project”</li></ul><p><strong>Unwritten Rule 5️⃣:</strong> Don’t fight the client’s methodology head-on; instead, introduce Agile principles as solutions to specific problems they recognise.</p><h3>The Definition of Done Dilemma: Quality vs. Speed</h3><p>In textbook Agile, the Definition of Done ensures quality is built into every increment. In reality, clients often pressure teams to prioritise speed over completeness, creating technical debt and future problems.</p><p>On a retail client project, pressure to meet a market deadline led to a “we’ll fix it later” mentality. Six months later, “later” never came, and the accumulated technical debt had reduced development velocity by 60%.</p><p>Here’s how to manage this tension:</p><ol><li><strong>Create a graduated Definition of Done</strong><br>→ Minimum DoD for all work (never compromised)<br>→ Standard DoD for most work (occasionally flexed)<br>→ Ideal DoD for critical components (when time allows)</li><li><strong>Make technical debt visible</strong><br>→ Track shortcuts explicitly as “debt stories”<br>→ Estimate the interest rate (future cost) of each debt item<br>→ Include debt metrics in reporting</li><li><strong>Establish a debt repayment plan</strong><br>→ Allocate a percentage of each sprint to debt reduction<br>→ Prioritise debt that impedes current development<br>→ Connect debt repayment to future capability delivery</li><li><strong>Educate on the economics of technical debt</strong><br>→ Show how initial speed creates later slowdowns<br>→ Quantify the cost of delayed debt repayment<br>→ Demonstrate velocity impacts with data</li></ol><p>The most effective approach I’ve found is to reframe the conversation from “quality vs. speed” to “short-term speed vs. sustainable speed.” This shifts the discussion from a technical concern to a business decision about long-term delivery capacity.</p><p><strong>Unwritten Rule 6️⃣:</strong> Never fight for quality in engineering terms; fight for it in business terms of sustainable delivery and total cost of ownership.</p><h3>Navigating Distributed Agile: When the Team Is Everywhere</h3><p>The ideal of co-located, fully dedicated Agile teams rarely exists in consulting engagements. More often, we work with teams distributed across locations, time zones, organisations, and competing priorities.</p><p>On a global transformation programme, our team spanned four countries and seven time zones. The textbook approach of daily face-to-face communication was impossible. We had to reinvent our Agile practices for distributed reality.</p><p>Strategies that actually work for distributed Agile:</p><ol><li><strong>Overcommunicate visually</strong><br>→ Use digital Kanban boards with rich information<br>→ Create information radiators accessible to all locations<br>→ Develop visual status reporting that doesn’t require real-time explanation</li><li><strong>Establish core collaboration hours</strong><br>→ Identify time windows when all team members can collaborate<br>→ Schedule key ceremonies within these windows<br>→ Rotate meeting times to share the time zone burden</li><li><strong>Create location-based sub-teams</strong><br>→ Form complete, cross-functional capabilities at each location<br>→ Minimise dependencies between locations<br>→ Create local team leads responsible for coordination</li><li><strong>Implement asynchronous ceremonies</strong><br>→ Record demos for asynchronous viewing<br>→ Use digital tools for ongoing retrospective input<br>→ Create standup slacks or channels for updates</li><li><strong>Invest in relationship building</strong><br>→ Start projects with virtual team building<br>→ Create non-work connection opportunities<br>→ When possible, bring teams together physically at critical junctures</li></ol><p>The distributed teams that function best establish clear protocols for both synchronous and asynchronous communication, making explicit what requires real-time discussion versus what can be handled offline.</p><p><strong>Unwritten Rule 7️⃣:</strong> In distributed Agile, communication must be deliberately designed, not left to chance. What happens naturally in co-located teams must be explicitly structured in distributed ones.</p><h3>Case Study: Pragmatic Agile in a Resistant Environment</h3><p>Let me share a real example of navigating these challenges in practice:</p><p>I led a digital transformation project for a traditional insurance company with a strong command-and-control culture. The executive sponsor wanted Agile delivery but the organisation had:</p><ul><li>Quarterly funding reviews</li><li>A detailed business case with fixed scope</li><li>Separate development and testing teams</li><li>A heavyweight change control board</li><li>Limited user access for feedback</li></ul><p>Rather than forcing textbook Scrum, we created a hybrid approach:</p><ol><li>We established two-week development iterations within six-week “delivery increments” that aligned with their governance cycle</li><li>We maintained the fixed scope boundary but created flexibility in how features were implemented</li><li>We ran Agile ceremonies with the core team but translated outputs into the governance documentation the organisation expected</li><li>We created a “user proxy” group from internal stakeholders when actual users weren’t available</li><li>We demonstrated working software at the end of each two-week iteration but only formally delivered at six-week boundaries</li></ol><p>The result? We delivered the project successfully, and more importantly, the client gradually adopted more Agile practices as they saw the benefits. Two years later, they had transformed their entire delivery approach — not because we insisted on methodological purity, but because we showed pragmatic value.</p><h3>Conclusion: Principles Over Practices</h3><p>After years of implementing “Agile” in environments ranging from startups to government agencies, I’ve come to a simple conclusion: the principles matter more than the practices.</p><p>The Agile Manifesto values “individuals and interactions over processes and tools,” yet ironically, many Agile implementations become obsessed with specific processes and tools. The most successful Agile consultants I know focus relentlessly on the outcomes Agile was designed to achieve:</p><ul><li>Delivering value early and often</li><li>Reducing the cost of change</li><li>Improving quality through feedback</li><li>Enhancing team collaboration</li><li>Creating sustainable delivery pace</li></ul><p>When you focus on these outcomes rather than methodological purity, you can find ways to bring Agile benefits to even the most traditional environments.</p><p>In consulting, our job isn’t to implement Agile — it’s to help clients deliver better software more effectively. Sometimes that means textbook Scrum, sometimes it means pragmatic hybridisation, and sometimes it means subtle introduction of Agile principles within existing frameworks.</p><p>The measure of success isn’t how purely you implemented the methodology; it’s whether you left the client better able to deliver value than when you arrived.</p><p>In the next post in this series, I’ll explore “Team Whispering: Navigating the Human Dynamics No One Prepared You For” — the unwritten rules of working with the complex team dynamics that can make or break your consulting success.</p><p>Until then, remember that Agile is a means to an end, not an end in itself. Be principled in your goals but pragmatic in your approach.</p><p><em>What’s the biggest gap you’ve encountered between Agile theory and practice? Share your experiences in the comments below!</em></p><p>Photo by Medienstürmer on Unsplash</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9053bdb3272b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Unwritten Playbook: The Client Whisperer]]></title>
            <link>https://medium.com/@jdksloan/the-unwritten-playbook-the-client-whisperer-eef52a65bb70?source=rss-d0ea8d6ffc29------2</link>
            <guid isPermaLink="false">https://medium.com/p/eef52a65bb70</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[consulting]]></category>
            <category><![CDATA[advice]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[software-consulting]]></category>
            <dc:creator><![CDATA[Jethro Sloan]]></dc:creator>
            <pubDate>Mon, 16 Jun 2025 12:25:55 GMT</pubDate>
            <atom:updated>2025-06-16T12:25:55.373Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jQN_SVHwTMKJUQVA1YnbKw.jpeg" /></figure><h3>The Client Whisperer: Building Relationships That Survive Project Storms</h3><p>“We’re going to need you to step up into the leadership role in your current team as the other two engineers have fallen out with the product owner.” my firm’s unit manager told me over the phone. My surprise was almost palpable.</p><p>For the sake of anonymity let’s call the product owner Ted. Ted was the PO who ran the project and was a vital stakeholder in achieving success in the organisation. The previous consultants had apparently created such a mess that he’d vowed never to work with “overpriced advisors” again.</p><p>Six months later, Ted was personally requesting me for his next project and telling his colleagues I was “different from other consultants.”</p><p>What changed? Not my technical skills — those remained constant. What changed was my approach to the relationship.</p><p>Welcome to the second instalment of “The Unwritten Playbook,” where I’m sharing the hard-earned wisdom that most consultants learn through painful experience. Today, we’re diving into the most crucial and least taught aspect of consulting: building client relationships that weather the inevitable storms of complex projects.</p><h3>Reading the Unwritten Org Chart: Finding the Real Decision-Makers</h3><p>Every organisation has two org charts: the official one they show you during onboarding, and the real one that determines how decisions actually get made. Learning to read the latter is perhaps the most valuable skill in consulting.</p><p>I once spent three weeks carefully building support for a solution with a client’s “leadership team,” only to have everything dismantled in five minutes by an unassuming IT manager who wasn’t even in most of our meetings. As it turned out, the executive sponsor deferred to this manager on all technical decisions because they’d worked together for 15 years.</p><p>Look for these telltale signs of the real power brokers:</p><ul><li>Who gets consulted before decisions are finalised</li><li>Whose objections immediately halt progress</li><li>Who speaks least but is most attentively listened to</li><li>Whose calendar dictates when key meetings happen</li><li>Who can bend or ignore the organisation’s standard processes</li></ul><p>But beware — power isn’t always where you expect it. I’ve seen executive assistants with more practical influence than directors, and junior developers who could sink projects because they were the only ones who understood legacy systems.</p><p><strong>Unwritten Rule 1️⃣:</strong> Invest early in identifying both the formal and informal influence networks. The project kickoff document tells you who should matter; the first few weeks show you who actually does.</p><h3>The Expectation Gap: Why Clients Are Often Disappointed Even with Good Delivery</h3><p>Here’s a painful truth: You can deliver exactly what’s in the statement of work and still have an unhappy client.</p><p>The expectation gap exists because clients aren’t buying your deliverables — they’re buying the outcomes they believe those deliverables will create. And they often have unstated expectations about how those outcomes will materialise.</p><p>I learned this lesson the hard way after delivering a complex data architecture that met every specified requirement. The client’s feedback? “This isn’t what we wanted.” After some digging, I discovered they expected the architecture to solve data quality problems that weren’t mentioned anywhere in our scope but were their primary motivation for the project.</p><p>To bridge the expectation gap:</p><ol><li><strong>Ask about hoped-for outcomes, not just requirements:</strong> “When this project is successful, what will be different for your organisation?”</li><li><strong>Uncover the project’s origin story:</strong> “What prompted this initiative in the first place?”</li><li><strong>Identify the unspoken fears:</strong> “What concerns do you have about this approach?”</li><li><strong>Surface assumptions regularly:</strong> “Let me check my understanding of what success looks like…”</li><li><strong>Distinguish between “must-haves” and “nice-to-haves”:</strong> “If we had to focus on just three capabilities, which would deliver the most value?”</li></ol><p>A technique I’ve found invaluable is to check-in regularly with key project stakeholders to validate if you’re moving in the right direction. This ensures the business outcomes, emotional wins, and political necessities that truly define success in the client’s eyes are being met.</p><p><strong>Unwritten Rule 2️⃣:</strong> The client’s unstated expectations will sink your project faster than any technical challenge. Make the implicit explicit as early as possible.</p><h3>Delivering Bad News: The Art of Transparency Without Panic</h3><p>In almost a decade of consulting, I’ve never seen a complex project go exactly to plan. The differentiator between consultants who build trust and those who lose it isn’t whether things go wrong — it’s how they handle it when they inevitably do.</p><p>I remember the dread I felt discovering a critical integration wouldn’t work as planned three weeks before launch. My instinct was to scramble for a solution before saying anything. A mentor gave me advice I’ve followed ever since: “Bring problems to clients while they’re still problems, not after they’ve become disasters.”</p><p>The framework I now use for delivering bad news:</p><ol><li><strong>Early warning, no surprises:</strong> Flag issues as soon as you see them, not when they’re unavoidable</li><li><strong>Context before content:</strong> Start with the broader project context (“Overall, we’re on track with 7 of 8 workstreams…”)</li><li><strong>Clear, direct statement of the issue:</strong> No technical jargon or sugar-coating</li><li><strong>Impact assessment:</strong> What this means for the project objectives</li><li><strong>Options with recommendations:</strong> Never bring problems without potential solutions</li><li><strong>Clear next steps:</strong> Who does what by when</li></ol><p>The most counterintuitive lesson I’ve learned is that properly delivered bad news often strengthens client relationships. It demonstrates integrity, transparency, and confidence — all traits clients value more than an unblemished record.</p><p>I once had a client tell me: “I don’t trust consultants who say everything’s going perfectly. I trust consultants who tell me about problems while there’s still time to fix them.”</p><p><strong>Unwritten Rule 3️⃣:</strong> How you deliver bad news defines your relationship more than how you deliver good news. Practice the difficult conversations before you have them.</p><h3>The Insurance Policy: Documenting Conversations Without Being Paranoid</h3><p>Documentation in consulting serves two purposes: creating deliverables and covering yourself. The latter is rarely discussed in training but is essential to survival.</p><p>I don’t mean this in a cynical way. Clear documentation prevents honest misunderstandings, helps clients defend decisions to their stakeholders, and ensures continuity when team members change — which they inevitably will during long projects.</p><p>A former colleague lost a client relationship because he couldn’t prove the client had approved a critical design decision that later proved problematic. The client genuinely didn’t remember giving that approval in a rushed hallway conversation.</p><p>My documentation practice now includes:</p><ul><li><strong>Decision logs:</strong> Tracking what was decided, by whom, and based on what information</li><li><strong>Assumption registers:</strong> Explicitly noting what we’re taking as given</li><li><strong>RAID logs:</strong> Risks, Assumptions, Issues, Dependencies</li><li><strong>Meeting notes:</strong> Sent within 24 hours with clear action items</li><li><strong>Requirements traceability:</strong> Connecting delivered features to original requirements</li></ul><p>The key is doing this without seeming defensive or bureaucratic. I position it as a service: “To make sure we’re aligned, I’ll send a quick summary of what we discussed and the decisions made.”</p><p><strong>Unwritten Rule 4️⃣:</strong> Document diligently but diplomatically. The goal isn’t to prove the client wrong but to ensure shared understanding.</p><h3>Building Champions: Turning Clients into Advocates Who Request You by Name</h3><p>The ultimate achievement in consulting isn’t completing a successful project — it’s creating client champions who specifically request you for future work.</p><p>Early in my career, I focused solely on technical delivery. Now I realise that champion-building is an intentional practice that runs parallel to delivery. Some of my most valuable client relationships began with difficult projects that we navigated together.</p><p>The client champion blueprint:</p><ol><li><strong>Find their personal win:</strong> Understand what success means for them individually, not just their department</li><li><strong>Make them look good:</strong> Create materials they can share upward that showcase the value of the work</li><li><strong>Transfer genuine expertise:</strong> Teach them things that enhance their standing in the organisation</li><li><strong>Show vulnerability:</strong> Asking for their input creates investment in your success</li><li><strong>Remember the human element:</strong> Acknowledge their pressures, celebrate their wins, respect their challenges</li></ol><p>I had a client who went from sceptic to champion after I helped him prepare for a board presentation about our project. He later told me: “You’re the first consultant who seemed to care about my success, not just the project’s success.”</p><p>The most powerful form of relationship building happens in the small moments: staying late to help with a deadline that isn’t technically your responsibility, sending an article relevant to their professional interests, or simply remembering details about their priorities.</p><p><strong>Unwritten Rule 5️⃣:</strong> A client who likes you personally will forgive technical imperfections. A client who only respects your technical work will not forgive relationship missteps.</p><h3>The Stakeholder Spectrum: Different Approaches for Different Roles</h3><p>Not all client relationships require the same approach. I categorise stakeholders into five types, each needing a different relationship strategy:</p><ol><li><strong>The Sponsor<br></strong>✓ <em>Cares about:</em> Business outcomes, ROI, reputation<br>✓ <em>Relationship approach:</em> Strategic alignment, executive updates, big-picture focus<br>✓ <em>Communication style:</em> Brief, business-focused, forward-looking</li><li><strong>The Gatekeeper<br></strong>✓ <em>Cares about:</em> Process adherence, risk management, governance<br>✓ <em>Relationship approach:</em> Transparent compliance, early consultation, respect for protocols<br>✓ <em>Communication style: </em>Formal, documented, comprehensive</li><li><strong>The SME<br></strong>✓<em> Cares about: </em>Technical accuracy, professional respect, being heard<br>✓ <em>Relationship approach:</em> Genuine consultation, acknowledgment of expertise, peer-level discussion<br>✓ <em>Communication style:</em> Technical depth, evidence-based, collaborative</li><li><strong>The End User<br></strong>✓ <em>Cares about:</em> Usability, practical benefits, minimal disruption<br>✓ <em>Relationship approach:</em> Empathy, demonstration of benefits, responsiveness to feedback<br>✓ <em>Communication style:</em> Concrete, benefit-focused, jargon-free</li><li><strong>The Sceptic<br></strong>✓ <em>Cares about:</em> Proof, precision, not being oversold<br>✓ <em>Relationship approach:</em> Under-promise/over-deliver, factual evidence, respectful persistence<br>✓ <em>Communication style: </em>Direct, substantive, honest about limitations</li></ol><p>The most common mistake I see consultants make is using a one-size-fits-all approach to stakeholder management. The executive sponsor doesn’t need the same relationship as the technical lead, and treating them identically will undermine your effectiveness with both.</p><p><strong>Unwritten Rule 6️⃣:</strong> Tailor your relationship approach to each stakeholder’s role, priorities, and communication style. What builds trust with one may erode it with another.</p><h3>Navigating Client Politics Without Getting Burned</h3><p>Client organisations are political environments, and as a consultant, you’ll inevitably be drawn into those politics. The challenge is navigating them without becoming a casualty of conflicts that predated your arrival.</p><p>I once joined a project where two client departments were engaged in a years-long turf war. Each tried to use our team to outmanoeuvre the other, placing us in an impossible position. We survived by establishing some crucial guidelines:</p><ol><li><strong>Maintain equidistance:</strong> Avoid being seen as aligned with any faction</li><li><strong>Focus on organisational goals:</strong> Consistently reference the broader objectives that transcend departmental interests</li><li><strong>Create neutral forums:</strong> Establish working sessions with clear, objective decision criteria</li><li><strong>Document competing requirements:</strong> Acknowledge differing needs without judging their validity</li><li><strong>Escalate thoughtfully:</strong> Know when and how to involve senior sponsors in resolving conflicts</li></ol><p>The political savvy that matters most isn’t about manipulating situations, but about recognising the human dynamics at play and creating spaces where productive work can happen despite them.</p><p><strong>Unwritten Rule 7️⃣:</strong> You can’t solve long-standing organisational politics, but you can create temporary truces around your project by focusing on shared goals.</p><h3>Conclusion: Relationships Are Your Real Deliverable</h3><p>Technical deliverables have a short shelf life. Systems get replaced, code gets rewritten, and designs get updated. But relationships endure.</p><p>The longer I consult, the more I recognise that my technical work is ultimately judged through the lens of the relationships I build. A flawlessly executed project with damaged relationships is a failure. A project that faces challenges but strengthens relationships often leads to more work and better outcomes in the long run.</p><p>Your technical reputation is built project by project, but your consulting reputation is built relationship by relationship. The former might get you assigned to projects; the latter will get you requested by name.</p><p>In the next post in this series, I’ll explore “Agile in the Real World: Beyond the Textbook” — the unwritten rules of making Agile methodologies work in environments that don’t match the ideal conditions described in training.</p><p>Until then, remember that in consulting, as in life, people rarely remember exactly what you did, but they always remember how you made them feel.</p><p>What relationship lessons have you learned the hard way in your consulting career? Share your experiences in the comments below!</p><p>Photo by Chris Liverani on Unsplash</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eef52a65bb70" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Unwritten Playbook: Consulting Advice They Don't Teach You]]></title>
            <link>https://medium.com/@jdksloan/the-unwritten-playbook-consulting-advice-they-dont-teach-you-9adfa39140bd?source=rss-d0ea8d6ffc29------2</link>
            <guid isPermaLink="false">https://medium.com/p/9adfa39140bd</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[consulting]]></category>
            <category><![CDATA[advice]]></category>
            <category><![CDATA[software-consulting]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Jethro Sloan]]></dc:creator>
            <pubDate>Thu, 12 Jun 2025 10:14:53 GMT</pubDate>
            <atom:updated>2025-06-12T10:14:53.973Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cFNaIDy0Oo9m7sJUUbsGIQ.jpeg" /></figure><h4><strong>Beyond the Technical: The Hidden Art of Software Consulting</strong></h4><p>I was three weeks into my first major consulting gig when I learned the most important lesson of my career—one that no training had prepared me for.</p><p>The client&#39;s CTO had just reviewed our technical architecture, nodded approvingly at our elegant solution, and then said: &quot;This looks great, but the CEO will never approve it. He had a similar system fail at his last company.&quot;</p><p>In that moment, I realised something crucial: being right technically wasn&#39;t enough. I hadn&#39;t been hired just to design a system; I&#39;d been hired to navigate the client&#39;s politics, history, and fears. My computer science degree hadn&#39;t covered that.</p><p>Welcome to the first post in &quot;The Unwritten Playbook&quot; series, where I&#39;ll share the consulting truths they don&#39;t teach you in formal training. Let&#39;s start with the fundamental reality that separates great consultants from merely good technologists.</p><h3><strong>The Consultant&#39;s Mindset: Why Thinking Like an Employee Will Sink Your Career</strong></h3><p>When I mentor new consultants, the first mindset shift I help them make is from &quot;employee thinking&quot; to &quot;consultant thinking.&quot;</p><p><strong>Here&#39;s the uncomfortable truth:</strong> clients don&#39;t hire consultants who think like their employees—they already have employees.</p><p>❌ <strong>Employee mindset</strong></p><ul><li>I&#39;ll build what they ask for</li><li>My job is to complete assigned tasks</li><li>Success means meeting the technical requirements</li><li>I should wait for instructions and clarification</li></ul><p>✅ <strong>Consultant mindset</strong></p><ul><li>I&#39;ll solve the problem behind the request</li><li>My job is to deliver business outcomes</li><li>Success means the client achieves their goals</li><li>I should proactively identify and address gaps</li></ul><p>I once watched a brilliant developer-turned-consultant fail spectacularly because he kept his head down writing perfect code while missing the executive infighting that eventually killed the project. His code worked flawlessly, but the project was still deemed a failure.</p><p><strong>Unwritten Rule 1️⃣:</strong> Clients pay premium rates for consultants not because we write better code, but because we understand the business context in which that code must succeed.</p><h3><strong>The Real Value You Bring: Is Rarely Your Coding Skills</strong></h3><p><strong>Let me be brutally honest:</strong> unless you&#39;re working with cutting-edge technology, your clients probably have people who can code as well as you can. What they lack—and what they&#39;re actually paying for—is a specific combination of elements that has little to do with your technical certifications.</p><p>What clients are really buying:</p><ol><li><strong>Cross-pollination knowledge:</strong> You&#39;ve seen how multiple organisations solve similar problems</li><li><strong>Acceleration:</strong> You can skip the learning curve because you&#39;ve already made those mistakes elsewhere</li><li><strong>Political cover: </strong>Sometimes they need an external voice to say what internal people can&#39;t</li><li><strong>Pattern recognition:</strong> You can spot issues before they become problems</li><li><strong>Business translation:</strong> You can convert technical concepts into business value language</li></ol><p>I remember sitting in a meeting where a client&#39;s developer proposed the exact same solution I was about to suggest. The difference? When the executives questioned it, I could say, &quot;This approach worked successfully for three other financial institutions with similar regulatory constraints,&quot; while the internal developer could only say, &quot;I think this is the best approach.&quot;</p><p><em>Same solution, different credibility.</em></p><p><strong>Unwritten Rule 2️⃣: </strong>Your experiences across clients are your superpower. Reference them constantly (without breaking confidentiality).</p><h3><strong>Managing the Expertise Paradox: How to Be Confident When You Don&#39;t Know Everything</strong></h3><p>Here&#39;s the dirty secret every consultant eventually faces: you&#39;ll frequently be positioned as the expert in rooms where you&#39;re learning just as much as you&#39;re teaching.</p><p>The expertise paradox is real and unavoidable. Clients expect you to have immediate answers, but also to understand their unique situation—which, by definition, you&#39;re still learning about.</p><p>I&#39;ve developed a four-step approach that&#39;s saved me countless times:</p><ol><li><strong>Acknowledge and frame:</strong> &quot;That&#39;s an interesting challenge. I&#39;ve seen similar situations at other clients...&quot;</li><li><strong>Ask clarifying questions: </strong>&quot;To make sure I understand your specific context, could you tell me more about...?&quot;</li><li><strong>Bridge to known territory: </strong>&quot;This reminds me of a project where we faced...&quot;</li><li><strong>Collaborative solution: </strong>&quot;Based on that experience and what you&#39;ve shared, we might consider...&quot;</li></ol><p>This approach buys you time, shows you&#39;re listening, establishes credibility, and creates a collaborative solution—all while you&#39;re actually figuring things out!</p><p>I once walked into a client workshop completely unprepared because a calendar mix-up had me in the wrong meeting. Instead of panicking, I used this exact approach, asked thoughtful questions, and related the discussion to a previous project. After the meeting, the client director told me how valuable my &quot;<em>expertise</em>&quot; had been. Sometimes listening intelligently is mistaken for genius.</p><p><strong>Unwritten Rule 3️⃣:</strong> Clients expect certainty, but respect thoughtfulness. When you don&#39;t know, never guess—instead, structure how you&#39;ll find the answer together.</p><h3><strong>Building Your Professional Persona: The Unspoken Expectations Clients Have</strong></h3><p>No one tells you this explicitly, but clients have subconscious expectations about how consultants should behave, speak, dress, and interact. These expectations aren&#39;t fair or necessarily rational, but they&#39;re real.</p><p>Your professional persona needs to strike a careful balance:</p><ul><li><strong>Confident but not arrogant</strong></li><li><strong>Polished but not slick</strong></li><li><strong>Friendly but not familiar</strong></li><li><strong>Knowledgeable but not condescending</strong></li><li><strong>Adaptable but not chameleon-like</strong></li></ul><p>I learned this lesson when a client took me aside after a meeting and said, &quot;You know your stuff, but you apologised three times in that presentation. It makes the executives nervous about your recommendations.&quot;</p><p>The truth is that different clients expect different personas. Government clients often expect formality and comprehensive documentation. Startups typically value adaptability and quick insights. Financial services prize precision and risk awareness.</p><p>Your job is to read the environment and adapt appropriately—without losing your authenticity.</p><p><strong>Unwritten Rule 4️⃣:</strong> Match your client&#39;s formality level and communication style, then dial it up just one notch on the professionalism scale.</p><h3><strong>The Balancing Act: Serving Three Masters (Client, Firm, and Project)</strong></h3><p>The most stressful aspect of consulting is the constant balancing act between:</p><ol><li><strong>The client&#39;s expectations</strong> - What they think they&#39;re paying for</li><li><strong>Your firm&#39;s expectations</strong> - Profitability, reusability, future work</li><li><strong>The project&#39;s requirements</strong> - What actually needs to be done technically</li></ol><p>These three masters often want conflicting things:</p><ul><li>The client wants customisation, your firm wants reusable assets</li><li>The client wants unlimited support, your firm wants scope boundaries</li><li>The project needs time, the client wants speed, your firm wants efficiency</li></ul><p>One of my most uncomfortable moments came when my firm&#39;s partner instructed me to &quot;<em>find opportunities for follow-on work</em>&quot; while the client specifically told me they valued that we &quot;weren&#39;t like other consultants always trying to extend contracts.&quot;</p><p>The solution? Radical transparency—but tactfully applied. I&#39;ve found that directly addressing these tensions actually builds trust. For example: &quot;I&#39;ve identified an approach that balances customisation for your specific needs while leveraging our firm&#39;s existing frameworks, which helps with both quality and timeline.&quot;</p><p><strong>Unwritten Rule 5️⃣: </strong>When tensions between stakeholders arise, name them explicitly (but diplomatically) rather than trying to silently satisfy everyone.</p><h3><strong>The Ethics Tightrope: When Values Collide</strong></h3><p>One area no training adequately prepares you for is navigating ethical grey zones. You&#39;ll encounter situations where:</p><ul><li>You&#39;re asked to recommend solutions you don&#39;t believe in</li><li>The client wants you to &quot;fix&quot; a technical assessment to support a predetermined decision</li><li>You discover your firm overpromised capabilities during sales</li><li>The client asks you to work on something outside your expertise</li></ul><p>Early in my career, I was pressured to tell a client their aggressive timeline was feasible when I knew it wasn&#39;t. The partner said, &quot;Once we&#39;re in, we can reset expectations.&quot; I still regret not pushing back harder—the project failed, and the client never worked with our firm again.</p><p>Develop your personal ethical boundaries before you need them, because in the moment, pressure can cloud judgment.</p><p><strong>Unwritten Rule 6️⃣: </strong>Your reputation is the only asset you truly own in consulting. Protect it fiercely, even when it costs you in the short term.</p><h3><strong>Conclusion: It&#39;s About Trust, Not Technology</strong></h3><p>After 10+ years in consulting, I&#39;ve watched technically brilliant consultants fail and technically average consultants thrive. The difference? The thriving consultants understood that while technology is what we deliver, trust is what we sell.</p><p>The most sophisticated architecture diagram means nothing if the client doesn&#39;t trust that you understand their business, respect their constraints, and genuinely care about their success.</p><p>The secret playbook of consulting comes down to this: Technical skills get you in the door, but trust gets you invited back.</p><p>In the next post in this series, I&#39;ll reveal &quot;The Client Whisperer: Building Relationships That Survive Project Storms&quot;—the unwritten rules of managing client relationships through the inevitable challenges every project faces.</p><p>Until then, remember: In consulting, being right is only the beginning. Being trusted is what matters.</p><p><em>What consulting lessons did you learn the hard way? Share your experiences in the comments below!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9adfa39140bd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>