<?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 Alison Renfro on Medium]]></title>
        <description><![CDATA[Stories by Alison Renfro on Medium]]></description>
        <link>https://medium.com/@alisonrenfro?source=rss-b0bc0ee7f65b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*591ZgC79qXBLgvWoxIXctQ.jpeg</url>
            <title>Stories by Alison Renfro on Medium</title>
            <link>https://medium.com/@alisonrenfro?source=rss-b0bc0ee7f65b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 03:11:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alisonrenfro/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[6 Rapid Prototyping Techniques To Develop Products Quickly]]></title>
            <link>https://medium.com/the-product-manager/6-rapid-prototyping-techniques-to-develop-products-quickly-b0b620c071be?source=rss-b0bc0ee7f65b------2</link>
            <guid isPermaLink="false">https://medium.com/p/b0b620c071be</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[rapid-prototyping]]></category>
            <dc:creator><![CDATA[Alison Renfro]]></dc:creator>
            <pubDate>Mon, 21 Dec 2020 23:00:02 GMT</pubDate>
            <atom:updated>2020-12-21T23:04:14.643Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/585/1*mhL_F5ufPzNsArCuSBlylw.png" /></figure><p>So you want to figure out how to validate your approach for a new feature or digital product?</p><p>In this day and age, searching for new methods and concepts for tackling rapid prototyping can bring back an incredible amount of information, and honestly, it can be pretty hard to parse through all of that information to find something that makes sense for <strong>your specific need</strong>.</p><p>Well, my friends, you’ve come to the right place. As a Digital Product Manager with 6 years of experience managing the lifecycle of building, testing, and iterating on technology, I’ve had my fair share of testing different rapid prototyping techniques across products.</p><p>During my time at Crema, I’ve learned how to hone-in on the best type of rapid prototyping techniques for a specific application, as well as when and where they apply best, and how to utilize them most effectively to find answers to the questions that are needed to build the best possible version of a product.</p><p>In this article, I’ll be sharing my 6 go-to rapid prototyping methods, and discussing how you can find the perfect technique that provides the fidelity you need.</p><p><a href="https://theproductmanager.com/topics/rapid-prototyping-techniques/#rpr">Rapid Prototyping Recap</a><br><a href="https://theproductmanager.com/topics/rapid-prototyping-techniques/#thlf">The High vs Low Fidelity Decision </a><br><a href="https://theproductmanager.com/topics/rapid-prototyping-techniques/#lfpt">Low Fidelity Prototyping Techniques</a><br><a href="https://theproductmanager.com/topics/rapid-prototyping-techniques/#hfp">High Fidelity Prototyping Techniques</a></p><h3>Rapid Prototyping Recap: What Is Rapid Prototyping?</h3><p><a href="https://www.cs.colostate.edu/~bieman/Pubs/GordonBieman93SQJ.pdf">Studies have shown</a> that “<em>prototyping helps ensure that the nucleus of a system is right, before the expenditure of resources for the development of the entire system.”</em></p><p>This of course, sounds like music to our product manager ears, particularly when there’s a focus on understanding if a new approach/tool is going to be worth the squeeze of building it.<br>So, what exactly is the rapid prototyping approach?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wls-5VKK_s8SMY6f.png" /></figure><p>Rapid prototyping is all about getting an idea in front of users, collecting feedback, and quickly refining and iterating your idea based on that feedback. It’s an indefinite loop, which should be utilized over and over until the team is satisfied with their validated approach.</p><h3>The Fidelity Decision: High Fidelity vs Low Fidelity</h3><p><strong>High Fidelity? Low Fidelity?…<em>What does it all mean?</em></strong></p><p>The first thing we need to fully understand in order to determine which types of rapid prototyping will work best for your prototype is the level of fidelity.</p><p>Both high and low fidelity prototyping approaches are incredibly beneficial, but their individual impact will greatly depend on whether they’re implemented at the right time.</p><p>InVision, an industry leader in high fidelity prototyping software and iterative design process thinking, also<a href="https://www.invisionapp.com/inside-design/low-fi-vs-hi-fi-prototyping/"> recognizes and encourages people to understand the differences between the approaches</a>:</p><p><em>“Prototyping at the wrong fidelity is one of the top prototyping mistakes. Unfortunately, there isn’t a one-size-fits-all solution. Instead, you should evaluate it based on each individual scenario.”</em></p><h3>Low Fidelity Prototypes</h3><p>These are low-cost, easily attainable, and great for new projects or ideas that need to be validated or invalidated by multiple stakeholders. This type of approach is useful for those who may not have immediate access to resources for design and/or development.</p><h3>High Fidelity Prototypes</h3><p>These are higher in cost since they can utilize development/design resources, but high fidelity prototypes allow for a more real-life experience for users to provide feedback on. This type of approach is great for projects that want to better understand a specific experience, test new ideas and workflows, or better validate/invalidate overall functionality and purpose.</p><h3>Low Fidelity Prototype Techniques</h3><h3>1. Pen &amp; Paper</h3><p>As one of the most adaptable and widely used techniques, the good ‘ole pen &amp; paper process allows individuals to collaborate using what they have on hand (pen and paper) to source ideas and concepts from as many people as possible.</p><p>Pen and paper can be an incredibly effective way to communicate ideas to your team and stakeholders, without conducting a larger session.</p><p>Here are a few example circumstances where a pen &amp; paper technique might be applied:</p><ul><li>A customer has requested a new feature for the product that your team has built. This feature has various ways of being implemented, and it seems like each team member has a different suggestion or idea for how it can be completed.</li><li>A client has a new idea for an application. This app is meant to serve and solve a specific problem or task for the end-user, or, there’s at least one focused user flow that needs to be clearly defined in order for the product to succeed.</li></ul><h4>How might you conduct this?</h4><p>The good news is that Pen &amp; Paper exercises are incredibly flexible, so consider what needs and constraints you may have, and feel free to adapt them to what best works for you. Below are a few steps you can take to get your groundwork in place:</p><ul><li>Gather necessary individuals into a room — stakeholders, application developers, end-users, designers, etc. This exercise is inclusive to all people, and requires only that you’re willing to participate!</li><li>Provide each person with paper and a pen, and describe the problem that is to be solved.</li><li>Place a timer (~10 minutes) and advise each person to visualize &amp; demonstrate how that problem might be solved.</li><li>Once the timer has expired, allow each individual to walk through their proposed solution.</li><li>Review the differences/similarities between each approach, and collect any feedback/suggestions during this time.</li><li>You can also allow the team to utilize a <a href="https://www.fastcompany.com/3034772/note-and-vote-how-google-ventures-avoids-groupthink-in-meetings">“note &amp; vote”</a> session to determine notable and actionable feedback.</li></ul><h3>2. Feedback Forms and Surveys</h3><p>Feedback forms and surveys are a great low impact way to reach large audiences. In order to be effective, feedback forms and surveys have to be precise and unbiased, so it is important to pose and word your questions appropriately.</p><p>Here are a few example circumstances where feedback forms and surveys might be applied:</p><ul><li>You’re looking to rebrand your company, and a new company logo is next up on the to-do list. It’s important to your team that the logo is widely accepted by your customers, so you’d like their input during this creation process.</li><li>There’s a decision to be made for your product, and that decision would greatly benefit from a bit of data to back it up. You don’t have access to an analytics tool, but you do have access to many individuals who might be willing to answer a few short questions.</li></ul><h4>How might you conduct this?</h4><ul><li>Consider your tool options, and determine what works best for your needs.</li><li><a href="https://docs.google.com/forms">Google Forms</a> and <a href="https://www.surveymonkey.com/">SurveyMonkey</a> are widely-known free tools that most people are comfortable with. However, these tools may not provide visuals or graphs of responses.</li><li><a href="https://www.typeform.com/">Typeform</a> is a paid tool that provides data visualizations and customizations, but it can take a little bit of time to learn how to use it.</li></ul><p>When you’re crafting your questions, make sure that you aren’t posing questions in any sort of leading way. Additionally, keep surveys relatively short (~ 5 minutes to complete) to ensure end-users feel comfortable completing the survey, so word your questions in a way that will provide the most value while being easy to answer.</p><ul><li>Surveys are only effective when they provide unbiased feedback. The individuals who receive your survey should be — if possible — users who do not have a direct relationship or investment in the product.</li><li>Each response (especially any free-text response) should be reviewed and considered as your team determines what to iterate upon next.</li></ul><h3>3. Initial Concept Validation</h3><p>Initial concept validations are one of my favorite approaches to utilize when you’re trying to validate a product during the early stages, as well as when you’re looking to validate additional features for a long-standing product.</p><p>This technique involves ensuring (or validating) that the product concept is going to be useful, relevant, or necessary for customers. I have to say, it can take a little bit of guts or courage to try these out, but if you’re willing to ask the right questions, you’ll be sure to find answers.</p><p>Here are a few example circumstances where initial concept validation might be applied:</p><ul><li>You’ve got a new product concept that you’re looking to launch, and you’d like to gauge the audience’s interest in this new product.</li><li>Another way to implement this approach is for ideas that have already been validated, but you’re looking for additional engagement for a new feature or tool within the product.</li></ul><h4>How might you conduct this?</h4><p>By spinning up a landing page or website, you can create a great opportunity to present some of the more basic information around the product, while requesting email addresses from users to keep them in the loop.</p><p>This requires users to consider if they’re truly interested — based on whether they’re willing to receive emails and updates as the product progresses. This also provides you with a set of beta-testers and users who may be more likely to engage in longer term testing and validation down the road.</p><p>Another opportunity to utilize this technique is when a product moves from being a free tool to one that is paid. How might companies determine if users are actually interested and invested enough to start paying for tools? They start out by asking a simple question: “Would you swipe your card today?”</p><ul><li>There are lots of aspects and considerations to be made in the world of pricing, but before any of those decisions can be made or numbers can be hashed out, the concept of paying for the product has to be validated.</li><li>By asking this question, users must pause and evaluate the return that this product provides to them. Is it worth it? Could I live — unchanged — without it? If users are eager and willing to swipe their cards, you’ve got yourself a validation.</li></ul><h3>High Fidelity Prototype Techniques</h3><h3>1. Digital Prototypes &amp; User Interviews</h3><p>If you’re considering utilizing digital prototypes and user interviews, you’re looking at one of the quintessential high-fidelity prototyping techniques (or at least, one of my favorite go-tos!).</p><p>This method does utilize a decent amount of resources across different domains, so it’s fairly standard practice to ensure you’ve got some validated interest in the overarching idea, prior to investing time and people into creating and interviewing end users.</p><p>This is not to say that brand new concepts shouldn’t be tested using this method (I recommend it if you can swing it!) but it is important to note that by creating and refining the prototypes, as well as interviewing end users, you’ll be utilizing a baseline amount of time in this process. How deep in the design/refinement and interview processes you go, though, is entirely up to you!</p><p>Here are a few example circumstances where digital prototypes and user interviews might be applied:</p><ul><li>You consider your product or feature to be a good candidate for a design sprint. You’ve found that there’s validation and design needed, and you’d like to timebox the amount of resources focused for the short-term.</li><li>You’re an entrepreneur with a product idea that you’ve been circulating or validating with low-fidelity prototypes for some time. You’ve reached the point where you’re looking to find a way to design and validate your approach for an initial minimum viable product (MVP).</li><li>The next feature that has been requested is a pretty heavy lift from a technology perspective, so you’d like to create a prototype to validate that the feature truly solves a problem for end users, while searching for ways to minimize scope through user feedback.</li></ul><h4>How might you conduct this?</h4><p>If you have a design sprint facilitator handy, consider yourself incredibly lucky and tap into their expertise! If you find yourself without that resource at your disposal, you can tap into some of the exercises that <a href="https://www.gv.com/sprint/">GV utilizes for their design sprints</a>, and implement them across your projects — focusing on targeting a segmented area and problem, designing out potential solutions, and interviewing end-users for feedback and iterations.</p><p>You don’t have to invest a full week at the start, especially if that’s not feasible for your team. These can be timeboxed to fit your needs. Crema has had success in practicing a <a href="https://www.crema.us/blog/running-a-2-5-hour-feature-sprint-with-a-startup-mobile-app">2.5-hour feature sprint</a> before diving into further sessions for incremental prototype design and feedback.</p><h3>2. Breadboarding</h3><p>The team at Basecamp has helped to spread the word and value of <a href="https://basecamp.com/shapeup/1.3-chapter-04">breadboarding</a> in their tried and true technique, which they use within their own organization. This technique can also be considered low fidelity, as you’re not creating assets or designing digital prototypes during this process.</p><p>However, in order to really align on the best approach using this breadboarding process, you’ve got to have the right set of people in the room — and many times that means resources from development, design, product, stakeholders, and end-users.</p><p>Because we are utilizing individuals ranging from various teams, there’s a strong argument that you’re actually creating a prototype with high fidelity — one that is refined and ready to be implemented from a design standpoint.</p><p>Here are a few example circumstances where breadboarding might be applied:</p><ul><li>You work for an organization that produces Software as a Service (SaaS)<br>You have internal stakeholders (leadership), external stakeholders (clients who use the product), sales teams who sell the product, and product teams who build the products. Time and time again, you’ve found yourself in a situation where at least one or more of those groups has felt or voiced that X or Y solution didn’t fit the need from their perspective.</li><li>You work on a product team, creating software or tooling for a specific client: You’re looking to collaborate with each prospective member of the team and your client to ensure that the workflow is considerate of all needs, requirements, and <a href="https://theproductmanager.com/topics/product-specification/">product specifications</a>, prior to designing and developing.</li></ul><h4>How might you conduct this?</h4><p>Determine who needs to be in the room. Depending on the problem that you’re trying to solve, you may need to narrow down the focus group or expand the room to ensure that all parties are represented and part of the decision making process.</p><p>Just like Basecamp recommends, utilize a whiteboard (or virtual whiteboard, like Miro!) and focus on defining a user flow with three basic elements, only using words (no pictures!):</p><ul><li><a href="https://basecamp.com/shapeup/1.3-chapter-04#breadboarding"><strong>Places</strong></a><strong>:</strong> These are things you can navigate to, like screens, dialogs, or menus that pop up.</li><li><a href="https://basecamp.com/shapeup/1.3-chapter-04#breadboarding"><strong>Affordances</strong></a><strong>:</strong> These are things the user can act on, like buttons and fields. We consider interface copy to be an affordance, too. Reading it is an act that gives the users information for subsequent actions.</li><li><a href="https://basecamp.com/shapeup/1.3-chapter-04#breadboarding"><strong>Connection lines</strong></a><strong>:</strong> These show how the affordances take the user from place to place.</li></ul><p>Discuss each element with your team, iterate the connections, affordances, and even places with the feedback that is received. You’ll do this step as many times as it’s needed — to ensure that different perspectives and viewpoints are reviewed so that each flow can be considered and if applicable, incorporated, prior to design implementation</p><h3>3. Patchwork Prototyping</h3><p>Patchwork prototyping is a type of rapid prototyping that involves the use of open-source software and was a part of an incredible <a href="https://www.ideals.illinois.edu/bitstream/handle/2142/9804/jones_floyd_twidale_patchwork_prototyping_draft.pdf?sequence=3&amp;isAllowed=y">study at the University of Illinois</a>.</p><p>This approach in prototyping takes into account so many of the things that we instinctively do to create uniformity and save time (such as choosing to use material designs rather than custom designing a UI) as we build product prototypes, while bringing open source software into the equation as well.</p><p>According to the study, patchwork prototyping involves “<em>patching together open-source applications as a means of creating high-fidelity prototypes,</em>” and “<em>combines the speed and low cost of paper prototypes, the breadth of horizontal prototypes, and the depth and high-functionality of vertical, high-fidelity prototypes</em>.”</p><p>Here are a few example circumstances where Patchwork Prototyping might be applied:</p><ul><li>You’ve received requests for new functionality within your product, functionality that might be a bit out of scope for what your tool was originally intended for, so you’d like to validate this request with other users or stakeholders before taking on the full challenge of building it out.</li><li>Time and/or resources are limited, but you need a rapid way to validate a concept or use case, or to gain momentum with users or stakeholders.</li></ul><h4>How might you conduct this?</h4><p>Let’s say that you’ve received a request to build out a custom CRM. In that CRM, they’d like to have not only records of customers/management of clients, but visibility into different projects for each of those customers, as well. In other words, it should act as a “one stop shop” for managing clients, while also doing the work for the clients as well.</p><p>Before building out each tool individually, validate whether this tool is sustainable and solves the problem that the requester is facing. So, you’ll utilize patchwork prototyping to implement a quick solution, prior to developing any custom software.</p><p>You’ll begin by researching open source software that might be a good fit for the short term prototype. For example:</p><ul><li>VLC Media Player (Media Player)</li><li>GIMP (Photo Editor)</li></ul><p>Once you’ve selected the different tools that you need to fit the various requests within the product, you’ll begin to stitch them together. The desired outcome isn’t to create a perfect product. In reality, it might feel a bit weird to use so many different open source tools within one another. However, this will allow you to quickly generate a functioning, high fidelity prototype to validate your approach.</p><p>Once tested and validated, you may find that a few simple iterations within the open software will work for your use cases, or, you’ll have the feedback that you need to refine the concept and create your custom solution.</p><h3>Rapid Prototyping &amp; Iterative Design Process</h3><p>We’ve reviewed many different prototyping techniques that can be applied across various states of products and ideas, but now is where the hard part begins: how do I make this a part of my regular product lifecycle? It can be difficult to dive right into prototyping, gaining buy-in across various teams (and especially if you need resources to do it!).</p><p>However, the best way to get momentum and create a habit of prototyping is by starting small. Finding a small problem that users are experiencing — even if the solution seems obvious — can be a great way to test some of these techniques out with your team.</p><p>You’ll be able to find new ways to improve not only your tool but your team’s ability to proactively collaborate and solve problems together.</p><p><em>Originally published at </em><a href="https://theproductmanager.com/topics/rapid-prototyping-techniques/"><em>https://theproductmanager.com </em></a><em>on September 24, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b0b620c071be" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-product-manager/6-rapid-prototyping-techniques-to-develop-products-quickly-b0b620c071be">6 Rapid Prototyping Techniques To Develop Products Quickly</a> was originally published in <a href="https://medium.com/the-product-manager">The Product Manager</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Workflow Management: A Guide To Mastering Your Product Delivery | Blog | Crema]]></title>
            <link>https://medium.com/ideas-by-crema/workflow-management-a-guide-to-mastering-your-product-delivery-blog-crema-ed000ea9376a?source=rss-b0bc0ee7f65b------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed000ea9376a</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[workflow]]></category>
            <category><![CDATA[process]]></category>
            <dc:creator><![CDATA[Alison Renfro]]></dc:creator>
            <pubDate>Fri, 19 Jul 2019 18:42:01 GMT</pubDate>
            <atom:updated>2019-10-09T17:57:50.017Z</atom:updated>
            <content:encoded><![CDATA[<h3>Workflow Management: A Guide To Mastering Your Product Delivery</h3><p>Ever wonder how on earth you’re going to track and manage your ever-expanding product? Are you worried about missing details or delivering the wrong tools at the end of a product’s lifecycle? Have no fear — we’re here to help you set your team and product up for success with our guide to mastering your product delivery with workflow management.</p><p>In order to do this, we’re going to need to unpack a few things along the way. Here’s what you should expect to learn:</p><p>1. What the heck is a workflow, anyway?</p><p>2. How to make your own workflow, and make it really work for you (+ tips!)</p><p>This guide will equip you with applicable solutions and examples within product workflows and help you master the art of workflow management.‍</p><h3>What The Heck Is A Workflow, Anyway?</h3><p>A Workflow is likely close to what you think it might be — a managed flow in which your work goes from inception to completion. As easy as the initial concept may sound, it can actually be quite complex to implement in an impactful (and effective) way, and it’s definitely seen as a necessary component for products to run <strong>well</strong>.</p><p>When it comes to digital product management specifically, your workflow could look a lot like business process management once you dive into the development phase of building products. <em>A BPM framework (</em><a href="https://thedigitalprojectmanager.com/workflow-management-software/"><em>business process management</em></a><em>) framework is a process-centric framework that provides definition for and visibility into an organization’s sets of coordinated tasks.</em>‍‍</p><h3>Holistic Workflows In Digital Product Management</h3><p>Consider a holistic workflow as the first step to take when planning out a new product. This type of workflow is used when you begin to compile how you might take a product from inception all the way through development. You may begin with mapping out your strategic concepts and end with a high-level roadmap for the direction of your product. In the following example, I showcase a holistic workflow that shows the different steps we follow to take an idea from concept through product roadmapping.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_H02I0fmU5p0Zvo2.png" /></figure><p>First: <strong>Concept Mapping</strong>. This first step within the holistic workflow allows the team to describe the different ideas/concepts that they have and visualize how those components interact with one another.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iAtO3B8QuMctR4-D.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JeC4epOs65un9qhY.png" /></figure><p>Second: <strong>Value Chain.</strong> This step takes the ideas from Concept Mapping and prescribes value to those ideas. This allows the team to understand how ideas can feed into the overall goal for the end product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*edrNbDDWCB0WEW4X.png" /></figure><p>Third: <strong>The Lean Model Canvas</strong>. This step is populated with information gathered from the Concept Mapping and Value Chain exercises.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pwhiHfhTk2XtzRIa.png" /></figure><p>Fourth: <strong>User Story Mapping</strong>. This occurs next, where your Concepts (and their applied value) are defined into potential features or requests within your new product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1CP7aL8UlJTeOb4R.png" /></figure><p>Fifth:<strong> Product Mapping</strong>. Once you’ve defined user stories, you will then map out the general (timeline or desired priority) approach of how and when you plan to complete the features within your tool.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*148V3M69ekt5SVOe.png" /></figure><p>Every holistic workflow looks a little different, depending on the goals of the product and organization. However, the purpose of creating this workflow is to visualize the steps and exercises that are dependent on one another, and to provide transparency to not only your team, but to potential stakeholders as well.</p><p><a href="http://miro.com/">Miro</a> (previously Real Time Board) is a tool that does a great job of providing different templates, so that you can build out your holistic workflow with ease and confidence.</p><h3>A Deepdive Into Business Process Management Workflows For Digital Product Management</h3><p>Once you have your product roadmap built, you will likely dive into design and development. This stage of product management is where things can get incredibly complex — but your workflows don’t have to be part of that complexity! Below, I’ve outlined one of my favorite templates from <a href="https://www.atlassian.com/software/jira">Jira</a>, one of the more commonly used Product/Process Management solutions used by teams all across the world.</p><p>This template showcases a simple Scrum workflow within Jira.</p><p>You’ll notice that tasks begin in “<strong>To Do</strong>”, but aren’t required to transition to a single next step — there are many options you can take depending on the status of the task!</p><p>“<strong>Ready For Dev</strong>” is a secondary status in the flow. You’d treat this status like you would a “sprint backlog”, where items are ready and queued up to be worked on by the development team.</p><p>“<strong>In Progress</strong>” is just what you might think it is — it’s in progress (or actively being worked on) by someone on the team.</p><p>“<strong>Blocked</strong>” is a status that allows tasks to be illuminated when they run into issues/problems that must be solved (or need assistance with) someone outside of the team. This status is helpful for those who are working on the tickets, but also for PM’s like ourselves! It allows visibility into what issues are relevant, and may allow you to find the help or tools to get the task unblocked.</p><p>“<strong>In Review</strong>” means that the task has been transitioned for review. Depending on your team size, the reviewer could be someone outside of your immediate team. Having a separate status for this step is important, because it means that once the task is approved, you’ll be able to move it to the next (and final stage).</p><p>“<strong>Done</strong>” is where your work lives when you’ve completed all required work that was defined, and all tests on the task have passed with flying colors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BuytlqW8xfSjILHg.png" /></figure><h3>Practical Guide: How to make your own workflow, and make it really work for you</h3><p>Now that you’ve walked through some of my favorite workflows to implement, you may be itching to get started making your own (and you totally should). Here are some steps to help you get going on the right path and a few tips to make life a little easier (and fun!) along the way.</p><p><strong>First things first:</strong> Decide what you should map out. <br>- This is the very first thing that you need to do, and this is the step that may take you the longest. My recommendation would be to first physically (oh yes, grab that pen and paper!) draw out what your process looks like. You may need to walk through it a couple of times in order to really nail it down (and ensure you didn’t miss a step), but take the time you need. It’s important that you visualize what your specific process looks like, because this will be what you use to translate your process into a tool.</p><p><strong>Pro Tip:</strong> Once you feel good about what you’ve outlined, have someone else on your team take a look at it. Specifically if you’re working with development or design, as they may have steps that they’d like mapped out, too.</p><p><strong>Second:</strong> Find a tool that works for you. <br>- There are so many amazing tools outside of Jira and Miro that can help you to visualize some of the workflows you utilize within your day-to-day. Find one that works best for you and feels comfortable when you use it.</p><p><strong>Pro Tip:</strong> Make sure that the tool you use has good integrations! If you use something specific for managing your tasks/tickets and decide to utilize a different tool for developing your workflows, you’ll want to make sure that those tools can talk to each other, as your workflow may change over time.</p><p><strong>Last but not least: </strong>Don’t be afraid to mess with templates. <br>- I have no shame in admitting that many of my workflows are really just workflow templates that I’ve adjusted to fit my own team needs. There are many templates available (even beyond what the tools have provided in-house). Utilize what others have created, and make those creations work for you.</p><p><strong>Pro Tip: </strong>Even if you aren’t able to utilize a template, even if you aren’t able to utilize a template, make sure you visualize the difference paths your workflow can take when you create or alter a workflow (remember the Jira example above? Tasks aren’t always forced into a single workflow, because tasks can have different statuses depending on what’s happening/what is needed).</p><h3>What Do You Think?</h3><p>Workflows are such an incredible tool to keep in your toolbelt of PM knowledge. They can make processes transparent and help to ensure products are built in a way that works best for the needs of the whole team. We hope that you feel the same way, too!</p><p>Now that you’ve got all the know-how when it comes to workflow management, what do you think about it all? Is this something that you utilize in your organization, or plan to begin championing? Let me know in the comments below!</p><p><em>Originally published at </em><a href="https://www.crema.us/blog/workflow-management-a-guide-to-mastering-your-product-delivery"><em>www.crema.us</em></a><em>.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F3eee85%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2F3eee85&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/649b83359ed6c72f505d9bd1d5e9ed30/href">https://medium.com/media/649b83359ed6c72f505d9bd1d5e9ed30/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed000ea9376a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ideas-by-crema/workflow-management-a-guide-to-mastering-your-product-delivery-blog-crema-ed000ea9376a">Workflow Management: A Guide To Mastering Your Product Delivery | Blog | Crema</a> was originally published in <a href="https://medium.com/ideas-by-crema">Ideas by Crema</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Doing hard things: why is it so hard to do well?]]></title>
            <link>https://medium.com/ideas-by-crema/doing-hard-things-why-is-it-so-hard-to-do-well-29d6944197ee?source=rss-b0bc0ee7f65b------2</link>
            <guid isPermaLink="false">https://medium.com/p/29d6944197ee</guid>
            <category><![CDATA[process]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Alison Renfro]]></dc:creator>
            <pubDate>Wed, 17 Apr 2019 19:08:35 GMT</pubDate>
            <atom:updated>2019-10-09T18:54:09.096Z</atom:updated>
            <content:encoded><![CDATA[<h4>The Irony Is Real.</h4><p>Ask any Product Manager what the least favorite component of their job is, and I’d be willing to bet the majority of responses correlate with something in the realm of “having hard conversations”.</p><ul><li>They can be incredibly <strong>uncomfortable</strong>.</li><li>They’re <strong>not</strong> inherently easy to do.</li><li>If they’re not done well, they can lead to a lot of <strong>added complexity</strong> within your project, as well as within the relationships of the team and client.</li></ul><p>Pretty exciting, yeah?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*vWFN_CZZxWfXrj2C.gif" /><figcaption>yep.</figcaption></figure><p>I really hate to break it to you, but as cringe-worthy as some of these conversations can be, they’re not going anywhere any time soon.</p><p>Let’s take a collective deep breath, and walk through some of the ways we can make these better, together.</p><p>We got this!</p><h3>Hard Conversations: What Actually Makes Them Hard?</h3><p>Having a conversation typically isn’t seen a strenuous activity (excluding the idea that communication in its general nature is difficult), so what exactly shifts a conversation from something that’s effortless to something that’s grueling?</p><p><strong>What if it’s you[r emotions]?<br></strong>That’s honestly okay, because it probably means that you <strong>care</strong>. Having an emotional connection to your day-to-day work means that you’ve got passion for what you do, and that you’re likely concerned with doing your job well. But it can also mean that you’ve got challenges to overcome when the honeymoon phase is over.</p><p>I like to think of this as healthy stress — motivation to do well for the projects/teams that you care deeply about. Embrace and respect the passion you have for your project, but don’t allow it to overcome you. Use it to your advantage.</p><p><strong>What if it’s you[r mistake]?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*z3lmOsGroqbrVDEF.gif" /><figcaption>oops.</figcaption></figure><p>As unfortunate as it is, we are all guilty of imperfection and <strong>we all screw up</strong>. Sometimes it’s a completely siloed mistake, and sometimes it’s a mistake that the team has made together. The goal with any mistake though, is gaining the courage to own up to it and grow from it.</p><p>There’s a lot to be said for those who own what they’ve done, and even more to be said for those who choose to make changes moving forward. Do your best not to let the anxiety feel too heavy, because (in the words of the esteemed Hannah Montana): everyone makes mistakes, everyone has those days.</p><h3>Hard Conversations: How Can We Make Them Less Hard?</h3><p><strong>Ask questions, and ask them often.<br></strong>If there’s one thing that I’ve learned that applies to all areas of life, it’s that asking questions (particularly the ones that aren’t so easy to ask) is the best way to gather clarity. Hard conversations can be softened by asking targeted questions, aimed to provide clarity or alleviate miscommunications.</p><p>Seeking and asking for clarity should always stay top of mind when you’re diving into difficult conversations. If you ever find yourself having doubts about the intention or meaning behind why or what something means, simply ask for clarity. You’ll likely save yourself (and others) from additional or unnecessary duress when miscommunication occurs.</p><p><strong>Talk through your thoughts with other people.<br></strong>Discussing your plan of action with another co-worker or friend is a great way to get genuine feedback before you dive into hard conversations. There are a few key steps to ensure that this process works:</p><ol><li>Make sure the person you confide in is someone who is honest and trustworthy. You should feel comfortable receiving feedback from them.</li><li>The feedback you receive should be taken into consideration and deeply analyzed. You will be the final decision-maker when it comes to the conversation you craft, so take any/all action items from this chat and thoroughly review them before incorporating or disregarding any of the components you received.</li><li>Pay that person back in the future — lend your ear to that person in return.</li></ol><p><strong>Look inward before you look outward.<br></strong>Remember when we talked about what actually makes conversations hard? Well, this is the time that we reflect on these components (and by components, I am absolutely referring to <strong>you</strong>).</p><ul><li>Is the reason the conversation seems hard, because you feel sensitive to the topic, or personally impacted? Remember that the reason you may feel this way is because you legitimately care about what you’re doing. Acknowledge this, and find ways to press forward without overwhelming yourself.</li><li>Is the reason the conversation seems hard, because you/your team made a mistake? Remember that the goal of any mistake is two fold — ownership and growth. Determine how you found your error, and determine how you’re going to improve moving forward.</li></ul><p>Hard conversations are just that: they’re hard. Making the choice to engage in a hard conversation is the first step (and sometimes the hardest). But by utilizing tools such as self-realization, seeking feedback, and ensuring clarity by asking questions, you will begin to shift perspectives and arm yourself with the confidence you need to succeed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*I_gMfwXrs9B3AdRl.gif" /><figcaption>you got this, no doubt.</figcaption></figure><p><em>Originally published at </em><a href="https://www.crema.us/blog/doing-hard-things-why-is-it-so-hard-to-do-well"><em>https://www.crema.us</em></a><em>.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F3eee85%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2F3eee85&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/649b83359ed6c72f505d9bd1d5e9ed30/href">https://medium.com/media/649b83359ed6c72f505d9bd1d5e9ed30/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29d6944197ee" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ideas-by-crema/doing-hard-things-why-is-it-so-hard-to-do-well-29d6944197ee">Doing hard things: why is it so hard to do well?</a> was originally published in <a href="https://medium.com/ideas-by-crema">Ideas by Crema</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Is Scrum?]]></title>
            <link>https://medium.com/ideas-by-crema/what-is-scrum-3d2e5263c5c6?source=rss-b0bc0ee7f65b------2</link>
            <guid isPermaLink="false">https://medium.com/p/3d2e5263c5c6</guid>
            <category><![CDATA[process]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Alison Renfro]]></dc:creator>
            <pubDate>Thu, 21 Mar 2019 18:50:41 GMT</pubDate>
            <atom:updated>2019-10-09T19:02:37.373Z</atom:updated>
            <content:encoded><![CDATA[<h4>Scrum can get really complex, so we’re going to help break it down for you.</h4><p>Good ‘ole Scrum.</p><p>Maybe you’ve heard of it, maybe you haven’t.</p><p>Maybe you’ve internet-stumbled your way to this post in hopes of figuring out what the heck this silly-sounding concept is.</p><p>Well, great news. <a href="https://medium.com/ideas-by-crema">Crema</a>’s here to provide you with some considerations from our experience with this whole ‘Scrum’ thing. We hope it shines a bit of light into the complex world of new-age product development and management.</p><p>Enjoy!</p><h3>So, what is Scrum?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VxxO00REknKUpBNbhhUMXg.png" /><figcaption>We like it, we love it.</figcaption></figure><p><a href="https://www.crema.us/primer/scrum">Scrum</a> is a <a href="https://www.scrum.org/resources/what-is-scrum">framework</a> — that’s truly what it boils down to at the end of the day. Some may feel that Scrum is a ‘mindset’ or even a ‘way of business’. As overwhelming as that may seem, frameworks can be implemented beyond just product development, so don’t let that scare you or overwhelm you. In Scrum, we like to start small, so let’s dive into the basics before we start drinkin’ the Kool-Aid®:</p><p>Scrum is to Agile like nice, cast iron skillets are to cooking: it’s not the overall concept of what you’re doing, but the distinct way in which you get your final product (may that be amazing cornbread or, in our case, a digital product).</p><p>In <a href="https://www.crema.us/primer/agile">Agile</a> development, we intentionally take things in iterative, palatable chunks of work. Scrum gives us proven tools, tips, and tactics to plan, develop, and deliver those chunks of work. There are many different types of implementation when it comes to Agile development (check out our other post <a href="https://medium.com/ideas-by-crema/whats-the-difference-between-kanban-and-scrum-647dec826a20"><strong>Kanban vs Scrum</strong></a><strong> </strong>for more) but when it comes to the default we use here at Crema, we love to lean into Scrum.</p><p>This framework encompasses Scrum Events (sans Kool-Aid®) that inspire:</p><ul><li>Collaboration for teams</li><li>Data to estimate future progress</li><li>Inherent team ownership</li><li>The overall value of process and product</li></ul><h3>What are the basics of the Scrum Events?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CKnTpt5xPW4-KnvAMqhkKg.png" /><figcaption>Scrum, made easy!</figcaption></figure><p><strong>Daily Standup</strong></p><p>This daily event is focused on getting updates communicated throughout the full team. This is done by each team member providing answers to three specific questions:</p><ul><li>What was completed yesterday?</li><li>What is being worked on today?</li><li>Do you have blockers or issues?</li></ul><p>This event provides the opportunity for clarity and open communication across a product team.</p><p><strong>Backlog Grooming</strong></p><p>Backlog Grooming is dedicated time to focus on ensuring the product backlog is in tip-top shape. During this event key stakeholders (product owners, clients, etc) will collaborate with select members of the product team (product strategists, and/or managers) to refine and prioritize tasks that correlate to your product.</p><ul><li>Backlog grooming can occur as frequently as your product/team requires</li><li>Lots of incoming bugs and frequent shifts in priority? Meet weekly.</li><li>Only need to ensure your backlog of work is aligned with the goals of the product and stakeholders? Meet bi-weekly.</li></ul><p>This event is core for reaching alignment between those who are strategically making decisions, and those who are tactically implementing changes.</p><p><strong>Sprint Retrospective</strong></p><p>This is an important event to prioritize regularly as a team, as it allows for reflection, learning, growth and overall healthy conversations. Each product team does this differently, but the main discussion points should stay the same:</p><ul><li>How did things go well last sprint?</li><li>Were there times last sprint that things weren’t going so well?</li><li>How can the team improve moving forward?</li></ul><p>Retrospectives can be done as frequently as your team sees fit. At Crema, we conduct retrospectives at the end of each sprint, so that learnings can be applied quickly.</p><p><strong>Sprint Planning</strong></p><p>This event is broken up differently, depending on the organization, client, or product. Here at Crema, we like to include Sprint Reviews, Demos, Refinement &amp; Story Pointing during our planning event.</p><p><strong>1. Sprint Review</strong></p><p>During sprint reviews, the team will discuss any work that was accomplished over the last sprint. Many times, this means walking through each individual ticket, and discussing specifically how/what was accomplished.</p><ul><li>The team may use this time to break apart incomplete tickets, as well as allocating any effort (points) for the incomplete tickets.</li><li>Any new items found during testing can be discussed, and new tickets can be created and prioritized as needed.</li></ul><p><strong>2. Product Demos</strong></p><p>After the sprint review, the team shifts direction to focus on what is headed down the pipeline. This timeframe is best utilized to allow for demonstrations of design progress.</p><ul><li>Remember: any designs that are shown are always subject to change based off of feedback.</li><li>These demo’s should be fairly short, but if additional (or thorough) feedback is needed, schedule time outside of your sprint planning for followup.</li></ul><p><strong>3. Story Refinement</strong></p><p>Story Refinement is how our ideas are brought to life. This process is how we determine exactly what is implemented throughout a product lifespan. Story writing takes collaboration from the whole team throughout different stages of the process.</p><ul><li><a href="https://www.crema.us/primer/epics-stories">Stories</a> should be initially defined by the Product Manager/Owner prior to team refinement.</li><li>If any additional context or acceptance criteria is discussed when the stories are brought to the full team for collaboration, the stories should be updated accordingly.</li></ul><p>For a deep-dive into User Story writing, be sure to check out our post: <a href="https://medium.com/ideas-by-crema/how-to-write-user-stories-fdc3746d59c"><strong>How To Write User Stories</strong></a>.</p><p><strong>4. Story Pointing</strong></p><p><a href="https://www.crema.us/primer/story-points">Story pointing</a> provides a product team the tools they need to measure the complexity of a story. By assigning value to individual stories, you can set your team up to better understand their overall capacity and predict what volume of work can be completed in the future.</p><ul><li>Utilize a pointing scale that works best for your team.</li><li>Understand that each team you work with can have different <a href="https://www.crema.us/primer/story-points">velocity</a> metrics.</li></ul><p><strong>Sprint Commitment</strong></p><p>As a team, you’ll review the selected (and refined) stories and make a commitment for the sprint. When this is done, it’s important to understand that the full-team is committing to completing everything that is in the sprint, including development, testing, and merging changes.</p><p>In order to drive understanding in this area, it’s suggested that the team summarizes their commitment into a statement (sprint goal) and confirms alignment of that goal with the client.</p><p>For more information on perfecting your Scrum Events, be sure to check out our post → <a href="https://medium.com/ideas-by-crema/the-4-scrum-ceremonies-made-simple-a-quick-guide-to-scrum-meetings-ea91fe604d88">The 4 Scrum Ceremonies Made Simple: A Quick Guide To Scrum Meetings.</a></p><h3>What are common challenges with moving to Scrum?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BLsx-teYGG00ExaqFT-ahQ.png" /><figcaption>We can get through it together.</figcaption></figure><p>Product design and development isn’t inherently an easy thing to do, which is why so many organizations come to the experts (like <a href="https://www.crema.us/">Crema</a>!) to do it for them. Each method of implementation (and their corresponding frameworks) have positives and negatives, so it’s important to choose something that’s going to best work for your specific team, client, and product.</p><p><strong>Going from Kanban → Scrum</strong></p><p>Kanban is another Framework option within Agile development, and it can be an incredible way to produce a product. However, when teams make the transition from Kanban to Scrum, there can be a lot of learning in the process.</p><p>Kanban doesn’t typically work in sprints. Which means that when using a Kanban framework, new priorities are easily injected into the current development pipeline. Scrum requires teams to commit to prioritized work and stick to their commitment (as much as possible) rather than allowing for continual changes in development or design focus.</p><p>This shift in thinking can be difficult for projects that have frequent changes in prioritization (including production bugs, project focus, client request, etc). These sprint commitments may seem hard, but they’re intentionally used to guide the team towards a focus on prioritization and provide an overall sense of stability.</p><p><strong>Going from Waterfall → Scrum</strong></p><p>Waterfall is a methodology (just like how Agile is a methodology) that can be used for product/project management. Waterfall has been used far and wide, from large <a href="https://www.crema.us/primer/enterprise-client">enterprise clients</a> to <a href="https://www.crema.us/primer/small-business">small businesses</a> and <a href="https://www.crema.us/primer/startup">startups</a>. This methodology is the granddaddy of product/project management and has been around for quite some time. When this method is used, members of the product team fully scope all product features and timelines before development or design is started.</p><p>When using Agile &amp; Scrum, product scope is done a bit differently. Although upfront planning and thoughtfulness is a key component, Agile &amp; Scrum allow for flexibility in features and in timelines. This distinction can cause a lot of friction when teams are transitioning from Waterfall to Agile and can be a large deterrent from completely moving teams and processes over to Agile.</p><h3>So why use Scrum?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ltCFDXScibP2hicmvRhUVQ.png" /><figcaption>(You totally should)</figcaption></figure><p>When building products, it can be hard to initially predict every possible external and internal factor you may face, even with the most methodical evaluation and plan in place. When utilizing Agile &amp; Scrum, you allow your team and project the ability to adapt to the changing needs of users and stakeholders (while keeping the product goal top of mind).</p><p>These adaptations (or shifts) are what we call <strong>iterations</strong>.</p><p>Iterations allow your product the ability to become the very best version of itself, as needs and requirements inevitably change over time. These iterations give your team the chance to pose questions/develop solutions for use-cases as they arise, while balancing the needs of stakeholders, clients, and end-users. But most importantly, these iterations give us, as humans, the opportunity to continually and intentionally grow our skills and knowledge, all while building amazing products.</p><p>So, is Scrum a little less of a crazy concept now that we’ve clarified some of its components?</p><p>We sure hope so.</p><p>How are you utilizing Scrum in your workplace? Do you have other questions about Scrum? Are you interested in hearing about some of the other “cast iron skillets” of product management? If so, give us a shout in the comments below! We’d love to help (and we love to talk about what we do, too).</p><p>Cheers!</p><p><em>Originally published at </em><a href="https://www.crema.us/blog/what-is-scrum"><em>www.crema.us</em></a><em>.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F3eee85%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2F3eee85&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/649b83359ed6c72f505d9bd1d5e9ed30/href">https://medium.com/media/649b83359ed6c72f505d9bd1d5e9ed30/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d2e5263c5c6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ideas-by-crema/what-is-scrum-3d2e5263c5c6">What Is Scrum?</a> was originally published in <a href="https://medium.com/ideas-by-crema">Ideas by Crema</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>