A seasoned product manager and leader in the e-commerce and technology industry, boasting 10+ years of experience in product management and a proven track record of launching and growing successful products. Currently based in Berlin, I lead a team responsible for the technology powering Zalando's sourcing process, making millions of fashion items available to customers of one of Europe's leading online fashion retailers. Prior to this role, I worked at Hyke.ai, a B2B start-up that empowers wholesale and distribution businesses, and led the e-commerce platform and mobile apps at Al-Futtaim Group, a conglomerate headquartered in Dubai. I also co-founded and led the product and engineering efforts for Taskty.com, the first online marketplace for home services in the Middle East and North Africa region.
My Mentoring Topics
- Product Management
- Product Strategy
- e-Commerce and Omni-channel Retail
- Leadership and Team Management
Mohamed didn't receive any reviews yet.
INSPIRED - How to Create Tech Products Customers Love
Marty Cagan
Key Insights from "INSPIRED: How to Create Tech Products Customers Love" Emphasizes that product management is a team sport, advocating for a cross-functional team approach. Illuminates the importance of discovering the right product to build before diving into the development. Reveals the role of product managers as the discoverers of the product, not simply project managers. Encourages adopting an outcome-based rather than output-based approach to product development. Highly recommends the application of prototyping and testing techniques to validate ideas before committing to full development. Asserts the necessity of continuous product discovery for sustainable success. Advises on how to establish a customer-centric culture in a tech organization. Reinforces the value of learning from product failures, not just successes. Insists on the importance of strong leadership in product management. Underlines the need for strategic alignment between the product team and the larger organization. Stresses on the significance of a shared product vision within the team. Deeper Analysis of the Book "INSPIRED: How to Create Tech Products Customers Love" by Marty Cagan, a Silicon Valley product management veteran, is a veritable guide for tech entrepreneurs, product managers, and those aspiring to create successful tech products. Starting with the assertion that product management is a team sport, Cagan underscores the necessity of collaboration among cross-functional teams. This aligns with the concept of Collective Ownership in Agile methodologies, where everyone in the team is responsible for the quality and success of the product. The book extensively discusses the role of product managers, distinguishing them from project managers. Cagan positions product managers as the discoverers of the product. This involves understanding customer needs, exploring market opportunities, and working closely with the product team to create a product that aligns with the business objectives and customer expectations. One of the notable principles that Cagan advocates for is an outcome-based approach over an output-based one. This shift in focus from simply delivering features to achieving desired outcomes is a core tenet of modern product management, emphasizing on value creation rather than just activity. In "INSPIRED", Cagan also emphasizes the importance of continuous product discovery. This is about constantly seeking to understand customers, experimenting with solutions, and validating ideas before committing to full-scale development. The principle resonates with the Lean Startup methodology, particularly the Build-Measure-Learn feedback loop. Prototyping and testing are other key aspects that Cagan discusses. He advises product teams to validate their ideas with low-fidelity prototypes, conduct usability tests, and gather feedback to refine the product. This aligns with the principle of Fail Fast, Fail Often in Agile, which encourages learning through quick experiments and iterations. An essential part of creating tech products that customers love, according to Cagan, is establishing a customer-centric culture. This involves prioritizing customer needs and feedback in the product development process, which is a fundamental principle of Human-Centered Design. Cagan also acknowledges that not all product initiatives will succeed. He encourages teams to learn from product failures and to leverage these learnings to improve future products. This resonates with the concept of a Learning Organization, where failure is seen as an opportunity for learning and growth. Underpinning all these principles, Cagan stresses the importance of strong leadership in product management. He insists that leaders should inspire, guide, and empower their teams to do their best work, which aligns with the concept of Servant Leadership in Agile. Lastly, Cagan highlights the need for strategic alignment and a shared product vision. This implies that all efforts of the product team should be directed towards achieving the strategic goals of the organization, and everyone on the team should understand and be committed to the product vision. In conclusion, "INSPIRED: How to Create Tech Products Customers Love" is a comprehensive guide that offers invaluable insights and practical advice on how to create successful tech products. It should be a must-read for anyone involved in product management, as it encapsulates the collective wisdom of one of the most experienced product managers in the tech industry.
ViewContinuous Discovery Habits - Discover Products that Create Customer Value and Business Value
Teresa Torres
Key Facts and Insights Continuous Discovery: The book paints a vivid picture of the continuous discovery process, arguing that it's not a linear or one-off process but an ongoing cycle of learning, adapting, and improving. Customer-Centric Approach: The author underscores the importance of a customer-centric approach, suggesting that understanding customer needs and behaviors should be at the heart of product development. Outcome-Over-Output Mindset: Torres emphasizes the importance of focusing on outcomes rather than outputs. It's not about how many features a product has, but how it impacts customers' lives. Collaborative Discovery: The book outlines the importance of collaborative discovery, promoting the idea of involving the whole team in the product discovery process. Opportunity Solution Tree: Torres introduced a unique tool called the Opportunity Solution Tree to visualize and prioritize opportunities for product improvements. Experimentation and Validation: The author stresses the necessity of experimentation and validation throughout the product development process. Interview Techniques: The book provides insightful interview techniques and tools to gain a deep understanding of customer needs. Building Empathy: Torres highlights the importance of building empathy with customers to create products that genuinely solve their problems. Product Trio: The book suggests that the most effective discovery teams are composed of a product manager, a designer, and a software engineer - referred to as the "product trio". Discovery Cadence: The book advocates for a weekly discovery cadence, where teams engage in regular discovery activities to keep learning and adapting. In-depth Summary and Analysis "Continuous Discovery Habits" is a comprehensive guide to modern product management. Teresa Torres, an experienced product discovery coach, brings to light the importance of continuous discovery in creating valuable products. Torres starts by challenging the traditional, linear model of product development. Instead, she proposes a cycle of continuous discovery where learning, adapting, and improving are continuous processes. As a professor who's been dealing with these topics for years, I find this perspective refreshing. It aligns well with the rapid pace of change in today's digital world, where products must constantly evolve to meet changing consumer needs. The book's emphasis on a customer-centric approach is another crucial insight. Torres argues that understanding customer needs and behaviors should be the cornerstone of product development. This aligns with concepts I've taught over the years, such as "user-centered design," where the user's needs, wants, and limitations are a focus at all stages within the design process. A key theme in the book is the outcome-over-output mindset. Torres points out that product teams often get caught up in delivering features (output) and lose sight of the desired outcomes. This resonates with the "Jobs to Be Done" theory, which argues that customers don't buy products or services; they "hire" them to do a job. Another key insight from the book is the role of collaboration in discovery. Torres argues that involving the whole team in the product discovery process can lead to better solutions. This concept parallels the "cross-functional team" approach popular in agile development practices. The Opportunity Solution Tree, a unique tool introduced in the book, is an effective way to visualize and prioritize opportunities for product improvements. As an academic tool, it encourages systematic thinking and can help teams avoid jumping to solutions before thoroughly exploring the problem space. Torres' emphasis on experimentation and validation is in line with the scientific method and lean startup principles. She suggests that before investing significant resources into building a product, teams should validate their assumptions through small, quick experiments. The book is also a valuable resource for learning interview techniques to gain a deep understanding of customer needs. Torres provides practical advice on how to ask effective questions and listen empathetically. Building on the idea of empathy, Torres underscores the importance of building empathy with customers. She argues that deep empathy leads to products that genuinely solve customer problems, a concept that aligns with the empathize stage in the Design Thinking process. The product trio concept proposed in the book is also noteworthy. Torres suggests that the most effective discovery teams are composed of a product manager, a designer, and a software engineer. This trio ensures a balance of business, design, and technical perspectives in the discovery process. Finally, Torres advocates for a weekly discovery cadence, where teams engage in regular discovery activities. This routine allows teams to continuously learn, adapt, and improve, keeping the spirit of continuous discovery alive. In conclusion, "Continuous Discovery Habits" provides a comprehensive framework for modern product discovery. It echoes many concepts I've taught over the years while introducing new tools and perspectives. By internalizing the book's key insights, teams can create products that create real value for customers and businesses alike.
ViewGood Strategy Bad Strategy - The Difference and Why It Matters
Richard Rumelt
Key Facts and Insights from the Book Strategy is not a goal or vision; it is a coherent mix of policy and action designed to surmount a high-stakes challenge. A good strategy has a kernel composed of three parts: a diagnosis, a guiding policy, and a set of coherent actions. Bad strategy is characterized by fluff, a failure to face the challenge, mistaking goals for strategy, and bad strategic objectives. 'Fluff' is a form of gibberish masquerading as strategic concepts or arguments. A strategy is a way through a difficulty, an approach to overcoming an obstacle, a response to a challenge. Good strategy requires leaders to make tough choices and potentially upset certain stakeholders. Strategic objectives should be an actionable step that moves you towards your goals. A strategy should be dynamic and flexible, able to adapt to changing circumstances. Bad strategy tends to skip over pesky details such as problems. It ignores the power of choice and focus, trying instead to accommodate a multitude of conflicting demands and interests. Good strategy works by focusing energy and resources on one, or a very few, pivotal objectives whose accomplishment will lead to a cascade of favorable outcomes. Strategy is about how, exactly, you are going to move in a chosen direction. A Detailed Summary and Analysis "Good Strategy Bad Strategy - The Difference and Why It Matters" by Richard Rumelt is a seminal work that dissects the good, the bad, and the ugly aspects of strategy. The book kickstarts with a profound declaration: Strategy is not a goal or vision; it is a coherent mix of policy and action designed to surmount a high-stakes challenge. This declaration sets the tone for the rest of the book, positioning strategy as a tool for problem-solving, not a lofty vision or a set of objectives. Rumelt posits that good strategy has a kernel composed of three parts: a diagnosis, a guiding policy, and a set of coherent actions. The diagnosis is a judgement about the nature of the challenge, while the guiding policy is an overall approach chosen to cope with or overcome the obstacles identified in the diagnosis. The set of coherent actions are steps that are coordinated with one another to support the accomplishment of the guiding policy. In contrast, bad strategy is characterized by fluff, a failure to face the challenge, mistaking goals for strategy, and bad strategic objectives. 'Fluff' is a form of gibberish masquerading as strategic concepts or arguments. It uses “Sunday” words (words that are inflated and unnecessarily abstruse) and apparently esoteric concepts to create the illusion of high-level thinking. Rumelt also underscores the point that a strategy is a way through a difficulty, an approach to overcoming an obstacle, a response to a challenge. This is a crucial demarcation between strategy and other elements such as vision, mission, or objectives. It's about making hard choices about where to invest your time, energy, and resources to overcome your biggest challenges and move the organization forward. One of the main reasons for the prevalence of bad strategy, according to Rumelt, is the unwillingness of leaders to make tough choices, and to upset certain stakeholders. This results in what he calls 'the blob', a set of compromise decisions that satisfy various stakeholders but fail to provide clear guidance for action. Rumelt also highlights that strategic objectives should be an actionable step that moves you towards your goals. They should address a specific process or accomplishment that can be completed with available or soon-to-be available resources. The author further emphasizes that a strategy should be dynamic and flexible, able to adapt to changing circumstances. This is a clear departure from the traditional view of strategy as a fixed, multi-year plan. In conclusion, "Good Strategy Bad Strategy" is a compelling and insightful guide to distinguishing between good and bad strategy and understanding why the difference matters. It is a must-read for any business leader, manager, or decision-maker who wants to create strong strategies that lead to success.
ViewMeasure What Matters - How Google, Bono, and the Gates Foundation Rock the World with OKRs
John Doerr
Key Insights from "Measure What Matters" The OKR (Objectives and Key Results) system is a powerful tool for setting, tracking, and achieving goals. OKRs are designed to align the efforts of individuals, teams, and organizations towards a common purpose. Transparency is a key principle of OKRs, promoting accountability and collaboration. OKRs should be ambitious (moonshots) and complemented by more achievable (roofshots) goals. OKRs should be flexible, adaptable and not tied to compensation or performance reviews. OKR success is reliant on a supportive, feedback-rich culture. OKRs have been instrumental in the success of major companies like Google, Intel, and the Gates Foundation. The "superpower" of OKRs lies in its focus, alignment, tracking, and stretching capabilities. OKRs are not just for businesses, they can be applied to personal goals as well. Continuous learning and improvement are integral to the OKR system. In "Measure What Matters," John Doerr presents the OKR (Objectives and Key Results) system as a vital tool for goal setting and achievement. He does this through a series of compelling case studies from Google, Intel, the Gates Foundation, and even U2's Bono, illustrating how the system is adaptable across different contexts. Objectives and Key Results (OKRs) Doerr outlines the OKR system as a simple method to create alignment and engagement around measurable goals. The system involves setting ambitious objectives and then defining quantitative key results to track progress towards these objectives. This encourages focus and prioritizes action on the most important tasks. Doerr emphasizes that OKRs should not be tied to compensation or performance reviews, as this can encourage risk-averse behavior. Instead, they should be seen as a way to foster learning, innovation, and personal growth. Transparency and Alignment Transparency is a key principle in the OKR system. By making OKRs public within an organization, individuals and teams can see how their efforts contribute to the overall goals. This promotes accountability and encourages collaboration, as everyone understands their role in the bigger picture. Through the use of OKRs, organizations can ensure that everyone is pulling in the same direction. This alignment is crucial for achieving large, ambitious goals, or as Doerr terms them, "moonshots." Moonshots and Roofshots Doerr encourages organizations to set audacious "moonshot" OKRs, which are big, bold goals that inspire and challenge. These should be complemented by more achievable "roofshot" OKRs, which provide a more immediate, realistic target. The combination of moonshots and roofshots encourages organizations to stretch beyond their comfort zones while also providing a clear path to progress. OKRs in Practice The success of the OKR system is exemplified through the stories of Google, Intel, and the Gates Foundation. These organizations have used OKRs to focus their efforts, align their teams, and achieve extraordinary results. For example, Google's Larry Page and Sergey Brin credit OKRs with keeping the company focused during rapid growth. Intel used OKRs to drive a major strategic shift in the 1980s, while the Gates Foundation uses them to tackle complex global health issues. Conclusion Doerr's "Measure What Matters" offers a compelling argument for the power of OKRs. The system's simplicity, flexibility, and emphasis on transparency and alignment make it a potent tool for any organization or individual seeking to achieve their goals. However, as I often stress in my lectures, the implementation of OKRs should be done with care. It requires a supportive, feedback-rich culture and a commitment to continuous learning and improvement. Used effectively, OKRs can, indeed, rock the world.
View
Escaping he Build Trap
Melissa Perri
Key Facts and Insights from "Escaping the Build Trap" The Build Trap: This refers to the scenario where organizations are stuck in a cycle of building features without a clear understanding of the value they provide to the customers or the business. Product Management: The book emphasizes the role of product management in escaping the build trap, underlining the significance of strategizing, coordinating, and optimizing product development. Outcome over Output: The book insists on focusing on outcomes (the value derived) rather than outputs (the features built). Experimentation: Melissa Perri advocates for a culture of experimentation and learning to validate ideas and assumptions before full-scale implementation. Customer Centricity: The book highlights the importance of understanding and serving the customer's needs as the central mission of any product organization. Product-Led Organizations: The author proposes the need for organizations to transform into product-led entities, where product management drives strategy and business growth. Product Kata: The book introduces the concept of Product Kata – a structured routine for continuous learning and improvement. Product Metrics: The book discusses the importance of defining the right metrics to measure the success of a product. Leadership Role: Melissa Perri discusses the role of leadership in enabling a product-centric culture and escaping the build trap. Product Strategy: The book emphasizes the need for a clear, customer-centric product strategy to guide product development and decision-making. Value-Based Backlog: The book introduces the concept of a value-based backlog, where product features are prioritized based on the value they provide rather than their perceived importance or ease of implementation. An In-depth Analysis "Escaping the Build Trap" by Melissa Perri is a comprehensive guide for organizations stuck in the cycle of building features without a clear understanding of their value. This phenomenon, referred to as the "Build Trap," is a common pitfall that organizations fall into, resulting in wasted resources, a lack of strategic direction, and products that fail to meet customer needs. The book positions product management as the key to escaping the build trap. Perri highlights the role of product managers in strategizing, coordinating, and optimizing product development. She emphasizes that product management is not just about overseeing the creation of products, but about ensuring that these products deliver value to both the customers and the business. One of the key insights of the book is the focus on outcomes rather than outputs. This is a shift from traditional product development practices that focus on the number of features built or tasks completed. Instead, Perri argues that organizations should focus on the value derived from these features or tasks. This aligns with the Lean Startup methodology and the concept of "value-driven delivery" in Agile practices. Perri also advocates for a culture of experimentation and learning. She suggests that ideas and assumptions should be validated through small-scale experiments before they are implemented on a full scale. This approach reduces the risk of failure and ensures that resources are invested in features that provide real value. The book also underscores the importance of customer centricity. Perri argues that understanding and serving the customer's needs should be the central mission of any product organization. This concept aligns with the principles of Human-Centered Design and User Experience (UX) Design, which prioritize the user's needs and experiences in product design and development. Perri proposes that organizations should transform into product-led entities. In such organizations, product management drives strategy and business growth. This shift requires a change in organizational structure and culture, with the product team playing a central role in decision-making. The concept of Product Kata, introduced in the book, is a structured routine for continuous learning and improvement. It is an iterative process of defining a vision, understanding the current state, setting a target condition, and continuously experimenting and learning to move towards the target condition. This concept is reminiscent of the PDCA (Plan-Do-Check-Act) cycle used in quality management and the Scrum framework's empirical process control. Perri discusses the importance of defining the right metrics to measure the success of a product. These metrics should align with the product's objectives and the value it is intended to deliver. This concept complements the Key Performance Indicators (KPIs) and Objective and Key Results (OKRs) frameworks used in performance management. The book also sheds light on the role of leadership in enabling a product-centric culture. Perri argues that leaders should encourage experimentation, foster customer centricity, and empower product teams. The book emphasizes the need for a clear, customer-centric product strategy. This strategy guides product development and decision-making, ensuring that the product delivers value to the customers and aligns with the business objectives. Lastly, the book introduces the concept of a value-based backlog, where product features are prioritized based on the value they provide rather than their perceived importance or ease of implementation. This is a shift from traditional backlog management practices and aligns with the principle of "maximizing the work not done" in Agile practices. In conclusion, "Escaping the Build Trap" is a valuable resource for organizations seeking to transform their product practices and become more customer-centric, value-driven, and strategic. By focusing on outcomes, promoting experimentation, and fostering a product-centric culture, organizations can escape the build trap and build products that truly deliver value.
ViewThe Culture Map - Breaking Through the Invisible Boundaries of Global Business
Erin Meyer
Key Facts and Insights from "The Culture Map - Breaking Through the Invisible Boundaries of Global Business" Understanding cultural differences is crucial for successful business communication and negotiation in the global marketplace. The book presents eight dimensions to map and understand cultural differences: Communication, Evaluating, Persuading, Leading, Deciding, Trusting, Disagreeing, and Scheduling. Each culture falls on a scale within these eight dimensions, which helps in comparing and contrasting different cultures. Communication styles vary greatly between cultures, and misunderstandings can easily occur if these differences are not recognized. Concepts of leadership and decision-making differ greatly among cultures, which can impact how businesses operate and negotiate internationally. The concepts of trust and disagreement also vary significantly across cultures. Understanding these differences can help build stronger, more effective international business relationships. The book includes real-world examples and case studies to illustrate the concepts discussed, making it a practical guide for business professionals. Erin Meyer's Culture Map provides a framework for understanding and navigating cultural differences in a global business context. Cultural intelligence is a vital skill for any business professional operating in a multicultural environment. The book emphasizes the importance of flexibility, adaptability, and open-mindedness in understanding and respecting cultural differences. "The Culture Map" is not only about understanding others but also about understanding oneself’s cultural biases and preferences. Detailed Summary and Analysis "Breaking Through the Invisible Boundaries of Global Business" by Erin Meyer is a comprehensive guide for anyone navigating the complex world of international business communication. The book presents a novel approach to understanding cultural differences, introducing an eight-dimension model that provides a structured way to compare and contrast different cultures. The dimensions – Communicating, Evaluating, Persuading, Leading, Deciding, Trusting, Disagreeing, and Scheduling – act as a map to navigate cultural complexities. In the dimension of Communication, Meyer explains that cultures can be categorized as low-context (where good communication is precise, simple, and clear) or high-context (where good communication is sophisticated, nuanced, and layered). This distinction is particularly crucial as misunderstandings can easily occur if individuals from different cultures do not recognize these differences. Moving on to Evaluating, the book discusses how different cultures give feedback. Some cultures are more direct, others are indirect. Misunderstandings can arise if feedback is interpreted through one's cultural lens without considering these differences. The dimensions of Leading and Deciding are intertwined, as they both deal with hierarchies and decision-making processes. In some cultures, leadership is equated with hierarchical status, while in others, it is more linked to expertise and competence. Similarly, decision-making can either be top-down or consensus-driven, depending on the culture. Trusting and Disagreeing are two more dimensions that vary significantly across cultures. In some cultures, trust is built through business relationships, while in others, it is established through personal relationships. The way cultures handle disagreement can also be very different, with some favoring a confrontational approach and others preferring to avoid open conflict. The final dimension, Scheduling, deals with how different cultures perceive time and deadlines. Some cultures view time as linear and rigid, while others see it as flexible and fluid. The book carefully balances theory with real-world examples and case studies, making it an insightful and practical guide for business professionals. The author emphasizes the importance of flexibility, adaptability, and open-mindedness in understanding and respecting cultural differences. The book encourages readers not only to understand and appreciate others' cultural biases and preferences, but also to recognize and understand their own. In conclusion, "The Culture Map" provides valuable insights and tools to navigate the cultural complexities that characterize today's global business environment. It emphasizes the importance of cultural intelligence as a vital skill for any business professional operating in a multicultural environment. This book is a must-read for anyone seeking to communicate, negotiate, and do business effectively in the international arena.
View