When New Transit Infrastructure Misses the Mark

When Toronto’s Finch West LRT opened in 2025, the conversation did not centre on design quality. It centred on journey time. Within weeks, the line was being compared not to other rail systems, but to the bus it replaced and even to a runner along the corridor.

What the design choices reveal

The Finch West LRT was planned around short, local trips. Coverage mattered more than momentum. Stops are frequent and closely spaced across the 10.3-kilometre line. The vehicles move when the street allows them to move, not on their own terms.

This becomes visible in the performance data.

A complete journey takes 55 minutes eastbound and 47 minutes westbound. The line lost a race with a runner. It travels slower than the buses it replaced. In its first month, it experienced 350 delays. Public reception was overwhelmingly negative, with 70% of Torontonians calling the rollout unsuccessful.

None of this was accidental.

These outcomes follow directly from the operating environment that was chosen. Signal priority at junctions is partial. The line operates in a dedicated right-of-way but doesn't use the full extent of transit signal priority at intersections. Metrolinx offered to update the software. The city hasn't implemented it fully.

Each stop adds accessibility. It also adds friction. The line works best for people who value proximity over speed. It's less persuasive for anyone comparing it to driving, especially if they are making this choice while in their warm car, overtaking the train.

The cost of treating speed as negotiable

When a project is presented as rail, people bring an assumption with them. Rail is meant to compress distance, to feel decisive, to offer an advantage that's obvious without explanation.

When journey times end up close to what the bus already offered, that expectation collapses.

Passengers start to treat the line as a different vehicle on the same street rather than as a step change in how the corridor works. Every pause at a junction reinforces the idea that rail is constrained by the same forces as everything else.

Perception is harder to fix than minutes.

You can see the opposite dynamic in places where speed was protected from the outset. In Strasbourg, trams were given consistent priority through junctions and stops were spaced to maintain flow. The system uses its own dedicated signaling system with priority over other traffic at all junctions. The tram became the reference mode along its

corridors.

The CTrain in Calgary is one of the more heavily used light rail systems in North America, with two lines covering about 59.9 km and 45 stations under Calgary Transit’s operation.

It consistently ranks among the continent’s busiest LRT services, with weekday ridership figures in the high hundreds of thousands.

Much of the network runs in its own right of way, a legacy of early planning decisions that protected dedicated space for rail. That reliability helped make the train a default choice for many commuters, especially into the downtown core. While detailed demographic and historical comparisons are complex, widespread transit use in peak periods reflects both corridor investment and ridership commitment.

On Finch West, the absence of that signal has consequences beyond the timetable. It narrows who sees the line as useful. It dampens mode shift because the advantage over driving feels marginal. Critics focus on speed because speed is the easiest proxy for value when transformation isn't self-evident.

What governance structures prevent

Planning teams usually operate inside governance structures that reward continuity and consent rather than sharp outcome definition. Setting a non-negotiable threshold creates a focal point for accountability.

Someone has to own whether the project meets it. Someone has to explain the consequences if it doesn't.

In multi-agency programs, that level of exposure is uncomfortable. Diffuse objectives allow responsibility to remain shared and decisions to keep moving.

Hard performance targets surface trade-offs early. Faster journeys imply fewer stops, stronger signal priority, and more decisive allocation of street space. Those choices generate visible impacts for specific groups. Softer objectives make it easier to accommodate competing interests without forcing resolution.

Without a single metric acting as a reference point, design decisions drift toward what is easiest to approve.

The Docklands Light Railway benefited from clearer alignment between purpose and delivery. The railway had a defined job and limited tolerance for underperformance because its wider role in enabling development depended on it. That clarity carried through into operational expectations and expansion planning.

What cities should lock in before design begins

I would fix three things in place before a line is drawn or a junction is debated.

First, a single outcome owner with authority. Not a steering group. Not a rotating sponsor. One named role, accountable for whether the line delivers what it claims. That role needs the power to pause design if decisions drift away from the stated purpose.

Second, a small set of outcome tests written in plain language. One should be a pass-fail metric tied to journey time and reliability. Another might relate to frequency or operating hours. Those tests should sit above technical standards and be referenced explicitly at every stage gate.

Third, a governance rule that treats deviation as a decision, not an accident. When a choice weakens performance, that should trigger a recorded acknowledgement of impact against the agreed tests. This creates institutional memory. It also changes behaviour.

Transit signal priority has repeatedly been shown to cut intersection delay dramatically while having only marginal impact on general traffic. The technology to improve Finch West's performance already exists and is widely used elsewhere.

What prevents its use isn't technical limitation. It's governance choices.

The lesson for other cities

If you don't lock in what the line must prove in everyday use, the system will quietly optimise for everything else.

Someone observing Finch West should notice how many decisions were reasonable in isolation and how predictable the combined outcome became. Signal priority negotiated junction by junction. Stops added to satisfy access goals. Vehicle speeds constrained to fit the street.

Each choice made sense locally. Together, they produced a line that struggles to demonstrate why rail was chosen in the first place.

The moment to protect transformation is before design begins, when outcomes can still be stated in blunt terms and defended. Journey time, reliability, and frequency need to be treated as conditions of success, not variables to be traded away later.

Once those conditions slip, no amount of architectural quality or operational tuning can recover the perception of what the line is for.

On your next project, don't ask whether a design element is justified on its own. Ask whether the scheme still passes the test it claimed it would meet. Keep asking that question in public, in writing, and at every decision point.

When that discipline holds, rail has a chance to reshape behaviour and expectation. When it doesn't, the line may still function, but it will rarely transform the corridor it was meant to change.