Otis White

The skills and strategies of civic leadership

  • About
  • Archives

Connecting the Phases: The Guiding Coalition

December 6, 2011 By Otis White

In a series of postings, we’re exploring how conscious change happens in communities. If you haven’t read the first posting in this series, please take a moment to do so.

As we walk through the community change process, let’s pause and see if we can connect more closely the first two parts, the discussion phase and planning phase. Briefly, the discussion phase awakens the community to a need and pulls together a group of people to search through a number of possible answers for a workable solution. The planning phase takes the workable solution and turns it into a set of specific plans that speak to the public, decision makers, and funders. It may also involve organizational work and fundraising.

What connects these phases? Aside from you, as the primary leader, it’s the guiding coalition. This is the group that helps you, in the discussion phase, sift through possible solutions and come up with the one to take forward. In the planning phase, you still need a group—if anything, the tasks multiply and grow harder, so you need others to help carry the load. And the obvious people to begin with are those who were with you in the discussion phase. After all, by this point, it’s their project, too.

But who else is needed? As I mentioned in an earlier posting, a good way of thinking about guiding coalitions is to consider people with expertise, power, credibility, and the ability to get things done. How does this change in the planning phase? It doesn’t. It’s just that, as you work into the details, the problems and opportunities grow narrower and deeper, so you’ll need people who can help you not just with the broad outlines of community change but the crevasses as well.

To make this clearer, let’s return to the example I used in my planning phase posting, the building of New York’s High Line Park. Remember that this project began in 1999 when two neighborhood residents, Joshua David and Robert Hammond, learned that an abandoned elevated freight line running through their West Side neighborhood was to be torn down. They both had the idea that something, some kind of public space, could be made of this industrial relic and provide a much needed amenity. Thus began one of the most astonishing urban improvement projects of the past half-century, culminating in 2009 with the opening of a park in the sky, one of the country’s most innovative public spaces.

Who joined David and Hammond’s guiding coalition, and when did they join? As they write in their book, “High Line: The Inside Story of New York City’s Park in the Sky,” David and Hammond started out with little knowledge of parks, planning, politics, or charitable fundraising. So they began with what they had: friends who knew people. And, here, they were lucky. Hammond had gone to college with a man who had become a well-connected New York lawyer. He introduced David and Hammond to the first member of their guiding coalition, a developer and former political insider named Phil Aarons. Aarons had three of the four qualities a guiding coalition needs: expertise, credibility, and the ability to get things done. He was immediately won over by the idea of the High Line and invested untold hours in making introductions, attending meetings, and advising David and Hammond about politics and public opinion.

Hammond had another college friend, Gifford Miller, who was by then a city council member (he would later be president of the council). Skeptical at first—Hammond says Miller called it a “stupid idea” when he first heard it—Miller changed his mind when Hammond took him atop the High Line and he saw its potential. Miller brought credibility and expertise to the group (he knew city government and especially the city council) and, of course, power.

Others joined the coalition soon after. There was a lawyer who understood transportation law and federal regulation, and helped guide them through the federal maze. Miller brought in the city council’s zoning and land use attorney. Aarons introduced David and Hammond to Amanda Burden, who was then a member of the city planning commission. In time, Burden would become the project’s most important champion and strategist. (In a stroke of luck, when Michael Bloomberg was elected mayor, he appointed Burden the city’s planning commission chair, which is a powerful position.)

Even more joined in time. One was a city government lobbyist who knew the nooks and crannies of city hall even better than Miller and Aarons. Another city council member, Christine Quinn, came aboard. An economic development expert, John Alschuler, was hired to study the project’s impact on property values and was so taken with the High Line, he stayed on as a volunteer and became part of the inner circle. There were others: One was a man who knew so much about the neighborhoods that the project crossed that he was known as the “mayor” of the lower West Side. He helped convince building owners and neighborhood groups to support the High Line. Finally, as the project moved into major fundraising, a partner at Goldman Sachs, the Wall Street firm, joined the group to help them connect with the wealthiest families and corporate interests.

