Making the case

A well designed project that nobody approves changes nothing. The final skill is communication, and the version of it that matters here is narrow and learnable: saying the right things, in the right order, to the one person who can say yes.

Know your audience

A principal reads differently to a year 8. The year 8 wants the story: the mission, the planet, the why. The principal is scanning for three things: what will this cost, what could go wrong, and what exactly are you asking me to do. A business manager reads for the budget line. A council officer reads for liability and precedent. Same project, different documents. Before writing a word, ask: who is this for, and what do they need to see in the first ten seconds?

Lead with the number and the ask

Open with your measured problem number, then say what you want, immediately. Busy readers decide in the first paragraph whether to keep reading, and burying the ask on page three is how proposals die politely. Which brings us to length: one page beats ten. A single page signals that you respect the reader's time and that you understand your own project well enough to compress it. Anyone who wants ten pages of detail will ask, and that is a conversation, which is exactly what you want.

The same ask, two ways

Consider two openings for the same proposal. The first begins by explaining that climate change is the great problem of our generation, that the school has a duty to act, and that a group of passionate students has come together to make a difference, and three paragraphs in the actual request finally appears. The second opening is one sentence: the senior courtyard sends about 90 kilograms to landfill each week and nearly half of it is recyclable, and we are asking for two recycling bins and one assembly announcement to fix it. The first reads as warm up. The second tells a busy principal, in ten seconds, what the problem is, how big it is and what they are being asked to do. Same project, same students, same passion. Only the order changed, and the order is most of what determines whether the rest gets read.

Why the order matters so much

A reader is not a blank page waiting to be filled. They arrive busy, half distracted and deciding, sentence by sentence, whether this is worth more of their attention. So the first few lines are not really an introduction. They are an audition for the rest of the document. When you lead with the measured number and the exact ask, you pass that audition immediately, because the reader now knows what they are being asked to weigh up and can read everything after it as evidence. Bury those two things and the reader spends the early paragraphs unsure why they are reading, which is precisely when a busy person decides they are not.

Anticipate the first three objections

Every reader silently generates objections, and the first three are usually predictable: it costs too much, whose job does this become, and what happens when the students lose interest. Answer them inside the document before they are asked. An objection you raise and answer yourself builds trust. The same objection raised by the reader, unanswered, ends the meeting.

Length is not seriousness

It is tempting to believe that a longer proposal signals a more serious project, that ten pages of detail will be read as ten pages of effort. Decision makers read it the opposite way. A proposal that cannot state its case in a page reads as one whose owner has not yet worked out what the case is, and the length becomes a warning rather than a reassurance. The detail is not wasted, it simply belongs in your own working notes, ready for the moment someone asks. Holding it back is not hiding it. It is trusting the reader to ask for what they want, which is also how you turn a document into a conversation.

You already do this

You use this skill more often than you think. When you message a manager to ask for a shift swap, the version that works opens with the ask and the two dates, not with three sentences of apology and background, because your manager is busy and skims. When you want the group chat to actually decide on a plan, the message that gets a decision is the one that ends with a clear question and a time, not the one that muses about options. A one page proposal to a principal is the same move in a more formal setting: respect the reader's attention, make the decision easy to find, and make saying yes require the least possible work.

The pitch structure

• Problem: the one sentence with the measured number in it.
• Response: what you will do, in its smallest version that still matters.
• Cost: dollars and hours, honestly counted.
• Measurement: what you will read, how often, and when you will report back.
• Ask: the exact decision you want, by an exact date.

This is where the topic comes together. You chose a project you could finish, framed it as a measured problem, designed the smallest response that would still move the number, and now you can put it in front of the person who can approve it in a way that gets a yes. The case study that follows walks a real group through all four steps end to end, from noticing sprinklers running at midday to a principal signing off a term long trial, so you can see the whole method working as one build rather than four separate skills.