<?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 Gisoo Garmeki (Ux|Ui designer) on Medium]]></title>
        <description><![CDATA[Stories by Gisoo Garmeki (Ux|Ui designer) on Medium]]></description>
        <link>https://medium.com/@gisoogarmeki?source=rss-1a70cdff49a7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*kGAVwnNTWrzAhWgvCQI6LQ@2x.jpeg</url>
            <title>Stories by Gisoo Garmeki (Ux|Ui designer) on Medium</title>
            <link>https://medium.com/@gisoogarmeki?source=rss-1a70cdff49a7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 23:11:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gisoogarmeki/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[Product Strategy and Strategic Planning Framework]]></title>
            <link>https://medium.com/@gisoogarmeki/product-strategy-and-strategic-planning-framework-5e9fc8267d0d?source=rss-1a70cdff49a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e9fc8267d0d</guid>
            <category><![CDATA[strategy-planning]]></category>
            <category><![CDATA[product-mission]]></category>
            <category><![CDATA[product-strategy]]></category>
            <category><![CDATA[product-vision]]></category>
            <category><![CDATA[strategy-framework]]></category>
            <dc:creator><![CDATA[Gisoo Garmeki (Ux|Ui designer)]]></dc:creator>
            <pubDate>Tue, 05 Dec 2023 19:54:02 GMT</pubDate>
            <atom:updated>2023-12-05T19:54:02.817Z</atom:updated>
            <content:encoded><![CDATA[<p>Product strategy involves the planning and executing development and management of a product or service. it involves identifying the target market, defining the features and benefits of the product, and determining the pricing, distribution, and promotion strategy that will be used to bring the product to market. effective product strategy requires to deep understanding of the target market, the competition, and the industry landscape, as well as the ability to adapt and adjust the product as needed in response and changing market conditions and customer needs.</p><h4>How a strategic planning framework can help you achieve your big goals?</h4><p>a strategy planning framework is a tool that your team uses to focus on and fill a specific element of your strategy plan. you&#39;ve got big ideas and bigger goals for your company. may you’re set on making the world a better place(hey, aren’t we all?). Or maybe you want to be known for unmatched customer care. Regardless of your specific aim, your whole team is gung-ho about your mission.</p><p>But now’s the hard part: How do you transform that idea into an actionable strategy? The strategic planning process can be daunting, but a strategic planning framework can help. You’ll use your framework (or frameworks) to tackle a specific piece of the strategic planning process with zero confusion and eye-rolls, and plenty of energy and enthusiasm.</p><h4>Who needs a strategic planning framework?</h4><p>Here’s the short answer: Anyone who’s completing a strategic plan, whether it’s a strategic plan for a single project or an entire organization.</p><p>The good news is that these frameworks are way more straightforward than you think. Anyone from your grandma to your dog will be able to use them.</p><h4>What is a strategic planning framework?</h4><h3>A strategic planning framework is a tool you and your team will use to focus on a specific element of your strategic plan.</h3><p>Your entire strategic plan needs to cover a lot, including:</p><ul><li>Where you are now</li><li>Where you want to go</li><li>How you’ll achieve those goals</li></ul><p>Pulling all of that together can be overwhelming, but a strategic planning framework will help you chip away at that iceberg.</p><p>For example, you could use the objectives and key results (OKRs) framework to iron out the goals included in your strategic plan. Or, you might use the framework called Porter’s five forces (we’ll cover this later) to dig into your competition and understand how competitive factors will impact the future of your organization.</p><p>Strategic planning frameworks help you dig deep into a specific section of your plan, so you can create something comprehensive that actually helps you turn ideas into action.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/860/0*GRoIIbN7jGC02Ays" /></figure><h4>Strategic planning frameworks vs. models: One of these things is not like the other</h4><p>Many people use the terms “strategic planning framework” and “strategic planning models” interchangeably. However, the terms represent two parts of a whole.</p><p>Your strategic planning model provides a high-level overview of all of the elements of your strategic plan. Your model comes first, as it dictates the structure of your entire plan.</p><p>Tom Wright, CEO and co-founder of Cascade Strategy, a strategy execution platform, likens it to building an airport. “A model of the airport would show you at a high-level how the approach roads connect to the departure hall, and how the departure hall connects to immigration, which then connects to the terminals, the runways, etc.,” he writes in a <a href="https://www.executestrategy.net/blog/strategy-planning-models#:~:text=Another%20way%20to%20put%20it,detail%20within%20our%20strategic%20plans.">blog post</a>.</p><p>In contrast, frameworks help you fill in different elements with specific information.</p><p>“In our airport example, we might apply a building framework that is designed to maximize the speed at which people move through the airport for efficiency,” Wright adds. “Or alternatively, we might apply a framework which is designed not to maximize speed, but rather to maximize the amount of time people spend in the airport shops.”</p><p>The model encompasses all pieces of your strategic plan, but your framework is your approach for a specific piece. Think of your model as the forest, and your different frameworks as the trees. You’ll only use one strategic planning model, but you can use numerous frameworks.</p><h4>8 strategic planning frameworks to hash out your strategy with confidence</h4><p>You’ll use different frameworks for different aspects of your strategic plan, from developing your action items to evaluating your competitors.</p><p>Here are eight of the most common strategic planning frameworks, and which piece of your strategy they can help you with.</p><h4>1. SWOT analysis</h4><p>Use this framework: To grasp what internal and external factors can impact your strategy</p><p>SWOT stands for strengths, weaknesses, opportunities, and threats. Strengths and weaknesses are internal factors (meaning you have some control over them), while opportunities and threats are external factors (and you have little to no control).</p><p>Get your team together for a brainstorming session where you can tackle each category. Using our customer service example, you might determine:</p><ul><li>Strengths: We have a new and innovative product that people love.</li><li>Weaknesses: Our customer ticketing system is outdated and ineffective.</li><li>Opportunities: Customers have a growing interest in chat support, which we could roll out relatively easily.</li><li>Threats: All of our competitors are prioritizing customer service.</li></ul><p>You’ll use this framework at the beginning of your strategic planning process, as it helps you understand where things are going well for your company — as well as where you need to improve. That’s important information as you hash out your strategy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/860/0*hx6nMhioMctuArVY" /></figure><h3>2. Issue-based strategic planning</h3><p>Use this framework: To build a strategic plan that addresses your organization’s biggest problems</p><p>While most of the strategic planning frameworks start with objectives (where you look to the future), this one starts with problems (where you look to the present). You’ll identify the challenges your organization is facing right now and create action plans to address them.</p><p>This is another framework that you’ll use at the very beginning of the strategic planning process, as it will shape your entire plan.</p><p>Start by asking: What are the biggest problems our organization is dealing with?</p><p>Perhaps you’ll realize that your customer feedback scores are plummeting. From there, your strategic plan should detail the steps you’ll take to resolve that issue.</p><h4>3. Balanced scorecard</h4><p>Use this framework: To define your goals and the steps you’ll take to get there</p><p>A balanced scorecard (BSC) outlines what your team or organization is trying to accomplish, as well as what work everybody needs to do in order to make it happen. It’s helpful for understanding objectives, connecting and prioritizing day-to-day work, and monitoring progress using established metrics.</p><p>With this framework, you’ll need to identify:</p><ul><li>Objectives: The goal you want to achieve (i.e. be looked to as the industry standard for quality customer care)</li><li>Measures: How you’ll define success (i.e. average customer feedback score of B+)</li><li>Initiatives: Programs established to achieve objectives (i.e. launch a new customer ticketing system to manage your customer support cases)</li><li>Action items: Individual steps one person or a small team will take (i.e. Rico will research ticketing software, Sarah will complete the migration from our current platform, etc.)</li></ul><p>See how you move from the big, seemingly unattainable goal all the way down to bite-sized actions you can take? That’s the beauty of a balanced scorecard — it connects your organization-wide goals to the daily tasks of everybody on the team.</p><h4>4. Strategy mapping</h4><p>Use this framework: To understand how all of your company’s objectives fit together</p><p>A strategy map is often used as a supplement to your balanced scorecard. You’ll list every objective from your balanced scorecard on your strategy map. It should be represented by a shape.</p><p>Next, you’ll group objectives into different perspectives. Think of these as buckets or themes for similar goals. The most common perspectives are:</p><ul><li>Financial</li><li>Customer</li><li>Internal business processes</li><li>Learning and growth</li></ul><p>Once all of your ovals are drawn out, you’ll draw arrows between them to show cause and effect. Does one objective have a direct impact on another?</p><p>For example, perhaps boosting the expertise of your customer service team (perspective: learning and growth) directly impacts your ability to provide top-notch customer care (perspective: customer).</p><p>Your strategy map can become a living resource, and you can color-code your objective bubbles (green, yellow, and red) to show your progress toward that objective.</p><h4>5. Objectives and key results (OKRs)</h4><p>Use this framework: To keep a close eye on progress</p><p>Objectives and key results (OKRs) is a popular goal setting methodology to help teams go after audacious goals. With this framework, you’ll identify:</p><ul><li>Objectives: What you want to achieve</li><li>Key results: How you’ll measure your progress</li></ul><p>Keep in mind that your key results need to be quantitative, measurable outcomes and not tasks or to-dos. So, sticking with our example of world-class customer service, a key result could be, “Secure 25+ five-star reviews by the end of Q2.”</p><p>OKRs are designed to be ambitious, and you don’t want to overdo it and overwhelm your team. Set only three to five at a time (this template can help) to make sure they’re motivating, and not anxiety-inducing.</p><h4>6. Porter’s five forces</h4><p>Use this framework: To understand the ins and outs of your existing and prospective competitors</p><p>Most strategic plans include a section for competitive analysis, and Porter’s five forces is a framework you’ll use to fill in that section. The five competitive forces you’ll identify are:</p><ul><li>Competition in the industry: Are your competitors growing rapidly?</li><li>Potential of new entrants into the industry: Are a lot of new players able to easily enter your market and thrive? Or is it tough to get going?</li><li>Power of suppliers: How much bargaining power do your suppliers have to pressure you to lower costs?</li><li>Power of customers: How much bargaining power do your customers have to pressure you to lower costs?</li><li>Threat of substitute products: Is your product easily replaced with another product? Or are you one-of-a-kind?</li></ul><p>Your competition will shape your strategy, and this framework will help you understand how. If you realize that there’s a high threat of substitute products, then maybe differentiating yourself needs to be a key piece of your strategic plan.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/860/0*nKnTp4zaBTVwvAoa" /></figure><h4>7. Gap planning</h4><p>Use this framework: To determine how you’ll close the gap between where you are and where you want to be.</p><p>You have a strong vision for your organization. Maybe that vision feels like it’s within arm’s reach, or maybe it feels like it’s still miles and miles away.</p><p>Either way, bridging the gap between where you are now and where you want to be is no easy task. That messy middle is where all of the hard work happens.</p><p>That’s where gap planning (also called a needs assessment) comes in. It zeros in on everything you need to do to move from your current state to your vision. When you analyze a gap, you need to challenge yourself to think about why you haven’t achieved your ideal state. What’s the root cause?</p><p>Here’s a very simple example of what this could look like:</p><p>Vision: Reputation for industry-leading customer service</p><p>Current state: Good customer service, but not great (average feedback score of B-)</p><p>Gap: Customer service representatives are using outdated software</p><p>Improvement: Implement a new ticketing system to support the customer service team</p><p>This framework is another way to break your vision down into more tactical steps and improvements.</p><h4>8. PEST analysis</h4><p>Use this framework: To understand the external factors that can impact your company</p><p>When drafting your strategic plan, you can’t just think about what’s happening internally — you also need to think about what’s happening externally. A PEST analysis will help you take a holistic look at the environment your company is operating in.</p><p>PEST stands for political, economic, sociocultural, and technological, and this framework requires that you determine how each of those factors could impact your company’s overall health. Here are a few (of many) examples:</p><ul><li>Political: Are there a lot of government regulations that dictate how your industry can correspond with customers?</li><li>Economic: Are customers in your industry watching their wallets closely?</li><li>Sociocultural: Do customers expect an increasingly fast response?</li><li>Technological: Are you operating with outdated customer ticketing software?</li></ul><p>These are important considerations to make, so you avoid hashing out a strategy that doesn’t align with what’s happening around you.</p><h4>Strategic planning frameworks vs. models: One of these things is not like the other</h4><p>There are plenty of strategic planning frameworks to choose from, and one isn’t inherently better than the others. They all serve different purposes.</p><p>So, when you need to choose a framework, start with your goal and work backward from there.</p><p>Do you need to identify clear action items? Then gap planning or a balanced scorecard are your best bets. Do you want to understand the impact of outside forces? Look at a PEST or SWOT analysis.</p><p>Keep in mind that you don’t have to choose only one. You can use different frameworks for different stages and elements of your strategic planning process. Plus, strategic plans are often revisited and reevaluated. You might require a different framework as your plan and company evolve over time.</p><p>Regardless of which framework(s) you use, you’ll want to keep your strategic plan and all of your supporting documentation somewhere organized and accessible. Your strategic plan doesn’t do any good if it sits and collects digital dust. A collaborative workspace like <a href="https://www.atlassian.com/software/confluence">Confluence</a> makes it easy for your entire team to reference that information whenever they need it.</p><h4>Goals require strategy (and action)</h4><p>Coming up with goals is easy. The hard part is figuring out how you’ll achieve them.</p><p>Your strategic plan takes your high-level vision and breaks it down into actionable steps you’ll take to make it happen.</p><p>The strategic planning process itself can sound dry and daunting, but a strategic planning framework makes it way easier to dig into the details of every element of your strategic plan.</p><p>Use one (or even a few) of the eight frameworks we discussed here, and you’ll be ready to take action on your company’s most ambitious goals.</p><p>Document all of your company’s goals, plans, challenges, and more. Check out the Confluence template gallery to make knowledge sharing even easier.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e9fc8267d0d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product vision and mission]]></title>
            <link>https://medium.com/@gisoogarmeki/product-vision-and-mission-e867773346cd?source=rss-1a70cdff49a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/e867773346cd</guid>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[product-vision]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[product-mission]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <dc:creator><![CDATA[Gisoo Garmeki (Ux|Ui designer)]]></dc:creator>
            <pubDate>Thu, 30 Nov 2023 13:45:48 GMT</pubDate>
            <atom:updated>2023-11-30T14:07:31.490Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><em>“If you want to build a ship, don’t drum up the men to gather wood, divide the work, and give orders. Instead, teach them to yearn for the vast and endless sea.” — Antoine de Saint-Exupéry.</em></blockquote><p>product vision and mission are essential components and overall strategy of the companies, but they follow distinct purposes. I have collected a breakdown of the difference between product vision and product mission:</p><h4>product vision</h4><p>Product vision is a long-term view or aspirational statement that outlines the desired feature state of the products. by focusing on the impact and value of the product aims to deliver to its user or the boarder market. typically it takes many years of time and provides a guiding direction for the product evolution. the product vision by articulating a compelling picture of what the product could become, it causes inspires, and motivates the product team.</p><p>For Example: “To revolutionize the way people communicate by providing a seamless, intuitive, and globally accessible messaging platform that connects individuals and communities.”</p><h4>product mission</h4><p>product mission is a more specific statement that outlines the purpose of the product, the target audience, and the fundamental value that guides its development. focus mission, it emphasizes the current purpose and core functionality, and benefits the product provides to users. timeframe mission, product mission often is immediate and focuses on what the product is doing now to achieve its purpose. product mission guides day-to-day decisions and actions, helping the team stay aligned with the product purpose.</p><p>For Example: To empower businesses with a user-friendly project management tool that increases collaboration, increase efficiency and enables the team to achieve their goals.</p><h4>In summary:</h4><p>while the product vision paints a broad and inspirational picture of the future, the product mission is more focused on the present, describing the product’s current purpose and how it serves its users. Both are crucial for providing direction and purpose to the product team and aligning their efforts with the overall goals of the organization. Remember, the product vision needs to be persuasive. It needs to inspire. Have you ever been inspired by a canvas or board?<br>This is why so many companies invest real energies into putting this product vision into a compelling medium. Increasingly that’s a video of a visiontype, which is a special form of prototype. They dramatize the user experience. They show how our customer’s lives demonstrably and emotionally improve.</p><h4>There is a link at below to more understand this approach:</h4><p><a href="https://www.youtube.com/watch?v=zpzZumZCdWA">https://www.youtube.com/watch?v=zpzZumZCdWA</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e867773346cd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[product thinking]]></title>
            <link>https://medium.com/@gisoogarmeki/product-thinking-101-6d8ec82d0501?source=rss-1a70cdff49a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d8ec82d0501</guid>
            <category><![CDATA[ux-ui-product-designer]]></category>
            <category><![CDATA[product-thinking]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Gisoo Garmeki (Ux|Ui designer)]]></dc:creator>
            <pubDate>Sun, 26 Nov 2023 20:31:47 GMT</pubDate>
            <atom:updated>2023-11-28T12:37:01.232Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>product thinking is a mindset and approach to problem-solving that focuses on creating valuable and meaningful products and experiences for users. product thinking comes from our mindset. it includes understanding the needs, and motivations of users, identifying opportunities to create value. and continuously iterating and refining products to meet the evolving needs and expectations of the target audience. product thinking involves a holistic and user-centered approach to product development, considering not just the technical and functional aspects of the product, but also the emotional and psychological impact it has on users.</blockquote><p>In this article, I will try to mention four basics of product thinking:</p><ul><li>Why is product thinking important?</li><li>How can you cultivate product thinking?</li><li>what is the product thinking process?</li></ul><h4><strong>then what is the product thinking?</strong></h4><p>product thinking is a journey from the problem space of the users to the solution space. and the goal of this journey is to reduce the gap between users and the business.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gYtqPGzuW_GDruXqCzZTpg.jpeg" /></figure><h4><strong>why is product thinking important?</strong></h4><p>Product thinking is crucial in the development and success of any product, as it shifts the focus from merely building features to creating value for users. Here are several reasons why product thinking is important:</p><blockquote><strong>User-Centric Approach: </strong>Product thinking emphasizes understanding the needs, desires, and pain points of the end-users. By putting users at the center of the product development process, you increase the likelihood of creating a product that truly solves their problems.<strong><br>Problem-Solving Orientation: </strong>Instead of just implementing features, product thinking encourages a problem-solving mindset. It involves identifying and solving real-world problems that users face, which leads to the development of more meaningful and impactful products.<br><strong>Continuous Iteration: </strong>Product thinking promotes an iterative approach to development. It encourages teams to release minimum viable products (MVPs) quickly, gather feedback, and make improvements based on user insights. This iterative cycle helps in adapting to changing user needs and market dynamics.<br><strong>Market Fit: </strong>Understanding the market is essential for a product’s success. Product thinking involves market research, competitor analysis, and a deep understanding of industry trends. This ensures that the product not only meets user needs but also fits well within the current market landscape.<br><strong>Focus on Value Creation:</strong> Rather than getting bogged down by a list of features, product thinking emphasizes delivering value. It’s about creating products that solve specific problems and deliver tangible benefits, which, in turn, increase user satisfaction and loyalty.<br><strong>Cross-functional collaboration: </strong>Product thinking encourages collaboration between various teams, including product managers, designers, developers, and marketers. This interdisciplinary approach ensures that everyone is aligned with the overall product vision and works towards common goals.<br><strong>Adaptability to Change: </strong>The business landscape is dynamic, and technology evolves rapidly. Product thinking equips teams with the mindset and processes to adapt to changes quickly. This adaptability is crucial for staying ahead of the competition and responding to emerging trends.<br><strong>Data-Driven Decision Making: </strong>Product thinking relies on data and analytics to inform decisions. By collecting and analyzing relevant data, teams can make informed choices about feature prioritization, improvements, and future directions, reducing the reliance on gut feelings or assumptions.<br><strong>Long-Term Sustainability: </strong>A product that is built with a deep understanding of user needs and market dynamics is more likely to have long-term sustainability. Rather than being a short-lived solution, a product developed with product thinking principles is better positioned to evolve and remain relevant over time.<br>In summary, product thinking is important because it aligns the development process with user needs, encourages a problem-solving mindset, and ensures that products are not just a collection of features but valuable solutions that meet market demands.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6Njp0qUIWkIvnB8tnBlgrA.jpeg" /></figure><p>what can businesses do to avoid this pitfall? how can product thinking to alleviate this situation? let&#39;s look at the basic heuristics of product thinking, more like thump rules to follow obscure failure.</p><h4><strong>rule 1: love the problem, not your solution</strong></h4><p>Love the problem, not your solution” is a mantra often associated with the concept of product thinking and user-centered design. This principle encourages product teams and innovators to focus on understanding and addressing the underlying problems or needs of users rather than becoming too attached to a specific solution or idea.<br><strong>understanding the problem:</strong> Before developing a product or solution, it’s crucial to deeply understand the problem you are trying to solve. This involves empathizing with users, conducting research, and identifying the root causes of their challenges.<br><strong>Avoiding Solution Biases: </strong>Sometimes, when teams come up with a solution or idea, there’s a natural tendency to become attached to it. This attachment can lead to confirmation bias, where teams focus on proving their solution right rather than objectively assessing whether it truly addresses the user’s problem.<br><strong>Being Open to Iteration: </strong>“Loving the problem” means staying focused on the user’s needs and being open to iterating on your solution based on user feedback. It encourages a mindset of continuous improvement and adaptation, allowing for the development of more effective and user-friendly solutions.<br><strong>Pivoting When Necessary: </strong>If evidence suggests that the initial solution isn’t adequately addressing the user’s problem, teams should be willing to pivot and explore alternative approaches. This flexibility is a key aspect of successful product development.<br><strong>User-Centric Design:</strong> The phrase underscores the importance of putting the user at the center of the design and development process. By maintaining a user-centric focus, teams can create products that truly resonate with and meet the needs of their target audience.<br>In essence, “Love the problem, not your solution” encourages a mindset shift from being attached to a specific idea to being committed to solving a real user problem. It promotes a culture of empathy, curiosity, and a willingness to adapt based on user insights, ultimately leading to more successful and user-friendly products.</p><h4><strong>rule 2: think about products, not the features</strong></h4><p>“Think in products, not in features” is another key principle associated with product thinking. This perspective encourages a holistic approach to product development, emphasizing the creation of a comprehensive solution rather than just a collection of individual features.<br><strong>User-Centric Value: </strong>Instead of focusing solely on adding features, consider the overall value that your product provides to users. Understand the problems your users face and think about how your product, as a whole, can address and solve those problems effectively.<br><strong>Solving Real Problems: </strong>Products are designed to solve problems or fulfill the needs of users. Rather than thinking about features in isolation, consider how a combination of features can work together to provide a complete and meaningful solution to the user’s pain points.<br><strong>Coherent User Experience: </strong>A product-oriented mindset encourages a seamless and coherent user experience. Instead of viewing features as standalone elements, think about how they integrate with one another to create a unified and intuitive user journey.<br><strong>Market Fit: </strong>When thinking about products, you consider how your offering fits within the broader market landscape. This involves understanding your target audience, analyzing competitors, and ensuring that your product not only meets user needs but also aligns with market trends and demands.<br><strong>Prioritization Based on Impact: </strong>Rather than prioritizing features based on individual requests or preferences, prioritize them based on their impact on the overall product and user experience. This strategic approach ensures that you’re building features that contribute significantly to the product’s success.<br><strong>Iterative Development: </strong>Product development is an iterative process. Instead of releasing a set of features all at once, focus on releasing a minimum viable product (MVP) and then iteratively improving and expanding based on user feedback and evolving needs.<br><strong>User Feedback-Driven: </strong>Products evolve based on user feedback. Encourage a feedback loop where user insights inform not only individual feature enhancements but also guide the overall product roadmap and strategy.<br><strong>Long-Term Vision: </strong>Thinking in products involves having a long-term vision for your offering. Consider how your product can grow and adapt over time to remain relevant and valuable in the market. This includes planning for future features and enhancements that align with the overall product strategy.<br>In summary, “Think in products, not in features” encourages a strategic and user-centric approach to product development. It’s about creating a cohesive, valuable, and market-responsive product that goes beyond the sum of its individual features. This mindset contributes to the sustained success and user satisfaction of the product.</p><h4><strong>Rule 3: Have your product heuristics in place before writing the first line of your code</strong></h4><p>Absolutely, having product heuristics or guiding principles in place before writing the first line of code is a wise approach to product development. Product heuristics are a set of broad rules or guidelines that help steer the decision-making process throughout the development lifecycle.<br><strong>Clarity of Purpose: </strong>Defining heuristics forces the team to clearly articulate the purpose and goals of the product. This clarity ensures that every subsequent decision aligns with the overarching vision.<br><strong>User-Centric Focus: </strong>Heuristics should be grounded in an understanding of user needs and behaviors. This user-centric approach ensures that the product is designed and built to address real problems and provide meaningful value to users.<br><strong>Consistency Across Features: </strong>Having heuristics in place helps maintain consistency across different features and components of the product. This consistency contributes to a more cohesive user experience.<br><strong>Guidance for Decision-Making: </strong>Heuristics serve as a guide for decision-making throughout the development process. When faced with choices about features, design, or functionality, teams can refer back to the heuristics to ensure alignment with the product’s core principles.<br><strong>Early Alignment: </strong>By establishing heuristics early in the process, you align the entire team — product managers, designers, developers, etc. — around a common set of principles. This shared understanding helps prevent divergence in the later stages of development.<br><strong>Risk Mitigation: </strong>Heuristics can help identify potential risks or challenges early on. If a proposed feature or decision contradicts the established heuristics, it prompts the team to reevaluate and mitigate potential issues before investing significant resources.<br><strong>User Experience (UX) Design Foundation: </strong>Heuristics often contribute to the foundation of UX design. They guide decisions related to usability, accessibility, and overall design principles, ensuring a positive and effective user experience.<br><strong>Scalability and Future-Proofing: </strong>Heuristics can contribute to the scalability and future-proofing of the product. They guide decisions about architecture and technology choices that align with the long-term vision for the product.<br><strong>Feedback Loops: </strong>Heuristics provide a basis for setting up feedback loops. Regularly evaluating the product against the established heuristics allows teams to learn, iterate, and continuously improve.<br><strong>Stakeholder Alignment: </strong>Clearly defined heuristics help in aligning not just the internal team but also external stakeholders, such as investors, customers, or partners. It sets expectations and provides a framework for evaluating the success of the product.<br>In summary, having product heuristics in place before writing code sets the foundation for a focused, user-centric, and strategically aligned development process. It helps avoid ad-hoc decision-making, promotes consistency, and contributes to the overall success and sustainability of the product.</p><h4><strong>How can you cultivate product thinking?</strong></h4><p>Cultivating product thinking involves developing a mindset that prioritizes understanding user needs, solving real problems, and creating valuable solutions. Here are several strategies to help you and your team cultivate product thinking:</p><p><strong>Understand Your Users:</strong> Invest time in understanding your users deeply. Conduct user interviews, surveys, and usability testing. Develop empathy by putting yourself in the user’s shoes to better comprehend their needs, challenges, and goals.<br><strong>Define Clear Problem Statements:</strong> Clearly articulate the problems you’re trying to solve. Instead of jumping to solutions, ensure that everyone on the team has a shared understanding of the problem you’re addressing. A well-defined problem statement guides the development of effective solutions.<br><strong>Prioritize Value Over Features:</strong> Shift the focus from building a laundry list of features to delivering value. Identify the core features that will provide the most significant impact and value to users. Prioritize these features and avoid feature bloat.<br><strong>Build Iteratively and Learn Quickly:</strong> Embrace an iterative development approach. Release minimum viable products (MVPs) quickly, gather user feedback, and use that feedback to make improvements. Learning from user interactions and iterating based on those insights is a key aspect of product thinking.<br><strong>Encourage Cross-Functional Collaboration: </strong>Foster collaboration between product managers, designers, developers, marketers, and other relevant teams. Cross-functional collaboration ensures that everyone is aligned with the product vision and works towards common goals.<br><strong>Embrace Failure as a Learning Opportunity:</strong> Encourage a culture where failure is viewed as a learning opportunity. Failures are inevitable in innovation, and each failure provides insights that can contribute to future success.<br><strong>User Feedback Loops: </strong>Establish regular feedback loops with users. Actively seek user feedback at various stages of development and use it to refine your product. This ongoing dialogue helps you stay connected with user needs and preferences.<br><strong>Data-Driven Decision Making:</strong> Utilize data to inform your decisions. Analyze user behavior, track key performance indicators (KPIs), and use data to validate assumptions. Data-driven insights provide a solid foundation for making informed decisions.<br><strong>Encourage Curiosity and Continuous Learning:</strong> Cultivate a culture of curiosity and continuous learning. Stay informed about industry trends, emerging technologies, and changes in user behavior. Encourage team members to seek new knowledge and share insights with the team.<br><strong>Think Beyond Features:</strong> Train your team to think beyond individual features and consider the holistic product experience. Encourage them to understand how features contribute to the overall value proposition and user satisfaction.<br><strong>Establish Product Heuristics:</strong> Define a set of product heuristics or guiding principles that align with your product vision. These heuristics can serve as a foundation for decision-making and keep the team focused on the core values of the product.<br><strong>Celebrate Successes and Learn from Failures:</strong> Acknowledge and celebrate successes, but equally important, learn from failures. Conduct post-mortems to analyze what worked well and what didn’t, and use those insights to improve future iterations.<br>By consistently applying these strategies, you can foster a product-thinking mindset within your team and organization. Remember that cultivating product thinking is an ongoing process that requires commitment, collaboration, and dedication to understanding and meeting user needs effectively. I’ve picked three tools for the problem space and three for the solution space.</p><h4><strong>Problem Space Tool: 5W1H (What, Who, Why, Where, When, &amp; How):</strong></h4><p>The 5W1H framework (What, Who, Why, Where, When, and How) is a powerful tool often used in problem-solving and project planning. When applied to the problem space, it helps teams and individuals thoroughly understand the context and nuances of a problem. Here’s how each element of the 5W1H framework can be applied:</p><p><strong>What</strong>:<br>Definition of the Problem: Clearly articulate the problem you are addressing. What is the nature of the problem? What are its characteristics and components? Defining the problem helps set the scope for finding a solution.<br><strong>Who</strong>:<br>Stakeholders and Users: Identify the individuals or groups who are affected by the problem and those who might be impacted by the solution. Understanding the various stakeholders helps in considering different perspectives and needs.<br><strong>Why</strong>:<br>Root Causes and Impacts: Investigate why the problem exists. What are the underlying causes? Also, consider the impact of the problem on users, stakeholders, and the overall environment. Understanding the “why” provides insights into the root of the problem.<br><strong>Where</strong>:<br>Context and Environment: Explore where the problem occurs. Is it location-specific? Does it manifest in particular situations or environments? Understanding the spatial and contextual aspects of the problem is crucial for designing an effective solution.<br><strong>When</strong>:<br>Timing and Frequency: Determine when the problem occurs and how often. Is it a persistent issue, or does it arise under specific conditions? Understanding the temporal aspects of the problem helps in designing solutions that are timely and relevant.<br><strong>How</strong>:<br>Processes and Mechanisms: Investigate how the problem manifests itself. What are the processes or mechanisms that contribute to the problem? Understanding the “how” provides insights into the dynamics of the issue and potential intervention points.</p><p>Applying the 5W1H framework to the problem space allows for a comprehensive exploration of the problem. This tool is particularly effective in the early stages of problem identification and analysis. It helps teams gather relevant information, define the scope, and develop a shared understanding of the problem before moving on to solution ideation and implementation. In practical terms, you can use the 5W1H framework through brainstorming sessions, workshops, interviews, or surveys. Encourage team members to collaboratively answer each of the six questions, fostering a shared understanding of the problem space. This can serve as a foundation for subsequent problem-solving activities and solution development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x3hdCRyD4Duwcm-ZNXmXpw.jpeg" /></figure><h4>Problem Space Tool #2: Mom’s Test (Foolproof your questions)</h4><p>The “Mom Test” is a concept popularized by entrepreneur and author Rob Fitzpatrick in his book “The Mom Test.” It’s a methodology for conducting customer interviews and gathering meaningful insights about a product or business idea. The essence of the Mom Test is to ask questions that provide unbiased and honest feedback, even if the respondent is your mom. Here’s how you can use the Mom Test as a tool in the problem space:</p><p><strong>Avoiding Bias:<br></strong>The Mom Test encourages you to phrase questions in a way that avoids bias or leads the respondent to give a positive response. Instead of asking, “Don’t you think this feature is great?” you might ask, “How would you currently solve this problem?”<br><strong>Understanding Their World:<br></strong>Rather than seeking validation for your idea, focus on understanding the customer’s world and experiences. Ask questions about their existing habits, problems they face, and their current solutions.<br><strong>Concrete Examples:<br></strong>Use concrete examples to ground your questions in reality. Instead of hypothetical scenarios, ask about specific instances where the customer has faced a particular problem or need.<br>Asking About Behavior, Not Opinion:<br>Rather than asking for opinions, inquire about past behavior. For instance, instead of asking, “Would you use a product that does XYZ?” ask, “Can you tell me about the last time you encountered a situation where XYZ would have been helpful?”<br><strong>Identifying Pain Points:<br></strong>Probe for pain points and challenges. Ask about the difficulties customers encounter in their daily lives and how they currently address those challenges.<br><strong>Testing Assumptions:<br></strong>Use the Mom Test to test assumptions you might have about your product or solution. Instead of assuming a feature will be valuable, ask questions to uncover whether users actually perceive it as valuable.<br><strong>Iterative Learning:<br></strong>Treat customer interviews as an iterative learning process. Each conversation should provide insights that help refine your understanding of the problem space and potential solutions.<br><strong>Listening Actively:<br></strong>Actively listen to what customers are saying, even if it challenges your assumptions. The Mom Test encourages a mindset of learning from customers rather than trying to sell or validate preconceived ideas.<br>Avoiding Leading Questions:<br>Be cautious about leading questions that inadvertently guide the respondent toward a particular answer. The goal is to get authentic, unbiased feedback.<br><strong>Refining Your Pitch:<br></strong>Use the insights gained from the Mom Test to refine your pitch and messaging. Focus on communicating how your product addresses real-world problems rather than showcasing features.<br>By applying the Mom Test in the problem space, you can gather valuable insights that help refine your understanding of the problem, validate assumptions, and guide the development of user-centric solutions. It’s a practical tool for conducting customer interviews that go beyond surface-level feedback.</p><h4>Problem Space Tool #3: Jobs-to-be-done (JTBD)</h4><p>Jobs-to-be-Done (JTBD) is a framework that focuses on understanding the underlying motivations and goals that drive individuals to “hire” a product or service to get a job done. This framework is particularly useful in the problem space, as it helps identify the real needs and desires of users. Here’s how you can use JTBD as a tool in the problem space:</p><p><strong>Define the Job:<br></strong>Start by clearly defining the job that customers are trying to accomplish. A job is not just a functional task but also includes the emotional and social aspects associated with achieving a goal.<br><strong>Identify the Trigger:<br></strong>Understand the trigger that prompts someone to start the job. What events or circumstances lead a person to seek a solution? This helps in identifying the specific situations that your product needs to address.<br><strong>Explore Functional and Emotional Jobs:<br></strong>Consider both functional and emotional aspects of the job. Functional jobs are the practical tasks that need to be completed, while emotional jobs capture the desired feelings and outcomes associated with the job.<br><strong>Segment by Jobs, Not Demographics:<br></strong>Instead of relying solely on demographic data, segment your audience based on the jobs they are trying to get done. This allows for a more precise understanding of user needs and preferences.<br><strong>Understand Switching Behavior:<br></strong>Explore what makes users switch from one solution to another. Understanding the circumstances that lead to switching helps in identifying pain points and areas for improvement.<br><strong>Create Job Stories:<br></strong>Develop job stories that describe a specific situation, motivation, and expected outcome. Job stories help in framing the user’s perspective and highlight the context in which they are trying to get a job done.<br><strong>Focus on Progress and Outcomes:<br></strong>JTBD emphasizes progress rather than features. Understand how users measure progress and the outcomes they seek. This perspective guides the development of features that contribute to users’ progress in their jobs.<br><strong>Uncover Unmet Needs:<br></strong>Explore unmet needs and opportunities. By understanding what users are struggling to achieve or what is missing from their current solutions, you can identify areas for innovation and product improvement.<br><strong>Iterative Learning:<br></strong>Like other problem space tools, JTBD encourages an iterative learning process. Continuously gather feedback, refine your understanding of the jobs, and iterate on your product based on the insights gained.<br><strong>Validate Hypotheses:<br></strong>Use JTBD to validate hypotheses about your product. Test whether your solution effectively addresses the jobs users are trying to get done and whether it provides the desired outcomes.<br><strong>Holistic Product Development:<br></strong>JTBD promotes a holistic approach to product development. Instead of focusing solely on features, consider how your entire product ecosystem contributes to helping users achieve their goals.</p><p>By applying the Jobs-to-be-Done framework in the problem space, you can gain a deep understanding of user motivations, uncover unmet needs, and guide the development of solutions that align with what users are trying to accomplish. It’s a valuable tool for creating products that truly resonate with users and fulfill their underlying needs and desires.</p><h4>Solution Space Tool: Get better at constructing hypothesis statements:</h4><p>A good hypothesis statement is the ultimate testimony of your problem space understanding. But first, what is a hypothesis? The best definition I found that seems to capture the essence of the word hypothesis is this → “A hypothesis is a testable explanation of an idea”. In other words, any explanation that is not testable is not a valid hypothesis. As a product person, it pays off to understand the difference, the relationship, and the hierarchy between an idea, hypothesis, and assumptions. I’ve represented this in the figure below.</p><p>Ideas are abundant, but every idea cannot be a hypothesis. Only ideas that can be testable qualify as hypotheses. A single idea can have multiple hypotheses (hypotheses), Every hypothesis comes with a set of assumptions and as a product thinker or product manager it is your responsibility to test and validate these assumptions during product development. Ideas do have assumptions too but if an idea is not a hypothesis then, these assumptions have no purpose in your path.</p><p>The shortest path to constructing a hypothesis statement to validate an idea and capture the testable aspect of the underlying assumptions is by using Josh Seiden and Jeff Golthelf’s hypothesis template published in their book — “Lean UX”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EhAhPBgT0vd3W7ijG3IMVw.jpeg" /></figure><h4>Solution Space Tool: Get creative with problem-solving</h4><p>When you get to solutions, finding the right starting point could be pretty daunting at times. This is where you can get smart by standing on the shoulders of the giants. Look around for proven models and systems. Below are six generic proven models that you could use as a starting point for solutions.</p><ol><li><strong>Transform:</strong> Transfer solution from one area to another. For example → We hear a lot of this is just like Uber but for pets, or for patients, or for something or someone else.</li><li><strong>Minimize:</strong> Reduce an existing solution. For example → When YouTube grew to a position where it was catering to a hub of various personas, Khan Academy was possible by focusing on just students and their need for simpler learning content.</li><li><strong>Maximize:</strong> Expand an existing solution. For example → Snapchat was the harbinger to introduce byte-size personal videos, and Instagram grew the same model with its mature influencer base, which in turn was taken to the next growth level by TikTok by democratizing influencer class altogether.</li><li><strong>Modify or Rearrange:</strong> Modify an existing solution. For example → Notion innovated from all the pain points from an Evernote user (there was no real innovation since inception) and modified the same product idea for the better with a delightful experience.</li><li><strong>Substitute:</strong> Substitute a part of an existing solution. For example → E-book readers. Although the idea of an electronic book reading existed for a few decades it only materialized to become a huge market after the introduction of the iPhone. iPhone enabled users to read on their devices for longer periods this prepped the market for a separate e-book reader category and products like Kindle, Nook, and Kobo were successful.</li><li><strong>Combine:</strong> Combine several existing solutions into one. For example: All super-apps like Alipay, Grab, and Gojek fall into this category. Don’t use this model for first-release products, it defeats the idea of MVP and lean thinking. This model is good for advanced growth stages.</li></ol><p>There are various creative ways to apply bullion operations on these models and find your bespoke approach to craft a solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GLr4jqYnheYpiIiT.jpeg" /></figure><h4>Solution Space Tool: Start focusing on the outcome and not output</h4><p>As a product thinker or product manager, you should start focusing on the outcome rather than output, the value you are generating versus the estimation of development effort, and the accuracy of the product to do a job versus simplicity. Ok, the last point raised a few eyebrows during my presentation, especially among designers. If you have frowned too, then allow me to explain it a bit further.</p><p>Albert Einstein said — “It can scarcely be denied that the supreme goal of all theory is to make the irreducible basic elements as simple and as few as possible without having to surrender the adequate representation of a single datum of experience.” Very scientifically and eloquently put. However, what does it mean? Music composer Roger Sessions paraphrased the same quote into simpler English as this → <strong>“Everything should be made as simple as possible, but not simpler.”</strong> It’s simple and deep. Now, when I say accuracy over simplicity it is in this sense. I do not mean simplicity is not important but as a product manager, if you are ever caught in a trade-off between simplicity and accuracy, always prioritize accuracy. Do not ruthlessly focus on simplicity. For instance, do not ruthlessly focus on reducing the number of clicks to the shopping cart, focus on the goals behind the action of adding an item to the shopping cart.</p><h4>summary:<br>Here are the key takeaways from this post/presentation:</h4><blockquote>. Definition of product thinking<br><strong>Why is product thinking important and the 3 rules you have to keep in mind:</strong><br>. Love the problem, not the solution<br>. Think in products, not in features<br>. Make products more meaningful with product thinking<br><strong>To cultivate product thinking try to apply these 3 problem space tools and 3 solution space tools to your next product idea:</strong><br>. Problem space tool#1 → 5W1H<br>. Problem space tool#2 → MOMS TEST<br>. Problem space tool#3 → JTBD<br>. Solution space tool#1 → Hypothesis Template<br>. Solution space tool#2 → 6 Solution Models<br>. Solution space tool#3 → Outcome &gt; Output</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d8ec82d0501" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>