These people came as needed. Alschuler was brought into the inner circle after the workable solution had been identified and when more detailed plans were needed. The lobbyist and neighborhood “mayor” joined as the approval process, at city hall and in the neighborhood planning boards, approached. The Goldman Sachs partner arrived after the project had won its most critical approvals and its heaviest fundraising began.

Others were influential, but more as allies than members of the guiding coalition. One was Dan Doctoroff, the deputy mayor for economic development. Acting on Mayor Bloomberg’s behalf, he had major development plans for the northern end of the High Line, an area called the Far West Side. Doctroff’s support was crucial for the High Line but his own plans were controversial. So David, Hammond and the rest of the guiding coalition walked a fine line. They had to stay in Doctoroff’s good graces while not being too supportive—otherwise the neighborhoods would have turned against the High Line. Somehow they managed this well enough that when Doctoroff’s Far West Side plans fell apart, the High Line sailed ahead . . . with Doctoroff’s support.

There were other important supporters, including celebrities, business leaders, politicians, and society mavens, and they were frequently consulted. But they weren’t in the guiding coalition. Yes, they might be in the ribbon-cutting photographs or featured in videos and printed materials (that was a way of compensating them for helping out), but they didn’t map strategy or search for answers and allies. That was the work of the guiding coalition.

At a point, the High Line needed more than a loose coalition; it needed the structure of a full-blown nonprofit, which came to be called Friends of the High Line. Many of those who were in the informal guiding coalition became board members. Aarons was the first chair of the Friends of the High Line. The next was Alschuler, the economic development expert who started as a consultant and became an advocate.

The interesting dynamic about guiding coalitions is how members’ involvement waxes and wanes. That is, at a point, one person might be the key member because she has the critical expertise or credibility, but at a later point, she may not be as central to things. As long as it’s an informal coalition, these things are almost self-regulating. That is, as people feel they are needed, they step up. When they’re no longer needed as much, they drift away.

When a coalition becomes a nonprofit board, though, it takes greater management. Someone has to choose who stays on boards and who leaves. This is known as “board development,”and it is one of the most important strategic duties a nonprofit director and board chair make. And how do you choose good nonprofit board members? Well, expertise, power, credibility, and the ability to get things done are good places to start. But add one more: the ability—and willingness—to raise money.

Planning Phase: The Slog of Civic Projects, and Why It’s Critical

November 18, 2011 By Otis White

In a series of postings, we’re exploring how conscious change happens in communities. If you haven’t read the first posting in this series, please take a moment to do so.

In a time when many wonderful parks have been built, New York’s High Line may be the most wonderful of all. It’s a park that runs above the street and through buildings on Manhattan’s west side. If you climb the stairs and walk the portions that are completed (it will eventually be a mile and a half long), you’ll see something at once modest and spectacular. The modest part is the park itself, a narrow trail edged with plants and trees with resting areas along the way. The spectacular part is the setting: a park in the sky, wending its way through post-industrial New York. The reviews, as you can see in this video, have ranged from glowing to awestruck.

But my interest is not in the park itself. It’s in the project—the road the High Line traveled from a pair of neighbors looking up and seeing potential in an old elevated track until its opening in June 2009—and what that journey tells us about the second phase of our map of community change, the planning phase.

Background: In 1999 two men, Joshua David and Robert Hammond, attended a neighborhood planning meeting on the future of the abandoned rail line known as the High Line. Some landowners wanted it torn down to make way for new developments. David and Hammond, who did not know one another, came with another idea, that you could turn this elevated freight line into . . . something else, some kind of community asset.

Their ideas were vague. They thought about a park of some sort, but what kind of park could you build on a narrow set of elevated railroad tracks? And David and Hammond hardly seemed the type to turn vague civic ideas into reality. David was a writer who specialized in travel articles for glossy magazines. Hammond was a consultant to business startups. Neither had run a nonprofit, managed a park, or had any serious contact with government at any level. They came to the meeting with hopes of volunteering for a nonprofit—any nonprofit—that would make the High Line into a community asset. What they learned was there was no such nonprofit. So, pretty much on the spot, David and Hammond decided to do it themselves.

