Complex problems deserve complex solutions.
When we meet a person we have not met before, one of the first questions we often ask is some form of “What do you do?”
Clever marketers have learned how to structure headlines to get us to click on a link.
You are a Genius. How does it feel to read those words about you? Pretty good, eh?
What are the characteristics of a Pretty Good Problem Solver?
When you view the world from 10,000 feet, people on the ground look like ants.
Would you expect to win an Olympic competition with no practice and training? Of course not, that would be ridiculous.
I believe a new standard is coming for the behavior of leaders.
The process of solving certain problems requires a physical sacrifice by the problem solver.
It is very easy to tell new engineers that they should learn from their mistakes, but often we struggle to explain how we should avoid those mistakes in the future.
Have you ever watched or read a story of an air crash investigation?
You will be better than 90% of your competition, if you just follow this one rule: Write it down.
We recently discovered a bunch of conversion errors in the Kindle ebook version of the second edition of An Engineer's Guide to Solving Problems.
Some of you might have noticed that recently this website was not available for several days.
The most powerful force in the universe might just be inertia.
The words family and familiar have a common root and surprisingly similar meanings.
Thinking is Hard. There are lots of different kinds of thinking, but this post addresses the thinking associated with making choices and decisions that affect any project or problem-solving effort.
Sometimes we simply cannot "solve" a problem to our own satisfaction. There are many reasons this can happen, but these reasons probably do not mean that your problem-solving method was bad.
Some people worry that documenting and sharing what they know makes them less valuable. I present arguments that sharing increases your value.
The DoD Principle is easily summed up with the short statement, "If it's not worth documenting it's probably not worth doing."