The question behind the ribbon
When a project opens, the immediate feeling is relief and celebration. The more useful question comes later: did it do what it was meant to do, for whom, and at what cost? Answering that honestly is harder than it sounds, because success is easy to claim and hard to demonstrate.
Evaluation is not about passing or failing a project. It is about learning. A modest project that is judged candidly teaches more than a large one declared a triumph without checking.
Start with the original aims
You can only judge a result against a goal. If the stated aim was to make a street safer, the measure is not how many people attended the opening. Evaluation works best when goals are written down before design begins, in terms specific enough to check. “Improve the neighborhood” cannot be measured. “Reduce vehicle speeds on this street and increase the number of people walking to the park” can.
A project may also have secondary aims, such as cost, schedule, accessibility, or local hiring. These deserve their own measures rather than being folded into a general impression.
Collect a baseline
The most common failure is not measuring the “before.” Without a baseline, any later number is just a number. A pre-project count of pedestrians, vacant storefronts, crashes, park users or resident opinions gives something to compare with. If no baseline was taken, it can sometimes be reconstructed from older records, though with less confidence, and the report should say so.
Simple tools are often enough: counts of people at set times, walk audits of conditions, vacancy surveys of nearby buildings and short resident questionnaires.
Choose measures that fit
Good evaluation mixes types of evidence.
- Outputs: what was built, on time and on budget. These are easy to count but say little about benefit.
- Use: how many people visit, walk, ride or shop, and who they are. Looking at who is not using a place is as informative as looking at who is.
- Outcomes: changes in safety, health, local business activity, property conditions or resident satisfaction.
- Experience: what people say in interviews or open comments, which can explain why numbers moved.
Planning indicators and dashboards can be helpful, but they become decorative if nobody acts on them. Pick a small number of measures tied directly to the goals instead of tracking everything available.
Timing matters
A project judged at three months may look different at three years. New places often attract curiosity visits that fade, and some benefits, such as changes in business mix or tree growth, take much longer to appear. A staged review, for example shortly after opening, then after one year and again after several years, gives a fuller picture. Seasonal effects also matter: a plaza surveyed only in summer says little about winter use.
Traps to avoid
Attributing everything to the project. Neighborhoods change for many reasons: the wider economy, other developments, interest rates, new transit. If sales rose after a street renovation, other factors may have contributed. Comparing with a similar nearby area that did not receive the project helps, although perfect comparisons are rare.
Counting only the winners. Businesses that thrive are visible; those that closed or moved are not. A fair review tracks both. The same is true of residents: rising rents may push out the people the project was meant to serve, which is why evaluating renewal and rents alongside physical results is important.
Choosing flattering measures. It is tempting to report what went well and leave out the rest. Reporting both strengths and weaknesses makes the findings more credible.
Confusing activity with benefit. Large crowds at an event do not prove a place works on an ordinary Tuesday.
Ignoring cost. A project may have achieved its goals, but if the price was far above what was promised or maintenance is unaffordable, the evaluation should say so. A basic cost-benefit analysis, with its assumptions stated plainly, can help, though its numbers depend heavily on what is counted.
Who should do it
Having the project team evaluate its own work creates an obvious conflict of interest. Independent reviewers, such as another city department, a university partner or a community group, can add credibility. Involving residents in collecting and interpreting data also builds trust, and brings knowledge that statistics miss.
Reporting results
A useful report is short, clear and public. It restates the original aims, shows the baseline and the new figures, explains limits of the data, and lists what the team would do differently. Admitting uncertainty is a strength. Phrases such as “the data suggest” or “we cannot separate this from other changes” are more honest than a confident claim the evidence cannot support.
Feeding lessons forward
Evaluation pays off when it changes later decisions. A finding that temporary trials predicted use poorly, or that approvals added unnecessary months, should inform the next project’s stages. Evaluation can also inform small fixes to the project itself, such as adjusting signal timing, adding seating, or improving lighting.
Not every benefit can be measured, and some effects take a generation to show. Still, a project that has been judged candidly, with its limits acknowledged, leaves a city better prepared than one that simply declared success and moved on.