Engineers are trained to identify, analyze, and solve technical problems with scientific method. Leadership asks for the same discipline on messier objects: team dynamics, stakeholder conflict, ambiguous requirements, and business constraints.
Without that transfer, engineers solve the local technical puzzle and miss the problem the organization actually hired them to close. Soft-skill problem solving means naming the real constraint, involving the people who live with the outcome, and choosing a solution that will survive contact with the calendar.
This chapter treats problem solving as a leadership practice: define the problem with the customer in the sentence, generate options, test them against cost and people, then decide.
Lessons
- A well-named problem is already half-led.
- The first solution is often the engineer’s favorite, not the organization’s need.
- Involve the people who will live with the fix before you fall in love with it.
Questions
- What problem are you solving that the customer cannot feel?
- Whose definition of the problem have you never asked for?
- Which current fire is a symptom of an unnamed system issue?
Rewrite the problem
- Take a live issue. Write it as a technical problem.
- Rewrite it as a customer, cost, or team problem.
- Show both versions to a peer. Ask which one is actually true.