<?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 Wade G. Cunningham on Medium]]></title>
        <description><![CDATA[Stories by Wade G. Cunningham on Medium]]></description>
        <link>https://medium.com/@WadeCunningham?source=rss-40b6d2de830b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*YkQx2pdyVyWc28A3.jpeg</url>
            <title>Stories by Wade G. Cunningham on Medium</title>
            <link>https://medium.com/@WadeCunningham?source=rss-40b6d2de830b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 02:44:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@WadeCunningham/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 Use Case of Use Cases]]></title>
            <link>https://medium.com/glassboard-blog/the-use-case-of-use-cases-44394f843c25?source=rss-40b6d2de830b------2</link>
            <guid isPermaLink="false">https://medium.com/p/44394f843c25</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[hardware]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Wade G. Cunningham]]></dc:creator>
            <pubDate>Fri, 27 Oct 2017 15:23:06 GMT</pubDate>
            <atom:updated>2017-10-27T17:39:42.664Z</atom:updated>
            <content:encoded><![CDATA[<h4>Helping your customers by looking at your product from their perspective</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hopDPJf1vd07vSQ9dnqvuw.png" /></figure><p><strong>How are you going to use this article?</strong> Let’s walk through a USE CASE. First you are going to read it, nod at parts and shake your head at others, then skim over a paragraph or two, and at the end you are likely going to make a note of the headings and main takeaway. If this article piques your interest, then it is likely you are reminded of a specific instance where you could have used a USE CASE in your last project.</p><p>Or maybe you are in the middle of a product project, and are continually uncovering gaps that are forcing you to go back to the beginning.</p><blockquote>The USE CASE has different names in different industries, with various levels of formalities. Storyboard, Usage Scenarios, Brain-storming or Mind Mapping. USE CASE in software of systems development are sometimes highly structured, with its own language. Not to be burdened by the terms or industry jargon, for our purposes, we will define USE CASE’s as flexible thought-experiment structured thinking around your product.</blockquote><p>What you really want to know is how can use a USE CASE to make your product better and deliver value to your customers. The way we have successfully used USE CASES is in the communication of the product, defining actors involved, scenarios, environments, and user interactions and special functions, like troubleshooting and service. USE CASES’s help you do this by creating a baseline customer user experience, and monitoring for actual usage differences from this expected baseline, and uncovering hidden requirements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/627/1*fstL_rtU5m6SZ1V_EYPk_Q.png" /><figcaption>A Use Case can be a simple one page document or something much more detailed</figcaption></figure><p><strong>CREATING A BASELINE USER EXPERIENCE</strong></p><p>To create a baseline user experience, think through and document the entire life cycle of your product. This includes not only the periods of time when your customer is using the product, but also when it is in transit, before first use, or is in storage. The desire is to cover the entire life of your product and think about issues before your customer experiences them.</p><p>Once you have this baseline, you can then drill down on specific functionality or areas of usage.</p><p>How does your product navigate the factory, and hold up during shipment to the customer? When the user first opens the product package, what has to happen before the product can be used as intended? When the product has been in storage for a while, are there special actions that the user needs to perform before the product can be used? Filling out a USE CASE for each of these scenarios can help you clearly define your product.</p><p>To create the USE CASE, it helps to have a specific person in mind, or multiple different actors. Go through the mental exercise of how this particular user will interact with the product. You can go as far as giving them a name and personality. When they open the package, what is the first thing they see, and do they know how to turn your product on and off? What are the steps they need to take to actually use the product?</p><p>Defining your product in this manner also helps your team. Explaining how the product work allows them to implement the functionality as it is described, and not make wrong and incorrect assumptions about the product. When characteristics of your product are not described, product developers will fill in the gaps with the assumptions they make about your customers. The USE CASE helps them get this right, or point to gaps that need filling.</p><p>If your product needs to be installed, then a USE CASE could go through the installation of the device, and what technicians will need to do. Realize that when your product ships, if you do not want constant calls, it has to work or be understood how to work.</p><p>The use case serves to inform of the expected usage of the device. Having an expected user experience allows for differences to be detected and assumptions confirmed. Even if the customers use the product differently, checking against these assumptions can provide valuable customer information.</p><p><strong>MONITOR ACTUAL USER EXPERIENCE AND LOOK FOR DIFFERENCES</strong></p><p>It is not easy to uncover all possible USE CASE scenarios by imagining your customers using your product. Customers will surprise you and use your product in unintended ways. But if there is no baseline, then no differences can be detected, and assumptions are harder to uncover and question.</p><p>If someone is not using your product like you intended, maybe this is an idea for a new product! If the product was designed for one task and used for a different one, it may speak to the versatility of your product and uncover another market need. There may be options to increase the usefulness of how the customers are using it in the unintended way.</p><p>Your own familiarity with your product gets in the way of seeing how an inexperienced user would use it. It is like a little child at an old desktop computer — He touches the screen and then picks up the mouse and starts talking into it, then when nothing happens, starts holding it to his ear! One of the most commonly cited causes of product error is “user error” which may be because the user just doesn’t understand the proper use of the device.</p><p>Don’t let smart customers sabotage your product because they just don’t understand how to use it. You have spent a lot of time and thought, and maybe use your product yourself. However, your customers may not have the experience that you do. Don’t beat them up, but try to guide them through the proper use of your by monitoring their usage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WwSc720Y58wJztDjrE4wlA.jpeg" /><figcaption>USE CASES can communicate the intent of the product, define actors, scenarios, environments, and user interactions. Here the quick brown fox gets ready to jump over the lazy dog</figcaption></figure><p><strong>UNCOVERING HIDDEN REQUIREMENTS</strong></p><p>Ultimately, by using USE CASES, you will uncover requirements that may not have been initially captured in the functional requirements or product description document. These documents are created with the perception that you know what product the end customer needs.</p><p>When one of our clients describes how a product is going to work, we ask lots of questions. We have to know this information to create the product. These questions and methodically walking through a USE CASE will pull out product details that may not have been completely thought through.</p><p>While walking through a USE CASE we will ask “How will the user know to press that button? When will the user know it is working? Not-working?” And our favorite “And then what?”</p><p>One example is a sensitive device that would be used to make measurements during a construction project. We covered the usage case, but then during the questioning about how the user would store the device, found that it needed to be well protected. It could not just be put in the back of a work truck, and would need to ride in a protective case, most likely in the truck cab. The harshest environment was not the one that the device was used in, but in the transportation to and from the worksite.</p><p>The assumptions about how customers are using the product are important for not just design, but also testing and validation. As a group that validates products, one example that sticks in our mind is when the first robotic vacuum was released. The product designers initially assumed that people would vacuum as much as they did manually before, typically weekly. The test and validation program covered this level of expected usage. What they found were worn out components, and they realized that if people did not have to be present and push the vacuum, they would run the robots daily! Components that were designed to operate 52 times a year were operating over 7 times that rate.</p><p><strong>CONCLUSION</strong></p><p>A USE CASE is simply answering, “How are the users going to in your product?” You are trying to foresee problems that your customer may encounter to preemptively fix the problems that they might see. Go through the customer product experience before they experience it, to remove un-necessary steps or make product use easier, more consistent and more robust. After it is developed, observe customer confusion and pain points. Use these learning’s to update the requirements and change your product.</p><p><em>Hope you found it USE-ful.</em></p><p><strong><em>Wade Cunningham is the Program Manager at </em></strong><a href="https://www.glassboard.com/"><strong><em>Glassboard</em></strong></a><strong><em>, a hardware focused product development company.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44394f843c25" width="1" height="1" alt=""><hr><p><a href="https://medium.com/glassboard-blog/the-use-case-of-use-cases-44394f843c25">The Use Case of Use Cases</a> was originally published in <a href="https://medium.com/glassboard-blog">Glassboard Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Prototype with Production in Mind?]]></title>
            <link>https://medium.com/glassboard-blog/why-prototype-with-production-in-mind-2271788722f8?source=rss-40b6d2de830b------2</link>
            <guid isPermaLink="false">https://medium.com/p/2271788722f8</guid>
            <category><![CDATA[hardware]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Wade G. Cunningham]]></dc:creator>
            <pubDate>Wed, 20 Sep 2017 17:43:55 GMT</pubDate>
            <atom:updated>2017-09-20T17:45:01.493Z</atom:updated>
            <content:encoded><![CDATA[<h4>Think Production Earlier in your Development Cycle</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/645/1*K9gP6efaqWATeNZ258KeBA.png" /><figcaption>Although the Raspberry Pi is an excellent platform for quick development and has sold over 12.5 million units in the past 5 years it might not be the best platform for your product</figcaption></figure><p><strong>So you have an idea for a produc</strong>t, and have created a rough mockup, showed it to some potential customers, and generated some excitement. If you are further along, you have a functioning prototype that was created quickly, using off-the-shelf parts, like a general-purpose computer and custom parts developed using rapid prototyping tools, like 3D printers. Sure, your prototype has some quirks, uses duct tape, and you have to do a funny reset every third time you turn it on, but you’re almost there and just need to tweak a couple of things before going to full production.</p><p>Prototypes are fundamental to product development, but they take time, effort, and money. Initial prototypes may be good for getting customers engaged and learning customer preferences. If you are thinking of going to production, it may be best to step back and think about a <em>better</em> prototype.</p><blockquote>A well-refined pre-production prototype will communicate more effectively to the manufacturer the special details, like color and feel, of the product.</blockquote><p>Just because you produced one unit does not mean you can scale and make a million. You need a different prototype for that, one that can actually be made at high volume.</p><p>Start your next prototype with production in mind, for these reasons: <strong>cost, control, customers</strong> <strong>and competitors</strong>.</p><p><strong>COST</strong></p><p>You may have a handful of hand-built prototypes. These are expensive. Expense is the tradeoff for fast development times, and this is acceptable in the early stages of development. However, these expenses should not be retained in the final released product and passed on to customers. At production volumes, additional overhead will become a piece-price burden. Even a 1-cent resistor at volumes of 100,000 adds up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GkMRvXFtvbyfjQqaX2lUew.png" /><figcaption>When prototyping, it is important to understand how the product will be made, even at low volumes. Here, a 2 piece, dual density child-seat head surround was designed to be quickly &amp; inexpensively produced using a 3-axis CNC mill</figcaption></figure><p>Many prototypes of products that require an embedded microcontroller are developed using the very powerful general-purpose computing boards, like the Raspberry Pi or Arduino. These are wonderful and well-supported devices. Before you decide to go to production with one of these boards, run a simple financial model. If your general-purpose computer costs $50, and 50% of the unused content can be removed by paying $50,000 for a custom board, the payback on this investment is positive after 2,000 units. Volume price breaks will change the result, but you may be surprised at how low the breakeven volume is required. Run a more detailed calculation for your project, then ask if you want to sell more than this.</p><p>Designing your product around the existing features of a general computing platform may add unintended costs. Do you use all of the features available? Does your product need all the bells and whistles to function? If it does not, then why pay for them?</p><p>If you are thinking that you can save some money by using an off the shelf board or other parts, at least be aware of what you give up: control.</p><p><strong>CONTROL</strong></p><p>Control is the ability to modify and change your product as you see fit during development, as well as in subsequent product generation releases. Control allows you to ensure product quality and functionality, mitigate sub-component obsolescence issues, protect your IP, and introduce product changes and revisions on your schedule.</p><p>When using an off-the-shelf component, or already designed sub-system, such as a general purpose development computer, ask yourself these questions:</p><p><strong><em>· What environment is your product going to exist in? Does the general-purpose computer meet the temperature, humidity and vibration requirements?</em></strong></p><p><strong><em>· Are you OK with the limitations imposed, such as form factor and un-allowed software changes? How much time and effort do you want to spend designing your product around the existing hardware to make it fit?</em></strong></p><p><strong><em>· If you find a problem, such as a hardware interface/software compatibility issue, how willing is your supplier to make and test the required changes?</em></strong></p><p><strong><em>· Is the supply of this generation board going to outlast your products life? Obsolescence in electronic components is a significant problem, which is why longer-term production IC companies have begun to guarantee a minimum product life. Your product is going to be around for a while, and subsequent product releases should be adding value to your product, not chasing the forced changes in your supply chain. The timing of these changes may not be in your best interest.</em></strong></p><p>Using an off-the-shelf general purpose board may limit your choices in the future if your product takes off. You could delay and decide to develop your own board in later generations, but this also brings risk, cost and backward compatibility concerns. When a project gets further along, there is often neither time nor funds to make changes.</p><p>Control might be the most important consideration because you need it to make product improvements and add valuable features to satisfy your customers and out-perform your competition.</p><p><strong>CUSTOMERS AND COMPETITION</strong></p><p>Customers are looking for a clean design. There may be a customer base that does not mind the clumsiness and shortcomings of an early prototype, but your typical customer will expect a more refined product. Customers don’t see the details that go into making a product, but they will almost always know if the cost is in-line with the value. Demonstrate that you spent the time making the product for them.</p><p>Competitors are never far behind. This is truer when your product exposes a real market and customer need. A product not designed specifically for the intended market and made of off the shelf components will have other, maybe better, versions along shortly.</p><p>Think of production early and often to make your product the best for all customers, and set yourself apart from competition.</p><p><strong>CONCLUSION</strong></p><blockquote>Prototypes bring your product idea from the world of fiction into a real world application.</blockquote><p>Any production level feature that can be prototyped as early as possible will lead to a more efficient product release. Product development builds upon itself. Product changes in the later stages of development are more difficult than earlier ones. A small course correction at the beginning of the program can save a massive investment later in development.</p><p><em>Wade Cunningham is the Program Manager at </em><a href="https://www.glassboard.com/"><em>Glassboard</em></a><em>, a hardware focused product development company.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2271788722f8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/glassboard-blog/why-prototype-with-production-in-mind-2271788722f8">Why Prototype with Production in Mind?</a> was originally published in <a href="https://medium.com/glassboard-blog">Glassboard Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tag! Your Product’s Design is now Frozen]]></title>
            <link>https://medium.com/glassboard-blog/tag-your-products-design-is-now-frozen-1955a67f6cf7?source=rss-40b6d2de830b------2</link>
            <guid isPermaLink="false">https://medium.com/p/1955a67f6cf7</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[hardware-startup]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[process]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Wade G. Cunningham]]></dc:creator>
            <pubDate>Wed, 06 Sep 2017 21:03:45 GMT</pubDate>
            <atom:updated>2017-09-08T14:21:39.520Z</atom:updated>
            <content:encoded><![CDATA[<h4>The Importance of Design Freeze in Product Design</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ei2OLc1Zp0r0KyHVbZGW_Q.jpeg" /></figure><p>Remember the recess game freeze tag? For those of you that don’t, (really? No freeze tag experience?) it’s the game where one person is “IT”, and the players they tag are frozen until an unfrozen player tags them or everyone is frozen. If you ever played, didn’t it irk you when you tagged everyone but one person, then he or she started unfreezing everyone and before you knew it you were winded, gasping for breath and everyone was unfrozen and running around? You were also probably deflated because after all that work, you were basically starting over.</p><p>Product development can sometimes be like this. A new product is designed, developed and prototyped, and eventually your company is on a path to produce enough for the customers that will want it, and then there is a change, or two, or three, based on any number of factors (to reduce cost, add features, meet regulations to name a few). Your team then tells you if you change a feature, then another component will need to change, and then the software will need to change, and then on and on…. Pretty soon you’re scratching your head, baffled because you have done all this work (or paid to have it done), and now it seems, you are starting over.</p><p>What to do? Here are some guiding principles that we have found useful.</p><h4>Clear Requirements, Documented up Front</h4><p>Step back and think about the product you are trying to create, and spend some time on the most important features. In freeze tag, one semi-effective strategy is to try and tag the fastest person first, then tag each subsequently slower player. Can this strategy work in product development? It may pay to try and conquer the “thorniest” issue with your product first, commonly identified and ranked on a feature evaluation matrix. This issue likely impacts everything else, and there is no sense in working on the less important peripheral (or slower) items.</p><p>By tackling the more difficult features first, this should reduce risk and also product change as time goes on. The important features should remain consistent. In electrical design we have found that at early stages, issues like thermal management (getting the heat out), energy management (ensuring sufficient battery size and packaging), and EMC requirements to be the thorniest issues. The required product tear-up to fix these issues later in the development cycle may not lend themselves to elegant or simple solutions.</p><p>But what if you do not know what your riskiest feature is? Another freeze-tag strategy is to tag whoever is closest then play defense and work outwards. If you know of a couple of features that are very important, then firm up these product fundamentals, and let the other less important details be malleable. Interfaces fall into this category, and defining and maintaining consistent interfaces between different parts of the product may limit the need for cascading changes later on.</p><p>Regardless of if the requirements stay the same throughout the entire project, there simply must be written documentation capturing them. This is either a list of product features, a detailed product description, or an engineering specification. Transient verbal descriptions are not enough, and have a way of morphing over time. A Discovery Phase for your project will help to identify and establish these product requirements.</p><h4>Have a Change Evaluation Process</h4><p>An unrelenting fact in product development is that things are going to change. Build in a process from the start (or at least a rough idea) of how you will evaluate any change and decide whether to implement it or not. This evaluation should be a trade-off assessment to lay out clearly what the proposed change is, and all steps that will need to be done or repeated if the change is implemented. Already implemented features have priority — since it is already exists there is no need to spend additional resources on it.</p><p><strong><em>The new feature always has to buy itself in.</em></strong></p><p>In the game freeze tag observers have a different perspective than someone actively playing. When you are in the middle of the game you are running and concentrating on the people running by and around you. You can’t step back — you’re busy tagging people! If you were to take a step back and look at the whole picture, you can see how a plan might help. An observer perspective will allow for a more targeted strategy to be planned, and lead to implementing productive changes.</p><p>Think about the steps that need to happen to implement a change to make sure that things don’t get overlooked. In this change process, evaluate the effect of the change on the agreed upon requirements. If there is an additional component added, how does this affect the battery size, which affects the product size, which affects the enclosure, which affects the cost. If components change enough, will testing and validation need to be repeated? Evaluations can be performed against the original requirements to define the tear-up needed.</p><p>Try to keep some resemblance of a process — there are good reasons for this.</p><p>Having a product change is not the end of the world, and this is what product development is — changing what is available. Change is happening around all the time, need to harness this and implement positive changes and features that make your product better.</p><h4>Relentlessly combat feature creep</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-uxGUxEAjX0qvyMdCvjfxw.jpeg" /><figcaption>Feature creep is not only represented by obsolete parts in a drawer, but by material impacts to the timeline and budget of a project</figcaption></figure><p>Features are great, and there are so many more things that your product could do. Freeze tag gets harder the more non-frozen players you add. One player is easy, two not too bad, but when you get to 10, 20, 50? Now you need to add to your team just to keep track.</p><p>In your product, it is important to understand that every resistor, capacitor, screw, or washer is connected to everything else. Since everything is connected, when one component changes, yes, everything about your product changes in some small way. True, some things are more connected than others, but simple changes can have cascading effects on the rest of your product. For instance, increasing the size of the power supply may affect all of the thorniest issues — adding heat to an already small enclosure, draining the battery faster, and enabling higher currents that cause additonal EMC issues.</p><p>If there are infrequently used features of your product that affect the cost and performance of the highly used features, they may be more trouble that they are worth. At a minimum the tradeoff may not be clear.</p><p>All features add to the functionality of your product, and customers may like each of them. However, there are constraints in implementing them. Have a process where you force rank features, where only one can be the most important. This forces decisions between the features relative to importance. So when a decision has to be made about adding features to a product, make sure you implement the most important one.</p><h4>Establish Realistic Freeze Dates — Plan for Incremental Releases</h4><p>Designers and engineers will continually tinker with and optimize your product if you give them the chance. You have to make them put down their pencils. The design freeze date, reasonably set, can force your team to realize that it is time to finish. In freeze tag, the teacher blows the whistle to end recess and you will have another chance to play next recess. Ambiguous end times make for frustration and delays in development.</p><p>The product should freeze well before production to ensure time for testing. In production, the cost of a change can spiral up very quickly. If a design flaw is not caught, you can manufacture many bad products very quickly during a production run. It is rather trivial to fix a resistor on a prototype, but what if now you have to fix that same component on some 300,000 units? What if half are already in customer hands?</p><blockquote><em>Software development teams are able to release “bug fixes” or software “updates.” In the hardware world, we refer to these as recalls…</em></blockquote><p>In the game freeze tag, you only win when everyone freezes. In product development, the definition of a win is not as straightforward. It could be when the product is developed efficiently on time and on budget, with little rework and redesigns. It may be when the product looks and operates like it customers expect, and customers feel as if it were specifically designed for them. Or it is when you ask customers what they would change about your product, and they say “nothing”. It is a high bar, but in truth, your product will likely never be completely frozen.</p><p><strong>In product development, just like freeze tag, as soon as everyone is frozen, you start again, just with different players and different rules.</strong></p><p><em>Wade Cunningham is the Program Manager at </em><a href="https://www.glassboard.com/"><em>Glassboard</em></a><em>, a hardware focused product development company.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1955a67f6cf7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/glassboard-blog/tag-your-products-design-is-now-frozen-1955a67f6cf7">Tag! Your Product’s Design is now Frozen</a> was originally published in <a href="https://medium.com/glassboard-blog">Glassboard Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What hitting the wall at 214mph taught me about product development]]></title>
            <link>https://medium.com/glassboard-blog/what-hitting-the-wall-at-214mph-taught-me-about-product-development-and-other-quotes-to-live-by-d3f9e776a891?source=rss-40b6d2de830b------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3f9e776a891</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[indycar]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Wade G. Cunningham]]></dc:creator>
            <pubDate>Tue, 15 Aug 2017 21:53:48 GMT</pubDate>
            <atom:updated>2017-12-01T15:12:40.038Z</atom:updated>
            <content:encoded><![CDATA[<h4>and other quotes to live by</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*eYr6V0R957qHSUruPgskxw.jpeg" /><figcaption>Texas Motor Speedway</figcaption></figure><p><strong>Texas</strong> Motor Speedway is unlike any of the other oval tracks distributed around the United States, it’s D shaped oval featuring an aggressive and gravity defying 24 degrees of banking, so steep in fact, that during the IndyCar race of 2001 the event had to be cancelled after 21 of the 25 drivers complained of dizziness, disorientation and blurred vision. With average speeds above 230mph, the drivers were experiencing sustained G forces over 5G’s, in hindsight — more than human tolerance. Fast forward to 2011 and the speeds had been reduced by a <em>whopping</em> 5 percent, the writer found himself qualifying at his debut IndyCar event at a tardy 214mph, good enough for 8th on the grid and next to fellow compatriot and Indianapolis 500 Champion Scott Dixon. After sustained green flag running in the top ten an unintentional tap from a competitor caused his car to lose adhesion and sent it careening into the “soft” concrete and steel wall system known as the SAFER Barrier.</p><blockquote><em>The Steel and Foam Energy Reduction Barrier (SAFER Barrier), sometimes generically referred to as a </em>soft<em> wall, is a technology found on oval automobile race tracks intended to absorb and reduce kinetic energy during the impact of a high speed crash, and thus, lessen injuries sustained to drivers and spectators. It was designed by a team of engineers led by Dean Sicking at the Midwest Roadside Safety Facility at the University of Nebraska-Lincoln. It was developed from 1998–2002, and first installed at the Indianapolis Motor Speedway in May 2002. The SAFER barrier consists of structural steel tubes welded together in a flush mounting, strapped in place to the existing concrete retaining wall. Behind these tubes are bundles of closed-cell polystyrene foam, placed between the barrier and wall. The theory behind the design is that the barrier absorbs a portion of the kinetic energy released when a race car makes contact with the wall. This energy is dissipated along a longer portion of the wall. The impact energy to the car and driver are reduced, and the car is likewise not propelled back into traffic on the racing surface.</em></blockquote><p>These were my thoughts:</p><p><em>“Relax. Only ten laps to go. Make sure you hit your marks. Turn in, breathe the throttle. But not too much. Use your tools. Adjust your weight-jacker. Make sure to breathe. Man I’m tired. Keep the car low. Stay balanced. Make sure to keep looking ahead for debris or accidents. Blink. Back to full throttle. React. Adjust.”</em></p><p>&lt;WHACK&gt;</p><p><em>“Not good!!! I’ve got this, stay flat! Wrong, lift! Counter steer! COUNTER STEER MORE. BRAKES. BRAKES.”</em></p><p>&lt;CAR IS NOW POINTED AT WALL&gt;</p><p><em>“This is it. The inevitable is going to happen. Accept what’s coming. Prepare for what’s coming. Can I avoid any competitors as the wall magnet in my carbon fiber canoe with no rudder sucks me up into it’s cold harsh embrace? Sigh of relief. No one else is coming. Relax. Keep breathing. Try and sink further into your custom molded safety seat, that has been designed and developed for this very reason. Lean your head back against the energy absorbing head rest, (also bespoke for each driver). One final step. After exhausting all your options. Trying every trick. Accept that this might hurt, a lot, then let go of the steering wheel. Symbolic, yes. </em><strong><em>But actually let go of the steering wheel</em></strong><em>. Tuck your hands under your shoulder belts. You are now ready to crash.”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/1*1yKfzJfVJf1jhOnErq_LGg.jpeg" /><figcaption>A visible dent in the SAFER Barrier after the author made heavy rearward impact — possibly the largest step forward in motor racing safety over the past 2 decades</figcaption></figure><p>In a nut-shell motor racing has taught me most of what I know, the value of preparation, preparedness, hard work, team-work and ongoing development, both emotionally and from a technology standpoint.</p><blockquote>During my motor racing career and now in product development I work by the following adages:</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*j_cVQfLZo6h5IZOlf-Xiyg.png" /><figcaption>All smiles before something goes wrong</figcaption></figure><p>“It Is Not Always Possible To Be The Best, But It Is Always Possible To Improve Your Own Performance” — <strong>Jackie Stewart</strong></p><p>Acceptance of one’s limitations, and setting on a course of improvement within those parameters, is one of the keys to success.</p><p>“You win some, you lose some, you wreck some.” — <strong>Dale Earnhardt</strong></p><p>No one has any idea if their product is going to be successful. Even if you have a killer Kickstarter funding round, your product may still be a flop. Your product may be a sleeper hit, slowly building a loyal following. If everything were pre-destined, there would be no need to race. Its why you have to actually go out and run the race, or build your product.</p><p>“A smooth race never made a skillful racer.” — <strong>unknown</strong></p><p>At Glassboard we have been through some tough projects, but we learned through each one, and have gotten better. Product and development snags have forced us to re-look at a product, from different angles, and sometimes we come up with better solutions in the end.</p><p>“Rubbing is racing” —<strong> Harry Hogge (Days of Thunder)</strong></p><p>At the end of the day you have to roll up your sleeves and you have to get a little dirty, your perfect idea will take time, effort, money and more effort. Oh and there will be bumps and disagreements along the way.</p><p>“When the flag drops, the bullshit stops.” — <strong>Dale Earnhart Sr.</strong></p><p>Glassboard gets its bearings by going through a <a href="https://blog.glassboard.com/discovery-phase-what-is-it-6fbf0c886794">Discovery Phase</a>. Discovery phase is perhaps a lot like qualifying — we lay out a plan, figure where we stand, and who the competitors are, and where we rank at the start of the race. When the flag drops and our clients invest, hardware is ordered, and execution is important, we get serious about changes and anything that throw a kink in the development.</p><p>“When you come to the end of your rope, tie a knot and hang on” — <strong>Franklin D. Roosevelt</strong></p><p>“If we are facing in the right direction, all we have to do is keep on walking.” <strong>— Joseph Goldstein</strong></p><p><strong>Never, ever give up.</strong></p><p><em>Wade Cunningham is the Program Manager at </em><a href="https://www.glassboard.com/"><em>Glassboard</em></a><em>, a hardware focused product development company.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3f9e776a891" width="1" height="1" alt=""><hr><p><a href="https://medium.com/glassboard-blog/what-hitting-the-wall-at-214mph-taught-me-about-product-development-and-other-quotes-to-live-by-d3f9e776a891">What hitting the wall at 214mph taught me about product development</a> was originally published in <a href="https://medium.com/glassboard-blog">Glassboard Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Discovery Phase — What is it?]]></title>
            <link>https://medium.com/glassboard-blog/discovery-phase-what-is-it-6fbf0c886794?source=rss-40b6d2de830b------2</link>
            <guid isPermaLink="false">https://medium.com/p/6fbf0c886794</guid>
            <category><![CDATA[hardware-startup]]></category>
            <category><![CDATA[electrical-engineering]]></category>
            <category><![CDATA[hardware]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Wade G. Cunningham]]></dc:creator>
            <pubDate>Tue, 21 Feb 2017 19:22:26 GMT</pubDate>
            <atom:updated>2017-02-22T18:17:21.241Z</atom:updated>
            <content:encoded><![CDATA[<h4>And is it worth paying for?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_6xakXGylYM0VMjE-uXEGA.png" /></figure><p>Think of the Discovery Phase as laying the foundation for the design and development that follows. The main functions of discovery are capturing the vision of the product from a client, ensuring that this vision is in line with the needs of end users, and performing an initial technical due diligence to certify that the product in question can be designed within the realms of today’s technology. The Discovery process can be a time-consuming and resource intensive task, but importantly it gives a hardware development team time and resources to build use case scenarios, identify functional requirements, prioritize and rate product features, create schedules and estimates and summarize their findings into a development proposal. All of these things are very important, while also demonstrating to the client that there is a process unifying a team, mitigating risk, and making sure the design or build won’t fall off schedule.</p><blockquote><strong><em>Hofstadter’s law</em></strong><em> is a self-referential time-related adage, coined by Douglas Hofstadter and named after him. </em><strong><em>Hofstadter’s Law</em></strong><em>: “It always takes longer than you expect, even when you take into account Hofstadter’s Law”</em></blockquote><p>Discovery is one of the most necessary areas of product development apart from the design process itself. It provides a tremendous amount of value to ideation, ensures a good market fit, and gives the client an accurate insight into the realistic time and costs of development. Yet, it is often the least understood phase of development. Many potential clients see the Discovery Phase as only a paid quote and nothing further. This can create problems between the development firm and their client’s relationship. In many industries, quotes for the entire service are expected to be obtained before any work is done, “How much to paint my house?”, How much is this insurance package?”, “How much does this gallon of milk cost?”. However, in product development, it would be a disservice to customers to estimate the costs and timelines of developing their product without sufficient research into it as we, as developers, would be just guessing at the costs and timelines.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cHdOiB3nC2mSlMYd3hrlVw.jpeg" /><figcaption>“Discovery should be so much more than a paid quote”</figcaption></figure><p>It may surprise many clients to find that a discovery process doesn’t usually add any cost to bottom line of a project. This is due to the fact that the discovery process, formal or informal, would happen regardless of whether it is broken out on the front end of any venture or simply baked into the cost of development. If fact, often a dedicated, upfront, and structured discovery process saves valuable development time further into the project. Not to mention, it often helps avoid costly misunderstandings of the design goals as the project progresses.</p><p>Simply put, deliberate exploratory effort and research is valuable and necessary to drive success for the client. By appending a discovery phase to the front of a project, a team can provide a clear gate for clients to walk away from any further development of the product, work with them to continue development, or pick up and develop with another firm of their choosing.</p><p>There are two things that are always true for a Discovery Process:</p><ul><li><strong><em>Discovery is a process the client is already used to paying for</em></strong></li><li><strong><em>Discovery reduces the risk for both the development team and the client</em></strong></li></ul><p>If a potential client pushes back against a Discovery Phase and demands a quote for the entire development phase up front, it becomes clear they may not be a good fit. It also shows a development team that they do not have a strong understanding of the process required to develop a hardware product. These actions indicate they do not value the time and expertise that a development team brings to the table. A development team should strive to provide the most accurate quotes or estimates. Doing so, without the adequate time, nor resources invested up front, makes it incredibly difficult to arrive at an accurate scope of work. It also inhibits a development team’s ability to truly understand the challenges a client is experiencing.</p><p><em>Wade Cunningham is the Program Manager at </em><a href="https://www.glassboard.com/"><em>Glassboard</em></a><em>, a hardware focused product development company.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6fbf0c886794" width="1" height="1" alt=""><hr><p><a href="https://medium.com/glassboard-blog/discovery-phase-what-is-it-6fbf0c886794">Discovery Phase — What is it?</a> was originally published in <a href="https://medium.com/glassboard-blog">Glassboard Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>