Chapter 4 — Different Summaries

What happens when people discover they were not describing the same project?

The first public meeting after the fence conversation was held at city hall.

Priya preferred the school cafeteria. The cafeteria had become familiar by then: folding chairs, coffee urns, whiteboards, parents arriving after work, teachers sliding in late with apology on their faces. City hall felt different. The room had rows instead of circles. Microphones stood at the front. A projector screen hung above a long table where David, Grace, Priya, and the city planner sat with name cards in front of them.

The arrangement changed the air.

People did not drift into conversation as easily. They entered, signed in, took printed agendas, and chose seats. A few neighbors came early and filled the middle rows. Teachers sat together near the aisle. Parents checked their phones. Several teenagers stood along the back wall until Priya noticed them and waved them toward a row of empty chairs.

Jade Calloway came in last.

She wore a green hoodie and kept one hand on the strap of her backpack. Two friends followed her. They did not sit immediately. They looked at the screen, then at the table, then at the adults already arranged beneath the city seal. Priya caught Jade's eye and smiled. Jade nodded once, not quite returning it.

At the front of the room, David unrolled the site plan.

The rendering looked beautiful.

The community center sat slightly back from the street, framed by young trees and a wide paved approach. Large windows faced the sidewalk. A covered entry opened into a lobby. From there, the plan branched toward classrooms, offices, a flexible room, storage, bathrooms, and a small courtyard. The old fence was gone. In its place, the design showed a cleaner perimeter: low landscaping along the street, a controlled service gate on one side, and a defined entrance where the sidewalk met the building.

David had refined the design for weeks. He had listened, adjusted, softened the roofline, added more glass, widened the lobby, and moved the flexible room closer to the courtyard. He had preserved enough structure to keep the building coherent and enough openness to show he had heard the community.

He believed the plan was ready to meet the room.

Grace believed the plan was barely ready to survive it.

She sat with a folder of cost estimates and operating assumptions. Each revision had added something: more lighting, more durable finishes, additional storage, public art coordination, extended hours, exterior cleanup, new accessibility improvements, a stronger perimeter. None of these additions were irresponsible on their own. Together, they had started to change the project from a building into a promise.

Priya looked out at the room and tried to read its mood.

The project had reached the stage she had both hoped for and feared. People had stayed involved long enough to care. That meant they could now be disappointed by specifics.

The city planner introduced the evening. Grace gave a brief overview of the process. Then David stood.

"Tonight," he said, "we want to show how the design has developed from the conversations we've been having."

He clicked to the first slide.

The room leaned forward.

The Plan Meets the Lot

David began with the approach.

He explained the street-side entrance, the line of sight from the sidewalk, the lighting strategy, the lobby, the way parents could enter safely with children, the way staff could see arrivals without creating a checkpoint atmosphere. He spoke with care. He did not sound defensive. He sounded like someone trying to show the reasoning behind a choice.

"This entrance gives the building a clear public face," he said. "It helps visitors understand where to go. It also lets us create a safer transition from outside to inside."

A parent raised her hand. "Will there be a drop-off area?"

David nodded. "Yes. We have a short-term curb zone here."

He pointed to the map.

A teacher asked whether students could enter from the school side after dismissal. David explained the path along the sidewalk and the crosswalk improvements under review. Grace added that traffic changes required a separate city approval process. Priya wrote school access in her notes.

The conversation remained orderly.

Then Jade raised her hand.

Priya saw it before David did. The motion was small, almost reluctant, but once Jade's hand was up, she held it there.

David paused. "Yes?"

Jade stood halfway, then seemed to decide sitting would make her voice disappear. She stood fully.

"That's not where people go in."

The room turned.

David looked at the screen, then back at her. "You mean currently?"

"I mean, yes. Currently. But also just... that's not where people go in."

David waited.

Jade pointed toward the projected site plan. "People go in back there."

She did not have a laser pointer. She walked toward the front, stopped before the first row, and gestured toward the rear edge of the lot, where the drawing showed landscaping and a service boundary.

"The hole is over here," she said.

