Value engineer’s original idea


When a system or a project under the design review is based on the original engineer’s idea that fact should be explicitly acknowledged as an advantage. That’s right, put it into the “pros” section of the “pros and cons” list. In bold.

An original engineer’s idea could be a new invention but doesn’t have to be it. For example, it could merely be a suggestion to apply a well-known technique in a new way. An original idea, however, must excite an engineer or a group of engineers who suggested it. Ideally, it should excite the whole team (and the whole company and all the way to the customers). So why give it an advantage during the design review?

First of all, it is just plain not fair to compare an original design to a well-known solution without adding extra point (or more) to it. Give it a benefit of doubt! It is going to be a new territory, and, of course, during the design review, you are going to miss a couple of goodies which you will for sure encounter down the road while implementing it. At the same time, you’re most likely able to list all the pros and cons of the well-known solution.

By applying an original idea at the very least an engineer and the whole team will learn a lot more about the problem and will deeper understand the solution. You will have to think carefully about the requirements, as many of them will pose a serious challenge. On the contrary, by using a common solution many of those requirements won’t be even visible because they are “covered” implicitly. Similarly, you will spot more design decisions and understand available options when you have to work through them one-by-one.

An original idea gives a chance to make something better. Yes, it increases the chance of a failure as well. But if you are not in a special situation when the failure cannot be tolerated, I’d definitely optimize for the former. And, let’s be honest here, it must be a very rare project when no failure can be tolerated at any cost. Even in the spaceships, there are numerous of systems exist to handle minor and major failures to avoid jeopardizing the mission.

Make a loud statement that the original ideas are welcome and believed in, by explicitly acknowledging that each has an advantage to it from the start off. Show that you believe this team is able to produce the highest mark or better than the competitor’s results. It is incredibly important, especially for the high-profile teams.

Double the points (use italic font in “pros and cons” list) if the idea originated from the engineer who will be doing the implementation. She’ll work harder on it, which, when you trust your teammates, increases the chances of success.

When you decide to pursue the original idea, watch out for a couple things, though. First, the very fact of originality should not be the only or the biggest advantage that outweighs everything else.

Second, be explicit about when the experiment must end and when the “original idea” fact should be removed from the list of advantages. The latter, if you think about it, makes perfect sense in the broader context: the idea becomes less of an original nature after it was battle-tested and e.g. proven to be not the best. Try to set the boundaries and termination conditions ahead of time, however, to avoid postponing this moment too far, when you are already attached to the idea too much (and you will be).

In the very end, when the original idea succeeds do not forget to look back to reflect and be proud of your fearless team.


Follow @abaranau to not miss future posts.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s