Before Milwaukee Called It Organizational Development, It Was Already Redesigning Work

A working history of organizational development in Milwaukee, Wisconsin

Milwaukee did not invent organizational development.

There is no local plaque marking the day OD arrived, no single Milwaukee practitioner who can claim to have brought the field to town, and no tidy line connecting one company, university, or consulting firm to everything that followed.

That is probably the wrong way to look for the history anyway.

Long before people used the term organizational development, Milwaukee was wrestling with the questions at the center of the field:

  • How should work be organized?

  • Who gets a voice in decisions?

  • What happens when growth outpaces the systems built to support it?

  • How do leaders improve performance without ignoring the people doing the work?

  • And what does an organization do when the old way stops working?

Milwaukee's OD history is not a clean chronology of models and methods. It is a story of factories, unions, training directors, civic coalitions, civil-rights organizers, quality circles, economic disruption, and repeated attempts to redesign systems under pressure.

In other words: the patterns were already there.

Before OD had a name, Milwaukee had an organizational problem

The formal field of organization development emerged in the United States in the years after World War II. Its roots are usually traced to behavioral science, Kurt Lewin's work in group dynamics and action research, laboratory training, survey feedback, and efforts to make planned change more participative. The Organization Development Network still defines OD around improving organizational effectiveness and health through planned, behavioral-science-based work.

Milwaukee's prehistory of OD began much earlier… not with consultants, but with industrialization.

By the late nineteenth century, the city had become a major manufacturing center. Its base of skilled craft shops, immigrant labor, transportation access, and metalworking expertise helped large manufacturers take root. Allis-Chalmers, A.O. Smith, Falk, Harnischfeger, Allen-Bradley, Cutler-Hammer, and others made Milwaukee known as the “Machine Shop of the World.” The Wisconsin Historical Society notes that Milwaukee's small craft shops became the foundation for the large manufacturers that later dominated the region.

Scale created wealth. It also created friction.

As work moved from small shops into large industrial systems, decisions became more centralized, jobs more specialized, and the relationship between management and labor more consequential. Milwaukee's first unions formed among bricklayers in 1847 and carpenters in 1848. By the 1880s, workers were organizing around the eight-hour day. The conflict culminated in the Bay View Massacre of 1886, when state militia fired on demonstrators and killed five people, according to the Wisconsin Historical Society's account of the early labor movement.

It would be anachronistic to call this organizational development. But it would be equally misleading to leave it out.

OD is concerned with how power, structure, participation, and working conditions shape behavior. Milwaukee's industrial conflicts made those dynamics impossible to treat as abstractions. Workers were not “resistant to change.” They were responding to systems that determined their hours, safety, autonomy, and livelihood.

That distinction still matters.

The local infrastructure for workplace change began forming early

In 1901, 23 Milwaukee business leaders formed what is now MRA–The Management Association. The organization says it was created during rapid industrial growth and workforce change so employers could take a shared approach to workplace challenges. Over time, its work expanded from labor relations and workplace dynamics into HR, training, organizational development, talent, and data-informed decision-making. In 2026, MRA marked 125 years since its Milwaukee founding.

Then, in 1944 (before OD was widely established as a distinct profession) a group of training directors in Milwaukee and Madison formed one of the earliest local chapters of what became the Association for Talent Development. SEWI-ATD's history traces the southeastern Wisconsin chapter to that group.

These organizations were not interchangeable with OD. Employer relations, training, HR, and organization development have different aims and traditions. Still, they created an important local infrastructure: people comparing practices across companies, building management capability, studying workplace problems, and treating organizational performance as something that could be deliberately improved.

The vocabulary would change. The impulse was already familiar.

After World War II, the unit of change grew larger

The national field of OD took shape in the 1940s, 1950s, and 1960s. Practitioners began using action research, T-groups, survey feedback, team development, and participative approaches to change. The underlying shift was significant: an organization was not simply a machine to optimize. It was a human system capable of learning and capable of defending the status quo.

Milwaukee was developing its own cross-sector version of that idea.

The Greater Milwaukee Committee formed in 1948, bringing together leaders from business, labor, education, philanthropy, and the professions. Its early projects focused heavily on civic infrastructure. By the mid-1980s, it had moved toward more complex issues such as education and inner-city development. The GMC's historical timeline includes the launch of Milwaukee's Social Development Commission in 1963 and later regional efforts spanning talent, entrepreneurship, education, and economic development.

Again, civic development is not the same discipline as organization development. But the parallel is useful. Both recognize that stubborn problems rarely belong to one department, or even one organization. Progress depends on convening stakeholders who hold different pieces of the system.

Milwaukee was learning, sometimes slowly and imperfectly, that the boundary around the problem matters.

A history of workplace change also has to ask: change for whom?

A polished history of Milwaukee's organizations could easily become a parade of prominent companies and executive decisions. That would miss too much.

Black Milwaukeeans built a significant industrial working class during the Great Migration while facing discrimination in employment, housing, education, and public life. Historian Joe William Trotter Jr.'s Black Milwaukee: The Making of an Industrial Proletariat, 1915–45 documents that history; the Milwaukee Public Library includes the book in its guide to African American labor history.

