<?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 Chris Hodgson on Medium]]></title>
        <description><![CDATA[Stories by Chris Hodgson on Medium]]></description>
        <link>https://medium.com/@chris_68692?source=rss-dbd2303817b4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*AhHFNNj_74tKgQPT</url>
            <title>Stories by Chris Hodgson on Medium</title>
            <link>https://medium.com/@chris_68692?source=rss-dbd2303817b4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 00:11:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chris_68692/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[From Feature Factory to Future Ready: Outcome driven leadership in the age of AI]]></title>
            <link>https://medium.com/@chris_68692/from-feature-factory-to-future-ready-outcome-driven-leadership-in-the-age-of-ai-fec2c053ad9a?source=rss-dbd2303817b4------2</link>
            <guid isPermaLink="false">https://medium.com/p/fec2c053ad9a</guid>
            <dc:creator><![CDATA[Chris Hodgson]]></dc:creator>
            <pubDate>Mon, 09 Jun 2025 22:46:50 GMT</pubDate>
            <atom:updated>2025-06-10T16:34:04.076Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GwbWGImtKRxyKeV_tINLjw.jpeg" /><figcaption>Created by AI in Genspark</figcaption></figure><p>If you’re a business leader, then take 30 seconds now and reflect on the last few weeks. How exactly did you communicate to your team about the things that they needed to prioritize to move your business forward? Did you use phrases such as “I need you to write a report”, or “We need to launch this feature”? It may surprise you that by using statements like this you may be radically limiting the potential of your people, and restricting the growth of your business.</p><p>After five years advising tech founders, I’ve witnessed a pattern so consistent it’s practically a law of nature: companies that focus on <strong><em>output</em></strong> communication hit a growth ceiling. This isn’t just a minor operational issue — it’s a fundamental mindset problem that can transform promising organizations into what I bluntly call “Feature Factories.” And if there’s one thing I’ve learned, it’s that factories produce widgets, not breakthroughs.</p><p><strong>The Feature Factory Trap</strong></p><p>The slide into becoming a Feature Factory business happens almost imperceptibly. It starts innocently enough — leadership identifies ‘customer features’ that they want, and teams diligently deliver them. Roadmaps fill with outputs: new modules, redesigned interfaces, additional capabilities. On paper, everything looks productive.</p><p>But here’s the hard truth I’ve observed repeatedly: focusing on <strong><em>output</em></strong> transforms teams into order-takers rather than problem-solvers. The emphasis shifts to the ‘production’ of features and delivery of tasks rather than the ‘impact’ those features have on customers’ lives, or the business itself.</p><p><strong>Key warning signs you’re running a feature factory:</strong></p><ul><li>Your product roadmap reads like a wish list from sales or executives</li><li>Success is measured by features shipped, not problems solved</li><li>Managers spend more time managing projects and backlogs than understanding customers</li><li>Your organization is siloed with each team producing their own output independent of its impact on other teams</li><li>Employees celebrate <em>quantity</em> more than <em>quality</em></li></ul><p>This approach is particularly dangerous for tech companies in that critical $10M-$150M growth phase. You’ve proven product-market fit, but sustained growth requires more than just adding features — it requires solving evolving customer problems in increasingly valuable ways.</p><p><strong>An alternative approach: Focus on Outcomes</strong></p><p>As an alternative, an <strong><em>outcome</em></strong> focused leader would communicate with phrases such as, “We need to improve customer retention by 10%”, or “We need business insights that marketing values”, or “We need to find a way to reduce customer acquisition costs”. Rather than dictating the solution, this leader has identified the outcomes that they would like and is empowering their employees to choose the best solution to achieve them.</p><p>Switching from <strong><em>output</em></strong> to <strong><em>outcomes</em></strong> seems minor, but it has radical implications.</p><p>In a world of increasingly powerful generative AI tools, the individual worker who is simply producing output will be replaced, and your company will become undifferentiated because it lacks critical thinking. The worker who is using critical thinking to solve problems is very well placed to be able to leverage the AI tools to test, iterate, learn and solve those problems faster.</p><p><strong>Lessons from Google: Where I First Saw Outcomes in Action</strong></p><p>My perspective on this wasn’t formed in a vacuum. Google was one of the first companies to fully embrace a business operating system called Objectives and Key Results (OKRs). Working there, I experienced firsthand how outcome-focused thinking can transform organizational effectiveness. Google’s implementation of OKRs wasn’t just a management technique — it was a mindset that permeated every level of the company.</p><p>What made Google’s approach powerful wasn’t the OKR framework itself (though it was well-designed), but how it oriented teams toward outcomes rather than outputs. Teams weren’t celebrated for shipping features; they were recognized for moving metrics that mattered to users and the business.</p><blockquote>“It doesn’t make sense to hire smart people and then tell them what to do; we hire smart people so they can tell us what to do.” Steve Jobs</blockquote><p><strong>Beyond OKRs: The Problem-Solving Approach</strong></p><p>While I’ve implemented OKRs with dozens of companies, I’ve come to realize that the framework alone isn’t enough. Jeff Gothelf and Josh Seiden’s book “<em>Who Does What By How Much?</em>” was a revelation that articulated something I’d observed but couldn’t quite name: OKRs only work when paired with a genuine problem-solving approach.</p><p>Without this problem-solving mindset, OKRs can devolve into another output-tracking mechanism — just with fancier language. I’ve seen teams create objectives around features (“Launch mobile check deposit”) rather than outcomes (“Increase the percentage of deposits made without visiting a branch”).</p><p>The difference is crucial. One focuses teams on delivery; the other focuses them on impact.</p><p><strong>The Cultural Requirements for Outcome Focus</strong></p><p>Here’s what many founders miss: shifting to outcomes isn’t just about changing your metrics — it requires fostering specific cultural behaviours that many organizations find uncomfortable:</p><p><strong>An outcome-focused culture demands;</strong></p><ul><li><strong>Deep customer empathy:</strong> Understanding problems from the user’s perspective, not the company’s.</li><li><strong>A problem solving approach:</strong> Individuals must be comfortable with ambiguity and working through solutions to problems.</li><li><strong>An experimentation mindset:</strong> Testing hypotheses rather than executing predetermined solutions.</li><li><strong>Comfort with “failing” quickly:</strong> The organization must recognize that many early approaches won’t work and that failure is inherent in the system and a pivot will be required.</li><li><strong>A willingness to learn:</strong> Teams must constantly gather insights about what’s working and what isn’t.</li></ul><p>This culture doesn’t happen by accident. It requires leaders who model curiosity, embrace uncertainty, and reward learning — even when that learning comes from ideas that didn’t work as expected.</p><p><strong>Making the Shift: Practical Steps</strong></p><p>For founders and product leaders looking to break free from the feature factory trap, here are the steps I typically recommend:</p><ol><li><strong>Start with customer problems, not solutions</strong></li></ol><ul><li>Before discussing features, articulate the specific customer problems you’re trying to solve.</li><li>Document how solving these problems creates value for both customers and the business.</li><li>Even if a team doesn’t work with external customers, they will at least have internal customers.</li></ul><p><strong>2. Reframe your roadmap around outcomes</strong></p><ul><li>Instead of listing features to build, define the outcomes you want to achieve.</li><li>Allow teams flexibility in how they achieve these outcomes.</li></ul><p><strong>3. Change how you measure success</strong></p><ul><li>Create clear metrics that indicate whether you’re solving the intended problems.</li><li>Celebrate learning and pivots as much as successful launches.</li></ul><p><strong>4. Model the right behaviours</strong></p><ul><li>As a leader, ask “what problem are we solving?” before “what are we building?”</li><li>Demonstrate comfort with uncertainty and experimentation.</li><li>Don’t penalize failure. Focus on the lessons learned and celebrate that you’ve learned them faster than your competitors.</li></ul><p>The companies I’ve seen make this shift successfully don’t just change their metrics — they change their mindset. They transform their entire organization from an assembly line into a discovery process.</p><p><strong>The Hard Truth About This Transition</strong></p><p>I won’t sugarcoat it — shifting to outcome-based thinking is hard, and I’ve seen many founders resist it, despite intellectually agreeing with the concept. The reason is uncomfortable but simple: outcome-based approaches demand accountability that output-based approaches don’t.</p><p>When you promise to ship ten features, you can declare victory when ten features ship, regardless of their impact. When you promise to increase user retention by 15%, there’s nowhere to hide if you don’t deliver.</p><p>This accountability is precisely what makes outcome-focused approaches more effective — but also more challenging to adopt. It requires vulnerability from leadership and a willingness to be measured by results, not activity.</p><p><strong>The Choice Before You</strong></p><p>If you’re leading a company in that critical $10M-$150M range, you face a choice that will significantly impact your growth trajectory:</p><p>You can run a <strong><em>feature factory</em></strong> — efficiently producing outputs that may or may not move the needle.</p><p>Or you can build an <strong><em>outcome engine</em></strong> — with smart, creative workers relentlessly focused on solving customer problems and delivering measurable impact.</p><p>One path leads to busy teams and impressive-looking roadmaps. The other leads to meaningful innovation and sustainable growth.</p><p>The companies that break through to $150M and beyond aren’t those with the most features — they’re the ones most effective at delivering outcomes that matter. They’re the ones who’ve learned that in business, as in life, it’s not about how much you do, but about the difference you make.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fec2c053ad9a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[15 lessons from three decades in Tech]]></title>
            <link>https://medium.com/@chris_68692/15-lessons-from-three-decades-in-tech-22d2ff0e32f0?source=rss-dbd2303817b4------2</link>
            <guid isPermaLink="false">https://medium.com/p/22d2ff0e32f0</guid>
            <category><![CDATA[advisor]]></category>
            <category><![CDATA[tech-career-advice]]></category>
            <category><![CDATA[career-progression]]></category>
            <category><![CDATA[tech-investing]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Chris Hodgson]]></dc:creator>
            <pubDate>Tue, 26 Nov 2024 14:56:03 GMT</pubDate>
            <atom:updated>2024-11-26T15:25:35.704Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="An old computer workstation with antique computer" src="https://cdn-images-1.medium.com/max/1024/0*fafpyjTAW0oL4mD8" /><figcaption>Photo by <a href="https://unsplash.com/@wizzyfx?utm_source=medium&amp;utm_medium=referral">Ugi K.</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I started my career in April 1993, the exact same month that the World Wide Web was made available to the public. 30 years later, I’ve recently started what might (likely) be the final stage in my career. This has caused me to reflect on the lessons from working for over 30 years in the tech industry, across 5 countries.</p><p>Most people look back on the evolution of their career as a gradual evolution — each change in job feeling similar to a software update. When I reflect on my career, the changes have felt more jarring — each one feeling a bit more like a completely new software release. It certainly hasn’t been easy to follow this route, but I’ve done it consciously by focusing on transferrable skills, and it’s been really rewarding.</p><h3>Release v1.0 — Engineer (1993–1997)</h3><p>I spent the first 5 years of my career becoming a Professional Engineer by working in the central engineering office of a global company. It was a great training ground, and I was given disproportionate responsibility for my level of experience. I oversaw large capital projects delivered by third-party engineering contractors and I learned about the inner workings of a large corporation. The responsibility was addictive, and it held me at the company for longer than I should have stayed.</p><p>● <strong>Lesson 1:</strong> <strong>Solving problems is a foundational career skill</strong>. Without it, your career will be limited to only doing what others ask you to do.</p><p>● <strong>Lesson 2:</strong> <strong>Focus on learning in your first serious job</strong>. When you know nothing about work, you can learn very quickly from others by starting your career in a small team of senior experts.</p><p>● <strong>Lesson 3:</strong> <strong>Don’t be afraid to move to your next role before you feel ready</strong>, but recognize that it takes 3 years to really add value.</p><h3>Release v2.0 — Consultant (1998–2007)</h3><p>Like most engineers, I chose to transition into business after completing an MBA. However, unlike most Canadians, I decided to study in France. This allowed me to immerse myself in many different cultures, and that changed my life. Afterward, I ended up living in the UK and working across Europe as a Strategy Consultant to the Telco industry. It was during the Dotcom boom, and I dove straight into the startup space — writing business plans and setting up a global incubator. This is where I was first introduced to the ability to build companies that could disrupt traditional industries.</p><p>● <strong>Lesson 4:</strong> <strong>Ideas are worthless, without the ability to execute</strong>.</p><p>● <strong>Lesson 5:</strong> <strong>Not all decisions in life should be made with your head</strong>. Sometimes it’s more important to listen to your heart, or your gut.</p><p>● <strong>Lesson 6:</strong> <strong>Have a close friend that helps you to dream big</strong>, but also does not let any success go to your head.</p><h3>Release v3.0 — Entrepreneur (2005–2011)</h3><p>I raised VC funding for my own business in 2007 after spending two years trying to get my idea off the ground. I had two newborn kids, and it was one of the hardest times of my life. We built a B2C loyalty program for parents and by working with partners and retailers, we acquired over 1m customers in the first 4 years. The business has now expanded to include a digital wealth management platform, and I’m proud of the positive financial impact it’s had for millions of UK families.</p><p>● <strong>Lesson 7:</strong> <strong>Learn how to be good at selling</strong>. Almost every job is really a sales job.</p><p>● <strong>Lesson 8:</strong> <strong>The support of a spouse can give you a superpower to accomplish almost anything</strong>.</p><p>● <strong>Lesson 9:</strong> <strong>Raising capital can feel like the end of a journey, but the real work hasn’t even started</strong>.</p><h3>Release v4.0 — Executive (2011–2018)</h3><p>It took me a while to come to grips with the idea of leaving my own business to work for someone else. However, it was my only viable option once we decided to move our young family across continents and back to Canada. I was fortunate to end up at a very entrepreneurial company, Google. This gave me a front row seat into the digitization of businesses and how to support large enterprises through that journey. I also had the chance to build consultative sales teams made up of fantastic people, selling complex solutions.</p><p>● <strong>Lesson 10: Learn how to thrive from change and chaos</strong>. The world isn’t going to slow down.</p><p>● <strong>Lesson 11:</strong> <strong>Never underestimate the power of culture to drive business success</strong>.</p><p>● <strong>Lesson 12:</strong> <strong>Be an honest version of yourself at work</strong> and find a place where your voice can be heard.</p><h3>Release v5.0 — Advisor (2019–2024)</h3><p>The entrepreneurial itch kept getting stronger, but rather than start something from scratch again, I made a commitment to work as an Advisor to Founders of high growth tech companies. As an independent advisor, it took longer than I would have liked to build my reputation in the space. At the same time, the impact I had on these companies was addictive. I advised companies on how to scale — for instance, building sales teams, driving marketing, and improving leadership effectiveness. In parallel, even at this later stage of my career, I continued to learn about myself and discovered that I have a natural ability to distill lots of conflicting and complex themes into a concise strategy and plan.</p><p>● <strong>Lesson 13:</strong> <strong>Reputation matters</strong>. It’s an asset that grows over time and can pay dividends later in life.</p><p>● <strong>Lesson 14:</strong> <strong>Find a way to have a positive impact on others</strong> - nothing is more rewarding.</p><p>● <strong>Lesson 15:</strong> <strong>Life is more interesting if you keep an open mindset to constantly learn!</strong></p><h3>Release v6.0 — Investor (2024–2035)</h3><p>I’m two months into my latest, and maybe <em>last</em>, role — a Partner at <a href="http://www.maverixpe.com/"><strong>Maverix</strong></a>, a Growth Equity firm passionate about investing in later-stage, disruptive technology companies.</p><p>I will be dedicating my time to finding, investing and supporting the Founders of high-growth, tech businesses. In my role, I am very lucky to be working directly with the Founders, following our investment, to help them tackle any challenges that are slowing them down. I’m really excited to be working with the rest of the <a href="http://www.maverixpe.com/"><strong>Maverix</strong></a> team and all of our portfolio companies.</p><p>In the coming months, and years, I’ll be providing more of my thoughts and experiences in scaling high-growth disruptive companies. Please reach out if you’d like to explore how we could work together.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22d2ff0e32f0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Turning Conference Trips into Business Wins]]></title>
            <link>https://medium.com/@chris_68692/turning-conference-trips-into-business-wins-22b3c9d7cc94?source=rss-dbd2303817b4------2</link>
            <guid isPermaLink="false">https://medium.com/p/22b3c9d7cc94</guid>
            <category><![CDATA[trade-show]]></category>
            <category><![CDATA[marketing-strategy-tips]]></category>
            <category><![CDATA[conference-planning]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[conference-tips]]></category>
            <dc:creator><![CDATA[Chris Hodgson]]></dc:creator>
            <pubDate>Mon, 25 Nov 2024 18:38:27 GMT</pubDate>
            <atom:updated>2024-11-25T18:38:27.796Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lTI6WFeYo1khDOse" /></figure><h3><strong>A Simple Guide to Maximizing Impact for high growth tech companies</strong></h3><p>Conferences and Tradeshows can be powerful tools for high growth tech companies to build awareness and drive leads. However, as CEOs, you need to ensure they’re driving real value from your limited resources and budgets.</p><p>I work extensively with the CEOs of tech companies, as they look to find the right tactics to accelerate their growth. I often get asked about how to develop a strategy to manage investment into the seemingly endless number of conferences that they could attend. Here are my tips for getting the most out of your investment and sales team’s participation.</p><h3>Defining Objectives: Beyond the free trip</h3><p>Let’s face it, some salespeople view conferences as company-funded vacations. It’s important to remind them that conferences serve three main objectives:</p><ol><li><strong>Building Awareness</strong></li><li><strong>Generating New Leads</strong></li><li><strong>Nurturing Existing Relationships</strong></li></ol><p>It’s true that any single conference can achieve all three of these objectives — but that’s what causes many of the issues. Most tech companies I’ve worked with spend anywhere from $10k to $500k a year on conferences and try to achieve all three objectives, every time. At this level, I always recommend that you be clear on the <strong><em>primary</em></strong> objective for every conference. I would also propose that the third objective — “nurturing existing relationships” — should never be the primary objective of any conference. These are relationships that you already have. You can usually meet the contacts in a more cost effective way. Sure, there are efficiencies from meeting many at once, but real ROI is going to be driven from the first two objectives — Building Awareness, or Generating New Leads.</p><h3><strong><em>Delivering Value: A structured approach to conference attendance</em></strong></h3><p>Most high growth tech companies have an ad hoc approach to conferences. Salespeople request ones that they want to attend — sometimes it seems like an endless list — and they are good at justifying attendance at each one. CEOs often have very little data to make an informed decision and as a result, they often default to ‘yes’, and usually have trouble measuring the performance later.</p><p>We need to shift the focus to a more structured approach:</p><h3>Plan for Building Awareness at the start of the year</h3><p>At the start of the year, identify industry conferences that align with your brand-building goals. These are normally a subset of the industry’s ‘must attend’ events. Allocate budget (in advance) for these events and plan for a significant presence.</p><p>Building awareness involves more than sponsorship, and a well staffed booth. Real awareness only comes from having speaking roles — giving the company a chance to showcase its products and services. If you aren’t speaking at a conference, then you aren’t building awareness. Simple.</p><p>Once you’ve identified (and budgeted for) the conferences you’ll use to build your brand, then the primary objective of every other conference — planned or unplanned — is to generate new leads.</p><h3>Set a “New Meeting Hurdle” in advance, for all other Conferences</h3><p>When salespeople ask to attend an event, push the question right back and ask them how many meetings they have already secured with new leads. I recommend setting a ‘new meeting hurdle’ for all “Lead-Generating” conferences. Depending on your industry, sales cycle and margins, this may be 3–5 new leads, and by leads, I mean new <strong><em>companies</em></strong> and NOT new people at one company. Once the new meeting hurdle has been met, then, and only then, should you give approval to go ahead and book tickets and travel to attend. By reversing the normal order of things and booking the meetings ahead of making the decision to attend, you are in a much stronger position to deliver real ROI.</p><p>Small local conferences may be the one exception to this rule — if there is limited travel, and costs are low, then it may be worth attending for opportunistic purposes, or to grow the industry knowledge and development of your salesperson. However, try to limit individual time spent at these because there is normally more value in other sales tactics.</p><h3><strong>In Summary</strong></h3><p>By aligning conference attendance with clear objectives and setting expectations, we can transform conferences from “fun trips” into strategic investments that grow sales and build awareness. Let’s leverage these events to generate valuable leads and fuel your hyper-growth journey!</p><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/turning-conference-trips-business-wins-chris-hodgson-axepc/?trackingId=vnDdfghpSYaRFUf23L%2BCoQ%3D%3D"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22b3c9d7cc94" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is it time to re-think your weekly leadership meeting?]]></title>
            <link>https://medium.com/@chris_68692/is-it-time-to-re-think-your-weekly-leadership-meeting-5c125d7567f0?source=rss-dbd2303817b4------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c125d7567f0</guid>
            <category><![CDATA[leadership-meeting]]></category>
            <category><![CDATA[tech-leadership]]></category>
            <category><![CDATA[business-leadership]]></category>
            <category><![CDATA[meetings]]></category>
            <dc:creator><![CDATA[Chris Hodgson]]></dc:creator>
            <pubDate>Mon, 25 Nov 2024 18:28:42 GMT</pubDate>
            <atom:updated>2024-11-25T18:43:11.693Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*weYzfUamH4yV2Gw8" /></figure><p>In the fast-paced world of high-growth tech, the weekly leadership meeting is a cornerstone of success. While many founders recognize its importance, few truly optimize this critical gathering. These meetings have often not changed much since the early days of the company, and are frequently too casual, resulting in inefficiencies, lack of leadership alignment and ineffective decision making. I’ve seen how it’s possible to unlock unparalleled value for your organization by implementing a little bit of professionalism into your meeting.</p><h3>Meeting Objectives</h3><p>Weekly leadership meetings are critical touchpoints with multiple objectives;</p><ol><li><strong>Leadership Alignment and Prioritization</strong>: Ensure everyone is focused on what matters most for the week ahead.</li><li><strong>Operational Efficiency</strong>: Identify and remove friction in daily operations.</li><li><strong>Informed Decision Making</strong>: Provide input into crucial operational decisions.</li><li><strong>Strategic Direction</strong>: Debate and agree on the company’s direction over the next 1–2 years.</li><li><strong>Team Cohesion</strong>: Build rapport and trust among team members</li></ol><h3>Rules and Expectations</h3><p>To make these meetings successful, I encourage you to establish clear rules and cultural expectations:</p><ul><li><strong>Agenda in Advance</strong>: Share it beforehand to give everyone time to prepare.</li><li><strong>Pre-Reading</strong>: Ensure any necessary materials are reviewed before the meeting.</li><li><strong>Time-Limited Discussions</strong>: Keep each agenda section concise.</li><li><strong>Leadership Dashboard</strong>: Provide a set of key metrics aligned with company priorities.</li><li><strong>Documenting Actions</strong>: Appoint a rotating scribe to document actions and decisions in a live, accessible document.</li><li><strong>Psychological Safety</strong>: Create an environment that encourages respectful challenges and open debate.</li></ul><h3>Potential Meeting Agenda</h3><p>The structure of your leadership meeting sets the tone for the week. Here’s a suggested agenda:</p><ol><li><strong>Personal Updates</strong> (5 min) : Share personal milestones briefly to build rapport. Limit to those who have updates. Not everyone needs to speak in every meeting, just ensure that everyone gets a chance to speak, over time.</li><li><strong>Outstanding Actions </strong>(5 min) : Review actions from previous meetings to ensure accountability.</li><li><strong>Weekly Priority Round Table</strong> (15 min) : Each leader shares their focus and deliverables for the week. Keep updates brief to ensure visibility and address misalignment.</li><li><strong>Leadership Dashboard Review</strong> (5 min) : Analyze KPI metrics to spot issues and track progress. Focus on gaps and solutions.</li><li><strong>Operating Topics</strong> (30 min) : The core of the meeting. Discuss 1–3 topics chosen by the CEO that require decisions. Ensure pre-reading is done so that the meeting can focus on discussion and making the decisions.</li></ol><h3>Monthly Strategy Discussion</h3><p>Beyond weekly operations, strategic alignment is crucial. I strongly recommend dedicating one meeting a month to one strategic topic that is chosen by the CEO, after input from everyone. Go deep on this topic and really ensure that the leadership team is aligned on where the company is going.</p><h3>Conclusion</h3><p>By implementing a bit more professional rigour, you can transform your weekly leadership meeting into a catalyst for innovation, growth, and organizational success. Remember, a well-executed leadership meeting is not just any meeting; it’s a strategic investment in your company’s future.</p><p>I’d love to hear about your own experiences and suggestions in the comments below.</p><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/time-re-think-your-weekly-leadership-meeting-chris-hodgson-i3m7c/?trackingId=vnDdfghpSYaRFUf23L%2BCoQ%3D%3D"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c125d7567f0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>