Jan Swierzowicz

Product discovery uses iterative testing to streamline idea prioritization. We love Itamar Gilad's post on the challenges of product prioritization in companies. He argues that decisions often seem arbitrary and that retrospective analysis frequently shows poor judgment in choosing which ideas to invest in. Read his post and article: https://lnkd.in/d-zvU7Kt He highlights the inherent uncertainties in understanding users, competition, and technology. A robust prioritization process should incorporate these unknowns and use evidence-based methods to improve decision-making. Effective prioritization starts with the following: → a clear mission and strategy → concise and measurable goals → a model that highlights key metrics Without these elements, prioritization becomes difficult, and the criteria for idea selection remain vague. Prioritization should focus not on which ideas to launch but on which to test. Itamar emphasizes the importance of validating ideas before committing to full-scale development. We agree. Helio is a great way to concept test your initial ideas with a targeted audience and evaluate them with prototypes before you ever build anything in code. A comprehensive product discovery process includes: → Idea Evaluation – Evaluate the ideas based on our available evidence. → Idea Validation – Build and test versions of the ideas, thus generating new evidence. The two together form your product discovery loop, leading you to product delivery. #uxresearch #productdiscovery #marketresearch #productdesign

116

4 komentarze

MVP vs. MLP: What's the Difference? We’ve all heard of the Minimum Viable Product (MVP)—the bare essentials to get your product out the door. But what about the Minimum Lovable Product (MLP)? 🔧 MVP: It works, it’s functional, and solves the problem. Think of it as a product in its simplest form—just enough to be viable. 💖 MLP: It doesn’t just work—it delights! It’s a version that people love and want to come back to. It's that special touch that sparks joy and turns users into fans. So, while an MVP gets you to market quickly, an MLP builds a connection with your users. 👉 Pro Tip: Don’t stop at viable—aim for lovable! Your product’s longevity depends on more than just solving a problem; it’s about creating an experience people enjoy. #ProductManagement #MVPvsMLP #CustomerExperience #ProductDevelopment #UserEngagement

5

What are the keys to successfully scaling a product management organization? Our #topicoftheweek for this week is Scaling Product Management. Scaling a product management organization is hard. Done well, it helps enable growth. Done poorly, it can be an inhibitor to growth. Share your thoughts on scaling a product management organization, and and make sure you put our LinkedIn Live panel on Friday (May 3) at 12 pm ET on your calendar. Perhaps your answer to this question could get you an invite to join us! #productmanagement #productleadership

7

6 komentarzy

75% of purchase decisions are based on emotion 🛍 Desirability testing helps ensure your product appeals to users on an emotional level: https://lnkd.in/dSmGRcRp By integrating desirability testing into your design workflow, you can: ✔️ Create products that not only work well but also feel right to users ✔️ Make data-driven decisions about visual design elements ✔️ Understand the emotional impact of your design choices ✔️ Refine your product's personality and brand alignment __ #ui #ux #uidesign #uxdesign #uiux #userinterface #userexperience #uxers #uxthinking #uxdesigners #uxcommunity #interface #interaction #clayglobal #claydesignagency #designagency #designstudio #designcompany #design #sanfrancisco #designinspiration #digitaldesign

8

