Or: How to use facts!There is a philosophy of engineering that states:
If you need or can make a choice or any kind of decision, then you have not collected enough data. The intent of the philosophy is to argue that if you fully understand a problem – the constraints, the valued attributes, the relative value and cost of each attribute and each failure mode – then there is only one solution. And if you find you need to make any kind of decision – as opposed to completing an analysis – then you need to collect more data. This is similar to the white hat thinking proposed by Edward de Bono, where one focuses on collecting facts and data. De Bono noted that this was very much a Japanese way of thinking – collecting facts as opposed to arguing for one’s point of view. It was argued by others that this was the approach the Japanese used when they dominated the automotive and other industries in the 1980s and 1990s. They understood exactly what the customer wanted and valued, the cost of each option for satisfying those wants and values, and the opportunities for reducing those costs. With all that in hand, the solution would become obvious. Let’s now consider this philosophy further to assess when it would be viable, when it might be desirable but not practical, and what it could mean for you and how it could improve your engineering. When it’s viable – When you have time and money This philosophy is viable when you can afford to understand the problem fully. If you know what the user values, the constraints, the likely failure modes and the cost and performance of each alternative, then the weaker options should eliminate themselves. What initially appeared to be a decision becomes an analysis. However, obtaining that understanding can take time and money. You need to speak with users, consult the people who will manufacture and maintain the system, complete analyses and perhaps conduct experiments. You therefore need an organisation with sufficient resources and an appreciation of the value of this work. It’s worth noting that not all large organisations with the necessary resources appreciate its value – that’s a result of culture. When it’s impractical – You’re in new territory The philosophy becomes impractical when the required information does not yet exist. Think start-ups or the need to get to market before a competitor. You either lack the resources or you lack the time. You don’t ignore the facts you have, and you don’t choose to collect nothing. Instead, you work with what you have, make the best decisions you can and be ready to respond when you discover that you have made a mistake after proceeding at risk. What it means for you – Do you at least try to use facts to guide your thinking? After reading about the two cases above, how do you deal with the need for facts?
You should try to give every decision some factual basis. This could come from customer research, user research, analysis, hand calculations, simulations or whatever else is applicable. And when you lack the data and can’t obtain it, be honest with yourself and others about the possibility of things going wrong and corrective action being required.
0 Comments
Or: Scientist, Drug dealer, Hitman, Engineer
You might have seen the bit by Don McMillan (the engineer who became a comedian) about what it takes to be an engineer.
Take a look if you have not seen it. It’s only a minute and it is funny.
There is, however, something that this video raises that is noteworthy.
The notion of engineering being quick and dirty. I think Don McMillan is right when he compares engineering to science. Especially the type that leads to a Nobel Prize – we just can’t wait that long, most of the time, for engineering solutions. It’s worth noting that we had steam engines powering the industrial revolution before we understood how they worked. If we always waited for the science to be complete, then engineering would not have pushed society along as fast as it has done. Still, some engineers, I have found, push the quick and dirty aspect more than is ideal. You can certainly progress a solution to an engineering problem without obsessing over some of the academic questions. And you do sometimes need to start solving a problem to sufficiently understand it. Nevertheless, your solution should still be sufficient. Sometimes that can mean near enough is good enough. But sometimes the engineering solution is the optimised one. Especially when you are in a competitive industry – due to commercial factors, the nature of the challenge, or maybe regulatory needs. And in this case, while you are not pushing for a Nobel Prize, you need to ensure you have been thorough. So always be mindful of how refined your solution needs to be given the nature of the challenge and its context. A sequel to “The Reason Engineering School Let You Down”
The last article I wrote for this newsletter elicited a lot of responses. It is the most read and commented upon article in the series thus far. That tells me that many of us have a deep interest in the education and training of engineers. It also revealed something else – many seemed to assume that if you do well on the exam, then you understand the respective theory.
I am going to explore that assumption more in this article: Do good exam marks really mean good understanding? It’s all on the surface. When I was an academic and involved in education research, I was introduced to a phenomenon called surface learning. It is where students study to pass the exam as opposed to studying for understanding. We all probably have some experience doing this, where we drilled questions (maybe even used Schaum’s) or we remembered things. Or we know a fellow student who would get good marks, but never seemed to actually understand anything. That’s all surface learning. You can get away with this when the exam is set such to allow for this. And many exams are like that. They don’t assess understanding, just your ability to drill problems to pick up on the procedure and repeat it at speed. As an example of how pervasive this is, take the time to watch the video below. It features Eric Mazur, a physics lecturer, talking about his students and how shocked he was when he assessed conceptual (read “actual”) understanding after the first year of physics.
Some key points from the video:
Surface learning isn’t just about the student it is encouraged by most exams in engineering courses around the world. As I mentioned in the previous article: many exam questions will list only the variables needed to find the answer. In such a scenario, students only need to recognise the pattern (or the recipe). This is why grades don’t always (and often don’t) reflect understanding. The exam format can encourage procedural fluency at the cost not conceptual understanding. But what to do about it now? If you would like to improve your conceptual understanding of first principles, and you should, then one of the best sites you can go to is Arbor Scientific. They offer numerous teaching resources that you can sign up for, but they also have a great conceptual questions page - https://www.arborsci.com/pages/next-time-questions. Go check them out and get the resources once you are done. I liked the double boiler question and the bikes and bee question. See which ones get you thinking or reveal your lack of understanding so you can improve it. Before I finish though, I’d like to ask: what conceptual understanding tools do you know of? I am always keen for more and others here can benefit from them too. Or: Knowledge; what is it good for? If you have not seen it yet, then take a moment to watch this excerpt of an interview with Barack Obama on how to get things done. He starts off by saying that getting things done is what’s important. He seems a bit flippant at first - surely that’s a motherhood statement: you need to get things done. But then he digs deeper into the attitude common to those who do get things done.
He notes that there are people who look for reasons why things can’t be done. And that there are those who look for ways to overcome the challenge. What’s interesting is that he notes the people in the former group are smart and well-educated. What’s also interesting is that he notes those who can make things happen do not see the solution straight away - instead, they say “leave it with me.” The reason why all this is interesting is that as engineers, we are typically well-educated. That means we could easily fall into the first group. Where we use all our knowledge to identify all the challenges that would make a proposed goal unattainable. However, as engineers, we should be in the second group. We should have confidence in our ability to explore the problem with first principles to better understand it, find opportunities through systemic thinking, and then reframe the challenge so it becomes something we can solve. Given that as engineers we could fall into either group, the thing that determines the group you fall into is your attitude. In my book I talk about how sometimes the negative attitude can help you find risks. But you still need to have that attitudinal shift to the positive - especially in the face of uncertainty that many engineering problems can exhibit. To use Edward de Bono’s hat paradigm, you need to take the black hat off. So be mindful of your attitude when you are presented with a problem. That way you can be an engineer who does indeed get things done - and be known as such. |
AuthorClint Steele is an expert in how engineering skills are influenced by your background and how you can enhance them once you understand yourself. He has written a book on the - The Global Engineer - and this blog delves further into the topic. Archives
October 2026
Categories
All
|


RSS Feed