{"id":4187,"date":"2016-04-07T09:32:25","date_gmt":"2016-04-07T08:32:25","guid":{"rendered":"http:\/\/www.solidapps.co.uk\/blog\/?p=4187"},"modified":"2016-04-07T09:32:25","modified_gmt":"2016-04-07T08:32:25","slug":"10-ways-to-reduce-product-development-costs","status":"publish","type":"post","link":"https:\/\/www.solidapps.co.uk\/blog\/2016\/04\/10-ways-to-reduce-product-development-costs\/","title":{"rendered":"10 Ways to Reduce Product Development Costs"},"content":{"rendered":"

\u201cHow do we make it cheaper?\u201d<\/em><\/p>\n

It\u2019s an all too familiar question. Engineers face constant pressure to reduce the cost of product development, and yet some \u201ccost-saving\u201d strategies are counter-productive, leading to increased costs and damaged projects.<\/p>\n

The thing is, in a competitive marketplace, there\u2019s no getting away from the question of cost. With as much as 60 percent of overall project cost determined during the concept stage, engineers must be able to wheedle out the cost-saving measures that work from those that don\u2019t.<\/p>\n

Here are ten tips.<\/p>\n

\"Screen<\/p>\n

Always simplify<\/strong><\/h4>\n

It\u2019s true what they say. There\u2019s beauty in simplicity.<\/p>\n

Some product development teams get a bit lost on the journey towards innovation. Before long, you have a product that is jam-packed with features, and while these products might impress fellow engineers, they can bamboozle consumers \u2013 who crave simplicity.<\/p>\n

In the May 2012 edition of Harvard Business Review<\/em>, Stefan Thomke wrote<\/a> the following on product design: \u201cDetermining which features to omit is just as important as\u2014and perhaps more important than\u2014figuring out which ones to include. Unfortunately, many companies throw in every possible bell and whistle without fully considering important factors such as the value to customers and ease of use.\u201d<\/em><\/p>\n

Always keep the end user in mind. When it comes to product design, less really is more.<\/p>\n

Concentrate effort in the planning stage<\/strong><\/p>\n

When you are on a tight deadline, it\u2019s tempting to rush through the planning stage and begin designing as quickly as possible. Not a good idea. Speeding through the planning stage is likely to get your project off on the wrong path, and the further you go down that path, the costlier your project becomes.<\/p>\n

Instead it\u2019s best to spend considerable energy at the start of a project clarifying the task, visualising the problem that needs to be solved and brainstorming ideas on how to solve it. Getting to grips with the project from the start will reduce the need for complicated, costly iterations, revisions and improvements later.<\/p>\n

But\u2026<\/p>\n

Don\u2019t stick rigidly to the development plan<\/strong><\/p>\n

Having a solid development plan is important, but treating it as a blueprint from which you cannot deviate is a mistake. New insights and ideas will be generated as you move through your project. New limitations will arise. Conditions will change. Remember that your plan is just an initial hypothesis.<\/p>\n

Repurpose old designs<\/strong><\/p>\n

Do you really need to design an entirely new product from scratch? Or can you repurpose parts from previous designs? With SOLIDWORKS you can build a silo of legacy designs that you can call on within a matter of clicks. In some instances, SOLIDWORKS can even automate parts of the design process by choosing the right elements for you.<\/p>\n

Collaborate!<\/strong><\/p>\n

Some people say there\u2019s strength in numbers. Others reckon too many cooks spoil the broth.<\/p>\n

Whichever side of the fence you fall on, collaboration in product development can speed your project through to completion. For small scale products, 3D CAD allows you to troubleshoot problems with fellow engineers through file sharing. And for larger, complex projects, concurrent engineering \u2013 where multiple engineering teams work in parallel to hit project milestones \u2013 allows you to interact quickly and move through a project as efficiently as possible. Co-locating your engineering and manufacturing teams is another way to use collaboration to grease the wheels of product development.<\/p>\n

Prune your marketing spend<\/strong><\/p>\n

Marketing costs always seem to turn out higher than you bargained for. With SOLIDWORKS you can generate photo-realistic images of your design. That means there\u2019s no need to wait until your product has been manufactured to begin marketing it. And, there\u2019s no need to pay for expensive photography.<\/p>\n

Reduce prototyping<\/strong><\/p>\n

Prototyping is essential to the success of any product, but the back-and-forth between testing a prototype, tweaking the design, building another prototype, tweaking the design ad nauseam<\/em> gets expensive. SOLIDWORKS allows you to simulate interferences and collisions between moving parts, but that\u2019s just the tip of the iceberg.<\/p>\n

You can perform all sorts of simulations, right there in the design suite: linear and nonlinear static, vibration, fatigue, thermal, optimization and nonlinear dynamics. You can compare the performance of different materials, and you can automatically calculate forces on critical components \u2013 such as springs and bearings.<\/p>\n

Using these simulations early in the design process allows you to optimise your design, raises the quality of your products and dramatically reduces the burden of real-world prototyping.<\/p>\n

Speed through to sign off<\/strong><\/p>\n

3D CAD software like SOLIDWORKS makes it far easier to share product designs with project stakeholders. No more posting 2D drawings that furrow your client\u2019s eyebrows. You can send CAD files electronically that allow all invested parties to visualise the product in 3D.<\/p>\n

Good project management<\/strong><\/p>\n

It\u2019s impossible to understate the importance of good project management, especially as it\u2019s where lots of product development teams fall down. A fallacy exists about the need to be busy; for lots of projects to be queued. Yet it can be counterproductive. When you feel like you have too many projects live at one time, you lose clarity. It becomes harder to prioritise. Feedback gets delayed. And, relatively, projects take longer to complete.<\/p>\n

Similarly it creates a pressure to \u201cget it right first time,\u201d which hinders creativity and thwarts innovation. There\u2019s nothing wrong with a full order book, but it must be managed by an expert who can strike a balance between keeping a development team busy and overwhelming them. Don\u2019t take on too much. Don\u2019t quote too low. Manage deadlines realistically. It will result in sharper focus and clearer priorities.<\/p>\n

Listen<\/strong><\/p>\n

No matter how strong your development plan, or how sturdy your prototype, there\u2019s always room for a product to be streamlined. Listen to manufacturers and those on the production line. It might be that removing an unnecessary function, or swapping a material, could shave a huge amount off your development and manufacturing costs.<\/p>\n

Over to you<\/strong><\/p>\n

How do we make it cheaper? By turning your back on the normal way of doing things. Focusing too hard on building efficiencies into the product development process too often leads to shortcuts that are counter-productive. You end up adding to a project\u2019s cost, rather than generating the savings that were intended.<\/p>\n

Real savings come from innovation in process, not just innovation in design.<\/p>\n

Originally posted in the SOLIDWORKS Blog<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

\u201cHow do we make it cheaper?\u201d It\u2019s an all too familiar question. Engineers face constant pressure to reduce the cost of product development, and yet some \u201ccost-saving\u201d strategies are counter-productive,… <\/p>\n","protected":false},"author":1,"featured_media":4189,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[25],"class_list":["post-4187","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-solidworks","tag-solidworks-2"],"post_mailing_queue_ids":[],"_links":{"self":[{"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/posts\/4187","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/comments?post=4187"}],"version-history":[{"count":1,"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/posts\/4187\/revisions"}],"predecessor-version":[{"id":4188,"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/posts\/4187\/revisions\/4188"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/media\/4189"}],"wp:attachment":[{"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/media?parent=4187"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/categories?post=4187"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/tags?post=4187"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}