The city planner adjusted his glasses. "The current fence opening?"

Jade glanced at him. "The entrance."

The word changed the room.

Not loudly. No one gasped. No one laughed. But something in the meeting tightened. The rendering on the screen still looked finished. The path still looked clean. The entrance still made sense. Yet Jade had named another reality, one not drawn on the plan.

David said, carefully, "That area isn't designed as a public entrance. It creates visibility and supervision concerns. It also brings people toward the service side of the building."

"Because that's where people already come from," Jade said.

A neighbor in the second row shifted. Someone whispered. Priya looked at the site map and saw, suddenly, what the map did not show: the worn path along the fence, the bent wire, the route from the apartments behind the lot, the way use had already drawn a line the design had erased.

Grace saw something else.

If the rear edge became an entrance, everything changed. Lighting. Staffing. Sightlines. Access control. Insurance. Snow removal. Trash pickup. Maintenance. The building would need to support two public faces instead of one. The budget would not absorb that as a small adjustment.

David saw fragmentation.

A building can have more than one entrance, but entrances are not neutral. They organize movement. They express hierarchy. They determine where attention goes. Add an entrance in the wrong place, and a building can lose coherence before it opens.

Priya saw the coalition.

The room had gone quiet in a way she recognized. Not silence exactly. Calculation. People were deciding whether this was a helpful comment, a challenge, a complaint, or the beginning of something harder.

She almost spoke.

She almost said, I think what everyone is saying is that access matters.

The sentence formed so naturally she felt its shape before she stopped herself.

Not yet.

Several Projects at Once

David returned to the slide and tried to explain.

"The plan is not ignoring how people currently move," he said. "But part of the project is making the site safer and more legible. Informal paths are often signs that a site lacks design. We have the opportunity to create something better."

Jade heard something better as something replacing what already worked.

Grace heard safer and more legible as words that would matter in a public meeting, a council presentation, and any future incident review.

Priya heard the phrase informal paths and wondered whether Jade had heard it as a compliment or a dismissal.

A father near the front raised his hand. "I understand what she's saying. My son cuts through the back too. If the entrance is only on the street, kids are going to keep cutting around."

A neighbor behind him shook her head. "But that's exactly the problem. People shouldn't be cutting through wherever they want. If it's a community center, it needs to feel cared for."

"It can be cared for and still match how people use it," the father said.

The neighbor looked toward the plan. "But if there are entrances everywhere, how do we know who's there?"

Grace leaned toward the microphone.

"These are exactly the kinds of questions we need to separate," she said. "There is access, there is safety, there is cost, and there is operational responsibility. Each choice has implications."

It was the kind of sentence Grace trusted because it was true and disciplined. It made the problem sortable.

But to Jade, operational responsibility sounded like another adult phrase that could turn a real entrance into a problem to be managed.

To David, access sounded like a design challenge that had to be integrated carefully or it would weaken the building.

To Priya, separate the questions sounded useful and dangerous at the same time. Useful because the room needed clarity. Dangerous because separation could make the human part disappear into categories.

The project had been one project when the words were broad.

Now it was becoming several.

For David, the community center was a building that needed form. If the design became a collection of requests, it might satisfy every comment and fail as a place. His responsibility was not to obey the loudest room. His responsibility was to make choices that would still make sense after the excitement passed.

For Grace, the community center was a public investment that needed to survive scrutiny. A plan that could not be defended, funded, insured, maintained, or explained would not serve anyone for long. Her caution was not lack of imagination. It was loyalty to the future version of the project, the one that would still have bills after the opening ceremony.

For Priya, the community center was a coalition. It existed only if people continued to believe the process could hold them. If conflict hardened too quickly, the fragile trust she had built might collapse before the project had learned enough from it.

For Jade, the community center was supposed to become a place where people like her belonged. But the more adults talked about safety, process, and design, the more belonging sounded like something they would define after she had already lost the only entrance that proved she had ever belonged there at all.

Each summary was partial.

Each summary was protecting something real.

The Fence as Evidence

The city planner advanced to the next slide.

