5 steps on the way to success for your startup

— gerecke

At the beginning of the year, our colleagues from the RealIZM blog wrote an article about the beginnings and challenges of SAF. You can read it here.

In the following, we have already extracted the quintessence - 5 reasons why projects have failed in recent years - so that you can do better and make your startup a complete success.

Without documentation you will fail

A central aspect that small teams in particular often neglect at the beginning is documentation. It is the be-all and end-all and forms the basis for the future success of the project. Documentation is not sexy, but it is essential!

The mantra is: When something has been tried, whether it worked or not, write it down! It saves an enormous amount of time and also frustration if it is comprehensible what has already been tested and if it is documented what has proven successful under which conditions. It must be clear in each team how documentation is to be done.

Know the path you have taken

Over time, a project changes. Many teams often turn away from their original core idea for funding reasons. It is therefore important to understand why one left the originally planned path at a certain point.

View electronics through the user's lens

Numerous projects fail due to a lack of usability. To develop a successful product, you need the understanding and time to design, implement, test and, if necessary, further develop prototypes from an application perspective.

Know your dependencies

In the initial euphoria, little attention is paid to the question of the availability of components and parts and their delivery time. As a software developer, you need a computer as equipment. As a hardware developer, you are dependent on suppliers and the availability of certified components, parts as well as materials.

Define your product as early as possible

While interventions and adaptations of a software code are (theoretically) possible at any time, so-called redesigns of hardware are much more difficult and time-consuming. In the first product sketch, a Bluetooth connection may not play a role. However, if you already know that this will be an important requirement in one of the next product stages, it is advisable to include this option on the PCB from the very beginning or to provide for it right away.

If you take these points into account, nothing will stand in the way of a successful start with us as the SAF team. We are looking forward to hear from you and to let your ideas become reality.