How do you keep track of multiple product teams? This is a common problem for product leaders, as you've got: • Lots of product teams working on stuff • Limited time to spend with them You need to know which teams are struggling and you need to dive deep on, and which ones are fine on their own. We recommend a system called a 𝗗𝗘𝗟𝗜𝗩𝗘𝗥𝗬 𝗨𝗣𝗗𝗔𝗧𝗘: 📈 Built in Google Sheets / Excel. Low tech, but reaches people where your find them 📈 1 tab per team; 3 main sections: team health / output / outcomes. Allows you to do root cause analysis as team health drives output, and output drives outcomes 📈 Teams fill a column each week. Seeing weeks side-by-side allows you to spot trends 📈 Does NOT cover product strategy: what problems we should solve / how are we solving them / how are we reducing value + usability risk. I cover this separately in product reviews, because the conversations are very different 📈 Team health: covers number of engineered days you’ve got, % time spent on planned (e.g. different OKRs) vs. unplanned work (e.g. bugs, ad hoc requests), and any qualitative feedback from teams on blockers they foresee 📈 Output: tracks delivery of epics related to OKRs. Simplicity much more important than accuracy, so usually just the number of tickets “done” each week out of the expected total 📈 Outcome: the OKR metrics you are tracking. Keeps everyone focused on outcomes, even as you talk about delivery / outputs. 𝗛𝗼𝘄 𝘁𝗵𝗲 𝗣𝗥𝗢𝗖𝗘𝗦𝗦 𝘄𝗼𝗿𝗸𝘀: ⏱️ Each team completes their column on a given day each week (e.g. Weds by 1pm). Should take 10-15 mins ⏱️ Leadership review all teams that day (e.g. Weds 3pm). Takes about 3 mins per team, so scales to 10+ teams quite easily ⏱️ Everyone blocks out an hour the next day to problem solve: “Office Hours” (e.g. Thurs 10-11am), which is typically 4x15 min slots ⏱️ Anyone in a team, or in leadership can request a team takes an Office Hour slot to joint problem solve. Agenda sent out after leadership review (e.g. 4pm Weds) ⏱️ Really important to stress psychological safety / on-the-same-side atmosphere in Office Hours 𝗪𝗵𝗮𝘁’𝘀 𝗥𝗘𝗔𝗟𝗟𝗬 𝗚𝗢𝗢𝗗 𝗮𝗯𝗼𝘂𝘁 𝘁𝗵𝗲 𝘀𝘆𝘀𝘁𝗲𝗺: ✅ Very easy to see which teams are struggling by comparing teams and over weeks ✅ Report allows root cause analysis for common problems (why didn't this ship on time?! ... ah, ad hoc requests are eating 60% of engineering time) ✅ Helps you understand true capacity of teams for planning ✅ Teams can get guaranteed problem solving time each week More notes on how this works, and a template here: https://lnkd.in/e5q2m_Vk

7

Welcome to the first topic in a series of 7 videos that Product Leaders can use to build best practice across their teams. The full set of topics covered in video format is available via complimentary membership of our growing community of product leaders. https://lnkd.in/efZjRVgd Habit 1 : Stop firefighting & Start Strategising At its heart, Product Management is all about adding value to your company through the strategic management of your product. Balancing the strategic component of the role with the demands of interacting with multiple internal and external product stakeholders is a constant challenge and emphasises the need for prioritisation and management of time. Techniques for time management and tools for developing and enhancing a product strategy are discussed in the video. We particularly like: Creating an on--demand sales enablement tool set to reduce repetitive requests • Many stakeholder group interactions are on repeated regular topics. • Enabling on-line access to regular requested information is a time saver. • Reinforce usage by regularly updating content. • Regularly direct stakeholders to content. • Brand the site for improved uptake. E.g. "Product Hub" Use proven time management techniques to balance operational with strategic activity • Consider which meetings really need your attendance. • Actively manage shorter meetings with agendas and time boundaries.  • Set dedicated slots for regular tasks, Email management for example. Clarify your role  • Clearly document the role of the product manager. • Include what it involves and what it does not! • Regularly communicate this with other stakeholders. • This should lead to a gradual reduction in operational work load. Build up streams of work that are strategic in nature • Regular reviews of competitive behaviour. • Analysis of key market trends, in target markets and technology. • Use the above to develop and maintain a Megatrends roadmap. These techniques and more are discussed in the video. You can join The Product Leader Alliance for free and then access the entire series, developed in partnership wih Tarigo Product Management, on the resource hub https://lnkd.in/efZjRVgd #productmanagement #productleader #productskills #skilldevelopment #chiefproductofficer

1

Product managers are not the type to shy away from a challenge. Most product managers thrive with a fast-paced, varied product workflow. They live for the satisfaction of guiding a team through research, development, and execution to maximize customer delight. #hotjar

1

As a Product Manager, you have the power to lead big changes, but when things get too technical, it can shake your confidence. Imagine being able to join those conversations knowing exactly how each technical decision impacts the product you're building. That’s where our FIRST TIME live cohort “Technical Mastery for High-Performance PMs” comes in! Our CEO, Irene Yu, a former Amazon software engineer who’s mentored PMs at companies like IBM and Stripe, is here to teach in 2 weeks exactly what you need to know in order to become technically fluent without wasting time trying to learn how to code. If you’ve ever: ❓ Struggled to ask the right questions during technical discussions ❓ Struggled trying to prioritize features due to technical complexity ❓ Struggled to connect better with engineers but found it hard to build trust… Then, this course is for you! Enroll now and get 20% off! This special offer ends Sunday, September 8th and is only available for the first 10 people to use the code LAUNCH. Link in the comments below 👇🏼 #productmanagement #productmanagers

