The Tragedies of Sauk Creek Greenway

(disclaimer: this is a personal blog and not an official position of Madison Bikes)

Alder Nikki Conklin recently announced the scuttling of a long-planned North/South path through the Sauk Creek Greenway on Madison’s far west side. This is an unfortunate capitulation. The tragedy isn’t so much the loss of the path, but the way in which it was lost and how it unfairly perpetuates a “Bikes vs Trees” narrative.

If you just want action, jump to Next Steps at the bottom of this painfully-long blog.

I’ve also added a footnote¹ with updates and follow-ups since this blog was originally posted.

Background

The 26-acre Sauk Creek Greenway snakes from Tree Lane to Old Sauk Rd. There has long been a stormwater project to deal with years of neglect and surges of stormwater from west side development, particularly the parking lots near Menards. The issue became critical after the 2018 floods which resulted in the drowning death of a person in the nearby Chapel Hill-Greentree greenway, an area with many similarities to Sauk Creek. That incident resulted in the $5.9M McKenna Boulevard Flood Mitigation Project.

The Sauk Creek stormwater project’s goals are to stabilize the creek and build a gravel service road similar to the ones in Owen Conservation Park and Pheasant Branch north of Century Ave. The project would also thin the trees according to a soon-to-be-released corridor plan. It’s expected that the City will want to remove all damaged and unhealthy trees, and also many of the less desirable trees that are crowding the more desirable trees. Opinions vary on what is a “desirable” tree, but there’s no doubt the current greenspace is a product of neglect and mesophication, and there isn’t a single healthy oak tree under 80 years old. Unlike Owen, Olin, Hoyt, Picnic Point, and other urban greenspaces, this greenway has never had a volunteer group clearing invasives, burning duff, stemming erosion, maintaining trails, etc.

Throughout the project, neighbors have rightfully expressed concerns about what tree removal will look like, especially after a different tree-thinning exercise a few blocks away seemed excessive:

As far as I can tell, the City departments involved seem to have been responsive, going so far as to inventory the entire 26-acre wood and its 5500 trees, post a list of every public meeting and department involved, publish a community engagement guide, and issue multiple statements to dispel misunderstandings that had arisen. However, throughout the process one can’t help but sense that neighbors seemed more interested in how the project will affect their own properties than the City’s.

Enter the “Friends”

In mid-2022, the “Friends of Sauk Creek” formed. Unlike most “Friends” organizations that help improve our parks and open space, this group’s single goal was to “stop plans to remove 5,500 trees during a reconstruction of Sauk Creek,” i.e., to ensure nothing changes. [Update: their new web site has expanded their mission to include “stop bike paths in the nearby woods.” Their old web site with much of their history is still in google’s cache]. The leaders are nice, intelligent people and they’re passionate about their neighborhoods. But for reasons I can’t explain, their manner of engaging with the City quickly turned belligerent and hostile, and they’ve shown little interest in compromise or finding common ground.²

The group aggressively took the planners to task, demanding details and impacts long before any engineering had been done to provide precise answers. They looked for inconsistencies with what was said by different people in different City departments, jumping on them as signs of malfeasance or secrecy. They apparently filed Freedom of Information Act requests. To this outsider, their treatment of our City officials seemed unfair and unwarranted. Despite all that, a petition they crafted in late 2022 calling for public involvement in tree-clearing decisions was calm, measured and entirely appropriate. It got 373 signatures. I would have happily signed it.

Their true colors were revealed in May 2023 when they rallied to kill a planned youth single-track MTB trail in Walnut Grove Park that would have provided youth recreation similar to the Aldo Leopold Park shred-to-school trails. The trail didn’t endanger a single mature, healthy tree and was environmentally compatible with the park’s existing uses (which include a dog park!). With no environmental reason for their opposition, it’s impossible not to conclude that the “Friends” group is more concerned about the users of the greenway than the health of the greenway. To them, the greenway should remain their own private backyard in perpetuity and anything that brings more people into the area is a threat.