If you’re following this on the map of community change, we’re at the very start of the discussion phase, with the recognition of a need. Or, in this case, two needs. The first was David and Hammond’s belief that, in the crowded lower West Side of Manhattan, there wasn’t nearly enough open space. That part of New York takes in many old industrial areas (one neighborhood is still called the Meatpacking District). In the late 19th and early 20th century, New York didn’t build parks in places like that.

The other need was for quick action. If somebody didn’t act soon, they believed, the city would tear down the High Line and an opportunity for public space would be lost forever. (They were right. Less than two years later, the Giuliani Administration sided with the landowners and signed a demolition order for the High Line.)

A funny thing happened, though, once David and Hammond took up this project. It turned out—to their surprise and others’—that these two were uniquely equipped for a civic project of this magnitude and complexity. While they had no experience in leading an urban change effort, they had valuable and complementary skills. One could write well and knew some in New York’s social and philanthropic circles. The other was experienced in starting things, was at ease in asking people to do things (including giving money), and had a good sense of strategy. They were both quick learners, and each had an interest in art and design, which became important as the project moved forward.

It took three years of contacts, conversations, fundraising and strategic planning for David and Hammond to accomplish two things that ended the discussion phase and began the planning phase: First, they halted the demolition order with a lawsuit; second, they arrived at a workable solution for the High Line. You can view their workable solution online. It’s a 90-page document titled “Reclaiming the High Line,” researched by a nonprofit called the Design Trust for Public Space and written by David.

It’s an interesting document for three reasons. First, it’s beautifully designed. It had to be because it was aimed at multiple audiences: the political and planning communities that had such a big say in what would happen to the High Line; the community nearby, which at that time had barely any idea of the High Line’s potential; and possible donors who needed to understand the High Line’s vision.

Second, it’s modest in spelling out that vision. While it makes a strong case that the old freight line should not be torn down, used as a transit line, or turned into a commercial development (a long, skinny retail area, perhaps?), it doesn’t say it ought to be a park, either. It simply says its best use is as open space in a part of the city where there isn’t enough. In other words, the workable solution keeps its options open.

The third thing that’s interesting is who wrote the foreword: Michael Bloomberg, who by 2002 had succeeded Rudolph Giuliani as mayor. This gets to an important element in any change effort: luck. The High Line project was lucky in who got elected during its 10-year path from concept to ribbon-cutting, starting with the person in the mayor’s office.

Well, if a workable solution is at hand and a powerful new mayor wants it to succeed, that’s that, right? What else is there to do? The answer: The real work was just beginning. And this is my central message about the planning phase. Getting agreement on a workable solution is like getting everyone to agree on the design concept for a new house. Now comes the difficult, detailed work of hammering out costs and financing, drawing blueprints and mechanical plans, obtaining building permits, and bringing together a small army of independent contractors.

As David and Hammond explain in their book, “High Line: The Inside Story of New York City’s Park in the Sky,” even with the new mayor on their side, there was still a gauntlet of approvals to be run, from community planning boards (basically, neighborhood organizations that review developments) to the owners of the High Line (CSX, the railroad company) and the federal agency that approves transfers of railroad rights of way. And they had opposition: from landowners who had expected to build where the High Line stood, but also from residents who couldn’t see how the dark, peeling, scary elevated railroad could ever be anything but an eyesore. Finally, they realized a truth about government: that, even in a strong-mayor government such as New York has, the mayor doesn’t call all the shots. As Hammond writes:

(By late 2002) the Bloomberg Administration fully supported the High Line, but if they’d only endorsed it and done nothing else, the project would have died. Everything about the High Line was complex, and it had to pass through so many different agencies and departments. City government is like the human body: the head, which is the mayor’s office, may want to do something, but the body has a number of different parts that want to go their own way.

