BONUS: Flawless Execution — Translating Fighter Pilot Precision to Business Results | Christian "Boo" Boucousis

BONUS: Flawless Execution — Translating Fighter Pilot Precision to Business Results | Christian "Boo" Boucousis

BONUS: Flawless Execution — Translating Fighter Pilot Precision to Business Results

In this powerful conversation, former fighter pilot Christian "Boo" Boucousis reveals how military precision translates into agile business leadership. We explore the FLEX model (Plan-Brief-Execute-Debrief), the critical difference between control-based and awareness-based leadership, and why most organizations fail to truly embrace iterative thinking.

From Cockpit to Boardroom: An Unexpected Journey

"I learned over time that it doesn't matter what you do if you're always curious, and you're always intentional, and you're always asking questions." — Christian "Boo" Boucousis

Christian's path from fighter pilot to leadership consultant wasn't planned—it was driven by necessity and curiosity. After 11 years as a fighter pilot (7 in Australia, 4 in the UK), an autoimmune condition ended his flying career at age 30. Rather than accepting a comfy job flying politicians around, he chose entrepreneurship. He moved to Afghanistan with a friend and built a reconstruction company that grew to a quarter billion dollars in four years. The secret? The debrief skills he learned as a fighter pilot. By constantly asking "What are you trying to achieve? How's it going? Why is there a gap?" he approached business with an agile mindset before he even knew what agile was. This curiosity-driven, question-focused approach became the foundation for everything that followed.

The FLEX Model: Plan-Brief-Execute-Debrief

"Agile and scrum were co-created by John Sutherland, who was a fighter pilot, and its origins sit in the OODA loop and iteration. Which is why it's a circle." — Christian "Boo" Boucousis

The FLEX model isn't new—fighter pilots have used this Plan-Brief-Execute-Debrief cycle for 60 years. It's the ultimate simple agile model, designed to help teams accelerate toward goals using the same accelerated learning curve the Air Force uses to train fighter pilots. The key insight: everything in this model is iterative, not linear. Every mission has a start, middle, and end, and every stage involves constant adaptation. Afterburner (the company Christian now leads as CEO) has worked with nearly 3,800 companies and 2.8 million people over 30 years, teaching this model. What's fascinating is that the DNA of agile is baked into fighter pilot thinking—John Sutherland, co-creator of Scrum, wrote the foreword for Christian's book "The Afterburner Advantage" because they share the same roots in the OODA loop and iterative thinking.

Why Iterative Thinking Doesn't Come Naturally

"Iterative thinking is not a natural human model. Most of the time we learn from mistakes. We don't learn as a habit." — Christian "Boo" Boucousis

Here's the hard truth: agile as a way of working is very different from the way human beings naturally think. Business leadership models still hark back to Frederick Winslow Taylor's 1911 book on scientific management—industrial era leadership designed for building buildings, not creating software. Time is always linear (foundation, then structure, then finishing), and this shapes how we think about planning. Humans also tend to organize like villages with chiefs, warriors, and gatherers—hierarchical and political. Fighter pilots created a parallel system where politics exist outside missions, but during execution, personality clashes can't interfere. The challenge for business isn't the method—it's getting human minds to embrace iteration as a habit, not just a process they follow when forced.

Planning: Building Collective Consciousness, Not Task Lists

"Planning isn't all about sequencing actions—that's not planning. That's the byproduct of planning, which is collectively agreeing what good looks like at the end." — Christian "Boo" Boucousis

Most people plan in their head or in front of a spreadsheet by themselves. That's not planning—that's collecting thoughts. Real planning means bringing everyone on the team together to build collective consciousness about what's possible. The plan is always "the best idea based on what we know now." Once airborne, everything changes because the enemy doesn't cooperate with your plan. Planning is about the destination, not the work to get there. Think about airline pilots: they don't tell you about traffic delays on their commute or maintenance issues. They say "Welcome aboard, our destination is Amsterdam, there's weather on the way, we'll land 5 minutes early." That's a brief—just the effect on you based on all their work. Most business meetings waste 55 minutes on backstory and 5 minutes deciding to have another meeting. Fighter pilots focus entirely on: What are we trying to achieve? What might get in the way? Let's go.

Briefing: The 25-Minute Focus Window

"You need 25 minutes of focus before your brain really focuses on the task. You program your brain for the mission at hand." — Christian "Boo" Boucousis

The brief is the moment between planning and execution when the plan is as accurate as it'll ever get. It's called "brief" for a reason—it's really short. The team checks that everyone understands the plan in today's context, accounting for last-minute changes (broken equipment, weather, personnel changes). Then comes the critical part: creating the mission bubble. From the brief until mission end, there are no distractions, no notifications. If someone tries to interrupt a fighter pilot walking to the jet, the response is clear: "I'm in my mission bubble. No distractions." This isn't optional—research shows it takes 25 minutes of uninterrupted focus before your brain truly locks onto a task. Yet most business leaders expect constant availability, with notifications pinging every few minutes. If you need everyone to have notifications on to run your business, you're doing a really bad job at planning.

