This is the bridge from student to practicing engineer. The room just finished the program; some of them will confuse that with being ready to run a project alone. Your job is to draw the line between the two, hand them the tools for the first 90 days, and close the program on Michael's letter. Don't rush the ending. The last thing they should feel is that the work is worth doing, not that class is over.
| Segment | Min | What happens |
|---|---|---|
| Finishing isn't ready | 6 | Open on the hook. Finishing the program means you understand the methodology. It doesn't mean you can run a project alone. Ask the room which they think they are. Let the honest answers sit. |
| The first 90 days | 12 | Walk the three windows: shadow and verify, lead the calc and shadow the customer, lead the project and support in the room. Use the readiness-ramp figure. Stress that the point is building judgment, not proving it. |
| Don't run alone yet | 10 | Walk the triggers, then land the rule over them: if you're not sure it belongs on the list, it does, ask first. Don't re-teach the math behind each trigger. The skill is recognizing it and asking. |
| Readiness criteria | 8 | Five observable criteria, not a calendar date. Drive to the one that matters: can they name what they don't know before someone asks. That's the tell for whether they'll ask for help in time. |
| The escalation map | 6 | Four categories: engineering and calc, customer escalations, pricing and margin, controls and WMS. Have each student fill the categories now and leave the names for their first week. Categories today, names later. |
| The eight habits | 10 | Fast, high-energy pass. Read all eight aloud, one line of why each. These summarize practices from the whole program. Tell them to build the habits in from the first project, because they're harder to add later. |
| Forest, Capstone, the letter | 8 | The program forest in a minute. Point them at the Capstone as the solo run. Then read Michael's letter together to close the session. End here. Don't add logistics after it. |
| Total | 60 | This is the last lesson. End on the letter, not on housekeeping. |
The closing letter is personal and deliberate. It's the only place in the whole program where Michael speaks directly to the student rather than through the lesson format. Acknowledge that when you get to it. Read it aloud, or have the room read it in silence, but don't analyze it to death. Let it land.
Then use it as the launch point for the Capstone briefing. The letter ends by sending them to the Capstone and then to a real project. That's your handoff. When the last line is read, point the room at the Capstone and let the session end there.
Four failure patterns show up in this lesson. Drive each one back to the same test: can you do the work without being caught, and can you name your own edges.
Run the readiness self-assessment against Riverside, the project the room now knows end to end. Ask, honestly, could you run that solo, and where would you still ask? Go criterion by criterion. Have each student fill the escalation map with categories now and names later, and draft a first-90-days plan.
Steer them to discover, on their own, that the criterion that matters most is knowing what they don't know. Don't tell them. Ask. Put a project scenario in front of them and watch who names their own uncertainty before you point at it. Those are the ones building the right instinct.
Question 1 (testing the readiness claim). Test it against the five observable criteria, not the calendar: the Product Spec Calc run correctly on three live projects with the right binding case identified; a scope that held through the proposal; an unexpected customer question handled without help; articulating what they don't know before anyone asks; and a mistake caught and corrected before it reached the customer. Ask for specific evidence on each: which projects, which numbers, what they'd do differently. The telling criterion is naming what they don't know unprompted. An engineer who can find the edges of their own knowledge asks for help at the right time; one who can't won't ask until it's too late. Watch for answers that lean on confidence or the calendar. Ninety days is a window, not a graduation.
Question 2 (two triggers on one project). Both triggers sit on the do-not-run-alone list, so the rule over the list applies: ask first, before the proposal goes out. For the aggressive rate, run the calc, document where the stated rate sits against what the mix can do, and take it to the engineering-and-calculation contact; a rate the system can't reliably hold shows up at commissioning, not at signing. For the new vertical, shadow someone who has worked it before taking the lead, and bring in the customer-escalations contact if the conversation could shift scope or commitments. Strong answers name both escalation categories and flag before proposing. Watch for students who'd proceed because each concern feels manageable alone; two triggers on one project is more reason to ask, not less.
The letter on the student page is copied from the source transcript, not retyped, and isn't contracted or modernized. Its cadence and repetitions are intact. Three edits are applied per the Part VIII controller ruling, and are the only changes to Michael's words:
All three are documented so Michael can revert any of them before ship. Change nothing else in the letter on your own.
The project-folder habit you've been reinforcing since Lesson 1 pays off here. A student who lived the documentation discipline all program arrives at the Capstone with most of the package already built. The readiness self-assessment and the filled escalation map are the last two project-folder artifacts, and the students who kept their notes will assemble them in minutes while the others reconstruct from memory.
Don't reveal the payoff. Let them find it when they open the Capstone and realize how much they already have in hand. Your only job is to make the readiness self-assessment and escalation map feel like normal professional artifacts, the same way you framed the project note on day one.