Everything hinged on three tasks that occupied much of the High Line’s planning phase: Coming up with a design for the park that would please politicians and neighbors and excite donors; dealing with the landowners’ objections; and figuring out how to pay for the construction and maintain this most unusual park in years to come.

If this doesn’t sound like exciting work, it wasn’t. This is the slog of civic projects, but it’s also why the planning phase is so important. Managing these details determines the success or failure of projects. And there were hundreds of details, from mapping the decision points and how to approach each of them to knitting together a coalition of supporters and funders. There were competing interests that had to be satisfied and intense politics. Oh, and they had to design a park unlike any in the world, and figure out how to pay for it.

What this phase requires from leaders are three things: the ability to plan (that’s why it’s called the planning phase), a mastery of detail (in an earlier posting, I called this the realm of “small-p politics”), and a willingness to ask for things. Throughout its development, David and Hammond asked people to do things for the High Line. Early on, they asked for information and advice (who owns the High Line, and how should we approach them?). Soon after, they asked for support and permission. In time, they asked for money. They started by asking for a small sums for printing costs and filing the lawsuit against the demolition. Eventually, they asked philanthropists and politicians for millions to pay for the park’s construction and maintenance. And they got it, in ways that surprised even them.

This brings us to the three elements of the planning phase that are in the map of community change: champions, narrative and strategy. I put them in the map as reminders. We’ve talked about one, strategy—that’s about mapping the decision points and making plans for each decision. This is the “inside game” of civic change, the political and bureaucrat checklist of approvals.

But there is always an “outside game” as well, and that’s where the narrative becomes critical because it speaks to citizens and potential supporters and donors. A narrative, of course, tells a story. It explains the need, why the need exists, the opportunity for addressing the need, how the solution was arrived at, and the future benefits of the change. Sometimes, the narrative has to change how people think about their community and its potential, something I call “reframing the community’s mind.”

And finally, there are the “champions.” Obviously, David and Hammond are the central figures of the High Line project. Without them, the freight line would be a memory and a remarkable asset squandered. But they aren’t the champions I have in mind; they’re the leaders and strategists. The champions are those whom David and Hammond asked for support who brought others along. Some were political champions who used their influence to win approval and gain government funding—people like Mayor Bloomberg, two successive city council presidents, New York’s senators and congressional representatives, and a host of people inside the bureaucracy.

There were also business and philanthropic champions, like media tycoon Barry Diller and fashion designer Diane von Furstenberg who lent their names, made major financial gifts themselves, and hosted fundraisers for the High Line. Finally, there were celebrity champions who helped raise money and call attention to the High Line. An early celebrity endorser was actor Kevin Bacon, whose father had been an urban planner. Another actor, Edward Norton, also had a family interest (his grandfather was the pioneering urban developer James Rouse). When he read about the High Line project in a magazine article, he tracked down David and Hammond and offered to help out. As you can see from this video about the High Line, made before its opening, what Norton brought was public attention, which is what stars do.

The final box in the planning phase is “the plan,” but that’s a little too simple. In all likelihood, it’s not a single plan but a host of plans: one describing the project’s feasibility in great detail for decision makers, one speaking to the public about its benefits, one setting out the financing (for decision makers and funders), and one describing the design (if it’s a physical project). There will likely be internal documents that serve as a kind of project flow chart, laying out the approval process and decision points, and what each approval will require, so you can marshal the right supporters. Finally, your project may need interim funding, to print materials, commission studies and seek expert advice. You’ll need a plan for getting that funding along the way.

As I said earlier, this isn’t glamorous work; it’s a slog. The amount of detailed work and its complexity will test civic leaders’ commitment and attention spans. There will be victories along the way, and it’s important to broadcast them to keep your supporters’ spirits high. “One of the keys to the High Line’s success,” Hammond writes, “was in always showing progress, even if it was a really small step.” And sometimes there are big steps, like the day in late 2004 when Josh David opened an envelope and found a check for $1 million inside, from a donor he and Hammond had courted.

