<?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 Julia Bastian on Medium]]></title>
        <description><![CDATA[Stories by Julia Bastian on Medium]]></description>
        <link>https://medium.com/@juliabastian?source=rss-63e22d490e31------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*GnNBx9seOCrbtD-uNqiHgw.jpeg</url>
            <title>Stories by Julia Bastian on Medium</title>
            <link>https://medium.com/@juliabastian?source=rss-63e22d490e31------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 09:21:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@juliabastian/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[Breaking Free from Sales-Driven Decisions: The Power of Continuous Insight Management in B2B…]]></title>
            <link>https://juliabastian.medium.com/breaking-free-from-sales-driven-decisions-the-power-of-continuous-insight-management-in-b2b-c2362680edf5?source=rss-63e22d490e31------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2362680edf5</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[b2b-product-management]]></category>
            <category><![CDATA[product-discovery]]></category>
            <category><![CDATA[b2b]]></category>
            <dc:creator><![CDATA[Julia Bastian]]></dc:creator>
            <pubDate>Mon, 27 Jan 2025 20:40:08 GMT</pubDate>
            <atom:updated>2025-01-27T20:40:08.053Z</atom:updated>
            <content:encoded><![CDATA[<h3>Breaking Free from Sales-Driven Decisions: The Power of Continuous Insight Management in B2B Product Management</h3><p>The biggest challenge in B2B product development is making decisions based on reliable data without falling into a reactive cycle of acting upon customer requests. With a limited number of customers and lagging data, product teams often end up basing decisions solely on input from Sales or Customer Success. This leads to sales-driven roadmaps that focus on surface-level requests rather than solving real customer problems.</p><p>This sales-driven approach often turns product organizations into feature factories, constantly sprinting from one ad hoc request to the next. Over time, this cycle can lead to declining sales, frustrated customers, mounting technical debt, and, in the worst-case scenario, a loss of product-market fit.</p><p>What if there were a way to break free from this cycle and make smarter, more strategic decisions? A way to leverage the knowledge from Sales and Customer Success without blindly following their requests? The answer lies in <strong>continuous insight management</strong> — a powerful approach that turns customer feedback into actionable, data-informed decisions.</p><p><em>In this article, we’ll explore why insight management is essential for B2B product teams, how to set it up effectively with real-world examples, and how it can help your organization transition from reactive firefighting to proactive growth.</em></p><h3>Why B2B Product Teams Struggle to Make Customer-Centric Decisions</h3><p>B2B product teams often face challenges in accessing reliable, unbiased insights. While customer-facing teams like Sales and Customer Success interact with customers daily, the information they share with product teams is often influenced by their own priorities, creating biases:</p><p><strong>The issues with information from customer-facing teams:</strong></p><ul><li><strong>Agenda-Driven Insights</strong>: Sales and Customer Success may communicate what they think should be built, rather than what customers actually need.</li><li><strong>Limited Scope</strong>: Their insights often reflect only specific customer segments (e.g., enterprise customers) or lifecycle stages.</li><li><strong>Superficial Understanding</strong>: Time constraints and focus on immediate solutions prevent deeper exploration of underlying issues.</li><li><strong>Personal Bias</strong>: Individual experiences and expertise shape how information is interpreted and shared.</li></ul><p>Beyond customer-facing teams, product managers often rely on product metrics (e.g., adoption, frequency, usage patterns) to identify opportunities.</p><p><strong>The limitations of product metrics:</strong></p><ul><li><strong>Lagging Data</strong>: Metrics usually highlight issues only after they’ve affected customer experience or business performance, making them less effective for predicting trends or identifying opportunities.</li><li><strong>Lack of Context</strong>: Data can pinpoint where problems arise, but it rarely explains the “why” behind them. This requires additional research and customer engagement before decisions can be made.</li></ul><p>Relying solely on quantitative data isn’t enough. Qualitative insights are essential for making informed decisions that drive long-term customer and business value. Without a continuous and unbiased flow of insights, organizations will struggle to be more customer-centric and proactive.</p><h4>Symptoms of a missing insight management</h4><p>If your organization is experiencing any of these signs, it’s time to implement a robust insight management system:</p><ol><li><strong>Reactive, Sales-Driven Decisions</strong><br>Product teams are caught in a cycle of responding to sales and customer requests, creating a roadmap dominated by quick fixes rather than strategic goals. This reactive approach leads to rushed feature development, misaligned priorities, and missed opportunities for long-term growth.</li><li><strong>Lack of Data-Driven Decision-Making</strong><br>Without aggregated, reliable insights, product teams struggle to prioritize effectively. This results in inconsistent decisions, with solutions that often address surface-level symptoms rather than core customer needs or deeper issues.</li><li><strong>Misalignment and Team Inefficiency</strong><br>When product and customer-facing teams are not aligned, miscommunication and missed opportunities arise. Product teams are excluded from strategic discussions, leading to delayed product discovery and features that don’t resonate with customers, wasting resources.</li></ol><p>To break free from this cycle and shift towards proactive, strategic development, B2B companies must adopt a product-driven approach underpinned by continuous insight management.</p><h3>Building a Continuous Insight Management System</h3><p>Insight management is a systematic process of gathering, processing, and clustering insights — from ideas and problems to feature requests and sales blockers. Establishing this process enables product teams to prioritize strategically, rather than reactively.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vkragjLltB1gD8pD2GDy8Q.png" /><figcaption>Continuous Insight Management- Illustration by Julia Bastian</figcaption></figure><p>Customer-facing teams <strong>collect insights (1) </strong>through a defined workflow, and product teams are responsible for <strong>processing this information (2)</strong>. Processing doesn’t just mean reading through the data — it involves sorting, clustering, and structuring it. While this step can be time-consuming for product teams, it’s critical. It helps identify patterns beyond individual requests, uncovering underlying problems. The findings and build up knowledge is the basis for <strong>(re-)defining a vision, strategy and roadmap (3).</strong></p><p>Most important this process doesn’t mean that product teams are no longer in contact with customers and prospects. On the contrary, it <strong>defines the topics for product discovery (4)</strong>and helps to approach each interaction with a clear focus and research question, making those engagements more meaningful, valuable, and effective.</p><h4>A Practical Example: Insight Management at Alasco</h4><ol><li><strong>Collecting insights</strong></li></ol><p>Sales and Customer Success teams interact with prospects and customers daily, making it crucial to capture their insights efficiently. Instead of transcribing every interaction, we created a streamlined process using Slack, allowing both teams to share insights quickly and seamlessly as part of their routine. This ensured consistent information capture and allowed the product team to engage directly with follow-up questions or clarifications.</p><p>We differentiated insights by source (Sales or Customer Success) since they varied in detail, helping us understand differences between users and buyers. Each insight was rated for importance, with options like “Sales Blocker” highlighting critical issues needing immediate action.</p><p>While we use Slack for this workflow, it can be easily adapted to other tools like HubSpot or Notion. Looking ahead, we plan to automate this step using AI tools, like Fathom, to structure insights and integrate them into Productboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y7AYhONVFvQaY9-PWef2CA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0kQX55XpgmmLd5CeaRY2mw.png" /><figcaption>Template in Slack to share Customer and Sales Insights</figcaption></figure><p><strong>2. Processing insights</strong></p><p>Processing insights is the most time-consuming but essential step in building an effective insight management system. At Alasco, we use Productboard to manage insights, though tools like Notion, Jira Product Discovery, or Linear can also work.</p><p>When insights from Sales and Customer Success are submitted, they are funneled into an <strong>inbox in Productboard</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*9YF7SP7d_aQLxtI0etjcZA.png" /><figcaption>Inbox of Insights in Productboard (<a href="https://www.productboard.com/blog/6-benefits-of-processing-research-feedback-in-productboard/">source</a>)</figcaption></figure><p>Each week, product managers review and tag the insights (e.g., “PNG export”) and rate them on a scale of one to three for importance. While the initial rating comes from Sales or Customer Success, product managers can adjust it during review.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*N6OsWIdYISDRhOA49JSb_A.png" /><figcaption>Tagging insights in Productboard (<a href="https://www.productboard.com/blog/6-benefits-of-processing-research-feedback-in-productboard/">Source</a>)</figcaption></figure><p>This creates an aggregated, hierarchical view, helping teams prioritize quickly. Productboard’s flexibility allows for ongoing restructuring as new patterns emerge.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UrTCN-WkXzaZ80hmXPes9Q.png" /><figcaption>Clustering insights in Productboard (<a href="https://www.productboard.com/blog/6-benefits-of-processing-research-feedback-in-productboard/">Source</a>)</figcaption></figure><p>Processing isn’t just about skimming through insights — it’s about deeply engaging with them and synthesising. This hands-on approach helps product managers develop a “gut feeling” of customer needs and market dynamics. By clustering and reorganizing insights, teams can uncover hidden patterns and trends. For example, in one session, I identified a recurring theme that revealed an overlooked customer segment, explaining previously puzzling variations in needs — a true “aha” moment that justified the effort.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2-P3EoYRUDEhQh0VMlWOrA.jpeg" /><figcaption>Processing insights is about synthesizing</figcaption></figure><p>These insights are transformative, enabling clear prioritization and helping teams focus on what truly matters while confidently saying “no” to less critical areas. While AI could streamline the first step, I believe this stage requires the product manager’s direct involvement to fully absorb and understand the insights’ depth.</p><p><strong>3. (Re-)defining the vision, strategy and roadmap</strong></p><p>Processing insights lays the groundwork for shaping the product vision, strategy, and roadmap.</p><p>An insight repository transforms qualitative data into actionable insights by aggregating and quantifying feedback, uncovering new opportunities, and enabling data-informed decisions. This helps craft a customer-centric vision and strategy aligned with the broader needs of your target audience, rather than reacting to individual requests.</p><p>By systematically organizing and leveraging this knowledge, the product team transitions from a reactive mode to a proactive, strategic role. It also strengthens upward management, enabling product managers to effectively advocate for their priorities. Ultimately, insight management empowers product teams to take control, balancing customer needs with long-term business goals, and leading with confidence and clarity.</p><p><strong>4. Defining topics for product discovery</strong></p><p>This process does not mean product teams rely solely on customer-facing teams for information or reduce their own contact with customers and prospects. Instead, it ensures that customer interactions are more focused and productive. By clearly prioritizing discovery topics before conducting interviews or testing, teams can maximize the value of of each interaction..</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ba4FutrtwYZm6zfKmHovIQ.jpeg" /><figcaption>Prioritizing topics for product discovery through Insight Management</figcaption></figure><p>In B2B product management, discovery often requires significant time and effort due to the complexity of topics and the challenge of organizing customer interviews. A well-maintained research repository not only highlights potential opportunities but also identifies the most relevant customers or segments to engage with. All insights gathered during a discovery process are captured again in Productboard by the product teams.</p><p>This structured approach dramatically enhances the outcomes of product discovery. As teams deliver more impactful results, the organization better appreciates the value of discovery efforts, fostering a culture that prioritizes and invests in this business critical process.</p><h4>The Transformative Value of Insight Management</h4><p>A well-established, continuous insight management process offers multiple benefits:</p><ul><li>Customers and Customer-Facing Teams Feel Heard: Each request is captured, demonstrating that all input is valued and reviewed.</li><li>Product Teams Gain Decision-Making Clarity: Teams can clearly articulate why they are prioritizing certain topics over others, using data-driven insights to justify their focus areas.</li><li>A Customer-Centric Product Without Fragmentation: By aligning with the needs of an entire customer segment rather than single requests, the product remains cohesive and scalable.</li></ul><p>This aggregated decision-making reduces the customization burden, ensuring that focus remains on scalable solutions and aligned with strategic goals</p><h3>Insight Management: A Two-Way Street</h3><p>Collecting insights from customer-facing teams is just one part of the process. For insight management to be impactful, product teams must share their aggregated learnings — communicating the key patterns, structures, and concepts across the organization. This transparency drives alignment and benefits multiple teams:</p><ul><li>Marketing gains clearer focus on targeting prospects.</li><li>Sales shifts to value-selling, fostering customer-centric strategies.</li><li>Customer Success improves onboarding and addresses core pain points, accelerating expansion.</li><li>Management makes more informed strategic decisions based on product insights.</li></ul><p>This organizational learning requires effort from the product team. They must present insights during all-hands meetings or hold quarterly sessions with customer-facing teams. By preparing insights in clear, visual formats, they ensure accessibility.</p><p>This process not only strengthens the understanding of customers and the market but also creates a shared vocabulary, improving collaboration and feedback quality. When teams see their contributions leading to tangible impact, it drives more relevant and actionable insights. This exchange builds a customer-centric, product-led culture, accelerates decision-making, and strengthens alignment, fostering long-term success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*et29nNIQi4PAXwrDWX7Rbg.jpeg" /></figure><h3>Conclusion</h3><p>Breaking free from sales-driven decisions requires a shift from reactive feature building to strategic, customer-centric product development. Continuous insight management provides a structured framework to gather, process, and leverage qualitative and quantitative data effectively.</p><p>By implementing this approach, organizations can identify patterns, focus on real customer needs, and align product strategy with long-term goals. The result is a more scalable, cohesive product that delivers value not just for individual customers but for entire segments.</p><p>Ultimately, insight management transforms B2B product teams into proactive leaders, driving sustainable growth and fostering a culture of collaboration and shared understanding across the organization. <strong>Continuous insight management is more than a process — it’s a transformative mindset that unlocks sustainable growth and innovation.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4P3vbQLwuu0crKTA.jpeg" /><figcaption>Julia Bastian</figcaption></figure><p>I’m Julia Bastian, former VP of Product at Munich-based PropTech Alasco, now leading the Research &amp; Innovation Department with a focus on AI.</p><p>With a background as a UX Researcher, Product Manager, and VP Product, my core strength has always been simplifying complex topics and making them accessible to others — a skill rooted in my passion for visual thinking. I thrive on tackling intricate challenges, which is why I’m deeply passionate about B2B product discovery.</p><p>Get in touch with me on <a href="https://www.linkedin.com/in/julia-bastian/">LinkedIn</a> for feedback or questions or book a coaching with me over product academy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2362680edf5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Avoiding Over-Customization in B2B SaaS]]></title>
            <link>https://juliabastian.medium.com/avoiding-over-customization-in-b2b-saas-24676082124c?source=rss-63e22d490e31------2</link>
            <guid isPermaLink="false">https://medium.com/p/24676082124c</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[customization]]></category>
            <category><![CDATA[b2b]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[b2b-product-management]]></category>
            <dc:creator><![CDATA[Julia Bastian]]></dc:creator>
            <pubDate>Tue, 12 Nov 2024 19:29:28 GMT</pubDate>
            <atom:updated>2024-11-12T19:29:28.529Z</atom:updated>
            <content:encoded><![CDATA[<p>Over-customizing for clients can be tempting, especially when it comes to keeping large B2B customers happy. Yet, while minor adjustments might seem harmless, they can quickly add up to a mountain of tech debt that’s hard to manage.</p><p><em>This post explores how over-customization can hinder growth, revealing the hidden costs that often accompany it. Additionally, it provides practical strategies to manage and minimize customizations, helping you maintain a scalable, cohesive product that keeps customers satisfied without compromising on long-term vision</em></p><h3>The Problems of Over-Customization</h3><p>Customization isn’t inherently problematic; for some businesses, particularly those serving large enterprises and generating revenue from tailored solutions, a customization-heavy model can even be a viable strategy. These companies often prioritize bespoke solutions as a core offering, focusing on adapting their software to meet each client’s unique needs.</p><p>However, for most SaaS companies, excessive customization becomes a burden, especially as they scale. In early stages, saying yes to custom requests can be tempting as a way to win new clients and improve retention. But over time, the cumulative effect of these tailored adjustments begins to slow down product development, reduce user experience quality, and even risk the product’s long-term viability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qywFIyj9nHIYA_3uA84Wtw.jpeg" /><figcaption>Problems of customization — illustrated by <a href="https://medium.com/u/63e22d490e31">Julia Bastian</a></figcaption></figure><h4>Slower Development and Hindered Scalability</h4><p>Each unique feature added for a specific client introduces dependencies that can significantly slow down future development efforts. For example, a custom feature built for just one client may initially seem like a small change. However, even a seemingly minor adjustment adds layers of complexity to the codebase, requiring careful consideration of interdependencies and potential conflicts in every new release. A “quick win” customization might look minor, like a feature flag to turn off a dashboard element for one customer. However, from now on every time you touch this area you have to account for this “one-off” exception. Multiply that by five or ten unique requests, and suddenly, you have a web of special cases that complicates each new feature or improvement.</p><h4>Degraded User Experience and Product Coherence</h4><p>By prioritizing the needs of individual clients, products may gradually lose design consistency, resulting in a fragmented and less intuitive experience for the broader user base. Often, product teams make shortcuts, implementing client requests directly without the extra effort needed to align them with the overall system design. Each customization dilutes the overall product design and creates a patchwork feel where custom elements are scattered throughout, leaving users with a confusing interface that lacks the streamlined experience they initially expected.</p><h4>Risk of Losing Product-Market Fit</h4><p>Furthermore, a high volume of custom requests can signal a more fundamental issue: a mismatch between your product and your customer base. Each customization makes your target segment harder to define, as the product now tries to meet too many unique needs. This loss of focus can force some companies into reengineering their product entirely, realizing that they’ve morphed into a tool that serves too broad an audience with limited depth for any specific group. In extreme cases, such companies may face a difficult choice: either restructure the product to realign with a focused customer base — often at the cost of losing certain clients — or risk becoming unsustainable, offering limited value across too many segments.</p><p>Over time, excessive customization can transform a SaaS product from a streamlined solution into a complex and fragmented tool, challenging both the company’s growth and the product’s appeal to its core audience.</p><h3>The Hidden Costs of Customization</h3><p>Many companies calculate the ROI of customization requests, which helps clarify the revenue potential and direct costs involved. But often, the actual costs are underestimated due to hidden factors that aren’t immediately obvious.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uet3kKSADKQbyzdcLVuytA.jpeg" /><figcaption>Hidden Costs of Customization — illustrated by <a href="https://medium.com/u/63e22d490e31">Julia Bastian</a></figcaption></figure><p>In one of his <a href="https://www.linkedin.com/posts/johnpcutler_the-you-spend-on-engineers-is-probably-activity-7187872057739677696-40BK?utm_source=share&amp;utm_medium=member_desktop">LinkedIn posts</a>, <a href="https://medium.com/u/4c3f4fe11e6b">John Cutler</a> insightfully pointed out, “The money you spend on engineering is probably the least of your concerns when it comes to thinking about ROI.” Beyond the immediate engineering costs, he mentions significant hidden costs that deserve attention:</p><ul><li><strong>Opportunity Costs</strong>: Customization can divert focus from other high-impact projects across disciplines.</li><li><strong>Implementation Costs</strong>: Not just engineering, but UX and product design also carry expenses for initial development and ongoing incremental improvements.</li><li><strong>Delivery and Maintenance Costs</strong>: Processing, storage, and monitoring can add ongoing operational costs.</li><li><strong>Internal Training Costs</strong>: Teams need training to sell and support the feature, sometimes across multiple departments.</li><li><strong>Marketing Costs</strong>: Marketing efforts for the feature may target both existing and potential customers, adding new budget needs.</li><li><strong>Coordination Costs</strong>: Cross-functional teams require extensive coordination to align on new initiatives, which can be resource-intensive.</li><li><strong>Documentation and Usability</strong>: New features need to be documented for users and maintained, adding long-term costs to the system’s usability and team efficiency.</li><li><strong>Long-term System Complexity</strong>: Each customization can increase the codebase’s complexity, slowing future engineering work, requiring additional hires, and ultimately reducing overall system flexibility.</li></ul><p>These costs persist as long as the feature is in use, and unless the feature is sunsetted, they often only increase over time. Being aware of these hidden costs can lead to better decision-making around which customizations truly add value in the long run.</p><h3><strong>Reducing the Harm of Customization</strong></h3><p>There are scenarios where SaaS companies may still choose to implement customizations, despite the risks. This can be especially valuable in early phases of a company’s growth or when entering a new market segment, where rapid learning and testing product-market fit are critical. Other common reasons include short-term goals like enhancing metrics for a funding round or converting a major client with high market influence, which could serve as a signal to attract other potential customers.</p><p>When a deliberate decision is made to proceed with customization, product teams should consider these strategies to reduce potential downsides:</p><ul><li><strong>Abstract Unique Requests for Broader Use</strong><br>When a large client requests a unique feature, approach it with a discovery mindset. Ask if this need reflects a broader trend that could be adapted to suit a wider market. This prevents creating a fragmented product while still meeting client demands.</li><li><strong>Leverage Customization as a Learning Opportunity</strong><br>Treat feature requests as a way to test broader market interest. For example, if a significant client in a new segment requests a feature, consider developing it as an MVP with a time-limited trial. Use this period to gather insights and evaluate if the feature could benefit a larger audience.</li><li><strong>Reframe Requests as Configurable Features</strong><br>Explore if the customization can be made configurable rather than bespoke. By developing a solution that can be toggled or tailored within the product, you increase its appeal across different customers while preserving scalability and usability.</li><li><strong>Evaluate Product-Market Fit Continuously</strong><br>Use customization requests as a pulse check for product-market fit. If you’re receiving frequent customization requests, it may signal a gap in your core offering. Regularly assess these needs to ensure your product aligns with the evolving demands of your target audience.</li></ul><p>By approaching customization carefully, SaaS companies can fulfill unique client needs while minimizing long-term risk and maintaining product coherence.</p><h3>Handling Pricing of Customization</h3><p>In B2B niche markets (like the construction industry), customers are used to customizations and may be willing to pay for them, especially if they are accustomed to traditional software providers where customization was more the norm. However, for SaaS startups, one-time payments for custom work aren’t as attractive as recurring revenue, which is essential for sustainable growth and valuation.</p><p>To approach customization pricing effectively, here are some strategies to reduce the risk while maximizing both revenue potential and long-term value:</p><ul><li><strong>Use Pricing as a Demand Filter</strong><br>Setting a price on custom requests not only compensates for the work but also acts as a filter to gauge urgency. When a fee is associated with a custom feature, it clarifies how critical that feature truly is to the customer. If a client hesitates to pay, it often signals that the request was more of a “nice-to-have” than a necessity. This helps product teams prioritize features with genuine business impact, while deprioritizing those that may dilute the core product’s value.</li><li><strong>Prioritize Recurring Revenue over One-Time Payments</strong><br>For customizations that are deemed essential, try to structure payments as part of a recurring model. Rather than a single charge, consider integrating customizations as part of a contract expansion, upsell, or premium package</li><li><strong>Use Customization to Build Strategic Partnerships</strong><br>In cases where a custom feature could benefit a significant client with industry influence, it may be worthwhile to approach customization as part of a strategic partnership. This might mean offering reduced rates for highly visible clients in exchange for case studies, testimonials, or co-marketing. Such collaborations not only bring recurring revenue but also enhance credibility and attract new clients with similar needs.</li></ul><p>By carefully structuring customization pricing, SaaS companies can manage customer demands strategically, focusing on those that bring both immediate value and long-term alignment with product goals.</p><h3>Strategies to Reduce Customization and Maintain Focus</h3><p>To avoid the risks of over-customization, it’s essential to estabish three core elements: a clear product strategy, an effective insight management, and education for both internal teams and customers.</p><ol><li><strong>Define and Communicate a Clear Product Strategy to Guide Customization Decisions<br></strong>A solid product strategy does more than outline what the product will achieve — it also clarifies what it won’t do. By having a well-defined product strategy, you establish clear boundaries that help you evaluate customization requests against your core vision and target market. This clarity simplifies decision-making; if a customization request falls outside the defined scope of your product strategy, the choice to decline becomes straightforward.<br>To ensure alignment, share this strategy with internal stakeholders, including Sales and Customer Success teams, so they understand both the product’s purpose and its limitations. This enables them to set realistic expectations with clients, reinforcing why certain customizations won’t be pursued. By focusing on a shared vision, you can avoid ad hoc customizations that might dilute the product’s focus, ensuring that all development efforts contribute directly to scalable, strategic growth.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4IOXRJB6wo6scvcP1tcl_A.jpeg" /><figcaption>Decision Stack by Martin Erikson — illustrated by <a href="https://medium.com/u/63e22d490e31">Julia Bastian</a></figcaption></figure><p><strong>2. Establish Continuous Insight Management to Abstract Single Feature Requests</strong></p><p>To reduce the pressure of responding to individual customization requests, it’s essential to build a structured insight management process. In many B2B companies, much of the customer and market knowledge resides within customer-facing teams like Sales and Customer Success. These teams are often the primary source of feature requests or customization demands, as they have direct contact with client needs and challenges. Instead of acting on each request individually, creating a systematic process for gathering, processing, and clustering insights helps product teams take a more strategic approach.</p><p>This process allows you to quantify the qualitative data that flows in daily, uncovering patterns, understanding core issues, and deepening knowledge about your customer segments. With these insights, you can shape a customer-centric strategy that meets the broader needs of your target audience rather than reacting to isolated requests.</p><p>At Alasco, for example, Customer Success and Sales teams use a simple template to document every customer insight, issue, feedback point, idea, or requirement. Product teams then process this input within a product management tool, such as Productboard, where insights are organized to reveal patterns. This aggregated approach helps product teams make decisions based on overall trends rather than individual demands, guiding both strategic planning and roadmap priorities. It also informs where product discovery efforts should focus next.</p><p>A well-established, continuous insight management process offers multiple benefits:</p><ul><li><strong>Customers and Customer-Facing Teams Feel Heard:</strong> Each request is captured, demonstrating that all input is valued and reviewed.</li><li><strong>Product Teams Gain Decision-Making Clarity:</strong> Teams can clearly articulate why they are prioritizing certain topics over others, using data-driven insights to justify their focus areas.</li><li><strong>A Customer-Centric Product Without Fragmentation:</strong> By aligning with the needs of an entire customer segment rather than single requests, the product remains cohesive and scalable.</li></ul><p>This aggregated decision-making reduces the customization burden, ensuring that focus remains on scalable solutions and aligned with strategic goals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lPLtipFYoh4pOftAlFcvaw.jpeg" /><figcaption>Continuous Insight Management- Illustration by <a href="https://medium.com/u/63e22d490e31">Julia Bastian</a></figcaption></figure><p><strong>3. Educate Internal Teams and Customers on the SaaS Model and its Benefits</strong></p><p>Educating internal teams and customers about the SaaS model — and the implications of over-customization — is essential for maintaining a scalable product that serves a broad market effectively. Start by communicating with internal stakeholders, especially Sales, Customer Success, and executive leadership, about the long-term impacts of customization on product scalability. Then, extend this education to customers so they understand that SaaS operates differently than custom-built software and is optimized for continuous, scalable improvements rather than unique, one-off builds.</p><p>Help internal stakeholders recognize that customization involves more than immediate development costs. Each one-off feature brings hidden costs: long-term maintenance, slower product iterations, added support, and potentially lost focus on the product’s core value. Being transparent about these hidden costs allows both teams and customers to evaluate if a specific request aligns with the product’s strategic direction and long-term goals.</p><p>Creating educational resources, such as a slide deck or a knowledge base, can be a useful way to communicate these points. Consider including the following key ideas:</p><ul><li><strong>Customer-Centric ≠ Custom-Built</strong>: Emphasize that SaaS is designed to deliver continuous improvements that benefit the majority rather than bespoke features for individual customers. Illustrate how over-customization can drive up costs, slow down development, and lead to less intuitive interfaces as the product becomes fragmented by unique solutions.</li><li><strong>Collaborative Development Approach</strong>: Reinforce that while customer input is highly valued, SaaS products must evolve to serve the entire user base. Position customization requests as opportunities for collaborative discovery. Invite customers to participate in interviews or testing for new features, giving them a voice in the product’s evolution without committing to bespoke changes. This way, they benefit from their input as well as improvements driven by the broader community of users.</li><li><strong>Highlight the Value of Standardization for Scalability</strong>: Remind customers of SaaS’s core advantage — standardized, continuously improved software. Outline benefits such as ongoing product enhancements, lower licensing costs, a consistent and intuitive user experience, and long-term product value. Emphasize that these benefits are possible because the product evolves to meet the collective needs of a diverse customer base rather than focusing on one-off solutions.</li></ul><p>By educating both internal and external stakeholders, you can build a shared understanding of the SaaS model’s value and foster alignment with your product’s scalable, customer-centric vision. This approach helps to reduce the pressure for customizations, allowing the product to evolve with broader input while preserving the flexibility and efficiency SaaS is known for.</p><h3>Conclusion</h3><p>In B2B SaaS, customization requests can be a double-edged sword — potentially valuable for customer satisfaction but often challenging for product scalability and strategic growth. While every client’s needs may feel urgent, over-customization can hinder development, degrade user experience, and dilute product focus. By establishing a clear strategy, insight management process, and educational approach for internal teams and customers, SaaS companies can maintain a balanced approach to customization that preserves the product’s core value and appeal to a broader market.</p><p>Ultimately, achieving this balance requires thoughtful prioritization, collaborative communication, and a commitment to serving the needs of many rather than a few. By approaching customization strategically, B2B SaaS companies can deliver a scalable, high-value product that not only meets the core needs of their customers but also positions the company for sustainable growth in an ever-evolving market.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vEibVsND2_TQtHDm.jpeg" /></figure><p>I’m Julia Bastian, former VP of Product at Munich-based PropTech Alasco, now leading the Research &amp; Innovation Department with a focus on AI.</p><p>With a background as a UX Researcher, Product Manager, and VP Product, my core strength has always been simplifying complex topics and making them accessible to others — a skill rooted in my passion for visual thinking. I thrive on tackling intricate challenges, which is why I’m deeply passionate about B2B product discovery.</p><p>Get in touch with me on <a href="https://www.linkedin.com/in/julia-bastian/">LinkedIn</a> for feedback or questions or book a coaching with me over product academy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24676082124c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Visual Thinking — an essential skill in Product Management]]></title>
            <link>https://juliabastian.medium.com/visual-thinking-an-essential-skill-in-product-management-c4913a611a07?source=rss-63e22d490e31------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4913a611a07</guid>
            <category><![CDATA[visualization]]></category>
            <category><![CDATA[b2b-product-management]]></category>
            <category><![CDATA[product-discovery]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[visual-thinking]]></category>
            <dc:creator><![CDATA[Julia Bastian]]></dc:creator>
            <pubDate>Mon, 21 Aug 2023 13:05:33 GMT</pubDate>
            <atom:updated>2023-09-04T14:29:49.231Z</atom:updated>
            <content:encoded><![CDATA[<h3>Visual Thinking — an essential skill in Product Management</h3><p>Visual thinking is a process of learning new information and organizing thoughts by visually processing them. Learn how to make use of it in product management.</p><p>Traditional ways of working with many reporting layers, written handovers, and linear structures have been erupted by agile, iterative, and lean approaches “All these new ways of working have one thing in common; they need a high degree of visual techniques to stimulate collaboration. These techniques improve the speed, creativity and effectiveness of teams as they collaborate in a dynamic environment” (Willemian Brand, 2022)</p><p>Luckily, visualization has already found its way into our daily work through methods like design thinking, Kanban boards, user story maps or prototypes. However, there is way more value to be leveraged as soon as all product people start to learn, practice, and apply not only visualizations but visual thinking in their daily work.</p><p>Therefore, I believe that visual thinking is a central skill all product managers should have or start to practice.</p><h3>What is visual thinking?</h3><p>Visual thinking is a process of <strong>learning new information and organizing thoughts by visually processing them</strong>. It can be used to make complex information which we see, hear, or read accessible — not only for ourselves but also for others.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q7EtP3p8A1NCcOP_jWs9-g.jpeg" /><figcaption>The process of visual thinking (Julia Bastian)</figcaption></figure><p>Visual thinking helps me process information by connecting them with mental models and images in my brain. Mental models are simplified representations that reflect processes and structures in the world which have developed from our past experiences, memories, perceptions, and knowledge. They are an essential part of our daily lives because they influence our thinking, our behavior, and our approach of solving problems.</p><p>Jay Forrester, a pioneer in digital computer development, author, and lecturer, explained it that way: “<em>The image of the world around us, which we carry in our head, is just a model. Nobody in his head imagines all the world, government or country. He has only selected concepts, and relationships between them, and uses those to represent the real system.”</em></p><p>Therefore, visualizing my thought process helps me to externalize those mental images and make them explicit, in order to:</p><ul><li>get access to what I am actually thinking</li><li>analyze my own thinking (and certain gaps it might have)</li><li>and to share my thoughts with others</li></ul><h3>What’s the value of visual thinking?</h3><p>Many people who want to start with visual thinking see the value in the output of the process: the visualization itself. And yes, the visualization is great! It helps to communicate thoughts, share information and create a common understanding with others.</p><p>However, I think the biggest value lies in the process itself: the creation of the visualization. The creation of a picture enables us to externalize our thought process. This externalization helps to focus on a certain aspect of a topic and, therefore, have less information overload — especially for complex matters this is key! Visual thinking brings me into a state of really deep thinking and concentration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1vmooyMBQ2So5TN81mWYRw.jpeg" /><figcaption>The value of visual thinking (Julia Bastian)</figcaption></figure><p>When I draw:</p><ul><li>I order my thoughts</li><li>I see patterns, I have not seen before</li><li>I am able to simplify complex matters</li><li>I get new ideas</li></ul><p>All of this has a huge impact on working with others. By visualizing, I make my perception of the world accessible for others. This helps to discuss complex matters and, therefore, leverage the value of cooperation.</p><h3>How can you make use of visual thinking in product management?</h3><p>While visualization is already used a lot for the ideation of solutions and prototyping of ideas, many product managers miss out on using visualization in the phase before: the discovery of new product and market opportunities. In this phase the most important aspect is not the visualization or the design (e.g. a mock-up of the solution) but the abstraction of the topic, the alignment in the team, the reduction of complexity and the preciseness of understanding the customer problem.</p><h4>Getting alignment in the team &amp; defining a starting point</h4><p>When discovering a new opportunity, it is essential, to begin with the knowledge which is already existing in the team/organization. You must align the team around the status quo to give a clear starting point:</p><blockquote>What do we already know? What do we assume to know? What do we not know? Where do we disagree?</blockquote><p>This is crucial to clarify the scope, the research questions and the hypotheses on which the research process will be based. Many teams who skip this alignment in the beginning tend to get lost throughout the process or waste time in endless discussions.</p><p>In order to get this alignment in the beginning, I am a huge fan of Teresa Torres´ experience map, which she explains in her book C<a href="https://www.amazon.com/Continuous-Discovery-Habits-Discover-Products/dp/1736633309">ontinuous Discovery Habits</a>. I like that the method describes how a team should approach the visualization process, not what the output looks like.</p><p>The steps Teresa Torres describes are the following:</p><ol><li><strong>Set the scope</strong> of the experience map: this defines how broad or narrow the topic will be</li><li><strong>Work individually</strong> — to avoid group thinking in the beginning</li><li>Experience maps are <strong>visual not verbal</strong></li><li><strong>Explore the diverse perspectives</strong> of you team: share your drawing, clarify your thinking and answer questions</li><li><strong>Co-create</strong> a shared experience map in the team</li></ol><p>Eventually, an experience map is just a visualization of what you know — it can be a process, a concept map, a story line, a graph or what ever helps to get a common understanding of the topic.</p><h4>Synthesizing information &amp; creating insights</h4><p>After or while doing interviews, screening data and researching online it is important to synthesize the information that is being collected continuously. Synthesizing is not summarizing! It is not about bringing information into fewer words — it is about comparing or combining topics and finding patterns in order to create new insights.</p><p>And yes, visualization is the best way to do this and to find those patterns! There is not ONE visualization that you should always use, but especially when you get started, it helps to have a look at examples of how information can be visualized:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lswuUR4gINg8_OHTynrEcg.jpeg" /><figcaption>Examples of how information can be visualized (Julia Bastian)</figcaption></figure><p>There is no right or wrong! It is just about getting started and doing it. I iterate continuously on my drawings and if I get stuck, I try to change the perspective on how I look at the collected information.</p><p>I always recommend product managers not to do all the research and then start synthesizing. There is no clear point at which to stop and synthesize - it is about <em>“synthesizing as you go”.</em></p><p>This is how I do <em>“synthesizing as you go”</em>:</p><ol><li>During an interview, I write down the essential information that I am hearing (and a second person is doing this as well)</li><li>We follow up with a de-brief of the interview and summarize the information.</li><li>Then, I draw the underlying structure which I have heard in the interview and write down the most important insights that come to my mind while drawing. I might even connect the drawing with the experience map from the beginning.</li><li>I share my drawing with the team, involve their feedback, clarify open topics and improve the interview questions for the next interview.</li><li>Then I repeat this for a couple of interviews.</li><li>After having conducted a couple of interviews and maybe having involved other data points, I look at all the drawings and condense them in a new visualization. Many times I suddenly find a pattern or a structure that I had not been aware of before and which brings clarity or preciseness into the research, which makes a huge difference in the end.</li></ol><h4>Share learnings and drive organizational learning</h4><p>However, all of those visualizations are not just important to find patterns and get a deeper understanding of the customer, they also help to drive organizational learning. Not only product and engineering needs to understand the market and the customer - (product) marketing, sales and customer success also need to get educated.</p><p>Therefore, the product team should not only share information to feature launches but also on underlying market structures, customer processes and pain points. Visualizations created throughout the discovery process are a great tool to tell stories and take the whole organization on a continuously learning journey. Here you can also get in support from Designers to make your drawings more appealing if you do not feel comfortable to share yours with the whole organization.</p><h3>How to get started?</h3><p>When you start with visual thinking, I would always recommend to start with pen &amp; paper. You get reminded of childhood days when you where not afraid of drawing and you can just start exactly at this moment, without any setup and distraction.</p><p>As soon as you feel comfortable with pen &amp; paper you can start using digital tools like <a href="https://miro.com/de/">Miro</a> , <a href="https://excalidraw.com/">Excalidraw</a>, or apps like <a href="https://concepts.app/de/">Concepts</a> (this is the one I use) or <a href="https://procreate.com/">Procreate</a> on a tablet. It took me some practice to feel comfortable with a digital drawing tool, but as soon as you have some routine, it is just amazing :)</p><p>Furthermore, I can recommend to practice drawing by setting up an icon library or a visual alphabet. This helps to practice thinking in simplified pictures - for instance: an idea is a light bulb, a goal is a dart board or a start up is a rocket.</p><p>And, do not confuse visual thinking with graphic recording. The focus of visual thinking is not summarizing information and making it look appealing — the focus is the process of thinking and collaborating through visualizations. Therefore, the visualization does not have to look “perfect”, it is about making it good enough to understand a topic, to discuss it, and to learn.</p><p>In the end the most important thing is just to get started, trust in yourself and to have the courage to follow your gut feeling in drawing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h2LUatlXbWR9tWULfUOtBA.jpeg" /><figcaption>How to get started with visual thinking (Julia Bastian)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LYRSIRhGLSpNthpoAycS2g.jpeg" /></figure><p>My name is <a href="https://www.linkedin.com/in/julia-bastian/">Julia Bastian</a> and I am VP product at the Munich-based PropTech <a href="https://www.alasco.de/">Alasco</a>.</p><p>During my time as UX researcher, Product Manager, and VP Product my biggest strength has always been to simplify complex topics, and therefore, make it accessible for others — and the basis for this has always been visual thinking.</p><p>Since I love complex topics I have found my passion in the B2B product world and in product discovery.</p><p>Get in touch with me on <a href="https://www.linkedin.com/in/julia-bastian/">LinkedIn</a> for feedback or questions and have a look at the <a href="https://alasco.tech/">Alasco Tech Blog</a> for more content.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4913a611a07" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing a Remote (Ideation) Workshop with Miro]]></title>
            <link>https://medium.com/alasco-tech/designing-a-remote-ideation-workshop-with-miro-cdca8a5e881?source=rss-63e22d490e31------2</link>
            <guid isPermaLink="false">https://medium.com/p/cdca8a5e881</guid>
            <category><![CDATA[remote-workshop]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[ideation-workshops]]></category>
            <category><![CDATA[ideation]]></category>
            <category><![CDATA[miro]]></category>
            <dc:creator><![CDATA[Julia Bastian]]></dc:creator>
            <pubDate>Fri, 08 Jan 2021 00:00:00 GMT</pubDate>
            <atom:updated>2021-01-13T17:20:22.761Z</atom:updated>
            <content:encoded><![CDATA[<p>I aced a remote Ideation Workshop with <a href="https://miro.com/about/">Miro</a> — here is how and what I have learned.</p><p>I knew that I did not want the remote workshop to be a poor version of an on-site one. Therefore, I designed the workshop in a way that uses the remote setting as an advantage — and Miro is a great tool for that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EI7hIKAQIdlcXa9twavPtg.png" /><figcaption>“House of Ideation” (using Miro) — Source: <a href="https://miro.com/miroverse/the-amsterdam-house/">https://miro.com/miroverse/the-amsterdam-house/</a></figcaption></figure><p>Besides the main goal of a workshop (e.g. creating ideas, education), it should be fun and inspiring for the participants and it should get them out of their daily routine. In a non-remote setting, this is rather easy, using posters, various cards, pens stickers, etc., but in the current situation, these items need to be transferred to an online, easy-to-use setting. Miro gave me the perfect opportunity to do so, with its many possibilities, one can overcome the drawbacks of working remotely.</p><p>For the Ideation Workshop, we decided to create a “House of Ideation” where each team moves through independently — as we are a Proptech company, a house seemed quite suitable to me (other ideas: traveling from one island to the next or driving a car to different places). You can be really creative but you should think of a theme that connects the process and the setting in a way that makes sense and does not take away too much attention from the main task. My house of ideation was built on the idea of “the Amsterdam House”, which is a great template (find it here <a href="https://miro.com/miroverse/the-amsterdam-house/">https://miro.com/miroverse/the-amsterdam-house/</a>)</p><h3>Taking a tour through the house of ideation</h3><p>Welcome to the Alasco house of ideation and a couple of its rooms! — I hope this gives you some inspiration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*g5ZcPs5s1jDvYf6N.png" /></figure><p>First of all, I think it is essential to create a structure in every room that helps the participants to get orientation. Therefore, I have given each room a name and an emoji which can be found on the agenda as well, and I have added a time and a description. The Entrance is the first room to meet up with the team. It gives some general information and invites the participants to become active through the check-in board.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*23hfvc5WjjUubKjT.png" /></figure><p>In the Ideation room, the teams have different boards to become creative. The easiest thing to work with in Miro are probably the post-its. Therefore, it is ideal to do brainstorming sessions. Compared to an on-site workshop you do not have the problem of bad handwriting and the clustering of post-its is way faster. Furthermore, I love that you as a facilitator do not have the effort of digitizing post-its afterwards (I think every workshop facilitator knows this struggle).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YsJ0QXL-NepXl1YD.png" /></figure><p>Since the workshop was shortly before Christmas, I have added a little game in the break room. Every team was able to decorate their Christmas tree and at the end of the day, we even nominated the prettiest. It is just fun for the participants (and the facilitator) to add little games like this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hGeskxk_NB3SBU2w.png" /></figure><p>In a remote setting, it is really difficult for a facilitator to see if all teams are on track and have understood the task since you can not simply walk around. Furthermore, the psychological barrier for participants to ask the facilitator for help, when they are stuck, is higher. This can lead to a huge waste of time for the teams. Therefore, it is important to be as precise as possible. I have added the room “Library” which gives an example of how the pitch, in the end, could look like. I also added an example of how a prototype of an interface could look like to take away the fear of trying this out. Nevertheless, I found it to be extremely helpful to talk to the teams from time to time to make sure they are on track and understood everything.</p><h3>My Learnings from the remote workshop with Miro</h3><p>Even though I have done many on-site workshops, it was my first workshop with Miro and I wanted to share some of my learnings that might help others for their first try!</p><ul><li>I really liked that I as a facilitator was always able to jump into the different team´s Miro boards and see their progress</li><li>Many people worked with Miro in the Workshop for their first time. Nevertheless, it was easy to use for everyone. You can also start with some warm-up games on Miro, to overcome inhibitions. Try it out!</li><li>You have to make a decision beforehand whether you want all teams to work on one board (if you have many participants this might influence the loading time of Miro) or on multiple boards. I have decided to create one Master Board and then copy it for each team since it was more important for me to have a good performance of Miro than to have the teams see each other’s progress.</li><li>After the preparation you have to lock all items and especially backgrounds on the Miro Board otherwise the participants can move every little element.</li><li>Miro has many great add-ins. I especially liked the wireframe library since it is a very fast way to prototype first solutions.</li><li>If you facilitate a workshop with many participants and boards it makes sense to have a paid plan. I decided to take the “consultant plan” which was great because you can invite an unlimited number of people and you do not have to pay for each one.</li><li>In addition to Miro we worked with Zoom and its breakout rooms which is a great way to timebox, give instructions or do some warm-up exercises</li></ul><p><strong>How have your experiences been with Miro so far? Any learnings you have made and that you want to share?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7zfEXn-PNyaPxER3.jpeg" /></figure><p>My name is <a href="https://www.linkedin.com/in/julia-bastian/">Julia Bastian</a> and I am the Head of Product at the Munich-based Proptech <a href="https://www.alasco.de/">Alasco</a>.</p><p>I am really proud to work for a company where we highly appreciate different perspectives and invest resources in the creation of new ideas!</p><p>Get in touch with me on <a href="https://www.linkedin.com/in/julia-bastian/">LinkedIn</a> for feedback or questions.</p><p><em>Originally published at </em><a href="https://alasco.tech/2021/01/08/innovation-day.html"><em>https://alasco.tech</em></a><em> on January 8, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cdca8a5e881" width="1" height="1" alt=""><hr><p><a href="https://medium.com/alasco-tech/designing-a-remote-ideation-workshop-with-miro-cdca8a5e881">Designing a Remote (Ideation) Workshop with Miro</a> was originally published in <a href="https://medium.com/alasco-tech">Alasco Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lean UX At A SaaS Startup]]></title>
            <link>https://medium.com/alasco-tech/lean-ux-at-a-saas-startup-f0909cdea06?source=rss-63e22d490e31------2</link>
            <guid isPermaLink="false">https://medium.com/p/f0909cdea06</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[lean-ux]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Julia Bastian]]></dc:creator>
            <pubDate>Thu, 25 Jun 2020 00:00:00 GMT</pubDate>
            <atom:updated>2020-07-05T15:32:57.659Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>You don’t have time to NOT do research</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*ZQkdDCpkTfxMh8ua.png" /></figure><p><em>Why Lean UX?</em></p><p>Especially in startups, we are working in an environment of limited resources and the organization has to make clear decisions on what to invest them in. Nevertheless, the result of this should not be, to not invest in research! It is actually the other way around — because of limited resources you do not have the time to NOT do research! Limited resources force you to be way more precise and clear about your research, therefore, Lean UX is essential.</p><p>In my opinion, Lean UX is a mindset that impacts the whole company. It combines many different approaches from lean, agile to design thinking, and creates a holistic perspective on designing user experiences in rapid, iterative cycles that solve real customer problems. Furthermore, it strives to reduce waste throughout the whole process.</p><h3>What influence does the context of B2B / SaaS have on UX?</h3><p>In many books, UX seems simple because the examples are based on B2C products. Working at Alasco, I have experienced that designing Software for Businesses brings other conditions and therefore other challenges:</p><ul><li><strong>We are working in a field of specialized knowledge:</strong> It takes much time to just understand how our customers are working right now since I have no specialist background in the construction industry. However, not being an expert in this field as a UX Researcher also brings many advantages, because you ask questions that are not influenced by any learned concepts in this field.</li><li><strong>We have a limited number of users:</strong> Since people in a coffee shop or in the city are not our typical target group I can not just “go out of the building”. Our customers and users are experts in the field and therefore their number is limited.</li><li><strong>Users and customers are not the same:</strong> The person making the decision to buy our product is not necessarily our main user. Therefore, we have to understand the motivation, needs, and pains of both.</li><li><strong>Relationship to customers is key:</strong> In order to get enough and especially fast feedback from users, the relationship to the users as a UX researcher is essential. This takes time to build up and especially to keep.</li><li><strong>Long onboarding cycles:</strong> Since we have long onboarding cycles, it always takes time until users are actually using new features, therefore, feedback and especially metrics are lacking behind.</li></ul><h3>5 Facts about Lean UX and our approach at Alasco</h3><h4>1. Lean UX is a company effort</h4><p>Lean UX is not something the product team does by themself. The essential part is that you enable a process, in which the insights of all customer-facing teams are gathered. Since sales and customer success teams are in contact with our prospects and customers on a daily basis, they are the ones who have a deep understanding of their motivations, needs, and pains. We, as the product team, are in daily exchange with them, and tools like <a href="https://www.productboard.com/">Productboard</a> help us gather all the information at one place to cluster and categorize the topics in order to identify patterns. This aggregated information has to be aligned with the vision and strategy of the company and helps us to continuously adjust our roadmap based on new insights and learning. Furthermore, our engineers are involved in customer interviews and testing because it is essential that they build up a deep understanding and empathy for our customers as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*66eZUrEMfDscVh-a.png" /></figure><h4>2. Lean UX is iterative</h4><p>During the whole product development process, we strive to reduce uncertainty. In order to do so, we do not only work in sprints for building a feature, but also for understanding the problem and creating solutions. This approach has shown to be very useful for us because it is always difficult to know when to stop doing explorative research or testing possible solutions. Therefore, we set a scope for a timeframe of two weeks (our sprint length). This scope includes research questions and hypotheses we want to validate or actually INvalidate. After each sprint, we share the information within the product team and decide on what to do: Iterate? Move on? Kill it? Furthermore, a feature for us is not finished when it is shipped, it is just ready for the next iteration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZQkdDCpkTfxMh8ua.png" /></figure><h4>3. Lean UX is fast &amp; cheap</h4><p>In everything we do, we strive to reduce waste. One major factor in producing waste is multitasking. Therefore, we love to work in design sprints in order to focus on just one topic for a couple of days. During those sprints, we define hypotheses, do interviews, create solutions, and test them. Another factor of producing waste is building features when there is still too much uncertainty because you might just end up with a feature that no one needs or which does not solve a pain. Therefore, prototyping and testing are an integral part of our process. Prototyping can be done in many different ways — from sketches, over excel to clickable dummies. We decide on the type of prototype and testing based on the question we want to answer or the hypotheses we want to validate.</p><h4>4. Lean UX is data-driven</h4><p>Lean UX is also about the right balance between qualitative and quantitative research. While qualitative research helps us to understand the “why” behind the behavior, quantitative research gives us hints about where to look at and measure changes. Therefore, one of the things we measure is the frequency (how often is it used by single users?) and the adoption (how many use it?) of our features. This helps us to check if we have reached our intended goals, to identify features we need to improve or even kill features that are underperforming.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LguGI-dTIppDYF5i.png" /></figure><h4>5. Lean UX is pain-driven</h4><p>Many approaches focus on customer-driven or user-centered design, however, Lean UX is more than this: it is pain-driven! Since we strive to solve real customer problems, we do not want to digitize shitty processes, we want to rethink processes, simplify them, and make them more agile. Digitization is just our vehicle to do so. Working pain-driven changes the way you are handling user requests. Users ask for things they are familiar with, not necessarily what would be best for them. That is why it is so important to understand the problems behind every feature request. Based on the problem we can build solutions that solve problems, in a way no one has thought of yet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uIwgfz-mqxS5ZUGG.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GnNBx9seOCrbtD-uNqiHgw.jpeg" /></figure><p>My name is <a href="https://www.linkedin.com/in/julia-bastian/">Julia Bastian</a> and I am the UX Researcher at the Munich based Proptech <a href="https://www.alasco.de/">Alasco</a>.</p><p>I am really proud to work for a company where UX and customer-centricity are not just buzzwords, but were this an essential part of our mindset. Since we are growing really fast I am excited to learn how we as a team can make our approach scalable and improve it continuously.</p><p>Get in touch with me on <a href="https://www.linkedin.com/in/julia-bastian/">LinkedIn</a> for feedback or questions.</p><p><em>All the illustrations in this article are drawn by myself</em></p><p><em>Originally published at </em><a href="https://alasco-tech.github.io/2020/06/25/lean-ux.html"><em>https://alasco-tech.github.io</em></a><em> on June 25, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f0909cdea06" width="1" height="1" alt=""><hr><p><a href="https://medium.com/alasco-tech/lean-ux-at-a-saas-startup-f0909cdea06">Lean UX At A SaaS Startup</a> was originally published in <a href="https://medium.com/alasco-tech">Alasco Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>