Execution: Awareness-Based Leadership vs. Control-Based Leadership

"The reason we have so many meetings is because the leader is trying to control the situation and own all the awareness. It's not humanly possible to do that." — Christian "Boo" Boucousis

During execution, fighter pilots fly the plan until it doesn't work anymore—then they adapt. A mission commander might lead 70 airplanes, but can't possibly track all 69 others. Instead, they create "gates"—checkpoints where everyone confirms they're in the right place within 10 seconds. They plan for chaos, creating awareness points where the team is generally on track or not. The key shift: from control-based leadership (the leader tries to control everything) to awareness-based leadership (the leader facilitates and listens for divergences). This includes "subordinated leadership"—any of the four pilots in a formation can take the lead if they have better awareness. If a wingman calls out a threat the leader doesn't see, the immediate response is "Press! You take the lead." This works because they planned for it and have criteria. Business teams profess to want this kind of agile collaboration, but struggle because they haven't invested in the planning and shared understanding that makes fluid leadership transitions possible.

Abort Criteria: Knowing When to Stop

"We have this concept called abort criteria. If certain criteria are hit, we abort the mission. I think that's a massive opportunity for business." — Christian "Boo" Boucousis

There are degrees of things going wrong: a little bit, a medium amount, and everything going wrong. When everything's going wrong, fighter pilots stop and turn around—they don't keep pressing a bad situation. This "abort criteria" concept is massively underutilized in business. Too often, teams press bad situations, transparency disappears, people stop talking, and everyone goes into survival mode (protect myself, blame others). This never happens with fighter pilots. If something goes wrong, they take accountability and make the best decision. The most potent team size is four people: a leader, deputy leader, and two wingmen. This small team size with clear roles and shared abort criteria creates psychological safety to call out problems and adapt quickly.

The Retrospective Mindset: Not Just a Ritual

"A retrospective isn't a ritual. It's actually a way of thinking. It's a cognitive model. If you approached everything as a retrospective—what are we trying to achieve? How's it going? Why is it not going where we want? What's the one action to get back on track?" — Christian "Boo" Boucousis

The debrief—the retrospective—is the most important part of fighter pilot culture translated into agile. It's not just a meeting you have at the end of a sprint. It's a mindset you apply to everything: projects, relationships, personal development. Christian introduces "Flawless Leadership" built on three M's: Method (agile practices), Mindset (growth mindset developed through acting iteratively), and Moments (understanding when to show up as a people leader vs. an impact leader). The biggest mistake in technology: teams do retrospectives internally but don't include the business. They get a brief from the business, build for two months, come back, and the business says "What is this? This isn't what I expected." If they'd had the business in every scrum, every iteration, trust would build naturally. Everyone involved in the mission must be part of the planning, briefing, executing, and debriefing.

Leading in the Moment: Three Layers of Leadership

"Your job as a scrum master, as a leader—it doesn't matter if you're leading a division of people—is to be aware. And you're only going to be aware by listening." — Christian "Boo" Boucousis

Christian breaks leadership into three layers: People Leadership (political, emotional, dealing with personalities and overwhelm), Impact Leadership (the agile layer, results-driven, scientific), and Leading Now (the reactive, amygdala-driven panic response when things go wrong). The mistake: mixing these layers. Don't try to be a people leader during execution—that's not the time. But if you're really good at impact leadership (planning, breaking epics into stories, getting work done), you become high trust and high credibility. People leadership becomes easier because success eliminates excuses. During execution, watch for individual traits and blind spots. Use one-on-ones with a retrospective mindset: "What does good look like for you? How do we get to where you're not frustrated?" When leaders aren't present—checking phones and watches during meetings—they lose people. Your job as a leader is to turn your ears on, facilitate (not direct), and listen for divergences others don't see.

The Technology-Business Disconnect

"Every time you're having a scrum, every time you're coming together to talk about the product, just have the business there with you. It's easy." — Christian "Boo" Boucousis

One of the biggest packages of work Afterburner does: technology teams ask them to help build trust with the business. The solution is shockingly simple—include the business in every scrum, every planning session, every retrospective. Agile is a tech-driven approach, creating a disconnect. Technology brings overwhelming information about how hard they're working and problems they've solved, but business doesn't care about the past. They care about the future: what are you delivering and when? During the Gulf War, the military scaled this fighter pilot model to large-scale planning. Fighter pilots work with marines, special forces, navy, CIA agents—everyone is part of the plan. If one person is missing from planning, execution falls apart. If someone on the ground doesn't know how an F-18 works, the jet is just expensive decoration. Planning is about learning what everyone else does and how to support them best—not announcing what you'll do and how you'll do it.

