Every other page on this site documents a decision that went badly. This one does the opposite: it takes the sharpest crayon in the box — explore alternatives — and shows what an hour of using it could have produced. The answer is a small errand shuttle nobody costed — and it turns out to touch Hopkins, the Marina, the ferry, and where Berkeley puts homeless services.
The Hopkins debate was framed as a contest over a fixed resource. Should the street space belong to parked cars, or to bicycles?
Once those became the only two choices, the argument became zero-sum. Every gain for one side had to come out of the other. The reasoning on both sides grew more detailed and more heated, and all of it rested on one assumption nobody examined:
Because it recurs from here on, it is worth naming at the outset. There was a third answer available throughout, and it was never costed: a small, frequent, fare-free shuttle built for short errand trips within the city, with cargo — ride down to the shops, ride back up with the shopping. Emeryville and the Presidio have run services of this shape for years.
This page calls it a connector. It is introduced here rather than at the end because the whole argument turns on it having been available the entire time. Everything that follows — the interests beneath the positions, who each answer actually reaches, what it would cost — is an attempt to work out what an hour of considering it would have produced.
This site’s crayon box counts seven ways Berkeley could answer a fiscal or service problem, and finds that four are worn to stubs while three keep their points. One of the sharp ones is explore alternatives. This page picks it up. The corridor itself is examined separately as Case Study A in the framework.
Fisher and Ury, in Getting to Yes, give this failure a name and a remedy. The failure is bargaining over positions — the specific outcome each side demands. The remedy is to step back to interests, the underlying needs those positions were meant to serve, and then look for options that satisfy the interests on both sides at once. That is what a win-win actually is: not a compromise in which each side gives up part of its position, but a different option that serves what each side was really after.
Hopkins is a clean example, because the positions and the interests come apart so plainly.
Mutually exclusive. One must lose.
Not in conflict. Nobody wants the other side to fail at these.
Stated as positions, the two sides cannot both win. Stated as interests, there is considerably more overlap: cyclists also benefit from reachable shops and pharmacies, while many people who need or prefer to drive may still support the city’s safety and climate goals. The fight was real, but it was a fight about the instrument, conducted as if it were a fight about the goal.
It is worth being exact about the instrument, because the public argument has not been. The contested item was not a bike lane in the ordinary sense — a painted lane alongside traffic is uncontroversial and largely already there. It was a Class IV separated bikeway, a cycle track physically divided from the roadway by posts, curbs, planters or a row of parked cars. That is a different object with different consequences: it consumes street width permanently, it changes how a fire engine reaches a curb, and it complicates refuse collection, loading and passenger drop-off in ways paint does not.
Those consequences are precisely what the Fire Chief was being asked about on 28 July 2026, and precisely what the record put before Council said had been reviewed when it had not — see the Hopkins Street fire review. Collapsing “cycle track” into “bike lane” is how a specific engineering dispute became a referendum on whether you support cycling.
It also matters for the argument this page is making. Reducing vehicle trips could also change the design problem itself. With meaningfully lower traffic volumes and speeds, less space-intensive bicycle treatments might become more plausible. Whether they would provide adequate safety is an engineering question that should be tested rather than assumed — and it is a question nobody put, because the debate had already narrowed to two fixed designs.
There is also a question about the safety evidence that we cannot answer. The case for separated tracks is usually made on cyclist injury rates against motor vehicles, which is a real and well-studied benefit. Whether anyone has modeled that alongside the rest of the ledger — delayed emergency response on a narrowed street, refuse and delivery vehicles obstructing a lane they can no longer pull clear of, conflicts between cyclists and pedestrians at crossings and bus stops, and the behavior of cyclists themselves — we do not know. Such an analysis may well exist. We have not seen one cited in the Hopkins record, and we have not searched the literature for it.
We raise it as a question rather than a finding, because a question is what it is. If the integrated analysis exists, it belongs in the staff report. If it does not, that is worth knowing before narrowing a street.
A broader alternatives search could also have widened the evidence base. UC Berkeley’s Institute of Transportation Studies and SafeTREC — the Safe Transportation Research and Education Center, which runs a Center for Pedestrian and Bicyclist Safety — sit about a mile from Hopkins Street and specialize in transportation-safety questions. Neither appears in nineteen months of Council transcripts, the agenda record, or the technical basis cited for the July 2026 item. That does not establish that they would have recommended a different design. It establishes that the record does not show Council asking.
That is the crayon box again, in its purest form: the option was not rejected, it was not considered.
There is a second thing the positions hide. Each of them only works for part of the population, and the argument has largely been over whose part matters more.
The comparison below sets the two debated answers against the groups each one actually reaches, and includes the connector for the same reason it was named at the top: a coverage comparison containing only the two debated answers would beg the question the debate was already begging.
Illustrative, not measured — no mode-share data for these trips has been published, and the bars show relative reach rather than exact shares. The fourth band is the one most often left out of this argument: Berkeley is built on a hill, and the difference between “can ride a bicycle” and “can ride a bicycle up Marin Avenue with a week’s shopping in February” is most of the population. Cycling provision serves the trip down. Nothing currently serves the trip back. The distinction that matters most, though, is the third band. Some people drive because it is easiest; some drive because nothing else works — a disability, an injury that will heal in six weeks, a parent managing a toddler and a week’s shopping. For that group there is no substitute, and any proposal that treats their spaces as available is not a serious proposal. Conflating the two groups is what makes this argument so bitter: each side hears the other denying a need rather than debating a convenience.
Set out this way, the connector’s claim is narrower than it first sounds, and better for it. It does not serve everyone. It takes pressure off the first two bands — which is precisely what would leave more spaces for the third. The people who must drive do better under a proposal that reduces competition for parking than under one that rations it, and better still than under one that removes it.
This is also why the bicycle argument keeps running aground on weather and on the hill. A lane is an excellent answer in September on the flat and a poor one in a February downpour on a grade, and a policy that relies heavily on year-round uphill cycling will fit a narrower population than one that does not. The asymmetry is the giveaway: the ride down to the shops is easy and the ride back is the whole problem, which is why the bicycle answer works best for exactly the trip that needs it least.
A connector does not replace cycling provision. It makes cycling usable as a choice rather than a commitment. That hybrid would become another available choice: ride down when conditions are suitable, take the connector back with the shopping, or use it both ways when cycling is unattractive.
Once the underlying interests are visible, the curb question does not disappear. A Class IV bikeway and existing curb parking cannot occupy the same space. The decision still requires Council to decide who gets the curb.
What changes is the size of the option set around that decision:
That question still permits the separated bikeway. It also invites other alignments, parking-management changes, delivery arrangements, transit improvements, and a connector designed for short errands — the one this page follows, because it is the one nobody costed. Exploring those possibilities does not make the conflict imaginary. It tests whether the conflict must remain as zero-sum as it first appears.
Hopkins was directly about parked cars and a Class IV bikeway. But the consequences extended beyond the curb: how residents reach neighborhood businesses, carry groceries home, reach a pharmacy, make several stops, and travel safely. A better process would have decided the curb question with those broader access needs explicitly in view.
Call it a Berkeley Community Connector: a small, frequent, fare-free shuttle optimized for one job that no existing service does well — short errand trips within the city, with cargo.
It would not replace AC Transit or duplicate BART. Transit networks are built for different jobs. BART moves people across a region. AC Transit is built for corridor throughput across a large service area. Neither is designed for the trip that ends with someone carrying two bags four blocks uphill, and neither should be. That job currently has no service designed for it, which is precisely why it keeps being addressed through street design instead.
| Emery Go-Round | PresidiGo | |
|---|---|---|
| Riders | ~1.4M/year pre-2020, about 5,000 a day | 300,000+ a year |
| Fare | Free, open to the public | Free, open to the public |
| Owner | Nonprofit transportation management association | Presidio Trust |
| Operator | MV Transportation, on contract | MV Transportation, on contract |
| Governance | Nine-member board — property, business, employer and residential seats — meeting publicly each month | Federal trust, funded by commercial leasing rather than appropriation |
| Funding | Property-based improvement district. In 2016 parcel owners voted by 71.25% to expand the assessment because they had concluded the service was worth paying for. | Lease revenue |
Neither is a city department. Both are governed by a board that meets in public and buys operations on a contract. That is the shape of the thing, and it is not speculative.
There is a sharper way to put this. The Emery Go-Round already runs into Berkeley, and it already does the grocery run. Its Hollis route crosses the city line, turns off Hollis and makes a loop up 9th Street specifically to reach Berkeley Bowl West, which is the route’s northern terminus. The stop is named for the store. Service runs every fifteen minutes from just after six in the morning, and it is fare-free and open to anyone — including any Berkeley resident standing at the stop.
So a neighboring city of about 13,000 people funds a shuttle that detours into Berkeley to bring its residents to a Berkeley grocery store, at a frequency no Berkeley service matches. Berkeley, with roughly ten times the population, has nothing comparable in either direction — not to Berkeley Bowl West, not to the Oregon Street store, not to Monterey Market, not to Solano or North Shattuck or Fourth Street.
The model is not hypothetical and it is not distant. It is operating on Berkeley streets, on a fifteen-minute headway, paid for by somebody else.
Now hold that next to Hopkins.
Monterey Market is the North Berkeley version of the same destination: a grocer people travel to rather than stumble across, drawing customers from well beyond walking distance, with parking that has been contested for as long as anyone can remember, sitting on the corridor the city spent years arguing about. It presents a strikingly similar access problem to one Emeryville addresses by routing a frequent shuttle to a grocery store.
Emeryville’s operating network includes a frequent route terminating at a grocery store. Berkeley’s Hopkins debate treated access to a major neighborhood market primarily as a contest over curb space. One of those cities treated “how do people get their groceries home” as a transportation question with transportation answers. The other treated it as a territorial dispute between drivers and cyclists, and then held a vote to see who won.
That is what the missing crayon costs. Not a shuttle — a whole category of answer.
The reason to take this seriously is not Hopkins. Hopkins merely exposed the gap. The same missing option appears in four other places on this site, each one already documented.
Hopkins was a fight over a curb. The waterfront is heading into a fight over a parking lot, and it has exactly the same shape.
The City’s own transportation plan projects peak weekday demand of 421 spaces against a baseline of 250 — 171 short before ferry service begins. The Draft Environmental Impact Report describes 425 to 475 spaces being used by the project’s new trips, on a site that holds about 404 today. Whatever the final numbers, the structure is set: ferry passengers and existing waterfront users — the people who come for Cesar Chavez Park, Adventure Playground, Shorebird Park, the sailing clubs, the launch ramps, the sunset — will be allocating a fixed supply between them.
Two constituencies, one lot, and the arithmetic guarantees that one of them loses. That is the Hopkins argument again, relocated three miles west and not yet begun.
There is a second problem, and it is more awkward. The business plan models 68% of ferry passengers arriving by car and 5% by public transit, and the EIR projects 1,127 new vehicle trips a day to the waterfront. The project’s stated objective is to reduce single-occupancy vehicle travel; its own model says it works by generating it. The environmental case rests on those drivers otherwise having driven 25 miles to San Francisco — a comparison nobody has tested, because the business plan contains no analysis of how many riders would be diverted from BART, AC Transit or the Richmond ferry rather than from cars.
This is the part that ought to trouble the people who argued hardest for Hopkins. The case for narrowing a street was that Berkeley should make driving less convenient in order to meet its climate commitments. The case for the ferry accepts a project whose access model is two-thirds cars and several hundred new parking spaces. Both positions can be held. Holding both without noticing is what happens when each decision is judged on its own.
A frequent connector does not resolve the ferry’s finances or its permits. It does change the parking arithmetic from a fixed pie into a variable one, and it is one option that could make the project’s access model more consistent with the climate rationale used in the Hopkins debate. It appears nowhere in the project record.
Figures from the WETA Berkeley Ferry Service Business Plan, the March 2025 Parking and Transportation Demand Management Plan, and the February 2026 Draft Environmental Impact Report — see the pier-ferry explainer. The framework treats recreation, the Marina and ferry expansion together as Case Study H.
The waterfront hotel is separated from downtown, the campus and BART by a freeway interchange. Visitors increasingly choose accommodation by asking whether they can stay somewhere without renting a car, and for the Berkeley Marina the honest answer today is no. That is a competitive disadvantage the City has never addressed with a service, in a fund the City Manager described in 2021 as “on the brink of insolvency.” A connector does not fix the Marina Fund. It removes one of the reasons the waterfront underperforms as a destination.
Berkeley has also made a series of individually considered housing and service decisions along University Avenue without addressing their cumulative effect on the corridor. Transportation does not resolve those siting choices. But access changes the option set: if residents of a facility can reliably reach services without a car, location and service access become less tightly coupled.
That does not make every site appropriate or answer questions of neighborhood concentration. It illustrates the same principle as Hopkins: changing one constraint can reveal options that remain invisible while the constraint is treated as fixed. The acquisitions and siting record is documented in the Oxford Street case and the District 4 siting record.
Solano, North Shattuck, Fourth Street and Downtown all depend on customers who currently arrive by car, and all face the same constrained parking. Meanwhile the residents least able to drive — and least able to carry a load any distance — are the ones for whom every errand becomes a logistical problem. Both are access problems, and curb allocation is one part of them rather than the whole of them.
Everyone asks about groceries, and they are right to. The reason people drive to a grocery store is the load they carry home, and a fixed-stop loop can reintroduce exactly the walk the trip was meant to avoid.
Which is why the Berkeley Bowl West stop is worth sitting with. The Emery Go-Round is a commuter shuttle built to connect Emeryville to MacArthur BART. Nothing about that job requires detouring across the city line and looping a residential block to reach a grocery store, and yet the route does exactly that, and the store is the northern terminus. Somebody, at some point, concluded the grocery trip was worth designing for.
That is not proof the load problem is solved — no origin-destination data for that stop appears to have been published, and how people actually carry their shopping home from it is unknown. It is precisely the kind of thing a serious option search would go and find out, and it is available for the cost of a phone call to the Emeryville Transportation Management Association.
It is also worth being precise about how large the objection really is. The load argument is usually made against the shuttle and rarely against the bicycle, and the two do not survive the comparison. The physical ask is comparable, and the bike version requires balancing it at speed in traffic.
So the group genuinely defeated by a short walk from a stop — someone with a mobility impairment, a large family shop, several children in tow — is substantially the same group already defeated by a bike lane. Some residents would remain poorly served by either a bicycle facility or a fixed-stop shuttle. That is not a reason to stop considering the connector; it is a reason to identify the unmet group and test design responses such as demand-responsive returns, carefully located pickup points, cart handling, or delivery partnerships. It is the population that neither existing position ever served, and the one a demand-responsive return leg could actually reach.
Berkeley would not need to invent this service model from scratch. Emeryville has years of nearby operating experience. A serious alternatives search would begin by asking what trips riders actually make, what the grocery terminus accomplishes, what the service costs, what has failed, and what Berkeley could learn before spending public money.
That is a design constraint, not a fatal objection, and it is the thing a pilot exists to answer. Plausible responses include demand-responsive routing on the return leg, siting the small number of pick-up points for walkability rather than coverage, coordinating with stores on cart handling, or pairing the service with delivery for the heaviest trips. Which of those works is an empirical question that six months and a modest budget would settle.
What none of this requires is perfect substitution. If a meaningful share of errand trips shift out of single-occupant cars, parking pressure eases for the people who genuinely need to drive, commercial districts get more reachable, and the street-space argument gets less zero-sum — without anyone having to lose it.
The framework this site measures against sorts municipal work into three categories. This is not Category 1 — Berkeley does not need to own a shuttle to benefit from one. It is a textbook Category 2: an undertaking whose scale, expertise and beneficiaries require genuine partners.
Category 2 carries a condition, and it is the part that usually gets skipped: “Collaboration must be binding, not aspirational. A Category 2 proposal should identify each partner contribution, governance right, continuing obligation, service area, benefit allocation, and exit condition.”
Listing willing partners is not a plan. Emeryville’s answer is a plan: a nonprofit association with a public board and defined seats, funded by an assessment the payers voted on, operating through a contract that can be re-bid. Berkeley’s version might look different — the plausible partners here are the commercial district associations, Visit Berkeley, AC Transit, BART, waterfront stakeholders, and the ferry project if it proceeds — but it needs the same skeleton.
One further condition, from the same framework: provider neutrality. The operating model should be chosen by comparing city staff, a transit agency, a nonprofit, a private contractor and a partnership on equal criteria. Emeryville landed on a nonprofit contracting to a private operator. That may or may not suit Berkeley. It should be the result of a competitive process, not an assumption written into the first staff report.
A six-month pilot, competitively bid, with private, nonprofit and public operators all eligible, reporting against measures that can be compared directly with the infrastructure alternatives:
The next step would not be to create a permanent service. It would be to cost a limited pilot and decide whether the price of finding out is justified by the questions it could answer.
Every other analysis on this site documents something that went wrong. This one is here because a critique that only ever prosecutes is easy to dismiss, and because the framework is worth more as a tool than as a verdict.
Berkeley’s decisions are routinely framed as a choice between two positions, each with a constituency, each requiring the other to lose. That framing feels like rigor — the arguments get very detailed — but it is what a small option set looks like from the inside. The most valuable question in a public meeting is rarely which side should win. It is:
On Hopkins, that question would not have eliminated the need to choose between parking and a Class IV bikeway. It could have produced additional configurations and complementary measures that changed the costs of that choice — at least one option touching the ferry, the Marina, the commercial districts, the siting fights, and the people on both sides of the curb argument. The connector is one such option. It might have failed. Nobody costed it, so nobody knows.
Hopkins is decided. Most of what it touches is not. The waterfront parking fight has not started. University Avenue has no plan. The ferry’s use permit still needs findings from the Planning Commission, the Zoning Adjustments Board and the Council, and its construction money does not exist yet. Every one of those is a live decision where somebody could still ask what else is on the table.
The curb space on Hopkins was fixed. The option set around it did not have to be. That is the standard the next decision can be measured against.