But make no mistake: This is the period when obstacles are met and overcome—or not. Do the planning phase right, and the next one, the decision phase, will be a triumph. Do it poorly and your chances of success are about as good as winning the lottery: theoretically possible . . . but practically impossible.

Photo of the High Line by Katy Silberger licensed under Creative Commons.

Discussion Phase: How Need, Relationships, and Ideas Begin the Change Process

October 21, 2011 By Otis White

In a series of postings, we’re exploring how conscious change happens in communities. If you haven’t read the first posting in this series, please take a moment to do so.

Let’s start at the top of the map, with the discussion phase. This is where change begins, with a leader recognizing a need and using her relationships, a set of ideas and a series of discussions to find a workable solution. But don’t let the casual-sounding name fool you. The discussion phase isn’t chit-chat; it’s a structured process involving different types of conversations with different groups, each a critical step in the change process. This phase ends with a decision about the solution to take forward.

Community change map

You begin with the need—the community problem or opportunity that’s the reason for the change process. This sounds so commonsensical that I’d hesitate to mention it were it not for the fact that most community change efforts (and virtually all failed ones) begin with something else: a solution.

Look at the ideas floating around your city. If it’s anything like mine, you’ll find proposals for streetcars, parks, bike trails, changes in taxes, water conservation, redevelopment finance, road improvements, zoning regulations, and on and on. What do most of these ideas have in common? They’re solutions without context. Their proponents serve them up without first establishing the problem they’re intended to solve. As a result, they create a ripple of interest . . . before sinking out of sight.

Business consultant William Bridges knows why this doesn’t work. As he warns corporate executives:

Most managers and leaders put 10 percent of their energy into selling the problem and 90 percent into selling the solution to the problem. People aren’t in the market for solutions to problems they don’t see, acknowledge, and understand. They might even come up with a better solution than yours, and then you won’t have to sell it—it will be theirs.

Right on both points: If people don’t believe a problem exists, they’re not going to buy its solution. And when they do accept the need, they’ll often come up with good solutions on their own—which ends not with your leading people but marching with them. And that’s exactly where you want to be.

The keys to introducing a successful change process, then, are to convince citizens and decision makers of the need for change and, in time, facilitate a group of people who’ll arrive at a solution. Let’s take these in turn.

Begin with the need. It can be a problem (vacant properties in a neighborhood, say, or a declining local economy) or an opportunity (a local university that could have closer ties to the community). It can be a short-term problem (say, a spike in crime) or a long-term problem (domestic violence). You might start out with a solution in mind. Let’s say you’re concerned about obesity, and it seems to you that more sidewalks and playgrounds could go a long way toward solving it. If so, put aside your solution and concentrate on the problem.

This is harder than it seems. We were all rewarded in school for having the right answers, but in leading a change process it’s better to be the quiet kid in the back of the room than the one in the front row with his hand up. Why? Because many people eye change suspiciously. You may think you’re offering helpful ideas when you volunteer solutions, but some will see a hidden agenda. It’s better to say you don’t know the answer yet—and politely ask people for their thoughts.

And then there’s what William Bridges said: If you’re successful at getting people to accept the problem and think about it, they may come up with better solutions than you had anyway. So for both reasons—it lessens resistance and opens the door to other, perhaps more creative, ideas—it’s far better to sell the problem at first than to push a solution.

But how do you sell a problem effectively? I’ll write more about this in the future, but in general leaders must do four things to move people from awareness to action. They have to convince them that:

  • The problem is a community problem; it’s not just a personal issue.
  • It’s an important need, one that affects the community’s future.
  • It is urgent; things will grow worse with delay.
  • It’s possible do something about it; the community has the ability to solve the problem or significantly reduce it. It’s not hopeless or beyond reach.

When you convince people—decision makers and citizens—of these four things, something wonderful happens: People and resources are drawn to you. If offering solutions builds resistance, convincing people of needs does the opposite: It smooths the path of acceptance. Again, the trick is to build confidence that a solution can be found while not offering up a specific one.