During a meeting in July 2023, City planners indicated that the stormwater project may be coordinated with a long-planned North/South path through the greenway. This would mean paving and grading the access road to ADA and NACTO path standards, adding one or more bridges, and connecting the path to the City’s growing All Ages & Abilities bike network. The idea of a path goes back at least to the 2000 bike plan (pg 84) where it was listed as a “third priority” because “suitable on-road routes exist.” The “Friends” group twists that to say that the City had declared the path “wasn’t a priority.” In reality, “third priority” means exactly that and, after 24 years, many of the other “third priority” projects have been completed, including Wingra Creek underpass, Stricker Pond path, a path in Blackhawk Park, the new Starkweather bridge, etc. The path again appeared in the 2015 bike plan on the future map (figure 4-7, pg 39). It also was on the West Area Plan that kicked off in early 2023.

At some point, East/West path connections through the greenway were also added to the West Area Plan. I’m not sure the history of that, but do know that students headed to Memorial High School, Jefferson Middle School, and the Lussier Community Center have expressed a desire for an E/W connection without having to go all the way down to Tree Lane. For some, an E/W connection will eliminate up to a mile of extra travel and avoid having to take busy four-lane Old Sauk Rd. It will also provide a connection to WisDOT’s planned bike/ped beltline bridge just to the west. Even after Alder Conklin capitulated on the N/S path this week, the E/W path remains in the plan and will surely be a continued fight.

Enter the Boogeyman

Once the “Friends” heard about a paved path, they were livid and shifted their attention towards this new boogeyman — the bike path! After all, what better symbol of hatred than a smug, entitled biker?

Their web site soon shouted “City planner describes creek area as biking hub; it could destroy thousands of trees, birds, wildlife.” Taking a lesson from the “see what sticks” playbook, they brainstormed a random assortment of false and exaggerated talking points, listed below (with my rebuttals):

• “Thousands of trees removed”, “decimate”, “reduced canopy”, etc. (The stormwater project is what will remove trees! A paved path will only require minor additional tree removals for bridges and the E/W path. Engineers will surely try to avoid the healthy, desirable trees.)
• “Destroy nature”, “harm animals”, etc. (Paths are not a major factor. Studies do show that mountain biking can impact nesting habits of some bird species in wilderness areas. But this is an urban greenway; any animal here is adapted to houses, highways, noise, and the adjacent dog park. Turtles even dig their nests next to paths.)
• “The path’s impervious surface will leach toxins into our lakes!” (Path asphalt is inert and the path has no gutters or drains for water to reach the lake. All rainwater soaks into the ground a few feet from where it falls. Porous asphalt can also be used, as Fitchburg did along Lacy Rd. Toxins from asphalt largely come from driveway sealants used by homeowners.)
• “The grade is too steep and the path will be dangerous!” (The grades are nothing that design engineers couldn’t handle; overall it’s much tamer than paths in Yarmouth Crossing and Pheasant Branch Creek.)
• “Heat-island, climate change!” (The stormwater project is responsible for the extent of tree removal; their thinning will allow the remaining trees to flourish, improving the overall canopy. Plus, if the path can convince even a single person to give up their car or drive less, that can save up to 250 mature trees worth of carbon capture. Biking and walking are climate solutions, not problems!)
• “The path will be lighted!” (This is not in any plan and is technically challenging. It would only be added if neighbors asked for it. [edit: see footnote 1])
• “The cost will be $6M! or $7M!” (The City doesn’t have a design detailed enough to know what the cost will be. By the time the stormwater project has rehabilitated the gravel access road, the cost to add asphalt and bridges should be very reasonable with most costs covered by a federal grant.)
• “Bikers are fast and dangerous” (FUD. See below for why this path would not be a major bike thoroughfare.)
• “The path doesn’t connect anywhere!” (Never mind the chicken-and-egg fallacy of arguing against paths because of lack of other paths, this path would have immediately connected to bike lanes on Old Sauk Rd and Tree Ln, and it would nearly reach Mineral Point Rd’s new widened sidewalk. The E/W path will connect WisDOT’s planned beltline overpass at Sauk Creek Park.)
• “The path isn’t needed because there are other routes on Westfield and High Point!” (This is absolutely true for most bicyclists one sees on the roads today. However, it’s estimated that ⅓ of bicyclists only bike where there are comfortable off-street paths. This path could be the difference in whether a family bikes or drives to Swagat for dinner or whether their child can reach Alicia Ashman Library on their own.)

