Here is a question that I answered by e -mail from which From the concept to the start: What does it take to build and send a new device Podium discussion. We share the answer in our blog to make it available to a wider audience.
For the context, I pointed out during the discussion that a gateway to publish your product is that you must have a clear idea of what is “done”. If you do not know what “done” looks like, you can move the goal posts further and delay the ship date. It can also bring you into difficulties from the production page – you can hurry to build devices before you are close to “done”, which sits in a warehouse until your software is ready. Your company would have saved the construction and storage costs and spent more time refining the hardware.
Do you have strategies to ensure that you achieve this goal of “finished” and determine what this critical way is and how you make sure that you always work towards?
There has to be something in human nature that prevents us from defining what “good enough” actually is before we make an effort. On the whole, we fear that the requirements and criteria will be assessed against which we postpone the risks and open questions as late as possible. In this way they end up in the hellish situations that we have all experienced – constantly changing goal posts, only shift critical studies to find out that what we have on the way will never work, and the product direction after creating a series Functions that are, turning is now unnecessary, and adding new feature inquiries late in the game.
There is a greater challenge than creating precise estimates and tasks in creating schedules. You simply cannot plan the work if you have not decided what you build if you have open risk factors if you don’t know all the steps ”looks like. If you don’t know what you are building, you are ultimately not ready to build it. They research and research; You still have no product that is ready to develop and produce on a scale.
In my experience, the team always knows what the difficult/risky/unknown parts of the system are. We only ignore this in favor of “progress” by first addressing the well -known/simple/fun areas. We hope that the difficult/risky/unknown parts somehow dissolve if we move to them. The risk of taking this is that you only find out that you build the wrong At the end. It is difficult to recover if you have already spent millions of dollars producing devices and salaries.
And yet we always see how this pattern is before dangers. So much that three of the first four mistakes in our series described, A look at ten hardware start -up errorsRelate to what I have described above:
It’s okay before you have all the answers. Sometimes they have to start to get answers to become obvious. Some details are further developed when the system is developed and used. But I would like to say it again: If you find out strangers, the open questions should be closed first. The critical characteristics from which the product depends should be completed first. And surely these should all be addressed before You commit to manufacturing data.
References
- From the concept to the start: What does it take to build and send a new device
- A look at ten hardware start -up errors, part 1: Process
Another symptom of this error is that teams tend to open problems and open questions throughout the project. The problems postponed are often of crucial importance for the design and functionality of the product. Common hardware problems such as thermal management and wireless connectivity can advance the need for important revisions. Large software risk ranges are postponed until late in the program, which triggers last-minute firefighting exercises and extensive descriptions. Both situations lead to delayed product ship data and the need for additional NPI Development builds. Saving the difficult questions for later is never a profit strategy, even if it may feel like it is saving time.
Engineers must have a feeling for the entire product to effectively design the hardware and software systems. Requirements also serve as a metric with which teams can evaluate the compromises between design options. When teams try to build a new product without determining the prerequisites and creating the front, open the door for repeated redesign efforts and frustrated engineers. Systems without documented requirements are subject to strong change winds of product designers. The constantly changing feature inquiries lead to the restructuring of the systems. Make sure your team has a handling process requirement Change the inquiries and convey the final requirements to the entire team.
- A look at ten hardware start -up errors, part 2: schedule and focus
When companies rush through the various hardware creation of milestones, you generally learn that the ship date has to be delayed because the software is not finished. Millions of dollars of capital are bound in stock that cannot be sold to customers while the developers still fill out the software. Weeks and months pass while the developers complete the software, and CM Payment penalties will accumulate in the form of memory and shipping delay fees.
The teams have to rely on the product plan on the development of the entire ecosystem, not just the EE And ME Components. Your team needs enough time to test the designs, identify improvements and to include changes for the next milestone.
In almost all cases of a shipping date that we met, the blame was the guilty of software. If you rely your schedule on the functions of your entire ecosystem and team, distribute your hardware building. Your hardware team has time to validate and refined the design, and the quality of your hardware increases. The hardware team can also benefit from time to design and validate the accessories between important system builds.
- Manufacturing devices