Engineering Project Planning and Problem Solving
Engineering projects follow a structured cycle: define the problem and constraints, research, generate and evaluate options, plan, make, test and evaluate. Candidates must understand design briefs, specifications, constraints and criteria, and tools such as Gantt charts, flowcharts, work schedules, bill of materials and risk assessments.
Problem solving should be systematic: identify the root cause (using techniques like the 'five whys' or cause-and-effect analysis), gather data, propose solutions, test, and review. Understand the difference between a constraint (a limit that cannot be changed, such as budget or safety standards) and a criterion (a desirable feature used to compare options). Evaluation matrices weight criteria to choose between options.
Traps: jumping to a solution before defining the problem; confusing constraints with criteria; ignoring testing and evaluation; and forgetting to record modifications and reasons (traceability).
Rule of thumb: every project decision should be traceable to the brief, a constraint, or test evidence. Worked example: a bracket fails in service. Rather than thickening it immediately, use the five whys: why did it fail? Cracked at the weld. Why? Undercut defect. Why? Wrong current setting. Why? No welding procedure specified. The root cause is a planning gap, so the fix is a documented welding procedure, not just a thicker bracket.