Lesson 31 is where the proposal package meets the people it was built for. The one thing every student must leave with: one set of documents serves a technical buyer, a business buyer, and a maintenance buyer at once, if you lead with outcomes and put the executive summary first. If they leave thinking presenting is persuasion instead of communicating the engineering and standing behind it, the lesson didn't land. Run the room live; don't lecture it.
| Segment | Min | What happens |
|---|---|---|
| Hook: three questions | 7 | Open cold on the hook: the person who evaluates the engineering and the person who approves the budget are often not the same person, and sometimes they're at the same table. Name Riverside's three seats and their three questions. Land the frame: one meeting, serve all of them, go as deep or as high as the room asks. |
| The three buyers | 14 | Walk what each seat is really evaluating: technical buyer (is the engineering sound), business buyer (is the investment justified), operations and maintenance buyer (can my team keep it running). Put the buyer-type table on the board. Make the room say what each one leads with and what each one challenges. Draw out the third seat that proposals forget. |
| Exec summary first + two summaries | 16 | Teach the structure: exec summary and outcomes first, system description after, limitations in their own section, calculations in the package not the narrative. Then run the two-exec-summaries exercise: one summary for Dana, one for Tom, same system. Compare a few aloud. The gap reveals who understands audience. |
| Present and defend (live room) | 18 | Run the three-buyer room. Three students play Dana, Tom, and Michael, each with one hardest question. A fourth presents and defends, leading with outcomes and going deep only when challenged. Push hand-wavers back to the matrix or the calculation. Do not tell them; ask. |
| Forest and Part VII close | 5 | Students commit the presentation and defense plan to their Riverside note. Close Part VII: the design is now a document three different people can act on. Name the boundary, Part VIII delivers it. |
| Total | 60 | Baseline session. Expand with the stretch options below if you have 90 minutes. |
The two-exec-summaries exercise. Have students produce two versions of the same executive summary from the Riverside scenario: one for Dana Merrill as the technical buyer, one for Tom Ruiz as the business buyer. The difference between the two reveals whether the student understands the audience. A student who writes the same summary twice hasn't read the room.
Then put both buyers in the room at once and have a student present a single opening that serves both. The right move leads with outcomes and signals the technical depth is coming, so neither buyer feels unserved. Watch for the student who tries to split the difference and lands a summary that's too technical for Tom and too thin for Dana. That's the failure to catch here.
Every one of these is the same failure: presenting one depth to a room that holds more than one buyer. Drive each back to read the room, then match the depth.
Run the three-buyer room live as the session's spine. Assign three students to play Dana, Tom, and Michael, each armed with one hardest question: Dana on why that sorter model and not another, Tom on the labor assumption behind the payback, Michael on whether his one technician can service it at peak. A fourth student presents and defends.
Steer the presenter to lead with outcomes and to answer Michael as honestly as Dana. Do not tell them which seat they underserved. Ask. Let the presenter discover it when the maintenance lead's question goes unanswered or the finance chair checks out during the controls detail. The grade is simple: did all three get their question answered at the right depth? Keep the misdirect rate honest at about three percent, and never invent the associate headcount or labor cost; the source withholds them, so a strong presenter asks Tom for the number rather than making one up.
Question 1 (VP and Director in one meeting). Structure the proposal exec-summary-first: two outcome paragraphs with no model numbers, then the system description for the Director, then limitations and assumptions in their own labeled section, with the calculations in the package but out of the narrative. In the presentation, open in outcomes for the VP, what the system does for labor and throughput, and signal to the Director that the equipment selection and controls architecture are next so they know their question is coming. Then go deep and defend the engineering from the layout, the matrix, and the calculations. Lead with outcomes. The reason: a business buyer who stops after page two still has the case, and the Director finds the depth exactly where they expect it. Strong answers name both moves, leading with outcomes and telling the Director their turn is coming.
Question 2 (the maintenance lead's one question). Answer Michael directly and honestly, from the maintenance section that addresses him by name, tied to the two failures he lived through: the pneumatic system that died when the shared compressor's air pressure dropped at peak, and the line where anything downstream stopping stopped everything. Name what the system requires to maintain, what his one technician needs to know, the recommended intervals, and how the design avoids both failure modes. No sales words. Why the seat is underserved: the operations-and-maintenance buyer doesn't sign the check and doesn't evaluate elegance or ROI, so proposals skip past him, but he's the person who decides whether the system survives year two. Strong answers refuse to reassure and give specifics; weak answers hand-wave or push it onto the vendor.
This lesson ends Part VII. Note for yourself, not the room, that the part deliverable is complete: the design is now a drawing every trade can build from, a business case the money can approve, and a proposal three different buyers can understand, presented and defended. It feeds forward to Part VIII, where the customer says yes and the work gets delivered.
This is where the project-folder habit pays off one more time. The presentation and defense plan isn't a document the student writes from scratch tonight; it's a project-folder artifact. A student who kept every Riverside note from Part I forward can source every answer the room asks for, because the sorter matrix, the sizing calculations, the confirmed one-second latency, and the business-case inputs are already saved and labeled. When Dana challenges the model, the matrix is in the folder. When Tom challenges the payback, the inputs are in the folder. The defense is mostly assembly, not invention.
Never announce it. The students who lived the documentation discipline will feel how ready they are, and the ones who didn't will feel how much they're reconstructing under pressure. That contrast teaches the habit better than any lecture. Let them find it.