The next step is to gather a group of people to talk about the need, discuss a range of possible solutions and agree on one to take forward. Who should be in this group? If you’ve done a good job of talking about the need—in small meetings with decision makers, in larger forums with citizens, perhaps through the news media and social media—then you know some who should be included. These are people who’ve responded to your call for action with support and resources. If you’ve spent time building relationships in the community (see “What Glengarry Glen Ross Teaches Us about Change“), you’ll know others who should be involved.

But you should also be strategic. You are assembling what John Kotter, the Harvard business professor and expert on corporate change, calls the “guiding coalition” for the change process. The coalition will change somewhat as you move through the planning and decision phases, but basically it is the group that will be the brains and muscle behind your initiative, the strategists and doers.

And who makes up a strong guiding coalition? Kotter suggests four types (which I’ve modified slightly for community change projects):

  • People with expertise in the issue.
  • Those with power in this area.
  • People with credibility in the community.
  • Leaders who’ve shown they can get things done.

For a change effort about obesity, then, the experts might be public health officials and perhaps those who run youth sports programs. Those with power might include school system officials, city parks officials and public-works officials. The other two types are harder to suggest, but you almost certainly know those in your community with a track record of getting things done and those whose judgment is respected. For the latter type, you might want to consider leaders in your city’s ethnic communities: If there are special problems with obesity among African-American or Latino youths, who can speak credibly for, and to, these families?

When you bring the coalition together, the initial goal to arrive at a workable solution (see “What Makes a Solution Workable?“). How do you manage such a thing? Well, there’s a great deal to learn about group facilitation—far more than I can cover in this posting—but three guidelines will serve you well:

  • Be patient. You will almost certainly introduce people to one another, so allow time for members to talk and listen. Good decisions require trust and candor. You won’t get them in a single meeting or probably in several sessions . . . but you can in time.
  • Start with the need and return to it frequently. The best way to begin a group’s work is with the need: a thorough discussion of what makes the problem a community concern, why it’s important and urgent, and why members believe it can be solved. As the group gets bogged down debating solutions, bring it back to the need. It will remind members of the importance of their work and encourage them to stick with it.
  • Keep an eye on group dynamics. One dynamic to watch for is a rush to judgment by the experts or those with power. This shouldn’t be surprising. These are people who’ve been thinking about this problem for years. They may even have solutions they’ve promoted in the past that they’d like the group to endorse. You’ll need the others—those with credibility and leadership ability—to slow things down by asking questions, gently challenging assumptions and pushing for new answers. This is an important role but one that some are uncomfortable playing. So before the first meeting, you may want to ask one or two of the most confident leaders to be the questioners of assumptions.

One way to improve the group’s work is with some “market tests” along the way. With the group’s permission, take its tentative ideas and assumptions to decision makers and citizens, through private meetings, op-ed articles and forums. This has an obvious benefit: Before committing to a solution, the group needs to know what decision makers think, how citizens respond, and where the likely obstacles lay. Yes, it will slow the process, but that’s not necessarily bad. It will prevent a rush to judgment and allow members time to know each other better.

And, who knows? Someone you talk with might offer a better solution than the ones the group was considering.

Photo by Jason Diceman licensed under Creative Commons.

What Makes a Solution Workable?

October 21, 2011 By Otis White

In a series of postings, we’re exploring how conscious change happens in communities. If you haven’t read the first posting in this series, please take a moment to do so.

At the end of the discussion phase, the guiding coalition settles on a workable solution. But what makes solution workable? And how will you know when the group finds one?

Actually, these are good questions for the guiding coalition. Ask members as they begin their work to say how they want to judge the solutions they’re about to consider. Write down the criteria they suggest, combine them into a small set of standards and hand them back to the group at your next meeting.

This may seem a little touchy-feely but it’s actually strategic. If you can get the group to set criteria early on, you’ll be able to steer it away from inadequate solutions (because they don’t meet the criteria) and free it from dead-end discussions (by reminding members of what they’re looking for). It will also help convince members when it comes time to dig deeper. If none of the alternatives they’re considering meets the criteria they’ve set, it’s time to expand the search for answers.