High-Definition Destinations: Beyond Goals

"Planning is all about the destination, not the work to get there. Think about when you hop on an airplane—the pilot doesn't tell you the whole backstory. They say 'Welcome aboard, our destination is Amsterdam, there's weather on the way, we'll land 5 minutes early.' All you want is the effect on you." — Christian "Boo" Boucousis

Christian uses the term "High-Definition Destinations" rather than goals. The difference is clarity and vividness. When you board a plane, you don't get the pilot's commute story or maintenance details—you get the destination, obstacles, and estimated arrival. That's communication focused on effect, not process. Most business communication does the opposite: overwhelming context, backstory, and detail, with the destination buried somewhere in the middle. The brief should always be: Here's where we're going. Here's what might get in the way. Let's go. This communication style—focused on outcomes and effects rather than processes and problems—transforms how teams align and execute. It eliminates the noise and centers everyone on what actually matters: the destination.

About Christian "Boo" Boucousis

Christian "Boo" Boucousis is a former fighter pilot who now helps leaders navigate today's fast-moving world. As CEO of Afterburner and author of The Afterburner Advantage, he shares practical, people-centered tools for turning chaos into clarity, building trust, and delivering results without burning out.

You can link with Christian "Boo" Boucousis on LinkedIn, visit Afterburner.com, check out his personal site at CallMeBoo.com, or interact with his AI tool at AIBoo.com.

Avsnitt(200)

The No-Scroll Bar Rule—Empowering PO's Through Constraints | Joel Bancroft-Connors

The No-Scroll Bar Rule—Empowering PO's Through Constraints | Joel Bancroft-Connors

Joel Bancroft-Connors: The No-Scroll Bar Rule—Empowering PO's Through Constraints Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. The Great Product Owner: The Collaborative Innovator Joel describes an exceptional Product Owner scenario at a large insurance organization where complementary skills created magic. Working with two different people - a business expert who understood insurance but lacked development knowledge, and a designer with user experience expertise - Joel suggested the designer take on the Product Owner role while collaborating closely with the business person. This collaboration between complementary skills produced outstanding results. The great Product Owner understood that their role wasn't to control every detail but to unleash developer creativity by providing problems and context rather than prescriptive solutions. Joel's approach of "give the developers a problem and a canvas" allowed the team to innovate while staying focused on customer needs. This Product Owner fostered innovation rather than preventing it, demonstrating how effective collaboration can transform product development. The Bad Product Owner: The Business Analyst That Couldn't Let Go Joel identifies a problematic anti-pattern: the Business Analyst who transitions to Product Owner but can't abandon their documentation-heavy approach. While Business Analysts can make excellent Product Owners with proper support, those who insist on documenting everything create communication bottlenecks and slow down delivery. This creates a "telephone game" effect between the BA/PO and developers. Joel encountered one such individual who would declare "the developers can't do that" without giving them the opportunity to explore solutions. Following his "no-scroll bar rule" for documentation, Joel emphasizes that Product Owners should provide just enough information to enable developer creativity, not overwhelming detail that stifles innovation. When the problematic BA was replaced with someone who understood customers and trusted developers, the team's innovation flourished. In this segment, we refer to the book Liftoff, by Larsen and Nies. Self-reflection Question: Are you enabling developer innovation by providing problems and context, or are you stifling creativity with excessive documentation and control? [Scrum Master Toolbox Podcast Recommends] 🚀 Global Agile Summit 2025 Join us in Tallinn, Estonia, from May 18th – 20th, 2025, for an event that will inspire, challenge, and equip you with real-world Agile success stories. 🌍 Connect with global Agile leaders. 💡 Learn practical strategies for impact. 🔥 Break free from Agile fatigue and become a Pragmatic Innovator Check Full Program [Scrum Master Toolbox Podcast Recommends] About Joel Bancroft-Connors Joel Bancroft-Connors is The Gorilla Coach — a Certified Scrum Trainer and Agile disruptor focused on sustainable value and effectiveness. With a background in product, project, and coaching, Joel blends sharp insights with practical tools to help teams thrive. He is a Miro power user and rocks curated classroom playlists. You can link with Joel Bancroft-Connors on LinkedIn.

6 Juni 19min

Sustainable Value—Redefining Success Beyond Profit | Joel Bancroft-Connors

Sustainable Value—Redefining Success Beyond Profit | Joel Bancroft-Connors

