<?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 Swarna Hebbar on Medium]]></title>
        <description><![CDATA[Stories by Swarna Hebbar on Medium]]></description>
        <link>https://medium.com/@swarnahebbar?source=rss-b9959ace5163------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*87wuGKy8hAm5Wkhu.</url>
            <title>Stories by Swarna Hebbar on Medium</title>
            <link>https://medium.com/@swarnahebbar?source=rss-b9959ace5163------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 16:21:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@swarnahebbar/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[AI can never replace Product Managers]]></title>
            <link>https://blog.prototypr.io/ai-can-never-replace-product-managers-9d96202a218c?source=rss-b9959ace5163------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d96202a218c</guid>
            <category><![CDATA[generative-ai-tools]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[roadmaps]]></category>
            <dc:creator><![CDATA[Swarna Hebbar]]></dc:creator>
            <pubDate>Mon, 24 Jun 2024 10:57:32 GMT</pubDate>
            <atom:updated>2024-07-04T10:04:47.155Z</atom:updated>
            <content:encoded><![CDATA[<p>But AI can be a sexy assistant.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BUqK0zOO2qjmfRp8pOnxqQ.png" /></figure><p>The intuitive lateral thinking, the charming negotiation, the cunning trade-offs, the edgy toe-ing of the line.</p><p>The wonderful human attributes and behaviours are so unique &amp; so integral to the role of a product manager. It is the creamy layer of wordly intellect.</p><blockquote><strong>This is why product jobs are sought after. Once human beings reach a certain level of intelligence, the need to exercise that intellect becomes orgasmic.</strong></blockquote><p>For AI to replace these qualities, it is almost unimaginable. Almost ridiculous to think of AI being able to generate a product requirements document that covers edge cases, takes care of caveats with the intricacies of how every company uniquely functions.</p><p>But AI can be a great assistant for product folks.</p><p>For example, AI can generate a generic template for product requirements by <strong>pulling in market facts to boost your problem statement</strong>, suggesting industry-related metrics, giving you a <strong>boiler plate for your user stories</strong> &amp; features.</p><p>And this you can convert to product gold with the very abilities that make you uniquely human.</p><blockquote>And from this product gold (requirements) that contains all the unique insights that you have added, AI can slice, dice, rephrase &amp; enhance to generate Customer Documents &amp; Release Announcements. In just <strong>5 minutes.</strong></blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FFsKi5l8Lsrc%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DFsKi5l8Lsrc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FFsKi5l8Lsrc%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e0b8e79cbc947f09488acfb740fcd8ee/href">https://medium.com/media/e0b8e79cbc947f09488acfb740fcd8ee/href</a></iframe><p>Boggl does this efficiently by picking up <strong>specific aspects of your PRD to generate specific sections</strong> of your Customer documents or Release documents.</p><blockquote>Needless to say, you save precious time.</blockquote><blockquote>But most of all, it is absolutely <strong>delightful✨</strong> to see that sleek magic happen.</blockquote><p>Check us out on <a href="http://www.boggl.app/">Boggl.a</a>i!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d96202a218c" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/ai-can-never-replace-product-managers-9d96202a218c">AI can never replace Product Managers</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why your Product Requirements shouldn’t be a Document]]></title>
            <link>https://blog.prototypr.io/why-your-product-requirements-should-not-be-a-document-a9797aaabd35?source=rss-b9959ace5163------2</link>
            <guid isPermaLink="false">https://medium.com/p/a9797aaabd35</guid>
            <category><![CDATA[work]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Swarna Hebbar]]></dc:creator>
            <pubDate>Wed, 20 Dec 2023 12:10:31 GMT</pubDate>
            <atom:updated>2023-12-21T04:31:27.325Z</atom:updated>
            <content:encoded><![CDATA[<p>First things first, write less. Much less.</p><p>Documents are boring as hell. You don’t need a blog to tell you that.</p><p>Because of this, companies are going from writing long pages of requirements to not writing requirements at all.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zLyifV-ZEaBCvwDa" /></figure><blockquote>You can get away with not writing requirements if you are a super lean product with a loyal workforce. But if the product expands out or you have a churn of employees, your Knowledge Transfer process will be a disaster.</blockquote><h3><strong>Having said that, the document concept itself is flawed. Why?</strong></h3><p>❌ Siloed product data</p><p>❌ No Transparency around Product / Feature Status</p><p>❌ Inflexibility of documents leads to Repetitive Product work on other tools</p><p>❌ Meaningful organisation of Documents is hard</p><p>❌ No Structure &amp; Format — Every Document looks different making it hard for stakeholders</p><p>❌ Too much, too long, too difficult to read!</p><h3>So, what are the ideal attributes of Product Requirements?</h3><p>With <a href="https://www.boggl.ai/">Boggl.ai</a>, you can supercharge your Product Requirements to have more value to you &amp; your team.</p><p>✅ <strong>Bite sized, concise documents</strong> — nothing is uneccessary</p><p>✅ <strong>AI Power your Requirements:</strong> <br>In the age of AI, why should your PRDs be left behind!<br>Autogenerate Customer facing notes, Internal/External Release Notes &amp; more from your PRD through AI.</p><p>✅<strong> Label every Feature:</strong><br>Every Feature has a status label — In Development? Your whole org knows.</p><p>✅ <strong>Transparency of Data:</strong><br>Product data beautifully reflected across dashboards — easily search for features, metrics, you name it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6ii7SSXRIPHT69HPffGogQ.png" /></figure><p>✅<strong> Super-powered as a Task Tool:</strong><br>Convert stories / features / both to task links and handoff!</p><p>✅ <strong>Organic Product Organisation:</strong><br>Features are seamlessly filed into products &amp; modules created by you</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SjsgtEMaD_NPFLG3uz5wDw.png" /></figure><p>Check out the <a href="https://boggl.app/">Boggl app</a> at <a href="https://boggl.app/">https://boggl.app/</a> !</p><p>Please leave your feedback in the comments below, thank you :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a9797aaabd35" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/why-your-product-requirements-should-not-be-a-document-a9797aaabd35">Why your Product Requirements shouldn’t be a Document</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Ideal Tool for Product Requirements]]></title>
            <link>https://blog.prototypr.io/google-docs-no-longer-cuts-it-for-product-documentation-550f5522b74d?source=rss-b9959ace5163------2</link>
            <guid isPermaLink="false">https://medium.com/p/550f5522b74d</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Swarna Hebbar]]></dc:creator>
            <pubDate>Tue, 12 Dec 2023 12:09:09 GMT</pubDate>
            <atom:updated>2024-01-08T14:09:14.411Z</atom:updated>
            <content:encoded><![CDATA[<p>Greg just joined a mid-sized company as a Product Manager last week &amp; has spent hours in getting up to speed but things are going slow.</p><p>He scrolled through pages of documents on Google Docs hoping dearly that this prep will help him score points with his manager.</p><p>Finally after a few hours he decided to setup a call with his manager. A few minutes into the call, he realised that the PRDs he went through were not relevant to his team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8CCrja_9YgHuLp25" /><figcaption>Photo by <a href="https://unsplash.com/@charlesdeluvio?utm_source=medium&amp;utm_medium=referral">charlesdeluvio</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Sound familiar?</p><p>Well, this is how things work in generic document systems like Google docs &amp; Microsoft. And they are wonderfully flexible- these systems.</p><p><strong>But with AI, we can do much better with Product Documentation.</strong></p><blockquote>Product Managers are a lot like homemakers of most families. They have to cater to everybody else’s needs. One needs their pasta cooked al dente, the other likes it mushy, another might not want pasta at all.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q8VlPdx6XkzpIljPT0Rc6w.png" /></figure><blockquote>Product folks are now working on tools that other team members are comfortable with &amp; find themselves limited to tools that aren’t really customised to product needs.</blockquote><h3>So what is frustrating about Google docs for product documentation?</h3><p>❌ <strong>Documents are silos</strong> of product information with no transparency</p><p>❌ <strong>Hours wasted on formatting</strong> of product requirements &amp; other docs</p><p>❌ <strong>Errors</strong> because of non-standardisation of Product Documents</p><p>❌<strong> Rework of product data on different tools</strong> like Roadmaps, Launch Planners, Metric trackers because of the 1-dimensionality of a document.</p><p>❌ <strong>Has anybody read your document?</strong></p><p>❌ <strong>Difficult for stakeholders to read</strong> because all PMs write different.</p><p>So do things get better?</p><p>Yes!</p><h3><strong>Boggl.ai is a AI Powered Product Document Tool customised to Product Manager needs</strong></h3><p><a href="https://www.boggl.ai/">Check out Boggl here</a></p><p>✔️<strong> Laser Sharp Requirements with Curated Sections</strong></p><p>✔️ <strong>Autogenerate accurate Product Documents using AI from PRDs</strong>:</p><ul><li>Release Notes</li><li>Customer facing Product Document</li><li>Market Strategy Plan</li><li>Test cases for QA</li></ul><p>✔️ <strong>AI Generation of Product Documents</strong>:</p><ul><li>Competitor analysis</li><li>User Research Document</li></ul><p>✔️ <strong>Convert User Stories / Features into Task links</strong> share-able on any Task Tool</p><p>✔️<strong> Track Metrics &amp; Feature Launches</strong> directly from PRDs</p><p>✔️ <strong>Easy Discoverability of Features</strong> &amp; Documents</p><p>✔️ <strong>Create Persona cards</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FJzo4_yNkoyA&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DJzo4_yNkoyA&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/b08603d03eff00249ac076107811c6d0/href">https://medium.com/media/b08603d03eff00249ac076107811c6d0/href</a></iframe><p>Product Managers finally have a AI Powered document Suite customised to their needs.</p><blockquote>Product Managers &amp; Founders can save 70% time by using Boggl.ai for data management &amp; focus that time on what matters- Strategy.</blockquote><p>And if it is tough to convince your team to start using another tool, you can always export all Boggl Documents in a Google Docs Format ;)</p><p><a href="https://boggl.app/">Check out the Boggl app here!</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=550f5522b74d" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/google-docs-no-longer-cuts-it-for-product-documentation-550f5522b74d">The Ideal Tool for Product Requirements</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ChatGPT sucks at creating Product Requirements]]></title>
            <link>https://blog.prototypr.io/chatgpt-sucks-at-creating-product-requirements-5ee07b550998?source=rss-b9959ace5163------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ee07b550998</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-manager]]></category>
            <dc:creator><![CDATA[Swarna Hebbar]]></dc:creator>
            <pubDate>Mon, 11 Dec 2023 08:29:00 GMT</pubDate>
            <atom:updated>2023-12-11T11:02:16.098Z</atom:updated>
            <content:encoded><![CDATA[<p>At <a href="https://boggl.app/">Boggl.ai</a>, we are trying to be AI first.</p><p>Being an app that helps PMs create kickass Product Requirements, we have been trying out AI to help autogenerate PRDs.</p><p>After repeated testing, we figured that it is just not reliable enough for Product folks &amp; Founders.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1GlomYSr_t01OY8htoG9XQ.png" /><figcaption>Nobody likes to edit mediocre, generic content!</figcaption></figure><p>It is probably a passable boiler plate. But by no means is it something that brings actual value.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-7yyj0z_PAWXGjoC" /><figcaption>Photo by <a href="https://unsplash.com/@hhh13?utm_source=medium&amp;utm_medium=referral">傅甬 华</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>ChatGPT has worked beautifully for Developers, but what about Product teams?</h3><p>Developers find immense value with the current form of AI with Github’s copilot autocompleting code in a pretty flawless way.</p><p>However code is more or less deterministic, strategy isn’t.</p><blockquote><em>The effort that goes into editing text far outweighs the benefit of autogenerating PRDs through chatGPT- this is why OpenAI hasn’t picked up amongst PMs like it has for developers.</em></blockquote><p>Compiling requirements is not just an act of data. <br>Human intuition, wisdom &amp; even in some cases, emotional intelligence plays a role in how you convey your vision to your team.</p><h3>So, how can AI help Product Managers?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b4YGmBFcCKvhqvR_93yv_Q.png" /><figcaption>Save time by augmenting your documentation with AI</figcaption></figure><h4><a href="https://boggl.app/">Boggl.ai</a> uses your Product Requirements to auto-create product documents with AI:</h4><p>At Boggl, we apply AI to specific aspects of your PRD for accurate output of different document types.</p><p>✅ Internal Release Notes<br>✅ External Release Notes<br>✅ Customer Product Document<br>✅ Test Cases<br>✅ Market Plan<br>✅ Competitor Analysis</p><p>Your PRD is a single source of truth for all AI outputs &amp; this makes all product documents you generate on Boggl.ai <strong>meaningful &amp; accurate!</strong></p><p>Curious to check it out? <a href="https://boggl.app/">Here is our app!</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ee07b550998" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/chatgpt-sucks-at-creating-product-requirements-5ee07b550998">ChatGPT sucks at creating Product Requirements</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your Product Requirements should be a Workflow, not a document]]></title>
            <link>https://medium.com/@swarnahebbar/your-product-requirements-should-be-a-workflow-not-a-document-fa5a9eb3a048?source=rss-b9959ace5163------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa5a9eb3a048</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Swarna Hebbar]]></dc:creator>
            <pubDate>Tue, 06 Jun 2023 11:08:28 GMT</pubDate>
            <atom:updated>2023-06-06T11:08:28.871Z</atom:updated>
            <content:encoded><![CDATA[<p>Alan sat to write his product requirements document. After spending 2 weeks on it &amp; making sure that he has covered all his user scenarios along with his designer, he added his developers to the document.</p><p>Brenda, the engineering manager &amp; Alan got on 4–5 calls over the next 2 weeks. After a high level thumbs up, Alan got the green signal to start handing this off to his tech team.</p><p>Alan would now spend a couple of days copy pasting these features to Jira tickets, grooming his backlog, setting priorities etc. All this prep before the next sprint cycle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iWSmupu2YkTPghaa" /><figcaption>Photo by <a href="https://unsplash.com/@sammywilliams?utm_source=medium&amp;utm_medium=referral">Sander Sammy</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>For the next sprint cycle, Alan spent 3 hours with his tech team, individually assigning tickets to each member.</p><p><strong>2 days after sprint planning:</strong></p><p><em>Hey Alan! Jamie here. Just wanted to call out that the sorting of values cannot be done without backend effort.</em></p><p><em>Hey Jamie! That’s a bummer. Can we just have a default sorting in that case?</em></p><p><em>Sure!</em></p><p><em>Cool, thanks Jamie.</em></p><p>Scroll, scroll, click, close, scroll, scroll.. After 10 minutes of scrolling, Alan finally finds the Jira ticket assigned to Jamie and makes changes to it.</p><p><strong>Done!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ks6L7_2tr13_TAwX" /><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><strong>3 weeks go by:</strong></p><p><em>Hey Maurice, why hasn’t the dashboard feature been pushed to the test website yet?</em></p><p><em>Hey Alan, there are a couple of failure points when I test. Sorting isn’t working as it should.</em></p><p><em>We decided to scrap sorting, don’t need that feature!</em></p><p><em>Oh really? your PRD still states that feature with a high priority mention though!</em></p><p>Alan’s pulse rose quickly. 2 weeks of feature delay because he missed updating his PRD.</p><p>Product Managers own many many many things. They own requirements, handoff process, team collaboration, negotiation, customer success, customer feedback, business bottomline considerations. You name it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bP0kd6GtlKC1JV-O" /><figcaption>Photo by <a href="https://unsplash.com/@markuswinkler?utm_source=medium&amp;utm_medium=referral">Markus Winkler</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>Adding to the juggle, is the stress of managing these across multiple platforms, and worse still, highly customisable platforms that require PMs to do the added work of personalising them to their workflow.</blockquote><h3>Everything starts with Product Requirements. But with Google docs / Microsoft Docs, this is the first &amp; most disconnected step in the workflow.</h3><p>At <a href="http://www.boggl.ai/">Boggl.ai,</a> we aim to make the life of PMs a little easier by upgrading Product Requirements from a mere document to a Microapp that can be integrated into any workflow.</p><p><em>Because, whether it be personas, project management, metrics, customer success, roadmap planning, feature launch planning, </em><strong><em>everything starts with product requirements.</em></strong></p><p><a href="https://beta.boggl.app/">Click here to try out free beta!</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa5a9eb3a048" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your PRD is NOT the single source of truth you think it is.]]></title>
            <link>https://blog.prototypr.io/your-prd-is-not-the-single-source-of-truth-you-think-it-is-654655e68f91?source=rss-b9959ace5163------2</link>
            <guid isPermaLink="false">https://medium.com/p/654655e68f91</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Swarna Hebbar]]></dc:creator>
            <pubDate>Wed, 31 May 2023 12:32:50 GMT</pubDate>
            <atom:updated>2023-06-01T06:34:01.496Z</atom:updated>
            <content:encoded><![CDATA[<h3>Your PRD is NOT the single source of truth you think it is</h3><p>Tom is a Product Lead at a large SAAS company. With recent layoffs at his company, he has had to take up multiple products under his wing &amp; manage workflows across several teams.</p><blockquote>Around 60% of his time is spent in writing, editing PRDs and FRDs for multiple teams. He spends around 2 hours a day copying User Stories from his PRD &amp; pasting them onto Jira tickets to prep for the next Agile cycle.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nsGjZNZYNaDtF82h" /><figcaption>Photo by <a href="https://unsplash.com/@glenncarstenspeters?utm_source=medium&amp;utm_medium=referral">Glenn Carstens-Peters</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Tom has a pretty cool manager named Jack. Jack knows that Tom is doing the best he can juggling multiple teams. It had been 6 months since the org restructure and Jack needed to review how the projects under him were faring.</p><p><em>Hey Tom! Can we catch up next week? We need to review your OKRs and success parameters of the product features you are owning.</em></p><p>Tom sighed &amp; rubbed his eyes. He has been swamped for the past few weeks &amp; now he has to prep for a review meeting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/446/1*K6qNQCD98VV4rK-gjt51zQ.jpeg" /></figure><p><strong>Another !ping</strong></p><p><em>Hey Tom! Lisa here. Didn’t we finalise on including the Payment flow within the same sprint? I can’t find the specs in your PRD</em></p><p><em>Hey Lisa, sorry about that! I added those specs directly on Jira. Give me a minute, I will share the ticket with you.</em></p><p><em>Thats great Tom! But could you update the PRD as well? I don’t think my manager can access your Jira board.</em></p><p><em>Oh sure Lisa, I will get to that right away.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-r4zmYqcUfBti8Q4" /><figcaption>Photo by <a href="https://unsplash.com/@vechorko?utm_source=medium&amp;utm_medium=referral">Dmitry Vechorko</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>!ping yet again</strong></p><p><em>Hey Tom! I needed to discuss something around the June 15th launch.</em></p><p><em>Hey Jim! What June 15th launch?</em></p><p><em>The launch of the checkout feature.</em></p><p><em>Hey Jim, that has been preponed to June 1st!</em></p><p><em>Oh really? But your PRD states June 15th!</em></p><p>Scroll. Scroll. Click. Close. Scroll. Click.</p><p><em>Ah sorry Jim, I hadn’t updated the PRD. Going forward, you can check updated dates on this other tool -*</em>*****</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8NOtOzgKvqr2G3f_" /><figcaption>Photo by <a href="https://unsplash.com/de/@braydona?utm_source=medium&amp;utm_medium=referral">Braydon Anderson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>The PRD writing process is a a disconnected effort. Documents become outdated quickly especially since handoff to design and tech teams happens on other tools.</blockquote><h3><strong>Your PRD can be a single source of truth with 1 hack.</strong></h3><p>For your product requirements to be a consistent source of truth,<em> it needs to be the only thing you need to update </em>even if story or feature handoff happens across various tools like Jira, Asana etc.</p><p>With Boggl.app, every story or feature from your PRD can be handed off to your team through any workflow. Iterations or changes to the document? It is all auto-synced from your PRD!</p><p>At <a href="https://www.boggl.ai/">Boggl.ai</a>, we are building the revolutionary tool for Product managers to make their lives a little easier. We aim to elevate the way in which feature and product requirements are communicated.</p><p>Are you a Product manager? Or an entrepreneur managing a tech team? <br>Try our <a href="https://beta.boggl.app/">free beta version</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=654655e68f91" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/your-prd-is-not-the-single-source-of-truth-you-think-it-is-654655e68f91">Your PRD is NOT the single source of truth you think it is.</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Frustrations of Writing Standard PRDs]]></title>
            <link>https://medium.com/@swarnahebbar/writing-standard-product-requirement-documents-is-frustrating-outdated-ecac70709f33?source=rss-b9959ace5163------2</link>
            <guid isPermaLink="false">https://medium.com/p/ecac70709f33</guid>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[product-requirements]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <dc:creator><![CDATA[Swarna Hebbar]]></dc:creator>
            <pubDate>Thu, 08 Sep 2022 06:03:42 GMT</pubDate>
            <atom:updated>2023-06-01T04:54:45.909Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Frustrations of Writing Product Requirement Documents</h3><p>Raul was picked to lead the new project at his company. He completed 4 rounds of user interviews, a 10 hours of meetings with his manager, team &amp; CEO to solidify a direction &amp; then finally sat to work.</p><p>Now you’d ask, what do you mean by he ‘finally sat to work’? Aren’t those hours of meetings &amp; interviews, actual work? Well, yes. But also, no.<br>In the product world, documentation is everything. The Product (or Feature) Requirement Document (PRD) is a reflection of you, your aptitude, your skill. And the ultimate stamp &amp; proof of your work.</p><p>Raul would now spend the next few weeks on this document - writing, editing, discussing each advancement with his product team. <br>The document is finally ready to be shared with the tech team. He clicks Share, adds 6 email addresses &amp; presses Done<em>.</em></p><p>1 week goes by..</p><p><em>Sam, do you have any questions or concerns on the document I shared last week?</em></p><p><em>Hey Raul, can we sync on this &amp; discuss the document first?</em></p><p>Raul frowns &amp; rubs his forehead- <em>why wouldn’t he just read it? </em>He pulls the laptop closer and types - <em>Sure, let me send you a Zoom link.</em></p><blockquote>After all, it is his job to relay product to the tech team.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fn3oLV5D3pQVHoXF" /><figcaption>Photo by <a href="https://unsplash.com/@magdaleny?utm_source=medium&amp;utm_medium=referral">Magdalena Smolnicka</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Do you empathise with Raul? I’m sure you do. After all, I have narrated the story from his point of view. But if you have a look at the document that Raul shared with his team, you might think differently ;)</p><p>Product managers compile requirements in documents in exhaustive ways. Exhaustive because that is the only way they are able to showcase their work, ensure that no detail is missed, have the product be watertight, unquestionably so.</p><p>But then, who wants to read exhaustive documentation? Nobody.</p><blockquote><strong>This means that Product Managers inevitably redo all of their work.</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pcDmi4-8j4ttVObe" /><figcaption>Photo by <a href="https://unsplash.com/@a_d_s_w?utm_source=medium&amp;utm_medium=referral">Adrian Swancar</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Product teams across the tech world operate in vastly differently ways from each other. Every Product owner, even within the same team, writes documentation very differently- making it very challenging for stakeholders to consume this information.</p><p>Engineers have CodeEditors, Linkers, Compilers- extensive tools to help them code. Even smaller teams follow standard processes &amp; have tools to manage them — Waterfall, Agile, Jira, Trello etc. <br>Designers have Sketch, Figma, Zeplin, prototyping tools.</p><blockquote>Product managers have 0 specialised tools for their basic job of compiling requirements effectively &amp; sharing it with their stakeholders.</blockquote><p>At <a href="https://www.boggl.ai/">Boggl.ai</a>, we are building the revolutionary tool for Product managers to make their lives a little easier. We aim to elevate the way in which feature and product requirements are communicated- one step at a time.</p><p><strong>Are you a Product manager? Or an entrepreneur managing a tech team?</strong></p><p>Communicate your product vision effectively in a matter of minutes &amp; share them through any workflow your team is comfortable with.</p><p>Try our <a href="https://beta.boggl.app/">free beta version!</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ecac70709f33" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An Artist’s ode to past glory]]></title>
            <link>https://medium.com/writers-guild/an-artists-ode-to-past-glory-c2a85e83dedb?source=rss-b9959ace5163------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2a85e83dedb</guid>
            <category><![CDATA[artist]]></category>
            <category><![CDATA[poetry]]></category>
            <category><![CDATA[life-well-lived]]></category>
            <category><![CDATA[fiction]]></category>
            <dc:creator><![CDATA[Swarna Hebbar]]></dc:creator>
            <pubDate>Thu, 29 Aug 2019 18:57:03 GMT</pubDate>
            <atom:updated>2019-08-29T18:57:03.883Z</atom:updated>
            <content:encoded><![CDATA[<h4>No more life to live.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LvUFlaNHiAQTP-uvWXweKQ.jpeg" /></figure><p>Knotted fingers splayed across white paper<br>Mosaic creased skin, green veins throb through<br>She cracked her knuckles against the steely table<br>Barely breathing whilst she drew.</p><p>She paused, fingertips pressed against scrawny wrist<br>Her pulse still felt strong, steady and slow<br>She sighed, stretched out, observed her hands<br>Once smooth and beautiful, now tremulous, old</p><p>Starchy white paper beneath powdery black charcoal<br>There is beauty sometimes, in simple stark contrast<br>But look closely n study, a trained eye will know<br>No detail was worthy, no impression would last</p><p>There was a time when the lady saw glory<br>Her touch could put Midas to shame<br>Each easel, each one held a wonderful story<br>But in time there was no story to share</p><p>Her work, last few, stacked in a corner<br>It had been months since she had seen the light<br>Forehead creased, she tried to stop the tremor<br>No avail, no matter how hard she tried</p><p>She sighed once more, at the corner she gazed<br>There were going to be no more glorious days<br>She looked around at the wooden walls she built<br>It was time, maybe time to see the light again</p><p>The stroke of the matchstick, the smell of burnt ash<br>It burnt through canvas, the corner was a flame<br>Eyes closed, leaned back, the walls now orange<br>Smiled softly, she would see the light again.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z3yHbv_ME_KrjXaw5sr2-g.png" /></figure><h4>Thanks for reading Writers Guild — A <a href="http://penname.me/?penaid=5c9d9cd86b86e65745140bfa">Penname</a> publication</h4><p>Share your stories on <a href="http://manystories.com/?penaid=5c9d9cd86b86e65745140bfa"><strong>ManyStories.com</strong></a> to reach more readers. <a href="http://pensignal.com/?penaid=5c9d9cd86b86e65745140bfa"><strong>Auto-tweet your stories on repeat</strong></a> with Signal to increase engagement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*843pidPZQqrNHEEhb5cYVA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2a85e83dedb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/writers-guild/an-artists-ode-to-past-glory-c2a85e83dedb">An Artist’s ode to past glory</a> was originally published in <a href="https://medium.com/writers-guild">Writers Guild</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6 UX Design tips to reduce Website Load time]]></title>
            <link>https://blog.prototypr.io/6-ux-design-tips-to-reduce-your-website-load-time-503c97b4ed20?source=rss-b9959ace5163------2</link>
            <guid isPermaLink="false">https://medium.com/p/503c97b4ed20</guid>
            <category><![CDATA[visual-design]]></category>
            <category><![CDATA[website-load-time]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-designer]]></category>
            <category><![CDATA[web-design-tips]]></category>
            <dc:creator><![CDATA[Swarna Hebbar]]></dc:creator>
            <pubDate>Tue, 16 Jul 2019 07:16:58 GMT</pubDate>
            <atom:updated>2019-07-20T05:53:56.097Z</atom:updated>
            <content:encoded><![CDATA[<h3>6 UX Design tips to reduce your Website Load time</h3><h4>A Designer’s role in making websites faster.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YPdRFYXfljhbqdtmcebqZw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@officestock?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Sebastian Herrmann</a> on <a href="https://unsplash.com/search/photos/hand-on-head-laptop?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>3 seconds. 3 seconds are all your get before more than half your users (~53%) decide your website load is taking up too much time of their lives and decide to move on- so states the <a href="https://www.thinkwithgoogle.com/marketing-resources/data-measurement/mobile-page-speed-new-industry-benchmarks/">2018 Research by Google</a>.</p><p>Impatience is the most reliable trait your user has. Today, if your website doesn’t open, there are 3 other websites who offer the same services that you do. Hell, even if Instagram takes more than a couple of seconds to open, it doesn’t take much thought for users to just move on to a completely different app like a Quora or an Youtube to entertain themselves.</p><p>That is how dispensable you really are.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FOiC5BKaPVLl60%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fphone-OiC5BKaPVLl60&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FOiC5BKaPVLl60%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="238" frameborder="0" scrolling="no"><a href="https://medium.com/media/f25b8ed07e5537d0ef47916ddb2d9422/href">https://medium.com/media/f25b8ed07e5537d0ef47916ddb2d9422/href</a></iframe><p>A short website load time is not necessarily just the responsibility of the developer. Designers can help make a huge difference.</p><p>How?</p><h3>1) Avoid Rare Fonts:</h3><p>An obscure font can slow down web load time. Especially, if your website has a lot of text content. Popular font are usually already cached and open super fast.</p><p>The best practise would be to use <a href="https://fonts.google.com/">Google fonts</a>. They have a great collection and also have this really cool feature where you can actually check if a font loads fast or not.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qv9LsEZmlVpXUHFtHi0Nwg.png" /><figcaption>Google Fonts: Click ‘SELECT THIS FONT’ on the font page to check the font speeds.</figcaption></figure><p>If you must use an Ornate font for the sake of preserving the brand look, confining it’s use to Headers or better still, confining it’s use to 1 page would be a good idea- with the rest of the content being in standard fonts.</p><h3>2) Be judicious with Social media buttons:</h3><p>Social media buttons plugins essentially make calls back and forth between social network’s server and your site, as your page loads. The mere distance from the social network’s server (if it is in another continent) can create latency.</p><p>This only gets worse when there are multiple different social media buttons on 1 page; the more buttons you have, the more calls need to be made and the slower the page loads.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/846/1*MTQhI3AMU2CynTVZkC3sGg.png" /><figcaption>The mind boggling galaxy of Social media</figcaption></figure><p>Putting some thought into this, helps. Would users really feel the need to click them at this point? Would your users really be interested in sharing the content that is on this page?</p><p>If there is an absolute need, you could request your Developer to ensure that the Social media buttons loads last. This makes sure that the rest of the page is up for your user and the buttons can take their time after!</p><h3><strong>3) Rollover buttons should be imageless:</strong></h3><p>Rollover buttons are dynamic buttons that have 3 different states- Normal state (mouse away), Hover state (mouse over it), Clicked state (mouse clicked). These greatly enhance user experience by providing the feedback to users as they interact with it.</p><p>However, traditionally Rollover Buttons is essentially a composite of 3 images (for the 3 statuses) that have to load <em>before</em> the user interacts with it.</p><p>In the past, Javascript was used to swap the images and this can make your website slow (this method isn’t used anymore). Conversely, allowing each button image to load only <em>after</em> interaction might result in broken images being shown to the user- which is just terrible user experience.</p><p>Tip:</p><p>1. If you are thinking rollover, check if your developer can create interactive rollover buttons using CSS that are imageless! These load pretty fast.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*ADKzAuFlOX0WqRnSoJK8bA.gif" /><figcaption>Mentioned by <a href="https://blog.prototypr.io/stunning-hover-effects-with-css-variables-f855e7b95330">Tobias Reich</a></figcaption></figure><p>2. Coding the button to change its Hex colour upon click ensures there aren’t any hidden elements that would slow the page down.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sqq4JAUolnT2QQ1r7_hpPw.gif" /><figcaption>Credits: <a href="https://medium.com/@BertolaBrett/hover-button-with-design-components-in-framer-x-247b24eddab2">Brett Bertola</a>- Simple hex changes in button look elegant and do not compromise loading time.</figcaption></figure><h3>4) Accordions are your friend:</h3><p>If you have designed a website with lot of text content, you probably would have used accordions to segment content and make your page look less intimidating.</p><p>These are often designed as ‘Read more’ buttons; upon clicking of which users can view concealed content.</p><blockquote>Accordions are pretty neat tools to reduce webpage load time as well. If you expect only select users to be interested in expanding on the subject, <strong>you can ensure accordion content</strong> <strong>loads only once they are clicked</strong>; thereby ensuring that the website isn’t slowed down by hidden content.</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FSS3OlZyi8IqBYy5Nhz%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fsnl-saturday-night-live-season-44-SS3OlZyi8IqBYy5Nhz&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FSS3OlZyi8IqBYy5Nhz%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="235" frameborder="0" scrolling="no"><a href="https://medium.com/media/78153abd051d0283f37c9f4f8c61f39a/href">https://medium.com/media/78153abd051d0283f37c9f4f8c61f39a/href</a></iframe><p>Though, this should be a very calculated move. If majority of your users are likely to expand on the accordion, then they’d just end up waiting twice instead of once- which is just self defeating. If you have short and important content compartmentalised by accordions (for example, FAQ sections), it would make sense to load them along with the rest of the page.</p><h3>5) Optimise your images before sharing them with your developer:</h3><p>Cropping the images you want on the website to the perfect size before you share them with your developer goes a long way to ensure that load times are not affected.</p><p>Oversized images placed on the server would need to be scaled down on the browser and this slows down the website. Images that are in MBs are way too big- keeping them well under 100kB would help save atleast 20–100ms. The milliseconds add up with each image; ideally if your images are within 10kB, nothing like it!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KhuQFU932rlXMnOovSzfbw.png" /><figcaption>Responsive design: Cropped images for mobile website helps save load time and also allows you to customise the focus of the image on your mobile website. Source: My design of a Home bidding website</figcaption></figure><p>Each file type has their pros and cons. I personally prefer SVG formats; inspite of them being relatively large files, they guarantee good quality and can be scaled up and down easily. If you aren’t too concerned about image quality (ex. small thumbnails) or if you are displaying photographic images, JPEG is a good bet to allow for quick website load.</p><h3>6) To Parallax or Not to parallax:</h3><p>Animations like dynamic elements that animate into place, parallax scrolling provide a very engaging vibe to users but have their drawbacks.</p><p>Parallax scrolling is an effect wherein the background of your website moves at a different speed than the rest of the page, creating an illusion of depth and provides an immersive experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/528/1*MvEB4Thn9UPyKa7xZwisvQ.gif" /><figcaption>Image: Squarespace template.</figcaption></figure><p>However, the code would need to constantly calculate where everything should be placed as your scroll and this causes the page to scroll very slow. Also, this effect is difficult to execute in mobile screens.</p><h3>How to manage User Perceived Wait time?</h3><p>In an article by Steve Souder, <a href="http://www.stevesouders.com/blog/2012/12/03/the-perception-of-speed/?sleep=5">The Perception of Speed</a>, he delves into user’s perception of time and how engaging them with interesting content or interactions can help prolong their wait time effectively.</p><p>But which type of animation to use when?</p><h4>Short loading time (&lt;6s):</h4><p>Most important factors to take care of:</p><ol><li>Engaging animations.</li><li>Ensure the load time never exceeds a maximum of 10 seconds.</li></ol><p>Loading spinners work well for relatively short loading time. Engaging animations greatly add to user experience and make the wait enjoyable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*CO8nV9rxH-rqVKA9CMBFdg.gif" /><figcaption>This is so cool! Credits:<a href="https://dribbble.com/shots/5515091-Loading-spinner"> Jeppe Drensholt</a></figcaption></figure><h4>Longer loading time (&gt;6s)</h4><p>Most important factors:</p><ol><li>Show a time estimation of website load.</li><li>Explain why the user needs to wait.</li><li>Make sure your progress bar is always moving.</li></ol><p>Progress bar animations are a good idea if you have lot of content on the page and you expect it to take a while. It is always a good idea to show the user how much longer they need to wait</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*YiqpEomcAJxcs_YpPGtYaA.gif" /><figcaption>A dream come true. Credits: <a href="https://dribbble.com/galshir">Gal Shir</a></figcaption></figure><h4>Skeleton screens- the reigning King of loading animations:</h4><p>In 2013, <a href="https://www.lukew.com/ff/entry.asp?1797">Luke Wroblewski</a> spoke against the spinner and in favour of the concept of Skeleton screens. The essence of what he meant is, any spinner or progress bar animation simply draws attention to the fact that the user is waiting- and that is exactly what we don’t want.</p><p><a href="https://uxdesign.cc/what-you-should-know-about-skeleton-screens-a820c45a571a">Skeleton screens</a> are placeholders for your webpage whilst they load; providing a step-by-step loading of images, text and content. The gradual appearance of UI elements keeps the user engaged and makes the website feel much faster.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/781/1*7r1ez5AaBgEcGZbsGp-N2w.gif" /><figcaption>The instant rendering of neutral blocks upon load that are gradually replaced by UI elements as they become available. Credits: <a href="https://www.tandemseven.com/blog/how-to-use-disneys-principles-of-animation-to-improve-ux/">tandemseven</a></figcaption></figure><p>The focus of the user is on the content that is incrementally loading; and not on the fact that the website is in the process of loading. This small shift in perspective makes all the difference in user experience.</p><p>Skeleton screens are pretty much universal in their usage and wins hands down in being able to efficiently and effectively manager user perceived time with good user experience.</p><p>Loading time is not one of the main parameters that designers work by but it is important to keep it in mind- it might come in handy to tip the scales when you are at an impasse with a design decision!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=503c97b4ed20" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/6-ux-design-tips-to-reduce-your-website-load-time-503c97b4ed20">6 UX Design tips to reduce Website Load time</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Should recurring events be designed differently from one-time events?]]></title>
            <link>https://blog.prototypr.io/event-card-design-why-should-recurring-events-be-designed-differently-fceabc9cee52?source=rss-b9959ace5163------2</link>
            <guid isPermaLink="false">https://medium.com/p/fceabc9cee52</guid>
            <category><![CDATA[events]]></category>
            <category><![CDATA[eventbrite]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[cards]]></category>
            <dc:creator><![CDATA[Swarna Hebbar]]></dc:creator>
            <pubDate>Thu, 06 Jun 2019 09:04:18 GMT</pubDate>
            <atom:updated>2019-06-13T09:10:24.332Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why should recurring events be designed differently from one-time events?</h3><p>All event websites have one thing in common- the card design.</p><p>Do they do justice in treating recurring events different enough from one-time events? The simple answer is <strong>No</strong>.</p><blockquote>But then, do recurring events special treatment? Most definitely yes! A Salsa dance workshop on Sundays that takes place for 3 months requires users to spend tens of hours of their lives; compared to a one-time stand up comedy event.</blockquote><p>Showing two similar looking cards with salsa and stand-up comedy would mean, ignoring not just the time factor, but also, ignoring the needs of a very different type of end user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J4KdGS31tbtJ6BJqWKtl-Q.png" /></figure><p>Event cards are a tried and tested method.</p><p>The card design, is an ideal way of showing event information in the most eye catching and concise manner. Cards are also responsive, optimally use space, can be scanned easily, allows for flips, stack, swipe, click actions and are a designer’s dream when it comes to creating effective visual hierarchy.</p><p>But there is one thing in common in all the above event card designs in event websites- the proportion of space taken up by each element in the event card are more or less the same.</p><ol><li><strong>The image takes up &gt;50%</strong> of the real estate (irrespective of the image quality)</li><li>Event header is usually the boldest text.</li><li>Event description is concise.</li></ol><p>This is a perfect format for a non-recurring event.</p><p>However, what about recurring events that require attendance from a user for a period of time?</p><h3><strong>Polly’s story:</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EpKHR2S578kzLrmyRjDEeg.jpeg" /><figcaption>Polly buys milk everyday from the grocery store. Sort of like a recurring event?</figcaption></figure><p>Now imagine if this grocery store with no clear signboard, and which is located in a local street with loyal customers; is relocated to a mall? The mall, which is a place where people usually go to window shop or make an occasional large purchase.</p><p>The grocery store sales is going to suffer in comparison.</p><p>It’s not a perfect analogy but it comes close.</p><blockquote>Non-recurring events rely on jazzy advertisement to attract a 1 time purchase, not dissimilar to boutiques in malls. On the other hand, recurring events (the grocery store) rely on regular customers that merit the long term effort of a service provider.</blockquote><p>Simply put, placing them amongst non-recurring events just doesn’t do them justice.</p><h3><strong>So why should recurrent events be designed differently?</strong></h3><ol><li><strong>Because they require a higher level of commitment from the user.</strong></li></ol><p>This might impact functionality changes; for example, allowing users to RSVP to each session of the recurrent event they sign up for.</p><blockquote>A user who subscribes for an event happening 4 times a week for a month, is already committing 16–20 hours of his time to this event. Doesn’t this user deserve special attention when it comes to his experience of browsing through the website?</blockquote><p>2. <strong>Because recurring events are frequently specialised events targeted towards a specific audience:</strong></p><p>For example, tech workshops- wherein, the names of the faculty, content of the workshop, information about certification has a higher value than a bright image meant to grab attention.</p><p>Most of the event websites choose to ignore this critical difference.</p><p>3.<strong> Because they have different advertising requirements:</strong></p><blockquote>In a website, if recurring event cards are repeated several times, it might result in users just scanning over them.</blockquote><blockquote>On the contrary, if a recurrent event is mentioned just once amongst a group of non-recurring events , you are taking away from the specialised quality of a recurring event. Event Brite attempts both the above methods:</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v-IclU5ntuiThhg_bCfj1g.png" /></figure><p><strong>4. The value for the Service provider of a recurring event:</strong></p><p>A Service provider devotes his/her time over a long period to make recurring events happen.</p><p>Sorting his/her event between non-recurring events does not fulfil his requirements, which are:</p><ol><li><em>Being able to stand out to users specifically looking for specialised, in-depth events, </em>and,</li><li><em>Allowing a live support system on the website that assists users in being regular to the event they have subscribed to, over a period of time.</em></li></ol><p>These 2 requirements are very unique to Service providers conducting recurring events and are not addressed at present. As a result, many of these Service providers invest a whole lot of money in creating their own websites.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DUXekusZtCorJH8dDEAr3A.png" /></figure><h3>Event card differences?</h3><p>So what are priority differences between recurring and non-recurring events that should ideally reflect in the way you design your event cards?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BSNm9Jg0Ff-OKutamvdqxg.png" /></figure><h3><strong>UX Design solutions?</strong></h3><p>The first step is recognising that mixing Recurring events amidst Non-recurring events is not an ideal UX approach.</p><p>There is no single UX solution to such a problem. The architecture largely depends on the business.</p><p>A few approaches are:</p><ol><li><strong>A high level separation of recurrent and non recurrent event types:</strong></li></ol><p>This would mean all recurring events are displayed separately from non recurring one-time events.</p><p>I have explained 2 possible scenarios in this format. There could be more scenarios depending on the context.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bbdBdiWSQDHrdYVufAskKg.png" /></figure><p><strong>2. Ability to separate recurrent and non-recurrent event types by a filter.</strong></p><p><strong>3. Distinction of event types reflective in the design of event cards:</strong> A subtle and yet, noticeable difference in how the event cards look would help a great deal in informing the user at a glance as to the nature of the event.</p><p>It is unrealistic to declare a single general UX solution that would apply to all event websites.</p><p>Design is about the context, as always.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff51076%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Ff51076%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Ff51076%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href">https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fceabc9cee52" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/event-card-design-why-should-recurring-events-be-designed-differently-fceabc9cee52">Should recurring events be designed differently from one-time events?</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>