3

1 komentarz

With Nuro pivoting to a different strategy (https://bityl.co/Rz9L), the udelv Transporter (https://udelv.com/) becomes the ONLY remaining working and available dedicated autonomous vehicle for last and middle mile delivery. #autonomousvehicle #selfdrivingcar #logistics #cleantransportation #autonomousdelivery

2

𝐂𝐫𝐞𝐚𝐭𝐢𝐧𝐠 𝐚 𝐩𝐫𝐨𝐝𝐮𝐜𝐭 𝐜𝐡𝐚𝐫𝐭𝐞𝐫 has helped multiple teams not get lost in the product development process 📋 It’s no wonder, as it provides a structured approach to defining your product’s vision, objectives, and scope, ensuring that everyone on your team is aligned and moving in the same direction. So, why is a product charter so crucial? Rather than getting bogged down by endless tasks and decisions, the product charter helps you focus on what truly matters. How does a product charter benefit your team? ✓ establishes a clear vision ✓ brings the team on the same page ✓ facilitates communication ✓ defines scope and sets boundaries ✓ outlines a roadmap to success ✓ and more! Ready to craft one? Keep reading to explore tips for building a robust product charter and find a 𝐭𝐞𝐦𝐩𝐥𝐚𝐭𝐞 𝐰𝐢𝐭𝐡 𝐞𝐱𝐚𝐦𝐩𝐥𝐞𝐬 of how to fill it out ⤵️ https://lnkd.in/egz_4YGU #ProductCharter #ProductDevelopment #startups #StartupTips

4

You don't have to organize your product team by product feature. It is a perfectly acceptable method, but it’s not the best fit for every situation. 1. 𝘐𝘵 𝘪𝘨𝘯𝘰𝘳𝘦𝘴 𝘵𝘩𝘦 𝘪𝘮𝘱𝘰𝘳𝘵𝘢𝘯𝘤𝘦 𝘰𝘧 𝘧𝘦𝘢𝘵𝘶𝘳𝘦 𝘷𝘴 𝘱𝘳𝘰𝘥𝘶𝘤𝘵 𝘧𝘰𝘤𝘶𝘴. When you have a PM aligned to a feature, they’re highly unlikely to suggest offloading that feature. It makes the PM attached to the feature rather than the product. 2. 𝘐𝘵 𝘰𝘣𝘴𝘤𝘶𝘳𝘦𝘴 𝘵𝘩𝘦 𝘳𝘰𝘭𝘦 𝘰𝘧 𝘪𝘮𝘱𝘢𝘤𝘵. It assumes that the PM owning a feature will be able to direct their resources to the strategic priorities of the business. The problem is: this breaks down very often. Feature teams have to do the work, and often fail, in mapping the features to outcomes. 3. 𝘐𝘵 𝘥𝘰𝘦𝘴𝘯’𝘵 𝘵𝘰𝘶𝘤𝘩 𝘰𝘯 𝘸𝘩𝘦𝘵𝘩𝘦𝘳 𝘰𝘸𝘯𝘦𝘳𝘴𝘩𝘪𝘱 𝘧𝘰𝘳 𝘵𝘩𝘦𝘴𝘦 𝘧𝘦𝘢𝘵𝘶𝘳𝘦𝘴 𝘪𝘴 𝘴𝘰𝘭𝘦𝘭𝘺 𝘗𝘔 𝘰𝘸𝘯𝘦𝘥 𝘰𝘳 𝘤𝘳𝘰𝘴𝘴-𝘧𝘶𝘯𝘤𝘵𝘪𝘰𝘯𝘢𝘭𝘭𝘺 𝘰𝘸𝘯𝘦𝘥. In a PM-owned org, cross-functional leads contribute but aren’t equal owners to the plan. Whereas, in cross-functionally owned orgs, multiple teams and cross-functional stakeholders contribute. So what's a better way of structuring your product team that can help overcome such problems? The go-to framework I’ve seen is from Ravi Mehta in Reforge's Product Leadership course. In it, he explains that there are two questions to ask: 1. Are teams focused on features or outcomes? 2. Do teams own their metrics or share their metrics? The answers to these questions map to the type of product organization you have. These are considered as the "2 Dimensions of Product Org Design." When you answer each, you'll probably end up in one of the following 4 categories: • 𝗢𝘂𝘁𝗰𝗼𝗺𝗲 𝗼𝘄𝗻𝗲𝗿: This is when the PM is responsible for driving a metric and takes its sole ownership. • 𝗢𝘂𝘁𝗰𝗼𝗺𝗲 𝗰𝗼𝗻𝘁𝗿𝗶𝗯𝘂𝘁𝗼𝗿: This is when the PM is focused on a metric (vs a feature) but does not solely own it. • 𝗙𝗲𝗮𝘁𝘂𝗿𝗲 𝗼𝘄𝗻𝗲𝗿: This is when the PM has sole ownership over a feature (vs a metric) • 𝗙𝗲𝗮𝘁𝘂𝗿𝗲 𝗰𝗼𝗻𝘁𝗿𝗶𝗯𝘂𝘁𝗼𝗿: This is when the PM is focused on a feature but does not solely own it. None is "better" than the other. 𝗜𝘁'𝘀 𝗮𝗯𝗼𝘂𝘁 𝗳𝗶𝗻𝗱𝗶𝗻𝗴 𝘄𝗵𝗮𝘁 𝗳𝗶𝘁𝘀 𝗯𝗲𝘀𝘁 𝗳𝗼𝗿 𝘆𝗼𝘂𝗿 𝘀𝗶𝘁𝘂𝗮𝘁𝗶𝗼𝗻.

25

1 komentarz

Have you heard about rich push notifications? 🚨 We've teamed up with our partners at Pushwoosh to explore the power of rich push notifications and how they can significantly boost your app's conversion rates. 🤩 In their latest blog, they delve into: 1️⃣ What rich media push notifications are 2️⃣ Best practices for creating high-converting rich push notifications 3️⃣ Success stories Take advantage of actionable insights that can transform your app marketing game! 🎯 Check it out now 👉 https://lnkd.in/eFg4WdgS #AppMarketing #PushNotifications #DigitalMarketing #CustomerEngagement

28

1 komentarz

Rather than the usual SaaS pricing dance, where you’re often left guessing, we’re committed to a model that’s transparent, fair, and simple. Here's a bit of our thinking. 1️⃣ Pay for What You Use No hidden fees, no negotiation games. Everyone pays the same rate based on usage. Bigger teams may pay more because they use Tuist more, while a small startup pays only for what they need. Straightforward. 2️⃣ If You Don’t Use It, You Don’t Pay Indie devs and small teams who don’t rely heavily on Tuist shouldn’t have to pay. Starting out shouldn’t be about costly tools; it’s about building something great. With Tuist, you get to start for free. 3️⃣ Affordable at Every Scale Our goal is to be the most affordable, transparent option for Swift app development. If we fall short, we want you to tell us. We’re a commercial open source company. Our open source software and paid extensions work hand in hand. If Tuist adds value to your work, enjoy it for free. As your usage grows, we’re here to scale with you—no strings attached. And if you ever decide to move on, we make that simple too. We built this model because we’re tired of seeing “contact sales” buttons and complicated pricing schemes that end up locking people in. Instead, we’re aiming for transparency and an open-door policy. Thanks to this approach, we can continue to develop open source tools for the Swift ecosystem and support the communities behind great apps.

1

✨ 5x types of product vision ✨ Product visions are hugely effective at two things: 1. 𝗔𝗹𝗶𝗴𝗻𝗺𝗲𝗻𝘁 - making it clear what you're building 2. 𝗜𝗻𝘀𝗽𝗶𝗿𝗮𝘁𝗶𝗼𝗻 - making everyone care about what you're building But how do you actually do that? "Product vision" is one of the most ambiguous terms in product management... Right up there with "roadmap" and "product strategy" 😜 We've found 5x ways people use the term: 1. 𝗔 𝟭-𝗹𝗶𝗻𝗲 𝘀𝗲𝗻𝘁𝗲𝗻𝗰𝗲 This crisply sums up the future you want to build ✅ Memorable and stable 🚨 Very ambiguous and easily confused with a mission statement. 2. 𝗪𝗿𝗶𝘁𝘁𝗲𝗻 𝗽𝗿𝗶𝗻𝗰𝗶𝗽𝗹𝗲𝘀 3-4 bullet points describing key benefits and features you want to offer ✅ Fast to create and clear what the customer benefits are 🚨 Hard to envisage what we're talking about 3. 𝗣𝗿𝗼𝗱𝘂𝗰𝘁 𝗩𝗶𝘀𝗶𝗼𝗻 𝗕𝗼𝗮𝗿𝗱 Roman Pichler's famous business canvas ✅ Triangulates on vision from both customer and business perspective 🚨 Not at all inspiring 4. 𝗣𝗥 / 𝗙𝗔𝗤𝘀 Amazon's thorough process for drafting a press release and FAQs up front ✅ Holistic appraisal of the merit of a new idea 🚨 Significant effort to do well, still not visual 5. 𝗩𝗶𝘀𝗶𝗼𝗻𝘁𝘆𝗽𝗲 Vision in a prototype. A series of mockups, often with a storyboard narrative ✅ Vivid and inspiring illustration of what you're building 🚨 Can be lots of work to create We're a big fan of vision types, but which one is right for you? What are the right trade offs for you to make? Full article here: https://lnkd.in/drGGcC4x

5

🔧 Tool of the Week: Vercel/Stripe Utilizing over a dozen tools weekly to reach goals, there are so many options out there. It can get overwhelming hearing about all these different things, but not having the time to actually explore theme. Each week, we’ll highlight a tool—whether free or paid—that we’ve used the most, sharing why it stood out to us and how it helps us stay ahead of the curve. To kick off the series, we have two tools coming together to form one: - Vercel/Stripe—a dynamic duo that’s perfect for quickly building and monetizing apps. These are no joke. You can build and monetize and app TODAY. These tools caught our attention for a few key reasons: - Using Vercel/Stripe allows us to easily integrate payment systems into apps, letting us focus on building out the core features. - With Vercel’s rapid deployment capabilities, we’re able to launch apps quickly, a game changer when turnaround times are tight. - Stripe’s secure, flexible payment options make it simple to create smooth, user-friendly payment experiences. What are Vercel & Stripe? - A project built using Vercel & Stripe brings together Vercel’s fast, serverless deployment platform and Stripe’s reliable payment processing. - This pairing makes it easy for us to build, deploy, and monetize apps quickly, while offering a seamless experience for users. Here’s how to leverage Vercel with the Stripe API: - We’re able to create monetized apps in hours, allowing businesses to start generating revenue quickly. - Stripe gives us the flexibility to adapt payment flows to different business models, which makes it useful across industries. - Payments types vary. Feel free to utilize the subscriptions, monthly vs. annually billed upsells, payment links, and more. With Vercel, updates can be deployed quickly, ensuring that apps stay optimized and up-to-date. As we continue exploring Vercel/Stripe, we’re excited to see how we can streamline future projects where speed and monetization are key. This is just the beginning—check back next Sunday to see what tool we spotlight next based on how much we’ve used it in the week ahead. Let’s keep discovering what’s possible together! Stripe.com Vercel.com

1

UX metrics inform product success. We love Tim Herbig’s article on using leading and lagging indicators to shape product OKRs (objectives and key results). Balancing these indicators helps teams track progress and make better decisions. Leading indicators give early signs of success, enabling quick adjustments, while lagging indicators confirm results but focus on past performance. Focusing on the right metrics keeps teams aligned with their goals and improves their chances of product success. Check it out: https://lnkd.in/gvrMEc-R Here are his big ideas: • Leading predicts success • Lagging shows past results • Metrics shift between leading & lagging • Lagging confirms • Leading predicts with less precision • Measure actions driving success • Use both indicators to adapt • Focus on leading to act fast We love it. Using UX metrics in your testing can help you quickly determine whether you are optimizing your leading OKRs. Here are a few that would work in his example: → Desirability This helps assess how appealing the banner or message concept is to users. It is helpful for early-stage evaluations before significant design efforts. → Expectations Gauges what users expect to achieve by engaging with the banner. Aligns design and messaging with user goals. → Usefulness Identifies whether users perceive the banner as valuable or relevant. Critical for ensuring the banner motivates action. → Comprehension Measures whether users understand the banner’s message. A core metric to track before input to validate clarity. → Engagement Examines how users interact with early concepts or prototypes. Useful to identify friction points and improve designs. Helio helps teams gather fast user signals to guide decisions. You can test ideas, measure key UX metrics, and identify leading indicators early, ensuring your efforts align with user needs and business goals. #uxresearch #productdiscovery #marketresearch #productdesign

165

9 komentarzy