Getting your Trinity Audio player ready...

Facing a dilemma, the Mountain View City Council found it impossible to choose between two competing visions for developing North Bayshore’s large gateway property. Rather than take a side, council members decided they may need to dictate their own development plans for the area.

At its Tuesday, Feb. 26, meeting, the City Council was asked to pick between two starkly different master plans submitted by Google and SyWest. The two companies each own roughly half of the 30-acre swath of land known as the Gateway site, located just north of Highway 101 and west of Shoreline Boulevard at the entrance to the North Bayshore tech corridor.

The backstory is complicated. In 2015, SyWest was originally planning to partner with LinkedIn to construct a 10-building campus that would mix corporate offices with entertainment such as restaurants and a movie theater. Impressed at the time, the City Council granted the partnership about two-thirds of the bonus development rights being allotted for North Bayshore.

It was a huge win for SyWest and LinkedIn, especially since they won the lion’s share of office development rights that Google was seeking. But Google managed to turn the situation to its advantage. In a 2016 land swap, Google traded several fully built offices on Mountain View’s east side in exchange for all of LinkedIn’s land holdings in North Bayshore.

Effectively, that trade eliminated LinkedIn and made Google the new partner of SyWest in developing the 30-acre Gateway property. Suffice it to say, it doesn’t appear to have worked out. Over the course of two years, the two companies failed to reach an agreement to work together. Late last year, both parties submitted their own conflicting development master plans for the area.

“Fundamentally, we’re just taking two different approaches,” said Bill Vierra, SyWest president. “We need 880,000 square feet of office space, and Google doesn’t want any offices on the site.”

The SyWest proposal calls for developing only its own 16-acre property, which is currently occupied by the Century Cinema theaters and its sprawling parking lot. That would be replaced with about 740 residential units as well as a hotel, shops and a new theater. The project would also create about 880,000 square feet of offices, leaving a smaller portion of office development rights for Google to use on its own development. But the plan left various details vague, such as how it would manage the immense traffic burden, and didn’t specify what community benefits it would offer.

In contrast, Google included the Gateway site as one cog in the wheel of its broader plans to create three new neighborhoods in North Bayshore, a “master framework” plan that the company has heavily promoted. In total, the company plans to build up to 7,000 housing units, as well as 1.18 million square feet of new offices — including 1,200 homes and 275,000 square feet of office space specifically for the Gateway site. City officials noted that Google was being presumptuous by planning to use SyWest’s land without any consent from the company.

Google real estate director Michael Tymoff said that his company was trying its best to comply with the city’s ambitious precise plan, including its hefty requirements for affordable housing and funding. He noted that the city’s demands for open space, retail and an elementary school made it so that his company could no longer aim for the 6,600 units the company originally envisioned. Now Google is looking to build somewhere in the area of 5,700 units, and any other units will need to be built by other developers, he said.

“Any further delay would make these issues that we’re trying to solve together much more acute and difficult to solve in a comprehensive way,” Tymoff said. “The last thing we’d want to do is reopen the precise plan and CEQA to delay this further.”

The two proposals spurred an ambivalent reaction from city staff, who noted that both fell short of the various requirements of the North Bayshore Precise Plan. Both parties were essentially feuding over who would get more development rights for office space, staff noted. As the issue came before the City Council, everyone lamented that the two companies couldn’t work out something on their own.

“What’s frustrating for me is there’s a clear win-win here: Google needs the office space, and there’s an ability for office here,” said Councilman Chris Clark. “Everyone could work together to marry all the elements, and I wish we could get to that point.”

To prod that process along, Councilwoman Margaret Abe-Koga suggested the city should step in and spell out how to develop the Gateway site. Basically, the city would draft its own master plan, similar to those submitted by SyWest and Google. Abe-Koga said she favored SyWest’s proposal, and she made a motion to use it as a starting point in any future master plan.

