In one line: A year-long, sponsor-backed engineering project that each candidate leads inside their own company. It is where technical depth, business value and leadership are practiced together and judged together.
Core idea
The program’s capstone is not an exam but a real project. Each candidate proposes, plans and leads a significant engineering effort for an industry sponsor, usually their employer. The project is supported by a program mentor, a sponsor representative and a faculty advisor. It is deliberately designed to exercise everything else in the program at once: the product development toolkit, the scientific foundations, and the leadership capabilities.
Reviewers judge a proposal on six things:
- Significance: the problem matters.
- Engineering depth: the solution is substantial engineering, not routine work.
- Science: fundamental principles are visibly applied.
- Leadership: the candidate will have to lead, not just execute.
- Feasibility: it can realistically succeed in the time available.
- Impact: the sponsor will be measurably better off.
How it works
The arc of the project:
- Concept and selection. Find an opportunity that matters to the sponsor and can be answered with the blunt test of so what, and who cares? (see Opportunity Identification).
- Early phase gate to check direction with mentors before full commitment.
- Formal proposal, which reads like a funding request:
- an executive summary that sells;
- a one-page Product Mission Statement;
- market and impact assessment, with customers, needs, and return on investment;
- the technical approach, with Product Specifications and a verification and validation plan;
- a project plan, with statement of work, schedule, budget and risk;
- leadership goals and team staffing.
- Progress reviews, including a short “no media” pitch: five minutes with no slides or props, just a clear explanation of the project, its value, its technical depth and its leadership component.
- Final paper and presentation, with a sponsor-approved statement of impact, results, a leadership self-assessment and recommendations for future work.
The business case. Companies choose among many possible investments, so a project must show its strategic and financial value in the sponsor’s own terms (see Product Development Economics). Even an informal “gut” approval rests on someone’s judgment of value against cost.
In practice
Most of what makes these projects hard is not technical. Typical challenges include:
- securing funding that spans fiscal years;
- influencing senior technical staff and stakeholders outside your chain of command;
- working with partners at other sites or organizations;
- operating inside a development process that is itself still being defined.
The project is where Influence Without Authority, Managing Up and Monkey Management stop being theory. The proposal structure doubles as a reusable template for pitching any internal project.
Questions to ask yourself
- Can I state my project’s value to the sponsor in one sentence that a non-engineer would care about?
- Which leadership capability will this project stretch the most?
- What evidence will show, at the end, that the project made an impact?
Connections
- Toolkit it applies: Product Development Process, Product Mission Statement, Product Specifications, Work Breakdown Structure, Product Development Economics, Risk Management.
- Leadership it tests: Influence Without Authority, Managing Up, Monkey Management.
- Capabilities exercised: Realizing the Vision, Vision, Initiative, Communicating and Advocacy.
Sources
- Program challenge-project proposal and final-paper templates, review rubric, and business-case guidance; no public source.