<?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 Karim Ali on Medium]]></title>
        <description><![CDATA[Stories by Karim Ali on Medium]]></description>
        <link>https://medium.com/@karim-ali?source=rss-4fb178da873a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*C6k6KJp8H9bW4NcyYS4jJQ.png</url>
            <title>Stories by Karim Ali on Medium</title>
            <link>https://medium.com/@karim-ali?source=rss-4fb178da873a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 20:42:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@karim-ali/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[My Product Philosophy: The 4 Concentric Circles]]></title>
            <link>https://karim-ali.medium.com/my-product-philosophy-the-4-concentric-circles-0c0f82482bc2?source=rss-4fb178da873a------2</link>
            <guid isPermaLink="false">https://medium.com/p/0c0f82482bc2</guid>
            <dc:creator><![CDATA[Karim Ali]]></dc:creator>
            <pubDate>Mon, 29 Jul 2024 20:17:25 GMT</pubDate>
            <atom:updated>2024-07-29T20:18:20.846Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WIqKdzwVK7NWC8uuvjZNxw.png" /><figcaption>The 4 Ps Framework</figcaption></figure><p>In the dynamic world of product management, having a clear and structured philosophy is crucial. Over time, I’ve developed a framework that guides my approach, which I call “The 4 Concentric Circles.” This philosophy encapsulates four key areas: Purpose, People, Practices, and Product. Each circle represents a layer that builds upon the previous one, ensuring a holistic and user-centered approach to product management.</p><h3>Purpose</h3><p>At the core of any successful product team lies its purpose. This involves understanding the mission of the team and the organization from a user perspective. The purpose is about identifying the core reason why the team exists and how it ties back to the broader vision of the organization or product.</p><p>To define the purpose, I start with foundational tools such as a user journey map, a service blueprint, or a Job To Be Done (JTBD) research. These tools help in capturing the user needs and mapping them to the value the team aims to provide. Furthermore, techniques like cell-splitting or reverse Conway maneuver are employed to design the relationships and structures within the team. This ensures that the team’s efforts are always aligned with delivering meaningful value to the users.</p><h3>People</h3><p>The next layer focuses on the people involved in bringing the product to life. This involves identifying the necessary skillsets, defining roles and responsibilities, and establishing a coaching and up-skilling structure. The goal is to build a culture that supports continuous learning and development.</p><p>In addition to defining roles, this circle also extends to cover the competency framework and leveling structure. It is essential to ensure that team members have clear career progression paths and that their growth is supported by the organization. Furthermore, product support functions are also defined here, ensuring that the team has the necessary resources and backing to succeed.</p><h3>Practices</h3><p>Once the purpose and people are in place, the next circle involves defining the practices that will guide the team’s operations. This includes establishing an operating model and the critical systems needed for the organization to function effectively.</p><p>Key aspects here include defining domain boundaries, governance structures, decision-making processes, and the balance of power within the team. Agility is also a crucial element, ensuring that the team can adapt to changes quickly and efficiently. Effective engagement, communication strategies, and self-service options are established to foster a collaborative and autonomous working environment.</p><h3>Product</h3><p>The outermost circle represents the product itself — the tangible outcome of the team’s efforts. This circle is about defining the narrative or story that communicates the product priorities. It involves articulating what success looks like, how it will be measured, and outlining the growth model for the product.</p><p>This narrative should be compelling and clear, providing a roadmap for the team and stakeholders. It ensures that everyone is aligned on the goals and understands the metrics for success. By clearly defining these elements, the team can maintain focus on delivering a product that meets user needs and drives organizational growth.</p><h3>Conclusion</h3><p>The 4 Concentric Circles framework provides a structured and comprehensive approach for product leaders to manage their product organizations effectively. This framework emphasizes starting with a clear purpose, building a skilled and motivated team, defining effective practices, and focusing on delivering a compelling product. By adhering to these principles, product leaders can ensure their efforts are consistently aligned with delivering maximum value to users. This philosophy not only facilitates the creation of successful products but also fosters the development of a cohesive and high-performing product team.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0c0f82482bc2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering Product Strategy: A Comprehensive 5-Stage Process for Product Leaders]]></title>
            <link>https://karim-ali.medium.com/mastering-product-strategy-a-comprehensive-5-stage-process-for-product-leaders-feb7ee3758da?source=rss-4fb178da873a------2</link>
            <guid isPermaLink="false">https://medium.com/p/feb7ee3758da</guid>
            <dc:creator><![CDATA[Karim Ali]]></dc:creator>
            <pubDate>Mon, 29 Jul 2024 14:53:25 GMT</pubDate>
            <atom:updated>2024-11-05T16:31:38.855Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mastering Product Strategy: A Comprehensive 6-Stage Process for Product Leaders</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DZMx-aMfsIUG2k_E206-cA.jpeg" /><figcaption>Image Generated By DeepAI</figcaption></figure><p>Product strategy is a critical aspect of product management that ensures the alignment of product goals with the broader organizational objectives. As a product leader, I’ve developed a structured 6-stage process to streamline this endeavor, ensuring strategic clarity and effective execution. This article captures the essence of my product strategy process, derived from years of experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nTwwjw15_cPQzIUt34x6cA.png" /></figure><h3>Stage 1: Set the Stage</h3><h4><strong>Key Steps:</strong></h4><ol><li><strong>Choose the Right Framework:</strong> Select a model or framework that aligns with both your product vision and organizational goals.</li><li><strong>Establish Governance:</strong> Set up a governance structure to oversee the strategy’s creation, execution, and iteration.</li><li><strong>Assemble the Strategy Team:</strong> Bring together a diverse product council, including senior leaders and market experts, to provide broad perspectives.</li><li><strong>Kickoff with Brain Dumps:</strong> Initiate brainstorming sessions to capture raw ideas and early-stage insights.</li></ol><p>The first stage focuses on laying a solid foundation. Selecting the right framework ensures a structured approach, while assembling a diverse team fosters varied expertise. Brain dumps help surface initial ideas, setting the stage for deeper analysis in the following stages.</p><h3>Stage 2: Diagnose The Current State</h3><h4>Key Steps:</h4><ol><li><strong>Data Exploration:</strong> Dive into quantitative data, assess its quality, and identify patterns that shed light on your product’s current performance.</li><li><strong>Qualitative Insights:</strong> Engage with user feedback to understand pain points and how your product meets or fails to meet their needs.</li><li><strong>SWOT Analysis:</strong> Analyze strengths, weaknesses, opportunities, and threats to assess your product’s positioning in the market.</li></ol><p><strong>Desired Outcome: Well Discovered Opportunities Space</strong></p><p>In this stage, it’s about getting to the core of where your product stands today. Analyzing data, both quantitative and qualitative, will help surface crucial insights. The goal is to uncover opportunities that will shape the strategic decisions in the next stage.</p><h3>Stage 3: Establish A Strategic Direction</h3><h4>Key Steps:</h4><ol><li><strong>Make Strategic Choices:</strong> Based on the diagnosis, prioritize opportunities and evaluate trade-offs and risks.</li><li><strong>Visualize the Future State:</strong> Craft a high-level vision of your product’s desired future state, using simple visuals like user journeys or sketches.</li><li><strong>Align with Leadership:</strong> Ensure strategic alignment with senior leadership and address budget concerns early on.</li></ol><p><strong>Desired Outcome: Well-Defined Choices &amp; Tradeoffs</strong></p><p>Here, the goal is to outline where you want the product to go and what it should achieve (AKA: where to play). This stage sets the tone for the overall strategy, ensuring leadership buy-in while outlining a compelling future narrative for your product team.</p><h3>Stage 4: Frame the Product Big Bets</h3><h4>Key Steps:</h4><ol><li><strong>Top-Down to Bottom-Up Handover</strong>: Leverage the strategy kernel and the outcomes of the previous stage to facilitate onboarding sessions, debates, and Q&amp;A sessions, ensuring the strategy and its reasoning (the “What” and “Why”) are well understood by bottom-up teams.</li><li><strong>Mobilize the Product Trios</strong>: Empower PMs to lead local bottom-up planning for big bets, using frameworks like OST (Opportunity Solution Tree).</li><li><strong>Calibrate Big Bets</strong>: Balance major initiatives between different packs/teams and markets.</li><li><strong>Engineer a Low-Fi Roadmap</strong>: Create a roadmap to clarify intents, milestones, capacity gaps, and dependencies.</li></ol><p><strong>Desired Outcome: A Low-Fi Roadmap</strong></p><p>Transitioning from high-level strategy to actionable plans involves extensive collaboration and bottom-up planning. Engaging product trios led by PMs ensures that strategies are practical and aligned with on-ground realities. The low-fi roadmap serves as a guide, outlining key milestones and dependencies.</p><h3>Stage 5: Secure Sign-Off</h3><h4>Key Steps:</h4><ol><li><strong>Calibrate Cross-Functional Priorities</strong>: Ensure alignment across different functions within the organization.</li><li><strong>Identify Misalignments:</strong> Address any discrepancies between teams before final approval.</li><li><strong>Leadership Approval:</strong> Secure leadership’s sign-off, including budget confirmation.</li></ol><p><strong>Desired Outcome: A Calibrated Strategy</strong></p><p>Securing organizational buy-in is critical at this stage. By aligning cross-functional priorities and ironing out any misalignments, you’ll ensure a smooth transition to execution. Leadership approval marks the official green light for deployment.</p><h3>Stage 6: Strategy Deployment</h3><h4>Key Steps:</h4><ol><li><strong>Deploy the Strategy</strong>: Implement the strategy using OKRs (Objectives and Key Results) or NCTs (Narrative, Commitments, Tasks).</li><li><strong>Monitor and Adjust: </strong>Continuously track progress and outcomes, adjusting the strategy as needed to maintain alignment with goals.</li></ol><p>Deploying the strategy involves translating plans into actionable steps. Using frameworks like OKRs or NCTs helps in setting clear objectives and tracking progress. Regular reporting and reviews are essential for making necessary adjustments and ensuring the strategy remains on track.</p><h3>Balance of Power &amp; Knowledge Horizons</h3><blockquote>A word of caution: There is <strong>no one-size-fits-all approach in product development</strong>. It is the product leader’s responsibility to balance power distribution within the team and decide what to delegate and what to own, considering factors such as team size, maturity, and seniority.</blockquote><p>Product leaders must facilitate the fluid movement of knowledge between the <strong>general</strong> and <strong>specific</strong> horizons to ensure continuous progression. Over-focusing on the general horizon can lead to broad, non-executable strategies, while getting bogged down in specifics can cause decision delays, lack of progress, and over-engineering.</p><h3>Top-Down Ownership:</h3><ul><li><strong>Roles</strong>: CPOs, VPs, Directors</li><li><strong>Focus</strong>: Define the general direction (the “What” and “Why”) by studying heuristics, stitching insights together, blending them with product sense, and aligning with the overall company strategy.</li><li><strong>Objective</strong>: Create a vivid depiction of the desired state (the bigger picture) to inspire and clarify strategic goals to their teams.</li></ul><h3>Bottom-Up Ownership:</h3><ul><li><strong>Roles</strong>: PMs, Heads, GPMs</li><li><strong>Focus</strong>: Deep-dive into the specifics, exploring opportunity and solution spaces within their team’s direct influence.</li><li><strong>Objective</strong>: Figure out the actions they’ll be owning with their teams (MVPs, experiments, builds) in order to contribute to the product strategy in a coherent way.</li></ul><p>The fluid movement between these two levels of planning ensures a comprehensive strategy that is both visionary and executable. <strong>Leadership defines the main pillars of the strategy</strong>, while <strong>teams fill in the details, continuously validating and refining it</strong>. This approach enables timely corrective actions as needed, maintaining a fair and logical balance of power.</p><h3>Conclusion</h3><p>A well-defined product strategy process is essential for product leaders seeking strategic alignment and effective execution. By adhering to this 6-stage process and maintaining a balance of power between top-down and bottom-up approaches, product leaders can guide their teams toward successful outcomes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=feb7ee3758da" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agility in Product Organizations, The Why and How — Karim Ali]]></title>
            <link>https://karim-ali.medium.com/agility-in-product-organizations-the-why-and-how-karim-ali-b539e418a95e?source=rss-4fb178da873a------2</link>
            <guid isPermaLink="false">https://medium.com/p/b539e418a95e</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-leadership]]></category>
            <category><![CDATA[agile-transformation]]></category>
            <category><![CDATA[agility]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Karim Ali]]></dc:creator>
            <pubDate>Sun, 03 Oct 2021 18:17:51 GMT</pubDate>
            <atom:updated>2021-10-05T17:05:53.476Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/582/0*fTjr2b6vXVeMpPDJ" /></figure><h3>Agility in Product Organizations, The Why and How</h3><blockquote><strong><em>Agility is the ability to adapt and respond to change … agile organizations view change as an opportunity, not a threat</em></strong></blockquote><blockquote><em>Jim Highsmith</em></blockquote><p>Organizational Agility is probably the most important characteristic of not only product organizations but entire businesses.. want an example ? think COVID-19 !</p><p>When COVID-19 was declared a global pandemic and lock-downs started by early 2020, a lot of businesses went into shock, no one ever witnessed something like this before, simply no one studied something like this in business text-books or schools. Many organizations didn’t have any sort of blue-prints or SOPs (standard procedures) for how to act to this sudden and devastating change, no one also had any sort of predictions to when things would get back to normal, hence the uncertainty in taking actions, questions like should we downsize, should we wait, should we pivot the business, should we close physical stores, should we pay rent ! answering any of these questions required knowledge that no one actually possessed and a lot of businesses went into real-time decision making based on new findings as they come.</p><p>It’s almost 2 years now since the start of the pandemic, and when you look at the businesses which were able to not only survive but actually flourish, you will find a common characteristic that defines almost all of them, <strong>Agility</strong>.</p><h3>Why should you care about your Organization Agility?</h3><p>The answer is quite simple; survival.. put it this way, if your organization is not fast enough in sensing and responding to new changes then you will most probably become a nice meal for some potential predator !, this predator can be a lethal virus, a natural disaster, a financial crisis, or a new competitor.</p><p>Now if you work in technology then you are most probably aware of “Agile software development” and practicing it in some way or another, and if you know the story of how it came to be then you’d know that it was introduced to solve some very critical problems with the way software development used to happen before 2001, It advocates adaptive planning, evolutionary development, early delivery, and <a href="https://en.wikipedia.org/wiki/Continual_improvement_process">continual improvement</a>, and it encourages flexible responses to changes in requirements, resource availability, and understanding of the problems to be solved.</p><p>Yet as great as it is, the concepts of “Agility” is in many organizations limited only to engineering or technology teams !, it’s a weird phenomena but I bet you encountered it a lot, i call it the <a href="https://en.wikipedia.org/wiki/A_Tale_of_Two_Cities">“tale of two cities</a> “ syndrome, where there is a product/tech city appreciating flexibility and adaptability and a business city ruled by the ex-BCGs and ex-McKinseys of the world who value very long business cases and 5-year forecasts..</p><p>If you are the product leader in your organization then you will definitely have a great influence on your company’s culture and a big opportunity to participate in evolving it, start with a robust foundation within your own team and make sure that you have the right people onboard, partner solidly with tech to make sure that you have full synergy and then move outwards to the most adjacent business functions to change their subcultures a team at a time. Based on my experience, Marketing teams were always the most open to change and adopt a more Agile way of thinking.</p><h3>How can you introduce systematic agility in your product organization?</h3><p>In this part of the article i’ll be talking about a model that i developed over the years to introduce systematic agility in the product teams i led, yet the same model can be deployed throughout an entire organization since it’s steps are not product and tech specific.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/944/0*_0PO9cbEJ_zCsZ8y.png" /></figure><p>The model is made up of a continuous cycle of 4 main activities that you and your organization need to master; sense, reflect, plan and communicate.. it has no end state, should be always running and continuously calibrated. Now let’s deep dive into each one of these activities;</p><p><strong>Sense</strong></p><p>It’s time to grow antennas ! or develop your own spidey senses, whichever sounds cooler to you.. <br>This activity is the main key to the whole model, as you will only be able to respond to changes if you were good enough in detecting them in the first place, obviously.</p><p>In order to get good at sensing changes you should establish the right subprocesses and continuously improve them to sense changes in your <em>business environment</em> as in new rules, regulations or business models, in your <em>competitive landscape </em>as in new competing products or features launched by existing competitors, in your <em>customer base</em> as in inter-segment movements, in <em>technology</em> as in new software or hardware, in your <em>customers behaviour</em> as in needs or wants shifts.</p><p>The following subprocesses if established can help you get started, yet you need to continuously evaluate and improve them, with more training and experience you should also be able to <strong>separate signal from noise </strong>as responding to noise can create a catastrophe to your organization, you’ll be indefinitely shifting your plans, accomplishing nothing which leads to a loss of trust in your product org and in your capability as a leader.</p><p>Ways to harvest signals;</p><ol><li>Form a product council: the value of the product council is that it acts as an “intelligence agency”, the council should be formed from only senior members who are capable to sift through the many granular details and only afloat the most important ones. In Delivery Hero MENA i established a product council which included the VPs of engineering, operations and sales with the mandate to meet on bi-weekly bases to share new insights, anecdotes, and strong rumors.</li><li>Insure data availability and invest in data discovery: If you are not doing it already then you should start right away, start with hiring strong product analysts who can help you sense meaningful changes in data trends, build live data dashboards and work with them to build early anomaly detection and reporting capabilities, using IQR or other methods of anomaly detection.</li><li>Establish continuous user research &amp; VOC scanning: In a previous article i spoke about the importance of <a href="https://karim-ali.medium.com/eat-your-broccoli-my-thoughts-on-user-research-e23122ad541f">user research </a>and how you can -and should- integrate it effectively into your product development process, equally important you should also actively scan for VOC in social media, store reviews, feedback emails and almost all customer touch points. Hence you should always cover both active (customers reaching out to you) and passive (you reaching out to customers) qualitative feedback.</li><li>Streamline teardowns for competing products: teardowns can be extremely helpful in understanding and responding to competing products, not only will they help you save time by avoiding re-inventions but also they can help you pinpoint potential flaws in competing products which you can act upon on your own product to create a strong competitive advantages.</li></ol><p>Remember that no one size fits all in the world of product development and hence you should continuously test and only maintain what works for your organization the best.</p><p><strong>Reflect</strong></p><p>Here comes the time to ask yourself the million dollar question; Was what i sensed relevant to my company overall direction ? and is it more important than what i’m doing right now ?, if your answers to both questions were “yes” then you should continue with the rest of the model stages, if it was “no &amp; no” or “yes and no” then you shouldn’t disrupt your current team focus and plans.</p><p>Now this question is what is known as a “Compare &amp; Contrast” question, it doesn’t ask whether or not a new sensed change is important, rather it asks if the change is in particular more important to respond to compared to everything that you are doing right now, hence reflection in essence is as good as your ability to master calculating the opportunity cost of the alternatives you have in front of you.</p><p>Reflection as an activity will consume time, either from you as the team leader or from a subset of your team who will be tasked to do the due diligence, and yes due diligence should be done properly as the last thing you want to do is to keep throwing unrefined and inconclusive thoughts at your team while they are focusing on delivering the agreed upon product plans. If this happened then you will be shooting yourself in the foot, disruption causes time loss and eventually will cause frustrations within your team. There is a reason why your product managers and their teams are following the no-scope-change rule heartedly once their sprint has started.</p><p>So, 3 very important things you need to take care of at this stage:</p><ol><li>Understand the cost of disturbing your team while focusing on a preset, pre-agreed upon plan.</li><li>Do your due diligence to make sure that you are not responding to noise! and calculate the opportunity cost of not responding to a sensed change, like if it’s going to push you out of business then obviously you should act immediately.</li><li>Be transparent, show empathy and make sure that you do bring your team fully onboard, they have to buy-in and be 100% aligned with your decision, they need to understand the “why” and “how” would that change bring them even closer to their goals and hence be a much better use for their time &amp; effort.</li></ol><p><strong>Plan</strong></p><p>At this stage you are kind of replacing an airplane engine in midair, so be surgical, decisive and fast.</p><p>Solid planning for the next best action is extremely important as without it you risk your team going into planning chaos.. One thing that helped he in such situations was to onboard the team leads first, and work with them on the change plan, and also to put a plan for consequences.</p><p>It’s worth noting that not everyone responds well to change, hence the importance of doing the action planning properly, because when your team sees a solid articulate plan in-front of them they will tend to maintain their trust in you and in your decisions, and make sure that you also plan well for the consequences, anticipate resistance and be ready.</p><p>During my last year with Delivery Hero, i faced multiple situations where we had to change the missions of entire teams, basically scrapping what they have been working on for the past months in order for the whole organization to reduce redundancy thus gain speed and become more efficient, such situations are very hard and emotional as teams get attached to their products by time, hence you should anticipate things like potential talent loss, and you better be ready with a plan !</p><p><strong>Communicate</strong></p><p>As with everything product development, structured communications always play a great rule in the success of your plans, keep it inclusive and give room for feedback.</p><p>Keep your communications well structured; You should be communicating the reason behind the change in your plans, why is it important, what will get changed and how changes will be executed.</p><p>Keep your communications inclusive; Product decisions rarely only impact product and tech, unless what you were working on originally was in-fact a very a technical task like addressing tech debt or breaking down a monolithic application, otherwise your product decisions will impact other business functions beyond product &amp; tech, like marketing, sales, finance, operations.. etc, for that they need to be included in your structured communications to act upon the new changes and be able to highlight any risks if any.</p><h3>Finally…</h3><p>Agility should be one of the main characteristics of any product organization, it ensures your organization long term business sustainability and continuous growth.. You should deeply root Agility as a value in your product culture and it should guide your hire and fire decisions. In a previous article i wrote about the main <a href="https://medium.com/p/4f23e7eb051d">characteristics of Scalable Product Managers</a> and how to spot them, the obvious link here is <strong>people</strong>, having product managers who can embrace change, accept uncertainty, and can themselves demonstrate resilience will definitely have the greatest impact on the success of your efforts of building agility in your organization.. So make sure your have the right people onboard.</p><p>I hope you enjoyed reading this article, and as usual please remember to share your thoughts &amp; comments below.. cheers!</p><p><em>Originally published at </em><a href="https://www.karim-ali.com/2021/10/agility-in-product-organizations-the-why-and-how/"><em>https://www.karim-ali.com</em></a><em> on October 3, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b539e418a95e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Adopting A Mobbing Approach In Product Development]]></title>
            <link>https://karim-ali.medium.com/adopting-a-mobbing-approach-in-product-development-d202a3285580?source=rss-4fb178da873a------2</link>
            <guid isPermaLink="false">https://medium.com/p/d202a3285580</guid>
            <category><![CDATA[design-sprint]]></category>
            <category><![CDATA[cocreation]]></category>
            <category><![CDATA[mob-programming]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Karim Ali]]></dc:creator>
            <pubDate>Mon, 20 Sep 2021 15:49:56 GMT</pubDate>
            <atom:updated>2021-10-05T17:09:00.197Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*t5nA8QXwF3aPbjLg6QYCQQ.jpeg" /></figure><h3>Introduction to Mob Product Development, promoting inclusivity and diversity</h3><blockquote><em>The basic concept of mob programming is simple: the entire team works as a team together on one task at the time. That is: one team — one (active) keyboard — one screen (projector of course).</em></blockquote><blockquote><strong><em>— Marcus Hammarberg, </em></strong><a href="http://codebetter.com/marcushammarberg/2013/08/06/mob-programming/"><strong><em>Mob programming</em></strong></a><strong><em> — Full Team, Full Throttle</em></strong></blockquote><p>In 2017 when I first joined Delivery Hero MENA, I was obsessed by trying to figure out ways to make co-creation a reality across different product teams, effectively breaking all the silos that existed.. In my vision I wanted to bring entire product teams (that is the product manager + designer + engineers) together along with their core business stakeholders in a single room, locked away from daily distractions to focus together on solving a common product challenge..</p><p>The outcome of the concept i’m going to talk about in this article helped the teams to introduce the first version of our grocery delivery vertical as well as the very first version of our customer help center.</p><h3><strong>How can you adopt mobbing in product development ?</strong></h3><p>Being influenced by the concepts of both mob programming &amp; <a href="https://www.interaction-design.org/literature/topics/design-sprint">design sprints</a>, I introduced a hybrid adaptation which I called the “<strong>Working Product Session</strong>” or WPS as a concept to my team.</p><p>The core of the WPS was a thinking process similar to the 5 steps of the design sprint (Understand, Sketch, Decide, Prototype, Validate) yet conducting the 4 first steps in 1 day rather than the normal 4 days simply because it was very hard to have everyone stick together (especially with business stakeholders) for more than 1 day while maintaining their focus.</p><p>As with the normal design sprint the team would hijack a meeting room, prepare their post-its , charts, pens .. etc and make sure that they would have a representation of the below participants, each one leads one of the 4 big risks of the product initiative and alternatives you collectively come up with:</p><ol><li>Functional/Commercial Owners: lead the <strong>Business Viability</strong> risk assessment.</li><li>Tech Owners (team Engineering Manager + other engineers): lead the<strong> Feasibility</strong> risk assessment.</li><li>Product Experience Owners (product designers): Own the <strong>Usability </strong>risk assessment.</li><li>Product Value Owners (product managers): Own the <strong>Value </strong>risk assessment.</li></ol><p>If you are not aware of the 4 Big Risks, then I recommend you this article by <a href="https://svpg.com/four-big-risks/">Marty Cagan</a> as well as his famous book; <a href="https://www.amazon.ae/dp/1119387507/ref=cm_sw_em_r_mt_dp_CCQ2NTZMT54YR0EBRHGH">Inspired</a></p><p>Generally the product manager &amp; designer co-lead the WPS formation, guide everyone through, arrange note taking and of course arrange food :)</p><h3>Why Working Product Sessions can add great value to your product org ?</h3><p>The answer is simple, <strong>Inclusion and Diversity</strong>, each one of these 2 aspects can drive tremendous value once adopted properly throughout the product org.</p><p><strong>Inclusion in product thinking</strong></p><p>There is a misconception that many product managers unfortunately have, which is that they “exclusively” own the rights of thinking and acting on the development of the products they lead ! is this absolutely wrong — in case you haven’t figured that already — as the role of the PM is the absolute opposite, it’s to maximized customer value creation by establishing ways for inclusive thinking within his/her organization.</p><p>A core benefit which Mob product development offers out of the box is that it helps the product managers achieve a high degree of inclusivity &amp; co-creation in an easier and more structured way, enabling them to establish a solid common ground, drive consensus and compile a 360 knowledge of all the ins and outs of their product initiatives.</p><p><strong>Diversity in product thinking</strong></p><p>Imagine a Mob formation which includes all the 4 key owners I mentioned above (Designer+Engineers+Product Manager+Functional Owners), each comes with a unique set of skills and experiences which when combined have a far more powerful impact on customer value creation compared to it’s isolated individual pieces.. A <a href="https://powerrangers.fandom.com/wiki/Megazord">Megazord</a> !</p><p>Accepting and appreciating diversity is that what such types of highly collaborative product development frameworks help you bring to your organization, call it Mobbing, call it working sessions or call it anything else, doesn’t really matter, the bottom-line is that much better product decisions will be taken as a direct result of combining such diverse set of experiences &amp; skills.</p><h3>Finally…</h3><p>Over the years while I was continuously scaling the product organization in Delivery Hero MENA, this model continued to evolve and mature, it became part of our squad mentality and operating model.</p><p>Yet it takes time for teams to really embrace co-creation as a habit, doing it autonomously and without top-down supervision because they understood the great value which inclusion and diversity have on product development, Nevertheless, transformation requires a lot of persistence, reliance and continuous coaching.. As product leaders we should help our teams break decision making silos, loosen-up their sense of authority and adopt decentralization as a principle.</p><p>At the time of COVID-19 and the remote work culture, I found that a great team has already created a very nice guide for how to deploy mob programming remotely ! you can find the full write-up <a href="https://www.remotemobprogramming.org/">here</a></p><p>I hope you enjoyed reading this article and as usual please remember to share your thoughts &amp; comments below.. cheers!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d202a3285580" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scalable product managers and how to find them]]></title>
            <link>https://karim-ali.medium.com/scalable-product-managers-and-how-to-find-them-4f23e7eb051d?source=rss-4fb178da873a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f23e7eb051d</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[hiring-product-managers]]></category>
            <category><![CDATA[product-leadership]]></category>
            <category><![CDATA[hiring-tips]]></category>
            <dc:creator><![CDATA[Karim Ali]]></dc:creator>
            <pubDate>Thu, 16 Sep 2021 06:56:06 GMT</pubDate>
            <atom:updated>2021-10-10T17:01:01.718Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/558/1*-CHW9iCDo7kzT53JpClRdw.jpeg" /></figure><p>Hiring talented people takes a lot of time and considerable investment from hiring managers, throughout the past 6 years i’ve done a lot of sourcing myself, using channels like LinkedIn and Medium for doing so, and i can easily claim that i’ve conducted hundreds of interviews, looking for the very best and the very promising, looking for what i later began calling the “Scalable Product Managers”</p><p>It also happens that in one of my recent talks with a senior leader in OLX Group — the global leader of online classifieds operating in 45 countries — i was asked about how i can define these Scalable Product Managers and how can i spot them, which gave me the idea and provocation to write this article, sharing my humble thoughts with the many rather than the few.</p><h3>Definition</h3><p>I define Scalable Product Managers as those who have the ability to continuously learn new things, adapt to change and assume more responsibilities either as individual contributors or people managers during their career progression in any organization.</p><p>When we talk about individual contributors (IC) career growth, we talk about the IC product manager’s ability to assume more responsibilities adjacent to his/her current ones, this is for example if he/she leads a SCRUM team focused on the search functionality for a certain product they would have the capability to additionally oversee 1 or more other adjacent product areas like listing pages, homepage being formed into a product domain thus grow into what you can call “Domain Experts”, even if they don’t manage other PMs directly yet they still own and manage the product domain, setting the product domain strategies and overseeing execution with very heavy focus on practices and execution excellence.</p><p>Alternatively when they have the right abilities, PMs can grow into becoming people managers thus venture in the area of people leadership, retention, up-skilling, mentoring &amp; coaching, along their other responsibilities towards product practices and execution of-course. In some organizations they get the titles of Senior Managers, Directors, Heads, VPs .. etc, and they usually manage a team of 5 to 8 product managers directly.</p><h3>Characteristics</h3><p>Although a lot of things can be taught yet i consider the characteristics of scalable product managers to be absolutely organic and are usually very hard -even impossible- to teach, they were simply developed over the many years or got inherited as part of the person’s DNA, in essence this is their personality along with the influence of the environment in which they lived in, shaped by factors like where they grew up and how they grew up and where did they get their education. Changing or acquiring any of these personal traits requires a lot of self-awareness and a lot of determination coming from within.</p><p>To me, scalable product managers have 3 notable characteristics, among others of course;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IvftOIHnFiYmUBfOm_k0Vg.jpeg" /></figure><p><strong>Resilience</strong></p><p>On the strategic level, scalable PMs show the ability of being flexible enough when needed so they can get things done, they can demonstrate a strong ability in dealing with change and embracing it, in many situations you will find them open minded, willing to change course to achieve a bigger objective rather than being stuck at the specifics.</p><p>Communications-wise, you will find them able to get into deep conversations with designers, engineers, data teams, finance, operations..etc in the language that each of them understands and has the ability to demonstrate a clear T-shaped product knowledge..</p><p>On a skillset level, these types of PMs never shy away from getting their hands dirty whenever they are stuck using a wide range of tools from design tools (like Sketch, Photoshop, Figma..etc), to prototyping tools (like invision, Axur), analytics &amp; data mining tools (like Google Analytics, Looker, Tableau, excel .. etc) and even writing simple code !.. in essence they can wear multiple hats, and bounce back to their core PM scope once they finish.</p><p><strong>Persistence</strong></p><p>Scalable PMs always bring their opinions to the table, they are ambitious, comfortable getting into arguments in a positive way, and they are constantly trying to back their views by evidences.</p><p>As a hiring manager and a product leader you should simply resist hiring people who are always saying yes, building a team of order takers is not going to get you anywhere, as Marty Cagan describes in his great book -Inspired- you should always do your best to build a team of missionaries not mercenaries.</p><p>And don’t get me wrong here, i’m not talking about arrogant or thickheaded PMs here — these ones you should weed out right away and it’s easy to spot them because they usually come with weak arguments and have a repelling negative attitude — rather i’m talking about people who can dare to say no, can challenge the status quo, present different solutions to common problems, always show a positive attitude even when disagreeing and once they get their heads around something they simply go the extra miles to deliver without excuses.</p><p><strong>Curiosity</strong></p><p>Scalable PMs continuously read, listen and watch to develop their skills, they seek knowledge not because your HR team is mandating it as part of a systematic corporate employee development program or because it’s needed to get promoted, rather because they are constantly hungry for answers, hungry for progress and team advancement.</p><p>Internally, these eager PMs tend to be very active, participate in talks, help peers, connect with different people across the organization, and become a key asset in developing your product culture and brand.</p><h3>How to spot them</h3><p>I consider the art of spotting scalable PMs to be very similar in essence to what scouters do in professional sports! Referencing Wikipedia; <a href="https://en.wikipedia.org/wiki/Scout_(sport)">scouters</a> are experienced talent evaluators who travel extensively for the purposes of watching athletes play their chosen sports and determining whether their set of skills and talents represent what is needed by the scouter’s organization.</p><p>Similarly, to be successful in hiring and attracting these scalable product managers you have to have extensive knowledge in product management yourself — Obviously ! — and you need to know where to look and what to look for.</p><p><strong>Where to look ?</strong></p><p>I heavily use 2 sources for scouting; LinkedIn and Medium.. i highly recommend both as they are easily accessible, include all the information needed to spot the 3 characteristics i mentioned earlier and will enable you to “watch athletes while they are playing their chosen sport”.</p><p>Tips for LinkedIn:</p><p>First, head to search, use the term ‘Product Manager’, then select ‘People’ from the filters.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1w6lnH0IWRVmHNJS.png" /></figure><p>Second, use the ‘All filters’ menu to drill deeper, i particularly use ‘Location’ , ‘Current Company’ , ‘Previous Company’ and ‘Industry’ while looking for candidates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/924/0*VkcS9XHX_XLWS0y8.png" /></figure><p>Third, send personalized connection requests, keep your messages simple, humble and catchy,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*AOjGOjAAzU2qtG8F.png" /></figure><p>Tips for Medium:</p><p>Although Medium is not as a straight forward source of talent acquisition and will definitely take longer time from you yet with a bit of persistence it can help you recruit some of the best talents out there by reading about their experiences and ideas first.. it can be considered as the ultimate recruitment by outcome tool.</p><p>My recommendation here is to read this <a href="https://www.sourcecon.com/how-to-source-candidates-on-medium/">amazing article</a> written about how to source candidates on Medium by SourceCon, i consider it as the main go to guide. It includes the different search strings you can directly use on Google to search Medium using different operators.</p><p>Once you get your eye on a solid talent, search for them on LinkedIn using their name + title or company name and then reach out to them as you’d usually do through a personalized connection request praising the articles on Medium which they wrote.</p><p><strong>What to look for ?</strong></p><p>In recent years i became a fan of the “<em>Tell me about a time when</em>” type of interview questions to probe into how a candidate reacted in similar past situations and in the coming part i’ll discuss how you can use such type of questions as well as what aspects of the candidate’s profile/CV to look at in order to spot each of the 3 main characteristics of Scalable Product Managers;</p><p>Signs of Resilience: Here you should be looking for signs of <em>flexibility &amp; dynamism</em></p><ol><li>On LinkedIn, look at the different types of companies the candidate has worked for, have they worked for early stage startups ?, growth phase companies ?, established corporates ?..etc</li><li>Still on LinkedIn, look at the industry diversification of the candidate, have they spent their entire career working in a single industry like entertainment ? or have they gained experience working in FinTech, Ecommerce, VAS .. etc</li><li>During the interview stress on questions that assess the candidate’s ability to wear different hats; data, design, engineering, finance ..etc. Always ask them to give examples about them using each one of these skills in the past, like “tell me about a time when you got your hands dirty deep diving into a raw data set which then helped you set a direction based on your analysis”</li><li>Similarly, ask them during the interview to talk you through examples of times when they were able to deal with a failed assumption and what type of actions they took next, like “tell me about a time when one of the product features you launched with your team didn’t work out as originally expected and what did you do next”</li></ol><p>Signs of Persistence: Here you should be looking for signs of <em>overcoming difficulties or opposition</em></p><ol><li>On LinkedIn, look at the candidate’s career progression, have they been progressing properly over the years, from an associate PM to a PM to Senior PM..etc, this shows you what they had to overcome, their ability to focus and their will in getting up the career ladder.</li><li>During interviews try to probe into their ability to form an opinion, debate and handle opposition, ask them to give you an examples of to demonstrate their opinions forming and decision making skills, like “tell me about a time when you were able to rally people behind a product decision that you had to make, how did you present your opinions and how did you handle disagreements and opposition ?” .</li><li>It’s very important to introduce case studies and panel interviews to you interviewing process, case studies usually will help you understand the candidate’s ability to “talk the talk and walk the walk”, and panel interviews will further assess their abilities in handling crowds, going through arguments and overcoming stress.</li></ol><p>Signs of Curiosity: Here you should be looking for signs of <em>eagerness towards seeking knowledge &amp; asking questions</em></p><ol><li>On LinkedIn &amp; Medium, look at the candidate’s interactions, posts and articles, who they are following and what are their interests.</li><li>During interviews try to understand better about the candidate’s eagerness towards knowledge gaining, how they acquire new skills, what are their favorite books, podcasts &amp; YT channels, and which writers, product leaders or thinkers influence them.</li><li>Furthermore, leave enough time during the interview for your candidate to ask questions, an interview is not an interrogation or a one sided conversation, so make sure to give enough space for your candidate to ask and assess the types of questions they were asking, were these questions meaningful, sophisticated and compelling enough or were they asking superficial questions just for the sake of asking.</li></ol><h3>Finally…</h3><p>It’s worth sharing that not all my hiring decisions were right, i made my share of mistakes and learned along the way yet what’s really very very important here is for every hiring manager to bounce back from failures fast, if you made a wrong hire don’t shy away from confronting it, do your best first to make ends meet but if they don’t then it is what it is, cut the ties fast, and be extremely supportive to your employee during the exist. As well, you must make sure you learn from your hiring mistakes, review what has led to the wrong hire, review your hiring and onboarding processes and take corrective actions.</p><p>Remember that when you hire someone you get into a strong moral commitment which is more important to me than any legal ones, as when you offer someone to join your ranks and convince him/her to accept your offer and leave their existing employer you introduce a great deal of instability into their lives — emotional &amp; financial — even if their past employer was not as good as you or paying them lesser still they might be in a much stable position compared to the one they might get into so please keep this in mind when you let somebody go.</p><p>I hope you enjoyed reading this article and that it can help you find these amazing scalable product managers to add to your team, as usual please remember to share your thoughts &amp; comments below.. cheers!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f23e7eb051d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Eat your broccoli ! My thoughts on User Research]]></title>
            <link>https://karim-ali.medium.com/eat-your-broccoli-my-thoughts-on-user-research-e23122ad541f?source=rss-4fb178da873a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e23122ad541f</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-leadership]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Karim Ali]]></dc:creator>
            <pubDate>Mon, 13 Sep 2021 13:30:36 GMT</pubDate>
            <atom:updated>2021-09-20T09:23:51.944Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*GnCB0VqKub37FFYOLf2OmQ.png" /></figure><h3>Eat your broccoli ! A Practical Guide to User Research</h3><p>Whenever i think about user research in the context of product development, i remember broccoli ! the vegetable that is so good for your health yet tastes bad.. as a father i learned about ways to trick my 6-year-old into eating his broccolis without him knowing, thus reaping all the nutritious values minus the taste… And comparably as a product leader i also figured out ways to integrate user research into the product discovery framework of the teams i led, making it more enjoyable, accessible … and tastes better 🙂</p><p>Throughout the 2 parts of this article i’ll be sharing with you my thoughts on the importance of user research, the most common challenges facing teams and how to overcome some of these challenges through promoting good practices and people setup to empower and sponsor a user research culture across your organization.</p><h3>Part 1: What makes user research that important ?</h3><p>Let’s grasp the big picture by plotting the most common methods used by product teams during product development, what should be used earlier in the cycle VS later and what usually takes more effort hence can be considered slower to execute VS methods that can be deployed in a much easier &amp; faster way</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TgYBu-4m5W5XBmp0.png" /><figcaption>The Product Discovery Matrix</figcaption></figure><p>The term “User Research” refers to a wide range of qualitative research techniques that can help product teams answer an array of questions like;</p><ol><li>What should we build next and why ?</li><li>What pain points our customers are currently facing ?</li><li>How can we ensure a better product-market fit ?</li><li>What needs are currently being underserved ?</li><li>Are we solving the right problems with the right solutions ?</li><li>Why a specific pattern in data is happening ? what explains a specific user behavior ?</li></ol><p>In essence user research helps you answer 3 main types of questions:</p><ul><li><em>Investigative</em>, as in why a certain consumer behaviour is occurring</li><li><em>Generative</em>, as in what opportunities or underserved needs are out there</li><li><em>Evaluative</em>, as in validating which solutions solve the problem at hand and how does your users perceive it</li></ul><p>If you are already a product manager or working as part of a product team then you’ll find these 3 types of questions — and their underlying activities — quite matching to your own job description or team mandate ! <em>hence trying to continuously answer these types of questions is profoundly important for you and your team’s success in product development and in achieving product-market fit</em>.</p><p>Technically, product managers, designers or researchers spearhead user research, that means they typically should know exactly which type of research can help them answer which type of questions, how to run the research, who to involve and how to synthesize learnings collaboratively ..</p><p>Although there are different types of user research yet in most cases — especially with generative/inductive research — you will find yourself talking directly with a sample of your users in a structured manner, either online, face to face, voice to voice, in your office, on the streets or in coffeeshops &amp; shopping malls. As for evaluative research like user testing, tools like usertesting.com &amp; usabilityhub.com contributed greatly in simplifying and accelerating the execution of such research projects by offering fully remote-unmanaged research execution with a great degree of reliability and at an affordable cost.</p><p>Finally, let’s cover the most common steps found in user research projects, and please note that the below steps might differ based on the research type and setup:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*18aTCqMZG7uSsZmg.png" /><figcaption>Common Research Steps</figcaption></figure><h3>Part 2: What makes user research challenging ? and how to overcome some of these challenges ?</h3><p>I chose to highlight the following 6 challenges which i personally faced most commonly while conducting user research over the years:</p><ol><li>Dealing with the fear of talking to strangers</li><li>Finding enough time to dedicate to research projects</li><li>Defining a solid research goal</li><li>Setting the right research structure</li><li>Recruiting the research participants who represent the target audience</li><li>Documenting your research learnings in an easy to digest format</li></ol><p>The rest of this article provides additional details as well as recommendations on how to overcome each one of these challenges based on what i tried and worked. It’s worth noting that some of these recommendations will be more relevant to individual contributors and some to functional managers with more executive powers (CPOs /VPs of Product /Heads of Product..etc).</p><h4>Challenge 1: Dealing with the fear of talking to strangers</h4><p>This is the most common challenge with user research especially facing teams or individuals who are new to user research, like newly appointed product managers, designers or new entrepreneurs.. Most of us were told during our childhood to not to talk to strangers, and even as adults most of us still are not very open talking to strangers, mostly because we don’t know what to expect, will they be open, will they respond nicely, will they be rude.. etc. Leaving this fear of talking to strangers unattended will be always hamper your abilities and your team potential as well.</p><p>Recommendations for individual contributors:</p><p>Start with friendlies first, such as your friends, relatives, colleagues at work or friends of friends. Basically invite them to your research projects as research participants till you overcome your fear of talking to strangers and gain confidence by talking with people that normally you’d be comfortable talking to.. Obviously the golden rule here would be that they should fall within the target audience of your research project !</p><p>Recommendations for functional managers:</p><p>Hold hands and lead by example, train your team by carrying on research yourself at least for the first couple of researches, teach them by showing not telling. This technique is very powerful in solidifying the ties between you and your team members since you’ll be seen as the type of manager who is not afraid in getting his/her hands dirty.</p><h4>Challenge 2: Finding enough time to dedicate to research projects</h4><p>As i covered in part 1, user research projects tend to include several steps, which means that time and effort will need to be invested to get the most out of them and reach unbiased conclusions. If you skipped some of these steps or tended to deal with them in a hurry you will be basically putting the whole research outcomes at risk and you will be increasing the chances of taking wrong decisions based on inconclusive inputs.</p><p>Furthermore, not all product organizations (and or companies) can afford to have dedicated researchers with proper project management skills, and usually this task gets assigned to the product manager or designer in the team.. If you are already a product manager or designer yourself, then you’ll know the pile of other tasks on your plate and you’ll know just how hard it is to find enough time to project manage and execute research projects yourself while taking care of everything else.</p><p>Recommendations for individual contributors:</p><p>Apply the “Peanut Butter Approach” to user research. In most product orgs, you won’t be working alone, normally you will find yourself part of a team of 5 or 6 people on average, so why have all the user research fun alone while you can peanut butter it ? simply put, either you are the product manager or designer of that team, try to always up-skill your team, train them on how to do recruitment &amp; conduct user interviews, and simply share the responsibilities with them. Spreading the load of user research can be a very effective technique if done right, and comes with a massive bonus; Empathy ! , as now everyone in your team including engineers will be familiar with their users, needs, pains, and the context in which the product that they are building and shipping is used in, this on the other-hand should keep everyone in your team motivated, empowered &amp; help improve the overall product quality.</p><p>Recommendations for functional managers:</p><p>Establish a federated research organization within your department or team. In my recent years as a product leader, i used federated models in order to introduce functions like user research within my product organization where i would hire a small number of resources specialised in a certain product discipline, acting as a center of excellence, providing support, guidance and overseeing common practices. The role of these federated teams would then be to act as “enablers” not “gatekeepers”, hence their role is not to create any bottlenecks for the teams they work with, rather unblock them so they can move much faster.</p><p>You can start your atomic research team by hiring 1 senior product researcher and 1 talented research operations specialist to work together owning the below mandate:</p><ol><li>They should lead &amp; execute the most important, most complex or most impactful research projects themselves.</li><li>They should establish, safeguard and evangelize a solid framework for how research should be done in your organization.</li><li>They should continuously train product managers, designers and engineers on how to conduct user research, providing these teams with all the needed guidance &amp; templates.</li><li>They should streamline research participants recruitment, continuously driving quality research participants to needed teams so they can get unblocked.</li></ol><p>This atomic team can then be expanded whenever needed so they can support a larger number of product teams.</p><h4>Challenge 3: Defining a solid research goal</h4><p>Throughout my career i have seen teams spending much time and effort conducting user research trying to meet weak or vaguely set goals. Remember that user research is NOT the goal, rather its the mean that enable you to achieve a clearly defined research goal.</p><p>Your research goals should match the type of research you are conducting, examples of generative research goals can look like this “What are the underserved needs of young new mothers during the first year of their newborn ?” , or “What are the pains that car owners go through when they want to sell their old cars ?”</p><p>Recommendations for individual contributors:</p><p>Make sure that your research goal is well written before hand, discussed with your research team and whoever is going to involved in your research project such as your close stakeholders. Your research goal should be specific enough to enable you and the team know whether you have met the goal or no ! otherwise you’ll go into an infinite loop of research, not knowing when to draw conclusions.</p><p>When you finalize all the users interviews it’s always very important to meet with the rest of the team who attended these interviews as observers or note takers for a research briefing and conclusion, during these meetings make sure that you also review and assess the goal which you started with, conduct a retro and define what can be improved in the next cycle along with the research next steps.</p><p>Recommendations for functional managers:</p><p>Continuous engagement and coaching would be my advice here, make sure that you are getting yourself very close to the research projects being conducted, and establish a panel for the research outcomes to be collectively shared &amp; discussed.</p><p>During my recent years as a VP of product, i used to organize and host a bi-weekly insights cadence involving my product managers, designers and stakeholders where we discussed the learnings of the different types of research projects that were concluded along other qualitative customer driven insights.</p><p>Once you start conducting such type of bi-weekly meetings, you will be able to spot research projects which seem to be in limbo, with multiple reruns or inconclusive outcomes, when you spot such projects you should then start an offline discussion with the concerned team to deep dive and review the set goal and practices they are following, this should give you a prime opportunity to guide your team through the adjustments they need to consider.</p><h4>Challenge 4: Setting the right research structure</h4><p>As mentioned earlier, i tend to classify user research into 3 main types; generative, evaluative and investigative. Depending on your research goal you should select the right research type to conduct, the common here is that you’ll definitely have to interview users, ask them questions and listen a lot more than talking, yet the questions you might structure will differ based on the type of research you want to run.</p><p>Developing the research questionnaire is a very crucial and challenging aspect of your research project, as even if you got everything else right yet during the interviews you ask the wrong questions then you’ll definitely come to wrong conclusions.</p><p>It’s not uncommon to combine multiple types of questions within the same interview session as long as the questions are related to the same research topic/goal, and as long as you won’t overly exhaust your research participants or take any over time, as this might lead them to give you all sorts of answers just to get over with your research so they can leave !</p><p>Recommendations for individual contributors:</p><p>Throughout this article, you’ll find me stressing on the value of inclusion and involvement of other team members in your research to maximize it’s success opportunities, and my advice to overcome the 4th challenge won’t be much different, you have to keep the right people included in the right way.</p><p>Now i want you to think about research projects in a way that is similar to how you think about running your SCRUM sprints — that of course if you use sprints to begin with — every sprint should begin with a sprint planning session involving the SCRUM team and it should end with a retro and a review.</p><p>So start your research projects with a planning meeting where you’d invite the team that will be involved in the user interviews as well as your most relevant business stakeholders, during the planning session you should deep dive into the research goal and questionnaire with the group, make sure that they get well discussed, adjusted and agreed upon before moving forward.</p><p>Another advice while working on your interview questions, remember that they shouldn’t be persuasive, they shouldn’t include the answers, and they shouldn’t be as if you want to prove your own ideas to yourself, which is called confirmation bias. Remember to fight your own bias and try to keep an open &amp; eager mind.</p><p>Recommendations for functional managers:</p><p>Work towards setting common guidelines, either yourself or with your dedicated researcher involved. The purpose of having common guidelines in place is to make sure that your product teams are well supported with the best practices that can limit the time they take in trial and error.</p><p>If you were able to hire the dedicated researcher i mentioned in challenge #2 then basically this person should lead such an effort to establish a working framework that enable product teams conduct user research in the right way.</p><p>I also advice you to consider the below aspects while working on your company’s user research framework:</p><ol><li>The framework should define clearly the different types of research, along with the recommended setup, practices &amp; tools.</li><li>The framework should define the contribution model, as in who should be involved in research projects and how.</li><li>The framework should be published online for example on your confluence project or whatever you use for documentation as long as it can be widely available and easily accessible.</li><li>The framework should and its documentation should be dealt with as a living organism, hence it should be continuously audited, reviewed and updated through multiple revisions.</li><li>Avoid developing a framework that is rigid with low levels of resilience, as this will most probably be a DOA piece of work</li></ol><h4>Challenge 5: Recruiting the relevant research participants</h4><p>Recruiting research participants is maybe the biggest challenge and the most time consuming one, and it also drives the biggest risk if done wrong.. Imagine if you are developing a new product to be used by orthopedics yet you wrongfully recruited ophthalmologists to be part of your research ! absolutely 2 different branches of medicine all together, none of the feedback given — if they actually were able to give any — will be relevant to the research goal in this case.</p><p>Recommendations for individual contributors:</p><p>While you might need some very minor development help with this, yet there are ways you can help yourself and your team get unblocked:</p><ol><li>Implement in-product, always-on research participants recruitment touch points, which can be easily done via tools like braze for in-app messaging. Most effectively run your recruitment campaigns towards the very end of your product funnel so they won’t disturb the user flow.</li><li>Land your recruitment campaign on a simple google form or a Qualtrics Survey to ask screening questions, this is very important to make sure you are recruiting the right participants for your research. For example, questions that would let you know the participant demographic, context of use of your product, frequency of use of your product, other similar products that they also use .. etc</li></ol><p>Implementing these 2 tactics should give your recruitment capacity a nice boost, enabling you to focus on screening effectively.</p><p>Recommendations for functional managers:</p><p>Most effectively, hire the research operations specialist. I discussed the federated product research model above, and what makes the role of the research operations specialist very important and very interesting, is because of the effect this person creates by acting as a catalyst, he/she will not only be owning the continuous research participants recruitment, but also manage the research participants lifecycle from beginning to end.</p><p>Below is how i define the research operations specialist scope of work:</p><ol><li>Own the implementation of recruitment campaigns both on and off product.</li><li>Own and manage the research calendar, as in who is expected on what day and time.</li><li>Manage all research participants communications pre and post interview.</li><li>Run post interview feedback surveys with those who participated in the research interviews.</li><li>Ensure participants rewarding post interview, like giving voucher codes or freebies.</li></ol><p>The role of the research operations specialist is very flexible and can scale nicely with your investment in user research.</p><h4>Challenge 6: Documentation</h4><p>A lot of teams overlook the importance of documentation and it’s not a surprise, remember that in most small and medium sized companies research projects are owned by the product manager or designer themselves, who are also very driven by execution speed and don’t usually have enough time to write detailed research summaries yet also remember that your research outcomes must be available in an easy to share format so you can share it with your other team members (engineers++), stakeholders and other functional heads whenever needed to secure a common understanding and get their buy in.</p><p>Recommendations for individual contributors:</p><p>Well let’s put it this way, no one is expecting you to write a book or a 300-pages thesis 🙂 , by documentation i mean the bare minimum amount of written information that can help an outsider — or a future self — know what was the purpose of the research, what was the composition of the research participants who took part of it, what were the key outcomes and decisions taken.. in other words your research document should answer the why, the who &amp; the what, a 3 or a 4 pager document which is well written should be sufficient in most cases.</p><p>As with all documentation i always encourage my teams to stay organized, keep everything hosted on the cloud, and openly shared internally.. there are no secrets and literally everyone in your company should have easy access to the research learnings.</p><p>Along with the written piece of documentation, i always ask my teams to record the sessions and keep recordings uploaded online as well for future reference and further deep dives if required. Keeping recordings as well will help you a lot with learnings summarization and extracting exact user quotes to enrich your narrative.</p><p>Another humble recommendation to help you during your documentation journey, which is to write your research document iteratively, start with an initial document that states the research goal, questions and desired target participants, then add to it as you go, step by step, this way you won’t feel the burden of writing it all at once going through your memory lanes and scrap notes.</p><p>Recommendations for functional managers:</p><p>What functional managers can add as a meaningful contribution is to help their teams with tooling and creation of sample writing guidelines, from my personal experience i can recommend the below very helpful tools:</p><ol><li>Create and use a shared google drive as an online research library for video recordings, and make sure it’s shared with your team.</li><li>Create a “store front” for your research library using Google Sites, which is very simple yet powerful to use, and make it available internally.</li><li>Keep your internal guidelines &amp; framework documentation on Confluence if you use the Atlassian suite of apps or GDocs if you don’t.</li></ol><p>Aside the above, it’s very important for you to keep coaching your team, keep reminding them, be actively share notable research outcomes with upper management and other executive peers to keep them excited about research and most importantly aware of the voice of customers.</p><h4>The bottomline…</h4><p>As with broccoli, the trick is to <em>blend it </em>with other ingredients which makes it as hidden as possible :) if you are cooking pasta, blend it with the tomatoes to make a sauce, if you are cooking homemade burger then just mix it with the meat, i guess you got the point .. Simply: blend it, hide it, till your kid develops the habit of eating it.</p><p>Similarly, if you are the head of your product organization, then you can use the same tactic, blend user research into your product development lifecycle, streamline it’s known challenges to make it as seamless as possible, and bit by bit your team will fall in love with it, and hence turns into a habit.</p><p>It definitely takes time and persistence to strengthen the research muscle in any organization — which is almost true for many of our product practices — but no matter the challenge you face there will be always a way out..Throughout this article my intention was to share the common challenges i personally faced during my years in product development, and how i was able to overcome them, both as an individual contributor and later as a senior leader of a large product organization.</p><p>I hope my humble learnings &amp; recommendations can help you out and please remember to share your thoughts &amp; comments below.. cheers !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e23122ad541f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>