<?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 Randy Parmerlee on Medium]]></title>
        <description><![CDATA[Stories by Randy Parmerlee on Medium]]></description>
        <link>https://medium.com/@RandyParmerlee?source=rss-1483ea10e801------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*iIrHunqCWtZujm4YBgM_0w.jpeg</url>
            <title>Stories by Randy Parmerlee on Medium</title>
            <link>https://medium.com/@RandyParmerlee?source=rss-1483ea10e801------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 02:21:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@RandyParmerlee/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[Why Work with a Multidisciplinary Development Team?]]></title>
            <link>https://medium.com/glassboard-blog/why-work-with-a-multidisciplinary-development-team-c2ba6c9cfd0?source=rss-1483ea10e801------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2ba6c9cfd0</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[hardware]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[new-product-development]]></category>
            <category><![CDATA[electronics]]></category>
            <dc:creator><![CDATA[Randy Parmerlee]]></dc:creator>
            <pubDate>Tue, 05 Dec 2017 22:23:27 GMT</pubDate>
            <atom:updated>2017-12-06T12:55:39.151Z</atom:updated>
            <content:encoded><![CDATA[<h4>And what are the benefits</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UAyqG0Gnfic-qnj-399xXA.jpeg" /><figcaption>Product Development for Hardware can be a beautiful ballet, and at other times, a scrum. Having team members all push in the same direction can sometimes make the difference</figcaption></figure><p><strong>Let’s face it</strong>, if you’re looking to develop a physical product nowadays, it’s going to contain several different engineering disciplines (not to mention the non-technical roles needed). It’s rare we see a project that doesn’t require some combination of electrical, software, and/or mechanical engineering (and many others). Launching a new product, especially in hardware, requires balancing and managing a lot of resources. Most companies can’t afford the luxury of doing every single aspect of their product in-house, and in many cases is at a disadvantage to do so.</p><p>If you’ve made the decision to utilize outside resources for your hardware product development, it’s worth understanding some of the benefits of partnering with a single, dedicated Multi-disciplinary Development Team.</p><p><strong>Creativity and Innovation</strong></p><p>When your development team all lives under one roof, conversations and discussion tend to be more fluid and organic. There isn’t this virtual time barrier that usually comes from the typical email, wait for response, respond back, wait game. These delays can hinder the creative process, and derail the design thinking phases of your development.</p><p>That’s just the fluffy stuff. Hardware product expectations are becoming more and more demanding, requiring more features and functionality crammed into smaller and smaller devices. The integration and packaging of electrical and mechanical components has become more strenuous. How much room is there in the mechanical enclosure for a PCB? Is there enough clearance for this connector? Does the light pipe reach the LED? Will the battery get too warm in this location? Real time, face to face, discussions between the electrical and mechanical team are more than critical.</p><p>Hardware designs are utilizing microcontrollers and microprocessors more than ever. With the cost of these components declining, and the performance increasing, it’s hard not<strong> </strong>to put one of those parts in a design. Thus, deep interactions between software team and hardware team must happen to streamline PCB design. Can we move this address bus to these ports to simplify routing? Can we use the microcontrollers ADC (analog to digital converter), and drop the dedicated extra parts? Does the firmware need to monitor the switch mode power supply output?</p><p>In addition, you’d be amazed at how good mechanical guys are at solving electrical problems, or how electrical guys can spark (pun absolutely intended) an idea in the firmware team. Creativity and innovation can come from anywhere.</p><p><strong>Communication and Cohesive Vision</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1004/1*eeBw8_UevPWd5gM14jQmUQ.jpeg" /></figure><p>A huge problem that plagues nearly every development effort is lack of communication and cohesive vision. It’s usually the task of the project or programs manager to make sure everyone is on the same page. This is a daunting task, even when everyone is in the same building. If your team is scattered across the city or country, sometimes that cohesion can easily erode. Communication is essential to make sure that everyone’s efforts are for the same cause. Nothing is more frustrating than the electrical team getting nearly complete on a PCB design, to learn the mechanical team was asked to move some mounting holes, or remove an air cooling vent. I’m assuming I don’t have to mention the impact on time and cost.</p><p>Sure, a kickoff meeting with all the teams located in one spot at the beginning of the project can be a great start. Maybe physical meetings can be planned every other week or so. But as they say, the devil is in the details. And the details rarely get discussed in real time, during a planned meeting. What if that meeting is a week away, and you can’t continue forward until the issue is resolved? There’s that time impact thing again.</p><blockquote>We all know that we can attempt to sync up on our next Skype call, create another Slack channel, or spend 15 minutes trying to figure out what magic caused the phone system to drop calls again. But, a simple head poke in the room can get teams up to date rather quickly.</blockquote><p><strong>Get to Market Faster</strong></p><p>If it wasn’t obvious from the previous sections, having a dedicated Multidisciplinary Development Team can drastically increase your development time, thus speed to market. If teams are waiting on emails, or waiting for when the software team in Chicago is available to schedule a call with the hardware team in the Boston area, crucial market time is being eaten away. Markets vary, but we all know consumers have an attraction to the latest and greatest. Sometimes more the latest, than the greatest.</p><p>Developing hardware means at some point, you’re going to have to touch and hold physical prototypes. Each team is going to need to interact with these prototypes. That means, you could be shipping parts all over the place. Ignoring the potential risk in damaging/loosing parts or prototypes (dare I say expose your tech), the time alone can add weeks (potentially months) to a project.</p><blockquote>In today’s world, speed is everything. Sometimes being first, is better than being the best. The hardware startup landscape is littered with companies like <strong>Doppler Labs who created a genuinely great product but were beat to market by a much larger player like Apple.</strong></blockquote><p><strong>Cost Savings</strong></p><p>While there are many additional reasons for using a Multidisciplinary Development Team, the final one I want to mention, and likely most important one worth noting, is cost savings. We spoke about shipping risks, we spoke about misalignment in vision, we talked about speed to market, all things that have a direct impact on the bottom line. A lot of efficiency is lost when teams are not tightly integrated in the same process, which can be very difficult to achieve across multiple locations and between multiple different vendors.</p><p>It’s nearly impossible to find a one stop shop, that can solve every aspect of every product needs. That being said, the fewer amount of individual teams you have to manage, the more likely your product will find success quicker and faster than your competition.</p><p><strong><em>Randy Parmerlee is the CEO 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=c2ba6c9cfd0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/glassboard-blog/why-work-with-a-multidisciplinary-development-team-c2ba6c9cfd0">Why Work with a Multidisciplinary Development Team?</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[10, 9, 8, 7…WAIT, Are You Ready to Launch a Product?]]></title>
            <link>https://medium.com/glassboard-blog/10-9-8-7-wait-are-you-ready-to-launch-a-product-8bd32ec6bddc?source=rss-1483ea10e801------2</link>
            <guid isPermaLink="false">https://medium.com/p/8bd32ec6bddc</guid>
            <category><![CDATA[hardware-design]]></category>
            <category><![CDATA[hardware]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Randy Parmerlee]]></dc:creator>
            <pubDate>Wed, 04 Oct 2017 13:29:58 GMT</pubDate>
            <atom:updated>2017-10-04T13:34:45.341Z</atom:updated>
            <content:encoded><![CDATA[<h4>Questions you should be asking yourself before lift-off</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oIXVQngK0a01Nst2EGGs-A.jpeg" /></figure><p><strong>If If you’re contemplating launching</strong> into the world of hardware product development, there are numerous questions you need to be asking yourself. Having and initial idea, performing market research, developing functional product requirements, creating a working prototype, and then bringing the product to life through iterative design and development can be a long and costly investment. It can be longer and more costly if not managed appropriately. While the payoff of creating an incredible product can benefit many, the process should be entered into only once you’ve asked yourself — and your potential market — some serious questions.</p><p>While this article would be entirely too long to hit every permutation of every product we’ve seen, we will hit a few fundamental questions our team wants you to consider. These questions are not meant to discourage you from further developing your idea. Rather, they are meant to give you a head start, because any product development firm that you engage with will likely persist in asking the same questions, and expect answers.</p><h4>Questions To Ask Yourself:</h4><p><strong>Are you willing to see it through to the end?</strong></p><p>“Passion” is a word that’s often thrown around. Perhaps better words in this case are “devotion” or “persistence.” Any originator that wants to see their idea brought to life must work through all of the necessary steps — regardless of how mundane and unimportant they may seem. When it comes to developing a hardware product, no step should be hurried and no step is insignificant to the final product. That’s why the originators must have patience, perseverance, and yes, both passion and devotion.</p><p>This first question is important. If you are not willing to write requirements, talk to potential customers, make choices on product feature tradeoffs, then it may not make much sense to go through the rest of the questions unless you plan to hire someone to perform all of these necessary steps.</p><p><strong>Do you have the time and resources to develop a hardware product?</strong></p><p>As you’re probably already aware, developing a hardware-based product requires a fairly significant amount of resources, depending on the complexity of the product. If you do not already have an engineering team, the process requires you to work with a partnering product development company through all the development stages such as: ideation, discovery, definition, design, prototyping, testing and production. Each and every step of the process requires a commitment, both in terms of financial resources and perhaps more importantly, your time. Developing a physical product means that you must be readily available to answer questions and provide feedback throughout all aspects of developing your product.</p><p><strong>What are your metrics for success?</strong></p><p>What does success mean for you and all stakeholders involved? When developing a hardware-based product, it’s crucial to have realistic goals in mind for how you will measure the outcome. And while the journey ahead likely isn’t a one-and-done approach, it’s important to develop milestones and key objectives along the way so you know whether you’re on track or whether you need to ramp up marketing, work to establish partnerships, upgrade your offering, or abandon the project. Determine your break-even point, your profit margin and revenue requirements. These are all important metrics and milestones to keep in mind when you’re starting along the journey of launching a hardware product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*74I1yryXioyHIIksjeTDLA.png" /><figcaption>Do you have a process, and are you asking yourself the right questions?</figcaption></figure><h4>Questions to Ask The Market:</h4><p><strong>What makes your product idea better than your competitors on the market today?</strong></p><p>One of the important first steps in market validation is to search for existing and potential competitors. It’s vitally important to perform thorough research on your own to know and understand your market, even if a competitive analysis is included in your design firm’s process. How many competitor products already exist? What makes their product offering unique? How successful is their product? Have you read their customers reviews? What are their specifications? Where is their product manufactured? How do they market their product?</p><p>If successful competitors exist, that doesn’t necessarily mean that you should table your idea. In fact, in many cases it helps validate your market opportunity. It’s very possible that you could make your product better in some way, shape or form, or find an underserved niche. If a competitive product does exist, the key is to identify pain points that it doesn’t meet, and determine how your product will close that gap. Are there features that you could incorporate that would make the product more useful? Would your product be made with better quality materials? Could you sell the product for a competitive price? But beware, if your only differentiator is lower cost, please go back and check your numbers.</p><p><strong>Have you validated the product concept with the market?</strong></p><p>You need to ensure that you aren’t the only one that believes in the product. What good is a product that no one will want to use or purchase? Make sure to test your idea out on friends, family, experts and potential customers who will share their honest opinions. Getting honest feedback and insight from your close circle is an important step in the process of bringing a physical product to life — and fortunately, doesn’t cost a thing. However, a minimum level of research may not be enough to justify spending resources for a project kickoff. How will you ensure that your customers — especially if your product is very technical or is a niche product — will view your product as useful and a beneficial investment?</p><p>It’s critical to understand who your target market will be. Will you market to consumers or to businesses? Who will be the audience you need to influence and who will be the actual buyers? Once you’ve established your target market, it’s critical to validate your product with both those who will actually use your product AND those responsible for its purchase.</p><p><strong>What if your product is successful? Are you ready to scale with success?What then?</strong></p><p>If you made it this far, it may be prudent to plan for a successful product launch. When your product is ready and released to the marketplace, will there be a company behind it?</p><p>Creating a physical product is only just the beginning. While checking the boxes on all of the steps required to bring a physical product to life can seem like the finish line (and it is a major victory indeed!), you’re just getting started. Before you start the initial process of building your product, have you considered what comes after that? Do you have partnerships or designated channels in place to take the product to market? Will you sell and market the product yourself? What will the costs of taking your product to the industry entail? Do you have a plan for maintaining the required certifications, and ongoing product improvements and customer support? While the specifics don’t need to be perfected at the front-end, it’s critical to have a go-to-market plan in the works throughout the process so once your product is developed and market ready, you’re set up for long-term success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f2iKXMuHkXfuM-JFtjj-pA.jpeg" /><figcaption>It’s critical to have a go-to-market plan in the works throughout the process so once your product is complete, you’re set up for long-term success</figcaption></figure><p><strong><em>Randy Parmerlee is the CEO 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=8bd32ec6bddc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/glassboard-blog/10-9-8-7-wait-are-you-ready-to-launch-a-product-8bd32ec6bddc">10, 9, 8, 7…WAIT, Are You Ready to Launch a Product?</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>