Try to imagine the big picture, from the fact that components are to be procured, to how the user of the product should get it in hand, and how it should be handled practically. Including also the steps between, in matters of distribution and logistics, registration and eventual software and communication activities.
From such an analysis, new perspectives often emerge about what the real challenges are to achieve success.
Early in the development work, bringing in thoughts about how production should take place, how requirements for labeling and traceability should be met, and how the product should be packaged and distributed, provides a leverage in the work with a large exchange on the effort against how the outcome will be.
Here there are often both regulatory requirements such as CE marking or industry-specific requirements as for medical products. There are also demands from users, both direct and indirect, who make demands based on how the product is to be used and its function in a larger perspective. These can be more difficult to get a handle on and require analysis by, for example interview users and test in splendorinken.
Acomprehensive grasp of the requirements is one of the basic conditions for successfully achieving the goal.
Production technical requirements can advantageously be determined with the IPCs' various classifications; Class 1-3 for reliability and A-C for manufacturability (IPC-222X series), where requirements are aimed at both developers and manufacturers and are a good basis for setting levels on how the work should be run.
Of course, the market's requirements for design regarding color and shape also have an impact, something that developers not too rarely become aware of.
Set a realistic schedule by contacting people with experience in the field. They can often give a hint of the scope and of the task to be solved and estimate a hypothesis about time consumption.
It is rarely good to set up an over-optimistic schedule in the belief that it will speed up the project, rather it can instead become a disruptive moment that leads to rescheduling and extra work.
All efficient development and manufacturing is based on structured documentation. Think through before starting what will be needed. It's often more than you initially think.
A document overview, preferably graphic, should be established as early as possible in order for the work to be planned and carried out in an efficient way. It is easy to get lost in unstructured documented products.
A basis should be established for item numbering, nomenklatura and how revisions are to be named and handled. There are always changes, and it is essential to have the ability to track them.