“I’d like to move forward in some way with SyWest’s concepts. The elements in their plan is close to what we envisioned,” she said. “I think we could be quite successful in this.”

Abe-Koga’s motion generated some pushback from city staff. City Manager Dan Rich pointed out that using SyWest’s proposal as the basis of a new overarching neighborhood plan would be essentially the same as approving its project. Plus, he noted that the city already had specific development goals in its own precise plan, which took nearly five years of work.

Upon hearing some concerns from other council members, Abe-Koga agreed not to specify any office allocation for SyWest. She also included a stipulation to urge SyWest and Google to enter mediation in a last-ditch effort to get them to settle their dispute on their own.

As the council meeting neared a vote, it became clear that a new Gateway master plan could be a complicated effort that may involve revisiting the larger precise plan. Abe-Koga suggested the city’s total allocation of office development might be infeasible. Mayor Lisa Matichak also recommended the city could consider shifting the building density specified in the precise plan.

Councilman Lucas Ramirez expressed doubt that the city would achieve better results by trying to force a compromise between Google and SyWest. He favored Google’s plan because it provided the most community benefits.

“Splitting the baby might not lead to the best outcome for anybody,” he said. “I’m not seeing an outcome where we can get the level of community benefit that Google is currently offering.”

The council voted to pursue a new master plan for the Gateway site 6-1, with Ramirez opposed.

Join the Conversation

7 Comments

  1. What has SyWest done to be a good neighbor to MV? SyWest only has power because the city council chose it and Linkedin over Google despite Google offering more in community benefits. Once again Google offers more in community benefits.

    So SyWest’s plan makes it itself rich all the while making Google pay it for offices and MV residents pay in the form of more traffic, less housing, and less community benefits. What political influence is SyWest putting on the city council that SyWest isn’t being seen as the most selfish stakeholder in this process?

  2. How is it that I come to find myself rooting for Google as the good guy and underdog? I don’t want to be on Google’s side, but the city council deprives me of any alternative.

  3. It’s easy to scapegoat than to look at it with a keen eye.

    Was MV better before all the other HUGE tech heavyweights moved in in the 80’s and 90’s, well before Google? Ever see this area before Sun Microsystems and SGI? Where’s their blame?

  4. Originally LinkedIn and Google had a plan and jointly took it to the city which approved of the plan. It covered 24 acres of land, of which 16 acres belongs to SyWest. Then Linked in made additional purchases and end up owning 6 more acres
    of land on the other side of SyWest’s property bringing the total up to 30 acres. But what was approved was 1.6 Million square feet of added office space on those original 24 acres, and SyWest contributed to that the integration with their property which was very important for the LinkedIn land along the freeway,
    which does not have good access to Shoreline.

    Anyone looking at the current traffic flow can see that the SyWest property is a
    major cut through for traffic leaving Google’s buildings at night and heading over to Shoreline.

    So now Google has to add 7000 units of housing somewhere. But the overall area is 500 acres and Google occupies and continues to develop a large part of it. So this is just a case of them saying that SyWest should provide housing to allow Google to grow. SyWest’s plan has 800 units of housing on its own, which is a very fair share of what’s needed considering they only have 16 out of 500 acres.

    SyWest can just sit on their property as-is, indefinitely. It only gets more valuable with each passing year. But they might close off the cut through traffic that is messing up the movie theater parking lot.

  5. As I have been predicting.

    This project will never get started.

    The parties of Google and SyWest are niether feasable or defined enough to get a green light.

    This is by design because both of them want the ability to make changes that radically change the plans after they get apporved.

    This is what cannot occur given the new state laws placing significant liablilty on the City for failure to comply with the new laws.

    As of this time the project is just about dead on arrival, or at the very least on life support before getting to the hospital.

  6. I can see this ending with Google buying SyWest off. Or, at least I hope they do. I view Google as being more responsible and committed to a long-term “greater good” policy for rational and integrated development of N Bayshore.

Leave a comment