Problem Solving Framework
The Engineering Problem-Solving Framework
Engineering problems are rarely solved by simply guessing an answer. Because errors can lead to catastrophic failures, engineers use a structured, highly disciplined approach to organize information and execute calculations. This framework is essential for both accuracy and peer review.
1. Given (The Inputs)
The first step in any engineering calculation is to explicitly state all the information you already have. This includes reading the design brief, specifications, or field measurements and writing them down with their proper units.
- Why it matters: It prevents you from repeatedly searching for numbers and ensures you are using the correct starting parameters.
2. Find (The Objective)
Clearly state what you are trying to calculate. Are you looking for the maximum stress? The required pipe diameter? The total cost?
- Why it matters: Defining the objective prevents you from calculating useless information and keeps the process focused.
3. Assumptions
Real-world problems are messy. Engineers often have to make simplifying assumptions to make a problem solvable. For example, assuming a material is perfectly uniform, or ignoring the weight of a very light cable.
- Why it matters: If your calculation fails or is questioned later, the assumptions explicitly tell other engineers why you chose a specific path. If an assumption is proven wrong later, you know exactly what needs to be recalculated.
4. Known/Unknown Analysis
Before doing math, evaluate what you know against what you need to find. This bridge determines if the problem is solvable. If you have three unknowns but only one equation, you must either make an assumption or find more data.
5. Equation Selection
Based on the Knowns and Unknowns, select the governing physical laws, codes, or formulas. Write the raw equations down before plugging in any numbers.
- Why it matters: Writing the raw equation allows a senior engineer to instantly verify that you are applying the correct theory, even before checking your arithmetic.