During the 1960s, Milwaukee residents organized protests, boycotts, and legislative campaigns against discriminatory systems. UWM's March on Milwaukee digital collection preserves that history of collective action.

This belongs in an OD history because “the system” is never neutral. Hiring rules, promotion paths, informal networks, job classifications, neighborhood boundaries, and whose feedback counts all shape organizational life. An intervention can improve efficiency and still preserve inequity. It can invite participation while leaving the most consequential decisions untouched.

The lesson is not that civil-rights organizing was an OD program. It was not. The lesson is that no credible account of organizational change can examine process without examining power.

Harley-Davidson made employee involvement a survival strategy

If Milwaukee has a widely recognizable case of organization-wide change, it is Harley-Davidson's 1980s turnaround.

After executives bought the company back from AMF in 1981, Harley faced recession, debt, falling sales, serious quality problems, and intense Japanese competition. More than half of its motorcycles were reportedly failing inspection and requiring repairs in 1980.

In 1982, company executives and union leaders visited Honda's plant in Marysville, Ohio. What they found was not simply better technology. They saw a leaner system, stronger labor relations, close attention to operations, and employees who were involved in improving the work.

Harley adopted a combination of just-in-time inventory, statistical process control, and employee involvement. Managers and line workers redesigned production together. Employees were trained to monitor processes, identify defects, question ineffective methods, and propose solutions. By 1987, annual revenue per employee had doubled from 1981 levels, productivity had risen 50 percent, and 99 percent of motorcycles came off the line ready to ride, according to a detailed Forbes account of the turnaround.

The tools mattered. The larger change mattered more.

Quality stopped being the job of an inspector at the end of the line. It became part of how the system operated—and part of the responsibility and agency of the people closest to the work.

That is classic OD territory: redesigning structures, skills, decision-making, relationships, and norms together rather than announcing a new value and hoping behavior follows.

It is also worth resisting the tidy turnaround myth. Employee involvement did not erase future labor conflict, market pressure, or hard tradeoffs. Organizational change is not a permanent state of alignment. It creates new conditions that have to be maintained, questioned, and renegotiated.

Deindustrialization changed the problem again

From the late twentieth century forward, Milwaukee's organizations faced a different kind of pressure. Factory closures, automation, globalization, restructuring, and the decline of industrial employment disrupted not only companies but neighborhoods, career paths, unions, and the city's civic fabric.

The physical evidence is still visible: former industrial corridors, repurposed plants, brownfields, and factories operating with far fewer people than they once required. Milwaukee remains an industrial hub, but the City acknowledges that industrial employment has declined even as manufacturing continues to be economically important. Its industrial land analysis describes both that legacy and the continuing evolution of modern manufacturers' needs.

For OD, the boundary of the work expanded again.

The challenge was no longer only how to improve a production line or develop a supervisor. Organizations had to integrate acquisitions, adopt new technology, retain knowledge, redesign roles, build more inclusive workplaces, respond to community expectations, and lead people through repeated uncertainty. Hospitals, universities, nonprofits, financial institutions, public agencies, professional services firms, and technology companies joined manufacturers as settings for organizational change.

The center of gravity shifted from training people for a stable system to helping the whole system adapt.

What Milwaukee's history can teach today's leaders

Milwaukee's OD history does not offer one proprietary model. It offers something more useful: a set of recurring patterns.

Structure shapes behavior. When work repeatedly stalls, the first question should not be “What is wrong with these people?” Look at roles, incentives, authority, workload, information flow, and the conditions around the work.

The people closest to the work hold essential data. Harley's turnaround became possible when employees were treated as problem solvers, not simply as hands carrying out someone else's design.

Participation without power is theater. Milwaukee's labor and civil-rights history is a reminder to ask who can influence the decision, who bears its consequences, and whose experience is being discounted.

Organizations do not change outside their context. Economic conditions, technology, public policy, neighborhoods, labor markets, and community trust cross the imaginary line around the organization every day.

What saved the organization before may constrain it now. Milwaukee companies have repeatedly had to reconsider systems that once made them successful. The old way is often not irrational. It is simply optimized for conditions that no longer exist.

The weird stuff is data. The workaround on the factory floor. The decision that keeps moving upward. The job no one can fill. The customer complaint that points to an internal handoff. The employee joke everybody understands. These are not side notes to the organizational story. They are clues to how the system really works.

Milwaukee is still writing this history

Today's Milwaukee organizations are navigating AI, demographic change, hybrid work, labor scarcity, succession, consolidation, and new expectations from employees and customers. The technologies are different. The core questions are not.

How will work be organized? Who will shape the change? What will leaders measure? Which voices will count? And can the organization adapt without losing what made it worth preserving?

Milwaukee has been working on those questions for more than a century, even when it used different names for the work.

The history of organizational development here is not the history of a field arriving fully formed. It is the history of a city learning—through conflict, experimentation, failure, and reinvention—that performance and people cannot be separated for long.

The organization always tells on itself eventually.

The work is learning how to listen.

Previous
Previous

Why Your Company Feels Slower as It Grows

Next
Next

Before You Call It a People Problem, Look at the Whole System