Joel Bancroft-Connors: Sustainable Value—Redefining Success Beyond Profit Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. Joel has evolved his definition of Scrum Master success over time, moving beyond traditional metrics to focus on what truly matters: sustainable value delivery. While Agile principles clearly state the goal of delivering value continuously, Joel emphasizes that success isn't just about making profit - it's about creating sustainable profit through sustainable processes and people practices. He challenges Scrum Masters to consider their "people sustainability metric" and asks whether their approach supports long-term team health and organizational resilience. Joel's definition encompasses three pillars: delivering sustainable value, maintaining sustainable processes, and ensuring sustainability for people. This holistic view of success requires Scrum Masters to think beyond immediate outcomes and consider the long-term impact of their practices. In this segment, we refer to the book Turn the ship around! by David Marquet. Self-reflection Question: What is your people sustainability metric, and how are you measuring whether your Scrum practices support long-term team and organizational health? Featured Retrospective Format for the Week: Back to Basics Joel advocates for returning to the foundational retrospective format outlined in "Agile Retrospectives" by Derby and Larsen. Rather than getting caught up in complex or creative retrospective techniques, he emphasizes the power of following the basic steps: set the stage, gather data, generate insights, decide what to do, and close the retrospective. Joel stresses that there's an important arc to retrospectives that shouldn't be overlooked. By taking time to properly gather data and following the structured approach from the agile retrospectives book, teams can achieve more meaningful and actionable outcomes. Sometimes the most effective approach is simply executing the fundamentals exceptionally well. In this segment, we refer to the book Agile retrospectives, by Derby and Larsen. [Scrum Master Toolbox Podcast Recommends] 🚀 Global Agile Summit 2025 Join us in Tallinn, Estonia, from May 18th – 20th, 2025, for an event that will inspire, challenge, and equip you with real-world Agile success stories. 🌍 Connect with global Agile leaders. 💡 Learn practical strategies for impact. 🔥 Break free from Agile fatigue and become a Pragmatic Innovator Check Full Program [Scrum Master Toolbox Podcast Recommends] About Joel Bancroft-Connors Joel Bancroft-Connors is The Gorilla Coach — a Certified Scrum Trainer and Agile disruptor focused on sustainable value and effectiveness. With a background in product, project, and coaching, Joel blends sharp insights with practical tools to help teams thrive. He is a Miro power user and rocks curated classroom playlists. You can link with Joel Bancroft-Connors on LinkedIn.

5 Juni 17min

The 90-Day Rule—Building Trust Before Disrupting the Status Quo | Joel Bancroft-Connors

The 90-Day Rule—Building Trust Before Disrupting the Status Quo | Joel Bancroft-Connors

Joel Bancroft-Connors: The 90-Day Rule—Building Trust Before Disrupting the Status Quo Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. Joel shares his first experience as a CSM at a traditional hard drive manufacturing company, where he learned the art of patient change management. Tasked with bridging the gap between a rigid mothership company and their agile startup division, Joel discovered the power of focusing on principles rather than processes. For six months, he concentrated on creating transparency and shifting focus from status reporting to "getting to done" without ever mentioning Scrum or Agile. His approach followed what he calls the 90-day rule: "In the first 90 days - do no harm, but then have a plan to do something." By listening first and building trust, Joel helped the team deliver a product in just three months. He emphasizes the importance of making people feel valued and using "future perfect thinking" to envision desired outcomes before introducing change. In this episode we refer to Luke Hohmann's Innovation Games, the website and resource Manager-Tools.com, and Daniel Pink's book Drive. Self-reflection Question: Are you rushing to implement changes, or are you taking time to build trust and understand the current state before introducing new practices? [Scrum Master Toolbox Podcast Recommends] 🚀 Global Agile Summit 2025 Join us in Tallinn, Estonia, from May 18th – 20th, 2025, for an event that will inspire, challenge, and equip you with real-world Agile success stories. 🌍 Connect with global Agile leaders. 💡 Learn practical strategies for impact. 🔥 Break free from Agile fatigue and become a Pragmatic Innovator Check Full Program [Scrum Master Toolbox Podcast Recommends] About Joel Bancroft-Connors Joel Bancroft-Connors is The Gorilla Coach — a Certified Scrum Trainer and Agile disruptor focused on sustainable value and effectiveness. With a background in product, project, and coaching, Joel blends sharp insights with practical tools to help teams thrive. He is a Miro power user and rocks curated classroom playlists. You can link with Joel Bancroft-Connors on LinkedIn.

4 Juni 14min

How Performance Reviews Killed a Great Agile Team | Joel Bancroft-Connors

How Performance Reviews Killed a Great Agile Team | Joel Bancroft-Connors

