Dan Genduso, Inc

Start solving problems. Not just responding to them.

Every city has a system for responding to problems. Few have a system for solving them consistently, sustainably, and across issues. The same problems keep reappearing, cycle after cycle, causing residents to lose trust in the system.

We help city governments operate differently — learning from residents, systematically solving problems, and continuously improving how they serve.

See How It Works

The problem

The response is where the process ends. It should be where it begins.

City governments respond to problems every day. But responding is not solving. Without a process that continues past the response — into the underlying cause, the defined problem, the designed solution — the same issues keep reappearing, cycle after cycle, compounding as they go.

Respond. Close. Repeat.

Every problem generates a response. The sidewalk gets patched. The trash gets picked up. The ticket closes. But the underlying condition that keeps generating those problems goes unexamined. The response provides relief — like taking Tylenol every day. Necessary in the moment. But not a path to sustained health. Over time the volume of responses grows, the cost compounds, and the city runs faster and faster just to stay in the same place.

Underlying causes compound. Costs grow.

What starts as a manageable issue becomes a massive, entrenched one. Homelessness is a clear example — the symptom gets more expensive to manage every cycle while the underlying causes push more people onto the street. The city spends more and more treating the surface while the conditions generating the problem grow.

Occasional progress. No repeatable system.

Problems do get solved — but slowly, singularly, and in ways that can't be replicated. It happens despite the system, not because of it. There is no structured process that moves consistently from symptom to cause to resolution. Just occasional progress surrounded by persistent problems.

Everything feels urgent. Nothing feels solvable.

Without a system for working through problems, prioritization becomes impossible. Every issue competes for attention. Resources get spread across symptoms. Nothing gets the sustained, structured effort required to actually resolve it. The backlog grows. The team burns out. And residents stop believing anything will change.

This is not a failure of effort or intention. It is an absence of system. And every cycle that passes without resolution makes the next one harder.

Why it happens

Built to respond. Not to solve.

This is not about effort, intention, or the quality of the people doing the work. Government was designed and optimized for responding — intake, dispatch, close ticket. That system has workflows, metrics, and accountability structures all built around response times, tickets closed, cases resolved.

There is no equivalent system upstream. No process for moving from symptom to cause to clearly defined problem to lasting resolution. Information exists everywhere — in 311 calls, service tickets, case notes — but it never flows through the organization as learning. It gets captured and stored. Never used to understand what is actually happening and why.

This is not a resource problem. It is not a people problem. It is a system design problem.

The consequence

Every cycle that passes without resolution creates two compounding crises.

A budget deficit that cuts can't fix.

Servicing symptoms is expensive. As underlying causes grow, the cost of managing them at the surface grows with them. Cutting budgets doesn't solve this — it just means doing less of the same ineffective work. The responsibility doesn't shrink with the budget.

A trust deficit that communication can't reverse.

Decades of the same problems reappearing have taught residents one thing: the system cannot solve problems. Not won't. Can't. Every cycle that passes without resolution deepens that belief. And once formed, it is very hard to reverse — not through messaging, not through community meetings, only through visible, felt progress.

A city that cannot afford to keep operating the way it does — serving residents who no longer believe it can change. That is what makes this existential.

The approach

A system built for solving.

Solving problems consistently requires a system. We help city governments implement one — a structured process that moves from resident experience all the way through to lasting resolution, and gets better at doing that over time.

Each phase produces the input the next phase needs. Shortcutting the sequence is how you end up with well-executed solutions to the wrong problems — which is where most organizations already are.

Discover

Understand the problem as residents experience it. Not themes from a survey — deep understanding of what keeps happening and what it means for the people living it.

Diagnose

Identify the underlying causes. What conditions are generating this problem? Which of them, if addressed, would prevent it from reappearing?

Define

Get precise. Vague diagnoses produce vague solutions. This phase turns a diagnosed cause into a clearly defined problem with a clear picture of what resolution looks like.

Design

Build the treatment plan. What interventions address each defined problem — individually and collectively? In what sequence? With what dependencies?

Deliver

Implement, monitor, and confirm the experience actually changed. Not 'did we ship it' — but 'did the problem stop appearing?' Band-aid work continues in parallel so residents don't wait while the deeper work happens.

What it involves

A new way of operating.

This is not a report delivered and forgotten. It is a change in how the organization operates — how it learns from residents, moves that learning through the organization, and uses it to solve problems and improve services over time.

Systemic problems do not respect departmental boundaries. Neither can the solutions. This requires cross-functional coordination, piloted approaches, feedback loops, and a willingness to test before committing resources at scale.

Over time the organization gets better at this — faster diagnosis, higher accuracy, the ability to tackle harder problems. The metrics shift too: from response times and tickets closed, to problems resolved, time to resolution, recurrence rate, and resident trust.

Change happens across four dimensions

People

The humans and AI agents doing the work — trained to learn from residents, capture signal, and move it forward rather than close tickets and move on.

Process

A structured problem-solving process that runs consistently — from resident experience through to lasting resolution — and improves with every cycle.

Policy

The rules and principles that guide decisions — updated to support learning, continuous improvement, and cross-functional coordination.

Product

The internal and external systems that capture learning, support diagnosis, and deliver services that reflect what residents actually need.

The outcome

Problems start going away.

For the first time, residents experience something different — not a faster response to the same recurring problem, but the problem actually stopping. That shift is felt before it is measured. And once residents feel it, trust begins to move.

Residents see problems actually getting solved — not faster responses, but the things that kept happening to them stopping.
Repeat service demand declines as underlying causes get resolved — the expensive cycle of symptom management begins to wind down.
Budget pressure eases — not through cuts, but through retiring the work that kept being required because nothing was being solved.
Trust begins to rebuild — not through communication strategies, but through visible, felt progress in the resident experience.
The capability compounds — every problem solved makes the next one faster, every diagnosis sharpens the next.

The organization shifts from measuring activity to measuring progress. And the system keeps improving — because that is what it was built to do.