So, in every way, it’s better if the coalition sets its own standards. Still, you may want to think beforehand about what makes a solution . . . well, workable. Here are some starter ideas.

  • A workable solution answers the need. It’s surprising how often groups that are deep into the details forget why they started. As a leader, you can contribute to the coalition’s work simply by asking, “Does this really solve the problem?”
  • A workable solution can win the support of decision makers and the citizens—with hard work. Your “market test” discussions along the way will gauge this, but in the end it’s a judgment call: Do the members think they can gain enough support to win approval?
  • A workable solution is practical and sustainable. There are a number of tests here: Is the solution financially feasible? Will it attract the human resources (volunteers, staff, etc.) it will need? Can it maintain its political and popular support in years to come? If the problem grows or shrinks, is it scalable? You don’t need to think of every detail (that will come during the planning phase), but you do need a general idea of how the solution will sustain itself in the long haul.
Workable solution

When you put the criteria together, as in a Venn diagram, you’ll find the solution in the area where they overlap.

But how will you know that you’ve found the right answer? This is where the market tests will pay off. By talking with people outside the coalition about where the group is headed, you’ll learn quickly if the solution can generate the support it will need. And you can ask about the other criteria as well: Does it answer the need? Is it practical and sustainable?

When talking with others, don’t be put off by resistance. Resistance indicates that someone is taking your ideas seriously. In fact, if you don’t run into any, you should treat it as a warning that your coalition isn’t offering up much change. The question, then, isn’t whether there will be obstacles—there will be—but whether you can overcome them.

If you do all of this—define the criteria early on, search for new answers if the initial ones don’t meet your standards, judge alternatives rigorously, test your tentative ideas with decision makers and citizens, and know how you’ll deal with obstacles—you can rest easy. The guiding coalition’s chances of choosing the right solution are very high.

Photo by GotCredit.com licensed under Creative Commons.

A Map of Community Change

August 22, 2011 By Otis White

I have been haunted by a question for the past four years. After my company worked on a visioning project in a community not far from Atlanta, a business leader turned to me and asked, “So what do we do now?”

If I do say so, the year-long visioning project had gone well. More than 800 citizens participated in 12 visioning sessions, collectively generating more than 4,000 ideas and images of what they would like their community to be. Working with a planning group drawn from those who participated in the visioning sessions, we boiled down those ideas into 14 strategic objectives, 27 specific recommendations and 173 action steps. It was the greatest act of citizen engagement and planning the community had ever undertaken, and its sponsors were delighted with the results, which were ambitious, affirming and specific.

So I was happy to go back afterward to talk with one of the sponsors, a business executive with wide community and political experience who had immersed herself in the project. “So what do we do now,” she asked me. “How do we implement these ideas?”

I fumbled for an answer, saying something about creating groups to take charge of the most promising ideas, but I had two thoughts in the back of my mind. The first was that I was in the visioning business, not the implementing business. Thankfully, I didn’t say that. My second thought was one of surprise: You mean even smart and experienced community leaders don’t know how to get things done? Thankfully, I didn’t say that either.

It hit me as I drove back to Atlanta that I needed—and she needed—a theory of community change, one simple enough to fit on a sheet of paper but which fully describes the way complicated and diverse communities make up their minds to do something different—and get it done.

In the years since, I’ve sketched and resketched multiple versions of that theory. I tried first expressing it as a formula, kind of like E=MC².  Then I tried doing it as a step-by-step process. (I had been influenced by John Kotter’s eight-step process for corporate change.) Then I tried various ways of drawing flow charts. The problem, I quickly realized, wasn’t in how I represented the process; the problem was that it was hard to capture all the elements of community change and still keep it simple enough to be useful.