Joel Bancroft-Connors: How Performance Reviews Killed a Great Agile Team Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. Joel tells the story of a team caught in the crossfire of a poorly executed large-scale agile transformation. While the CTO championed going agile, they quickly checked out, leaving the organization without clear direction or understanding of why they were adopting agile practices. The company measured success through output metrics like "number of teams trained" rather than meaningful outcomes. Joel worked with an exceptional team that had built their own collaborative workspace and was performing well, but external forces kept pulling them out of flow. Performance reviews created internal conflict, leading team members to focus on individual success rather than collective achievement. The team ultimately fell into their own traps, with everyone "focusing on themselves and throwing others under the bus." Joel recommends balancing performance evaluations with 50% team-based and 50% individual metrics to prevent this destructive pattern. Self-reflection Question: Does your team truly understand why they are using Scrum, or are they just going through the motions of the framework? Featured Book of the Week: Start with Why by Simon Sinek Joel credits Simon Sinek's "Start with Why" as a transformational influence on his coaching approach. The book's central principle that "people don't buy what you do, they buy why you do it" fundamentally changed how Joel teaches Scrum. He realized he had been teaching Scrum incorrectly by focusing on the mechanics rather than the purpose. Now Joel listens to this book annually and has shifted his focus to helping teams and organizations understand why Scrum matters and why it's important. This shift from teaching the "what" to emphasizing the "why" has made his coaching significantly more effective and meaningful. Joel also mentions the book Coaching Agile Teams by Lyssa Adkins. [Scrum Master Toolbox Podcast Recommends] 🚀 Global Agile Summit 2025 Join us in Tallinn, Estonia, from May 18th – 20th, 2025, for an event that will inspire, challenge, and equip you with real-world Agile success stories. 🌍 Connect with global Agile leaders. 💡 Learn practical strategies for impact. 🔥 Break free from Agile fatigue and become a Pragmatic Innovator Check Full Program [Scrum Master Toolbox Podcast Recommends] About Joel Bancroft-Connors Joel Bancroft-Connors is The Gorilla Coach — a Certified Scrum Trainer and Agile disruptor focused on sustainable value and effectiveness. With a background in product, project, and coaching, Joel blends sharp insights with practical tools to help teams thrive. He is a Miro power user and rocks curated classroom playlists. You can link with Joel Bancroft-Connors on LinkedIn.

3 Juni 12min

When Great Scrum Masters Fail—The Hidden Cost of Poor Value Communication | Joel Bancroft-Connors

When Great Scrum Masters Fail—The Hidden Cost of Poor Value Communication | Joel Bancroft-Connors

Joel Bancroft-Connors: When Great Scrum Masters Fail—The Hidden Cost of Poor Value Communication Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. Joel shares a powerful lesson about the critical importance of communicating value beyond team performance. Despite achieving remarkable success with multiple teams as an agile coach, Joel and his colleagues ultimately failed because they couldn't effectively demonstrate their value to leadership. The teams were thriving, but when budget cuts came, the coaching support was eliminated first. Without ongoing support, these successful teams began to deteriorate. Joel emphasizes that as Scrum Masters and agile coaches, we must actively communicate our impact and connect team success to business outcomes. Simply assuming that good team performance speaks for itself is not enough - we need to interact more with stakeholders and clearly articulate the value we create. In this episode, we refer to the TV series Ted Lasso, and the books Start with Why by Simon Sinek, and Coaching Agile Teams by Lyssa Adkins. Self-reflection Question: How effectively are you communicating the business value of your Scrum Master activities to leadership, and what specific metrics or stories could better demonstrate your impact? [Scrum Master Toolbox Podcast Recommends] 🚀 Global Agile Summit 2025 Join us in Tallinn, Estonia, from May 18th – 20th, 2025, for an event that will inspire, challenge, and equip you with real-world Agile success stories. 🌍 Connect with global Agile leaders. 💡 Learn practical strategies for impact. 🔥 Break free from Agile fatigue and become a Pragmatic Innovator Check Full Program [Scrum Master Toolbox Podcast Recommends] About Joel Bancroft-Connors Joel Bancroft-Connors is The Gorilla Coach — a Certified Scrum Trainer and Agile disruptor focused on sustainable value and effectiveness. With a background in product, project, and coaching, Joel blends sharp insights with practical tools to help teams thrive. He is a Miro power user and rocks curated classroom playlists. You can link with Joel Bancroft-Connors on LinkedIn.

2 Juni 15min

BONUS Martti Kuldma: How to Transform Century-Old Organizations Through Product-Driven Agile Transformation

BONUS Martti Kuldma: How to Transform Century-Old Organizations Through Product-Driven Agile Transformation

