“The design brief is a dynamic document, and it’s frequently updated throughout the project whenever you discover new insights or make a design choice.”
“Are we doing it to keep up with the competition? Are there new trends to follow? Has the market changed? Are there new technologies that can make our products even better? The motivations can be many but are essential to articulate.”
“Which are most important, and why are they relevant?”
“Never forget service workers, maintenance specialists, or other users that come in contact with the product. Use methods like Customer Journeys or product timelines to identify all user groups relevant to the development of the product.”
“Remember, the buyer and the user are not necessarily the same. They often have different needs, requirements, and desires for the product, which do not always pull in the same direction.”
“Should the product be integrated with other products or systems? Are there any existing standards the solution must follow?”
“Think of all the things that are most likely to go wrong and describe them. It will make it easier to develop easy-to-use solutions and, more importantly, is not misused.”
“Should it be handheld? Are there any buttons? What features do you use most often? Do you wear gloves? Is it used outdoors? Should it be paired with a mobile phone? You have to consider many interactions.”
“We often do this through workshops, user involvement, and expert and specialist interviews.”
“User guides, cables, wires, connectors, spare parts, bags, straps, storage box. Think about it in the design process and the requirements it entails.”
“It is easier to relate to examples than it is to say: I want a simple and functional form, which must express robustness and at the same time must fit into the living room. Building a common vocabulary about shape and style makes it easier to communicate.”
“The heaviest components must be at the bottom. The battery must be replaceable. These are examples of conditions affecting the product architecture.”
“If so, determine it at an early stage, as the choice of components in itself defines requirements for the product regarding weight, placement of components, selection of materials, and many other things.”
“What should the product cost the customer, and how much must it cost to produce? This information is crucial for many reasons. But it especially concerns material selection, production methods, and timeframes.”
“Know what is already on the market and use it to your benefit in the development process – whether it is to be inspired, to innovate, or differentiate your product.”
“Remember to state the uncertainties and risks in the project. Then they are easier to accommodate along the way.”
“However, it would be a shame to base a project on assumptions, which later turns out not to be correct. It wouldn’t be the first time in design history. So pay attention to your assumptions and test them on an ongoing basis.”
“Idea development, design, production, prototyping, testing and approvals, marketing, sales, transportation, logistics, holidays, and more. A timeframe from idea to market in 8-18 months is not unusual for a relatively simple product.”
“An early estimate is a good starting point. In total, launching a brand new product can cost anywhere from €25,000 to several million.”
“From material selection and production methods to life cycle, climate impact, recycling, servicing and disposal – and much, much more. Remember, like everything else in the design process, it is about finding the right compromises based on the priorities you have chosen.”
“You can implement some ideas, while you can put other ideas to use at a later time. Maybe the great idea for the next product pops up in the development of the current project – remember to save it for later. Ensure the project has a strong foundation and that it’s not derailed by a sudden sales opportunity requiring just a few tiny changes.”
“Remember to always ask questions along the way.”