It showed the existing conditions: an aerial photograph of the lot, the fence line, the patched sections, the street, the school, the apartment buildings behind the property, the worn strip along the rear edge where the grass had thinned from use.

The photograph did what the rendering had not.

It made the informal path visible.

Jade saw it immediately. So did David. So did Grace. Priya watched the room look from the photograph to the plan and back again.

The worn path had no official status. It did not appear in the design brief. It had not been discussed in the first meeting. It had not appeared on Priya's whiteboard except as access. Yet there it was, a pale line in the grass, thin but unmistakable, connecting the apartments behind the lot to the opening in the fence.

For Jade, the path was evidence that use had already spoken.

For David, it was evidence that the site needed design.

For Grace, it was evidence of unmanaged risk.

For Priya, it was evidence that the process had missed someone.

The same photograph. Four different summaries.

None invented. None sufficient.

A teacher raised her hand. "Could the path become part of the design?"

David did not answer immediately.

He looked at the slide, then at the rendering. His mind began working through consequences: circulation, supervision, grading, lighting, drainage, construction cost, how a rear entrance might change the building's internal logic. He did not reject the idea. That mattered. But neither could he accept it simply because it sounded responsive.

"It might be possible," he said. "But it would require rethinking the plan."

He rubbed his thumb along the edge of his pencil without meaning to—a habit from studio reviews when a comment was right enough to cost him sleep.

The room heard that sentence in different ways.

Some heard openness.

Some heard resistance.

Grace heard expense.

Priya heard a door not fully closed.

Jade heard we will think about it, which adults often said when they meant no.

When Summary Becomes Reality

A summary is not a lie.

It is a way of making reality small enough to handle.

No person can hold every detail of a situation at once. We select. We compress. We name. We decide what belongs in the foreground and what can remain background. A budget is a summary. A design is a summary. A meeting note is a summary. A teenager's route through an empty lot is a summary too: not of numbers or drawings, but of felt permission, habit, risk, and use.¹

The trouble begins when a summary forgets that it is a summary.

David's plan compressed the project through space, sequence, durability, and form. Grace's budget compressed it through responsibility, constraint, maintenance, and public survival. Priya's notes compressed it through relationship, participation, momentum, and shared language. Jade's path compressed it through use, access, belonging, and the memory of being told where she did not belong.

Each summary made something visible.

Each summary made something disappear.

Perspective is not merely preference. It organizes attention, sorts evidence, names the failure each person is trying to prevent, and decides which details feel urgent or negotiable.

When perspectives collide, people often assume the problem is disagreement. Sometimes the deeper problem is that each person is defending a different summary of reality.²

Surge Pricing and the Same Ride

A similar pattern appears far beyond community meetings.

Consider surge pricing in ride-hailing. The same price increase can be summarized in several ways at once. To a platform, surge pricing may appear as a coordination mechanism: prices rise when demand exceeds supply so that more drivers are encouraged to enter the area and riders receive a clearer signal about scarcity. To a driver, it may look like an opportunity to earn more during peak demand, though not always with full control over the conditions that create it. To a rider standing in bad weather after a delayed flight, it may feel like being penalized for needing transportation at the wrong moment. To a city regulator, it may raise questions about fairness, transparency, emergency conditions, and public dependence on private infrastructure.³

The same ride.

Different summaries.

Market signal. Income opportunity. Exploitation. Coordination. Convenience. Vulnerability.

None of these summaries is simply fake. Each highlights a real part of the system. Each becomes misleading when treated as the whole.

The conflict is not merely about whether people like the price.

It is about which summary gets to define what the price means.

Airbnb and the Same Home

Short-term rentals create a similar conflict around homes and neighborhoods.

A host may describe a spare room or apartment as flexibility: a way to earn income, use underoccupied space, or welcome visitors. A traveler may see access: a more personal, affordable, or convenient way to stay in a city. A platform may see an efficient network connecting unused capacity with demand. A neighbor may see something else entirely: strangers moving through hallways, noise on weekends, the weakening of familiar social ties, or housing stock shifting away from long-term residents. A city may see tax questions, zoning questions, enforcement questions, and pressure on already strained housing markets.⁴