BONUS: Martti Kuldma shares how to transform century-old organizations through product-driven agile transformation In this BONUS episode we explore the remarkable transformation journey at Omniva with CEO Martti Kuldma. From traditional postal services to innovative logistics solutions, we explore how a 100+ year old company embraced product thinking, DevOps practices, and agile transformation to become a competitive force in modern logistics. Omniva's Digital Evolution—IT as a Revenue Center "We innovated the parcel machine business for a few years, and software has been an area of investment for us - software as a separate vertical in our business." Omniva represents a fascinating case study in organizational transformation. While many know it as Estonia's post office, the company has evolved into an international logistics powerhouse with significant revenue streams beyond traditional postal services. Under Martti's leadership, the organization has reimagined software not as a support function but as a core revenue driver, positioning itself for the dramatic shifts expected in logistics delivery over the next five years. The Vision: Physical Mailing as the Next IP Network "The Vision: physical mailing as the next IP network - this will give us a lot more freedom to adapt to changes in delivery demand." Martti's strategic vision extends far beyond conventional logistics thinking. By conceptualizing physical delivery networks similar to internet protocols, Omniva is preparing for a future where logistics companies leverage their physical infrastructure advantages. This approach addresses the fundamental challenge of fluctuating demand in e-commerce and traditional logistics, creating opportunities for crowd delivery solutions and gig economy integration that capitalize on existing network effects. Breaking Down Waterfall Barriers "When I came we had waterfall processes - annual budgeting, procurement for software development. It took a couple of weeks to do the first rounds, and understand what could be improved." The transformation from traditional procurement-based software development to agile product teams required dismantling entrenched processes. Martti discovered that the contractor model, while seemingly cost-effective, created expensive knowledge transfer cycles and left the organization vulnerable when external teams departed. His engineering background enabled him to recruit talent and build sustainable development capabilities that keep critical knowledge within the organization. Creating Cross-Functional Product Teams "We started to create cross-functional product area teams. We are not going to tell you what you need to build. You are accountable for the logistics efficiency." The shift from eleven distinct roles in software development to autonomous product teams represents more than organizational restructuring. By empowering teams with accountability for business outcomes rather than just deliverables, Omniva transformed how work gets planned and executed. This approach eliminates traditional handoffs and role silos, creating teams that own both the problem and the solution. The Product Manager Evolution "For me, the PM is directly accountable for the business results. The final step of the transformation started when I took the CEO role." Martti identifies a critical challenge in agile transformations: the misunderstanding of Product Manager responsibilities. Rather than falling into delivery or project management patterns, effective PMs at Omniva own business results directly. This shift required company-wide transformation because technical changes alone cannot sustain organizational evolution without corresponding changes in mindset and accountability structures. Leadership Through Storytelling "My main tool is just talking. All I do is story-telling internally and externally. I needed to become the best salesman in the company." The transition from technical leadership to CEO revealed that transformation leadership requires different skills than technical management. Martti discovered that his primary value comes through narrative construction and communication rather than direct technical contribution. This realization highlights how senior leaders must evolve their impact methods as organizations scale and transform. Real-Time Feedback Philosophy "The feedback needs to be given immediately. 'Last year, in May your performance was not the best' - this is completely useless feedback." Martti's rejection of annual reviews stems from practical experience with feedback effectiveness. Immediate, personal feedback creates learning opportunities and course corrections that annual cycles cannot provide. Anonymous 360 feedback systems often dilute accountability and actionability, whereas direct, timely conversations enable meaningful professional development and relationship building. Essential Transformation Practices "You need to tell the story - and convince people that this transformation is essential and needed. You need to trust and let them make their own decisions." Drawing from experiences at both Pipedrive and Omniva, Martti identifies three critical elements for leading complex organizational change: Compelling narrative: People need to understand why transformation is necessary and how it benefits both the organization and their individual growth Distributed decision-making: Trust enables teams to solve problems creatively rather than waiting for hierarchical approval Business accountability for engineers: When technical teams understand and own business outcomes, they innovate more effectively toward meaningful goals The dynamic team formation model used at Pipedrive, where engineers and PMs pitched ideas and assembled mission-focused teams, demonstrates how organizational structure can enable rather than constrain innovation. About Martti Kuldma Martti Kuldma is CEO of Omniva, leading its transformation into a product-driven logistics company. A former engineering leader at Pipedrive and CTO at Omniva, he brings deep expertise in scaling teams, agile transformation, and digital innovation. Martti is also a startup founder and passionate advocate for high-impact product organizations. You can link with Martti Kuldma on LinkedIn.

31 Maj 44min

BONUS Entertainment That Makes Change: Lessons in Product Thinking from Believe Ltd. With Patrick James Lynch

BONUS Entertainment That Makes Change: Lessons in Product Thinking from Believe Ltd. With Patrick James Lynch

