<?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 Craig Brown on Medium]]></title>
        <description><![CDATA[Stories by Craig Brown on Medium]]></description>
        <link>https://medium.com/@craig-at-everest?source=rss-63bd0f44b19b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*eZwe9mwzdaucOFAQdryM-g.jpeg</url>
            <title>Stories by Craig Brown on Medium</title>
            <link>https://medium.com/@craig-at-everest?source=rss-63bd0f44b19b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 10:13:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@craig-at-everest/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[I’ve helped over 100 startups launch and have some notes]]></title>
            <link>https://medium.com/everestengineering/ive-helped-over-100-startups-launch-and-have-some-notes-c05780a8f91d?source=rss-63bd0f44b19b------2</link>
            <guid isPermaLink="false">https://medium.com/p/c05780a8f91d</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Craig Brown]]></dc:creator>
            <pubDate>Thu, 14 May 2026 07:52:10 GMT</pubDate>
            <atom:updated>2026-05-14T08:14:40.941Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This is about framing what a launch looks like. It tracks early agile and lean startup practices and ideas and how what “launched” looked like changed, bringing us to what good looks like today.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QKO9X40pS_rDj5fgj8oBog.png" /></figure><p>Once upon a time Sprint Zero was workshops with stakeholders, brainstorming, alignment on goals, and developing a project plan together.</p><p>The value add from this was internal alignment on intent and rough alignment on the plan/time and effort to get to that launch.</p><p>Then it became design sprints with user research and voice of customer, on top of building consensus internally.</p><p>The value this added was better insight into what was needed from the user point of view, and to challenge internal assumptions with external perspectives. The view on “done” got more tentative, and people were more open to be flexible with the plan.</p><p>Then we also got started on infrastructure, provisioning services and databases, and then also some immediate features like SSO and landing pages.</p><p>This got us to a state where we could demo user experience faster, and start responding to feedback more quickly, decreasing waste and reaching an impactful launch faster.</p><p>Of course smart people also build in CD from week one, so we bundled that in by default.</p><p>Which was for our benefit. Because if you don’t get continuous delivery in place early you’ll pay for it by increasing workload each release, and also spending weeks at the end of the project cleaning up your mess.</p><p>Now…</p><p>Now ‘Sprint Zero’ is there to build just enough product to run real experiments, with some foundational user analytics, so that you have a working lab bench you can use to run experiments.</p><p>Those experiments will be on everything from UX, configuration, the features you need, who the client really is, how you position and sell it and much more.</p><p>The new value platform for the future is being able to test ideas in market and learn what it really takes to win, faster and cheaper.</p><p>We don’t think your business idea was wrong, but we are sure it wasn’t right. We’ve watched over 100 founders launch their business and ALL of the successful ones pivot once they make contact with the real market. Something in your original idea was probably important, but you were almost certainly naïve about how it should be put together and presented to the world.</p><p>So now, when we help a start-up launch, we’re not building toward a released MVP. We’re building toward a successful business. And the fastest way there is real experiments with real customers, because that’s how you find out what the business actually is, not what you thought it was when you wrote the deck.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c05780a8f91d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/everestengineering/ive-helped-over-100-startups-launch-and-have-some-notes-c05780a8f91d">I’ve helped over 100 startups launch and have some notes</a> was originally published in <a href="https://medium.com/everestengineering">EverestEngineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How does AI Disrupt your Company’s Strategic Power?]]></title>
            <link>https://medium.com/everestengineering/how-does-ai-disrupt-your-companys-strategic-power-fe57d761e6fe?source=rss-63bd0f44b19b------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe57d761e6fe</guid>
            <category><![CDATA[business-strategy]]></category>
            <dc:creator><![CDATA[Craig Brown]]></dc:creator>
            <pubDate>Sun, 07 Sep 2025 05:23:51 GMT</pubDate>
            <atom:updated>2025-09-07T05:33:20.780Z</atom:updated>
            <content:encoded><![CDATA[<p><em>At Product Camp Melbourne this year, I shared some thoughts on how strategy needs to be re-thought for digital product companies.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/928/1*ydra_F69Sn19ThEEbLY9jQ.png" /></figure><h3>An intro to 7 Powers</h3><p>Many of us have been leaning on Helmer’s 7 Powers to help us think about whether we have the right strategy, and enough power to see us outcompete in our industries.</p><p>I first learned about 7 Powers thanks to Tim Webster several years ago when he introduced me to the Acquired podcast. As I listen to the many American or European stories covered at Acquired (and now elsewhere) I think about businesses in Australia. I try to apply the 7 powers framework to our ecosystem and try to understand these businesses I work with better.</p><p>At Product Camp this year I posited the idea that AI technologies will disrupt business models and the 7 Powers model/advantages may no longer work for your company (and some of the Powers may be foundationally disrupted.</p><p><em>The conference talk itself began with a run through “What are the 7 Powers?” which I won’t repeat here. If you want to learn more on the model; see </em><a href="https://medium.com/@tomlente/book-summary-7-powers-the-foundations-of-business-strategy-4ede89dfdec7"><em>here for a summary</em></a><em>, </em><a href="https://7powers.com/"><em>here for the book</em></a><em>, and </em><a href="https://www.youtube.com/watch?v=hKq1_KPSqy0"><em>here for a discussion</em></a><em>.</em></p><h3>Local case studies</h3><p>I then asked the room to nominate what they thought the Powers of some of Melbourne’s most iconic digital brands — MYOB, REA, Xero and Seek.</p><ul><li><strong>MYOB</strong> — Branding (long-standing player), Switching Costs (accountants rarely switch).</li><li><strong>REA</strong> — Network Economies (dominant property marketplace), Branding (deep agent relationships).</li><li><strong>Xero</strong> — Switching Costs (hard to move once set up), Network Economies (accountants and app marketplace reinforce adoption).</li><li><strong>SEEK</strong> — Scale Economies (global reach), Network Economies (two-sided marketplace), branding (trusted name in jobs).</li></ul><p>I then asked everyone in the room to think about what sustainable advantages their company had. If you are early stage, you probably don’t really know for sure; discovering your long term advantages only comes with time and either wide or penetration into a big market.</p><h3>An activity to help you think</h3><p><em>So reader, now is the moment for you to pause and ask yourself which of the 7 Powers are you leaning it? Remember, you need more than one for a long term sustainable advantage.</em><br><em>Pick at least 2 from</em></p><ul><li><strong><em>Scale Economies</em></strong><em> — Costs per unit fall as output or users grow.</em></li><li><strong><em>Network Economies</em></strong><em> — Each new user makes the product more valuable to others.</em></li><li><strong><em>Counter-positioning</em></strong><em> — A new model incumbents can’t copy without hurting themselves.</em></li><li><strong><em>Switching Costs</em></strong><em> — Customers face pain, risk, or expense in moving to a rival.</em></li><li><strong><em>Branding</em></strong><em> — Trust and preference let you charge more or win more easily.</em></li><li><strong><em>Cornered Resource</em></strong><em> — Exclusive control of a valuable asset others can’t get.</em></li><li><strong><em>Process Power</em></strong><em> — Unique, improving processes that competitors can’t replicate.</em></li></ul><p>Maybe early-stage startup people have tentative assumptions rather than knowledge. Assumptions are a Product Manager Thing, and yes, we will come back to that thought.</p><h3>What will AI disrupt? You. It will disrupt you.</h3><p>It’s a legit question; does AI disrupt the whole 7 Powers thesis? Do new advantages emerge? Do some or even all of the existing one die? We don’t really know, but models are models, right? They come and go. They are framing tools to help us think and aren’t the actual real thing.</p><p>I am reminded that strategy is a map and maps are only representations of reality, not actual reality. “The map is not the territory” is a great line from Alfred Korzybsky who was trying to teach us that our mental models are imperfect and limited.</p><p>The 7 powers are fundamentally challenged by AI on several fronts; Accessing knowledge and executing via code, chatbots etc is now orders of magnitude easier than it was before. Two sided market places can now (or soon) be replaced by digital agents. Commodity service providers who defend their business with ‘local knowledge” can be disrupted because knowledge is virtually unlimited now. IP is no longer easily defended in any industry and the LLMs absorb and synthesise the total knowledge of the human race.</p><h3>Are our fundamentals broken?</h3><p>Do the 7 Powers stand up to the change AI is bringing? Will every white collar job be automated away? Will the Saas industry be replaced? These are all pretty big questions, and over sufficient time the answer is probably yes, but in the years ahead, the answers are more uncertain.</p><p>It can be a bit much, can’t it.</p><p>Let’s be practical and narrow our focus to our businesses. What assumptions are you building your business on? Which ones are firm, which can be disrupted, and what should you be doing about it?<br>Back in the workshop this was that classic moment where everyone starts talking to their neighbour for a few minutes shaking down this idea in context of their business. What do we need to think about differently?</p><p>The usual upshot of these sessions is “We have to go away and think and talk more about this!”</p><p><strong><em>Note to your future self: Book a workshop for your team with me!</em></strong></p><h3>Let’s look at the threats our four local heroes face.</h3><p>The <strong>Accounting software</strong> threat is both urgent and serious; Any minute a startup is going to turn up that acts as a book-keeper. All you will need to do is plug in to some banking APIs, send it your emails statements and put your receipts in a Google drive and it will magic away all the work. I think this is an existential threat to these businesses.</p><p>A person’s <strong>Job search</strong> is also likely to migrate to an agent led experience. The first thing they might do is ask Chat GPT “I am looking for a job, any suggestions?” and then the search will be coordinated from there. What does this mean for a marketplace like Seek? Does the supply side inventory still make them the actual platform for the industry, or can an agent bypass it and get good results? I am not sure what the right game plan is here.</p><p>Digital agents could search local <strong>Real Estate</strong> agent listings and disintermediate REA. Concierge services could emerge that help people find a best fit for housing and step in front of REA as the destination site that integrates all the other services. But on the other hand, the network effect and branding powers may withstand the threat with only some minor defences. You still need listings and human agents to source the houses, and you still need good inventory to be the go to spot on the internet.</p><h3>Next steps</h3><p>Don’t wait for your Kodak, Blockbuster, or Nokia moment.<br>There is a job to do with new disruptive technology, and it doesn’t always start with a clear problem to solve.</p><p>We need to be sensing and mapping new capabilities to opportunities, and developing those capabilities so that you can execute well into the future. A whole bunch of early-stage startup skills are going to become relevant again; especially living in ambiguity and uncertainty.</p><p>By talking about what powers your organisation’s success today and what is at risk, you can then develop a plan. That plan needs to map things from certainly true through to assumptions and wild assed guesses. You need prioritize your assumptions and risks, and then develop a program of exploration and experiments to test your assumptions and address the risks and opportunities you discover.</p><p><em>What is your strategic foundation? How secure is it? What assumptions are you relying on? Are you testing them to validate your plans?</em></p><p>Take some time. Talk it out. Capture your assumptions and risks, and then map them in terms of certainty and priority. You’ll then probe the future with multiple small explorations.</p><p>If you’d like a hand running this conversation, I am happy to help you with a workshop or series of workshops depending on the scale of your org.</p><p>Have fun with it. What a time to be alive!</p><p>Cheers,</p><p>Craig</p><p>(And don’t forget to <a href="https://www.linkedin.com/in/craigwbrown/">book that workshop</a>.)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe57d761e6fe" width="1" height="1" alt=""><hr><p><a href="https://medium.com/everestengineering/how-does-ai-disrupt-your-companys-strategic-power-fe57d761e6fe">How does AI Disrupt your Company’s Strategic Power?</a> was originally published in <a href="https://medium.com/everestengineering">EverestEngineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Adapting to change; A workshop case study]]></title>
            <link>https://craig-at-everest.medium.com/adapting-to-change-a-workshop-case-study-71bc238ab0f0?source=rss-63bd0f44b19b------2</link>
            <guid isPermaLink="false">https://medium.com/p/71bc238ab0f0</guid>
            <category><![CDATA[change-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Craig Brown]]></dc:creator>
            <pubDate>Mon, 10 Feb 2025 01:04:59 GMT</pubDate>
            <atom:updated>2025-02-10T04:01:46.131Z</atom:updated>
            <content:encoded><![CDATA[<p>This blog post is based on a meetup I hosted in February 2025 with Business Analysts and Product Managers. The theme was “adapting to change.”</p><p>This workshop method is tabled for you because let’s face it; it’s been a hell of a few years, and there is a lot of uncertainty in our industry. You probably need to think about how you and your team are going to adapt.</p><p>By tackling these topics in this particular way you can reflect on industry trajectories, what has worked (and not worked) in recent years, and be mindful about how you evolve as we all move into the future.</p><p>By thinking ahead, and building a competence in adapting, you’ll be more able to succeed in your endeavours than those that cling to last year’s thinking.</p><p>The form and topic could be used with any group; different crafts or cross-functional teams. You could even apply it to strategy and org design.</p><p>In this meetup I ran the workshop in three stages;</p><ol><li>Looking back at the last 5 years of changes</li><li>How do our Values and Principles help us?</li><li>Thinking about the future, how might we evolve</li></ol><p>I have shared some images from the workshop&#39;s Miro board to illustrate the activity, as well as summaries of the doiscussion. As always the richness of data is in the conversation you have with your colleages, so I encourage you to have discussions like this where you work.</p><blockquote><em>If you’d like us to come run a session like this, please </em><a href="/service/mailto:hi@everest.engineering"><em>get in touch</em></a><em>. Contact details at the bottom of the post.</em></blockquote><h3>Part 1: Looking Back</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*puIvBWz0mi_XKXOdSgeLLg.png" /><figcaption>The last 5 years has been… dynamic</figcaption></figure><p>The past five years have been a rollercoaster. We started with a global pandemic that forced businesses to adapt overnight. Then came the age of remote work, the rapid acceleration of AI, and the mass layoffs for everyone, and possibly most acutely for the agile coaches and scrum masters as the Agile transformations declared “Mission Accomplished.”</p><p>Now, as we head into 2025, things feel different. Cost-cutting, job uncertainty, and political instability are dominating the conversation.</p><h4>Work Culture: The Remote Work Experiment is Over</h4><p>Back in 2020, remote work wasn’t a choice; it was survival. And for a while, it worked. Organisations figured out how to make it productive, people enjoyed the flexibility, and for some, it felt like we’d never go back to the old ways.</p><p>By 2022, hybrid models started to take shape, and businesses got better at handling remote teams. But then, cracks started to show. Senior leaders — many of whom never liked remote work in the first place — started pulling people back into the office.</p><p>Now, in 2025, the writing is on the wall: flexibility is shrinking. Some companies are still hybrid, but the golden days of “work from anywhere” are fading. For some, work-life balance is being compromised again, and people are realising they’ll need to fight for the autonomy they once had. For others, being back n the office separates home and work, or connects people socially.</p><h4>AI: A Productivity Boost That Became a Threat</h4><p>March 2023 was a turning point — ChatGPT-4 dropped, and suddenly AI was everywhere. People used it to automate boring work, improve Agile coaching, and even rethink knowledge work. For a moment, it looked like AI would be a fun and exciting productivity win.</p><p>But by 2024, the narrative shifted. Companies started replacing jobs, or curtailing staff growth in anticipation of AI solutions. More layoffs followed, and suddenly everyone was scrambling to explore these tools and what they mean. The hype turned into a race for survival, and we’re now seeing a world where AI-driven work is hard to measure, hard to govern, and not always as reliable as we thought.</p><h4>Cost-Cutting and Job Uncertainty: From Investment to Retrenchment</h4><p>2020 to 2022 was an era of investment. Companies were doubling down on agile, the startup economy was booming. There was plenty of investment in being a great place to work, leadership development, and new ways of working. There was industry-wide optimism.</p><p>Then, in 2023, the economic climate shifted. By 2024, cost-cutting had become the dominant strategy. Product managers, Agile coaches and transformation leaders were being let go, and suddenly the emphasis was on leaner teams, fewer resources, and proving your value every day.</p><p>Now, in 2025, job security remains a real concern, and the trend is clear: if you’re not delivering clear business value, you’re at risk. There’s less patience for experimentation and more focus on short-term results.</p><h4>Political and Market Instability: The New Normal</h4><p>Back in 2020, it was COVID. Now, in 2025, it’s political and economic instability driving uncertainty.</p><p>Trump’s back in office, and while no one knows exactly how that’ll play out, it’s already fueling more regulatory shifts and uncertainty in global markets. Tech is under more scrutiny, and there’s growing tension around AI regulation, ethics, and what comes next.</p><p>The bigger picture? Instability is here to stay. Businesses will need to stay adaptable, and professionals need to keep re-skilling and staying relevant in a market that’s constantly shifting.</p><h4>What’s Changed Over Time?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/749/1*UuxkdT1M9HMboJkjxiewIQ.png" /></figure><h4>The Good vs. The Bad</h4><p>The Good:</p><ul><li>AI actually is improving productivity in many ways.</li><li>Hybrid work is still viable in many places.</li><li>Agile principles still hold up despite shifting business priorities.</li></ul><p>The Bad:</p><ul><li>Layoffs and cost-cutting are the new normal.</li><li>Less investment in coaching, capability development, and leadership.</li><li>AI hype turned into AI job replacement fears.</li><li>Political and market instability is making long-term planning harder.</li></ul><h4>Where Will We Go from Here?</h4><ol><li>Remote work is no longer a given — Some companies will keep hybrid, but flexibility is shrinking.</li><li>AI will keep disrupting work — The question is whether it will empower people or make them redundant.</li><li>Job security is getting shaky — If you can’t prove your value, expect pressure.</li><li>Regulation and market instability will shape the next five years — Businesses need to stay adaptable.</li></ol><p>The people who stay flexible, keep learning, and focus on delivering real business impact are the ones who will thrive in this next phase. It’s a different game now, and adaptability is essential.</p><p>However…</p><p>When adapting, we need to think about what to hold onto and what to let go of. This next activity is an introspective one that helps us understand how to move forward.</p><h3>Part 2: Our Values drive our future success</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d_0qm9LcyL8ApuPP6NuK9Q.png" /><figcaption>What’s most important to our work?</figcaption></figure><h4>What Really Drives Success at Work?</h4><p>Looking at this diagram, it’s clear that success isn’t about following a rigid methodology or ticking boxes — it’s about trust, communication, and delivering value. The closer to the center, the more essential these values are. The further out you go, the more you hit things that slow us down, distract us, or just don’t matter.</p><h3>🎯What Actually Matters (Inner Circle)</h3><p>At the core, the things that <strong>really make a difference</strong> are simple but powerful:</p><ul><li><strong>Be reliable</strong> — If people can’t count on you, nothing else matters.</li><li><strong>Active listening</strong> — Communication isn’t just about talking, it’s about understanding.</li><li><strong>Show empathy</strong> — Work is about people, not just processes.</li><li><strong>Transparency across the team</strong> — If information is locked away, it slows everyone down.</li><li><strong>Put people and customer value first</strong> — If you’re not delivering value, why are you even here?</li><li><strong>Iterate and learn</strong> — Progress isn’t about getting everything perfect up front; it’s about adjusting as you go.</li></ul><p>This is the <strong>real foundation of good work</strong> — it’s what makes teams effective, creates better products, and keeps organizations moving forward.</p><h4>🎯Good, but Context Matters (Mid-Layer)</h4><p>These are values that are <strong>still important, but they depend on the situation</strong>:</p><ul><li><strong>Manage work, not people</strong> — Autonomy is great, but some people need more support than others.</li><li><strong>Simplicity / MVP</strong> — Doing just enough is smart, but not if it means cutting corners.</li><li><strong>Respect</strong> — Critical, but it should be a given, not something we need to constantly reinforce.</li><li><strong>Start together</strong> — Alignment is important, but sometimes you just need to <strong>get moving</strong>.</li><li><strong>Tolerance &amp; feedback loops</strong> — Feedback is great, but not everything needs a retrospective.</li></ul><p>These principles <strong>support</strong> effectiveness, but they aren’t the <strong>core drivers</strong> of success. They work best when <strong>applied with common sense</strong> — not as hard rules.</p><h4>🎯What Slows Us Down (Outer Layer)</h4><p>Now we’re getting into the stuff that <strong>gets in the way rather than helps</strong>:</p><ul><li><strong>Face-to-face communication when it could’ve been an email</strong> — Stop wasting time in unnecessary meetings.</li><li><strong>Old systems, old thinking</strong> — Just because something worked before doesn’t mean it should still exist.</li><li><strong>Concerns &amp; clarity discussions that go nowhere</strong> — Endless analysis without action is just procrastination.</li></ul><p>These are the <strong>things we should actively push back against</strong>. They slow down decision-making, kill momentum, and make work more frustrating than it needs to be.</p><h4>So What’s the Takeaway?</h4><ul><li>The best professionals focus on people, trust, and delivering value.</li><li>Processes, frameworks, and methodologies help, but they’re secondary.</li><li>The biggest obstacles are outdated ways of thinking, unnecessary complexity, and poor communication.</li></ul><p>If you want to be effective at work, lean into the core values, apply the mid-layer principles when they make sense, and actively push back on the outer circle distractions. That’s how you get things done.</p><h3>Part 3: Looking Ahead</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q5HTuEDKdW7uMu_DageCaw.png" /><figcaption>We Used Scamper and a tool</figcaption></figure><h3>Evolving Our Practice</h3><p>The future isn’t waiting for us. The way we operate — our habits, our approaches, even our beliefs about what “good” looks like — has to evolve. Otherwise, we risk getting stuck in outdated ways of working that don’t serve us anymore.</p><p>For this section of the workshop I grabbed an old innovation frameowork called Scamper.</p><figure><img alt="It’s an old code but it checks out" src="https://cdn-images-1.medium.com/max/660/1*KCHxhO2Q0-QHaYk8FBv66A.gif" /></figure><p>We used the <a href="https://www.interaction-design.org/literature/article/learn-how-to-use-the-best-ideation-methods-scamper">SCAMPER framework</a> as a way to push ourselves beyond default thinking. It forced us to look at how we could replace, combine, adapt, modify, reuse, eliminate, or rearrange the way we work.</p><p>Some things are obvious: AI should handle more of the grunt work — whether it’s eliciting requirements, generating reports, or surfacing insights from multiple tools — so we can focus on higher-value thinking. We need to be deliberate about where we spend our time, moving away from manual research and repetitive tasks and into deeper, more strategic contributions. Some things are still best done by people — real communication, deep stakeholder alignment, and making sense of ambiguity — but AI can help clear space for us to do those things better.</p><p>Other shifts are more subtle. The way we structure teams is changing, with AI acting less as a tool and more like an extra team member. Leadership isn’t about managing tasks anymore, it’s about creating clarity in a faster-moving, more automated environment. The idea of a “rigid job description” is becoming outdated. The smartest professionals are already diversifying their skills, thinking about second careers or side hustles, and making sure they’re future-proofing themselves instead of waiting for their roles to change beneath them.</p><p>Some things just need to go. Endless meetings that could have been an email, overly rigid release processes, excessive stakeholder balancing when data-driven decision-making should take the lead. If it’s slowing things down, it’s not worth keeping.</p><p>And then there’s the question of how we sequence work. Instead of writing requirements first and then prototyping, why not start with an experiment and work backwards? Instead of expecting humans to do all the early thinking and AI to clean up after, why not let AI generate a first pass and then refine it? The way we structure our work matters as much as what we do.</p><p>The people who thrive in this next phase of work won’t be the ones who cling to how things have always been done. They’ll be the ones who are willing to challenge assumptions, rethink processes, and actively shape their roles instead of reacting to change when it’s too late. AI won’t replace people who think this way — it’ll make them even more valuable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZOK67Q0JKVrdE3MWXurmPw.png" /></figure><p>If you’d like to run a workshop with your team about the future of work, <a href="/service/mailto:hi@everest.engineering">get in touch today</a>. Contact us via <a href="https://www.everest.engineering/contact">www.everest.engineering</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71bc238ab0f0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Everest wins Zero Distance Emergence Excellence Award]]></title>
            <link>https://medium.com/everestengineering/everest-wins-zero-distance-emergence-award-d19684b5c8a7?source=rss-63bd0f44b19b------2</link>
            <guid isPermaLink="false">https://medium.com/p/d19684b5c8a7</guid>
            <dc:creator><![CDATA[Craig Brown]]></dc:creator>
            <pubDate>Wed, 25 Sep 2024 02:21:05 GMT</pubDate>
            <atom:updated>2024-10-31T07:15:47.755Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2aY685NLHXnnefSbtGRFcg.jpeg" /><figcaption>ZeroDX Emergenct awards</figcaption></figure><p><strong>How RenDanHeYi Aligns with Our Management Philosophy at Everest Engineering</strong></p><p>Staying ahead isn’t just about product innovation — it’s about how we organise ourselves to deliver great outcomes for our clients and our teams. At Everest Engineering, our approach to management naturally aligns with the principles of the <a href="https://www.rendanheyi.com/home">RenDanHeYi model</a>, developed by <a href="https://www.forbes.com/sites/billfischer/2023/11/15/zhang-ruimin-a-lifetime-of-maximizing-human-value/">Zhang Ruimin</a> at Haier.</p><p>This alignment isn’t accidental; it’s a reflection of our shared belief in empowering teams and delivering value through autonomy and accountability.</p><p>Our approach to work has recently been recognised on the global stage. Earlier this year we were nominated by the <a href="https://www.desirablefutures.group/en/">Desirable Futures</a> team as one of the most innovative companies in Australia. The nomination was evaluated by the <a href="https://business-ecosystem-alliance.org/2024/08/09/can-any-organization-make-zero-distance-work/">Thinkers 50 Group</a> and inspired by Haier’s RenDanHeYi model.</p><p><em>We’re proud to announce that have won an Emergence award at the ZeroDX awards in Qingdao this month. This recognition highlights the strength of our approach and the impact it’s having not only on our clients but also on the broader industry.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/821/1*-S8EDDgHoJFkJopwVj71yA.jpeg" /><figcaption>Everest’s award for innovations in how we work together</figcaption></figure><p><strong>So, what’s RenDanHeYi all about?</strong></p><p>RenDanHeYi centers on decentralizing decision-making and pushing authority to those closest to the customer. It challenges traditional hierarchies by creating small, independent teams — essentially mini start-ups within a larger organization. Each of these teams owns its outcomes, with success directly tied to the value they create for customers.</p><p><strong>Where does Everest Engineering fit into this?</strong></p><p>At Everest, our way of working is naturally in tune with RenDanHeYi. We’ve built a structure where our teams — whether they’re in India, Malaysia, or Australia — have the autonomy to make decisions that directly impact our clients. These teams operate with a high degree of independence, allowing us to remain agile and responsive to our clients’ needs.</p><p>Accountability is also central to how we operate. Our teams own their results, and we trust them to innovate and adapt as the situation demands. This alignment with RenDanHeYi has allowed us to create an environment where innovation is more than just a goal — it’s a built-in expectation.</p><p><strong>Our approach to management</strong></p><p>While we align with many of the principles of RenDanHeYi, our management approach has its own unique nuances. We have practice leaders like Chris, Pilar, and Martin, along with our community of practice hosts, and three pairs of Crew Leads focused on startups, scale-ups, and enterprises. Their role isn’t about telling people how to work — it’s about ensuring our people’s wellbeing and success while also managing customer experience, growth, and revenue.</p><p>We believe that management is about creating the right environment for our people to thrive. This means managing systems and processes that support our teams, rather than micromanaging their day-to-day work. We focus on their wellbeing and provide the support they need to succeed, while trusting them to manage themselves and their work.</p><p>Leadership at Everest isn’t confined to a role or title. We expect leadership from everyone, at the right time and in the right context, while also making space for others to lead when it’s their turn.</p><p>We also recognise the importance of having project or team leads. These leads serve as the principal point of contact for questions and to disseminate information. Their role is crucial as a safety net — if a team fails to hold itself to the standards it has set, the lead is there to spot when help is needed and to call for it. They don’t need to solve every problem themselves, but they ensure that the right support is available when necessary.</p><p><strong>Looking forward</strong></p><p>At Everest Engineering, our management philosophy isn’t just aligned with the principles of RenDanHeYi — it’s a reflection of how we believe a modern organization should operate. By focusing on autonomy, accountability, and the wellbeing of our teams, we’ve created an environment where everyone is empowered to lead, innovate, and deliver outstanding value to our clients.</p><p><em>Winning the Emergence award at the ZeroDX awards this month in Qingdao is a testament to the effectiveness of our approach and our commitment to pushing the boundaries of what’s possible in our industry.</em></p><p>Want to know more?</p><p><a href="https://www.linkedin.com/in/craigwbrown/">Get in touch with me</a> to hear our story in more details, or to see how we can innovate and learn together towards a bigger and brighter future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L-C3NyX_ddk4ht_MKH6bKQ.png" /></figure><p>Thanks to the <a href="https://www.desirablefutures.group/en/">Desireable Futures</a> team for spotting us and nominating us into this process.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d19684b5c8a7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/everestengineering/everest-wins-zero-distance-emergence-award-d19684b5c8a7">Everest wins Zero Distance Emergence Excellence Award</a> was originally published in <a href="https://medium.com/everestengineering">EverestEngineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Everest at the Zero Distance Awards]]></title>
            <link>https://medium.com/everestengineering/everest-at-the-zero-distance-awards-bf544d9342ce?source=rss-63bd0f44b19b------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf544d9342ce</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Craig Brown]]></dc:creator>
            <pubDate>Tue, 17 Sep 2024 00:11:16 GMT</pubDate>
            <atom:updated>2024-09-17T00:11:16.255Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0Sj1Z_sj-SGo90S21VxRWw.png" /><figcaption>Growing together</figcaption></figure><p>I’ve been invited to the <a href="https://business-ecosystem-alliance.org/zero-distance-organizations/">ZeroDistance Excellence Awards</a> in Qingdao this week. It’s a recognition of our innovative work here in Australia, and we’re thrilled to be included.</p><p>This award stands apart from others; it’s not about paying for recognition, it’s about genuine innovation. It’s hosted by a true giant in the field, Zhang Ruimin of Haier, who has championed decentralized decision-making, empowerment, and customer intimacy on a massive scale.</p><p>Reading about Haier’s journey and comparing it to our own at Everest reveals striking similarities. We’re certainly smaller in scale, but we share the same unwavering focus on accountability, leadership at all levels, and the relentless pursuit of value.</p><p>What I admire most about Everest is our collective commitment to achieving exceptional outcomes for both our clients and their end users. This often requires us to challenge the status quo, which can lead to tension. We’ve developed a coaching strategy to address this, encouraging everyone to “meet people where they are and learn together.”</p><p>From the beginning, our priority at Everest was to build a company that people truly love to work for. We wanted to foster fulfilling careers and become a valued partner in our ecosystem.</p><p>As we evolve, this mission remains at our core, but we’re refining our focus on being that great partner. It’s evolving from just delivering frontline value, to actively helping organizations transform their cultures, discover what “great” truly means, and ultimately, rediscover the joy in their work — even amidst the challenges of recent times.</p><p>If you’d like to speak with us, <a href="https://www.linkedin.com/in/craigwbrown/"><strong>get in touch</strong></a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf544d9342ce" width="1" height="1" alt=""><hr><p><a href="https://medium.com/everestengineering/everest-at-the-zero-distance-awards-bf544d9342ce">Everest at the Zero Distance Awards</a> was originally published in <a href="https://medium.com/everestengineering">EverestEngineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Now that “Agile is Dead” we can all get more agile]]></title>
            <link>https://medium.com/everestengineering/now-that-agile-is-dead-we-can-all-get-more-agile-99890ed72c4a?source=rss-63bd0f44b19b------2</link>
            <guid isPermaLink="false">https://medium.com/p/99890ed72c4a</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Craig Brown]]></dc:creator>
            <pubDate>Fri, 07 Jun 2024 01:26:55 GMT</pubDate>
            <atom:updated>2024-10-28T00:46:20.488Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pzc4Gj_pwMRrkV5fp0LvUw.png" /></figure><p>With the <a href="https://www.infoq.com/presentations/cockburn-bury-not-praise-agile/">collapse of the Agile Industrial Complex</a> you may be wondering; Does any of that stuff matter any more? Of course it does. Good practices are good practices, regardless of the ‘Big Idea’ or movement they are associated with.</p><p>But which practices matter? Which are universal and which are situational? How should you prioritise what you pull into your organisation?</p><p>It’s time for us all to shift our focus from following a prescribed methodology or framework to selecting and adapting practices that best suit your specific context. This is a return to how we used to adopt agile stuff in the early days; one small bite-sized improvement at a time.</p><p><strong>Which Practices Matter?</strong></p><p>There are fundamental principles and practices that tend to be universally beneficial across most organisations and situations:</p><ul><li><strong>Customer Focus:</strong> Prioritise understanding and delivering value to customers.</li><li><strong>Collaboration:</strong> Foster effective communication and teamwork within and across teams.</li><li><strong>Iterative Development:</strong> Embrace a cycle of continuous improvement through frequent feedback and adaptation.</li><li><strong>Technical Excellence:</strong> Emphasise high-quality craft skills, automated testing, and continuous delivery.</li><li><strong>Delegate Decision-Making:</strong> Trust and empower teams to make decisions and take ownership.</li></ul><p>These core principles often translate into specific practices like:</p><ul><li><strong>User Stories:</strong> Capture customer needs in a concise, actionable format with clear measures of performance.</li><li><strong>Stand-ups:</strong> Hold daily brief meetings for team synchronisation, and as a platform to find ways to help each other.</li><li><strong>Retrospectives:</strong> Regularly reflect on how you work together, and improve your team’s processes and environment.</li><li><strong>Quality Systems:</strong> Ensure code quality through peer feedback like automated tests, pair programming or code reviews.</li><li><strong>Test-Driven Development (TDD):</strong> Write tests before code to guide development and improve your design skills.</li></ul><p><strong>Prioritizing Practices</strong></p><p>To determine which practices to adopt, consider the following:</p><ol><li><strong>Context:</strong> Assess your organization’s specific needs, challenges, and goals.</li><li><strong>Experimentation:</strong> Start with a few core practices and gradually introduce others based on their potential value and fit.</li><li><strong>Get early wins: </strong>Don’t try to solve your hardest challenges first. Build up your improvement fitness and get some early wins to build momentum.</li><li><strong>Feedback:</strong> Continuously gather feedback from your teams to assess the effectiveness of adopted practices and make adjustments as needed.</li><li><strong>Adaptability:</strong> Be prepared to modify or discard practices that don’t work in your context.</li></ol><p>The key is to prioritise practices that align with your organisation’s values, promote collaboration and continuous improvement, and ultimately deliver value to your customers.</p><p><a href="https://www.everest.engineering/academy">Let us know</a> if you would like a deeper dive into any of these practices or further guidance on prioritising them for your organisation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99890ed72c4a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/everestengineering/now-that-agile-is-dead-we-can-all-get-more-agile-99890ed72c4a">Now that “Agile is Dead” we can all get more agile</a> was originally published in <a href="https://medium.com/everestengineering">EverestEngineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Writing Better User Stories]]></title>
            <link>https://medium.com/everestengineering/writing-better-user-stories-836118e514a2?source=rss-63bd0f44b19b------2</link>
            <guid isPermaLink="false">https://medium.com/p/836118e514a2</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[user-stories]]></category>
            <dc:creator><![CDATA[Craig Brown]]></dc:creator>
            <pubDate>Tue, 05 Sep 2023 09:07:33 GMT</pubDate>
            <atom:updated>2023-09-05T09:30:32.948Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*A5RcMP_8wmL79wLZ" /></figure><p><em>The patterns of a product owner writing user stories for software development teams is an opportunity to be improved upon.</em></p><p>On Tuesdays at 11am, Mark walks over to the round table near the window. The team see he is ready and wrap up the tasks they are on. Justin heads over to the kitchen and grabs a fresh water. Jerome grabs the two index cards that are still in play from the whiteboard and brings them over to the table as well. Zoltan grabs some sharpies and a stack of post-it notes and walks over with David. They sit around the table.</p><p>I walk across and ask if I can sit in and observe the meeting.</p><p>Mark plays down six index cards onto the table like a blackjack dealer. Unlike blackjack the cards are all face up with Mark’s almost legible scrawl on them.</p><p>Mark picks one of the index cards up and starts reading it to the team. There is a back and forth across the table about why this user story, how does it help the customer, and how it might be implemented. After about 6–7 minutes a consensus is reached and Zoltan grabs the card, flips it over and writes a few acceptance criteria on the back, reading them aloud to the team as he writes. The other software developers on the team chip in with minor adjustments to the phrasing.</p><p>By the end of the session, all six cards have been accepted into the sprint and each of Mark’s index cards have also been marked up with the handwriting of the team members on the back.</p><p>The guys started to shift, getting ready to get up and head back to their desks to get a little more work done before heading out together for some Korean Fried Chicken (and beer.)</p><p>“Hey, before you go, can I ask a couple of questions?”</p><p>Everyone settles back into their seats and look at me expectantly.</p><p>“It’s interesting to me that each of you on this team have written on the cards. You all took turns to write up the acceptance criteria. Why is that?”</p><p>“Well,” says Justin, “If I write the card, then I know what I mean. If someone else writes the card, I have to struggle to remember the details of this conversation and probably have to repeat most of it in three or four days’ time.”</p><p>“It’s just easier this way” says Jerome.</p><p>“Cool. When did you start doing this?”</p><p>“I can’t remember. It just started one day. It didn’t come out of a retro or anything, but we did used to talk about how often we would repeat the user story discussion over a week or fortnight,” said Jerome.</p><p>There are fundamental reasons why this practice of shared story writing is better than having a product owner or business analyst be the one to exclusively write the user story cards.</p><p>Think about your own experience listening to others.</p><p>Your attention wanes in and out. You remember parts but not the whole of conversations. And the things that stand out in your memory the most aren’t necessarily the most important things.</p><p>However, when you take notes things change. For a start you need to make choices about what to write down. This makes you think about the content in more than one way — you are listening to it, engaging with the idea behind it, thinking about which points you want to focus on in your notes and also choose the words you use to represent the idea. Finally, your body also has to contribute to the note taking. Your hand moves a pen across some paper. Your eyes then read it to confirm what you have written is correct, and then you process the idea again.</p><p>All of this is going on almost simultaneously.</p><p>As you can see your brain is working much more when taking notes than just listening. This means that the memory around your idea is being imprinted much more firmly in your head than if you had just been listening, or even if you have been engaged in a discussion. You are creating multiple connections in your memory to the idea through these interactions and transaction.</p><p>Note taking is a powerful tool when trying to understand and later recall an idea.</p><p>(A side note; the act of physically writing appears to be a more powerful tool for understanding and remembering than typing. Even holding an index card improves understanding more than reading a screen because of the same multi-sensory processing going on.)</p><p>“Nice. Let me ask you another question,” I said. It was almost time to wrap up. The fried chicken was calling. “If this is a good practice, what would make it better?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*thJAby2ndwzS4Gt4" /><figcaption>“We shouldn’t let Mark touch the cards at all”</figcaption></figure><p>The team looked across to Mark, the product owner. A pause. Everyone thought for a moment. One of the guys was chewing his inner cheek as he thought. Zol twirled a pen around his finger. Then David, the team’s designer spoke up.</p><p>“We shouldn’t let Mark touch the cards at all.”</p><p>Mark was confronted by this idea.</p><p>“I don’t feel comfortable with turning up without cards to talk to.”</p><p>“That’s okay. You bring your cards, but we will rewrite our own.”</p><p>There is another opportunity in writing cards rather than receiving them. Can you guess what it is?</p><p>We sit at the table described above. I’m the product owner and I hand you a card with my user story on it. I tell you what the customer goal is, their motivations, the constraints and related rules around the user story. You listen attentively. It seems kind of obvious. You ask one or two questions about what I explain.</p><p>At the end of this discussion, because I am diligent I ask you; “Do you understand what needs to be done?”</p><p>You give a short nod affirming you understanding and head off to do the work.</p><p>That sounds straightforward and simple, right?</p><p>Now imagine this scenario.</p><p>Same job, but this time I hand you a pen and paper and you write the notes. I still tell you the same things but this time you are actively asking questions and drilling into what I am saying because you are writing notes down. You choose the description. You use your own mental models to frame the written description. And at the end you say what you understand the job to be, by reading out what’s on the card.</p><p>Which of these two scenarios is going to better equip you to go away and do the work?</p><p>Mark and the team tried the experiment and it was useful for a while. Over time they vacillated between Mark writing cards and the team writing the cards. They are a tight knit group and these days anyone writes whatever needs writing regardless of role.</p><p>There was one last effect I saw as they played this out, and it isn’t specific to the technique. It’s more about the people; By putting the card writing in the hands of the delivery team it put responsibility into their hands to pointedly and specifically ask “What’s in this for the customer.” Over and over again they guys asked that question. They were always very customer centric, but they were no longer being told. They were actively asking. That helped the knowledge acquisition and it helped memory and focus. It also helped with prioritization and managing scope better.</p><p>It’s funny. People like to find patterns and follow them. Inherent in high performing teams is the need to go farther and do better. The job isn’t done when you have your requirements on a pin-board and can ship features fortnightly. You don’t follow a manual.</p><p>The fundamental thing about this agile movement is learning through doing. You inspect and adapt. You ship and get feedback. You collaborate, deliver, reflect, and improve. You explore and learn. And that means experimenting and researching.</p><p>The scientific theory behind these ideas idea is pretty well established, although there is debate about how to make the most impact for memory. And it’s intuitively true to most people when you describe the ask over tell mode of communicating. Most people just get it. Still, people don’t change their habits without expending their limited energy.</p><p>To help you shift I want to ease you in with a low-cost experiment.</p><p>Share this post with your team mates and talk about it together. Propose that you all run the new card dynamic as an experiment in your next sprint. If your Product Owner is currently writing ALL the cards, maybe take the first step of just taking over acceptance criteria. But why stop there. It’s an experiment. You could just take over the whole card writing thing and give it a shot.</p><p>Then, at the end of each week, maybe for two sprints, talk about whether the new card dynamic has paid off in any ways.</p><p>Here are some links to more on this topic in case you want to go deeper.</p><p>Some details of this anecdote have been simplified to make the point, but this is a real case study with a real team.</p><p>As always I love to hear feedback if you try any of my ideas out. Comment below, tell me direct etc.</p><p><em>Originally published at </em><a href="http://www.betterprojects.net/2017/05/writing-better-user-stories.html"><em>http://www.betterprojects.net</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=836118e514a2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/everestengineering/writing-better-user-stories-836118e514a2">Writing Better User Stories</a> was originally published in <a href="https://medium.com/everestengineering">EverestEngineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Management at Scale, Part 2]]></title>
            <link>https://medium.com/everestengineering/product-management-at-scale-part-2-1bfbc9681a2a?source=rss-63bd0f44b19b------2</link>
            <guid isPermaLink="false">https://medium.com/p/1bfbc9681a2a</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Craig Brown]]></dc:creator>
            <pubDate>Mon, 14 Aug 2023 05:09:59 GMT</pubDate>
            <atom:updated>2023-08-14T10:23:33.172Z</atom:updated>
            <content:encoded><![CDATA[<p><em>The premise of this ‘talk converted to blog series’ is that the practices, frameworks and methods discussed among and employed by product managers are insufficient at any significant scale.</em></p><p><em>Go back to </em><a href="https://medium.com/everestengineering/product-management-at-scale-part-1-ef1eeea299a3"><em>Part 1</em></a><em> to get context.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*nvCTS4otMmpLTikY.png" /></figure><p>We wrapped up the last post with the assertion that the usual things we talk about in Product Management discourse are important, but insufficient at scale.</p><p>I then called out six concepts that need to be addressed to orchestrate product management across large teams. They are; Complexity, Uncertainty, Responsibility, Trust, A Shared Language and Power.</p><p>These are the things that program management offices, standards groups and the like are trying to address, although often without consciously knowing that it is these precise things. Perhaps they speak about risk as their unifying idea. Risk is a pretty broad abstraction, though, and as we so often see — when the thinking is at the wrong level, so are the results.</p><p>In order to be more precise, I’ll be using these six ideas to reframe what we need to be doing.</p><blockquote>Complexity, Uncertainty, Responsibility, Trust, A Shared Language and Power.</blockquote><p>Before I get into the instructional part of this talk, I’ll share a story that illustrates some key ideas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/969/1*EVqhoBNZBLKy6I3JGMRCDw.png" /><figcaption>Taking Henry to work, 2009</figcaption></figure><p>In 2009 I was project managing a software project for a government agency. The agency, like many government departments, had an IT team fuelled by talented people who wanted to good work for their citizens, but were beset by the usual challenges of government; competing agendas, an organisational culture built around compliance and risk avoidance, and never enough money or sustained attention to transcend the tactical.</p><p>In this case however, through fortune, an alignment of coincidences, and the sheer bloody mindedness of a few individuals, this organisation managed to pull off something amazing. It successfully completed a multi-year, multi-million dollar IT re-platforming project.</p><p>Even more remarkable, it was on budget, on time and even exceeded user expectations in terms of what it could do and how easy it was to use. What happened? Plenty. You could write an opera around some of the drama on the journey. But the thing I want to share with you today is the magic of collaboration and how that plays into our six big ideas.</p><blockquote>Complexity, Uncertainty, Responsibility, Trust, A Shared Language, Power</blockquote><h4><strong>The ITIL challenge</strong></h4><p>Early in the project, the team that was building the new software solution were blocked from progress because the ITIL driven operations team didn’t have enough capacity to support this new project team. At first, the team were frustrated by the blocker, but then when they realised there were no other options, they asked the infrastructure team what they could do to help make capacity.</p><p>Infrastructure teams don’t usually get offered help from Dev teams and in those days there was only so much they would share anyway, but they found some low risk work they could outsource, and share they did. The software team built capacity, and also goodwill.</p><h4>The user challenge</h4><p>The second challenge the team faced in this story was getting the users to buy-in to the changes the team wanted to bring. Government IT departments are known the world over for coming in years late, over budget with underwhelming products. The user groups were call centre and process workers who supported citizens wanting to use particular services. They needed changes, and they needed simplification in their workflows. Demand keeps growing, but headcount is limited. You know the story.</p><p><em>(Sorry for the concealing the specifics of the org, but, well… you know how it is.)</em></p><p>Regardless, the frontline workers were lukewarm at best about their interactions with the IT department. Something akin to “I’ll trust you when I see some results.” So the development team gathered some power users and incorporated them into their requirements discussions, and in addition, once they got their first version of working software out, they went and sat with users at each release to observe, support and take feedback.</p><p>Being there on the ground shortened the cycle of feedback to the dev team, and also enabled small, high impact things to bypass the usual backlog planning process. An example of this was the desire of frontline workers to tab from field to field. It took less time to implement that change than it would have taken to get it into a backlog, let alone prioritise it against other things.</p><p>The steady flow of value, the face to face interactions, and ‘turning up’ with the releases really helped build the relationship between the developers and the user groups.</p><h4>The regulatory challenge</h4><p>The third challenge of this story was further upstream in the requirements&#39; hierarchy; the regulators and parliament. The regulators had a similar experience in their careers to frontline users. A lack of direct and intimate contact with the software people meant they didn&#39;t know how to best frame requirements, and requirements were often intermediate by someone who only partially understood the real issues. <em>Hello, every BA ever.</em></p><p>As a result, these analysts often built in elements of ‘how’ to solve for things via regulations and laws that went to parliament, and those constraints would make implementation much more complex and difficult.</p><p>The lead BA on this project team developed a relationship with some of the regulatory officers and explained the consequences of too strict a requirement. Examples were shared, trade-offs were discussed, and in the end the regulatory analysts became much more oriented to the outcome than the instrument. Without any fuss the regulatory analysts (and the minister, and parliament, probably unwittingly) plugged themselves into the iterative development process.</p><p>To this day, this project stands out as remarkable.</p><p>It built an end to end product development process that incorporated the IT governance processes, the regulators and parliament and the users into one shared venture. Government IT projects just don’t do that (1).</p><p>How did it get there?</p><p>The team constantly looked outward and paid attention to the stakeholders and built relationships. They listened to what people asked for and heard beyond the specifics into the intent. They treated everyone in this network like a team member and found the shared desires that pulled everyone together. They got runs on the board.</p><p>I’d like to say I led them to success, but in reality my contribution was usually asking basic questions like “So what needs to be done?” and letting the team figure things out. The team are the ones who achieved this great result.</p><p>By taking this inclusive view of the environment they operated in, the team went slower in the week to week progressing of things, but they went further and faster at the large scale. And faster than any similar team that organisation (and probably that government) had ever seen to that point.</p><p>They built goodwill and trust by listening and delivering. They were able to cut through the complexity of organisational politics and competing priorities by slowing down and getting on the same page about mission, by helping neighbours along the way and by cutting out IT jargon and speaking plainly in the language of the organisation. And they were able to align people and address the power differentials by being consistent, backing up their words with actions, and most importantly, by taking the time to hear the needs of the people around them.</p><p>What does a government IT project from 15 years ago have to do with modern Software Product Management? The core principles are self-evident.</p><p>A good leader, in whatever context and whatever role, has to also be a good organisational citizen. You can&#39;t go out ahead and alone with your small cross-functional team without considering the cost of local optimisation.</p><p>Sure, there are exceptions to this, but for 90+% of product managers, you’re managing a fairly mature product in a known market, and you are one of many product managers in your organisation.</p><p>You need to be acting as a whole.</p><p>In the following posts in this series, I’ll drill into some ideas and tools on how you can do this.</p><p>Notes</p><p>(1) Government IT projects just don’t do that. <em>(Well, </em><a href="https://us.macmillan.com/books/9781250266774/recodingamerica"><em>they sometimes do</em></a><em>.)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1bfbc9681a2a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/everestengineering/product-management-at-scale-part-2-1bfbc9681a2a">Product Management at Scale, Part 2</a> was originally published in <a href="https://medium.com/everestengineering">EverestEngineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Management at Scale, Part 1]]></title>
            <link>https://medium.com/everestengineering/product-management-at-scale-part-1-ef1eeea299a3?source=rss-63bd0f44b19b------2</link>
            <guid isPermaLink="false">https://medium.com/p/ef1eeea299a3</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Craig Brown]]></dc:creator>
            <pubDate>Wed, 09 Aug 2023 00:47:49 GMT</pubDate>
            <atom:updated>2023-08-16T02:37:08.617Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This blog post is a replay of a talk I have given at a couple of product management conferences and meetups. Today is part 1 and I’ll update weekly.</em></p><p>The premise of this talk is that the practices, frameworks and methods discussed among and employed by product managers are insufficient at any significant scale.</p><p>In the presentation, I sneak in a bunch of ‘red herring’ slides to lull the audience into a suspicion they are going to hear what they have heard dozens of times before.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*bqtmRwOjWA4zsmJL1aAD0w.png" /></figure><ul><li>The double diamond is insufficient, as it leans to much into design up front, and not enough into start together-finish together.</li><li>North starts set our vision, but the road to success can be erratic and messy, full of dead ends and false paths. Embracing and navigating uncertainty is part of the job.</li><li>No plan survives contact with the enemy, no product strategy survives contact with the market, and no product design survives contact with the users. We need to be adaptable and work fluidly as a team when exploring new opportunities. We need to dance.</li><li>Iterate, iterate, iterate. Iteration isn’t incrementing. Aim for value fast. Solve problems fast. Pay to learn. But also deliver value frequently and continuously.</li><li>Teams need to be cross-functional; Voice of user, voice of tech and voice of business all need to engage in discourse and be solving things as a team. Leaders in each of these disciplines or crafts need to be stewarding the whole, not just their parts.</li><li>Use experiments to de-risk your success. Make uncertainty visible. Be as rigorous on testing hypotheses as anything else you do. Perhaps even more so than anything else.</li><li>Agile means adapting. But to adapt well, you’ll need a good plan that helps you evaluate options and trade-offs and manage alignment. Rigorous, continuous planning is necessary.</li><li>Focus on outcomes, not features. What job is your product doing for its users? How do they measure success? Align your success metrics with user goals.</li></ul><p>But, you know all that. The internet is full of this advice. This is the topics of the meetups, and books and podcasts.</p><p>The talk then switches to the theme: What extra things do you need to do when you are a large multi-program or multi product company, to the degree that simple group chat doesn’t work anymore? The above techniques, while necessary, are insufficient.</p><p>At large scale you need to do more than focus on your local optima. You’ll need to be a good corporate citizen. To do that, I present six concepts to think about and address;</p><ul><li>Complexity</li><li>Uncertainty</li><li>Responsibility</li><li>Trust</li><li>Shared language</li><li>Power</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*GIgCQJmPYt3r7b2_5_SFZg.png" /></figure><p><a href="https://medium.com/everestengineering/product-management-at-scale-part-2-1bfbc9681a2a">&gt;&gt; Part 2</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef1eeea299a3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/everestengineering/product-management-at-scale-part-1-ef1eeea299a3">Product Management at Scale, Part 1</a> was originally published in <a href="https://medium.com/everestengineering">EverestEngineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A story about complexity and a man named Martin]]></title>
            <link>https://craig-at-everest.medium.com/a-story-about-complexity-and-a-man-named-martin-de78bf137779?source=rss-63bd0f44b19b------2</link>
            <guid isPermaLink="false">https://medium.com/p/de78bf137779</guid>
            <category><![CDATA[complexity]]></category>
            <dc:creator><![CDATA[Craig Brown]]></dc:creator>
            <pubDate>Tue, 04 Jul 2023 10:06:04 GMT</pubDate>
            <atom:updated>2023-07-04T10:06:04.900Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A-XnVm5XRFidF_NTb-ejaA.png" /></figure><p>Once upon a time in a quaint village nestled in the Welsh countryside, there lived a cranky but highly intelligent man named Martin. He was known far and wide for his eccentricity and his love for preaching about the beauty and importance of complexity.</p><p>Martin was an aging gentleman with a wild shock of white hair, thick glasses perched on his nose, and a perpetually furrowed brow. He spent most of his days in his cozy cottage, surrounded by dusty books and stacks of papers filled with his musings on the subject of complexity.</p><p>Every morning, Martin would march into the village square, his voice booming as he shared his ideas with anyone who cared to listen. The villagers found him rather odd and often rolled their eyes at his long-winded speeches, but they couldn’t deny that Martin had a unique perspective on life.</p><p>Martin believed that complexity was the essence of existence. He argued that the world was a tapestry of intricate connections, where every action had a ripple effect that resonated throughout the universe. He spoke of the delicate balance that held nature together and the interdependence of all living beings. To him, simplicity was a disservice to the richness and depth of life.</p><p>Despite his grumpy demeanor, Martin’s passion was infectious. Some villagers found themselves captivated by his theories, secretly drawn to the allure of embracing complexity in their own lives. They began attending his daily lectures, engaging in lively debates, and eagerly seeking his wisdom.</p><p>Over time, Martin’s teachings started to influence the village. The once homogeneous community began to embrace diversity and different perspectives. People started noticing the intricate connections between their actions and the world around them. They became more compassionate and empathetic, understanding the profound impact they had on each other and the environment.</p><p>But not everyone was pleased with Martin’s influence. The village council, a group of conservative individuals, grew increasingly wary of his ideas. They saw him as a disruptive force, unsettling the established order of things. They decided to put an end to Martin’s preaching once and for all.<br>One fateful evening, as Martin was delivering a particularly passionate sermon in the village square, the council confronted him. They accused him of sowing discontent and disturbing the peace. Martin, undeterred, stood his ground, defending his belief in complexity and its transformative power.</p><p>The confrontation escalated, and the council threatened to exile Martin from the village. But before they could carry out their plan, the villagers who had been touched by Martin’s teachings intervened. They pleaded with the council to reconsider, citing the positive changes they had witnessed within themselves and the community.</p><p>Moved by the villagers’ testimonies and the unity they displayed, the council relented. They agreed to allow Martin to continue preaching, but with one condition: he had to find a way to express his ideas more succinctly, without overwhelming others with the sheer complexity of his language.</p><p>Martin, though initially resistant to this compromise, eventually realized that simplicity in communication could be just as powerful as complexity. He began to distill his theories into accessible stories, metaphors, and practical advice that resonated with people from all walks of life. His words became a bridge between the intricate world of complexity and the everyday experiences of the villagers.</p><p>In time, Martin’s teachings spread beyond the borders of the village. People from far and wide traveled to listen to his insightful sermons. He became a renowned figure, celebrated for his ability to bring clarity to complex ideas.</p><p>And as the world embraced the profound interconnectedness of all things, Martin’s legacy endured, reminding everyone of the beauty and importance of embracing the complexity of life.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de78bf137779" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>