Framing the problem

The most common way projects fail is not bad execution. It is solving a problem nobody measured. Enthusiastic teams leap straight to solutions, and months later discover the problem was smaller, different or somewhere else entirely. Framing the problem properly is slower at the start and faster everywhere after.

Measure the current state first

Before you propose anything, find out what is actually happening now. This is almost always cheaper and easier than it sounds. A week of weighing the bins tells you more than a year of opinions about waste. Ten photographs of a power meter beat any amount of guessing about energy. People's impressions of a problem are shaped by what annoys them, not by what is biggest, and the two are usually different. The data does not care what anyone assumed, which is exactly what makes it persuasive later.

Define the boundary

A measurement without a boundary is meaningless. Decide exactly whose waste, which building, what period. The school produces heaps of rubbish is not a problem you can work on. The four canteen bins in the senior courtyard, weighed each day for one week, is. A tight boundary makes the measuring achievable, and it stops the fatal drift where a project quietly grows until it is about everything and achieves nothing.

One sentence, with a number in it

Now compress everything you measured into a single sentence containing at least one number. Something like: the senior courtyard bins send about 90 kilograms to landfill each week, and around half of it is recyclable. If you cannot write that sentence, you have not finished framing. If you can, you own something rare: a problem statement nobody can argue with, because you measured it yourself.

A measurement, step by step

Suppose the circled idea is the canteen bins, and you want to see what one honest week actually looks like. On Monday you borrow the kitchen scales and a box of gloves, and at the end of lunch you weigh each of the four bins before they are emptied, writing the number on your phone. Monday comes to about 18 kilograms. You do the same on Tuesday, Wednesday, Thursday and Friday, and by the end of the week you have five numbers that add to roughly 90 kilograms, an average of around 18 a day. Then you spend one lunchtime tipping a single day of rubbish onto a tarp and sorting it into piles: food scraps, recyclable containers, soft plastics and true rubbish. The recyclable pile alone is close to half the weight. None of this needed permission beyond one conversation, none of it cost anything, and you now know something the whole school had only guessed at. That is the entire method: a boundary, a scale, a week, and one afternoon of sorting.

The trap of the loved solution

Watch for the trap of starting from a solution you already love. If you have decided the school needs a worm farm before measuring anything, every number you collect will quietly bend to justify the worm farm. Measure first, honestly, and let the biggest number choose the project. Sometimes it points exactly where you hoped. Sometimes it points somewhere better.

The problem you think you have

A common belief is that measuring is a waste of time, because everyone already knows what the problem is. Ask around and people will tell you with total confidence: the school wastes far too much paper, or the lights are the real culprit, or it is all those plastic bottles. The trouble is that confident impressions and actual quantities rarely match, because people remember what irritates them rather than what is largest. The bottles are visible and annoying, so they feel like the problem, while the food scraps that quietly outweigh them go unnoticed at the bottom of the bin. Measuring is not doubting people. It is the only way to tell a real problem from a memorable one.

The same habit outside school

This habit of measuring before deciding is not only for school projects. Your phone already does it for you, because the battery screen that shows which apps drained the day is a current state measurement, and it almost always names an app you did not suspect while the one you blamed sits near the bottom. The same gap shows up at a casual job, where a manager who guesses which hour is busiest is often wrong until the register data settles it. Once you notice how often confident guesses miss, framing a problem by measuring it first stops feeling like extra work and starts feeling like the obvious first move.

Framing sits between two lessons for a reason. The one before handed you a circled idea, and this lesson turns that idea into a measured problem sentence with a number you can defend. The next lesson takes that number and asks the harder question: what is the smallest response that would actually move it. So the sentence you write here is not the end of the framing. It is the input the whole rest of the project is built on, which is why it is worth getting the number honestly rather than quickly.