BONUS: Patrick James Lynch on Entertainment That Makes Change - Lessons in Product Thinking from Believe Ltd. In this BONUS episode we explore how Patrick James Lynch, filmmaker, media executive, and rare disease advocate, has built Believe Limited around a powerful mission: entertainment that effects change. Patrick shares his journey from personal experience with his brother's hemophilia to creating award-winning content that empowers rare and chronic disease communities, offering valuable lessons for product managers on human-centered design, stakeholder alignment, and building emotionally viable products. The Genesis of Entertainment That Effects Change "This is more than a product." Patrick's journey began with a deeply personal question about his brother who had hemophilia. As an entrepreneur, he set out to respond to an identified need with one product to meet that need, but quickly realized the scope was much larger. His curiosity about what was different between him and his brother led him to understand that he needed to help people like his brother. This realization drove him to create valuable online videos to engage their audience, marking the beginning of Believe Ltd.'s mission of entertainment that effects change. Essential Product Lessons: Listen, Learn, and Do No Harm "The fact that I am my audience, does not mean that I'm an expert." Patrick emphasizes the critical importance of conducting thorough needs assessments and truly understanding your community before building products. Key insights include: Embed yourself in the community you're serving rather than making assumptions Follow the principle of "listen, learn and do no harm" as your starting point Involve community engagement as a dedicated role - Believe Ltd. has a VP of community engagement Define clear phrases that explain the value you deliver to your audience Use your personal story to establish credibility and relate experiences to your audience The goal is to get as familiar with your community as possible, then conduct your own research and development based on those deep insights. Navigating Multi-Stakeholder Complexity "Collaboration only succeeds when all points of view are respected." Working with patients, funders, healthcare professionals, and pharmaceutical companies requires careful orchestration. Patrick's approach centers on prioritizing the end game and identifying the north star goal that aligns all parties. He emphasizes focusing on combined skills and networks rather than trying to accomplish everything at the start. The key is ensuring that aligning stakeholders becomes a central part of the process, with everyone being accounted for throughout the journey. Human-Centered Storytelling as Product Strategy "What's the story that shows the value add of your product?" Patrick advocates for human-centered storytelling as a fundamental product approach. Rather than leading with features or specifications, he suggests crafting stories that demonstrate real value - like how a thermos saved someone's life while hiking. Stories have been humanity's primary communication tool since the beginning of time, and they remain the most effective way to show product value and connect with audiences on a meaningful level. Being a Value Fundamentalist "At any given moment, if anyone takes a screen grab, and set it against our five core values as a company - you see it's playing out." Patrick describes himself as a value fundamentalist, meaning that their company's core values are always present in everything they do. This requires courage, including the willingness to say "no" when opportunities don't align with their values. As CEO, he believes in embodying these values consistently, even when it's challenging, because who they are must always be visible in their work. Balancing Vision with Community Feedback "When you ask the audience for a solution, there's no innovation." Patrick warns against sacrificing vision simply because you're working closely with your audience. While being in the sandbox with your community is essential, maintaining your original vision for entertainment that changes minds is equally important. He recommends having someone you can bounce ideas off to help maintain this balance, and remembers that all great things start small and are inherently iterative. Creating Emotionally Viable Products "We can't develop emotional connection by going through a list of features." Beyond minimum viable products, Patrick focuses on emotional viability - the hook that makes people truly care. Emotional connection cannot be built through feature lists but rather through compelling stories that capture people's imagination. When audiences engage with products outside of direct supervision, storytelling becomes the bridge that helps them discover new uses and applications. This creates a dance between product creators and their audience, leading to better product design. The Currency of Attention "Attention is the only currency - there's great wisdom in that." Patrick recognizes that in today's landscape, capturing and maintaining attention is the fundamental challenge. Since everyone is an audience member at different times, this perspective helps inform both strategy and tactics. Products must compete not just on functionality but on their ability to engage and maintain audience interest over time. As a recommended reading, Patrick suggests that we should read "Save The Cat! The Last Book on Screenwriting You'll Ever Need" to understand how to better tell stories about our products. About Patrick James Lynch Patrick James Lynch is a filmmaker, media executive, and rare disease advocate. CEO of Believe Limited and founder of BloodStream Media, he uses his experience with hemophilia to drive award-winning storytelling, health advocacy, and mission-driven content that inspires and empowers rare and chronic disease communities worldwide. You can link with Patrick James Lynch on LinkedIn and follow Patrick James Lynch's work on his website.

29 Maj 41min

BONUS The Startup CTO's Handbook With Zach Goldberg

BONUS The Startup CTO's Handbook With Zach Goldberg