This last point drives me crazy and points to a major failure in City messaging. This path would never have been a major bike hub or bike highway on the order of the Capital City trail or Southwest Commuter Path. Instead, it would be a backyard greenway path similar to ones in Greentree-Chapel Hill, Oak Meadow, Mineral Point Park, Garner Park, and dozens of others. Those are all important bike connections, especially for All Ages and Abilities, but they attract far more walkers, joggers, dog walkers, strollers, and kids than bicyclists. Most path users are from the adjacent neighborhoods.

Mobilization strategies

The “Friends” group issued a second petition in Fall 2023 filled with their false talking points, though it moderated its words on tree removal. Curiously, they only got 305 signatures, far less than the 2022 petition. This could have been due to shortness of time, but it might also be due to neighbor fatigue. I’ve spoken with several people in the area including a few who are serious conservationists and, frankly, they’re bewildered by how sideways things have gone and they’re afraid to speak up because of the power the “Friends” group seems to wield.

Another pillar of their mobilization strategy was to hound and harass every public servant and every public meeting related to the West Area Plan with emails, public comments, and in-person confrontations. Ald. Conklin’s inbox probably has a thousand messages about it, far more than any human could read, let alone reply to. At the Wisconsin Healthy Communities Summit last week, State Senator Chris Larson advised that one key to successful government advocacy was to “point out the problem without being problematic.” The “Friends” group proves him dead wrong! I recall one technical zoning meeting where an exasperated attendee asked of the barrage of Sauk Creek path comments, “Do these even refer to anything on the agenda?” (they didn’t, but it was a public meeting so there was no stopping it)

It was also agonizing to see how much time and energy the “Friends” group was able to extract from their own members. I’ve read every public comment from a half-dozen meetings. Most are earnest and thoughtful, and many brought up well-researched concerns about project bounds, path routing, grade, erosion, proximity to yards — all issues that would be really helpful during the design phase, had there been one. But so many of the messages also raised the same false and exaggerated talking points. At one meeting, a neighbor with a disability stood in opposition to the path because she couldn’t imagine how an ADA path could navigate the terrain. With the project now scuttled, we’ll never know how engineers would have solved that; but they would have.

A third pillar was the press. By framing this as “David v Goliath,” “neighbors saving trees from uncaring City planners,” or “trees versus bikers”, they got a lot of sympathetic press. Allison Garfield’s excellent Capital Times piece “A Silent Deforestation” gave most coverage to the neighbors, but it was extremely fair in presenting the City’s position. WORT‘s earlier coverage was similarly balanced. Coverage in the Wisconsin State Journal was more lopsided for the “Friends”, and Cap Times editor Paul Fanlund proved himself a sucker for the false messaging, lobbing cheap shots against bicyclists in his opinion piece on zoning changes.

The fourth pillar was to capitalize on the public outcry about proactive zoning, as Fanlund had done. The zoning issue is important and potentially affects the entire city, but it has nothing to do with the local Sauk Creek stormwater project. That didn’t stop a former Common Council candidate from making this FOX news-worthy video that egregiously conflates the two issues.

City Capitulation

The strategy of the “Friends of Sauk Creek” worked. The city is now planning to remove the N/S path from the West Area Plan. This is no big loss for the overall bike network, but it is a tremendous loss for low-stress bicycling since beautiful paths like this are often what get people hooked on biking in the first place. I personally think it’s also a huge loss for the neighborhood, but that’s really for the neighbors to judge.

