Measuring Grant Outcomes: Making the Improvement Stick

Short answer: the project is finished - the equipment is installed, the system is running, the consultant has moved on - and there is a strong temptation to consider the whole thing a success and get on with the business. But finishing a project is not the same as gaining from it, and the gap between the two is where a surprising amount of effort and money quietly goes to waste. A change that is completed but never measured might be delivering half of what you hoped, or nothing at all, and you would never know. A new way of working that is introduced but never embedded slowly gives way to the old way, and within months the business is back where it started, with only the invoice to show for it. The real return on a project comes not from finishing it but from measuring what it actually achieved and making the improvement stick - and that is the work most businesses skip. This guide walks through how to do it, and because it is general and educational it names no schemes and quotes no criteria or figures - those are set officially and change, so always confirm the current details on gobusiness.gov.sg.

Finishing a project is not the same as gaining from it

There is a quiet assumption behind most completed projects: that finishing equals succeeding, that once the work is done the benefit simply arrives on its own. It does not. Finishing is an activity; gaining is an outcome; and the two can be surprisingly far apart. A business can install exactly what it planned, tick every box, and still see very little change in the thing the project was supposed to improve - because the finishing was never the point, the improvement was. This gap is uncomfortable to look at, which is precisely why so many businesses avoid looking, preferring the clean feeling of a completed project to the messier question of whether it actually worked. But the whole reason to undertake a project is the gain at the end of it, and if you never check whether that gain arrived you are flying blind, repeating projects on faith. The businesses that improve over time are the ones willing to ask the awkward question - did this actually deliver what we wanted - and to act on the honest answer.

Capture the "before" or you have nothing to measure

Here is a hard truth that catches many businesses too late: you cannot measure an improvement if you never recorded what things were like before. Measuring a gain requires two pictures, the before and the after, and the before can only be captured before the project starts, never afterwards. Once the change is in place, the old state is gone, and any attempt to recall it is guesswork coloured by how you feel about the project. So the discipline of measuring outcomes actually begins right at the start - while you are still running the project and hitting its milestones - by capturing a clear picture of how things stand today, whatever it is you hope to improve. This is easy to skip in the excitement of starting, and its absence is only felt at the end, when you want to prove the project worked and realise you have nothing to measure against. If you take one practical thing from this guide, let it be to record the before, because without it every later claim of improvement is just a feeling.

Measure the outcome, not the activity

When businesses do try to measure a project, they often measure the wrong thing, counting the activity rather than the outcome. It is easy and satisfying to report that the training was delivered, the software installed, the process documented, because those things are concrete and clearly done. But none of them is the point. The point is what changed as a result - whether the work actually got faster, the errors fell, the capacity grew, or whatever the real goal was. Activity is what you did; outcome is what it achieved; and only the second tells you whether the project was worth doing. Measuring activity feels like measurement, but it is really just confirming that you completed the tasks, which you already knew. If that distinction still feels fuzzy, it is worth being clear on what "outcomes" really mean before you decide what to track. A pile of completed activities that changed nothing is not a success, however busy it looked.

Give the change time, and separate signal from noise

Two things make an honest measurement harder than it looks: timing and attribution. A new way of working almost always performs worse before it performs better, because people are learning it and stumbling through the awkwardness of the unfamiliar. Measure too soon, in the first raw weeks, and you will capture the dip and mistake it for failure, abandoning something that would have paid off handsomely once it settled. So give the change enough time to bed in - for the learning curve to flatten and the new way to become the normal way - before you take the measurement that counts. Then, when you do see a change, ask honestly how much of it the project actually caused, because a business is a noisy place where many things move at once. Sales may have risen because of your project, or because the market improved, or because a competitor stumbled. You will rarely get a perfectly clean answer, but looking honestly at what else was going on gets you far closer to the truth than assuming the project deserves all the credit or none of it.

Record it honestly, and report it plainly

Memory is a poor and flattering historian, smoothing over the struggles and reshaping the story to fit how things turned out, and a business that relies on it loses the real lessons of every project. So write down what actually happened, plainly and while it is fresh - the results you measured, but also the surprises, the things that went wrong, and what you would do differently. This honest record is worth far more than a tidy success story, because it is where the genuine learning lives. And that knowledge is only useful if it reaches the people who need it: yourself and the people running the business first, who deserve a plain account of whether the effort paid off, free of the spin that makes everything sound like a win, and then anyone else you must answer to. Reporting is not about producing an impressive document; it is about turning what you learned into something others can see and act on. Say what happened, say it clearly, including the parts that did not go to plan, and let the honesty of it build the trust that makes the next project easier to run.

Making it stick: build the habit and give it an owner

The most fragile moment in any improvement is right after the project ends, because the change is new, the old way is still familiar, and the pull of habit is backwards. An improvement only becomes real when the new way stops being new and simply becomes the way - done without thinking, without reminders. Getting there takes deliberate attention in the weeks after the project, reinforcing the new behaviour until it hardens into routine, and expecting the persistent tug back towards the comfortable old way, especially under pressure when a deadline or a busy season sends people reverting without noticing. This slide back is not a failure of character but the ordinary physics of habit, so plan for it rather than treat it as a surprise. It helps enormously to give the improvement an owner - just as the project had one while it ran - someone accountable for noticing when the new way is slipping and gently pulling it back before the slide becomes permanent. Without an owner the improvement belongs to no one, and things that belong to no one are the first to slide when the business gets busy, especially in a small business where no system quietly enforces standards.

Write it down, and feed the lessons forward

An improvement that lives only in people's heads is one resignation away from disappearing, because when they leave the knowledge of why things are done this way leaves with them. So write the new way down - not in exhaustive detail, but enough that someone new could understand how things are meant to work and why - turning private knowledge into something the business owns rather than borrows from individuals. Beyond protecting the improvement itself, a finished project is a source of hard-won knowledge about how your business handles change: how long things really take, what you are good and bad at, which kinds of change stick and which do not. Feed all of that into how you plan and run whatever comes next, closing the loop between one project and the following one - which is exactly the thinking behind sequencing your projects into a multi-year roadmap, where each effort becomes a rehearsal for the next rather than an isolated event you learn nothing from. The gain from a project is not only the improvement it delivers; it is also the wisdom it leaves behind, and only businesses that pause to collect it get to compound it over the years.

Finishing, in the end, is only the beginning of the gain. Measure what actually changed, do the patient work of making it stick, and carry the lessons forward into the next project - and, as always, confirm what applies to your own situation on gobusiness.gov.sg before you rely on any of it.

Frequently asked questions