<?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 Startup Reality Check on Medium]]></title>
        <description><![CDATA[Stories by Startup Reality Check on Medium]]></description>
        <link>https://medium.com/@StartupRealityCheck?source=rss-ae8f7209f9b5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*RX_cO51sYhQIPoRxZE_wyg.png</url>
            <title>Stories by Startup Reality Check on Medium</title>
            <link>https://medium.com/@StartupRealityCheck?source=rss-ae8f7209f9b5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 02:31:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@StartupRealityCheck/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 Tale of the Lost Startup and the Incredible Pitching Solution]]></title>
            <link>https://medium.com/agileinsider/the-tale-of-the-lost-startup-and-the-incredible-pitching-solution-29993fa9ed8d?source=rss-ae8f7209f9b5------2</link>
            <guid isPermaLink="false">https://medium.com/p/29993fa9ed8d</guid>
            <category><![CDATA[team-collaboration]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Startup Reality Check]]></dc:creator>
            <pubDate>Fri, 11 Aug 2023 19:45:28 GMT</pubDate>
            <atom:updated>2023-08-12T19:23:25.844Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fWhHS9MTRuhssuqRI-OPsg.png" /></figure><p>Can I tell you a secret? Brace yourselves… I actually do work sometimes! And no, I don’t mean pouring myself a coffee. My most recent assignment? A startup whose management team was as baffled as a pirate with two left hooks, trying to make a team of engineers walk the product development plank.</p><p>This team, bless their digital hearts, was drowning in a sea of confusion, gasping for the lifebuoy of understanding and ownership. To translate this into non-techy lingo, they didn’t have a clue what they were building, why they were building it, or who even wanted it. I mean, talk about having a compass but no map!</p><p><strong>Chaos Amidst the Comedy</strong></p><p>Adding to the comedy of errors, different teams were duplicating work, stepping on each other’s code, and battling over the same features like overexcited Black Friday shoppers. Meanwhile, a legion of other features was left collecting dust on the proverbial shelf. The ghost of inefficiency was definitely haunting this ship.</p><p><strong>Hope Amidst the Startup Storm:</strong></p><p>Naturally, the question on everyone’s lips was: How can we right this seemingly doomed ship? Yes, believe it or not, there’s hope even in the foggiest of startup seas.</p><p>Firstly, let’s dispel the idea that there’s a magical unicorn solution that can fix everything overnight. The reality is, there are a gazillion tools and techniques to use, but the real first step is figuring out where you are, where you want to be, and how to get from point A to B without walking the plank.</p><p><strong>Embarking on a Journey of Understanding</strong></p><p>So, the million-dollar question, how to understand where we are? Well, I suggested a team gathering, not for a game of ‘Guess Who’ but for something far more enlightening. I asked them to put together a product pitch and then… wait for it… present it to each other!</p><p><strong>The Melting Pot of Pitches</strong></p><p>You’d be amazed at the varied understanding of what they were building and why. The pitches were a melting pot of tech jargon, as high-level as Mount Everest. No one seemed to have thought about how they’d know if the product was successful. It was like they’d built a ship but hadn’t considered whether it would float or where they wanted it to go.</p><p><strong>The Missing Conversation with Navigators</strong></p><p>They’d been so busy hammering nails and tying ropes, they never spoke to the ‘navigators’ — the product managers, marketing, or sales departments. They hadn’t asked whether the product and features they were building would sail smoothly in the market ocean.</p><p><strong>The Power of a Simple Pitch</strong></p><p>There you have it, the tale of a startup adrift and the power of a simple pitch. Stay tuned to find out if they managed to get their ship sailing smoothly toward their destination!</p><p><strong>Delving into the Gritty Details</strong></p><p>Well, since you asked for it, let’s delve into the gritty details — all the dull but important stuff. Don’t worry, I’ll sprinkle in some of my usual charm. Ready to tackle the nitty-gritty of how to get your ship on the right course? Good, because I’ve been there and done that.</p><p><strong>Step One: Craft a Pitch Template</strong></p><p>Craft a pitch template. Yawn-inducing, I know, but believe me, it’s a game-changer.</p><p><strong>Step Two: Share It with Your Team</strong></p><p>Share it with your team. In my case, it was like addressing the United Nations, given the size of the company. But for you, it might be just your five-person ensemble. Whether it’s your developers, your marketing folks, your sales team, your designers, or even the office dog, everyone should be singing from the same hymn sheet.</p><p><strong>Step Three: The One-Minute Pitch Template</strong></p><p>Once the meeting was in everyone’s calendar (because who doesn’t love another meeting, right?), I gave them the lowdown:</p><p>[Solution Name]: A One-Minute Pitch Template</p><p>Solution Overview: “Our solution, [Solution Name], is a [describe what kind of solution it is] designed specifically for [target audience]. Its core purpose is to [describe the main goal of the solution].”</p><p><strong>Target Audience:</strong> “This solution serves [target audience], helping them to [describe the problem it helps the target audience solve].”</p><p><strong>Making a Difference:</strong> “The unique aspect of [Solution Name] is its ability to [explain how it changes the status quo or improves upon existing solutions]. This leads to [describe the larger, positive implications of this change].”</p><p><strong>Delivering Value to End Users:</strong> “By ensuring [describe the key benefit or result], we deliver valuable, relevant, and impactful solutions to our end users. This means [describe the tangible benefit for the user].”</p><p><strong>The Eye-Opening Experience</strong></p><p>Then, I rolled out the red carpet — the template. I allocated 15 minutes (because we all know time is money) for them to whip up their own pitches about the product, using the template I’d provided as a guide.</p><p><strong>Be Specific and Focused</strong></p><p>But here’s the catch. I asked them to stay on point and be specific. Vague statements like, “Our solution will make the world a better place,” were banned. I wanted the deets: How will it help? Whom will it help? And as creators, how would they know if they’ve really hit the mark with the user’s needs and expectations?</p><p><strong>Pitching Under Pressure: Team Showdown</strong></p><p>After 15 grueling minutes of frantic brainstorming, it was showtime. Each team member had their moment in the spotlight, tasked with pitching the product as if the rest of us were high-rolling investors. The pressure was on.</p><p><strong>A Breath of Fresh Air and a Team Reboot</strong></p><p>And boy, was it a spectacle! The team gave it their all, but if I’d actually been clutching a briefcase full of cash, it would’ve stayed firmly shut. Despite their best efforts, and listening to their pitches, you’d never guess they were all working on the same product for the same audience.</p><p><strong>Embracing the Essence</strong></p><p>But, don’t get me wrong. This exercise was not only a breath of fresh air but also a fantastic starting point for a team reboot — this time, with a solid understanding and alignment.</p><p>So, dear startup founders, here’s the essence of it: gather your crew, craft a pitch, present it, and brace yourself for the revelations. What you’ll find might surprise you, maybe even knock your socks off. But fear not, it’s all part of the process to get your startup ship sailing smoothly toward the horizon of success.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29993fa9ed8d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/agileinsider/the-tale-of-the-lost-startup-and-the-incredible-pitching-solution-29993fa9ed8d">The Tale of the Lost Startup and the Incredible Pitching Solution</a> was originally published in <a href="https://medium.com/agileinsider">Agile Insider</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Startups Unzipped: A Merry-go-round of Feedback Frenzy]]></title>
            <link>https://medium.com/agileinsider/startups-unzipped-a-merry-go-round-of-feedback-frenzy-1503aa338b84?source=rss-ae8f7209f9b5------2</link>
            <guid isPermaLink="false">https://medium.com/p/1503aa338b84</guid>
            <category><![CDATA[mvp-development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Startup Reality Check]]></dc:creator>
            <pubDate>Mon, 24 Jul 2023 15:47:52 GMT</pubDate>
            <atom:updated>2023-07-25T11:34:20.636Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aujacWh48y1kFgFsXZN2jg.png" /></figure><p>Right, let’s dive into my personal life a bit, shall we? Picture me at a Brit Milah party, it’s a Jewish ceremony that circumcises boys at the tender age of 8 days. And man, the trouble I had with the present! No wish list, no gift registry, just me and my own wits, battling with the ludicrous prices of baby items that could buy a small island in the Caribbean.</p><p>And after all that, I wasn’t even sure if my friends liked the gift! Just goes to show, it’s easier to predict the stock market than to guess what someone will think of your present.</p><p>And this got me thinking. Isn’t it funny how we stress out over a simple gift, but when it comes to launching a product or a startup, we’re as confident as a peacock on parade? We think our idea is the bomb and everyone will fall in love with it.</p><p>Sure, you might think that. But let’s get real, your chances of nailing it on the first try are about as good as finding a unicorn in the wild. Plus, most likely you’re bootstrapping this thing. So, every penny is a soldier, and you’re the general leading them to war.</p><p>Some might say, “Eh, they’ll love it!” and throw their money at it. But remember dear founders, you might as well toss that money into the sea and take a nice vacation.</p><p>Alright, enough with the reality check. Let’s roll up our sleeves and dive into the nitty-gritty of startup life.</p><p><strong>Ever heard of a feedback cycle? </strong>If not, think of it as your new best friend. It’s all about gathering feedback and letting it shape your plans like a skilled potter. Only then can you adapt and create something truly meaningful for your customers.</p><p>But how do you get started? Well, we can split this journey into a few stages:</p><ol><li><strong>Idea to POC (Proof of Concept)</strong>: So, you’ve got this brilliant idea. Your mom loves it, your friends are awed, and you’ve got a neat little nest egg ready. Before you start throwing money around like a drunken sailor, why not put together a Proof of Concept? It’s like a test drive for your idea, seeing if it’ll work in the real world. But hey, don’t just stop at creating it. Get out there, and gather some data, my dear! It’s not enough to have a long waiting list, you gotta know what they’re waiting for! What do they find most attractive? And don’t be shy, communicate with your users directly. Remember, the feedback cycle is a never-ending loop.</li><li><strong>Let’s stroll down the path from POC to MVP, shall we? </strong>Imagine you’ve been given the first chapter of a book that’s so gripping it could be the next “Harry Potter.” You’re now tasked with penning the subsequent chapters, while keeping the readers as hooked as they were with the thrilling opener. Sounds daunting, right? Well, that’s the jump from POC (Proof of Concept) to MVP (Minimum Viable Product) in a nutshell. Once you’ve created your POC, it’s time to strap in and prepare for takeoff. Your POC was well-received, the applause was deafening, and you’re ready to release the entire product into the wild. Not so fast, my dear! What does releasing the “whole product” entail exactly? In the language that’s less exciting than a PowerPoint presentation, your product, at its heart, is a meticulously prioritized list of all the features you plan to release, also known as your product backlog. But, here’s a question: do you need to unveil all your features at once? Is it necessary that your chat feature should mirror Instagram’s down to the last pixel? Or could it be slightly less snazzy, especially when your budget isn’t exactly the size of a Silicon Valley titan’s? Not all features are created equal, and it’s time you acknowledged that. When preparing for due diligence, founders are prone to wanting to dazzle with all the glitz they can muster. It’s akin to prepping for prom night or your wedding day. The catch? The morning after the party and all the days leading up to it, when your bank account keeps dwindling. You have to strike a balance between the extravagance of a Vera Wang dress and having enough left for shoes, cab fare, and yes, even food. So, how do you tackle this? First, compile a list of all features, and prioritize them with surgical precision. Embrace simplicity, and don’t fear the chopping block. It’s often easier to add than to overhaul a feature that’s already been released. Once your MVP is ready, release it to your eagerly waiting audience. Again, don’t forget to gather and scrutinize all the feedback. Remember, the release of the MVP is the ideal time to create a community around your product. But why, you ask? Simply put, your community serves as a real-time feedback machine, offering insights for improvement and validation of your product’s market fit. Plus, it cultivates customer loyalty, encouraging members to morph into your brand’s ambassadors. So, while you’re prepping your MVP for its big debut, start rallying your community around your product — it’s a step you won’t regret. So, take it from POC to MVP, but remember to tread cautiously. Your goal is to build a fantastic product, not to run out of resources before you reach the finish line.</li><li><strong>Oh, and last and not the least. Feature-by-feature development!</strong> Think of it as constructing a skyscraper, one floor at a time, versus trying to airlift the whole darn thing onto the plot. It’s about starting from ground zero and making incremental additions, not about attempting a big reveal and risking your entire investment. Once you’ve managed to convince your investors that you’re not just another startup chump and your product is worth their gold, you enter the phase of continuous improvement. Here’s where things get interesting, where you get to truly flex those creative muscles. Your best bet is to roll out your features slowly but surely, taking the tortoise’s approach rather than the hare’s. Why, you ask? Well, this method lets you adjust your course quickly if things start heading south. You get to gauge how your audience reacts to each feature, without betting the farm on a massive launch that might or might not hit the mark. Also, let’s not forget the cost of making a mistake when you’re pushing out one feature at a time is less cataclysmic than when you’ve sunk months into building out the whole kit and caboodle. You’ve got to develop a knack for ‘release, learn, iterate, and repeat.’ Don’t get stuck waiting for everything to be “perfect” because guess what? Perfection is a myth. You’re far better off releasing a feature, taking note of the reactions, and tweaking as necessary. The biggest selling point of this approach? It leaves room for learning, for adaption. You’re not just learning from the mistakes (and trust me, there will be plenty), but also from your victories. You’ve just launched a feature that’s the toast of the town? Fantastic! Why did it resonate with the users? How can you replicate this success in future features? And keep in mind, as long as your backlog is full of features waiting to see the light of day, your product is alive and kicking. Feedback, that crucial lifeline, keeps it thriving. So, listen to your customers. After all, they’re the ones running the show.</li></ol><p>Alright, it’s time to recap this whirlwind of a journey we’ve been on. Picture this — you’re invited to a Brit Milah party, battling with ridiculously priced baby items for a present. It’s enough to make you long for the clarity of the stock market. Now, isn’t it hilarious that we break a sweat over such trivial decisions, yet we march into the startup world with all the confidence of a peacock?</p><p>Brace yourself for the truth bomb — your chances of getting it right on the first try are slimmer than bumping into a unicorn on your morning run. If you think your idea is a surefire hit, you might as well sink that money into the ocean and take a much-needed vacation.</p><p>However, if you’re still ready to take the plunge, let’s dive into the world of startups. Our journey begins with the idea-to-POC phase, testing the waters before jumping in. Next, we navigate the treacherous journey from POC to MVP, careful not to release too much too soon. Remember, not all features are created equal.</p><p>As we progress, we build a community of loyal followers to provide invaluable feedback. This feedback helps us refine our product and make it resonate with our target audience.</p><p>Finally, we dive into feature-by-feature development, a slow and steady process that gives us the flexibility to adapt based on customer response. It’s all about learning from your successes and failures, and never losing sight of the fact that your customers are the ones pulling the strings.</p><p>So, there you have it. A brief overview of the wild ride that is launching a startup. <strong>Remember, you’re not just building a product, but a community. The feedback from your users is what keeps your product alive. So listen, learn, iterate, and repeat. After all, perfection is a myth — and those who chase it are doomed to run forever.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1503aa338b84" width="1" height="1" alt=""><hr><p><a href="https://medium.com/agileinsider/startups-unzipped-a-merry-go-round-of-feedback-frenzy-1503aa338b84">Startups Unzipped: A Merry-go-round of Feedback Frenzy</a> was originally published in <a href="https://medium.com/agileinsider">Agile Insider</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Syncing Ship: A Tongue-in-Cheek Look at Designers Dancing with Code]]></title>
            <link>https://medium.com/design-bootcamp/the-syncing-ship-a-tongue-in-cheek-look-at-designers-dancing-with-code-758c97e4aa4e?source=rss-ae8f7209f9b5------2</link>
            <guid isPermaLink="false">https://medium.com/p/758c97e4aa4e</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Startup Reality Check]]></dc:creator>
            <pubDate>Sun, 16 Jul 2023 23:50:28 GMT</pubDate>
            <atom:updated>2023-07-18T01:16:09.969Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6-feBs245nvCOrQzAG5EzA.png" /></figure><p>Ah, the delightful rendezvous of the Retrospective! Last Friday marked the birth of this captivating event for a team so fresh, they practically had “Hello, World!” written on their foreheads. Their mission? Tackling super critical features for an early-stage startup, because who needs a stress-free life, right? With a whopping two weeks of teamwork experience, they ventured into the realm of old, typical questions. One notable mention goes to Woodward, the valiant member of the engineering word delivery team, with their tales of not-so-well accomplishments. Amidst the shared feedback and ideas, it was time for the designers to grace us with their presence. And lo and behold, they seemed unsure whether to share their profound wisdom. “Should I even bother?” they pondered, questioning their existence in this code-less, test-less, meaning-less world. My, oh my, it was a delightful revelation that the company had unwittingly woven a tapestry of odd culture, casting designers into the shadows. So today, dear readers, let’s embark on a whimsical journey to discuss the pressing question: Should UX/UI designers be considered part of the delivery team? And fear not, for we shall explore smaller subplots within this grand tale: Shall we gather designers as a separate team and have them pass their magnificent results to developers? And what sorcery is required to gracefully manage multiple delivery teams and designers? Come along, my fellow adventurers, as we unravel the mysteries that lie before us.</p><p>Welcome, brave souls, to the magical realm of breaking down broad topics into digestible morsels! Our journey today is packed with twists and turns that teeter on the edge of irony. The first conundrum we’ll grapple with is this: Should UX/UI designers be considered part of the engineering team? As we delve into this enigma, we’ll also mull over whether designers should form a distinct collective, entrusting their creations to developers like classified missives. And as if this wasn’t enough to whet your appetite, we’ll delve into the uncharted waters of UX stepping into the shoes of product management during those grim times when a product owner is nowhere to be found. Strap yourselves in, for we’re about to embark on a thrilling adventure, packed with quickfire answers, detailed explanations, and some truly mind-bending corner cases. Ready to dive into the rabbit hole? Then let’s get started, my intrepid companions!</p><h3>Should UX/UI Designers be Part of the Engineering Team?</h3><p>Oh, undoubtedly! Who dares claim that engineering is solely the realm of developers, QAs, and the occasional DevOps whisperer? Such a belief is simply archaic! Consider this scenario: a product manager, the veritable idea factory, is isolated from the engineering team. How, pray tell, is the team supposed to deliver exactly what the market and the product demand? It’s akin to existing in parallel universes, each oblivious to the other’s needs. But fear not, for our UX/UI designers are here to save the day! They serve as the vital bridge between the product visionaries and the engineering foot soldiers. The product manager conceives a groundbreaking idea, a rough sketch on paper or in the form of nebulous requirements. This seed of an idea is then handed to the designers, who use their alchemy to transmute it into a visually stunning and functional marvel. But here’s the rub: designers must always bear in mind the constraints of the system and the time restrictions of the engineering team. It’s a fine dance of collaboration, designed to stave off unnecessary revisions. Thus, the inclusion of UX/UI designers in the engineering dream team is not only logical but necessary.</p><p><strong>However, there’s a corner case to consider! </strong>Imagine a scenario where multiple engineering teams are vying for the attention of a single, beleaguered designer. Oh, the horror! The lone designer would be overwhelmed, drowning in a sea of responsibilities. But fear not, for hard choices will have to be made. The designer’s time will need to be judiciously divided, with biweekly meetings with each team, active participation in planning sessions, and a presence at all crucial review meetings. It’s a juggling act, a delicate balancing act to ensure the team’s efforts align with the designer’s initial vision. So, chin up, lone designer, for your trials and tribulations are truly epic!</p><h3>Should Designers Gather as a Separate Team, Passing Results to Developers?</h3><p>Ah, the sweet seduction of separation! It can indeed be alluring to house designers in a separate team, especially when you have multiple engineering teams and a brood of designers working their magic. Each team could have its own processes, its own modus operandi. But here’s the twist: there still needs to be synergy, especially if they’re working on the same product. Envision different teams slaving away on distinct features of the same illustrious product. Without synchronization, chaos would ensue, with each feature appearing disjointed and unrelated, much like distant relatives at a family gathering. Not quite the harmony we’re aiming for! So, to ensure a consistent user experience and avoid befuddling the users, designers must regularly sync, communicate, and align their efforts. They may not need separate processes, but they should have the opportunity to collaborate and ensure a cohesive final product. It’s akin to a ballet, a harmonious dance of design collaboration.</p><h3>Can UX Act as a Product in the Absence of a Product Owner?</h3><p>Ah, the question of whether UX can don the product mantle! The answer is a mixed bag, my dear comrades. UX/UI designers indeed bring a wealth of creativity to the table, with brilliant insights into product flows and user expectations. However, they may lack the broader market perspective, in-depth user insights, or intricate financial knowledge. Thus, in the absence of a dedicated product owner, a robust marketing team can bridge this gap, providing crucial market insights. But this is merely a stop-gap arrangement. UX cannot replace a dedicated product owner in the long run. It’s akin to asking a shoemaker to double up as a tailor. An interesting concept, but not a sustainable solution, my friends.</p><p><strong>To sum it up, today’s journey took us through the fascinating world of UX/UI design in engineering teams.</strong> From their crucial role in bridging the gap between vision and reality to the importance of synchronizing their efforts, we traversed the thrilling landscape of collaboration. UX designers, when included in the engineering team, ensure a seamless translation of ideas into reality, preventing wasteful revisions. Whether gathered in separate teams or working on different products, synchronization and alignment remain key. And in the absence of a product owner, UX can step in temporarily, with a little help from a savvy marketing team. Stay tuned, for future articles will delve into the practical aspects of making all this a reality. The journey may be long, but the reward is well worth it, my friends!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=758c97e4aa4e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-syncing-ship-a-tongue-in-cheek-look-at-designers-dancing-with-code-758c97e4aa4e">The Syncing Ship: A Tongue-in-Cheek Look at Designers Dancing with Code</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[Bug Off: A Non-Techie’s Guide to the Importance of Testing]]></title>
            <link>https://medium.com/design-bootcamp/bug-off-a-non-techies-guide-to-the-importance-of-testing-8d8b7ef0e426?source=rss-ae8f7209f9b5------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d8b7ef0e426</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[startup-life]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Startup Reality Check]]></dc:creator>
            <pubDate>Tue, 13 Jun 2023 19:28:51 GMT</pubDate>
            <atom:updated>2023-06-14T06:37:38.985Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ml5fMuSHXFgxMP_n23nHIw.png" /></figure><p>Ah, the sweet, intoxicating aroma of self-promotion. Can’t get enough of it, really.</p><p>Recently, I somehow found myself whisked off to some flashy gathering — apparently, being “socially active” is good for it can’t be that bad, can it? Now, imagine a hodgepodge of hoodies and Armanis, startup geeks and deep-pocketed investors, all in one room. What a splendid opportunity for a little hype, eh?</p><p>Here’s my go-to list of questions — watch as their faces shift from smug to stupefied:</p><ol><li>Do you actually? Need a front-line product manager? What’s you say?</li><li>Release frequency — Are you sure that leisurely pace of yours gives you enough wiggle room to pivot, should the need arise?</li><li>Speaking of pivots, you’ll never have to do one, right? Of course not. How naive of me.</li><li>Tests? Who needs those? They’re overrated anyway, aren’t they?</li></ol><p>Ah, the joy of it all…</p><p>Now, despite my penchant for all these enlightening topics, let’s bring on the star of today’s show: Tests!</p><p>Bored by bugs? Desperate for a dream software? Time to dip into the refreshing waters of software testing. Don’t switch off just yet, I promise I’ll keep the jargon to a minimum.</p><ol><li><strong>Test Now, Save Later: </strong>Imagine throwing a party without checking whether you have enough food or drink. Disaster, right? Similarly, failing to test software is like opening the doors to a bug-infested funfair. No one wants to play those games. Testing early is like investing in insurance — you might not love the upfront cost, but you’ll be grateful when disaster strikes and you’re covered.</li><li><strong>Faster Than A Caffeinated Cheetah:</strong> With testing, developers can transform their code with all the confidence of a runway model in Paris. This means no more tiptoeing around code, but rather sprinting through improvements. And when it comes to startups, time is as rare and as valuable as a hen’s teeth.</li><li><strong>Satisfying Your Audience:</strong> Let’s be honest, customers don’t appreciate software that crashes more than a newbie at a skating rink. Regular testing leads to happier customers, and happier customers lead to more referrals. A win-win if ever there was one.</li></ol><p>Ever heard the phrase “If it ain’t broke, don’t fix it?” Well, when it comes to untested software, we can guarantee it’s going to be broken. And guess what, you’ll be fixing it alright. Not just fixing it, but probably doing a full reconstruction. Say goodbye to your precious resources, and wave hello to the monster of inefficiency.</p><p>Don’t let the term ‘quality’ lull you into a deep sleep. It’s not as dull as it sounds. Imagine the horror of burning your resources on endless bug fixes or the terror of your active users dropping like flies due to an annoying software experience. Now, that’s a scary movie.</p><p>However, I’m not here to sell testing as the magical potion that cures all software woes. Quality is built on strong foundations — the requirements. If the requirements are as clear as a foggy day in London, your final product will reflect that.</p><p>So, you get it. Testing is a necessity. Weave it into your procedures, and if you’re feeling overwhelmed, call upon the power of AI. AI has tools like ChatGPT that can support you in creating user stories, acceptance criteria, and end-to-end test scenarios.</p><p>Don’t let your eyes glaze over, let’s demystify these terms with a party analogy. User stories are like your party plans — “As a host, I want a rocking DJ so that my guests will dance all night.” Similarly, acceptance criteria are your conditions for a successful party — maybe the DJ must play 80s pop and no country music, who knows?</p><p>The same goes for software development. User stories describe what the software should do from a user’s perspective, and acceptance criteria define the conditions for a successful user story. With AI, you can generate these based on data and user behavior. Now, isn’t that a party trick?</p><p>But wait, there’s more. End-to-end test scenarios are your party’s blueprint. It outlines the entire process, from sending out invites to waving goodbye to your last guest. In software, it’s a step-by-step guide of how the whole system should work together, and AI can help you craft it.</p><p>So, who’s doing the testing? Initially, it might be your QA engineer. But with the scenarios created by ChatGPT, you can test everything step-by-step. Perhaps in the future, AI can take care of the entire testing phase while you sit back and sip your margarita.</p><p>That’s enough chatter about testing for now. Next time, we’ll navigate the treacherous waters of maintaining focus during product development. Stay tuned to avoid creating a monster product that’s all over the place and impresses no one. Until then, keep those bugs at bay!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d8b7ef0e426" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/bug-off-a-non-techies-guide-to-the-importance-of-testing-8d8b7ef0e426">Bug Off: A Non-Techie’s Guide to the Importance of Testing</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[Augmented Product Management: A Founder’s Guide to Harnessing AI]]></title>
            <link>https://medium.com/design-bootcamp/augmented-product-management-a-founders-guide-to-harnessing-ai-dee24a42ba0?source=rss-ae8f7209f9b5------2</link>
            <guid isPermaLink="false">https://medium.com/p/dee24a42ba0</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[startup-life]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Startup Reality Check]]></dc:creator>
            <pubDate>Fri, 19 May 2023 19:21:09 GMT</pubDate>
            <atom:updated>2023-05-20T01:32:03.264Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KHAttv2jiGtP4P2jQGY-kg.png" /></figure><p>Let’s get a little carried away, shall we? Can the mighty ChatGPT replace product managers or owners? Drum roll, please… No, not quite. But fear not, fellow Founders, because it can still lend a significant hand in shaping your product. Intrigued? Let’s unfold this digital mystery together.</p><p>So, you’re a hot-off-the-press Founder, with a team of engineers at your disposal and even a sprinkle of initial investment. You’ve got grand ideas and even grander aspirations, but alas, no product manager in sight. What’s a Founder to do?</p><p>The urge to panic may be strong, but hold your horses! Dumping your vision onto your engineers with a shrug and a “figure it out” might seem tempting, but let’s face it, that’s a Hail Mary at best. Your engineers are already juggling enough tasks — asking them to put on a product manager hat as well might just be the straw that breaks the camel’s back.</p><p>But, what if I told you there’s a way around this conundrum? Enter stage right, ChatGPT. With a little finesse and the right questions, this AI tool could help you carve out requirements in a way your engineers will appreciate.</p><p>But first, a brief history lesson. Remember when we first learned to use search engines? The struggle was real. But with practice, we got better. The same rule applies to using ChatGPT.</p><p><strong>Let’s explore a few scenarios where ChatGPT might be your secret weapon:</strong></p><ol><li><strong>Creating a to-do list (Product Backlog): </strong>Think of your product as a house you’re building. Each feature is a room, and you need to plan what goes into each room. This is where ChatGPT comes in. It can help you create a list of “User Stories”, which are essentially your blueprints for each room. In non-tech terms, a User Story is just a simple description of what you want a particular part of your product (a room in your house) to do, from the perspective of the person who will use it (live in the room). It’s like saying, “As the owner of the house, I want a big kitchen with a view, so that I can enjoy cooking while looking at the scenery.” However, ChatGPT isn’t a mind reader. It might not remember all the different types of people who will use your product, like registered users or admins. And the User Stories it generates might lack some important details, which could lead to misunderstandings later on. To avoid this, give ChatGPT as much information as you can about what you want in your house. The more details you provide, the better it can help you plan.</li><li><strong>Now, let’s talk about the role of ChatGPT in defining your MVP, or “Minimum Viable Product.”</strong> If this term sounds foreign, allow me to simplify it. In the realm of startups, an MVP is essentially the debut performance of your product. It’s a stripped-down version of your grand vision, containing just enough features to be functional and appealing to your potential customers. Think of it as the exciting teaser trailer that gets everyone talking before the full-length blockbuster hits the screens. However, don’t let AI be your only director for this show. As a Founder, it’s crucial for you to stay alert and use your common sense. Remember, ChatGPT is a tool providing guidance and sparking ideas, not a fortune teller predicting the perfect solution. You must bring your own critical thinking to the table and make the final decisions. After all, it’s your vision that’s being brought to life.</li><li><strong>Moving on to setting priorities.</strong> Just as every successful movie has a well-structured plot, every successful product needs a clear set of priorities. Without them, you’re essentially sailing a ship in the fog, with no idea which direction leads to your destination. You could have a whole treasure chest of brilliant ideas, but without knowing which ones are the most crucial, you might waste time and resources on less essential features. Here again, ChatGPT can be your trusty first mate, helping you navigate and decide which features are absolutely essential for your product’s initial launch and which ones can wait for the sequel. But remember, even the best first mate doesn’t replace a captain’s judgment. Use ChatGPT as a guiding compass, but remember that the final decisions lie in your hands. Because at the end of the day, it’s your ship to sail.</li><li><strong>If you’re feeling adventurous, ChatGPT could even assist in creating what we in the biz call “Use Cases” and “User Flow Scenarios.” </strong>Now, don’t let those jargons scare you. A Use Case is just a fancy term for a more detailed story of how someone might interact with your product to accomplish something specific. Picture it like a script for a play where the user and the system are the main characters.On the other hand, User Flow Scenarios are like treasure maps of a user’s adventure through your product. They guide us from the first “X marks the spot” (where a user starts interacting with your product) to the grand treasure chest at the end (the final result of their interaction).In other words, these are just tools to help you visualize and plan how your product will be used, ensuring a smooth and enjoyable experience for your users.</li></ol><blockquote><strong>Now, before you get too carried away, remember to tread lightly with sensitive data. ChatGPT isn’t Fort Knox, and you don’t want a data breach on your hands.</strong></blockquote><p><strong>Ready for a recap? Let’s revisit our rollercoaster of a journey together.</strong></p><p>In our quest to replace product managers with ChatGPT, we discovered a resounding, drum-rolling “No.” But wait, it’s not a dead-end! Think of ChatGPT as a trusty sidekick rather than the hero of the product development saga.</p><p>As a fresh Founder, you don’t need a product manager to interpret your vision to your engineers. You have ChatGPT. It’s like the search engine of yesteryears — learn to ask the right questions and you’ve got yourself a goldmine.</p><p>ChatGPT can churn out User Stories for your product — simple narratives that outline a feature from the user’s viewpoint. But remember, you need to spoon-feed it with details, or you’ll end up with broad, generic stories.</p><p>Next up, we explored the fascinating world of MVPs, or “Minimum Viable Products”. It’s your product’s debut, with just enough features to make potential customers sit up and take notice. While ChatGPT can suggest ideas, you, dear Founder, must make the final call. Your judgment is key.</p><p>We also navigated the tricky waters of setting priorities. Without them, you’re essentially a captain lost at sea. ChatGPT can be your compass, but you are the one steering the ship.</p><p>Feeling adventurous? You could even use ChatGPT to create Use Cases and User Flow Scenarios. These are essentially detailed scripts and maps of how users might interact with your product, helping you plan for a smooth and enjoyable user experience.</p><p>But, just as every adventure has its dangers, remember to tread lightly with sensitive data. Because while ChatGPT can be a trusty sidekick, it’s not a secure vault for your confidential information.</p><p>So there you have it, Founders. While ChatGPT may not replace your product manager, it can certainly be a game-changing ally in your quest for product success. But remember, it’s only a tool. The final decisions, the judgment calls, and the responsibility — all of that still lies with you. After all, it’s your vision, your product, and your success story waiting to be written.</p><p><strong>If you’re curious about testing types and their importance, or how they can be created using ChatGPT, do leave a comment. And remember, if a task can be accomplished by AI, why waste your precious time doing it manually? Stay tuned for more insights!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dee24a42ba0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/augmented-product-management-a-founders-guide-to-harnessing-ai-dee24a42ba0">Augmented Product Management: A Founder’s Guide to Harnessing AI</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[Lost in Translation: The Communication Challenge of Teams]]></title>
            <link>https://medium.com/design-bootcamp/lost-in-translation-the-communication-challenge-of-teams-3d3a1e11fcce?source=rss-ae8f7209f9b5------2</link>
            <guid isPermaLink="false">https://medium.com/p/3d3a1e11fcce</guid>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Startup Reality Check]]></dc:creator>
            <pubDate>Mon, 08 May 2023 14:00:59 GMT</pubDate>
            <atom:updated>2023-05-09T05:53:56.198Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3wQwoZcdcZQCsENkKqR13Q.png" /></figure><p>Oh, you think you can handle everything on your own and your team works in a vacuum? How adorable, you pure little baby. Let me break it to you — you can’t.</p><p>Remember the game of broken telephone? The more people in the chain, the funnier and more twisted the message became at the end. It’s hilarious if it’s just a game, but not so much if you’re a founder trying to build a product. And let’s add to that a generous helping of delays in communication. If your team has more than seven people, a lot of stuff is going to get lost in translation.</p><p>Can you avoid this challenge? Sorry, there’s no way. People will always be people. Unless you want to create a perfect robotic world, hello Skynet. Until then, what you can do is create an environment where team members feel like they’re building something meaningful together, like the story of building a temple, not just carrying stones.</p><p>If people feel like they belong to something, they’ll naturally try to make it the best it can be. After all, the product is their child and a source of pride. Does that mean conflicts, misunderstandings, or mistakes won’t happen? Of course not! But at least you’ll know right away, and you’ll have the time, money, and passion to make it right. Plus, emergent ideas and solutions will come up that you never would have thought of on your own.</p><p>Sounds great, right? So, how do you get there? Well, savvy leaders recognize the benefit of going slow to go fast. Take the time to make sure everyone understands the purpose and nature of the work. Help everyone learn, think, and make decisions together. That way, instead of feeling blocked or dependent on someone else’s decision, people use their knowledge to create shared emergent solutions.</p><p>To make it happen, you’ll need to share the purpose and meaning of the work with the team, help everyone get to know each other’s strengths and weaknesses and find the best ways to communicate and achieve the purpose. And don’t forget to put the team in context.</p><p>Oh boy, let’s get real deep into the nitty-gritty details, shall we?</p><p><strong>Purpose</strong>, purpose, purpose — that’s what we’re here to talk about, folks. You know, that elusive thing that gives your work meaning and makes it worth doing? It’s what brings value to your life and work.</p><blockquote>In his book, <strong>Drive: The surprising truth about what motivates us</strong>, Daniel Pink calls out autonomy, mastery, and purpose as the three primary human motivators.</blockquote><p>So, if you want to get your team pumped up and ready to go, you better have a clear understanding of your purpose.</p><p>And how do you communicate this purpose, you ask? Well, it’s simple really. Just use your mouth! But make sure to add every possible detail in your speech and focus on answering the all-important question: how the heck will we know if we’re successful? And don’t forget to provide your team with specific metrics to track, like those numbers you’ll see even in your wildest dreams. It’s like writers obsessing over their followers and views — you’ll be checking those stats like a madman.</p><p>But wait, there’s more! Empower your team to bridge the gap between lofty ideas and tangible tasks with collaborative requirements, and raise the bar even higher by leveraging the awe-inspiring technique of <a href="https://www.amazon.com/User-Story-Mapping-Discover-Product/dp/1491904909">StoryMapping</a>.</p><p>Oh, and one last thing — consistency is key, people. You can’t just share your purpose once and call it a day. Your product is alive and constantly changing with the market and environment, and so should your purpose. So don’t forget to keep your team in the loop with all the updates and changes. After all, sharing is caring.</p><p><strong>Team alignment: </strong>Oh boy, let’s talk about effective team alignment. Aren’t you excited? I know I am. We’re gonna build a coherent core team, people! And how do we do that, you ask? Simple. We just need some rules to guide us.</p><p>Take the example of this one team I worked with. Their main rule was “quality is our main goal”. And let me tell you, they were so proud of it. They spent all their time building new stuff and hardly any time fixing bugs. And even when they were moving fast, they never sacrificed quality. I mean, who needs a product that actually works when you can have a shiny new feature, right?</p><p>But it’s not just about the rules, people. We also need some working agreements. Make sure everyone is on board and values diversity and respecting boundaries. Then, it’s time to get real and have some open and honest discussions about what really matters. You know, things like how to communicate, when to communicate, and what your work-life balance is going to look like. Once you’ve got all that sorted out, you’ll be unstoppable! Your team will be able to handle anything that comes its way with ease.</p><p><strong>Context: </strong>Oh, so you and your team already have a shared understanding of the common purpose and you’re actually working together? Congratulations, you’re halfway there! But wait, there’s more! You also need to consider the real-world context. How much time, budget, workspace, and tools do you have? And how much more do you need? What limitations does your team have to deal with? Do you need to interact with other people like subject matter experts, marketing teams, or architects? And how should you even do that?</p><p>Let me tell you a story to give you a sense of how important context can be. Remember the <a href="https://www.simscale.com/blog/nasa-mars-climate-orbiter-metric/">Mars Climate Orbiter</a>? Yeah, that very expensive NASA mistake was caused by a difference in units of measurement systems (imperial and metric). In all the documents, the measurement units were marked “by default,” but apparently, Europe and the United States have different defaults. Oops!</p><p>So, don’t forget to speak up and put your ideas into context to avoid losing anything in translation. Because trust me, you don’t want to be the next NASA.</p><p>Building a successful product requires more than just technical expertise and hard work. It requires effective team communication and alignment, a shared understanding of purpose, and an awareness of the real-world context in which the product is being built. By creating an environment where team members feel like they’re building something meaningful together and by taking the time to ensure everyone understands the purpose and nature of the work, leaders can foster emergent ideas and solutions that can take the product to the next level. So, let’s start by sharing the purpose and meaning of the work with the team, helping everyone get to know each other’s strengths and weaknesses, and finding the best ways to communicate and achieve the purpose. And don’t forget to put the team in context, as it’s important to consider the real-world limitations and opportunities that can impact the success of the product.</p><p>Connect the dots, create an amazing team, and enjoy and happiness of each and every day working together, solving complex issues, creating new ways and approaches, and growing together.</p><p>Keep yourself updated on upcoming topics, and don’t forget to engage with me by liking, sharing, and subscribing. It’s all part of the wonderful magic!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d3a1e11fcce" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/lost-in-translation-the-communication-challenge-of-teams-3d3a1e11fcce">Lost in Translation: The Communication Challenge of Teams</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[The Founder’s Guide to Product Management: Don’t Just Hope for Success, Validate It]]></title>
            <link>https://medium.com/design-bootcamp/the-founders-guide-to-product-management-don-t-just-hope-for-success-validate-it-aa97c414cc72?source=rss-ae8f7209f9b5------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa97c414cc72</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[startup-life]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Startup Reality Check]]></dc:creator>
            <pubDate>Mon, 01 May 2023 23:07:37 GMT</pubDate>
            <atom:updated>2023-05-02T07:48:08.734Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LiJjUpYF4NLXzvSWpJuSNw.png" /></figure><p>Well, well, well, folks, it’s time to wrap up this oh-so-epic 3Vs article series with the most crucial and neglected component of product-related collaboration and description — <strong>Validation</strong>.</p><p>Product managers can effortlessly babble about the Vision, Mission, and all the blah-blah stuff. But ask them how they’ll know if they’ve accomplished their goals, and watch them stutter and sweat.</p><p>Why, you ask? Because it’s easier to spout off what and why you’re trying to do than to admit that all your ideas and features are just hypotheses. You’re merely hoping that they’ll cater to customer needs, but what if they don’t?</p><p>It’s tough to swallow the fact that your idea, if not entirely, then partially, is incorrect. In such a scenario, you’ll have to admit it publicly that you were wrong, which can be pretty scary.</p><p>But wait, there’s more! What’s even worse is realizing that you were wrong too late and that you’ve squandered all of your resources implementing the wrong concept. And now, you can’t pivot at all. Isn’t that just grand?</p><p>So, let’s start at the beginning, shall we? All your product ideas and vision are just assumptions until numbers back them up. You must ensure that your desired outcomes are achieved, whether it’s a customer satisfaction rate, an increase in daily active users, or revenue growth.</p><p>Keep these goals in mind while creating your vision and set of features, reflecting value. Make them a part of everything you share with your team to communicate better and foster a sense of belonging.</p><p>It also reduces the risks and wastage if something goes wrong. Fail fast, adapt, make a pivot, and keep moving forward.</p><p>Is it easy? Of course not! But if it were, every startup would be a success story, which we all know is not the case.</p><p>So, how do you set goals and validate them? Start with the easiest way — SMART goals:</p><ul><li><strong>Specific: </strong>your goal should be clear and concise, so you know what you’re aiming for. Typical questions you will need to address: “What do I want to accomplish? and Why is this goal important?”</li><li><strong>Measurable:</strong> set measurable goals so that you can track your progress and stay motivated.</li></ul><p>Numbers!!! Use them! Not just “more users/subscribers” — but “In 2 months after a feature release the number of subscriptions should increase by at least 25%” <br>Do you feel the difference?</p><ul><li><strong>Achievable:</strong> make sure your goal is realistic and attainable. You don’t want to set the bar too high and actually challenge yourself, do you? No, no, just make it easy enough so you can reach it without breaking a sweat. And who knows, maybe by setting such a low bar, you might actually stumble upon some overlooked opportunities or resources. Or maybe not. But hey, at least you didn’t try too hard, right?</li><li><strong>Relevant:</strong> ensure that your goal aligns with other relevant goals and matters to you.</li><li><strong>Time-bound: </strong>every goal needs a target date, so you have a deadline to work towards.</li></ul><p>Every goal needs a target date so that you have a deadline to focus on and something to work toward. You don’t have “all the time in the Universe” — you better fail fast and make it as much less painful and costly as possible. So, pick the shortest time range, within you actually will be able to see the difference or results and stick to it.</p><p>And for God’s sake, don’t forget to analyze those numbers and ideas afterward. They’re not just there to make you feel productive; they’re your map and compass. Use them correctly.</p><p>The SMART tool may not work perfectly for long-term strategic goal setting, but since we’re not there yet, we can relax and use simple, working tools. Aren’t we?</p><p>That’s it for the 3Vs series, folks. Hope you learned a thing or two. Next up, we’ll concentrate more on launching teams and communication. Stay tuned, or as they say, “like, share, subscribe.” Oops, sorry, wrong audience.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa97c414cc72" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-founders-guide-to-product-management-don-t-just-hope-for-success-validate-it-aa97c414cc72">The Founder’s Guide to Product Management: Don’t Just Hope for Success, Validate It</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[Stay Savage: The Mindset for True Craftsmanship and Success]]></title>
            <link>https://medium.com/design-bootcamp/stay-savage-the-mindset-for-true-craftsmanship-and-success-c9992aa91ea8?source=rss-ae8f7209f9b5------2</link>
            <guid isPermaLink="false">https://medium.com/p/c9992aa91ea8</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[startup-life]]></category>
            <dc:creator><![CDATA[Startup Reality Check]]></dc:creator>
            <pubDate>Tue, 25 Apr 2023 23:44:35 GMT</pubDate>
            <atom:updated>2023-04-27T05:17:23.399Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hOIGiiAQ5hcuB4f8cC_qyA.png" /></figure><blockquote><strong>I am the master of my fate,<br>I am the captain of my soul.</strong></blockquote><blockquote>“Invictus” by William Ernest Henley</blockquote><p>And yet another New York Times article telling us we can’t fake it until we make it anymore. Like we needed another reason to be depressed about the world. But hey, if you’re a founder who actually wants to do something meaningful instead of just making a quick buck, then you’re already ahead of the game. Unfortunately, it seems like the whole culture is just about faking it these days. Smile, lie, be braggy, explain loudly why you’re the best. Where’s the true craftsmanship? The deep, crazy, burning desire to change and improve things? It’s all gone, replaced by a bunch of posers trying to look good for the cameras.</p><p><strong>And why are we so afraid to be crazy and rebellious?</strong> Why do we keep accepting the same old rules over and over again? It’s time to break free and do something different.</p><p>Sure, building something can be scary. It’s a rollercoaster ride with plenty of ups and downs. But that’s just part of the journey. You’ll go from “I’ll change the world!” to “I probably sucked more than anyone in the history of kung fu. In the history of China. In the history of sucking!” and back again. But don’t worry, that’s ok. It’s instinct. It’s what makes us human. Don’t get me wrong: fear is normal and instinctual, created to save our lives. While success and wealth are desirable, start-ups aren’t all about that. If you just want money, Wall Street is waiting. However, Silicon Valley is all about the dream, at least I hope so…</p><p>So, what can we do? It’s simple. From one rebellious child to another: stay savage! What does that mean? Don’t give a damn about other people’s expectations, hopes, and dreams. It’s your world, your dream, and you’re the only one who’s responsible. Let’s go out there and kick some ass, being prepared for internal failure.</p><p>Try to minimize the damage from failures, learn, adapt, and move forward. And by learning, I mean not only from your mistakes but also from books, podcasts, blogs, and other people, every second of your life. Don’t be afraid to be highly selective; you don’t have time for generalities like “You need to have a strategy.” Focus on practical tools and ideas. Don’t be afraid to admit (first and foremost to yourself) “I’m bored! I’m confused! I don’t get it!”. That’s the only way to find the pearls of knowledge hidden in the ocean of sugarcoated news and information.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c9992aa91ea8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/stay-savage-the-mindset-for-true-craftsmanship-and-success-c9992aa91ea8">Stay Savage: The Mindset for True Craftsmanship and Success</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[The Founder’s Guide to Product Management: Don’t Mess Up the Product Side!]]></title>
            <link>https://medium.com/design-bootcamp/the-founders-guide-to-product-management-don-t-mess-up-the-product-side-a839b35745fb?source=rss-ae8f7209f9b5------2</link>
            <guid isPermaLink="false">https://medium.com/p/a839b35745fb</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[startup-life]]></category>
            <dc:creator><![CDATA[Startup Reality Check]]></dc:creator>
            <pubDate>Sat, 22 Apr 2023 01:51:29 GMT</pubDate>
            <atom:updated>2023-04-22T07:42:46.679Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SY8BSREisgtogI-ovOcieg.png" /></figure><p>Let’s do a quick recap of the previous article, shall we? As a Founder, you may have absolutely no experience as a Product Manager, but don’t worry, that’s totally okay. Just don’t make the mistake of thinking that the Product side of your business is not important. Because, you know, if you mess up on the Product side, your whole product could be doomed. No biggie, right?</p><p>So, the <strong>first thing you need to create is the Vision of the Product</strong>, which should be crystal clear, not just for Investors but for your whole team. It creates transparency and anchors everything in the process. But hey, without it, your product is just a ship lost at sea. No pressure, though.</p><p>And if you’re wondering how to create a Vision, well, go back and read the <a href="https://medium.com/@yaryna.hotlib/founders-build-your-product-like-a-pro-the-ultimate-basic-toolkit-ad118c0c3963">previous article</a>. It’s all in there. Tools, ideas, the whole shebang.</p><p>Now, assuming you’ve got your Vision sorted, and you’ve pitched it to your Investors and Team, and they’re all inspired and whatnot, it’s time to turn that Vision into a Strategy. You know, with details about features, priorities, and most importantly, an understanding of how much time you have to deliver those features to the market. Because time equals days nowadays if you’re lucky.</p><blockquote>Oh, and by the way, if you’re one of those people who think that a product should be built completely, perfect, and golden before it’s released, well, bless your heart. Newsflash: you don’t know for sure that a particular feature is required and being waited by the Market. And things tend to change with time. Yesterday you were the only one with this idea, and today your competitor launched already and people love it. Oopsie.</blockquote><h3>Anyway, getting back to Value — what is that, you ask?</h3><p>Well, I hope for you it’s not just part of the “Mission, Vision, Values” trio. Because in our case, Value is all about the features and functionality of your Product focused on addressing Customer needs. Remember when you created that Vision? It was all about Customer needs.</p><p><strong>Vision addresses the questions: </strong>What and Why Customer want/need?</p><p><strong>Value addresses the question: </strong>How exactly will the Customer get what they need with the help of our Product?<strong> </strong>In details! Let me be even more specific: Value addresses the question: How <strong>exactly</strong> will the Customer get what they need?</p><p>Now you need to translate somehow understanding of what exactly should be done and how to your engineering team. Best way to do that — through Requirements. You absolutely need them. A bit more details of why you may find <a href="https://medium.com/@yaryna.hotlib/why-your-killer-idea-isnt-enough-the-importance-of-requirements-for-startups-817452f11a1d">here</a></p><p>In order to create a set of Requirements you have to analyze a lot. Like, seriously, a lot. Business case, industry and competition analysis, product launch strategy, investors’ requests, marketing strategy, User Flow, and many other pieces of information. The more, the merrier.</p><p><strong>So, you take all of that, mix but do not shake, turn it into requirements, put priorities, and voila — you made it.</strong> Oh, and don’t forget about those priorities. Everything is important, but if you don’t put priorities, then nothing is important. And we don’t want that, do we?</p><p>Priorities will allow your team can focus on the most important things. Without proper prioritization, your engineering team may waste time on features that aren’t critical to your product’s success.</p><p>When it comes to delivering value to your customers, the only way to do it is by releasing your product. Don’t wait until it’s perfect — release it as soon as you can. And don’t you dare think that your idea is perfect from the scratch or that you can read someone’s mind? Release, get feedback, adapt, become better. Release again. And again.</p><h3>While you’re releasing, your product is alive!</h3><p>As we wrap up the Value section, let’s remember what we’ve learned: apparently, your product’s value lies in how well it can cater to the demands of your customers. But don’t just stop there! Turn that value into requirements and prioritize them (because who doesn’t love a good list?). And don’t waste time perfecting everything, just release it ASAP and gather feedback until you’re blue in the face. Because, let’s face it, the real value of your product only comes from releasing it.</p><p>But wait, there’s more! This is just the second part of a three-part series on the 3V methodology. There’s one more section left: Validation. Can you even contain your excitement?! Stay tuned to find out how to validate your product, and maybe, just maybe, you’ll become the next Steve Jobs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a839b35745fb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-founders-guide-to-product-management-don-t-mess-up-the-product-side-a839b35745fb">The Founder’s Guide to Product Management: Don’t Mess Up the Product Side!</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[The Founder’s Guide to Product Management: How to Look Like You Know What You’re Doing]]></title>
            <link>https://medium.com/design-bootcamp/founders-build-your-product-like-a-pro-the-ultimate-basic-toolkit-ad118c0c3963?source=rss-ae8f7209f9b5------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad118c0c3963</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup-life]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Startup Reality Check]]></dc:creator>
            <pubDate>Thu, 20 Apr 2023 21:27:23 GMT</pubDate>
            <atom:updated>2023-05-01T23:08:38.767Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yiMt1ATQ0JyUVsemK05KpQ.png" /></figure><p>Oh boy, do I have a treat for you, dear startup Founder. Are you ready for some life-changing, game-breaking advice on Product Management? Well, you better buckle up because I’m about to blow your mind.</p><p>As a Founder, you may not have any experience as a Product Manager, and that’s okay. But don’t make the mistake of thinking that the Product side of your business is not important. <strong>In fact, if you mess up on the Product side, your entire product could be doomed.</strong></p><p>First of all, let me tell you that there are a gazillion tools out there that are just oh-so-nice, important, and useful for Product Management. But, hey, not all of them are meant for you, you dear startup Founder. Don’t get too excited and start using everything at once, or you’ll end up burning through your money, energy, and passion faster than you can say “Product Manager.”</p><p>I mean, come on, let’s be real here. You’re a Founder, not a Product Manager. You probably don’t have a clue about half of the things you’re supposed to be doing. But don’t worry, I got your back.</p><h3><strong>Let me introduce you to the 3Vs concept: Vision, Value, and Validation.</strong></h3><p>In this series of articles, I’ll break down each “V” and give you some tips on which parts of the series will be most useful for you. But don’t just read them once — read them twice, thrice, until it’s drilled into your skull.</p><p><a href="https://medium.com/@yaryna.hotlib/the-founders-guide-to-product-management-don-t-mess-up-the-product-side-a839b35745fb"><strong>Second article, about Value also was published</strong></a></p><p><a href="https://medium.com/@yaryna.hotlib/the-founders-guide-to-product-management-don-t-just-hope-for-success-validate-it-aa97c414cc72"><strong>Third article: Validation</strong></a></p><h3><strong>Let’s start with Vision</strong></h3><p>Listen up, Founder, if you don’t have a clear Vision, you might as well be trying to sell ice to Eskimos. Your Vision should be crystal clear, not just for Investors but for your whole team. It creates transparency and anchors everything in the process. Without it, your product is just a ship lost at sea.</p><p>And no, your Vision isn’t just some elevator pitch for investors. It’s the key to understanding why your product exists and what problem it solves for your target audience. Don’t be greedy and try to please everyone. Stay focused on a single target customer and a single value proposition, or you’ll end up making chairs today and baking cookies tomorrow. <strong>Stick to your target audience and their pain points, and you’ll be golden.</strong></p><p>Now, I know you’re probably thinking, “But how do I create a Vision? I have no clue how to do that properly.” But don’t worry, I won’t leave you high and dry. I’ve got a cool template to help you create your Vision.</p><p>Just fill in the blanks:</p><p><strong>For [target audience], who [need, want, have to]. Our Product is a [help, service, game changer] that [one key benefit] unlike [competitors current situation] we can [unfair competitive advantage]</strong></p><p>I understand that it can seem both straightforward and daunting at the same time, but let me assure you that it’s not as intimidating as it appears. To give you an idea, imagine my product as a line of ceramic coffee mugs called CoffeeDream.</p><p>So, if I had to pitch CoffeeDream in an elevator, it would go something like this:</p><blockquote>“Are you a coffee lover who can’t start the day without a hot cup of coffee? CoffeeDream is the solution you’ve been looking for! Our innovative mug keeps your coffee at the perfect temperature without burning your hands. Unlike other mugs on the market, CoffeeDream combines functionality with stunning design, crafted by the most talented young artists. Experience the ultimate coffee-drinking pleasure with CoffeeDream”</blockquote><p>You may say: well, ha anyone can write something like that for coffee mugs. But how can I do something like that for my Product?</p><p><strong>Don’t worry, dear Founder. I have just the tools you need. They are straightforward, user-friendly, and require minimal instruction.</strong></p><ol><li><a href="https://medium.com/@steve_mullen/an-introduction-to-lean-canvas-5c17c469d3e0"><strong>The Lean Startup Canvas</strong></a><strong> </strong>is a powerful tool that can help you create a clear and concise vision for your startup, as well as identify and test your assumptions, revenue streams, and many more</li><li><a href="https://medium.com/the-xplane-collection/updated-empathy-map-canvas-46df22df3c8a"><strong>Empathy Map</strong></a> is a powerful tool that enables you to truly understand your users and their needs, leading to a superior user experience. By creating a vivid picture of your user’s journey, you can ensure that every touchpoint with your product is optimized for maximum impact. Your UX/UI lead will be thrilled with the insights you uncover and the improvements you make to enhance the user experience.</li><li><a href="https://businessmodelanalyst.com/downloads/product-market-fit-canvas-template/"><strong>The Product-Market Fit Canvas</strong></a> is a lifesaver for those who have experienced the startup grind or are brave enough to dive in headfirst. Say goodbye to the pain of product-market misalignment with this powerful tool. It helps you analyze key metrics, features, user jobs, and characteristics while identifying market alternatives and user acquisition channels. Don’t let misalignment hold you back from success — use the Product-Market Fit Canvas to ensure your product is a perfect fit for your target market.</li></ol><p>But here’s the bottom line, my friend. Don’t be greedy. Turn your idea into a Vision and inspire the world to fall in love with your “child.” Then, and only then, can you start making some serious money. And all the tools and ideas I’ve shared with you today will help you achieve that goal.</p><p>And as for the pearls on the thread…stay tuned for the next article where we’ll explore how to add value to your product and take your vision to the next level.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad118c0c3963" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/founders-build-your-product-like-a-pro-the-ultimate-basic-toolkit-ad118c0c3963">The Founder’s Guide to Product Management: How to Look Like You Know What You’re Doing</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>
    </channel>
</rss>