In one line: An engineer is someone who turns knowledge into working things and owns the result, so education should be judged by whether it produces people who can do that.
Core idea
The program opens with a deceptively simple question. Labels like scientist, technologist, artist or professional each capture a slice of engineering but none of them says what an engineer is expected to do. The founder’s answer starts from the user’s side: look at what industry actually needs engineers to accomplish, and work backward to the knowledge, skills and attitudes that make it possible.
On that view, an engineer is defined less by a body of facts and more by output. An engineer creates a product, system or process that functions in the real world, under real constraints of cost, schedule and physics. The engineer takes responsibility for it working.
How it works
- Knowledge is necessary but not sufficient. School supplies analysis; the job also demands judgment, persistence and the habit of finishing.
- Careers climb a ladder of responsibility. Early work is a well-defined piece of a larger design. Over time, an engineer is trusted with larger pieces, then with the architecture, and eventually with the whole product and the people building it.
- Technique is not content. Tools, and especially computers, amplify an engineer, but they do not replace understanding what the design must do and why.
- Engineering lives inside a company. Design, manufacturing, test, marketing and service form one connected tree. An engineer who sees only their own branch makes locally good, globally poor decisions.
In practice
The question works as a mirror at any career stage. A new design engineer can ask whether they are learning to own outcomes or only to complete tasks. A senior specialist can ask whether their depth is reaching the product, or stopping at the analysis. The idea also explains why the program spends so much time on how things are taught and practiced: the aim is to form habits, not just to transfer information.
Questions to ask yourself
- What have I built that works because of me, and what did I own beyond my assigned piece?
- Which rung of the responsibility ladder am I on, and what would the next one require?
- Am I using my tools to think, or letting them think for me?
Connections
- Builds on: the program founder’s career and philosophy (Bernard M. Gordon).
- Leads to: Leader Attributes and Behaviors, the idea that engineering leadership is the next rung of the same ladder.
- Complements: T-Shaped Professional, because depth makes things work and breadth connects them to the rest of the company.
- Capabilities exercised: Realizing the Vision, Responsibility and Urgency to Deliver, Connecting Across Disciplines.