<?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 Shavin Peiries on Medium]]></title>
        <description><![CDATA[Stories by Shavin Peiries on Medium]]></description>
        <link>https://medium.com/@shavinpeiries?source=rss-e765c0b29e18------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*_7w_MlkXr0WTDntfBnROBQ.png</url>
            <title>Stories by Shavin Peiries on Medium</title>
            <link>https://medium.com/@shavinpeiries?source=rss-e765c0b29e18------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 08:20:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@shavinpeiries/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[“The demo is in 5 hours”: How panic taught us a better way to prototype with v0]]></title>
            <link>https://shavinpeiries.medium.com/the-demo-is-in-5-hours-how-panic-taught-us-a-better-way-to-prototype-with-v0-71091cd971eb?source=rss-e765c0b29e18------2</link>
            <guid isPermaLink="false">https://medium.com/p/71091cd971eb</guid>
            <category><![CDATA[prototyping-techniques]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Shavin Peiries]]></dc:creator>
            <pubDate>Tue, 19 Nov 2024 16:33:54 GMT</pubDate>
            <atom:updated>2025-01-28T17:13:37.617Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4hsB5rQd7F5U8WBP" /><figcaption>Photo by <a href="https://unsplash.com/@sigmund?utm_source=medium&amp;utm_medium=referral">Sigmund</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>“We just scheduled a demo with a potential user. They want to see the new sales dashboard for feedback. Can you have something ready by 2PM?”</p><p>That Slack message from my founders hit me like a bucket of cold water. I looked at my screen: one barely-functional dashboard card, a messy Excel mockup full of sample data, and about 10 browser tabs of half-finished research. The dashboard redesign we’d been planning was supposed to take days, not hours.</p><p>The normal playbook was out the window. Usually, we’d spend days going back and forth:</p><ul><li>Mock up designs in Figma</li><li>Get feedback</li><li>Revise the designs</li><li>Realize something doesn’t work</li><li>Back to Figma</li><li>Repeat</li></ul><p>But five hours? That’s barely enough time to boot up Figma and pick a color palette.</p><p>We had started this dashboard redesign the right way. First, we created a low-fidelity mockup in Excel to figure out what data and filters we needed. Then, I began building one card in v0, our new prototyping tool (or at least we’re treating it that way), just to test the filtering interaction.</p><p>Now that single card and our ugly spreadsheet were all that stood between us and an important user demo.</p><p>My first instinct was to tell my founders we’d have to show the Excel mockup. But my CTO pushed back hard: “We can’t show them a spreadsheet. They need to feel what it’s like to use this thing.”</p><p>He was right. Our dashboard’s value was all in the interactions-how filters would cascade, how data would update in real-time, how everything would flow together. A static spreadsheet would kill any chance of meaningful feedback.</p><p>That’s when it hit me: I was thinking about this all wrong. We didn’t need a perfect design — we needed something people could actually use and play with. I already had one working card in v0. Not a mockup, not a prototype, but a real, interactive component. What if we completely flipped our usual process? Instead of designing the perfect layout first, what if we just… built the rest of it on v0?</p><p>It seemed backwards, maybe even a little reckless. I hadn’t heard of someone testing it out before with users. But we were out of options.</p><p>V0 let me:</p><ol><li>Build real, working components without touching our codebase</li><li>Use actual data instead of numbers that didn’t make sense together</li><li>Create working filters and interactions immediately</li><li>Share a live, interactive prototype through a simple URL</li></ol><p>I dove in. The next four hours were a blur of:</p><ul><li>Copying the base card’s structure into new cards</li><li>Adapting it for different data we wanted to showcase</li><li>Adding filter logic (by people and date ranges)</li><li>Testing interactions</li><li>Fixing bugs on the fly</li></ul><p>No Figma. No back-and-forth between design and code. <strong>Just plain English.</strong> After 24 rapid iterations, I had something that wasn’t just a prototype-it was a working proof-of-concept that users could actually test.</p><p>The demo arrived. If we’d shown the Excel version, I can imagine how it would have gone: “So, imagine these numbers automatically update when you filter…” * <em>awkward scrolling through sheets.</em>* “And pretend you could click here to drill down…”. We’d have spent the whole time explaining what <em>could</em> be instead of learning what <em>should</em> be.</p><p>Instead, we jumped straight into real usage. The user filtered data, watched updates happen in real-time, and explored the dashboard exactly as it would work in production. No imagination required.</p><p>The feedback was immediate and precise, focused entirely on value instead of implementation:</p><ul><li>“The numbers here are OK but what would really help me is if I can see rates and values”</li><li>“What happens if I group by week instead of month?” and “Can I compare different time intervals?”</li><li>“Could I drill into what the at-risk deals are here?” *<em>clicks</em>*<em> then</em> “OOOH!”</li></ul><p>No hypotheticals. No “well, in the real version…” disclaimers. Just concrete feedback about actual functionality.</p><p>We would have never gotten this quality of feedback from static mockups. More importantly, we wouldn’t have gotten it at all if we’d stuck to the traditional design approach-we’d still be wrestling with auto-layout inside tables.</p><h3>What we learned</h3><p>This accidental experiment taught us something crucial: the traditional “design → prototype → code” workflow exists mainly because of tool limitations, not because it’s the best way to work.</p><p>Here’s what made the v0 approach different:</p><ol><li><strong>Real data drove design decisions</strong> — Instead of mocking up charts with random numbers that didn’t make sense together, we could immediately see if our metrics and calculations worked. Those “rates and values” the user asked for? We added them in seconds, not days, with real mathematical relationships intact.</li><li><strong>Interaction = truth </strong>— That “OOOH!” moment when the user drilled into at-risk deals? You can’t get that from a Figma prototype that easily.</li><li><strong>Speed through focus</strong> -Instead of stringing frames together in Figma to create interactions and then checking them in prototype mode, you can directly build and test interactions in real-time. It’s just pure user-centric problem-solving.</li><li><strong>Faster path to insights</strong> — By putting working software in front of users immediately, we got actionable feedback in hours instead of days or weeks. Each iteration taught us something concrete about user needs, without the “open-to-interpretation” layer of static designs.</li></ol><h3>When to use this approach</h3><p>This workflow shines when:</p><ol><li>Your feature is interaction-heavy (like dashboards, multi-step forms with branching logic, or data exploration interfaces)</li><li>The value is in how data connects and transforms an interface</li><li>You need feedback on the actual experience, not just the look</li><li>You’re working against time like we did</li></ol><p>Don’t use this approach if your prototype is multi-page; I don’t think v0 supports this at the moment. Also, be mindful of the fact that generations can take time and slow you down. Instead, break up the components and then bring it together at the end.</p><h3>Try it yourself (in 1 hour)</h3><p>While my story was about a 5-hour dashboard sprint, you can test this approach in just one hour. Here’s how:</p><ol><li><strong>Pick one interaction to improve</strong> (10 mins)</li></ol><ul><li>Choose something small but annoying in your current product</li><li>Maybe it’s a form that could be smarter, or a feature that needs better validation</li><li>Don’t overthink it-pick the first thing that bugs you</li></ul><p><strong>2. Build one working piece</strong> (30 mins)</p><ul><li>Skip the Figma file</li><li>Create just the core interaction in <a href="https://v0.dev/?ref=shavinpeiries.com">v0</a> (it’s free)</li><li>Proxy the data from your product to make it real (if you can)</li></ul><p><strong>3. Share &amp; learn</strong> (20 mins)</p><ul><li>Send the URL to a colleague</li><li>Watch them try to use it</li><li>Note what confuses them</li><li>Rinse and repeat</li></ul><p>The goal isn’t to finish the feature. It’s to prove (or disprove) your idea with working code faster than you could with mockups.</p><p>I’m not saying never use Figma. It’s been my trusty prototyping side-kick for years. But for data-heavy or interactive features? Try building it on v0 directly. You will be surprised how much faster you can move and how unshackled you will feel.</p><p>Notable mention: Check out <a href="https://x.com/ctatedev?ref=shavinpeiries.com">Chris Tate</a>’s v0 <a href="https://v0.ctate.dev/?ref=shavinpeiries.com">portfolio</a>. It’s amazing what this tool can do!</p><p><em>Originally published at </em><a href="https://shavinpeiries.com/the-demo-is-in-5-hours/"><em>https://shavinpeiries.com</em></a><em> on November 19, 2024.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71091cd971eb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to make your product spread to new networks (without changing what makes it great)]]></title>
            <link>https://shavinpeiries.medium.com/how-to-make-your-product-spread-to-new-networks-without-changing-what-makes-it-great-c2cb95e6e157?source=rss-e765c0b29e18------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2cb95e6e157</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-strategy]]></category>
            <dc:creator><![CDATA[Shavin Peiries]]></dc:creator>
            <pubDate>Thu, 14 Nov 2024 09:19:32 GMT</pubDate>
            <atom:updated>2025-01-28T17:38:26.319Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NfFb_Kla9cDwP4X_" /></figure><p>Ever notice something strange about project management software?</p><p>Jira dominates engineering but can’t crack marketing teams. Notion captures creative agencies but struggles with traditional PMOs. Monday thrives with agencies but falters with dev teams. Basecamp endures with small teams while enterprise goes elsewhere.</p><p>In this post, you’ll learn the hidden pattern behind successful product expansion — and how to use it to grow your market without compromising what makes your product special. Let’s dive in.</p><p>Most people think this fragmentation is about features or market segments. But that’s just what it looks like on the surface.</p><p>If it were about features, the best tools would eventually win their entire addressable market. If it were about segments, the most focused tools would own their niches completely.</p><p>But they don’t. And there’s a reason.</p><p>Let’s look at a real example from a reddit thread: A marketing agency COO wrestling with tool choice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/623/0*zFfqEqbMTc3cFIus.png" /></figure><p>Despite using Basecamp and four other tools for project management, they’re hesitant about adopting tools that <a href="https://shavinpeiries.com/bare-minimum-feature/">lean too heavily into complexity like ClickUp</a> or the “database-mess” of Notion.</p><p>Why?</p><p>Because TAM/SAM/SOM is missing the biggest market qualifier: worldview alignment.</p><p>And this is where most builders get it wrong.</p><h3>The worldview puzzle</h3><p>When you start looking for it, you see these worldview patterns everywhere. In every product category, in every market conversation, in every buying decision.</p><p>Here are three worldviews I spotted in that same thread:</p><p><strong>The process pragmatist:</strong></p><blockquote><em>“Our current processes would disgust too many folks, so I won’t share more.”</em></blockquote><p>They need tools that embrace messy reality. They know their processes aren’t perfect, but they work.</p><p><strong>The specialist skeptic:</strong></p><blockquote><em>“Linear is great for product teams — but is getting more niched w roadmaps, sprints”</em></blockquote><p>They see specialization as a double-edged sword. In their world, tools that become too focused risk becoming irrelevant.</p><p><strong>The flexibility first:</strong></p><blockquote><em>“Its a new product focused on teams working with agile with the flexibility to customize everything”</em></blockquote><p>They see customization not as a feature but as a fundamental right.</p><h3>Why this explains market fragmentation</h3><p>Most product strategies stop at market segmentation. But once you understand worldviews, you start to see why even perfect segmentation fails. Here’s what’s really happening:</p><ol><li><strong>Context clustering</strong></li></ol><p>Your real available market isn’t:</p><ul><li>Companies in your sector (TAM)</li><li>Companies who could buy (SAM)</li><li>Companies you could reach (SOM)</li></ul><p>It’s:</p><ul><li>Networks who find themselves in similar contexts</li><li>Who share similar worldviews</li><li>At the same time</li></ul><p><strong>2. Worldview lock-in</strong></p><p>Once a tool aligns with a network’s worldview, switching costs become psychological, not just technical. This is why:</p><ul><li>Jira users defend its complexity: “You need this structure for real engineering”</li><li>Notion users evangelize its flexibility: “You can build anything you imagine”</li><li>Monday users champion its adaptability: “It works the way your team works”</li></ul><p><strong>3. The growth trap</strong></p><p>Tools that try to expand beyond their worldview alignment <em>often</em> fail:</p><ul><li>Add flexibility for broader appeal → lose simplicity lovers</li><li>Add structure for enterprise → lose startup adaptors</li><li>Add features for new segments → lose original advocates</li></ul><p>But here’s where it gets interesting. Some products do break through their natural ceiling. How?</p><p>The answer lies in a fascinating piece of marketing history from the 1920s that most people have never heard of.</p><p>Edward Bernays, Freud’s nephew and the father of public relations, faced an interesting challenge.</p><p>The American Tobacco Company wanted to expand their market to women, but they faced a massive worldview barrier: smoking was considered taboo for women. The addressable market wasn’t limited by features or demographics — it was limited by societal worldview.</p><p>Bernays’ solution wasn’t to change the product or target a different network. Instead, he orchestrated a worldview shift. During the 1929 Easter Sunday Parade in New York, he arranged for a group of young women to light up cigarettes in public, calling them “torches of freedom.” He transformed cigarettes from a symbol of moral looseness into a symbol of female empowerment and liberation.</p><p>The result? The societal worldview shifted, and the addressable market exploded.</p><p>If you’re interested, <a href="https://youtu.be/QNVtGe5VAnU">watch this video</a> to learn more about Bernay’s work.</p><p><strong>Modern examples in action</strong></p><p>While Bernays worked with cigarettes, today’s category leaders are using the same psychological principles to transform how entire markets think about their work:</p><ul><li>Notion transcended “wiki tool” by becoming a symbol of “your team’s second brain” — making knowledge management feel empowering rather than administrative. That’s why you see people sharing their Notion setups like they’re sharing productivity lifehacks, not documentation systems.</li><li>Airtable grew beyond “spreadsheet tool” by becoming a symbol of “anyone can build what they need” — transforming databases from IT territory into a tool for everyone. Now marketing teams build campaign trackers and event planners build conference schedules, without ever thinking “I’m using a database.”</li><li>Figma transcended “design tool” by becoming a symbol of “creativity without barriers” — transforming from a tool just for designers into the default whiteboard for any team collaboration. Now product managers run planning sessions and engineers sketch out architectures in Figma, without ever thinking “I’m using design software.”</li></ul><h3>The shift in action</h3><p>This isn’t just theory. Once you know what to look for, you can see these worldview shifts happening in real-time:</p><p>Look at how Notion users talk about it — they don’t say “I use Notion for documentation.” They say “I run my life in Notion.” That’s not just product adoption. That’s worldview transformation.</p><h3>How companies could engineer worldview shifts</h3><p>The real question isn’t whether worldview shifts drive category leadership — it’s how to engineer them deliberately. Here’s what I’d do:</p><p><strong>Phase 1: Map your current worldview territory</strong></p><p>Start by documenting the implicit beliefs of your current power users. Not just what they do with your product, but how they think about their work:</p><ul><li>What do they consider “real work” vs “busy work”?</li><li>What do they take pride in?</li><li>What do they apologize for?</li><li>What do they brag about?</li></ul><p>For example, early Figma users weren’t just looking for design tools — they believed design should be collaborative, not siloed. That belief was key to Figma’s expansion strategy.</p><p><strong>Phase 2: Identify adjacent networks</strong></p><p>Look for networks that share core beliefs with your current users, even if they work in different contexts. The key is finding philosophical alignment, not just feature-need fit.</p><p>Notion did this brilliantly:</p><ul><li>Core network: Tech teams who believed in building their own tools</li><li>Adjacent network: Knowledge workers who wanted to design their own workspaces</li><li>Shared belief: Systems should adapt to users, not vice versa</li></ul><p><strong>Phase 3: Create bridge stories</strong></p><p>Develop narratives that help new networks see themselves in your product without alienating your core. This isn’t about changing your product’s features — it’s about changing what your product symbolizes.</p><p>Consider Airtable’s evolution:</p><ul><li>Original symbol: “Spreadsheets with superpowers”</li><li>Bridge story: “Anyone can build what they need”</li><li>New symbol: “Your ideas, your way”</li></ul><p>The product didn’t fundamentally change — the story about what it represents did.</p><p><strong>Phase 4: Let your network lead</strong></p><p>Your most powerful worldview shifters are often your existing users who already work across contexts. They naturally translate your value to new networks.</p><p>Notion’s growth playbook:</p><ol><li>Tech teams used it for docs</li><li>Those same people started using it for personal projects</li><li>They became evangelists in their non-tech contexts</li><li>New use cases emerged organically</li></ol><p>The key is identifying and supporting these natural bridge-builders who already have influence across different networks.</p><p><strong>Phase 5: Maintain worldview integrity</strong></p><p>As you expand, resist the temptation to water down your core beliefs. Instead, show how those beliefs become even more valuable in new contexts.</p><p><strong>Warning signs of worldview dilution:</strong></p><ul><li>Marketing messages that contradict each other or sound too abstract</li><li>Features that solve problems your product used to take a stance against</li><li>User testimonials that showcase conflicting values</li></ul><p>Remember: You’re not trying to be everything to everyone. You’re trying to show more networks that your worldview applies to their world too.</p><p><strong>Measuring success:</strong></p><p>Don’t just track adoption metrics. Look for signs of worldview transformation:</p><ul><li>How do new networks describe your product to others?</li><li>What adjacent problems do they start using it for?</li><li>How do they defend it to skeptics?</li></ul><h3>The niche exception</h3><p>Not every successful product needs to engineer worldview shifts. Some companies deliberately choose to deeply align with a specific worldview that’s naturally expanding.</p><p>Linear and Basecamp exemplify this approach. While they compete in the project management space, they’ve chosen to deeply embed themselves in growing but distinct worldviews:</p><ul><li>Linear embraces the “engineering excellence” worldview: Where speed, keyboard shortcuts, and opinionated workflows aren’t just features — they’re symbols of craftsmanship. As more teams adopt engineering-led cultures, Linear grows without needing to shift worldviews.</li><li>Basecamp champions the “less is more” worldview: Where simplicity and focus aren’t compromises — they’re competitive advantages. As more teams face tool fatigue and complexity overload, Basecamp’s market expands naturally.</li></ul><p>These companies prove that if your chosen worldview is growing fast enough, you might not need to engineer shifts. The key is ensuring your worldview alignment is deep enough to retain users as they grow, even if you never expand beyond that core belief system.</p><p>But while these niche players can build sustainable businesses by riding growing worldviews, the playbook for category leadership looks different. Category leaders don’t just align with existing worldviews — they actively expand and transform them.</p><h3>Your spread strategy checklist</h3><p>To make your product spread to new networks:</p><ol><li>Map your current network’s worldview (use the questions in Phase 1)</li><li>Identify bridge-builders who already cross between networks</li><li>Document how early adopters in new networks describe your product</li><li>Craft stories that connect your core worldview to new contexts</li><li>Support and amplify users who are already spreading your product naturally</li></ol><p>Start with step 1 today: Interview three power users about how they think about their work (not just how they use your product).</p><h3>The path forward</h3><p>While most builders are still <a href="https://shavinpeiries.com/bare-minimum-feature/">obsessing over feature parity and market fit</a>, category leaders are quietly rewriting the rules of competition. They know something we don’t.</p><p>The next wave of category-defining products won’t win by having better features or broader market reach. They’ll win by understanding that growth isn’t about expanding your addressable market — it’s about expanding what your core worldview means to different networks.</p><p>Think about it:</p><ul><li>Jira didn’t need to become less complex to win engineering teams</li><li>Notion didn’t need to become more structured to win creative teams</li><li>Figma didn’t need to become less design-focused to win collaboration</li></ul><p>Instead, they showed different networks how their worldview solved problems in ways those networks hadn’t imagined.</p><p>Your product’s growth ceiling isn’t set by your features, your market size, or even your execution. It’s set by how successfully you can transform your worldview from a tool perspective (“this is project management software”) into a movement perspective (“this is how modern teams should work”).</p><p>Because in the end, there are no total addressable markets. Only expandable worldviews. And the products that win aren’t just the ones with the best solutions — they’re the ones that change how networks think about the problem itself.</p><p><em>Much of the thinking in this piece was inspired by </em><a href="https://www.linkedin.com/in/diegodjm/overlay/about-this-profile/"><em>Diego de Jódar</em></a><em>’s excellent work at </em><a href="http://pleasedontpush.com/"><em>pleasedontpush.com</em></a><em>. His insights on startup growth strategy have been instrumental in shaping these ideas.</em></p><p><em>Originally published at </em><a href="https://shavinpeiries.com/how-to-make-your-product-spread-to-new-networks-without-changing-what-makes-it-great/"><em>https://shavinpeiries.com</em></a><em> on November 14, 2024.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2cb95e6e157" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Design Your Own Component Library Without Spending $$$ on Courses]]></title>
            <link>https://medium.com/design-bootcamp/how-to-design-your-own-component-library-without-spending-on-courses-18b135d0ae57?source=rss-e765c0b29e18------2</link>
            <guid isPermaLink="false">https://medium.com/p/18b135d0ae57</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[component-libraries]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Shavin Peiries]]></dc:creator>
            <pubDate>Mon, 28 Nov 2022 08:40:20 GMT</pubDate>
            <atom:updated>2022-12-05T05:55:29.661Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AOMmEf1Jp8ggc38MPwaHiQ.jpeg" /></figure><p>Four months ago, I began a new job as a product manager at a pre-seed-stage startup. I was tasked with designing a B2B SaaS dashboard with multiple components to enable education-based service businesses to list and manage their classes.</p><p>After having had five discovery calls, I was aware of the issues that our potential users were experiencing, and we mapped out seven scopes for the initial MVP using low-fidelity wireframes.</p><p>It was then time to convert them into high-fidelity designs, but there was a problem.</p><p>I hadn’t built an entire library of components before.</p><p>I was aware that if we didn’t get it right from the start—with a growing design team to manage, a two-week deadline, and the knowledge that this would be a long-term project — we’d wind up with a Frankenstein product.</p><p>By the end of this article, you’ll understand how I solved it without needing to invest a lot of time or money in pricey Figma design courses.</p><p><strong>When I first faced this challenge, the options I had to overcome it wasn’t great:</strong></p><ul><li>At most, I’d have to watch 3–5 YouTube videos. It would have taken too much time to return to it, relocate the valuable parts, and inspect it by zooming into the Figma panels in the video.</li><li>I didn’t want to find a mentor either because I felt uncomfortable constantly interrupting someone with my questions. Some questions are too nuanced, like knowing “when to utilize variants and properties,” which only comes up when you’re in the process of designing the components, not before.</li><li>A three-month, high-priced Figma UI design course was not something I could entertain or devote the time to because I needed to hit the ground running quickly.</li></ul><p>Without a reliable source to depend on, I was running out of time before the sprint had to start. That’s when I began researching design kits.</p><p>In the past, I’ve learned that handwriting top-selling advertisements are one of the best methods for learning how to write compelling copy. “Copy work” is a term that refers to this type of learning. By rewriting the text from the advertisement, our brain starts to establish a pattern for what appeals to people. Learning component design can be done using a similar approach.</p><p>When I remembered this, I went to Google and typed in “best UI kits for Figma,” which brought me a <a href="https://www.untitledui.com/blog/figma-ui-kits">lengthy post</a> from Untitled UI comparing them to other design kits and claiming why they were superior and what the competition lacked. It turns out that they are actually superior.</p><p>They position themselves as a way to <strong><em>“kickstart any project, save thousands of hours, and level up as a designer.”</em></strong></p><p>Even though thousands of hours could be an exaggeration, it turned out to be a good starting point for this project and, more importantly, a way for me to grow my component design skills and understand where I was lacking.</p><h3>Getting started with Untitled UI is easy</h3><p>They&#39;ve got free and paid versions of the kit, and it’s well-documented with no filler language. I really liked that the documentation was concise and complete.</p><p>To start using the <a href="https://www.untitledui.com/free-figma-ui-kit">free version</a>, you simply have to copy a draft of their file from Figma into your own account.</p><p>Once you’ve done that, you’ll see the pages on the left-side panel neatly organized into separate sections. It goes from UI foundations to application components like card headers, models, charts, and much more.</p><p><strong>So how does this help you become better at designing a component library?</strong></p><h3>Instead of watching someone else do it, inspect the components in Figma to learn how to create them.</h3><p>A side panel navigation was one of the common design patterns in our low-fidelity wireframes. Since it was used repeatedly across the product, I decided it would be better if we made it a component.</p><p>I began by going to Untitled UI, where I got a close reference to the component and copied it into our project. Then, before creating one from scratch, I quickly scanned the component’s layers to understand how they were structured.</p><p>I noticed differences between what I was doing and how they were implementing it. They should have been identical, but they weren’t. For instance, if I added content to a navigation link, the text would overflow. I scrolled to their component since I was aware that I was still lacking something and made an effort to identify what it was. They had set their layer’s resizing for width to fill container whereas mine was set to hug contents, which resulted in the overflow. When the content inside the component changes, the parent component has to accommodate it, otherwise it won’t be usable. That’s how I learned how to properly use layer resizing.</p><p>Instead of doing this, you could have watched someone else do it on YouTube. What’s frustrating about watching YouTube is that they may not be teaching using the exact component you want. They might also fail to clarify layer resizing’s importance in the context of what you might be designing. Your performance and productivity will significantly improve after you learn how to use them properly. I couldn’t understand it before (even with Figma’s official documentation, because it was too abstract). I do understand now, thanks to Untited UI.</p><h3>Reference the design kit for answers if any questions come up when designing a component.</h3><p>Creating variants and properties for components was one of the key difficulties I encountered when designing our component library.</p><p>During the design process, questions like “Should I just make it a property so it’s flexible?” or “Does this need to be a variant?” and similar ones arose. Answering them was easy as opening up my copy of Untitled UI.</p><p>It’s simple to incorporate a component into a design that wouldn’t work in all situations. The result is a design system that is bloated and complex due to poor adoption by other designers. What happens thereafter is that they’d build components that are too concrete in order to fulfil their job but it’s a painful workaround.</p><p>In one particular case, we were creating a button with dynamic content. It had to vary in size and behave differently depending on the context of what had to be done on the screen.</p><p>Untitled UI’s button component implementation has exactly what we required when I checked it out. I had confidence that it would meet our needs in the majority of situations after seeing how it was set up.</p><p>If you’re designing a component library, you’ll probably have a lot of complex questions, just like I did. I didn’t need to consult anyone. The creator — <a href="https://jordanhughes.co/">Jordan Hughes</a> — has baked all the solutions inside the Figma file and you can just refer to it. In a certain sense, it is like them advising you but through the design kit.</p><h3>Save time, use a design kit.</h3><p>Given the time constraints, it was easy to complete the high-fidelity conversion since we used the kit to create our component library; without it, the effort would have been too significant and likely resulted in a messy situation that we’d have to pay for later on.</p><p>It’s as close as you can get to having a book or an experienced UI designer so that you can ask questions while you’re learning and building. Which is far preferable to spending weeks or months on a pricey design course.</p><h3>Next actions for you</h3><ul><li>Go ahead and grab your copy of <a href="https://www.untitledui.com/">Untitled UI</a></li><li>Use the <a href="https://www.figma.com/community/plugin/820660579767995949">Styler</a> plugin to extract the styles from their file and then paste them into your own project. Then use the Apply Styles function in Styler to automatically create the required styles.</li><li>Once you have their styles set up in your project, inspect the input field component layer by layer to view how it’s structured. Ask yourself, where have they used auto-layout? How have they managed icons inside input fields? How does that affect the text input area? How did they manage layer resizing when the input and the icon need to work together?</li><li>(The reason for choosing the input field component is because it’s diverse in its nature to include most of what you need to know when you’re building out the rest of your component library.)</li><li>Once you’re done inspecting it, try creating it from scratch by yourself and then try applying the child component to a screen where it will be utilised and observe if it works as intended.</li><li>Repeat this process for all the other components in your library!</li></ul><p>There’s no one size fits way to learn how to build your component library. However, if you’re like me and you enjoy learning by doing then using pre-existing design kits is the way to go.</p><p>If you liked this article, you’ll probably like: <a href="https://shavinpeiries.com/how-do-you-break-into-a-ui-ux-design-role-even-during-a-layoff-period/">“How do you break into a UI/UX design role even during a layoff period?”</a></p><p>This article was originally published on <a href="https://shavinpeiries.com/">shavinpeiries.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18b135d0ae57" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/how-to-design-your-own-component-library-without-spending-on-courses-18b135d0ae57">How to Design Your Own Component Library Without Spending $$$ on Courses</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Afraid of negative feedback for your design work? Try this instead]]></title>
            <link>https://medium.com/design-bootcamp/afraid-of-negative-feedback-for-your-design-work-try-this-instead-4382a24035ca?source=rss-e765c0b29e18------2</link>
            <guid isPermaLink="false">https://medium.com/p/4382a24035ca</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[figmadesign]]></category>
            <category><![CDATA[design-feedback]]></category>
            <dc:creator><![CDATA[Shavin Peiries]]></dc:creator>
            <pubDate>Mon, 28 Nov 2022 08:26:12 GMT</pubDate>
            <atom:updated>2022-12-05T05:55:26.031Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J9mBP48_PGDSWntcggsSHA.jpeg" /></figure><p>You open up your Figma file to view the red blip on the comments icon.</p><p>You click on it to scan through the right-side panel, where your design manager has left a long list of criticisms.</p><p>It starts to resemble a drive-by shooting more than a design review. After all of your hard work, the comments feel like bullets piercing you.</p><p>As you go through each comment, your confidence gradually starts to drain. You think, <em>“My co-workers are going to be looking at this!&quot; &quot;Why can’t this be done on a 1-on-1 basis?”</em></p><p>When we share our hard work, we naturally put our asses on the line, and reading through negative comments is going to sting.</p><p>But it doesn’t have to.</p><p>As designers, we go through a phase of maturity where we realize that when we work in UI or UX, we’re designing <em>how things should work and look</em>. Everyone, from customers, to design managers, will have an opinion about it.</p><p>However, the only way to make something great is to recognize that it might not be great yet.</p><p>Your goal is to <a href="https://shavinpeiries.com/bare-minimum-feature/">find the best solution</a>, not to attach your personal identity or self-worth to the work that you share.</p><p>Furthermore, receiving negative feedback doesn’t make you a bad designer. Most people are reluctant to share their actual thoughts.</p><p>If a customer knows you worked on the designs, for example, they might take the path of least resistance and try to spare your feelings when you test them with them. So it’s great if you get negative feedback! It means that you got closer to your goal. That’s a win in itself.</p><p>And if you’re still afraid, here’s one thing you can do to mitigate getting yourself into a drive-by design feedback situation.</p><h3>Expose your process and get feedback early</h3><p>When we don’t have a lot of confidence in our process, we tend to take our designs away, work in private, and then go back to showing them to managers when we think we have something solid to show. We do it in secrecy.</p><p>Later on, when we get more confident about our process, we open it up more to feedback because we know that things will never be perfect. Getting feedback becomes exciting, and you know that it will steer you toward a better design without making you feel like you’ve put your ass on the line.</p><p>And if you’re worried about asking people for feedback because they might be busy and you’re requesting their time and attention, try this:</p><p>Make a short, 3–5 minute <a href="https://loom.com/">loom</a> video of your design in progress.</p><p>Make sure to include these details in the video:</p><ol><li>Explain the motivation behind the design by contextualising the problem and what you’re trying to accomplish.</li><li>Explain how your design addresses those problems.</li><li>Mention any weak spots or details that you’re not sure about.</li><li>Invite your manager and other stakeholders to comment on it. Seek out a variety of perspectives.</li></ol><p>When you do this from the beginning, you take a lot of pressure off the review process for you and your manager. The feedback comes in smaller baby waves rather than a large tidal wave that washed out your creative energy.</p><p>It starts to feel much less like a review by the end of it since there are smaller increments of progress.</p><p>As mentioned, it doesn’t make you a bad designer to receive a lot of feedback (even if it’s negative). However, it does make you a bad designer when you don’t incorporate it into your process.</p><p>So, when it’s time to share and evaluate what you’ve done, try to put your emotions aside when sharing for feedback. You&#39;ll be able to argue ideas logically rather than emotionally if you can do this.</p><p>If you liked reading this article you might also like, <a href="https://shavinpeiries.com/how-to-design-your-own-component-library/"><em>How to Design Your Own Component Library Without Spending $$$ on Courses</em></a> and <a href="https://shavinpeiries.com/how-do-you-break-into-a-ui-ux-design-role-even-during-a-layoff-period/"><em>How do you break into a UI/UX design role even during a layoff period?</em></a></p><p>This article is from shavinpeiries.com</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4382a24035ca" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/afraid-of-negative-feedback-for-your-design-work-try-this-instead-4382a24035ca">Afraid of negative feedback for your design work? Try this instead</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How do you build a bare minimum feature?]]></title>
            <link>https://uxdesign.cc/how-do-you-build-a-bare-minimum-feature-1c2fbab86808?source=rss-e765c0b29e18------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c2fbab86808</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[jtbd]]></category>
            <dc:creator><![CDATA[Shavin Peiries]]></dc:creator>
            <pubDate>Fri, 07 Jan 2022 06:26:34 GMT</pubDate>
            <atom:updated>2022-01-17T11:37:18.395Z</atom:updated>
            <content:encoded><![CDATA[<h4>Understanding how to shape up a bare minimum solution starts with asking the right questions.</h4><figure><img alt="FlintMobile from the Flintstones — This is to communicate how you can build a bare minimum of something to get the job done. In the flintstones, the FlintMobile doesn’t have wheels, it’s just Fred Flintstone pushing it with his feet." src="https://cdn-images-1.medium.com/max/1024/0*UYhaeQSGTX2fRUnH.jpg" /><figcaption>FlintMobile from the Flintstones</figcaption></figure><p>Have you ever felt it was difficult to ship on time?</p><p>Isn’t it true that understanding what works is nearly impossible without having to build and ship different solutions to understand which one works?</p><p>Is there any better advice than to “ship it before you’re ready” in order to learn more quickly from the people you serve?</p><p>Feature development is a virtuous cycle of going from a problem to an idea to then build, launch and learn. But this is a very expensive form of development because the chances of being wrong are very high; the time, effort, and resources spent developing a big feature to get to the insight are wasted if it doesn’t resonate with your customers after months of development.</p><p>But failure is a data point to evaluate and ask <strong>“is there a better way to make progress towards mitigating the risk of building the wrong thing so that you can gain enough confidence that it will be adopted by customers?” </strong>The answer lies at the beginning of the product development process. At the heart of the customer problem.</p><p>So far your instinct as a product designer, manager or engineer might be to take what customers say they want at face value. Then you build it and launch it, only to find that it doesn’t quite work, and you’re back to square one. It then becomes critical to ask the right questions during customer discovery calls in order to determine how to reduce the risk of building the wrong thing.</p><p>The goal in a discovery call is to:</p><ol><li>Understand what their overall journey was to ask for the feature</li><li>How did they discover that it was important to them?</li><li>What event prompted them to reach out and ask for the feature?</li><li>How satisfied are they with the current way they’re doing things to make progress?</li></ol><p>What you’re searching for is a pain in the form of unmet needs where they aren’t sufficiently satisfied with their current process. It’s important to note that if they aren’t doing anything right now to make progress toward completing their task (whether through an external product or a manual process), it’s possible that it isn’t a real problem worth addressing.</p><p>What questions do you specifically ask then?</p><h3>First, understand the context behind where they started to struggle</h3><p>Ask questions such as:</p><ul><li>Can you tell me a little about how you got to needing this feature in the first place?</li><li>Can you tell me about when you started thinking that maybe this feature (their idea) could be used to solve the problem? Why are you doing this now?</li><li>What’s not happening that you want to happen?</li><li>Where’s the frustration?</li></ul><h3>Second, understand what they’re doing right now to progress</h3><p>Ask questions such as:</p><ul><li>What other tools or things have you done manually to try to do this?</li><li>How satisfied are you with this process/tool?</li><li>Where’s your frustration?</li><li>What don’t you like about the current way of approaching this problem?</li></ul><p>If possible try to observe how they go through it right now by asking them to show you.</p><h3>Third, understand where they want to be (the ideal outcome)</h3><p>Ask questions such as:</p><ul><li>Can you walk me through a little bit on what the end result you’re trying to get to is?</li><li>What are you hoping for?</li><li>What’s going to be different once you’ve got [the new feature] in your life?</li></ul><p>Knowing the answers to these questions will help you form a bounded bare minimum solution as well as tell you what not to build. You will have a clear understanding of where the customer is in relation to time: the point at which they begin to struggle and what they want to achieve.</p><p>Check out these references on how other companies came about this problem:</p><ul><li><a href="https://www.intercom.com/blog/shareable-map/">Building a worse map at Intercom</a></li><li><a href="https://youtu.be/C4WOfEyogo8?t=1440">Ben Orenstein on his experience building dual mouse cursors at Tuple.</a></li></ul><h3>References</h3><ul><li>A special thanks to<a href="https://twitter.com/mjwhansen"> Michele Hansen</a> for writing Deploy Empathy, some of the questions to be asked came from her <a href="https://www.getrevue.co/profile/mjwhansen/issues/customer-interview-script-template-relatively-new-customer-aka-jtbd-switch-interview-415338?utm_campaign=Deploy%20Empathy&amp;utm_medium=email&amp;utm_source=Revue%20newsletter">Switch Script</a>.</li><li>Some questions came from Bob Moesta’s Book Demand Side Sales under “Progress Tools”. You can also <a href="https://shavinpeiries.com/notes-on-demand-side-sales/">read my notes</a> or <a href="https://www.amazon.com/Demand-Side-Sales-101-Customers-Progress-ebook/dp/B08FRRF68Q">get the book</a> if you’d like.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c2fbab86808" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-do-you-build-a-bare-minimum-feature-1c2fbab86808">How do you build a bare minimum feature?</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to overcome creative challenges and explore breakthrough ideas]]></title>
            <link>https://shavinpeiries.medium.com/how-to-overcome-creative-challenges-and-explore-breakthrough-ideas-22228c656491?source=rss-e765c0b29e18------2</link>
            <guid isPermaLink="false">https://medium.com/p/22228c656491</guid>
            <category><![CDATA[ideas]]></category>
            <category><![CDATA[brainstorming]]></category>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[workshop]]></category>
            <dc:creator><![CDATA[Shavin Peiries]]></dc:creator>
            <pubDate>Tue, 29 Jun 2021 11:52:42 GMT</pubDate>
            <atom:updated>2021-06-29T11:52:42.119Z</atom:updated>
            <content:encoded><![CDATA[<p>If you have come across a daunting challenge and feel stuck on how to go about it, fret not.</p><p>All you need is a couple of design thinking exercises to blast through those creative blocks and into the realm of creative confidence.</p><p>The below steps is what I use to come up with ideas whenever there’s a big challenge or if the concept is unclear.</p><p>You can do this exercise individually or with a team.</p><h3>Step 1</h3><p>Define the challenge/problem you’re trying to solve using a How Might We (HMW) note.</p><p>HMW notes is a design thinking tool that’s great for looking at problems through an opportunistic lens rather than a problematic one.</p><h3>Example</h3><p>At <a href="https://verybadwizards.io/">Very Bad Wizards</a>, we often try to experiment and help businesses validate ideas before you do some severe execution. For example, my business partner’s roommate — Alec Herrera (@senior_smokie) — was trying to figure out if there was a market for healthy kombucha drinks in Sri Lanka.</p><p>We thought it was perfect for experimenting to figure this out.</p><p>Here are the two most important challenges we faced framed as “how might we” notes:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/704/0*C4pvG8OEdIXyKqu-.png" /></figure><h3>Step 2</h3><p>Now that you’ve gotten your challenges down, it’s time to look for inspiration. It’s important to know that you don’t need to rely on creativity to develop a brilliant idea. All you’ve got to do is fill your mind with similar solutions to the problem you’re trying to solve.</p><h3>Example</h3><p>For our challenges, these are the example solutions that we found:</p><h3>Overall concept</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/704/0*CxA5th5qcMn_M-J4.png" /></figure><h3>Poster designs</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/704/0*cFHY1uLx4H7TFtg1.png" /></figure><h3>Step 3</h3><p>Time to come up with your solution! This is where you remix and improve the ideas that you found in the previous step.</p><p>When you’re attempting this, it’s better to try it on paper before moving to a digital tool. This is because pen and paper encourage you to make mistakes and iterate quickly.</p><p>What you need in this step is enough detail that explains the idea clearly.</p><h3>Example</h3><h3>Initial concepts</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/704/0*VcY7I_3L49womekx.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/704/0*ao8jbC9e2U0ukTs_.png" /></figure><h3>From paper sketches to high fidelity designs</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/704/0*s-q6IahDOIvwNniC.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/704/0*aENIayT6kybwIot6.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/704/0*uxXMENMu7Xc0plXD.png" /></figure><h3>Everything you need to know:</h3><ol><li>Define your challenge or problem by writing it down as a “how might we” note.</li><li>Look for inspiration. By looking at your HMW statement, collect ideas of how other people might have solved the problem.</li><li>Remix and improve. With enough information on the problem and inspiration to solve it, your subconscious is primed to develop a killer idea. Sketch it out on paper first and then execute!</li></ol><p>Oh, and If you’re wondering how our example went during execution… it was a success!</p><p>Seventy-three cups in total in the “YES” bin and 2 in the “No”. Some people even paid for a coffee-infused kombucha which is the ultimate form of validation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/704/0*HofTQ-6YyQmUmCqO.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*pnmsD9YRL6gE6UHf.gif" /></figure><p>I talk about creative ideas like this on my <a href="https://twitter.com/shavin47">Twitter</a> come say hi!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22228c656491" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Notes on Demand Side Sales by Bob Moesta]]></title>
            <link>https://shavinpeiries.medium.com/notes-on-demand-side-sales-by-bob-moesta-202632fba421?source=rss-e765c0b29e18------2</link>
            <guid isPermaLink="false">https://medium.com/p/202632fba421</guid>
            <category><![CDATA[sales]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[jobs-to-be-done]]></category>
            <category><![CDATA[productdevelopmnet]]></category>
            <dc:creator><![CDATA[Shavin Peiries]]></dc:creator>
            <pubDate>Tue, 29 Jun 2021 11:46:48 GMT</pubDate>
            <atom:updated>2021-06-29T11:46:48.263Z</atom:updated>
            <content:encoded><![CDATA[<p>“People convince themselves. We convince them of nothing.”</p><p>Jobs to Be Done (JTBD) is a theory of how people buy. Demand-side sales is a method popularized by Bob Moesta for building a sales program around JTBD.</p><p><em>Understanding consumers at a deep and empathetic level add value to the sales approach rather than on your product and its features and benefits.</em></p><p>These are some core ideas from the Demand Sides Sales Book that will help you start selling from the demand perspective and help your customers make progress.</p><p>If you like these ideas, please consider <a href="https://www.amazon.com/Demand-Side-Sales-101-Customers-Progress-ebook/dp/B08FRRF68Q">purchasing the book</a>!</p><h3>Core Ideas</h3><h3>Demand is about a fundamental struggle</h3><p>Supply and demand are two different perspectives in sales.</p><p>When you’re getting a restful eight hours of sleep every night, you overlook the mattress store when you walk past it. But if you find yourself choosing the recliner every night over tossing and turning in your bed, then you begin to look at and see other options.</p><p><strong>When something’s not working, the struggling moment occurs.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RJEakXwBs_iuIOva.jpg" /></figure><h3>Eliminating the struggle is not progress.</h3><p>Customers <strong>overcoming</strong> the struggle is progress. This means not to remove the problem but to overcome it.</p><p>The key to understanding causation is found in the <strong>circumstance</strong> and determined by where you start compared to where you end.</p><p>Their circumstances are a reference point for their progress. Without understanding their starting place, you cannot design their progress.</p><h3>There are three types of motivation for people to make progress.</h3><p>Think of it as the energy that makes the buying process happen.</p><p><strong>Functional Motivation</strong></p><ul><li>How cumbersome is the purchasing process for the buyer — time, effort and speed-wise?</li><li>There’s a functional barrier that stands in the way of making a purchasing decision. We need to reduce this functional barrier because it’s pushing people away from our services.</li></ul><p><strong>Emotional Motivation</strong></p><ul><li>What are the positive and negative emotions that are driving the customers&#39; purchase?</li><li>Fears, frustrations and desires?</li></ul><p><strong>Social Motivation</strong></p><ul><li>How do other people perceive, respect, trust or acknowledge the customer?</li><li>How proud would their family and friends be? And, as a result, how proud would they feel about themselves.</li></ul><h3>The four forces of progress</h3><p>The forces determine whether people can move from A to B and make progress.</p><p><strong>(F1) The push of the situation</strong></p><ul><li>The struggling moment for a person to buy a mattress is the requirement for a good nights sleep. Tossing and turning are affecting their productivity throughout the day.</li></ul><p><strong>(F2) The magnetism of the new solution</strong></p><ul><li>The moment you realise that <em>something</em> might bring you a better night’s sleep and help you make progress. The solution creates magnetism, and you start to imagine a better life with a good night’s sleep.</li><li>For example, a friend talks about a new mattress they bought and raves about it. This is a pull towards a new solution.</li></ul><p><strong>(F3) The anxiety of the new solution</strong></p><ul><li>Despite the problem and the pull of the new solution, there’s anxiety.</li><li>Leaping one solution to another will raise anxieties about whether the new solution will bring about positive change (will the new mattress deliver on its promise?)</li></ul><p><strong>(F4) The habit of the present</strong></p><ul><li>You are used to the old mattress even though it sucks. You’ve learned to live with it. Energy in that incumbent solution keeps you from making progress and stops you from switching.</li></ul><p>By seeing the world in this new light, “buying” becomes a system.</p><ul><li>(F1 + F2) &gt; (F3 + F4)</li><li>The forces work as a system, and sometimes, adding more features is not better because it causes additional anxiety.</li></ul><p><strong>Note: money is made on the anxiety side of the equation.</strong></p><p>Reducing anxieties around the solution gets them to what you’re selling faster. If you can figure out what’s holding people back, you can shortcut the sales process and increase profits.</p><h3>The purchasing timeline</h3><p>Whether you’re buying a pen or a cup of coffee, buyers have to go through certain stages to make the purchase happen. Over the years, Bob’s team has uncovered six steps.</p><p>When you understand where people are in the timeline, it can help position the product or service with the ideal market. Also, knowing your customer’s stage in the timeline helps them move forward at their pace.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_Kh9FyrHZoCV9FrC.jpg" /></figure><p><strong>1. First thought</strong></p><blockquote>“I have a problem”</blockquote><p>This is about helping customers create space in their brain about a problem they’re having and admitting to it.</p><p>By having a deep understanding of the customers struggling moments and where they have them, you can create a space for a problem, for which a solution may fall into place.</p><p><strong>Creating the first thought means that customers see things in a new way.</strong></p><p>There are four ways to create the first thought:</p><ul><li>Ask a good question and not give an answer</li><li>Tell a story</li><li>Give a new metric</li><li>State the obvious</li></ul><p><strong>2. Passive looking</strong></p><blockquote>“Maybe I can do something”</blockquote><p>The active looking phase is about learning about the problem.</p><p>There’s a little transition going from the first thought to look passively.</p><p>At this stage, it’s about making your products/services repeatedly visible to the customer, especially in places where they <em>feel</em> the struggle. This is where marketing and advertising become useful.</p><p>When they’re exploring possible solutions to their problem, you <strong>help them connect the dots between the question in their brain (first thought) and your solution.</strong></p><p>By showing up at the right spot, you grow their social and emotional energy around the problem.</p><p><strong>3. Active Looking</strong></p><blockquote>“I need to do something!”</blockquote><p>Active looking is like exploring the solution.</p><p>Going from passive looking to active looking is almost instantaneous.</p><p>Once we’ve made space for the problem, they start narrowing down on solutions.</p><p>Then they go into having a time wall to decide on one solution to “hire”.</p><p>This is where people plan or spend time and even money figuring out what’s next, the solution to their struggling moment. These options help people create an ideal solution in their minds.</p><p>The buyer must have contrast; without contrast, it becomes impossible to decide.</p><p>In the active looking phase, buyers need a time wall like an artificial deadline or a time box to move to the next step of the timeline.</p><p>If there’s no time wall, people might take forever to make a choice. The moment a time wall is present, they make a choice.</p><p>It’s important not to overdo it, however, because you might lose urgency.</p><p><strong>4. Deciding</strong></p><blockquote>“What’s important and what’s not? What do I care about?”</blockquote><p>Deciding involves making the trade-offs and establishing value.</p><p>People need something to reject before they can buy something else. Creating reference points is a form of elimination.</p><p><strong>In sales, the definition of making a tradeoff is about choosing the best way to make progress instead of compromising.</strong></p><p>E.g., people want thick crust pizza or thin crust pizza. If you averaged those results, you’d get medium-thick-crust pizza. Nobody wants that.</p><p>The expectations for satisfaction are cemented while they decide, and value is defined.</p><p>The customer’s understanding of quality, performance, and satisfaction starts here, and everything in the future is measured based on the final expectation locked while deciding.</p><p>In the deciding phase, buyers factor in bigger discounts.</p><p>The discount is more emotional and social than financial motivation. Customers want to feel good about themselves about getting a discount.</p><p><strong>5. Onboarding</strong></p><blockquote>“Were my expectations met?”</blockquote><p>Onboarding is where the consumer is having the first use of the product or service and measuring it against their expectations when deciding to hire the solution.</p><p>It’s about being able to onboard them while delivering in a way that matches the expectations they set.</p><p>You want the customer to not only feel satisfied but excited and delighted about something they didn’t know they’d want or get.</p><p>Most people stop selling once the purchase is made. But progress is about <strong>making sure</strong> that you deliver on the expectations set.</p><p>Dissatisfying a customer comes because of a lack of communication, and it’s worth hearing about to improve future versions of the product.</p><p><strong>6. Ongoing Use</strong></p><blockquote>“Am I building a habit with this product?”</blockquote><p>There’s a difference between buying (onboarding) a product or service and using it every day.</p><p>If you did not set expectations well, the consumer would have a new struggling moment, which over time can lead to another big hire from a different solution.</p><p>So, this phase is about turning the first use experience from onboarding to ongoing use or building the habit of using the product.</p><p>Moreover, ongoing use concerns understanding the different struggling moments (which might cause people to fire you) and making the product/service better.</p><p>You, as a salesperson, have to meet the buyer in each of the six stages.</p><p>Your goal is to create an input at each of the six stages that trigger the desired output, leading to an ideal outcome for the customer.</p><h3>A lot of the time, sales feels icky.</h3><p>It’s icky because you might not believe that the product will help the customer make progress.</p><p>I like JTBD theory and Demand Side Selling because it takes an honest and empathetic approach to help customers get to where they need to be. If you’re failing to do so, it’ll help you understand why.</p><p>There isn’t a page that isn’t underlined or a margin that’s left without ink in my copy of demand-side selling. I highly recommend you <a href="https://www.amazon.com/Demand-Side-Sales-101-Customers-Progress-ebook/dp/B08FRRF68Q">add it to your library</a> if you’re a creator!</p><p>If you’re interested in JTBD, I talk about it on my <a href="https://twitter.com/shavin47">Twitter</a>, my DMs are open so say hi!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=202632fba421" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[To the people waiting to start something]]></title>
            <link>https://shavinpeiries.medium.com/to-the-people-waiting-to-start-something-3dee870ee36?source=rss-e765c0b29e18------2</link>
            <guid isPermaLink="false">https://medium.com/p/3dee870ee36</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[starting-a-business]]></category>
            <category><![CDATA[personal-development]]></category>
            <dc:creator><![CDATA[Shavin Peiries]]></dc:creator>
            <pubDate>Tue, 29 Jun 2021 11:34:54 GMT</pubDate>
            <atom:updated>2021-06-29T11:38:14.635Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CKeTF0tXmNoRvnyA" /><figcaption>Photo by <a href="https://unsplash.com/@punttim?utm_source=medium&amp;utm_medium=referral">Tim Gouw</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I remember wanting someone to create <a href="https://ideabakery.app/">Idea Bakery</a> for me by sharing it in a <a href="https://shavin.bearblog.dev/should-i-build-this-in-public/">public pitch</a>.</p><p>I come from a front-end development background, and the backend was always scary for me to touch.</p><ul><li>Should I use Ruby on Rails or go with Javascript?</li><li>How do entity relationships work?</li><li>What if I had to change the database after posting it to production?</li></ul><p>These are a few of hundreds of questions that kept me up at night.</p><p>It wasn’t until we started <a href="https://shavin.bearblog.dev/ending-very-bad-wizards/">shifting from a service business to a product business</a> when I had to get serious about understanding backend development.</p><p>I didn’t think I’d enjoy it, but then I tried it out.</p><p>The insight?</p><p>It turns out the way you solve issues on the frontend is the same way you do it on the backend.</p><p>Which is to Google your problem and focus on solving one problem at a time.</p><p>The good thing about coding is that you can only put out one fire at any given moment. So this focuses you on doing what’s right in front of you and taking small steps that will eventually get you where you need to be.</p><p>And it’s not just applicable to coding: Starting a business, writing your first non-fiction book or losing 50 lbs begins with being honest about what you want—and then building up momentum by taking a few steps at a time.</p><p>The starting part matters, though. Eventually, you’ll be able to answer your questions. Then, you’ll defeat uncertainty with action and make better choices towards your progress.</p><p>So, if you’re waiting for a signal to start, here it is!</p><p>I’m building a tool to help independent creators write without getting stuck on Twitter.</p><p>Follow me on <a href="https://twitter.com/shavin47">Twitter</a> to read the story!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3dee870ee36" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Design an Engaging Meetup? : Product Hunt Global Meetup]]></title>
            <link>https://shavinpeiries.medium.com/how-to-design-an-engaging-meetup-product-hunt-global-meetup-66ebacd69629?source=rss-e765c0b29e18------2</link>
            <guid isPermaLink="false">https://medium.com/p/66ebacd69629</guid>
            <category><![CDATA[product-hunt]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[creators]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[community-meetups]]></category>
            <dc:creator><![CDATA[Shavin Peiries]]></dc:creator>
            <pubDate>Sun, 16 Feb 2020 21:41:56 GMT</pubDate>
            <atom:updated>2020-02-24T13:47:21.081Z</atom:updated>
            <content:encoded><![CDATA[<h3>How You Should Design an Engaging Meetup: Product Hunt Global Meetup</h3><p>When the Product Hunt team put a tweet out calling for hosts in cities to host their Global Meetup we jumped at the opportunity.</p><h3>Ryan Hoover on Twitter</h3><p>We&#39;re trying something new in 2020. If you&#39;d like to host a Product Hunt meetup in your city, sign up. 🌎🌍🌏 https://t.co/mlyTZ1osRc</p><p>Having conducted multiple workshops for the design community in Sri Lanka with the <a href="http://instagram.com/vbwizards">Very Bad Wizards</a> (a product &amp; service design agency) we thought this would give us a good segway to band together the maker community comprising of engineers, designers and product managers. These three pillars of ‘making’ however, tended to work in silos and we really wanted to break that.</p><h3>However, we were faced with a challenge</h3><p>Most meetups we had attended thus far locally were notorious for being one of the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yWhmIV2vrwiQDJWaF2tFfQ.png" /><figcaption>The current perils of meetups</figcaption></figure><p><strong>We wanted to do something solid</strong>. Where people didn’t just come to hear one person talk for an extended period of time and go home without having anything to take away.</p><h3>So, in Very Bad Wizard style we designed it:</h3><p>We have an <a href="https://www.instagram.com/p/B3weUAvldbl/">exercise</a> that helps get ideas out of people, fast. Without having to go into an endless debate about the specifics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IYsbaVWjm3QdmRGQIGL2iA.png" /><figcaption>The Product Hunt Colombo Meetup hosts prioritizing challenges</figcaption></figure><p>The<strong> main challenge</strong> we were facing was this:</p><p>(HMW stands for How Might We)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/421/1*PAUZ-4Q3x1vGIuDGZJj6gA.png" /><figcaption>the main challenge we were going to solve for</figcaption></figure><p>There were other smaller challenges that we were also going to address:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_SC3aMaB8BLFCUqv1Y-ZFw.png" /></figure><p>As you can see the main theme was driven around creating an engaging meetup.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i_cCmOTS8UEKAORETh9EnQ.png" /></figure><p>After looking at outside inspiration for how other people managed to create amazing meetups for about 10 minutes, the four meetup hosts sat down to sketch out how our meetup would look like to solve for the top challenges.</p><p>The big idea behind this exercise is to not dive into endless discussions of what it should be, rather, to make things that are abstract (in our head), tangible.</p><p>When the sketching session was done after 20 minutes, we went for a round of dot voting to 1. Create a heat-map of the things we liked in everyone’s concepts. And 2. to select one winning concept!</p><p>After 5 minutes of heat-map voting, we had a winning concept!</p><p><strong>All four of us had our eyes set on one concept.</strong></p><h3>The Winning Concept</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6WHezybq4QOcNX7byFj_Jg.png" /><figcaption>What the meetup poster would’ve looked like</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mq2dnxO_JFh1fXOrOltGBw.png" /><figcaption>What the agenda for the meetup was</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mFoey5chngrJNc3ppOTsQQ.png" /><figcaption>Event Memorabilia</figcaption></figure><p>If you can’t understand what’s on there I don’t blame you. Here’s what it means.</p><p>The meetup was split into two parts:</p><ol><li>The Lightning Design Jam workshop — a workshop that was similar to one that was used to brainstorm the meetup but to find out the main challenges in the maker community, prioritize the challenge &amp; come up with solutions to solve for it, <strong>together</strong>.</li><li>Maker Demos — The Maker Demos segment was to feature the local creator’s products, but with a twist. We adopted the Japanese style of presenting called ‘Pecha Kucha’ which comprised of talking for 20 seconds per slide, 20 slides in total, a total of 6.67 minutes of speaking time. The big idea around doing this was to keep it concise and force the creator to have one single narrative or important lesson he/she wanted the audience to takeaway.</li></ol><h3>How did it all look?</h3><p>With a winning concept, we had all the groundwork needed to set up the meetup.</p><p>This was what the poster in high-fidelity looked like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rxr0DoI3v-gvVZgo9QeuMA.png" /><figcaption>The main meetup poster</figcaption></figure><p>We also wanted to have some memorabilia for the attendees (as shown in the last panel of the concept sketch):</p><p>The attendees whose solution got picked for the Lightning Design Jam exercise would’ve gotten a custom made Apprentice Sticker:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FSwhR2i-baTFawE39A77EQ.png" /></figure><p>And for the creators who presented for the Maker Demos, they got a Master Sticker:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5FmdXyg3BcWWzmMvulvZ6w.png" /></figure><h3>How did the meetup go?</h3><p>The response to the meetup was very positive. The lightning design jam exercise helped get everyone’s ideas out and allowed all perspectives to be heard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_Vp6CKEzJDqk0ODHKJfx8g.png" /><figcaption>Attendees going through the Lightning Design Jam Excercise</figcaption></figure><p>The entire photo album of the meetup is available to view <a href="https://www.facebook.com/media/set/?set=ms.c.eJxFU8kRA0AI6ijjffTfWGYxmi~%3BjIgIrbkluoUJJFf0RADpA~%3BwEXNzJl~%3BQHSBSByJyiEkkliJ4owUb4TOk9knxjbA8R5gYgHcO9ac8cE0w8IwROyfeJVlZp2E5Y2HEdqguN6J9KfDm1aHaH9JqL3uGB6pFp1QMzaFeasWHvHeQcAkgVEocMO0AQgS~_rGeOLnBxVcF1ugQOp8HAEO6rrjAsdVXFDwI2yv9USU6Ss9cs6vPFKGMNq1yjRR7trowJOrg2RjwtcxE5jcF0OSPR3SS5rS4NBV6pQ4~%3B4LyHj8uF5UpjF5QBtfV1~%3BVwQnK1SjUF518LTadBesLGdTnXkxnCfJXGlD~%3B~_5W~_sDbomF36D1J6f4VOp26KOLXGVioZ0uQZNcnnJ2TTIr0FWPunrreVZaxcDuq5noU7HVOoLMHrHLw~-~-.bps.a.2547052138737785&amp;type=1&amp;__xts__[0]=68.ARAJ0SmlSB9xMIFIO5htU-mc_V6LAYgbdzOYrHoEsU5G9ETVZ7cAOWz1Z9uFGClVrol8flZhnWV5n5F83qoc5YtHu4hl_cCju1frRqS6Tc1FjIYbFvW0SuF3PNEtnUhlKJ93kwX4Rh6M8rSSdQ_iUQDtUWo8cNw3dSxLVbwock46r7xNKwV8mDh5vRIPyWRjorriOlZrZHgeDfvy-kexSsiVb-QR0r0OuXpXvxQcnXaek7cIjMcMf0K7UdUpiAnaEx6m8r7Fi1GsY9hDfGrZ85KIIYszysODnXRnu6b1W0ZytQX7SBx18HXB-A9yzI4xNQmzM1E7qeItROTCoQPKXXoMh0bncMOmP_FKe53v6W7MSCbDNbwhAU6OHnh6sQxN0JwYKrIjeAhg4tnIQkzGhBPIYcX7ORoginaR_pw19QG3RE3p4UJIAzXHm1cU3WVytlmV9aQYVhQkyfpXOg1LQsJLKhN7j-Dxz3Uwr7sYgBBICQ-noLxPfhLLaG5waBaxQOlLk0NQshuK3VEDbuFuB8MCJJ7e1VqWCD8P4ZZ7CM5uGXNL&amp;__tn__=HH-R">here</a>.</p><p>We had 3 groups of about 10 people in each one, all attendees coming from either product management, design or engineering principles. We noticed more product managers (CXO’s, founders and directors also fell into this category) attended as opposed to engineers and designers, least of all being designers (something we’ll be solving for in the upcoming meetups).</p><p>Each of the three groups had different perspectives to what was the most pressing challenge in the local maker community right now. As event hosts, one of our goals was to also help the attendees empathize with the challenges faced in the other principles of making/creating and we felt that it was thoroughly realized by the end of the exercise. <strong>#HugeWin.</strong></p><p>As for the Maker Demos, the presenting style was challenging for the creators. But they rose to the occasion and delivered a really memorable story in under 7 minutes!</p><h3>What did the attendees think of the meetup?</h3><p>Here’s the RAW feedback we got!</p><p>We took it in the ‘I liked’, ‘A success was’ &amp; the ‘I wish’ format:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tqUsSFBNtnPlXmqgldmm2w.png" /><figcaption>The attendee feedback</figcaption></figure><p>Overall, we felt that the big challenge of curating the meetup to help the attendees deeply engage in a subject was overcome in the format that we decided on.</p><p>Based on the overwhelmingly positive feedback we received, we plan to have one Product Hunters &amp; Other Bad Wizards Meetup every month and constantly iterate on the challenges faced by the maker community and to also keep making it better each time with the feedback we receive!</p><p>Special shoutout to the Product Hunt team for being the absolute superstars they are. Allowing us to develop the community worldwide, for sending us Product Hunt merchandise and for answering any questions we have promptly! It&#39;s a real honour to be community host 🙂</p><p>Lastly, if you’re around for the next Product Hunt Meetup in Colombo we announce it on our <a href="https://www.instagram.com/vbwizards/">Instagram page</a> when the agenda has been confirmed!</p><p>Looking forward to seeing you there! 🧙🐱</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66ebacd69629" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>