The biggest tragedy for me as a transportation advocate is that this loss is entirely due to misinformation and bullying. The “Friends of Sauk Creek” apparently feels no shame in their tactics and perhaps this is just a case of local democracy emulating national politics. But that doesn’t make it right. It’s embarrassing to see it succeed in Madison.

Of course, the “Friends” aren’t done. Of course they know the path has little impact on tree removal. They will fight the E/W path that remains in the plan. They will fight the stormwater project later this summer. And, in a couple years, they’ll be fighting the off-street bike paths now planned for High Point and Westfield Rds — paths that will end up costing far more than the greenway path and that will remove parking and disrupt the front yards of the fifty or so home- and condo- owners on those streets.

What’s next?

Madison’s West Area Plan updates and information about all upcoming meetings are posted at https://www.cityofmadison.com/dpced/planning/west-area-plan/3896/. The Sauk Creek path change has two meetings:

• virtually on Thursday May 30 at 6pm
• in-person open house at High Point Church on Thursday June 6 from 6-8pm. Fortunately or not, this falls in the middle of Bike Week!

As bicyclists, our goals should be to show overwhelming support for the East/West path and to try to restore the North/South path through the Sauk Creek greenway.

Our success depends almost entirely on helping opposition neighbors to (a) understand that the paths are not responsible for mass tree removal and (b) that paths will be an asset, not a threat, to the neighborhoods, the greenway and the adjacent property owners.

Let’s mobilize with facts and kindness. Let’s help the opposition think about how they might personally benefit from a path. E.g., walking a dog without getting muddy feet or ticks, morning jogs or birding, walking or biking to dinner, sending your child alone to the park or library, and so on. If quality-of-life gains aren’t enough, remind them that a trail will increase property values by 3-5%.

Most importantly, let’s encourage them to go explore the similar greenways to see what paths are really like and how other neighbors use them. Here are four ideal ones to visit:

• Middleton’s Pheasant Branch Creek path (at Park St, not the larger area north of Century Blvd) is most analogous to Sauk Creek in terms of narrowness, length, and terrain.
• The Mineral Point Park path from behind Memorial High School to Inner Drive. This is similarly narrow to Sauk Creek but has a concrete stormwater drain.
• Fitchburg’s paths like Nevan Springs/Buttonbush and Oak Meadow have adjacent houses. Here you can see how homeowners integrate their yards with the paths while maintaining privacy.
• The Cap City trail west of Fish Hatchery (park at Adesys) is a popular trail so expect a much higher volume of bike traffic. It has steep grades, multiple bridges, and a meandering creek whose banks are reinforced with natural boulders.
• The gravel maintenance road in Owen Conservation Park from Inner Drive to Forsythia Pl. This is what Sauk Creek’s new maintenance road will look like unpaved. The corridor width is not that different from a paved path.

There is a path to saving the path.

1. Update: Added Mineral Point Park path to the list of suggests greenways to visit. Errata: Although the “Friends” group does not organize it, some Sauk Creek neighbors do independent garlic mustard removal and other woods maintenance. Follow-up: The “Friends” group has not responded to this blog , but instead doubled-down on their misinformation in a May 19 blog. Follow-up: social media discussions about this blog are at Nextdoor and Reddit (and earlier Reddit). A very good policy discussion about paths in Sauk Creek greenway took place in the Dec 13, 2023 meeting of the Madison Transportation Commission (watch here from 1:52:00 to 2:33:45). In it, and also at a June 6 meeting, City engineers said they preferred paths to be lit but that it was very much a design question, decided by public input. ↩︎
2. To be transparent, I have no first-hand exposure to the Friends of Sauk Creek prior to Fall 2023, so all descriptions of earlier events are based on the public record. There may be other plausible explanations. I welcome the “Friends” or other involved people to help correct the record and point out any mistakes they read in this blog. ↩︎