But what about the not so obvious ideas? The Ideas that need to be sold, where people needs convincing? Those are the majority of ideas where there are benefits and drawbacks, depending on the perspective. Sometimes the idea is yours, and sometimes the idea was brought up by someone else, and you would like to push it forward. Here are a few points for taking into account on how to sell an idea.

Quoting the book: "

As he designs the first work, frill after frill and embellishment after embellishment occur to him. These get stored away to he used "next time." Sooner or later the first system is finished, and the architect, with firm, confidence and a demonstrated mastery of that class of systems, is ready to build a second system.

System design requires using many building blocks, from different schools of thought and using some imagination for mixing it all together in a system. Since there is a limit to the knowledge one person has, one must start to look for information in other professionals and to create the complete picture of the required solution.

This where the professionalism of the system engineer is shown, not by knowing the solution, but by asking the right questions!

The right questions are the ones that:

1. seek the problems with the interfaces
2. seek to understand how the basic principles interact
3. try to find out the why of the answer
4. are the most difficult to answer because they go beyond the basic assumptions
5. ask why

Since asking those questions is something that can be learned this is the true professionalism of a system engineer.

In the words of Jeff Atwood (coding horror):

"How lasts about five years, but why is forever."

Next post will discuss learning how to ask the right questions.