At long last, though, I have a version of what I’m calling a “map of community change.” (Click below to see it.) It’s a simplified flow chart (no diamond-shaped boxes indicating decision points, no concurrency symbols). Its value, I hope, is that it will help leaders figure out where they are in their own change efforts and where they need to go next. Which, of course, is why I’m calling it a “map.”

In the next few postings, I’ll explain different parts of the map. For the time being, though, take a look at the three horizontal “phases”—discussion, planning and decision. Community leaders, I think, concentrate too much on the first and third phases (the blue and green areas) and not nearly enough on the gray area in the middle. And it was this area that the business leader was asking about: How do we use an engaged group of citizens to prepare challenging ideas for public acceptance and government action?

Again, I’ll talk about the phases in detail in the coming weeks, but let me offer three general thoughts about the map: First, the most successful mayors, chamber executives and community leaders I’ve ever known carried a map like this around in their heads. They knew how long it took to travel from realizing a need to making a decision (and even longer to implementing the decision), and they knew that most ideas didn’t survive that journey. But for those that did, this was the road they traveled.

Second, the area where ideas succeed or fail is usually in the gray zone, the planning phase. It’s here that advocates assemble the elements of success (which I call, simply, “the plan”) or they don’t. (Bear with me; I’ll explain the elements in future postings.)

Finally, there’s something very big that’s not represented on the map: luck. Communities are conservative places; they don’t accept change readily. Responsibility is diffuse, interests entrenched, and power hard to bring together. And, as Barney Frank, the U.S. representative from Massachusetts, once explained, opponents start with a great advantage over supporters: “It’s easier to get everybody together on ‘no,’ ” he said, “You all have to have the same reason for ‘yes.’ You don’t have to have the same reason for ‘no.’ ”

For that reason, every big idea that succeeds in a community requires some amount of luck: things happening at the right moments to confirm—to the public, elected leaders and bureaucrats—that this is the right decision. I can’t think of how to picture it, but as you look at this map imagine that, at various points, there’s an invisible force at work that helps advocates overcome obstacles. I could probably think up a fancier name, but for the moment let’s just call it “luck.”

This is the first of a series of postings about mapping community change.

Photo by Mark Deckers licensed under Creative Commons.

« Previous Page
Next Page »

Recent Posts

  • The Next Urban Comeback
  • A Reservoir for Civic Progress
  • How a Leader Assembles a Winning Team
  • What Smart Mayors Can Learn from the Turnaround of Central Park
  • How Communities Can Thrive in a Post-Newspaper World
  • Seven Habits of Highly Successful Civic Projects
  • When Bad Things Happen to Good Governments
  • How Citizen Engagement Could Save State Politics
  • How Odd Couples, Complementary Needs, and Chance Can Change Cities
  • A Better Way to Teach Civic Leadership
  • The Worst Management Idea of the 20th Century
  • How to Deal with a Demagogue
  • What Government Is Good At
  • Return to Sender
  • The Loneliness of the Courageous Leader
  • A Better Way of Judging Candidates
  • How to Build an Army of Supporters
  • A Beginner’s Guide to Facilitation
  • The Temperament of Great Leaders
  • Units of Civic Progress
  • Leadership as “a Kind of Genius”
  • How to Read a Flawed Book About Cities
  • A Mayor’s Test for Good Decisions
  • How to Manage a Crisis Before It Happens
  • Lesson Seven: Process and Results

Categories

About Otis White

Otis White is president of Civic Strategies, Inc., a collaborative and strategic planning firm for local governments and civic organizations. He has written about cities and their leaders for more than 30 years. For more information about Otis and his work, please visit www.civic-strategies.com.

The Great Project

Otis White's multimedia book, "The Great Project," is available on Apple iTunes for reading on an iPad. The book is about how a single civic project changed a city and offers important lessons for civic leaders considering their own "great projects" . . . and for students in college planning and political science programs.

For more information about the book, please visit the iTunes Great Project page.

Follow Us on Mastodon

Mastodon

You can find Otis White’s urban issues updates by searching on the Mastodon social media site for @otiswhite@urbanists.social.