Again, the same object becomes several objects.

A home.

An asset.

A guest experience.

A neighborhood disruption.

A regulatory category.

A source of income.

A threat to belonging.

Arguments about short-term rentals often become heated because each side defends more than an opinion—financial stability, daily texture, housing policy, access, or a model of coordination at scale.

The word home does not settle the question because the word contains more than one reality. Neither does community. Neither did fence.

The Project Splits

Back at city hall, the meeting continued longer than scheduled.

The agenda said the group would review the design, gather comments, and identify next steps. That still happened, officially. Priya took notes. Grace answered questions. David marked up his printed plan. The city planner promised to post materials online. People signed up for follow-up sessions.

But the meeting had changed.

People were no longer discussing one community center. They were discussing several.

One was a civic building that needed a coherent public face. One was a public investment that had to survive budgets, liability, maintenance, and future criticism. One was a fragile coalition that had to remain together long enough to build anything at all. One was a place teenagers had already been using, now at risk of becoming official in a way that erased them.

The summaries did not merely compete because people were stubborn. They competed because each one carried evidence the others needed and fear the others could easily dismiss.

David worried that the project would become incoherent.

Grace worried that it would become indefensible.

Priya worried that it would become divided.

Jade worried that it would become theirs without ever becoming hers.

When the meeting finally ended, people did not leave angry exactly. Some stayed to look at the maps. Some thanked Priya. A few approached David with suggestions. Grace gathered the sign-in sheets and placed them in her folder, then checked the date circled on her timeline printout—the council packet deadline was three weeks away, and the design had just become harder to summarize in one paragraph. Jade stood near the back with her friends, looking at the rendering on the screen.

Priya walked over.

"I'm glad you came," she said.

Jade kept her eyes on the plan. "Are you?"

The question was not loud. It was not cruel. It was not even accusatory in the way Priya might have expected. It sounded like Jade genuinely wanted to know whether her presence had been welcome or merely useful.

"Yes," Priya said.

Jade looked at her then. "Because it didn't really seem like anybody knew we were there until we said something."

Priya had no quick summary for that.

For once, she did not try to make one.

What Perspective Reveals

Perspective is often mistaken for distortion alone. It can distort—people are biased, defensive, uninformed, or wrong. But it is also information. Someone standing elsewhere may see what remains invisible from here. That is why conflict can feel both threatening and necessary.

David's perspective revealed the limits of improvisation—structure, sequence, and durability matter.

Grace's revealed the limits of aspiration—someone must ask what can be defended, funded, maintained, and explained.

Priya's revealed the limits of expertise and administration—a community project cannot be built only by drawings and budgets.

Jade's revealed the limits of formal planning—a place is not empty because no official purpose has been assigned to it.

The conflict was painful because each perspective corrected the others. It was dangerous because each correction felt like a threat.

Core Principle

Perspective reveals blind spots.

Different summaries often describe different aspects of the same reality. They become dangerous when any one summary mistakes itself for the whole.

Back to the Site Plan

After the room emptied, David stayed at the front with the site plan spread across the table.

The rendering still looked good. The street-side entrance still made sense. The lobby still worked. The circulation was still clean. Nothing Jade had said made the design careless or foolish.

But the aerial photograph sat beside the rendering now.

On one page, the entrance was where the design said people should arrive.

On the other, the entrance was where people already did.

David looked from one to the other.

For the first time, the worn path did not look like a problem outside the design.

It looked like information the design had not yet learned how to read.

Footnotes

1. Steffensen, How Meaning Moves (after-certainty.com, 2026) — on summaries as compressed meaning traveling through groups. ↩

2. Freeman, Strategic Management — on stakeholders interpreting the same project through different claims. ↩

3. Rosenblat, Uberland — on surge pricing experienced differently by platforms, drivers, riders, and regulators. ↩

4. Wachsmuth and Weisler, "Airbnb and the Rent Gap" — on short-term rentals and competing neighborhood interpretations. ↩