<?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 Dr. Mohamed El-Refai on Medium]]></title>
        <description><![CDATA[Stories by Dr. Mohamed El-Refai on Medium]]></description>
        <link>https://medium.com/@melrefai?source=rss-94a0b35df7ae------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6Dx8jg0TgMzhacM31n4esQ.png</url>
            <title>Stories by Dr. Mohamed El-Refai on Medium</title>
            <link>https://medium.com/@melrefai?source=rss-94a0b35df7ae------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 03:47:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@melrefai/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[The Future Operating Model for IBM Garage in the Age of Agentic AI]]></title>
            <link>https://melrefai.medium.com/the-future-operating-model-for-ibm-garage-in-the-age-of-agentic-ai-8ecc4ec2112c?source=rss-94a0b35df7ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ecc4ec2112c</guid>
            <category><![CDATA[ibm-garage]]></category>
            <category><![CDATA[agentic-ai]]></category>
            <category><![CDATA[ai-in-enterprise]]></category>
            <category><![CDATA[operating-models]]></category>
            <category><![CDATA[business-transformation]]></category>
            <dc:creator><![CDATA[Dr. Mohamed El-Refai]]></dc:creator>
            <pubDate>Wed, 01 Jul 2026 14:47:03 GMT</pubDate>
            <atom:updated>2026-07-01T14:47:03.579Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U_w4WDEgEFFy-4ak5lLg-w.png" /><figcaption>The Future Operating Model for IBM Garage</figcaption></figure><h3>From Agile at Scale to Agentic Value Orchestration</h3><p>For years, IBM Garage has helped organizations move from idea to outcome through a disciplined model of co-creation, co-execution, and co-operation. It gave enterprises a practical way to connect strategy, design, engineering, business value, governance, and adoption into one operating model.</p><p>But the world around that model is changing.</p><p>Agentic AI is not simply another productivity tool. It is changing how work is decomposed, specified, built, tested, governed, supported, and improved. It is changing the economics of digital delivery. It is changing the shape of squads. And it is changing the role of humans from people who manually perform every activity to people who define intent, set direction, provide judgment, manage risk, ensure quality, and orchestrate value.</p><p>The future IBM Garage operating model should not abandon what made Garage successful. In fact, most of the operating model should remain. The portfolio structure, governance boards, investment controls, chapters, communities of practice, design authority, value orchestration, and adoption mechanisms become even more important.</p><p>What changes most is the squad.</p><p>The future Garage will be less about large delivery teams executing tasks manually, and more about small, sticky, highly capable human squads directing AI agents through well-defined goals, specifications, standards, and guardrails.</p><p>The operating model evolves from:</p><p><strong>Human-heavy agile delivery</strong></p><p>to:</p><p><strong>Human-led, AI-accelerated, value-orchestrated delivery</strong></p><p>And that distinction matters.</p><h3>What Should Not Change</h3><p>A common mistake in thinking about agentic organizations is assuming that AI will replace the operating model. It will not.</p><p>AI can accelerate activities, generate insights, draft artifacts, write code, test solutions, produce options, monitor signals, and support decision-making. But it should not replace the governance, accountability, prioritization, value discipline, and human judgment required to run an enterprise technology organization.</p><p>The future IBM Garage operating model still needs the same core interface structures.</p><p>The <strong>Investment Board</strong> remains essential because funding choices do not disappear in an AI-enabled organization. In fact, they become more important. If AI makes it easier to generate ideas, prototypes, and solution options, the enterprise needs an even stronger mechanism to decide where capital should go, which business opportunities deserve investment, and which ideas should stop.</p><p>The <strong>Garage Board</strong> also remains essential. It continues to manage impediments, prioritization decisions, capability constraints, capacity trade-offs, location strategy, delivery risks, and cross-portfolio escalation. AI can surface issues faster, but leadership still needs to decide what to do about them.</p><p>The <strong>Core Garage Team</strong> remains critical. The Garage Leader, Value Orchestration Lead, and Delivery Excellence Lead continue to provide the connective tissue across business, technology, delivery, governance, and measurable outcomes.</p><p>The <strong>SME Bar, chapters, and communities of practice</strong> also remain. Engineering, design, product, industry, data and AI, security, cloud, QA, Agile, DevOps, and architecture chapters may become AI-augmented, but they should not disappear. These groups set standards, define patterns, review exceptions, assess risk, and ensure consistency across squads and products.</p><p>This is especially important in an agentic organization. When AI agents are generating designs, code, tests, documentation, and operational recommendations, standards matter more, not less.</p><p>The future operating model needs more discipline around reusable specifications, engineering guidelines, architectural patterns, design systems, testing policies, security controls, and value metrics. AI agents can help enforce those standards, but humans must remain accountable for accepting risk, approving exceptions, and evolving the standards over time.</p><h3>What Changes Most: The Squad</h3><p>The current Garage operating model is built around different squad archetypes across the product lifecycle: Co-create squads, Co-execute squads, and Co-operate squads. These squads are aligned to portfolios and supported by portfolio management, agile coaching, design authority, chapters, and governance ceremonies.</p><p>That structure still makes sense.</p><p>But the composition and operating rhythm of the squads will change significantly.</p><p>In the future, the standard squad will be much smaller. The model I believe will dominate is a <strong>three-person AI-augmented squad</strong>:</p><ol><li><strong>Product Owner</strong></li><li><strong>Forward Deployment Engineer</strong></li><li><strong>Designer / Design Researcher</strong></li></ol><p>This does not mean every squad will always have exactly three people. Complex systems may require multiple pods working in parallel. Highly regulated environments may require additional risk, security, compliance, or change specialists. But the default unit of execution becomes smaller, more senior, more cross-functional, and much more AI-enabled.</p><p>The Product Owner defines business intent, prioritizes outcomes, validates value, and keeps the squad anchored in business impact.</p><p>The Forward Deployment Engineer combines architecture, full-stack engineering, solution shaping, integration thinking, and AI-agent direction. This role is not simply a developer. It is a builder, architect, translator, and orchestrator of agentic execution.</p><p>The Designer or Design Researcher ensures that the work remains human-centered. This role shapes the target experience, validates user needs, protects usability, and ensures that adoption is designed into the solution rather than treated as a post-launch activity.</p><p>The major shift is that the squad is no longer sized around the assumption that every task must be manually performed by humans. Instead, the squad is sized around the assumption that humans define intent, direction, quality, context, and decisions while AI agents accelerate analysis, generation, testing, documentation, and delivery.</p><h3>Co-create: Accelerated, But Still Human-Led</h3><p>The Co-create phase should change the least in terms of human involvement, but it should change significantly in speed.</p><p>Co-create is where strategy becomes a value framework. It is where teams identify observations, formulate problem hypotheses, validate pain points, map personas and journeys, generate solution hypotheses, and shape business opportunities.</p><p>AI can accelerate almost every one of these steps.</p><p>An interview transcript can be converted into observations. Observations can be clustered into themes. Themes can become problem hypotheses. Problem hypotheses can be tested against additional research. Pain points can be drafted. Personas and journey maps can be generated. Solution ideas can be proposed. A business opportunity canvas can be pre-populated.</p><p>Platforms like IBM Garage Experience can already support this kind of AI acceleration.</p><p>But Co-create should not become fully autonomous.</p><p>The reason is not that AI cannot generate useful ideas. It can. The reason is adoption.</p><p>The envisioning moment still matters. People need to come together, review the challenges, understand the user journeys, debate the solution options, and make decisions collectively. That shared decision-making creates ownership. Ownership creates adoption.</p><p>If AI generates the solution and the organization is simply told to implement it, adoption will suffer. People will not know why decisions were made. They will not see themselves in the solution. They will feel that change was done to them, not with them.</p><p>So the future Co-create squad should be smaller and faster, but still deeply human.</p><p>AI should prepare the room.</p><p>Humans should make the meaning.</p><h3>Co-execute: The Biggest Transformation</h3><p>Co-execute is where the operating model changes most dramatically.</p><p>In the traditional model, Co-execute requires larger squads because design, development, testing, architecture, quality, DevSecOps, and release activities are performed largely by humans. In an agentic model, much of this work becomes specification-driven and AI-assisted.</p><p>The squad’s job shifts from manually creating every deliverable to defining the right specifications, rules, guardrails, acceptance criteria, user experience requirements, architecture constraints, and engineering standards.</p><p>The Forward Deployment Engineer becomes central.</p><p>This role works with the Product Owner to understand what needs to be built, works with the Designer to ensure the target experience is clear, and then directs AI agents to generate working deliverables. From the first iteration, the squad should have something tangible to inspect, test, refine, and improve.</p><p>In this model, execution becomes much more parallel.</p><p>A complex product can be decomposed into components, services, experiences, workflows, data products, APIs, or subsystems. Multiple small pods can work in parallel, each directing AI agents against a clear specification. The challenge is no longer only “how many developers do we need?” The challenge becomes “how do we coordinate parallel agentic delivery without losing architectural coherence, experience consistency, quality, security, or value alignment?”</p><p>That is why governance does not go away.</p><p>Product increment planning still matters. Architecture review still matters. Design authority still matters. Portfolio synchronization still matters. Standards still matter. Quality still matters.</p><p>AI changes the speed of execution. It does not remove the need for orchestration.</p><h3>Co-operate: From Manual Support to Agentic Operations</h3><p>Co-operate will also be transformed.</p><p>Once a product has achieved product-market fit or enterprise adoption fit, the question becomes how to scale, harden, operate, maintain, and continuously improve it.</p><p>In the current model, Co-operate often requires meaningful development, support, reliability, quality, and maintenance capacity. In the future, much of this work will be AI-assisted or agent-driven.</p><p>AI agents can monitor production signals, identify incidents, summarize root causes, propose fixes, generate regression tests, update documentation, detect usage patterns, recommend improvements, and support service reliability teams.</p><p>But again, humans remain accountable.</p><p>The Co-operate squad becomes a small human team that governs agentic operations. It ensures that agents are working within approved guardrails, that incidents are handled appropriately, that changes are validated, that user experience does not degrade, and that business value continues to be realized.</p><p>The operating model shifts from “humans perform support activities” to “humans supervise, improve, and govern intelligent operational systems.”</p><p>This is where the Value Office becomes especially important.</p><p>The point of AI-enabled operations is not just to reduce support cost. It is to protect and grow the value of the product. That means tracking adoption, usage, reliability, benefit realization, productivity improvement, cost reduction, customer experience, risk reduction, and financial outcomes.</p><p>Co-operate is not the end of Garage.</p><p>It is where the value curve must prove itself.</p><h3>The Portfolio Model Still Holds</h3><p>The future Garage operating model should remain portfolio-based.</p><p>Portfolios create business alignment. They allow squads to build domain knowledge. They create continuity. They help organize investment, capability, capacity, governance, prioritization, and value tracking around meaningful business areas.</p><p>What changes is how squads are managed inside the portfolio.</p><p>The future model should use <strong>sticky pods</strong>.</p><p>A small squad should not be assembled and disassembled for every initiative. It should develop domain knowledge, product intuition, stakeholder relationships, and technical familiarity over time. It should move from opportunity to opportunity as a pod, not as a set of disconnected resources.</p><p>This matters even more in an AI-enabled organization.</p><p>The more AI accelerates delivery, the more context becomes the differentiator. A sticky squad that understands the business domain, enterprise architecture, user needs, data landscape, operational constraints, and value drivers will outperform a temporary group of individuals, even if both have access to the same AI tools.</p><p>Agentic delivery rewards context.</p><p>Portfolios are how that context is preserved.</p><h3>The Value Office Becomes More Important</h3><p>In an AI-enabled enterprise, there will be no shortage of ideas.</p><p>There will be too many.</p><p>AI will make it easier to generate use cases, prototypes, concepts, mockups, process redesigns, and automation opportunities. The risk is that organizations will confuse activity with value.</p><p>That is why the Value Office becomes one of the most important parts of the future Garage operating model.</p><p>The Value Office must ensure that every initiative has a clear value hypothesis, measurable outcomes, baseline metrics, target metrics, ownership, and a benefit realization path. It must ensure that the organization is not investing in attractive ideas that do not produce meaningful business impact.</p><p>This is especially important because many AI initiatives fail to reach production or fail to produce measurable value after launch. The future Garage model needs strong value orchestration from the start:</p><ul><li>What business outcome are we targeting?</li><li>What value lever are we activating?</li><li>What metric will prove progress?</li><li>What is the baseline?</li><li>What is the expected target?</li><li>When should value start to appear?</li><li>Who owns realization after launch?</li><li>What happens if the initiative is off track?</li></ul><p>AI can help monitor these signals, but humans need to govern the value conversation.</p><p>The Value Office becomes the mechanism that keeps the agentic organization honest.</p><h3>The Design Authority Becomes More Important, Not Less</h3><p>In many organizations, governance is viewed as a bottleneck. In an agentic organization, governance must become an accelerator.</p><p>The Design Authority should evolve into a more active, AI-enabled quality and standards system.</p><p>It should include representatives from engineering, product, design, data and AI, security, cloud, QA, architecture, industry, Agile, DevOps, and relevant technology Centers of Competency.</p><p>Its role is no longer just to review finished designs or approve exceptions. It must define the standards that AI agents use to do the work.</p><p>That includes:</p><ul><li>Architecture patterns</li><li>Engineering standards</li><li>Security controls</li><li>Design systems</li><li>UX principles</li><li>Data standards</li><li>API guidelines</li><li>Testing policies</li><li>Documentation requirements</li><li>Responsible AI guardrails</li><li>Reusable prompts and specifications</li><li>Quality gates for agent-generated deliverables</li></ul><p>The Design Authority may use AI agents to perform first-level reviews. For example, an architecture review agent could check a solution against enterprise patterns before the human board meets. A security agent could flag policy exceptions. A design agent could detect inconsistency with the design system. A QA agent could assess test coverage.</p><p>The human Design Authority then focuses on exceptions, trade-offs, risks, and decisions.</p><p>This is how governance becomes faster without becoming weaker.</p><h3>Ceremonies Still Matter</h3><p>Agentic AI does not eliminate ceremonies. It changes what ceremonies are for.</p><p><strong>Product Increment Planning</strong> still matters because humans must decide which features, outcomes, and usable deliverables should be grouped into each iteration. AI can break features into stories, tasks, tests, and execution plans, but humans need to shape the product increment around value and adoption.</p><p><strong>Portfolio Sync</strong> still matters because multiple business opportunities will move through the funnel at different speeds. Portfolio leaders need to synchronize priorities, dependencies, capacity, capability, and investment decisions.</p><p><strong>Capital, Capability, and Capacity Planning</strong> still matters because humans remain part of the system. Even if AI agents perform more work, organizations still need scarce human expertise to define intent, manage risk, approve exceptions, shape architecture, and engage stakeholders.</p><p><strong>Impediment Management</strong> becomes even more important because blockers in an agentic model may include data access, environment access, model restrictions, security approvals, integration constraints, unclear specifications, or unresolved business decisions.</p><p><strong>Enterprise Architecture Review</strong> still matters because AI-generated solutions must align with the enterprise architecture, technology strategy, data standards, and security posture. AI can accelerate the review process, but accountability remains human.</p><p><strong>Investment Board governance</strong> still matters because the enterprise must continuously decide whether to continue, pivot, scale, or stop initiatives based on value evidence.</p><p><strong>RAID management</strong> — risks, assumptions, issues, and dependencies — still matters because AI does not remove uncertainty. It may actually increase the need for transparency because work is moving faster.</p><p>The ceremonies remain, but the preparation, analysis, documentation, and review workflows become AI-assisted.</p><h3>The To-Be Operating Model</h3><p>The future IBM Garage operating model can be described as a portfolio-based, value-orchestrated, agentic delivery system.</p><p>At the top, the <strong>Investment Board</strong> controls funding, value expectations, and strategic allocation.</p><p>The <strong>Garage Board</strong> manages prioritization, impediments, capacity, capability, delivery health, and cross-portfolio decisions.</p><p>The <strong>Core Garage Team</strong> provides leadership across Garage operations, value orchestration, delivery excellence, and adoption.</p><p>The <strong>Value Office</strong> defines value hypotheses, metrics, baselines, targets, realization plans, and benefit tracking.</p><p>The <strong>Design Authority</strong> defines the standards, patterns, guardrails, and quality expectations that guide both human squads and AI agents.</p><p>The <strong>Chapters and CoCs</strong> maintain capability excellence across product, design, engineering, data and AI, cloud, security, QA, Agile, DevOps, architecture, and industry.</p><p>The <strong>Portfolio Teams</strong> manage business-aligned portfolios and sub-portfolios, with sticky squads that build domain knowledge over time.</p><p>The <strong>Co-create Squads</strong> remain human-led and AI-accelerated, focused on strategy, value framing, discovery, pain point validation, solution envisioning, and business opportunity development.</p><p>The <strong>Co-execute Squads</strong> become specification-driven AI execution pods, focused on translating business intent into working solutions through AI-assisted design, engineering, testing, and release.</p><p>The <strong>Co-operate Squads</strong> become agentic operations pods, focused on reliability, adoption, continuous improvement, value realization, and scaled operational governance.</p><p>The model does not remove humans.</p><p>It moves humans to the highest-value work.</p><h3>How to Move from the Current Model to the Future Model</h3><p>The transition should not be treated as a big-bang reorganization. It should be a deliberate evolution.</p><h3>Step 1: Map the Current Operating Model</h3><p>Start by documenting the current portfolios, sub-portfolios, squads, boards, chapters, CoCs, ceremonies, governance flows, value tracking mechanisms, and escalation paths.</p><p>Identify where the current model already works well. Do not change those areas unnecessarily.</p><p>The goal is not to replace the Garage operating model. The goal is to make it agentic.</p><h3>Step 2: Define the Agentic North Star</h3><p>Create a clear statement of what the future model is meant to achieve.</p><p>For example:</p><p>“We will evolve IBM Garage into a human-led, AI-accelerated operating model where small, sticky squads use AI agents to move from strategy to value realization faster, while strengthening governance, standards, adoption, and measurable business outcomes.”</p><p>This north star should make clear that AI is not replacing the operating model. AI is accelerating it.</p><h3>Step 3: Redesign Squad Archetypes</h3><p>Define the new squad archetypes for Co-create, Co-execute, and Co-operate.</p><p>The default archetype should be the three-person AI-augmented squad:</p><ul><li>Product Owner</li><li>Forward Deployment Engineer</li><li>Designer / Design Researcher</li></ul><p>Then define when additional roles are needed, such as change manager, security specialist, data engineer, architect, SRE, QA specialist, or industry SME.</p><p>This creates flexibility without reverting to large default squads.</p><h3>Step 4: Establish Sticky Pods</h3><p>Move away from treating people as interchangeable resources.</p><p>Create sticky pods aligned to portfolios or sub-portfolios. Allow these pods to move from initiative to initiative while preserving domain knowledge, stakeholder context, technical familiarity, and delivery rhythm.</p><p>This is one of the most important operating model changes.</p><p>AI can generate output quickly, but sticky human context creates better judgment.</p><h3>Step 5: Upgrade the Design Authority</h3><p>Expand the Design Authority mandate from reviewing work to defining the standards that guide agentic work.</p><p>This includes reusable patterns, prompt libraries, solution templates, reference architectures, design systems, security policies, testing standards, documentation standards, and responsible AI controls.</p><p>Then introduce AI agents that perform first-level reviews against those standards.</p><p>The Design Authority becomes both a governance body and an enablement engine.</p><h3>Step 6: Strengthen the Value Office</h3><p>Define value orchestration as a core capability, not an optional reporting function.</p><p>Every initiative should have clear value drivers, value levers, KPIs, baselines, targets, ownership, and realization timing.</p><p>The Value Office should track whether initiatives are producing the expected value and should escalate when they are not.</p><p>This prevents the organization from scaling AI activity without scaling business impact.</p><h3>Step 7: Rewire Ceremonies for AI-Augmented Work</h3><p>Keep the ceremonies, but change the inputs and outputs.</p><p>Product increment planning should use AI-generated story maps, test plans, dependency maps, and delivery options.</p><p>Portfolio sync should use AI-generated portfolio health insights, value signals, risk summaries, and capacity scenarios.</p><p>Architecture review should use AI-generated standards checks.</p><p>Impediment management should use AI-generated blocker summaries and escalation recommendations.</p><p>The ceremony stays human. The preparation becomes AI-assisted.</p><h3>Step 8: Pilot the Model in One Portfolio</h3><p>Do not transform everything at once.</p><p>Select one portfolio with meaningful business demand, supportive leadership, available SMEs, and enough delivery complexity to test the model properly.</p><p>Run the new model across one or two business opportunities. Measure speed, quality, adoption, team experience, value realization, and governance effectiveness.</p><p>The goal is to learn what changes when squads become smaller, AI usage increases, and governance becomes more standards-driven.</p><h3>Step 9: Build the Agentic Enablement Layer</h3><p>Create the reusable assets that allow the model to scale.</p><p>This includes:</p><ul><li>Standard prompts</li><li>Agent workflows</li><li>Specification templates</li><li>Architecture review checklists</li><li>Design review checklists</li><li>Business opportunity canvases</li><li>Value framework templates</li><li>Testing patterns</li><li>Security review patterns</li><li>Delivery playbooks</li><li>Adoption playbooks</li><li>Governance dashboards</li></ul><p>Without this enablement layer, each squad will invent its own way of working. That creates inconsistency and risk.</p><h3>Step 10: Scale Across Portfolios</h3><p>Once the model proves itself, scale it across portfolios.</p><p>Use the Garage Board, Design Authority, Value Office, chapters, and CoCs to ensure consistency. Use the sticky pod model to preserve knowledge. Use the Investment Board to make sure funding follows value.</p><p>The future operating model should scale through patterns, not bureaucracy.</p><h3>The Real Shift: From Delivery Capacity to Decision Quality</h3><p>The biggest change in the future Garage operating model is not that AI writes more code or produces more documentation.</p><p>The biggest change is that the bottleneck moves.</p><p>In the old model, the bottleneck was often delivery capacity.</p><p>In the future model, the bottleneck becomes decision quality.</p><p>Can the organization decide which opportunities matter most? Can it define value clearly? Can it write good specifications? Can it set strong standards? Can it manage risk? Can it create adoption? Can it govern AI-generated work without slowing everything down? Can it stop low-value work quickly? Can it scale what works?</p><p>That is why the IBM Garage operating model remains so relevant.</p><p>Garage was never just a delivery method. It was always a way to connect business intent, user needs, technology execution, and measurable value.</p><p>Agentic AI does not make that obsolete.</p><p>It makes it essential.</p><h3>Conclusion: The Garage Becomes the Operating System for Agentic Transformation</h3><p>The future of IBM Garage is not a choice between humans and AI.</p><p>It is a model where humans and AI work together through a disciplined operating system.</p><p>Humans set direction. AI accelerates work.</p><p>Humans define value. AI generates options.</p><p>Humans make decisions. AI provides evidence.</p><p>Humans own adoption. AI supports change.</p><p>Humans govern risk. AI scales review.</p><p>Humans orchestrate outcomes. AI compresses the path from idea to impact.</p><p>Organizations that adopt IBM Garage should not simply add AI tools to existing squads and call that transformation. They should evolve the operating model itself.</p><p>The future Garage is portfolio-based, value-led, governance-enabled, AI-accelerated, and human-accountable.</p><p>It keeps the boards, chapters, ceremonies, portfolios, and value discipline that enterprises need.</p><p>It transforms the squad into a small, sticky, AI-augmented pod.</p><p>It turns Co-create into a faster but still human-led discovery and envisioning engine.</p><p>It turns Co-execute into a specification-driven agentic delivery system.</p><p>It turns Co-operate into an AI-enabled value realization and operational excellence model.</p><p>That is the next evolution of IBM Garage.</p><p>Not less Garage.</p><p>A more powerful Garage for the agentic enterprise.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ecc4ec2112c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Squad of the Future: How Three People — and AI — Can Take a Product from Idea to Scale]]></title>
            <link>https://melrefai.medium.com/the-squad-of-the-future-how-three-people-and-ai-can-take-a-product-from-idea-to-scale-d6bb95e32c90?source=rss-94a0b35df7ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6bb95e32c90</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[forward-deployment-eng]]></category>
            <category><![CDATA[agile-teams]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Dr. Mohamed El-Refai]]></dc:creator>
            <pubDate>Thu, 18 Jun 2026 02:05:22 GMT</pubDate>
            <atom:updated>2026-06-18T02:05:22.515Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0Y1-oef_PzBgHiUC74FITg.png" /><figcaption>The Three Person Squad</figcaption></figure><p>For years, the standard digital product squad has typically consisted of seven to ten people: a product owner, product manager, business analyst, user experience designer, technical architect, several engineers, testers, and sometimes specialists in security, data, operations, or change management.</p><p>That structure made sense when each discipline depended on significant manual effort.</p><p>Requirements had to be documented. Research had to be synthesized. Interfaces had to be designed screen by screen. Code had to be written line by line. Test cases had to be created manually. Environments had to be configured. Documentation had to be maintained. Operational data had to be collected and interpreted by different teams.</p><p>Artificial intelligence is changing the economics of all this work.</p><p>AI can now help squads research markets, analyze customer feedback, generate hypotheses, create prototypes, write production code, generate tests, review security risks, produce documentation, monitor performance, diagnose incidents, and recommend improvements.</p><p>This does not mean that product development no longer needs human expertise.</p><p>It means that many activities that previously required separate full-time roles can increasingly be orchestrated by a much smaller group of highly capable people.</p><p>My view is that the core product squad of the future may shrink from the familiar seven-person model to just three roles:</p><ol><li><strong>A Product Owner</strong>, accountable for the problem, the product, the business outcome, and the decisions.</li><li><strong>A Forward Deployment Engineer</strong>, responsible for materializing the product using software engineering, architecture, data, automation, and AI.</li><li><strong>A Product Designer</strong>, included when experience quality, behavioral change, trust, differentiation, or visual design are material to success.</li></ol><p>This is not simply a smaller Agile squad.</p><p>It is an AI-augmented, outcome-oriented product unit capable of taking an idea through IBM Garage’s <strong>Co-create, Co-execute, and Co-operate</strong> practices — and turning it into a scalable product.</p><h3>Why the Traditional Squad Is Becoming Too Large</h3><p>The traditional squad was designed around specialization.</p><p>One person translated business needs. Another created the designs. Another defined the architecture. Several people developed the software. Someone else tested it. Operations teams took over after deployment.</p><p>The result was often a sequence of handoffs disguised as collaboration.</p><p>Even when everyone attended the same ceremonies, work still moved through functional boundaries:</p><p><strong>Business idea → requirement → design → architecture → build → test → deploy → operate</strong></p><p>Each transition introduced delay, interpretation risk, rework, and diluted accountability.</p><p>AI changes this operating model because it compresses the effort required across disciplines.</p><p>A Product Owner can use AI to analyze research, draft hypotheses, structure a value tree, produce acceptance criteria, synthesize stakeholder feedback, and model business scenarios.</p><p>A designer can use AI to rapidly generate alternative experiences, create interactive prototypes, test content, explore accessibility considerations, and produce design specifications.</p><p>A Forward Deployment Engineer can use AI to design architectures, generate code, configure infrastructure, create tests, analyze logs, resolve defects, write documentation, and automate deployment.</p><p>The squad therefore spends less time producing intermediate artifacts and more time making decisions, validating assumptions, integrating capabilities, and delivering outcomes.</p><p>That distinction is critical.</p><p>The squad of the future is not smaller because AI blindly replaces people.</p><p>It is smaller because AI allows a few experienced people to cover a much broader span of work.</p><h3>The Three Roles</h3><h3>1. The Product Owner: Owner of the Problem, Product, and Value</h3><p>In the squad of the future, the Product Owner is not merely the person who manages the backlog.</p><p>The Product Owner is the product’s human point of accountability.</p><p>This person owns:</p><ul><li>the customer or user problem;</li><li>the strategic alignment of the product;</li><li>the expected business outcomes;</li><li>the prioritization of opportunities;</li><li>the product vision and roadmap;</li><li>the scope of the minimum viable product;</li><li>the trade-offs between speed, value, risk, and quality;</li><li>stakeholder alignment;</li><li>adoption and value realization.</li></ul><p>The Product Owner must understand enough about the customer, business process, technology, data, economics, and organizational environment to make integrated decisions.</p><p>AI can help the Product Owner perform analysis, generate options, identify inconsistencies, and maintain product information. But AI cannot be accountable for selecting the problem worth solving or deciding which trade-offs the organization should accept.</p><p>The Product Owner must remain the person who says:</p><p>This is the problem we are solving, this is the outcome that matters, and this is the evidence that will tell us whether we succeeded.</p><h3>2. The Forward Deployment Engineer: The Product Materializer</h3><p>The Forward Deployment Engineer, or FDE, is not simply a faster developer.</p><p>The role combines elements of:</p><ul><li>software engineering;</li><li>solution architecture;</li><li>data engineering;</li><li>AI engineering;</li><li>platform engineering;</li><li>integration;</li><li>quality engineering;</li><li>DevSecOps;</li><li>operational support;</li><li>client or user-facing problem solving.</li></ul><p>The FDE works directly with the Product Owner and, where relevant, the designer. The engineer remains close to the business problem instead of receiving fully documented requirements through layers of intermediaries.</p><p>The FDE translates product intent into a working solution.</p><p>This includes:</p><ul><li>assessing technical feasibility;</li><li>selecting suitable platforms and services;</li><li>designing the architecture;</li><li>building applications and integrations;</li><li>configuring AI models and agents;</li><li>establishing data pipelines;</li><li>generating and executing tests;</li><li>automating deployment;</li><li>implementing observability;</li><li>resolving production issues;</li><li>continuously improving performance and reliability.</li></ul><p>AI makes this broad role increasingly viable.</p><p>A strong FDE can use AI-assisted development tools to generate large portions of the application, but the engineer must still understand whether the generated solution is secure, maintainable, scalable, explainable, and appropriate for the intended environment.</p><p>The defining capability of the FDE is therefore not coding speed.</p><p>It is the ability to transform an ambiguous business opportunity into a reliable, scalable product.</p><h3>3. The Product Designer: The Optional Role That Is Often Essential</h3><p>I describe the designer as optional not because design is unimportant, but because not every product requires a dedicated designer throughout its entire lifecycle.</p><p>Some products are primarily:</p><ul><li>internal workflow automations;</li><li>machine-to-machine services;</li><li>APIs;</li><li>data pipelines;</li><li>infrastructure tools;</li><li>narrowly scoped operational utilities.</li></ul><p>For these products, the Product Owner and FDE may be able to create an acceptable experience using established design systems, reusable components, and AI-assisted design tools.</p><p>However, a dedicated designer becomes essential when success depends heavily on:</p><ul><li>human behavior;</li><li>customer trust;</li><li>emotional response;</li><li>ease of use;</li><li>accessibility;</li><li>complex workflows;</li><li>brand differentiation;</li><li>consumer adoption;</li><li>high-stakes decisions;</li><li>major changes to how people work.</li></ul><p>The designer owns more than visual styling.</p><p>The role is responsible for ensuring that the product is useful, understandable, usable, accessible, and desirable.</p><p>The designer brings expertise in:</p><ul><li>user research;</li><li>journey mapping;</li><li>interaction design;</li><li>service design;</li><li>information architecture;</li><li>prototyping;</li><li>usability testing;</li><li>content design;</li><li>accessibility;</li><li>adoption-oriented experience design.</li></ul><p>AI can generate screens, but it cannot independently determine whether an experience respects the context, fears, motivations, abilities, and behaviors of real users.</p><p>The designer protects the squad from building a technically impressive product that people do not understand, trust, or use.</p><h3>How the Three-Person Squad Works Through IBM Garage</h3><p>IBM Garage provides a useful structure for imagining how this smaller squad can take a product from idea to enterprise scale.</p><p>The model can be understood through three interconnected practices:</p><ul><li><strong>Co-create</strong>: Define the value, validate the problem, and shape the right solution.</li><li><strong>Co-execute</strong>: Design, build, test, release, and iteratively improve the product.</li><li><strong>Co-operate</strong>: Harden, scale, run, govern, and continuously optimize the product.</li></ul><p>The squad remains stable across these stages, while specialist expertise is brought in temporarily when needed.</p><p>This persistence is important. The people who understand the original problem remain accountable as the product moves into production and scale.</p><h3>Co-create: From Idea to Validated Product Opportunity</h3><p>Co-create begins with a strategic intent, business challenge, customer need, or operational problem.</p><p>The objective is not to immediately generate a solution. It is to determine whether the problem is worth solving, for whom, and with what expected value.</p><h3>The Product Owner in Co-create</h3><p>The Product Owner leads the framing of the opportunity.</p><p>They work with sponsors, users, subject-matter experts, and other stakeholders to define:</p><ul><li>the strategic initiative;</li><li>the expected outcomes;</li><li>the target users or customers;</li><li>the pain points to investigate;</li><li>the value pools and value drivers;</li><li>the business constraints;</li><li>the key risks and assumptions.</li></ul><p>The Product Owner creates or orchestrates the product’s value framework.</p><p>This connects the product to measurable outcomes such as:</p><ul><li>revenue growth;</li><li>cost reduction;</li><li>productivity improvement;</li><li>better customer experience;</li><li>risk reduction;</li><li>improved capital utilization;</li><li>strategic capability creation.</li></ul><p>AI helps the Product Owner analyze internal information, market research, user feedback, operational metrics, and comparable products. It can generate initial hypotheses and identify patterns that deserve further investigation.</p><p>But the Product Owner decides which hypotheses matter.</p><h3>The Designer in Co-create</h3><p>When experience is material, the designer leads the human-centered research.</p><p>The designer helps the squad understand:</p><ul><li>who experiences the problem;</li><li>what users are trying to accomplish;</li><li>where friction occurs;</li><li>how users currently work around the problem;</li><li>what emotions, incentives, or fears affect behavior;</li><li>what a better future-state experience might look like.</li></ul><p>The designer creates journey maps, experience models, prototypes, and concept tests.</p><p>AI can accelerate the synthesis of interviews and generate alternative concepts, but the designer must ensure that the team does not mistake plausible AI-generated observations for validated human insight.</p><h3>The FDE in Co-create</h3><p>The FDE participates from the beginning rather than waiting for a finalized specification.</p><p>The engineer evaluates:</p><ul><li>technical feasibility;</li><li>data availability and quality;</li><li>integration dependencies;</li><li>relevant existing platforms;</li><li>security and compliance constraints;</li><li>likely architectural approaches;</li><li>the suitability of AI;</li><li>build-versus-buy options;</li><li>technical risk;</li><li>indicative cost and effort.</li></ul><p>The FDE may create technical spikes, proofs of concept, or disposable prototypes to test the riskiest assumptions.</p><p>This prevents the squad from validating a desirable business concept that cannot be implemented economically or safely.</p><h3>The Joint Co-create Output</h3><p>Together, the three roles produce:</p><ul><li>a clearly defined problem;</li><li>validated user pain points;</li><li>a value framework;</li><li>a prioritized set of hypotheses;</li><li>an initial future-state experience;</li><li>a proposed solution concept;</li><li>a feasibility assessment;</li><li>an MVP definition;</li><li>success metrics;</li><li>an initial roadmap;</li><li>an evidence-based decision to proceed, pivot, or stop.</li></ul><p>The power of the three-person model is that desirability, viability, and feasibility are considered simultaneously.</p><p>There is no need to pass the opportunity from a strategy team to a design team and then to a technology team.</p><p>The squad develops the opportunity together.</p><h3>Co-execute: From Validated Opportunity to Working Product</h3><p>Co-execute turns validated hypotheses into a product that users can experience and the business can measure.</p><p>This stage has two closely linked dimensions:</p><ol><li>Designing the target experience and architecture to shape the MVP and roadmap.</li><li>Iteratively building, testing, releasing, and learning using Agile and DevSecOps practices.</li></ol><h3>Joint Product Ownership</h3><p>The Product Owner remains accountable for business and product decisions, but the product is shaped collaboratively.</p><p>The designer owns experience integrity.</p><p>The FDE owns technical integrity.</p><p>None of the roles works in isolation.</p><p>For example:</p><ul><li>The Product Owner cannot prioritize a feature without understanding its technical cost and user impact.</li><li>The designer cannot finalize a journey without understanding data, system, and regulatory constraints.</li><li>The FDE cannot select an architecture without understanding the desired user experience and business roadmap.</li></ul><p>The product emerges through continuous negotiation between value, experience, and engineering.</p><h3>The Product Owner in Co-execute</h3><p>The Product Owner manages the product as a sequence of measurable outcomes rather than a catalogue of features.</p><p>Responsibilities include:</p><ul><li>maintaining the product vision;</li><li>prioritizing the backlog;</li><li>defining acceptance criteria;</li><li>resolving scope decisions;</li><li>engaging stakeholders;</li><li>monitoring user feedback;</li><li>validating business assumptions;</li><li>tracking outcome metrics;</li><li>deciding when to release;</li><li>managing the product roadmap.</li></ul><p>AI can help generate user stories, acceptance criteria, test scenarios, release notes, product documentation, and stakeholder communications.</p><p>However, the Product Owner must prevent the ease of AI-generated output from creating backlog inflation.</p><p>The squad should build less, not merely generate more requirements faster.</p><p>Every backlog item should exist because it contributes to a validated outcome, reduces a meaningful risk, or generates necessary learning.</p><h3>The Designer in Co-execute</h3><p>The designer works continuously with the Product Owner and FDE.</p><p>Activities include:</p><ul><li>refining workflows;</li><li>creating interaction patterns;</li><li>applying the design system;</li><li>producing prototypes;</li><li>conducting usability tests;</li><li>testing content;</li><li>validating accessibility;</li><li>analyzing behavioral data;</li><li>improving the experience based on evidence.</li></ul><p>AI allows the designer to generate multiple alternatives rapidly.</p><p>Instead of spending days creating the first design, the designer can spend more time comparing options, testing assumptions, observing users, and refining the experience.</p><p>The designer also helps ensure that the product does not expose the complexity of its underlying AI.</p><p>Users should not need to understand prompts, models, retrieval pipelines, agent orchestration, or confidence thresholds unless that information genuinely improves their decisions.</p><h3>The FDE in Co-execute</h3><p>The FDE creates the working product using AI-accelerated engineering practices.</p><p>The role covers:</p><ul><li>application development;</li><li>API and system integration;</li><li>data engineering;</li><li>AI model or agent integration;</li><li>architecture;</li><li>infrastructure as code;</li><li>automated testing;</li><li>performance engineering;</li><li>security controls;</li><li>deployment automation;</li><li>monitoring and observability.</li></ul><p>AI can assist in producing:</p><ul><li>application code;</li><li>database schemas;</li><li>interface components;</li><li>integration mappings;</li><li>unit tests;</li><li>synthetic test data;</li><li>threat models;</li><li>infrastructure scripts;</li><li>technical documentation;</li><li>incident diagnostics.</li></ul><p>The FDE still reviews and owns the output.</p><p>This is particularly important for AI-generated code, which may function correctly in a demonstration while remaining insecure, fragile, expensive, or difficult to maintain.</p><p>The FDE ensures that speed does not create hidden technical debt.</p><h3>What Happens to Testing?</h3><p>Testing does not disappear in the three-person squad.</p><p>It becomes embedded.</p><p>The FDE establishes automated unit, integration, security, performance, and regression testing. The designer validates usability and accessibility. The Product Owner leads business acceptance and confirms that the product produces the expected outcomes.</p><p>AI generates and maintains many of the test cases, but humans determine what quality means.</p><p>For AI-enabled products, the squad must also test:</p><ul><li>response accuracy;</li><li>groundedness;</li><li>hallucination risk;</li><li>bias;</li><li>harmful outputs;</li><li>prompt injection;</li><li>data leakage;</li><li>model drift;</li><li>explainability;</li><li>cost per interaction;</li><li>human override and escalation.</li></ul><p>The absence of a dedicated tester does not mean the absence of quality engineering.</p><p>Quality becomes a shared property of the product.</p><h3>What Happens to Architecture?</h3><p>Architecture also becomes embedded.</p><p>The FDE is responsible for making the majority of architecture decisions, supported by reusable enterprise patterns, reference architectures, governance guardrails, and AI-assisted analysis.</p><p>For high-risk or enterprise-wide decisions, specialist architects can be engaged temporarily.</p><p>This leads to an important distinction:</p><p>The three-person squad is the persistent core, not the only expertise the product will ever require.</p><p>The squad may draw on specialists in areas such as cybersecurity, legal, compliance, data science, platform engineering, accessibility, industry regulation, or organizational change.</p><p>These experts should engage as needed without becoming permanent handoffs or approval queues.</p><h3>Co-operate: From Product Release to Scaled Business Capability</h3><p>Traditional product teams often treat deployment as the end of delivery.</p><p>The squad of the future treats production as the beginning of evidence.</p><p>Co-operate is where the product is hardened, scaled, run, measured, and continuously improved.</p><p>The same core squad remains involved.</p><p>This continuity eliminates the common divide between those who build the product and those who inherit its operational consequences.</p><h3>The Product Owner in Co-operate</h3><p>The Product Owner monitors whether the product is generating the intended value.</p><p>This includes:</p><ul><li>adoption;</li><li>customer or employee behavior;</li><li>financial performance;</li><li>productivity improvement;</li><li>service quality;</li><li>risk reduction;</li><li>user satisfaction;</li><li>outcome realization;</li><li>roadmap performance.</li></ul><p>The Product Owner works with business leaders to compare actual results against the original value hypothesis.</p><p>When the expected value is not being achieved, the Product Owner investigates why.</p><p>Possible causes may include:</p><ul><li>the original hypothesis was wrong;</li><li>users are not adopting the product;</li><li>the process around the product did not change;</li><li>data quality is inadequate;</li><li>the product is solving only part of the problem;</li><li>operational reliability is poor;</li><li>incentives discourage the intended behavior.</li></ul><p>The Product Owner decides whether to improve, reposition, scale, or retire the product.</p><h3>The Designer in Co-operate</h3><p>Where a designer remains part of the squad, they continue to study real-world behavior.</p><p>The designer analyzes:</p><ul><li>where users abandon workflows;</li><li>which steps cause confusion;</li><li>how the product changes user behavior;</li><li>whether accessibility is maintained;</li><li>whether AI recommendations are trusted;</li><li>where workarounds are emerging;</li><li>how the experience should evolve as the product scales.</li></ul><p>The designer may not need to remain allocated full-time.</p><p>They can move between products or join the squad at specific points in the lifecycle. But experience ownership must not disappear once the product is released.</p><h3>The FDE in Co-operate</h3><p>The FDE owns or closely supports:</p><ul><li>production reliability;</li><li>observability;</li><li>incident resolution;</li><li>system performance;</li><li>security;</li><li>capacity;</li><li>cost optimization;</li><li>automated remediation;</li><li>release management;</li><li>technical debt reduction;</li><li>platform evolution.</li></ul><p>AI-driven operations help the FDE identify anomalies, summarize incidents, diagnose root causes, recommend fixes, generate patches, and automate routine recovery.</p><p>For AI-enabled products, the FDE also monitors:</p><ul><li>model quality;</li><li>token and inference costs;</li><li>latency;</li><li>retrieval performance;</li><li>drift;</li><li>grounding quality;</li><li>agent failures;</li><li>model and prompt versions;</li><li>guardrail performance.</li></ul><p>The FDE ensures that the product remains not only operational, but economically and technically sustainable.</p><h3>Continuous Improvement in Co-operate</h3><p>The squad continuously cycles through:</p><p><strong>Observe → Learn → Prioritize → Improve → Release → Measure</strong></p><p>Operational telemetry informs product decisions.</p><p>User feedback informs design changes.</p><p>Business outcomes inform roadmap decisions.</p><p>Technical performance informs architecture changes.</p><p>AI accelerates each part of the loop, but the squad remains accountable for interpreting the evidence.</p><p>This is how Co-operate reconnects to Co-create.</p><p>Every product improvement is a new hypothesis.</p><h3>How Can Three People Perform All the Work?</h3><p>The answer is not that every activity disappears.</p><p>The answer is that work is divided into four categories.</p><h3>1. Human Accountability</h3><p>Some responsibilities should remain explicitly human:</p><ul><li>choosing the problem;</li><li>making ethical decisions;</li><li>setting priorities;</li><li>resolving trade-offs;</li><li>understanding organizational context;</li><li>earning stakeholder trust;</li><li>accepting business risk;</li><li>being accountable for outcomes.</li></ul><p>These sit primarily with the Product Owner, supported by the designer and FDE.</p><h3>2. AI-Augmented Work</h3><p>Many activities can be performed faster with AI:</p><ul><li>research synthesis;</li><li>user story creation;</li><li>prototype generation;</li><li>coding;</li><li>test generation;</li><li>documentation;</li><li>data analysis;</li><li>incident analysis;</li><li>communication drafting;</li><li>roadmap scenario modelling.</li></ul><p>Humans direct, validate, and take responsibility for the outputs.</p><h3>3. Automated Work</h3><p>Some work should become part of the product delivery system:</p><ul><li>continuous integration;</li><li>regression testing;</li><li>security scanning;</li><li>infrastructure provisioning;</li><li>deployment;</li><li>monitoring;</li><li>alerting;</li><li>policy enforcement;</li><li>documentation updates.</li></ul><p>This is primarily established by the FDE.</p><h3>4. On-Demand Specialist Work</h3><p>Certain expertise remains necessary but does not need to be permanently embedded:</p><ul><li>cybersecurity assessment;</li><li>legal review;</li><li>regulatory compliance;</li><li>specialist data science;</li><li>enterprise architecture;</li><li>penetration testing;</li><li>accessibility auditing;</li><li>change management;</li><li>domain expertise.</li></ul><p>These specialists should plug into the squad through clear, lightweight engagement models.</p><h3>The Three-Person Squad Is Not Three Junior Generalists</h3><p>This model only works when the core roles are highly capable.</p><p>A three-person squad of inexperienced practitioners using AI will not necessarily outperform a seven-person experienced team.</p><p>AI can amplify judgment, but it can also amplify poor decisions.</p><p>The future squad needs what might be called <strong>T-shaped-plus</strong> people.</p><p>Each person requires deep expertise in their primary discipline and sufficient understanding of adjacent disciplines to collaborate without extensive translation.</p><p>The Product Owner must understand technology and experience.</p><p>The FDE must understand products and users.</p><p>The designer must understand business value and technical constraints.</p><p>Their domains overlap, even though their accountabilities remain distinct.</p><h3>When the Three-Person Model Works Best</h3><p>The model is particularly effective when:</p><ul><li>the product has a clearly accountable Product Owner;</li><li>the squad has access to decision-makers and users;</li><li>enterprise platforms and design systems are available;</li><li>AI-assisted engineering tools are approved and integrated;</li><li>deployment pipelines are automated;</li><li>governance is expressed through guardrails rather than manual gates;</li><li>the product can be built through iterative releases;</li><li>specialist support is available when required;</li><li>the FDE has sufficient engineering depth;</li><li>outcomes can be measured.</li></ul><h3>When Three People Are Not Enough</h3><p>The three-person squad should not become an ideology.</p><p>Larger squads may still be required when:</p><ul><li>the solution includes several complex technical domains;</li><li>the product supports millions of users or extreme transaction volumes;</li><li>multiple platforms must be developed simultaneously;</li><li>the regulatory environment requires extensive independent controls;</li><li>the product involves safety-critical systems;</li><li>major data science research is required;</li><li>the organization lacks reusable platforms and automation;</li><li>the product requires significant organizational change;</li><li>several user segments have very different needs;</li><li>operational coverage is required around the clock.</li></ul><p>In these situations, the core three-person squad can remain the product leadership nucleus while additional engineers, designers, data scientists, or specialists join around it.</p><p>The aim is not to cap every squad at three people.</p><p>The aim is to start with the smallest accountable unit and add capacity only where the work demands it.</p><h3>The Designer May Be Optional, but Design Is Not</h3><p>One of the most important nuances in this model is the distinction between a dedicated designer and the practice of design.</p><p>A product without a full-time designer must still consider:</p><ul><li>who will use it;</li><li>what they are trying to achieve;</li><li>how the workflow should operate;</li><li>whether the product is understandable;</li><li>whether it is accessible;</li><li>whether people will trust it;</li><li>whether the experience supports adoption.</li></ul><p>For a simple internal tool, the Product Owner may lead this work using existing design patterns, with the FDE implementing the experience.</p><p>For a complex or differentiated product, an experienced designer should be part of the core squad.</p><p>Design capacity should therefore be driven by product risk, not by a fixed staffing formula.</p><h3>From Role-Based Delivery to Outcome-Based Delivery</h3><p>The broader change is not the reduction from seven people to three.</p><p>It is the movement from role-based delivery to outcome-based delivery.</p><p>Traditional organizations often ask:</p><ul><li>Have the requirements been documented?</li><li>Has design completed the screens?</li><li>Has development finished the sprint?</li><li>Has testing signed off?</li><li>Has the operations team accepted the release?</li></ul><p>The squad of the future asks different questions:</p><ul><li>Have we validated that the problem matters?</li><li>Is the product producing the desired behavior?</li><li>Is it generating measurable business value?</li><li>Is it safe, reliable, and scalable?</li><li>What have we learned?</li><li>What should we change next?</li></ul><p>The first set of questions measures functional completion.</p><p>The second measures product success.</p><h3>A Possible Operating Rhythm</h3><p>A three-person AI-accelerated squad could operate with a lightweight weekly rhythm.</p><h3>Product and Value Review</h3><p>The Product Owner leads a review of:</p><ul><li>product outcomes;</li><li>adoption;</li><li>customer feedback;</li><li>value realization;</li><li>risks;</li><li>priorities;</li><li>roadmap decisions.</li></ul><h3>Experience Review</h3><p>The designer, or the Product Owner when no dedicated designer is present, reviews:</p><ul><li>user behavior;</li><li>usability findings;</li><li>workflow friction;</li><li>accessibility;</li><li>prototype feedback;</li><li>experience improvements.</li></ul><h3>Engineering and Operations Review</h3><p>The FDE reviews:</p><ul><li>delivery progress;</li><li>architecture decisions;</li><li>quality;</li><li>security;</li><li>incidents;</li><li>performance;</li><li>AI model behavior;</li><li>infrastructure and inference costs.</li></ul><h3>Joint Prioritization</h3><p>The three roles decide what to learn, build, improve, or stop next.</p><p>AI agents can prepare much of the supporting material, but the squad makes the decisions together.</p><h3>The New Economics of Product Innovation</h3><p>The implications for organizations are significant.</p><p>When product squads become smaller and more capable:</p><ul><li>more ideas can be tested;</li><li>the cost of experimentation falls;</li><li>products can reach users faster;</li><li>fewer handoffs reduce rework;</li><li>accountability becomes clearer;</li><li>the distance between strategy and execution shrinks;</li><li>operational learning reaches the roadmap faster;</li><li>low-value ideas can be stopped earlier;</li><li>successful products can be scaled with greater confidence.</li></ul><p>The limiting factor may no longer be how many developers an organization can assign.</p><p>It may become how many qualified Product Owners it has who can identify valuable problems, make strong decisions, and lead AI-augmented product teams.</p><p>This is a major leadership challenge.</p><p>Organizations that invest only in AI coding tools may accelerate development without improving product outcomes.</p><p>They may simply build the wrong things faster.</p><h3>The Squad of the Future</h3><p>The future product squad is not a miniature version of today’s delivery team.</p><p>It is a different operating model.</p><p>The Product Owner owns the problem, value, and product decisions.</p><p>The Forward Deployment Engineer materializes the product and keeps it technically and operationally viable.</p><p>The Product Designer ensures that the product works for human beings when experience is central to success.</p><p>Together, supported by AI and on-demand specialists, they can move continuously through:</p><p><strong>Co-create → Co-execute → Co-operate</strong></p><p>They can frame the opportunity, validate the need, design the experience, architect the solution, build the MVP, release it, operate it, scale it, and measure whether it delivers the intended value.</p><p>The seven-person squad will not disappear overnight, and three people will not be sufficient for every product.</p><p>But the direction is becoming clear.</p><p>As AI takes on more of the production effort, the value of the squad will depend less on the number of roles represented and more on the quality of its judgment, collaboration, and accountability.</p><p>The squad of the future will be smaller.</p><p>Its members will be broader.</p><p>Its tools will be more powerful.</p><p>And its success will be measured not by how much it produces, but by how effectively it turns ideas into outcomes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6bb95e32c90" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Manager vs. Product Owner in the AI-Accelerated Product Life Cycle: Do We Really Need Both?]]></title>
            <link>https://melrefai.medium.com/product-manager-vs-product-owner-in-the-ai-accelerated-product-life-cycle-do-we-really-need-both-b4569d54353e?source=rss-94a0b35df7ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4569d54353e</guid>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Dr. Mohamed El-Refai]]></dc:creator>
            <pubDate>Sun, 31 May 2026 21:28:27 GMT</pubDate>
            <atom:updated>2026-05-31T21:28:27.826Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A critical view on product management and product ownership" src="https://cdn-images-1.medium.com/max/1024/1*vn0K3s7Bed9FfJJHqYE3iA.png" /></figure><p>Walk into almost any product organization and ask a simple question: <strong>What is the difference between a Product Manager and a Product Owner?</strong></p><p>You will probably get ten different answers.</p><p>Some people will say the Product Manager owns strategy while the Product Owner owns execution. Others will say the Product Manager owns the “why” and “what,” while the Product Owner owns the “how” and “when.” Agile practitioners may point to Scrum and say the Product Owner is accountable for maximizing the value of the product backlog. Enterprise transformation teams may point to SAFe and describe Product Managers as market-facing and Product Owners as team-facing.</p><p>The confusion is not just semantic. It creates real operating-model consequences.</p><p>When the distinction is clear and purposeful, the two roles can complement each other. When the distinction is artificial, the split creates handoffs, delays, meetings, diluted accountability, and a slower product life cycle.</p><p>That question becomes even more important in the AI era.</p><p>AI-assisted product engineering is reducing the need for large development teams. AI tools can now help generate code, produce prototypes, draft user stories, create test cases, summarize user research, generate documentation, analyze feedback, and accelerate release cycles. In that environment, organizations should be very careful before preserving old delivery structures that were designed for slower, heavier, more manual development models.</p><p>The real question is no longer:</p><p><strong>Do we need both a Product Manager and a Product Owner?</strong></p><p>The better question is:</p><p><strong>What roles are truly required to move from customer insight to business value as quickly, safely, and intelligently as possible?</strong></p><p>My view is simple: <strong>many small and medium-sized organizations do not need both roles. Many large organizations do — but only when complexity justifies the split and decision rights are crystal clear.</strong></p><p>The goal is not to protect job titles. The goal is to create a productive product life cycle.</p><h3>The Traditional Difference Between Product Manager and Product Owner</h3><p>The Product Manager is typically accountable for the strategic success of the product.</p><p>The Product Owner is typically accountable for delivery clarity and backlog execution.</p><p>That distinction is useful, but incomplete.</p><p>A strong <strong>Product Manager</strong> connects customer needs, market opportunity, business strategy, product direction, investment priorities, and measurable outcomes. The Product Manager should understand what problem is worth solving, why it matters, who it matters to, what value will be created, and how success will be measured.</p><p>A strong <strong>Product Owner</strong> translates product intent into actionable delivery work. The Product Owner ensures that the team understands what needs to be built, why it matters, what the acceptance criteria are, what should be prioritized next, and whether the delivered work meets expectations.</p><p>In theory, this creates a clean division:</p><p>DimensionProduct ManagerProduct OwnerPrimary focusStrategy, customer, market, business valueBacklog, delivery clarity, executionTime horizonQuarters to yearsSprints to monthsMain stakeholdersCustomers, executives, sales, marketing, finance, operations, supportEngineering, design, QA, delivery teamKey artifactProduct vision, strategy, roadmap, business case, outcomesProduct backlog, user stories, acceptance criteria, sprint prioritiesMain questionAre we building the right product?Are we building the product right, in the right order?Success measureAdoption, revenue, retention, productivity, customer satisfaction, business valueBacklog health, delivery readiness, accepted increments, team clarity</p><p>But the reality is messier.</p><p>The Product Manager cannot be disconnected from delivery. The Product Owner cannot be disconnected from customer and business value. When that separation happens, the organization gets the worst version of both roles.</p><h3>The Product Manager: Owner of Product Value</h3><p>The Product Manager should be accountable for product value, not just product direction.</p><p>That means the PM must answer hard questions:</p><p>What customer problem are we solving?<br>Is this problem important enough to justify investment?<br>What business outcome are we trying to create?<br>What customer behavior do we need to change?<br>What should we build, buy, partner for, automate, or not do at all?<br>What should we stop doing?<br>What trade-offs are we willing to make?<br>How will we know whether the product succeeded?</p><p>The PM is not just a roadmap owner. The PM is not the “CEO of the product,” because most PMs do not have CEO-like authority over budget, people, incentives, sales, marketing, or operations. A better description is that the PM is the <strong>connective tissue</strong> between customer needs, business strategy, product direction, and measurable outcomes.</p><p>A good PM should be deeply involved in:</p><p>Customer research<br>Market and competitor analysis<br>Product vision and strategy<br>Business case development<br>Roadmap prioritization<br>Value metrics and outcome tracking<br>Stakeholder alignment<br>Go-to-market and adoption planning<br>Continuous improvement after release</p><p>The PM’s accountability should not end when something ships. Shipping is an activity. Value realization is the outcome.</p><p>In many organizations, the PM role fails because it becomes too abstract. The PM becomes a strategy presenter, roadmap narrator, or stakeholder manager who is not close enough to engineering, design, users, or delivery reality. Hermes called this anti-pattern the <strong>“PowerPoint Strategist”</strong> — a PM who produces decks but not outcomes.</p><p>That version of the PM role is not useful. In an AI-accelerated product life cycle, it is even less useful because the speed of delivery demands tighter connection between strategy and execution.</p><h3>The Product Owner: Owner of Delivery Clarity</h3><p>The Product Owner should be accountable for delivery clarity.</p><p>That means the PO must answer different but equally important questions:</p><p>What is the next most valuable thing for the team to work on?<br>Is the backlog clear, ordered, and ready?<br>Does every backlog item connect to a product goal?<br>Are the acceptance criteria specific enough?<br>What decisions can be made now to avoid blocking the team later?<br>What should be descoped, split, deferred, or clarified?<br>Does the completed work meet the agreed definition of done?</p><p>A good PO is not a Jira administrator. A good PO is not a requirements secretary. A good PO is not a messenger between the PM and engineering.</p><p>A strong PO brings structure, clarity, and decision speed to delivery. The PO helps the team move without waiting for every small decision to be escalated. They protect the team from noise. They maintain backlog health. They help translate strategic intent into executable increments.</p><p>When the PO is effective, engineers and designers have enough context to make good decisions without constant interruption. When the PO is weak, the team either builds the wrong thing efficiently or waits endlessly for clarification.</p><p>Hermes identified one of the most common failure modes: the <strong>“Backlog Secretary.”</strong> In this anti-pattern, the PO simply takes requirements from others, formats them into user stories, and manages Jira without real decision authority or customer understanding.</p><p>That role does not create enough value to justify its existence.</p><p>In the AI era, this point becomes even sharper. AI can help draft user stories, acceptance criteria, release notes, documentation, and test cases. If the PO’s main contribution is manually writing tickets, the role will be increasingly difficult to justify. The PO must move up the value chain: from backlog administration to delivery intelligence.</p><h3>The AI Era Changes the Debate</h3><p>AI changes the PM/PO debate because it changes the economics of product delivery.</p><p>In the traditional world, large teams often needed multiple coordination roles because software development was slower, more manual, and more dependent on specialized handoffs. Product people wrote requirements. Designers produced screens. Engineers coded. QA tested. Release managers coordinated. Analysts measured. Program managers tracked status. Agile roles emerged partly to manage that complexity.</p><p>AI is compressing that model.</p><p>A smaller team can now do what previously required a larger group. A product manager can use AI to synthesize customer interviews. A designer can generate multiple experience concepts. Engineers can use AI coding assistants to accelerate implementation. Test cases, documentation, and release notes can be partially generated. AI agents can support backlog refinement, dependency analysis, research synthesis, and scenario planning.</p><p>This does not eliminate the need for product leadership. It increases the need for it.</p><p>When building becomes faster, deciding what is worth building becomes more important.</p><p>When AI can generate ten solution options, human judgment must decide which one is valuable, ethical, feasible, differentiated, secure, and aligned with strategy.</p><p>When AI can produce backlog items, someone must still ensure those items reflect real customer needs and business outcomes.</p><p>When AI can accelerate delivery, organizations must avoid accelerating waste.</p><p>The bottleneck shifts from development capacity to product judgment, context quality, decision rights, governance, and value measurement.</p><p>That is why I believe the AI era favors <strong>fewer handoffs, smaller empowered teams, stronger product accountability, and clearer ownership of value flow</strong>.</p><p>It does not automatically favor keeping both PM and PO roles.</p><h3>When Both Roles Are Not Needed</h3><p>Many organizations should not have both roles.</p><p>This is especially true for startups, small product teams, early-stage products, internal tools, and AI-native teams where one empowered product leader can remain close to users, strategy, design, engineering, delivery, and measurement.</p><p>In these environments, splitting PM and PO responsibilities often creates unnecessary friction.</p><p>The PM explains strategy to the PO. The PO translates it into backlog items. Engineering asks questions. The PO checks with the PM. The PM checks with stakeholders. By the time a decision is made, the team has lost momentum.</p><p>That may have been tolerable in slower delivery environments. It is unacceptable in AI-accelerated product engineering.</p><p>For a small AI-native team, the best model is often:</p><p><strong>One Product Manager or Product Lead who owns the full product life cycle.</strong></p><p>That person should own discovery, strategy, roadmap, backlog, delivery clarification, release readiness, adoption, and measurement. They should work directly with designers, engineers, users, stakeholders, and AI tools.</p><p>A separate PO is usually not needed when:</p><p>The team is small.<br>The product is early-stage.<br>The PM is close to engineering.<br>The backlog is manageable.<br>The organization needs speed and learning more than formal role separation.<br>The product has limited stakeholder complexity.<br>The PM can make timely product and delivery decisions.<br>AI tools reduce the administrative workload of backlog management.</p><p>In this context, adding a PO often does not create value. It creates a coordination tax.</p><p>The better solution is not another role. The better solution is a stronger Product Manager, better engineering autonomy, clearer product context, better acceptance criteria, and more effective use of AI to reduce administrative work.</p><h3>When Both Roles Are Needed</h3><p>There are also situations where both roles are genuinely useful.</p><p>Large organizations often have complexity that one person cannot manage effectively. A major enterprise product may involve multiple squads, multiple business units, regulatory constraints, legacy systems, customer segments, operational dependencies, security reviews, release trains, data governance, compliance requirements, and executive stakeholders.</p><p>In that environment, expecting one person to own deep customer discovery, product strategy, stakeholder alignment, roadmap prioritization, backlog refinement, sprint-level decisions, acceptance criteria, delivery clarification, release readiness, and outcome measurement across multiple squads is unrealistic.</p><p>In large organizations, the PM/PO split can make sense when it solves a real scale problem.</p><p>The Product Manager focuses on:</p><p>Product strategy<br>Customer and market understanding<br>Business outcomes<br>Investment prioritization<br>Roadmap direction<br>Stakeholder alignment<br>Adoption and value realization</p><p>The Product Owner focuses on:</p><p>Backlog health<br>Story clarity<br>Acceptance criteria<br>Team-level prioritization<br>Sprint and release readiness<br>Delivery decision-making<br>Traceability from backlog to product goals</p><p>This can work well in:</p><p>Large enterprise product organizations<br>Multi-squad product teams<br>Regulated industries<br>Complex B2B platforms<br>Internal enterprise platforms<br>Products with many stakeholder groups<br>Scaled Agile environments<br>Products requiring significant adoption and change management</p><p>But there is a non-negotiable condition: <strong>the PO must have real decision authority and real product context.</strong></p><p>If the PO has no authority, the role becomes a bottleneck.<br>If the PO has no customer understanding, the role becomes a delivery proxy.<br>If the PO has no strategic context, the backlog becomes disconnected from value.<br>If the PM has no delivery understanding, the roadmap becomes fiction.</p><p>Both roles are useful only when they operate as a tightly connected product leadership system.</p><h3>How the Model Should Differ by Organization Size</h3><p>The right answer depends heavily on organizational size and complexity.</p><h3>Small Organizations and Startups</h3><p>Small organizations usually do not need both PM and PO roles.</p><p>They need one strong, hands-on Product Manager or Product Lead who can move quickly from problem discovery to prototype to release to learning.</p><p>In small teams, every additional role creates communication overhead. The priority should be speed, customer intimacy, direct collaboration, and rapid learning.</p><p>Recommended model:</p><p>One Product Manager / Product Lead<br>One designer or product design engineer<br>One to three AI-augmented engineers<br>Shared accountability for outcomes<br>Minimal process<br>Direct customer feedback loops<br>AI-assisted research, prototyping, coding, testing, and documentation</p><p>The Product Manager should perform PO responsibilities directly. The backlog should not be outsourced because the backlog is where product strategy becomes real.</p><h3>Medium-Sized Organizations</h3><p>Medium-sized organizations need a more nuanced model.</p><p>They may not need a formal PO title for every team, but they may need delivery support as product complexity grows.</p><p>Recommended model:</p><p>One Product Manager owns strategy, roadmap, outcomes, and stakeholder alignment.<br>A Product Owner, Senior Business Analyst, or Delivery Product Lead supports backlog refinement and team-level delivery if needed.<br>The PM retains accountability for product value.<br>The PO or delivery support role owns backlog clarity but does not become a wall between the PM and engineering.</p><p>In medium-sized organizations, the biggest risk is premature role specialization. The company adds a PO because it feels more mature, but the result is slower decision-making.</p><p>The test should be simple:</p><p>Is the PO removing work from the PM that was genuinely limiting value flow?<br>Is the PO helping the team move faster with better clarity?<br>Is the PO connected to the product strategy?<br>Is the PM still close to delivery reality?</p><p>If the answer is yes, the role may be useful. If not, it is overhead.</p><h3>Large Organizations</h3><p>Large organizations are where both roles are most likely to be justified.</p><p>But large organizations also suffer the most from role confusion.</p><p>Recommended model:</p><p>Product Managers own product strategy, business outcomes, portfolio alignment, customer understanding, roadmap priorities, and value realization.<br>Product Owners are embedded with squads and own backlog execution, delivery clarity, and acceptance criteria.<br>Each PO is aligned to a PM or product area.<br>Decision rights are documented.<br>PMs and POs share customer exposure.<br>Delivery work is traceable to product goals and business outcomes.<br>Both roles are measured against value, not just output.</p><p>In large organizations, POs should not be treated as junior PMs or ticket managers. They are critical delivery leaders. But they must not become disconnected from strategy.</p><p>Similarly, PMs should not be allowed to float above delivery. They must understand what is being built, why it is hard, what trade-offs are being made, and whether the delivered increment will create measurable value.</p><h3>Decision Rights Matter More Than Titles</h3><p>Most PM/PO confusion comes from unclear decision rights.</p><p>If both roles exist, the organization must explicitly define who decides what.</p><p>Here is a practical model:</p><p>DecisionOwnerProduct visionProduct ManagerProduct strategyProduct ManagerBusiness case and investment prioritiesProduct ManagerProduct roadmapProduct ManagerProduct backlogProduct Owner, within PM strategic guardrailsSprint-level prioritizationProduct OwnerAcceptance criteriaProduct Owner, with input from PM, design, engineering, and usersRelease scopeProduct Manager and Product Owner togetherFinal business trade-offsProduct ManagerAcceptance of completed workProduct OwnerCustomer and business outcomesProduct ManagerDelivery clarity and backlog readinessProduct OwnerProduct value realizationProduct Manager, with PO contribution</p><p>The key is that <strong>strategic accountability cannot be separated from delivery consequences</strong>, and <strong>delivery decisions cannot be separated from product value</strong>.</p><p>That is where many organizations fail.</p><p>They give the PM the roadmap and the PO the backlog, then wonder why the roadmap and backlog diverge.</p><p>They measure PMs on outcomes and POs on velocity, then wonder why the team ships things that do not move the business.</p><p>They tell POs they own the backlog but give stakeholders permission to override priorities.</p><p>They tell PMs they own strategy but do not require them to participate in delivery reviews or customer feedback loops.</p><p>This is not a role problem. It is an operating-model problem.</p><h3>The Product Life Cycle View</h3><p>The product life cycle is the best way to understand where each role contributes.</p><p>Product Life Cycle StageProduct ManagerProduct OwnerDiscoveryLeads customer, market, and problem discoverySupports with feasibility and delivery insightStrategyDefines product vision, positioning, and outcome goalsProvides delivery and technical inputBusiness caseOwns value hypothesis, investment logic, and success metricsSupports effort, risk, and dependency analysisRoadmapOwns strategic sequencing and stakeholder alignmentHelps translate roadmap into epics and delivery slicesSolution designCo-leads with design and engineeringCo-leads with PM, design, and engineeringBacklog creationProvides strategic context and prioritiesOwns backlog structure, stories, and acceptance criteriaDeliveryStays close to trade-offs and risksLeads delivery clarification and team-level decisionsRelease planningOwns market, stakeholder, and adoption readinessOwns delivery readiness and acceptance traceabilityAdoptionLeads adoption strategy and business changeSupports enablement, documentation, and feedback loopsMeasurementOwns outcome measurement and value realizationConnects delivery results to learning and iterationContinuous improvementLeads product learning and strategic adjustmentsLeads backlog updates and delivery refinementRetirementOwns strategic decision to retire or replaceSupports technical decommissioning and transition</p><p>The pattern is clear.</p><p>The PM leads the outer loop: discovery, strategy, value, adoption, and outcomes.</p><p>The PO leads the inner loop: backlog, delivery clarity, acceptance, and execution flow.</p><p>In small teams, one person can often own both loops.</p><p>In large teams, separating the loops may be necessary — but only if they remain tightly connected.</p><h3>The Anti-Patterns to Eliminate</h3><p>Whether your organization has one role or both, these anti-patterns must be eliminated.</p><h3>1. The PowerPoint Product Manager</h3><p>This PM owns strategy in theory but is disconnected from customers, engineering, and delivery reality. They create roadmaps and executive decks but do not understand what is actually being built or whether it works.</p><h3>2. The Backlog Secretary Product Owner</h3><p>This PO writes tickets, formats requirements, and manages Jira but has no authority, no customer context, and no ability to make meaningful prioritization decisions.</p><h3>3. The Proxy Product Owner</h3><p>This PO becomes the person stakeholders pressure when they want work inserted into the backlog. Instead of protecting value flow, the PO becomes a demand intake channel.</p><h3>4. The Disconnected Roadmap</h3><p>The PM owns a roadmap of themes and priorities. The PO owns a backlog of stories and defects. Nobody can clearly explain how backlog items connect to strategic outcomes.</p><h3>5. The Velocity Trap</h3><p>The PO is measured on sprint velocity and throughput while the PM is measured on business value. The team becomes excellent at shipping but weak at learning.</p><h3>6. The AI-Speed Illusion</h3><p>The organization adopts AI tools and accelerates coding, but leaves decision-making, approvals, governance, prioritization, and stakeholder alignment unchanged. The result is faster output, not faster value.</p><p>This last anti-pattern will become increasingly common. AI can make teams faster, but if the organization does not improve product judgment, it will simply build the wrong things faster.</p><h3>The New AI-Native Product Role</h3><p>In the AI era, we may see a new blended role emerge: the <strong>AI-native Product Lead</strong> or <strong>Product Engineer</strong>.</p><p>This person may combine product thinking, customer insight, design judgment, technical fluency, AI prompting, prototyping ability, and delivery leadership. Manus highlights the rise of the Product Engineer and argues that AI is reducing the need for intermediaries in smaller, AI-empowered teams.</p><p>This does not mean every PM must become a software engineer. But it does mean product leaders must become more technically fluent and more hands-on with AI-enabled creation.</p><p>The future product leader should be able to:</p><p>Frame the right problem<br>Use AI to accelerate research synthesis<br>Generate and evaluate solution options<br>Collaborate directly with AI-augmented engineers<br>Draft clear product requirements and acceptance criteria<br>Prototype ideas faster<br>Validate with users earlier<br>Measure outcomes continuously<br>Understand data, architecture, security, and operational constraints<br>Make faster trade-off decisions</p><p>In this model, the old PM/PO split becomes less relevant for small teams.</p><p>The more important question becomes:</p><p><strong>Can this product leader move from insight to shipped value without unnecessary translation layers?</strong></p><p>If yes, do not add a PO.</p><p>If no, add delivery support — but only to improve value flow, not to satisfy a framework.</p><h3>A Practical Decision Test</h3><p>Before deciding whether to have both roles, organizations should ask seven questions:</p><ol><li>Is one person able to own product strategy and delivery clarity without becoming a bottleneck?</li><li>Is the product complex enough to require separate strategic and tactical product leadership?</li><li>Are there multiple squads requiring dedicated backlog ownership?</li><li>Does the PO have real authority, or are they just translating someone else’s decisions?</li><li>Is the PM close enough to delivery to understand trade-offs and constraints?</li><li>Does the backlog clearly trace back to product goals and business outcomes?</li><li>Would adding or removing the PO role make the product life cycle faster, clearer, and more value-driven?</li></ol><p>If the answer to the last question is no, the role should not exist in its current form.</p><h3>My Recommended Model</h3><p>Here is the model I would recommend for most organizations.</p><h3>For Small Organizations</h3><p>Do not split PM and PO.</p><p>Use one empowered Product Manager / Product Lead who owns the full product life cycle. Use AI to reduce administrative burden. Keep the team small, fast, and close to users.</p><h3>For Medium Organizations</h3><p>Start with one Product Manager accountable for outcomes. Add a PO, Business Analyst, or Delivery Product Lead only when backlog complexity starts slowing the team.</p><p>Make the role clearly subordinate to product value, not process compliance.</p><h3>For Large Organizations</h3><p>Use both roles when scale and complexity justify it.</p><p>But define decision rights clearly. Ensure PMs and POs share context, customer understanding, and accountability for outcomes. Do not allow PMs to become strategy-only and POs to become backlog-only.</p><h3>For AI-Native Product Teams</h3><p>Default to fewer roles.</p><p>Use AI to eliminate administrative work, not to create more process. Prioritize direct collaboration, fast validation, product judgment, and value measurement.</p><p>The AI-native model should not be:</p><p>PM writes strategy.<br>PO writes stories.<br>Engineer prompts AI.<br>QA tests output.<br>Stakeholders review later.</p><p>It should be:</p><p>Small empowered team.<br>Clear product outcome.<br>Fast AI-assisted prototyping.<br>Direct user feedback.<br>Rapid iteration.<br>Continuous measurement.<br>One product truth.</p><h3>Final Conclusion: Do Not Organize Around Roles. Organize Around Value Flow.</h3><p>The Product Manager and Product Owner distinction is useful only when it helps the organization manage complexity without slowing down value creation.</p><p>If the split creates clarity, speed, better prioritization, stronger delivery, and measurable product outcomes, keep both roles.</p><p>If the split creates handoffs, duplicated meetings, diluted accountability, disconnected roadmaps, and backlog administration, remove the split.</p><p>In the AI-accelerated product life cycle, organizations should be even more ruthless about this. AI reduces the need for large teams and heavy coordination. It increases the need for sharp product judgment, strong customer insight, clear business outcomes, and fast decision-making.</p><p>The winning organizations will not be the ones with the most complete role taxonomy.</p><p>They will be the ones with the clearest answers to these questions:</p><p>What problem are we solving?<br>Why does it matter?<br>Who is accountable for value?<br>Who is accountable for delivery clarity?<br>How fast can we learn?<br>How do we know whether we created measurable impact?<br>What roles are helping that flow — and what roles are slowing it down?</p><p>Sometimes the answer is one strong Product Manager.</p><p>Sometimes the answer is a Product Manager and Product Owner working as a tightly connected pair.</p><p>Sometimes the answer is an AI-native Product Lead supported by a small team of product engineers.</p><p>The title matters less than the accountability.</p><p>The product life cycle does not need more roles.</p><p>It needs fewer gaps between insight, decision, delivery, adoption, and value.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4569d54353e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why IBM Garage Is the Ideal Operating Model for Forward Deployment Engineering]]></title>
            <link>https://melrefai.medium.com/why-ibm-garage-is-the-ideal-operating-model-for-forward-deployment-engineering-5fa016684c5b?source=rss-94a0b35df7ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/5fa016684c5b</guid>
            <category><![CDATA[ai-factory]]></category>
            <category><![CDATA[business-value]]></category>
            <category><![CDATA[forward-deployed-engineer]]></category>
            <category><![CDATA[ibm-garage]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Dr. Mohamed El-Refai]]></dc:creator>
            <pubDate>Thu, 21 May 2026 02:51:47 GMT</pubDate>
            <atom:updated>2026-05-21T02:52:54.405Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iTE2KQo0-tEQboJIWKBn1A.png" /><figcaption>IBM Garage Ideal for FDE</figcaption></figure><p>The rise of AI-native software development is reshaping how enterprises deliver technology. Traditional delivery models — characterized by lengthy requirements gathering, siloed teams, and delayed value realization — are increasingly unable to keep pace with the demands of modern organizations.</p><p>At the same time, a new engineering paradigm has emerged: <strong>Forward Deployment Engineering (FDE)</strong>.</p><p>Popularized by leading AI and data companies, Forward Deployment Engineering emphasizes:</p><ul><li>embedding engineering teams close to users,</li><li>rapidly iterating in production environments,</li><li>solving real-world business problems directly,</li><li>and continuously adapting solutions based on live feedback.</li></ul><p>While many organizations are only now discovering FDE, IBM has already established an operating model that naturally aligns with these principles:</p><p><strong>IBM Garage.</strong></p><p>IBM Garage is not simply a workshop methodology or innovation framework. When implemented correctly, it is a complete business and technology transformation operating model that embodies the core principles required for modern Forward Deployment Engineering at enterprise scale.</p><h3>What Is Forward Deployment Engineering?</h3><p>Forward Deployment Engineering is fundamentally about collapsing the distance between:</p><ul><li>strategy and execution,</li><li>users and engineers,</li><li>ideation and deployment,</li><li>and technology delivery and measurable business value.</li></ul><p>Rather than throwing requirements over organizational walls, Forward Deployment teams:</p><ul><li>work directly with users,</li><li>rapidly prototype,</li><li>deploy continuously,</li><li>adapt solutions in real time,</li><li>and measure success based on adoption and outcomes.</li></ul><p>The focus shifts from:</p><ul><li>“building software”<br> to:</li><li>“solving business problems rapidly.”</li></ul><p>This is precisely where IBM Garage excels.</p><h3>IBM Garage Already Operates Like an Elite FDE Model</h3><p>The strongest Forward Deployment organizations in the world share several characteristics:</p><ul><li>cross-functional squads,</li><li>close customer collaboration,</li><li>iterative delivery,</li><li>rapid experimentation,</li><li>embedded design,</li><li>engineering autonomy,</li><li>and outcome-based measurement.</li></ul><p>IBM Garage operationalizes all of these.</p><p>Its modern lifecycle:</p><ul><li>Discover</li><li>Co-create</li><li>Co-execute</li><li>Co-operate</li></ul><p>creates a continuous feedback-driven delivery engine that mirrors the ideal Forward Deployment lifecycle.</p><p>The IBM Garage Methodology — <a href="http://ibm.biz/garageGAP">http://ibm.biz/garageGAP</a></p><h3>Discover: Aligning Engineering to Business Outcomes</h3><p>One of the biggest failures in traditional delivery is that engineering teams often begin building before alignment exists around:</p><ul><li>strategic priorities,</li><li>measurable outcomes,</li><li>success metrics,</li><li>or organizational readiness.</li></ul><p>IBM Garage’s <strong>Discover</strong> phase addresses this directly.</p><p>This phase aligns:</p><ul><li>executive stakeholders,</li><li>business leaders,</li><li>architects,</li><li>designers,</li><li>engineers,</li><li>and operational teams</li></ul><p>around:</p><ul><li>strategic initiatives,</li><li>target outcomes,</li><li>measurable KPIs,</li><li>and transformation priorities.</li></ul><p>This is critical in Forward Deployment Engineering because FDE teams must deeply understand:</p><ul><li>why the solution matters,</li><li>who benefits,</li><li>and what measurable business impact success creates.</li></ul><p>Without this alignment, engineering acceleration only accelerates waste.</p><h3>Co-create: Embedded UX + Engineering Collaboration</h3><p>Modern Forward Deployment Engineering is not purely engineering.</p><p>The best solutions emerge when:</p><ul><li>designers,</li><li>product thinkers,</li><li>users,</li><li>and engineers</li></ul><p>work together continuously.</p><p>IBM Garage’s <strong>Co-create</strong> phase operationalizes this collaboration.</p><p>This phase focuses on:</p><ul><li>value framework development,</li><li>pain point validation,</li><li>user research,</li><li>solution ideation,</li><li>opportunity prioritization,</li><li>and hypothesis-driven design.</li></ul><p>Importantly, this is not theoretical planning.</p><p>It is collaborative product shaping grounded in real user behavior.</p><p>This mirrors how elite FDE teams operate:</p><ul><li>rapid prototypes,</li><li>live user feedback,</li><li>iterative refinement,</li><li>and continuous validation.</li></ul><p>The inclusion of embedded UX within Garage is especially important.</p><p>Many engineering organizations fail not because the technology is weak, but because:</p><ul><li>adoption is low,</li><li>workflows are unintuitive,</li><li>or solutions fail to align with human behavior.</li></ul><p>IBM Garage prevents this by integrating design thinking directly into delivery.</p><h3>Co-execute: The Heart of Forward Deployment Engineering</h3><p>This is where IBM Garage becomes exceptionally aligned to modern FDE practices.</p><p>The <strong>Co-execute</strong> phase combines:</p><ul><li>Agile delivery,</li><li>DevSecOps,</li><li>joint squads,</li><li>rapid iteration,</li><li>continuous testing,</li><li>and collaborative engineering.</li></ul><p>This phase closely resembles the operating structure of elite Forward Deployment organizations.</p><p>The emphasis is on:</p><ul><li>iterative build/test/release cycles,</li><li>direct stakeholder engagement,</li><li>rapid adaptation,</li><li>and deployment acceleration.</li></ul><p>Modern AI-native development tools make this even more powerful.</p><p>Today’s Forward Deployment teams increasingly leverage:</p><ul><li>Cursor,</li><li>Claude Code by Anthropic,</li><li>OpenAI Codex,</li><li>Gemini Code Assist,</li><li>AI-assisted testing,</li><li>and agentic development workflows.</li></ul><p>These tools dramatically compress engineering timelines.</p><p>But tools alone are insufficient.</p><p>Without an operating model that supports:</p><ul><li>rapid iteration,</li><li>embedded collaboration,</li><li>continuous feedback,</li><li>and deployment autonomy,</li></ul><p>AI acceleration becomes fragmented.</p><p>IBM Garage provides the governance and delivery structure necessary to harness AI-native engineering effectively.</p><h3>Co-operate: Where Most FDE Models Are Weak</h3><p>Many Forward Deployment Engineering organizations focus heavily on:</p><ul><li>rapid deployment,</li><li>prototypes,</li><li>and short-term delivery.</li></ul><p>But enterprise transformation requires more than rapid shipping.</p><p>It requires:</p><ul><li>operationalization,</li><li>governance,</li><li>scaling,</li><li>adoption management,</li><li>and continuous optimization.</li></ul><p>IBM Garage’s <strong>Co-operate</strong> phase addresses this directly.</p><p>This phase focuses on:</p><ul><li>hardening solutions,</li><li>scaling operations,</li><li>governance,</li><li>change management,</li><li>measurable adoption,</li><li>continuous improvement,</li><li>and sustained value realization.</li></ul><p>This is one of IBM Garage’s greatest differentiators.</p><p>It recognizes that:</p><p>technology deployment is not the finish line.</p><p>Business adoption is.</p><h3>Why AI Changes the Importance of IBM Garage</h3><p>The emergence of generative AI and AI-assisted software development is increasing the speed of engineering dramatically.</p><p>Small teams can now produce:</p><ul><li>prototypes,</li><li>integrations,</li><li>workflows,</li><li>dashboards,</li><li>and applications</li></ul><p>at speeds previously impossible.</p><p>This creates a new challenge:</p><ul><li>organizations can now build faster than they can govern, prioritize, or operationalize.</li></ul><p>This is exactly why IBM Garage becomes even more important in the AI era.</p><p>IBM Garage introduces:</p><ul><li>alignment,</li><li>prioritization,</li><li>governance,</li><li>value orchestration,</li><li>and measurable outcome tracking</li></ul><p>into AI-native delivery.</p><p>Without this structure, organizations risk:</p><ul><li>AI chaos,</li><li>fragmented experimentation,</li><li>duplicated solutions,</li><li>low adoption,</li><li>and unclear ROI.</li></ul><h3>IBM Garage + AI-Native Engineering = Enterprise AI Factory</h3><p>The future of enterprise technology delivery is likely to combine:</p><ul><li>AI-native software development,</li><li>autonomous engineering squads,</li><li>embedded UX,</li><li>continuous deployment,</li><li>and measurable business outcomes.</li></ul><p>IBM Garage already provides the foundational operating model required for this future.</p><p>When combined with:</p><ul><li>AI-assisted engineering,</li><li>platform engineering,</li><li>agentic development,</li><li>and modern Forward Deployment practices,</li></ul><p>IBM Garage becomes:</p><p>an enterprise-scale AI Factory operating model.</p><p>One capable of:</p><ul><li>rapidly converting ideas into production solutions,</li><li>aligning delivery to business value,</li><li>scaling innovation safely,</li><li>and sustaining measurable transformation outcomes.</li></ul><h3>Final Thoughts</h3><p>Forward Deployment Engineering is not simply a new engineering role.</p><p>It represents a broader shift toward:</p><ul><li>customer-embedded delivery,</li><li>continuous iteration,</li><li>rapid experimentation,</li><li>and outcome-driven engineering.</li></ul><p>IBM Garage is uniquely positioned to operationalize these principles at enterprise scale because it already combines:</p><ul><li>strategy,</li><li>design,</li><li>engineering,</li><li>operations,</li><li>governance,</li><li>and value realization</li></ul><p>into a unified transformation model.</p><p>As AI continues accelerating software delivery, organizations will increasingly discover that:</p><ul><li>engineering speed alone is not enough,</li><li>AI tools alone are not enough,</li><li>and rapid prototyping alone is not enough.</li></ul><p>The true differentiator will be:</p><p>the ability to continuously align technology delivery to measurable business value.</p><p>That is exactly where IBM Garage excels.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5fa016684c5b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How IBM Garage & IGX Are Able To Transform Venture Capital]]></title>
            <link>https://melrefai.medium.com/how-ibm-garage-igx-are-able-to-transform-venture-capital-b6c891e82821?source=rss-94a0b35df7ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/b6c891e82821</guid>
            <category><![CDATA[vc]]></category>
            <category><![CDATA[ibm-garage-experience-igx]]></category>
            <category><![CDATA[ibm-garage]]></category>
            <dc:creator><![CDATA[Dr. Mohamed El-Refai]]></dc:creator>
            <pubDate>Mon, 23 Feb 2026 08:24:43 GMT</pubDate>
            <atom:updated>2026-02-23T08:26:17.906Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Surfacing High-Potential Opportunities &amp; De-Risking ROI at Scale</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KWN53RkTrBxcOlK6LMQ3iQ.png" /><figcaption>A New Venture Capital Model</figcaption></figure><p>In today’s venture capital landscape, the challenge is no longer access to opportunities — it’s identifying the right opportunities early and scaling them with confidence.</p><p>Too many investments fail not because lack of capital — but due to:</p><p><em>- Weak problem-solution fit</em></p><p><em>- Invalidated assumptions</em></p><p><em>- Poor execution discipline</em></p><p><em>- Lack of measurable value realization</em></p><p>What if VCs could systematically reduce these risks while increasing upside potential?</p><p>This is where concepts from IBM Garage and the IBM Garage Experience (IGX) platform offer a powerful, yet underutilized, advantage.</p><h3><strong>🔍 The Core Problem in Venture Capital</strong></h3><p>Traditional VC models rely heavily on:</p><p><em>- Founder narratives</em></p><p><em>- Market signals</em></p><p><em>- Pattern recognition</em></p><p><em>- Portfolio diversification</em></p><p>While effective, these approaches:</p><p><em>- Are reactive rather than experimental</em></p><p><em>- Lack structured hypothesis validation</em></p><p><em>- Provide limited real-time visibility into value realization</em></p><p>The result?</p><p>👉 High variance in outcomes</p><p>👉 Late discovery of failure signals</p><p>👉 Capital inefficiency</p><h3><strong>🧠 Enter IBM Garage: A Startup Operating System at Enterprise Scale</strong></h3><p>IBM Garage is a collaborative, value-driven methodology that integrates:</p><p><em>- Lean Startup</em></p><p><em>- Value Orchestration</em></p><p><em>- Enterprise Design Thinking</em></p><p><em>- Lean UX</em></p><p><em>- Enterprise Agility + DevSecOps</em></p><p><em>- Continuous value tracking</em></p><p>It is specifically designed to:</p><p><em>- Rapidly test ideas through MVPs</em></p><p><em>- Validate assumptions early</em></p><p><em>- Scale only what proves value</em></p><p>Critically, it enables organizations to go from idea → MVP → measurable outcomes in weeks, not months</p><p>And more importantly — it is built to de-risk innovation through:</p><p><em>- Hypothesis-driven development</em></p><p><em>- Continuous user validation</em></p><p><em>- Iterative delivery cycles</em></p><h3><strong>💡 Why This Matters for Venture Capital</strong></h3><p>If you reframe a startup as:</p><p><em>👉 “A portfolio of unvalidated hypotheses”</em></p><p>Then IBM Garage provides:</p><p><em>👉 “A structured engine to validate or kill those hypotheses early”</em></p><p>🔑<strong> Key Shift:</strong></p><p>From investing in ideas → to investing in validated outcomes</p><h3>⚙️ <strong>IGX: The Missing Link for VC Decision Intelligence</strong></h3><blockquote>While IBM Garage provides the method, IBM Garage Experience (IGX) provides the visibility and governance layer.</blockquote><p><strong>IGX enables:</strong></p><p><em>+ Real-time tracking of value at feature level</em></p><p><em>+ Visibility into delivery health, blockers, and throughput</em></p><p><em>+ Alignment of initiatives to business outcomes and ROI</em></p><p>It allows stakeholders to:</p><p><em>👉 “Understand which efforts are contributing the most return”</em></p><p>And even:</p><p><em>👉 Identify new value opportunities in minutes using AI-assisted insights</em></p><h3>🧩 <strong>Applying IBM Garage + IGX to the VC Lifecycle</strong></h3><ol><li><strong>🔎 Deal Sourcing → Structured Opportunity Discovery</strong></li></ol><p>Instead of relying only on pitch decks:</p><p>Use Garage principles to:</p><p><em>&gt; Map customer pain points</em></p><p><em>&gt; Build value trees (problem → value lever → value driver → value pool)</em></p><p><em>&gt; Identify high-impact opportunities</em></p><p>💡<strong> Outcome:</strong></p><p><em>+ VCs can prioritize startups based on validated problem significance, not just storytelling.</em></p><p><strong>2. 🧪 Due Diligence → Hypothesis-Based Validation</strong></p><p>Replace static due diligence with:</p><p><em>&gt; Rapid MVP experiments</em></p><p><em>&gt; Customer validation loops</em></p><p><em>&gt; Early product-market fit signals</em></p><p>💡 Outcome:</p><p><em>+ Faster “go / no-go” decisions</em></p><p><em>+ Reduced false positives</em></p><p><strong>3. 🚀 Post-Investment → Accelerated Value Creation</strong></p><p>Deploy Garage squads with portfolio companies to:</p><p><em>&gt; Define MVP scope aligned to value</em></p><p><em>&gt; Iterate using Agile + DevSecOps</em></p><p><em>&gt; Continuously measure adoption</em></p><p>💡 Outcome:</p><p><em>+ Faster time-to-market</em></p><p><em>+ Stronger execution discipline</em></p><p><strong>4. 📊 Portfolio Management → Real-Time Value Tracking</strong></p><p>Leverage IGX to:</p><p><em>&gt; Track ROI at initiative and feature level</em></p><p><em>&gt; Monitor portfolio health in real-time</em></p><p><em>&gt; Identify underperforming investments early</em></p><p>💡 Outcome:</p><p><em>+ Active portfolio optimization</em></p><p><em>+ Data-driven capital allocation</em></p><p><strong>5. 📈 Exit Strategy → Proven Value Narratives</strong></p><p>With IGX-backed data:</p><p><em>&gt; Value realization is quantified and traceable</em></p><p><em>&gt; Growth stories are backed by measurable metrics</em></p><p>💡 Outcome:</p><p><em>+ Stronger valuation multiples</em></p><p><em>+ More credible exit narratives</em></p><h3><strong>📉 Quantifying the Impact: Risk Reduction &amp; ROI Uplift</strong></h3><p>By applying IBM Garage + IGX, VCs can:</p><p>Reduce Risk Through:</p><p><em>+ Early hypothesis validation</em></p><p><em>+ Continuous user feedback</em></p><p><em>+ Built-in DevSecOps and scalability practices</em></p><p>Increase ROI Through:</p><p><em>+ Faster time-to-value</em></p><p><em>+ Focus on high-impact opportunities</em></p><p><em>+ Continuous value realization tracking</em></p><p>Real-world Garage engagements have demonstrated the ability to:</p><p><em>👉 Move from idea to working solutions in weeks</em></p><p><em>👉 Achieve multi-fold ROI (up to 7–10x in some cases) through validated outcomes</em></p><h3><strong>🔄 The New VC Operating Model</strong></h3><p><strong>Traditional VC Model:</strong></p><p><em>Invest → Wait → Hope → Exit</em></p><p><strong>Garage-Enabled VC Model:</strong></p><p><em>Discover → Validate (Co-create) → Build → Measure (Co-execute) → Scale (Co-operate)</em></p><h3>🧭 Final Thoughts</h3><p>The future of venture capital will not be defined by:</p><ul><li><em>Who has the most capital</em></li><li><em>Or who sees the most deals</em></li></ul><p>It will be defined by:</p><blockquote>👉 Who can systematically validate, scale, and realize value faster than others</blockquote><p>IBM Garage and IGX offer:</p><p><em>+ A repeatable innovation engine</em></p><p><em>+ A data-driven investment lens</em></p><p><em>+ A risk-reduction framework embedded into execution</em></p><p>For VCs willing to evolve, this is more than a methodology —</p><blockquote>👉 It is a competitive advantage in an increasingly uncertain market</blockquote><h3>💬 Reach Out and Let’s Discuss</h3><p>How are you currently:</p><p><em>? Validating opportunities pre-investment?</em></p><p><em>? Tracking value realization post-investment?</em></p><p>And more importantly:</p><p><em>👉 What would change if your portfolio operated like a continuous MVP factory with real-time value intelligence?</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b6c891e82821" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Business Initiative vs. Business Opportunity]]></title>
            <link>https://melrefai.medium.com/business-initiative-vs-business-opportunity-7ed545865589?source=rss-94a0b35df7ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/7ed545865589</guid>
            <category><![CDATA[business-opportunities]]></category>
            <category><![CDATA[business-initiative]]></category>
            <category><![CDATA[problem-hypothesis]]></category>
            <category><![CDATA[pain-points]]></category>
            <category><![CDATA[ibm-garage]]></category>
            <dc:creator><![CDATA[Dr. Mohamed El-Refai]]></dc:creator>
            <pubDate>Tue, 31 Aug 2021 23:59:13 GMT</pubDate>
            <atom:updated>2021-09-01T14:51:22.442Z</atom:updated>
            <content:encoded><![CDATA[<p>In the past two years I came across a lot of confusion where our IBM Garage practitioners use the word “initiative” to represent what we usually work on in an IBM Garage.</p><p>Here is a brief definition of what a business initiative is:</p><blockquote>“Business initiatives are typically internal or external campaigns that seek to improve an organization’s work environment, company culture or overall business strategy.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aEt4XNrXeU7iVG71ikpOfQ.png" /><figcaption>What is a business initiative?</figcaption></figure><p>I would describe a business initiative as <strong><em>the approach organizations use to frame their objectives based on deep analysis of their current state and where they expect their ideal state to be in the future.</em></strong></p><p>I would also say that <strong><em>IBM Garage is IBM’s way to realize these business initiatives for our clients.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3mfnRrf9byHfxyAcmAYq0g.png" /><figcaption><strong><em>IBM Garage is IBM’s way to realize these business initiatives for our clients</em></strong></figcaption></figure><p>We partner with our clients to understand their <strong><em>value drivers</em></strong> which form the foundation of their <strong><em>business initiatives</em></strong>. We dig deeper to surface <strong><em>pain points</em></strong> that are inhibiting these value drivers and from that identify possible <strong><em>business opportunities</em></strong> that can address some of these pain points. <strong><em>The value generated from these business opportunities have to align with the organizational business initiatives.</em></strong></p><p>So here you see why <strong><em>I call what we work on in IBM Garage as business opportunities and not business initiatives. </em></strong>We for sure align with business initiatives so the effort of the entire Garage could help a client achieve their business initiatives, but not one business opportunity by itself.</p><p>A business opportunity will go through different states in an IBM Garage and will be acted on by different roles to progress it from an idea to a full-fledged product, here are some of these states as we define them in IBM Garage: Drafted, Proposed, Reviewed, Queued, Approved, In Flight and finally Launched.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-5Nqh6oZJ6GajgVBhvRtJw.png" /><figcaption>States for a Business Opportunity</figcaption></figure><p>When the Garage starts in Co-create we start by <strong><em>conducting research</em></strong> to identify pain points that would frame our scope and help us narrow down our focus to key problems we could take on. So basically when we are looking at what to do in IBM Garage we are starting by<strong><em> identifying a business problem </em></strong>based on <strong><em>pain point observation</em></strong> that are observed by our researchers. We collaborate with our clients on defining these problem statements by applying <strong><em>Enterprise Design Thinking </em></strong>practices in a workshop we call the <strong><em>Business Opportunity Envisioning Workshop</em></strong>. During that workshop we review the facts from our research and draw the existing user scenarios to identify inefficiencies or opportunities for improvement. We would <strong><em>brain storm</em></strong> on the various areas we can improve, <strong><em>frame the top ideas as business opportunities</em></strong>, prioritize these and validate the top ideas with <strong><em>sponsor users</em></strong>. As we validate the <strong><em>problem hypothesis</em></strong>, and learn more about all aspects of the business opportunity we would usually <strong><em>frame it into more details using a Business Opportunity Canvas</em></strong> consisting of 16 dimensions that cover every part of the business opportunity and is used to present the business opportunity to the <strong><em>IBM Garage Board</em></strong> to get their approval.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zgsqdiVbRt2ll4gN3Y5KzA.png" /><figcaption>Business Opportunities address pain points</figcaption></figure><p>Under that business opportunity we could form several problem hypotheses that we would then validate with sponsor users. Some of these would be proven inconsiderable and would be ignored, some of these would be considerable and would warrant solving.</p><p>Following Lean Startup practices we would prototype some of these business problems through what we call a Golden Thread. <strong><em>The Golden Thread allows us to communicate a common understanding of the problem hypothesis and possible solutions that could eliminate that problem completely or partially.</em></strong> These solutions are considered <strong><em>features of a product that we would incorporate in an MVP</em></strong> to prove in the market, before we <strong><em>scale them in the actual product</em></strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fjZiz7iG2qRdEwsF_GKR6A.png" /><figcaption>Business Opportunities, Features, MVPs and Product</figcaption></figure><blockquote><strong>So in short one business initiative could be realized of several business opportunities that are coherent in nature. And each of these business opportunities could be realized through MVPs that validate their applicability to the market. The most important aspect is the business value generated and that is what we use to measure ROI for the business initiative as a collation of the ROI form each of its business opportunities.</strong></blockquote><p>Before I close, let me also shed a different light on this prominent confusion. I am not saying that IBM Garage can’t work on business initiatives, for sure <strong><em>IBM Garage can be also used to help clients identify the business initiatives they need to work on to achieve their ideal state</em></strong>, but I would say the <strong><em>key value of an IBM Garage is tackling these business initiatives and realizing quantifiable business value for our clients by realizing business opportunities that make up these business initiatives.</em></strong></p><p>Let me know in your comments what you think about my point of views on Business Initiatives and Business Opportunities, and the key value of IBM Garage.</p><p>Learn more at <a href="http://www.ibm.com/garage">ibm.com/garage</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ed545865589" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stop Controlling, Start Helping!]]></title>
            <link>https://melrefai.medium.com/stop-controlling-start-helping-e6b2478f7383?source=rss-94a0b35df7ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6b2478f7383</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[ibm-garage]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Dr. Mohamed El-Refai]]></dc:creator>
            <pubDate>Mon, 07 Jun 2021 13:51:44 GMT</pubDate>
            <atom:updated>2021-06-07T13:51:44.465Z</atom:updated>
            <content:encoded><![CDATA[<p>It is common to see leadership introducing measures and procedures to make them feel in control. But is that needed or even useful? In this blog I will review several of these measures and in my opinion the value and drawbacks that these measures introduce. I will also introduce what are better <a href="https://ibm.com/garage">IBM Garage</a> practices that should be followed to empower and motivate teams.</p><h3>Leadership measures that hinder teams</h3><p>One of these measures is weekly <strong>review meetings</strong>. Usually the leader in this case is so far from the effort being executed and that is why they ask for these meetings. The impact of such a measure is that the team will focus on this review week to week instead of the actual work they are supposed to be performing. The result is that the team’s efficiency will be impeded and the team goal changes from achieving their iteration targets to pleasing the leader.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ifO_9YSWic-FnsKGC1TWXg.png" /><figcaption>Weekly executive reviews distract the team from their daily activities</figcaption></figure><p>Another measure popular with leadership is asking for <strong>detailed requirements</strong> in the hopes that this will govern scope. If the team is really working in an agile manner, they have progressed by defining epics and user stories, and to bring that back to requirements they will have to perform reverse engineering. Given they already have defined the solution by the time they get this request, they will end up creating system requirements instead of business requirements. The impact is that we will not be able to control the scope given the requirements are at the solution level instead of business. Another impact is that it gives us a false sense of control, change is backed into agile iteration planning so it is counter productive to try to control the scope. This will also impact the team’s productivity as they will be wasting time on unproductive work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GKnWwkYOnhPKaMa_PU8qMw.png" /><figcaption>Detailed requirements and detailed documentation give a false sense of scope control</figcaption></figure><p>Another measure is asking teams to create test reports or <strong>any kind of report</strong>. If the tools the team are using to perform testing are not able to capture all the activities they are doing, then they invest in better tools instead of spending effort on creating a report manually that will be looked at once or potentially never. If the objective is for leaders to monitor progress, the work management tool the team is using should allow enough transparency and aggregation to allow a leader to get that directly without the need for anyone to create a manual report.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AqLt9ihl3mqr4xsMYHf1Nw.png" /><figcaption>Manually created reports distract the team form their key activities</figcaption></figure><p>Another even worse measure is the concept of <strong>review boards</strong>. In this case the team is asked to review what they are doing with an SME board that will give them guidance so they can achieve better quality. Even though the board might have great people on it, they are so far removed from all the discussion, co-creation, and decision making that their review is usually superficial, and the team bringing them content will try their best to give them the least amount of information possible so as not to be derailed. The outcome of this exercise could be that the team would be given a set of useless tasks to go execute just because the review board feel they are responsible to give some guidance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0f8bpV8DYBI575lBhb540Q.png" /><figcaption>Review boards derail the team with superficial activities in an attempt to demonstrate value</figcaption></figure><p><em>So if all of this is no good, </em><strong><em>how can leaders be useful to teams</em></strong><em> to accelerate their progress and improve their work experience?</em></p><h3>How leaders can help, not hinder</h3><p>First, if a leader would like to get a feel for an agile team’s progress they should <strong>join some of the daily standups instead of asking for weekly reviews<em>.</em></strong> This will have two positive effects. The team will feel their leader cares about what they are doing and will be more passionate about doing their best, and no waste would be incurred by the team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gx9IdwjNG7CW7YdQknp1tA.png" /><figcaption>Leaders to attend daily standups instead of asking for weekly reviews</figcaption></figure><p>Second, if a leader wants to have documentation and sign off at each step, follow agile practices instead. <strong>Make sure the right person is defining the acceptance criteria for every user story and have that person be the one that declares a user story is done<em>.</em></strong> Involve that person as much as possible in all the iteration activities (backlog grooming, iteration planning, iteration demo, and retro).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nuPX5sL70jHgpSNKVsMNhQ.png" /><figcaption><em>The right person is defining the acceptance criteria for every user story, and they are the one that declares a user story done</em></figcaption></figure><p>If a leader wants to have review boards with SMEs to validate that the team is doing the right things, <strong>it is much more beneficial and effective for these SMEs to train the next generation of SMEs on the right practices and empower them to do the right things<em>. </em></strong>That will help on two fronts, the SMEs will feel more productive in that they are training others instead of monitoring or reviewing others, and the practitioners will feel more confident and will deliver better quality. A lot of waste will be eliminated given these reviews boards are not needed and the culture will change from adherence and compliance to a culture of pride in quality and performance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7B8llnyeM4OxNsxwtoVQSw.png" /><figcaption><em>SMEs train the next generation of SMEs on the right practices and empower them to do the right things</em></figcaption></figure><p><strong>Leaders can also keep their hands on the pulse if there is a dashboard integrated into the activity management tooling without needing to hold review meetings that disturb the flow and progress of work.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Iu95uHObM-R1TRAQ4fZBbA.png" /><figcaption><em>Leaders can also keep their hands on the pulse if there is a dashboard integrated into the activity management tooling</em></figcaption></figure><p><strong>The best way to ensure the project will be successful is to adopt and support agile practices which introduce the concept of impediment management<em>. </em></strong>Impediments are uncovered during the daily standups and managed within the team. If they can’t be managed within the team they are escalated and that is where leadership support is needed to address the escalated impediments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eoOckXvlCgXFnitjpIb7Rg.png" /><figcaption>Adopt impediment management to ensure success</figcaption></figure><p>I welcome your thoughts and feedback on my recommendations for how leadership should help their teams become more effective by adopting some best practices we follow in <a href="https://ibm.com/garage">IBM Garage</a>.</p><p>Authored by Dr. Mohamed El-Refai, IBM Distinguished Engineer, IBM Garage@Scale Leader</p><p>Illustrated by Zhuo Ma, IBM Studios Dalian Designers</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6b2478f7383" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[So What is IBM Garage!!!]]></title>
            <link>https://melrefai.medium.com/so-what-is-ibm-garage-564750a28da9?source=rss-94a0b35df7ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/564750a28da9</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[ibm-garage]]></category>
            <category><![CDATA[enterprise-agility]]></category>
            <category><![CDATA[agile-transformation]]></category>
            <category><![CDATA[enterprise-transformation]]></category>
            <dc:creator><![CDATA[Dr. Mohamed El-Refai]]></dc:creator>
            <pubDate>Fri, 09 Apr 2021 01:56:24 GMT</pubDate>
            <atom:updated>2021-04-13T01:59:55.024Z</atom:updated>
            <content:encoded><![CDATA[<h3>So, What is IBM Garage?!</h3><p>After so many years with the IBM Garage, I am still asked this question by clients and even IBMers who are trying to wrap their mind around this new way of working.</p><p>Many times I have been asked by teams, “We’ve been using agile for years and we’ve adopted design thinking in most of our workshops, so how would IBM Garage be any different?”</p><p>From other more technical teams I am asked, “We follow DevSecOps practices, we adopted pair programming, we focus on delivering MVPs and not POCs, so how is IBM Garage any different than what we already do?”</p><p>In very simple words I would answer that:</p><blockquote>“IBM Garage is a collection of practices woven together as a methodology to bring all of IBM together in helping a client realize business value at the fastest and most efficient rate possible.”</blockquote><p>Let me shed some light on what that means by explaining some of these practices.</p><p>One of the earliest practices we use in Garage is Business Framing. This practice was developed by the IBM Garage for Cloud and evolved by the IBM Services team to focus on client pain points and possible opportunities for IBM to partner with our clients to address pain points through value-focused business opportunities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hZv-2piGdE8VqU_0MBGhYw.png" /><figcaption>Initiate the Garage through business framing</figcaption></figure><p>Based on that business framing there is viability to establish a Garage for that client. One of the practices that was devised to structure a Garage is the concept of Core and Flex. A Garage is not rigid in nature; it needs to flex if needed. We define the initial core team based on the capacity that we foresee, but as we expose more business opportunities we might need to scale the Garage team using the flex model. What flex really means is additional capacity to allow the Garage to deliver as many outcomes as needed without having to queue things due to limited capacity.</p><p>Another very important practice that was developed by the APAC Garage Center of Competency (CoC) team is the concept of an Interface Team. Innovation is not something new; every organization is trying their best to innovate, but most of these efforts fail because the teams driving these innovations are being influenced by the technical and business debt the enterprise is imposing on them. The only way to enable innovation is to shield it and let it flourish before it is exposed to the rest of the enterprise where it can then become an agent of transformation if introduced successfully. The concept of an interface team allows for that to happen. The interface team shields the Garage squads from the rest of the enterprise to allow for their efforts to thrive without being impeded. The interface team consists of two boards—a Garage Board and and Investment Board. The Garage Board is focused on supporting the Garage squads in achieving their mission: approving the business opportunities they will work on, addressing resources and capability challenges the squads can’t address on their own, as well as addressing impediments the squad might escalate where interaction with the rest of the enterprise is needed. The Investment Board on the other hand is focused on justifying the existence of the Garage by tracking realization of ROI. If the Garage team is not achieving the expected business value generation it was created for then it is the duty of the investment board to redirect the Garage team to the path that will generate the business value that would align with the overall enterprise business initiatives and value drivers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PKlGmd8SA1ghX7ELYbMm_g.png" /><figcaption>Shield the Garage from the enterprise to allow it to flourish through the Interface Team</figcaption></figure><p>To govern the IBM Garage our APAC Garage COC also came up with a framework they call VOTE (velocity, outcomes, technical and administrative debt, and employee capability and satisfaction). It is a collection of metrics that, when used together, can give the Garage team a a pulse on Garage operations. The term velocity comes from Agile, it is a measure of the number of completed user story points against the number of committed story points by iteration. The reason Agile uses velocity is that story point counting is not comparable squad to squad, but velocity improvement is comparable squad to squad. We actually prefer to use efficiency over velocity as it is a measure of work completed against work planned so it can can capture effort not just story points as velocity can capture. Outcomes is a measure of the expected business value that is being generated from business opportunities identified and realized by the Garage squads. Technical and administrative debt consists of several things; one being productivity: the amount of productive hours compared to the amount of wasted hours. Wasted hours could result due to impediments; that is why we prefer to call this metric productivity as technical debt isn’t the only contributor. Employee capability and satisfaction is a measure of the cohesiveness of the Garage squads—their ability to deliver the work expected of them, how they work together, and how they value the work they do. We prefer to call this engagement as it embodies all of these aspects and much more.</p><p>As we progress through the various IBM Garage phases we uncover yet more practices.</p><p>In the Co-create phase we would usually start by conducting user research around the business initiatives communicated to the Garage team by the enterprise. That research would be an input to an Envisioning Workshop focused on identifying value drivers and key metrics that map to the business initiatives. We would also identify pain points and outline as-is scenarios that would help us generate improvement ideas that we would frame into potential business opportunities that we can pursue in the Garage. This Envisioning Workshop relies heavily on Enterprise Design Thinking practices.</p><p>The Garage team would use value orchestration practices to estimate the value of the business opportunity. Various techniques are used to estimate the value of a business opportunity, and that value would continue to be refined throughout all the stages of the Garage.</p><p>As we further refine the business opportunity, we draft it in a Business Opportunity Canvas that covers 16 different aspects of the business opportunity and is used by the Garage team to communicate their vision to the Garage board and gain their approval to proceed with that business opportunity.</p><p>As part of refining the business opportunity the Garage team would develop one or several problem hypotheses and go through an exercise of validating these problem hypothesis with a group of sponsor users. This practice of validation is based on Lean Startup practices. If the problem hypothesis is proven wrong, we pivot to identify a more suitable problem hypothesis.</p><p>Once the problem hypothesis is validated, we would start to look at possible solutions. The Garage team would draft these as solution hypotheses and go through a validation process similar to the problem hypothesis validation. Prototypes could be used during the validation process to get feedback from sponsor users. Anything uncovered through this process is used to further refine the Business Opportunity Canvas.</p><p>The Garage board would meet on a regular basis and review all proposed Business Opportunity Canvases and make decisions on which to be approved to proceed to the next phase of the Garage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e3NIVklz7fn2tH_oMteViA.png" /><figcaption>Co-create is the engine for the Garage germinating business opportunities to fuel enterprise growth.</figcaption></figure><p>In Co-execute the Garage team would start to develop conceptual architecture and design for the approved business opportunity, which would be an input to an MVP (minimum viable product) Workshop. That MVP Workshop is based on enterprise design thinking practices and focuses on exposing all the features of the proposed solution and narrowing down to the key features needed for a minimum viable product. But we do not stop there; the Garage team would then break down the MVP into all the user stories and activities needed to realize it. This will be the foundation for iteration planning for the MVP.</p><p>From this point on we typically follow standard Agile and DevSecOps practices to realize the MVP. The only difference with IBM Garage is that we would perform an MVP Market Fit validation to make sure the MVP we created is on target to achieve the expected business outcomes we identified during Co-create. This is done by confirming the value driver metrics we captured early on during the Envisioning Workshop in Co-create. If for some reason we fail to validate market fit we would need to go back to the drawing board. Once market fit is validated we would then proceed to scale the MVP in Co-operate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3bmH1gzjyoRTumAtMZvB0A.png" /><figcaption>Co-execute establishes and realizes the MVP for the Business Opportunity</figcaption></figure><p>In Co-operate we perform an MVP Scaling Workshop where we identify challenges, identify ideas, and develop actions to address around production workload, security, compliance, regulation, ennoblement, adoption, value, go to market, distribution, service, support, deployment, and go live.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IykkYfGQtReO-DieVc9JkA.png" /><figcaption>Co-operate guarantees the return on investment for the Business Opportunity</figcaption></figure><p>Our North America Garage CoC developed two additional practices of note. The first practice, called the Golden Thread, is used to validate the solution hypothesis. The Golden Thread is a representation of the user journey for the solution. It is shared with the enterprise and feedback is collected from all stakeholders and parties of interest. The Golden Thread is updated as the solution evolves through the Garage phases. The second practice is called Pain Point Tracker and is used to capture the pain points identified during the Envisioning Workshop in Co-create and maps the features addressed by the MVP in Co-execute to the pain points they are addressing. This helps us make sure each feature introduced is addressing a key critical pain point.</p><p>The IBM Garage Methodology is also manifested through a set of tools that enable Garage teams to perform the various practices and enforces the governance needed by the interface team to support the Garage. These tools range from assessment of client readiness for the Garage way of working, to governance and operation of the Garage, to opportunity value projection, to squad health surveys, to opportunity framing and business case justification.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DlATSMhqnTwwGl3UgXeJYA.png" /><figcaption>IBM Garage way of working manifested through practices templates and tools.</figcaption></figure><p>Now that we have more background on the practices that make up IBM Garage, you should also understand that there is more to IBM Garage than its practices. IBM Garage is a way of working that brings together all of IBM with undivided focus on generating business value with our clients. What that means is that different IBM business units do not create separate Garages for one client. Instead, we recommend that we have a single Garage for each client and various IBM business units join the Garage flexibly based on the capabilities, skills, and assets that are needed to realize the identified business opportunities that we uncover with our clients. That is why IBM is the only company in the world that can deliver the breadth of capability in almost every aspect of IT as well as the depth of expertise we have developed over decades of experience in every industry that we bring to the table when we collaborate with our clients. To facilitate this kind of IBM business unit collaboration, we have aligned several of the methods used within IBM to the IBM Garage Methodology so when these business units join a Garage they can be clear on where the practices they use align to the various IBM Garage Methodology phases and practices.</p><p>I welcome your thoughts and feedback on my characterization of what IBM Garage is and how it is different from other practices and frameworks.</p><p>The best way to know more about IBM Garage is to acquire the IBM Garage Essentials badge available to everyone at: <a href="http://ibm.biz/garageessentials">http://ibm.biz/garageessentials</a></p><p>If you start to get involved in an IBM Garage, I would recommend you acquire the IBM Garage Practitioner Badge available at: <a href="http://ibm.biz/garagepractitioner">http://ibm.biz/garagepractitioner</a></p><p>If you are a squad leader in an IBM Garage, I would recommend you acquire the IBM Garage Squad Leader badge available at: <a href="http://ibm.biz/garagesquadleader">http://ibm.biz/garagesquadleader</a></p><p>If you have led several IBM Garages, I would recommend you acquire the IBM Garage Leader badge available at: <a href="http://ibm.biz/garagesquadleader">http://ibm.biz/garageleader</a></p><p>And if you are a master of everything that is IBM Garage, then I would recommend you acquire the IBM Garage Coach badge available at: <a href="http://ibm.biz/garagecoach">http://ibm.biz/garagecoach</a></p><p>Authored by Dr. Mohamed El-Refai, IBM Distinguished Engineer, IBM Garage@Scale Leader</p><p>Illustrated by Chloe Sun, Olivia Wen and Zhuo Ma, IBM Studios Dalian Designers</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=564750a28da9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ten Success Factors to establish the Perfect IBM Garage Squad]]></title>
            <link>https://melrefai.medium.com/ten-success-factors-to-establish-the-perfect-ibm-garage-squad-b6116d962a39?source=rss-94a0b35df7ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/b6116d962a39</guid>
            <category><![CDATA[squad]]></category>
            <category><![CDATA[garage]]></category>
            <category><![CDATA[success]]></category>
            <dc:creator><![CDATA[Dr. Mohamed El-Refai]]></dc:creator>
            <pubDate>Wed, 27 Jan 2021 14:22:07 GMT</pubDate>
            <atom:updated>2021-02-01T17:30:09.358Z</atom:updated>
            <content:encoded><![CDATA[<p>At the heart of every IBM Garage are the garage squads that make up the driving engine for the garage. A well-established squad is like a well-oiled machine. The IBM Garage squads work iteration after iteration to generate high business value outcomes while maintaining a steady velocity and be measured at a high standard of quality. For these squads to achieve this level of efficiency and harmony, they need to be formed from teams that have the right mixture of talent, skill, and growth mindset. That is the secret sauce for successful squads. Easily said but hard to achieve, that is mainly due to one key critical component which is chemistry between squad members. A high-performing squad has chemistry they care about one another and their success is more than just success it is the pride of the squad. They also care about one another personally, so you would see these squads work relations strengthened with time but also crossing over to their personal lives to the point that they end up becoming close friends. This is analogical to army squads, the more they suffer and endure together the strong the bond between them and the more efficient and effective they become. In conclusion, we need long-lasting engagements for the squad to achieve peak performance. That helps us put our hand on the first key success factor for the perfect IBM Garage Squad, which is:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QOcYMcNEfQt4f4YoIvTaFw.png" /><figcaption>1. Maintain the squad together at all cost, roles can change but people should not.</figcaption></figure><p>At the helm of the squad is the squad leader, in my humble opinion, the squad leader in an IBM Garage is the agent of change, they are the reason we have an IBM Garage and not a normal Agile project. The squad leader should exhibit a lot of capability that combines the key practices that make up IBM Garage such as Lean Startup, Lean UX, Enterprise Design Thinking (EDT), Agile as well as some concepts in DevOps. I also found that the most successful Squad Leaders are certified EDT coaches, that is not only due to their ability to facilitate complex workshops but because they are creative by nature and they use that creativity to inspire their squads to think out of the box and overcome every challenge they face. In any way, IBM Garage is the place to co-create so who best can lead the teams in IBM Garage than our best creatives. Another component a great squad leader should exhibit is strong belief and experience in Agile practices. Yes, anyone can learn agile but believing in Agile and driving it deeper into the squad culture is the difference a strong squad leader makes. Not only does the squad leader need to define the ceremonies that the squad will follow and enforce them, but also, they are expected to make the squad believe and enjoy these ceremonies. With that we have our second success factor:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DWsw62TjY2JTX5DwBoG-HA.png" /><figcaption>2. The squad leader needs to be creative, influential, and motivational.</figcaption></figure><p>The second most important role in a squad is the architect. The more knowledgeable and experienced they are the more successful will the squad be. The architect also plays an important role to keep the squad focused on the bigger picture and prevent them from getting lost in the weeds. The architect does all of that by abstracting the complexity of the solution in a manner that every member of the squad can understand. There is another very important role that the architect plays. The architect performs as a design authority governing the design and implementation of the solution and dealing with any technical risks or impediments that the squad will face. The architect should listen to everyone in the squad but when it comes to making a technical decision, they have the authority to set the path forward and the squad needs to trust in their experience and wisdom. That uncovers our third success factor:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W5-MbsEnPszvbvTM21VcXQ.png" /><figcaption>3. The Architect needs to be a hands-on experienced leader, with strong drive capability.</figcaption></figure><p>Since we are counting the third important role in the squad is the Research/UX Designer, and this because a product will never be successful if the user experience is not well-conceived and based on actual user research. Some might challenge that there are products that do not have a user interface and hence do not need a UX designer. In my view that is not correct no matter what the product is if there is a user, a UX designer will add value to that product. That is why the Research/UX Designer is critical in the success of the squad, without the right focus on how users will use this product even we deliver all the required features it might not be usable. Unveiling our fourth success factor:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_HAB1ttOMEGNL_5IHymhsQ.png" /><figcaption>4. Base everything, we decide or build on well-founded research and user experience.</figcaption></figure><p>Well, where does the rest of the squad come in? In fact, everyone in the squad is as important as the first three. The success of a squad results from every person’s contributions and their volunteer efforts to help when challenges surface. The rest of the squad members will be formed based on the product being developed. That will vary if we are transforming an existing process into an intelligent workflow, or if we are just creating a new algorithm to optimize shelf replenishment, or a mobile app. that is consumer-facing, or an enterprise HR solution to improve employee well being, or an IoT solution that is making sure a manufacturing line is working at its peak capacity, or a blockchain solution that establishes trust between multiple shippers and government custom organizations and shipping yard operation, or even a quantum solution to discover new materials that exhibit properties needed in our accelerated future development. As you can see there is really no predefined set of skills that you would need on any squad it is really based on the product that your squad will be formed. Wish leads to our fifth success factor:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dJnMl6aZxqKPEKakqHFPLA.png" /><figcaption>5. Extend the squad with the right technology and industry SMEs.</figcaption></figure><p>Each member is expected to have depth and breadth of skills. Their depth makes them the SME in that area on their team while their breadth lets them progress the entire squad independently and be able to help when one area needs more resources. Both depth and breadth are equally as important. A common term for mobile and web applications is a full-stack engineer, which means they have most of the skills to develop a solution from the front end to the back end, without having to depend on others. Even if one person can do everything when we plan squads, we need to consider the timeline. We want as much work to be done in parallel to deliver the product with speed also so as not to overload one person. In the case of mobile or web applications, even though we might have full-stack engineer we usually staff the squad with separate resources for Front End and Back End, so while the Front End resources are working on developing the UI the back end resources are creating the back end APIs, and with simple integration, we could potentially cut down the delivery time by 1/3 or a little more if we had resources going sequentially from front end to back end. Our sixth success factor is:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k9rJ0Wcv7gjy63oJeYRHUw.png" /><figcaption>6. Most of the squad members should be T shape skilled.</figcaption></figure><p>One of the major reasons why IBM Garage squads are more efficient and productive is due to their garage culture. The garage culture has evolved from various cultures, first from agile and DevOps, then from IBM Studios Lean UX and Enterprise Design Thinking, and lastly from Lean Startup. I prefer not to call these practices and instead call them cultures, as it is more about believing in a practice and performing it from the heart, than just learning a practice and executing it efficiently. The Agile and DevOps culture introduces the right level of rigor while allowing for squad autonomy and empowerment to make the right decisions. IBM Studios culture is hard to explain it has to be experienced to be understood fully but let me try my best, our IBM studios act as a melting pot for the diversity of knowledge and encourage creativity and eccentric thinking to generate original ideas that would have otherwise not surfaced. Enterprise Design Thinking culture is based on a set of practices that employ diverge and converge techniques to allow every participant&#39;s voice to be heard and taken into consideration. This EDT culture applied in a rapid iterative manner aligns best with Lean UX, where we prototype and eliminate failure cases fast so we can focus on the most promising ideas. Finally, with Lean Startup culture adopted by most entrepreneurship makes it ideal in a garage model where we seek to validate a product to market-fit and scale it. The evolution of all these cultures together makes up the squad culture which is essential to its success only if it is believed in and executed from the heart. The squad culture is also defined at the personal level. What habits does the squad tend to favor, such as weekend outings, casual happy hours, or even monthly birthday celebration, all of that makes up the squad culture. So our seventh success factor is:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3p05jwYdESkoh3sg_MrEkQ.png" /><figcaption>7. The culture that the squad believes in will secure its success.</figcaption></figure><p>The squad needs to reflect on its work and improves its performance with time. Agile introduces retrospective sessions that are adopted in the IBM Garage squad culture to a great extent. Through these retrospectives, most problems the squad is facing can be addressed so the next iterations can become more successful. For example, if one of the recently introduced squad members doesn’t have the right skills and is dragging the entire squad behind. That would be surfaced in the retrospective and the squad will act as a family and agree to take the right action to bring that person up to speed, so overall the squad can be more efficient. This leads to our eighth success factor:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pGF6A-h08LEusBkLNGFcCA.png" /><figcaption>8. Squad retrospectives are essential to reshape the squad for success.</figcaption></figure><p>Due to the current challenges, garages had to discover what remote work means, while others were already familiar with that way of working for years. It is no secret IBM Garage purest would tell you the team needs to be co-located, although there is great value to collocation it is not essential to happen all the time. Some squads are formed across dispersed geographic locations and although they manage to travel to collocate it is not a sustainable model, some have decided to collocate one week and work remotely one week, others have decided to work remotely most of the time and collocate during key ceremonies. For the squad to build chemistry and harmony, it is essential they do meet from time to time. That will improve the quality of communication and build relations to allow for the squad members to support one another when the situation calls for it. Now if everyone is working remotely how could these meetups happen, humans are very creative and have come up with ways to hold virtual happy hours, or always-on web conferences that allow individuals working remotely to stay connected. With that our ninth success factor is:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xi3jV90r7UTfSkPH3TG1LQ.png" /><figcaption>9. Regular physical or virtual squad meetups are instrumental in improving communication and collaboration.</figcaption></figure><p>The commercials of the garage play a big role in the contract being signed. Especially that it is a fixed capacity model with the client taking on a big part of the risk. With the current market competition, this makes getting a garage deal signed harder if we do not utilize our global resources to make the offer more competitive. Most would think that would introduce efficiency or quality factors, but that is more ignorance than fact. Our global resources are not the traditional low-cost staff augmentation resources, they have evolved over the years and now become an irreplaceable component in our overall technical vitality. So, with that in mind what is the best way to form a squad that will include global resources. The most important factor to consider is to keep the majority of the squad in the same time zone. Finally, our tenth success factor is:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GK84quqzV15Am9bDZt5-Ow.png" /><figcaption>10. Most of the squad members should be in the same time zone.</figcaption></figure><p>So, in summary, establishing the perfect IBM Garage Squad is essential for the garage success, and here are ten success factors that can guide you along the way:</p><p>1. Maintain the squad together at all costs, roles can change but people should not.</p><p>2. The squad leader needs to be creative, influential, and motivational.</p><p>3. The Architect needs to be a hands-on experienced leader, with strong drive capability.</p><p>4. Base everything, we decide or build on well-founded research and user experience.</p><p>5. Extend the squad with the right technology and industry SMEs.</p><p>6. Most of the squad members should be T shape skilled.</p><p>7. The culture that the squad believes in will secure its success.</p><p>8. Squad retrospectives are essential to reshape the squad for success.</p><p>9. Regular squad meetups are instrumental in improving communication and collaboration.</p><p>10. Most of the squad members should be in the same time zone.</p><p>I would like to leave you with one last quote and then I would love to hear your thoughts.</p><blockquote>“A perfect IBM Garage squad is any squad that enjoys working together and achieves the needed business success to justify its existence”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c_tCwK9qYLxGsNdpV4UyWQ.png" /></figure><blockquote>Authored by Dr. Mohamed El-Refai, IBM Distinguished Engineer, IBM Garage Assets and Platform Leader</blockquote><blockquote>Illustrated by Chloe Sun and Olivia Wen, IBM Studios Dalian Designers</blockquote><p>Learn more at <a href="http://www.ibm.com/garage">www.ibm.com/garage</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b6116d962a39" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>