BONUS: Zach Goldberg shares how to build high-performing engineering teams and master the startup CTO role In this BONUS episode, we dive deep into the world of startup leadership with Zach Goldberg, author of The Startup CTO's Handbook. We explore the critical transition from engineering to leadership, the art of balancing technical debt with startup urgency, and the communication skills that separate great CTOs from the rest. The Genesis of The Startup CTO's Handbook "My original training in software engineering was not enough for being a leader. All the people and leadership skills, I had to learn on my own." Zach's journey to writing The Startup CTO's Handbook began with a stark realization about the gap between technical training and leadership reality. Despite his classical software engineering background, he discovered that the people and leadership skills required for CTO success had to be self-taught. The book emerged from a growing Google Doc of topics and frameworks addressing the leadership and management challenges that CTOs consistently face - from hiring and performance management to making strategic decisions under pressure. Today, we can either buy the digital/print book on Amazon, or read the book on GitHub. In this segment, we also refer to the book The Great CEO Within. Learning to Truly Learn: The Max Mintz Story "Max only cared about my ability to learn - to get curious about something hard. He wanted to help me deal with complexity." Zach opens his book with a deeply personal story about his mentor, Max Mintz, who fundamentally changed his approach to learning during what he calls "the most impactful single coffee" of his life. Over 1.5 years of conversations, Max taught him that true learning isn't about accumulating facts, but about developing curiosity for hard problems and building the capacity to handle complexity. This lesson forms the foundation of effective CTO leadership - the ability to continuously learn and adapt in an ever-changing technical landscape. The Three Critical CTO Mistakes "As a CTO, the most important 3 things: people, people, people. Do the people have the right energy, the right passion? Assemble the right team." Zach identifies consistent patterns in startup CTO failures across his experience. The first and most critical mistake is undervaluing people decisions - failing to prioritize team energy, passion, and the right assembly of talent. The second category involves investment mistakes, particularly the challenge of balancing short-term survival needs with long-term technical goals. In startups, the ROI timespan is exceptionally short, requiring optimization for immediate objectives rather than hypothetical scale. The third mistake is treating technology as religion rather than tools, losing sight of what the business actually needs. Optimizing for Velocity and Developer Experience "You are optimizing for velocity! What are you doing to help developers get their work done? Look at developer experience as a metric." Successful startup CTOs understand that velocity - the time from idea to valuable market delivery - is paramount. This requires a fundamental shift in thinking about technology decisions, focusing on features that deliver real customer value rather than technical elegance. Zach emphasizes measuring developer experience as a key metric, recognizing that anything that helps developers work more effectively directly impacts the company's ability to survive and thrive in competitive markets. The Professional Skill Tree Concept "It's like a character progression in an RPG. When we learn one type of skills, we don't learn other types of skills. We make investments every day and we have a choice on where we learn." Drawing from gaming metaphors, Zach explains how technical professionals often reach Level 100 in engineering skills while remaining Level 1 in management. The skill tree concept highlights that every learning investment is a choice - time spent developing one skill area means less time available for others. For engineers transitioning to leadership, the key is recognizing opportunities to serve as tech leads, where they can begin setting culture and quality standards while still leveraging their technical expertise. Balancing Kaizen with Startup Urgency "Pick the high-impact debt, and pay that down. This is not always easy, especially because we also need to pick what debt we don't invest on." The tension between continuous improvement and startup speed requires sophisticated thinking about technical debt. Using financial analogies, Zach explains that technical debt has both principal and interest components. The key is identifying which debt carries the highest interest rates and can be paid down most quickly, while consciously choosing which debt to carry forward. This approach maintains the healthy tension between quality and speed that defines successful startup engineering. The Power of Audience Empathy "The single hardest skill, especially for very tech leaders is that of 'audience empathy.' When you explain ideas to people, you usually assume a lot - but they might not." According to Zach, the most undervalued communication habit for startup tech leaders is developing audience empathy. Technical leaders often suffer from the curse of knowledge, assuming their audience shares their context and understanding. The solution requires deliberately considering what the audience already knows before crafting any communication, whether it's explaining technical concepts to non-technical stakeholders or providing clear direction to team members. In this segment we refer to the concept of "the curse of knowledge", a cognitive bias that occurs when a person who has specialized knowledge assumes that others share in that knowledge. About Zach Goldberg Zach Goldberg is a seasoned technical entrepreneur, executive coach, and author of The Startup CTO's Handbook. With a founder's mentality and a passion for systems thinking, Zach helps engineering leaders build high-performing teams. He also founded Advance The World, a nonprofit inspiring youth in STEM through immersive experiences. You can link with Zach Goldberg on LinkedIn, and visit Zach's website at CTOHB.com.

28 Maj 41min

Populärt inom Politik & nyheter

svenska-fall
aftonbladet-krim
motiv
p3-krim
fordomspodden
flashback-forever
rss-viva-fotboll
rss-krimstad
aftonbladet-daily
rss-sanning-konsekvens
spar
blenda-2
rss-krimreportrarna
rss-frandfors-horna
rss-vad-fan-hande
dagens-eko
olyckan-inifran
krimmagasinet
rss-flodet
spotlight