The Next Stage of Responsible Tech: From Solving Problems to Managing Polarities

By: Beth Watson, Strategy Director, Forum One

Over the past decade, the Responsible Tech movement has helped make the broader consequences of technology much harder to ignore. Conversations about privacy, algorithmic bias, misinformation, AI, democracy, and human well-being have moved from the margins into the mainstream. Along the way, the movement has pushed us to think differently about who should have a voice in decisions about technology—not just the people building it, but the people and communities living with its effects.

That represents real progress. We understand far more today about the ways technology interacts with society, and there is growing agreement that technical feasibility and commercial success alone can't be the only measures of whether a technology is serving us well.

And yet, even when we understand the problems, meaningful change can remain surprisingly difficult. We can identify harms, document their causes, make the case for broader participation, and bring the right people into the conversation, and still find ourselves wrestling with many of the same tensions. At some point, it's worth asking whether the challenge is simply that we haven't found the right solution yet, or if what we're trying to solve isn't actually a problem at all.

What if some of the hardest challenges in Responsible Tech aren’t problems, but polarities—ongoing tensions that can't be solved because we need both sides?

Problems Can Be Solved. Polarities Have to Be Managed.

Organizational thinker Barry Johnson uses the term polarity to describe two things that appear to compete with each other, but actually depend on one another over time. Unlike a problem, a polarity doesn't have a final solution. We can't permanently choose one side and eliminate the other without eventually experiencing consequences. Think autonomy and collaboration, change and stability, or claiming and sharing power.

The difference matters. With a problem, identifying the gap helps us move toward the solution. With a polarity, what appears to be the solution is often simply the neglected side of a larger system.

A polarity we all are probably familiar with is described as Freedom to Innovate and Responsibility to Society.

On one side is the freedom of companies, entrepreneurs, researchers, and product teams to explore ideas, exercise expertise, develop business models, take risks, and create new products and services. On the other is the responsibility that comes with creating technologies that increasingly shape communities, institutions, economies, and people's lives.

Underneath that tension is also a question of power: Who gets to make consequential decisions about technology? Who gets to influence those decisions? And how much authority should rest with the technology builders versus the people impacted by the technology?

In systems terms, this is also a version of what Johnson calls a Part and Whole polarity. The Part needs enough autonomy and power to act. The Whole needs enough influence to ensure those actions remain connected to the health of the larger system.

Neither side is the answer. We need both. 

Our Natural Instinct Is to Solve the Problem

Most of us have been trained to approach complex challenges through some version of problem solving. We gather information about what's happening today, identify what's not working, imagine a better future state, and determine what needs to change to get from here to there. Whether we call it a gap analysis, strategic planning, design thinking, or something else, the underlying logic is familiar:

Current state → Gap → Desired state

It's an incredibly useful way to think. If users can't find information on a website, we can redesign the navigation. If a process has unnecessary steps, we can remove them. If people need a capability that doesn't exist, we can build it. We identify the problem, understand what's missing, and develop a solution.

Much of Responsible Tech can be understood through this same logic. We see consequential technology decisions being made without enough consideration of their effects on people and society. We see people affected by technologies without meaningful influence over the decisions shaping them. We see organizational and commercial incentives—growth, speed, market share, profitability—sometimes taking precedence over questions about public interest and human well-being.

Once the problem is framed that way, what's missing can seem fairly obvious. Bring more perspectives into the room. Elevate the issue to the people with decision-making authority. Give affected communities more influence. Create stronger governance. Connect technical expertise with the humanities and social sciences. Help executives and product leaders understand the societal consequences of their choices.

Underneath many of these efforts is a reasonable assumption: if the people making technology decisions better understand the problem and hear from the people affected by those decisions, they'll make different choices. Except it doesn't always work that way.

When Closing the Gap Doesn't Create Change

Anyone who has tried to change how an organization makes decisions knows that identifying the gap is often easier than closing it. The people being asked to change aren't necessarily missing information or unconcerned about the consequences. They're often responding to another set of pressures that are just as real.

They have products to ship, competitors to respond to, revenue targets to meet, funds to raise, regulatory requirements to comply with, investors or boards to satisfy, and technologies evolving faster than their organizations can absorb them. They need people with expertise to exercise judgment. They need clear decision-making rights. They need to experiment, learn, and sometimes act before they have every perspective or every piece of information they'd ideally like.

From that vantage point, many of the things proposed as solutions can also look like risks. More stakeholder involvement can mean slower decisions. More governance can mean more process. Broader ownership can make accountability less clear. More deliberation can make experimentation harder.

A familiar pattern starts to emerge. One group sees the consequences of moving too quickly and says, We need more oversight, more participation, and more deliberation. Another sees how hard it already is to get anything done and says, We need clearer ownership, more autonomy, and faster decisions.

Both may be right.

Yet our natural problem-solving instinct often pushes each group to make a stronger case for its preferred solution. Advocates for greater inclusion might think, If leaders understood the societal consequences more clearly, perhaps they'd prioritize them. Product managers might think, If advocates understood the realities of building and shipping technology, perhaps they'd demand less process.

But there may be something more fundamental underneath this disagreement. The things each group is trying to protect are genuinely valuable—and genuinely in tension. Technology companies need freedom to experiment, exercise expertise, take risks, and bring new products into the world. At the same time, the greater technology's impact becomes, the greater its responsibility to the people and systems affected by it.

When both sides understand the problem and the proposed solution still isn't producing movement, it may be time to zoom out. What looks like a gap may actually be part of a larger polarity.

What Happens When We See the Whole Map?

A polarity map (below) helps us see the full picture:

For decades the technology sector has invested heavily in the Freedom to Innovate side. And for good reason. Autonomy, expertise, entrepreneurship, clear ownership, experimentation, and commercial incentives have helped create extraordinary new products and capabilities at remarkable speed.

But overemphasize that side and its downsides become more visible. Power becomes concentrated among relatively few companies and decision makers. Commercial incentives can outweigh broader societal ones. People affected by technology may have little influence over it. A product or company can succeed on its own terms while creating costs elsewhere in the system.

Those are many of the concerns the Responsible Tech movement has helped make visible. And once we see them, the natural response is to strengthen the other side of the polarity: Responsibility to Society.

That can mean broader participation, stronger governance, more interdisciplinary perspectives, greater accountability, and giving communities more influence over technologies that affect them. At its best, this distributes power more broadly and reconnects technology decisions to the larger systems in which they operate.

But here's what a polarity map allows us to see that a traditional gap analysis doesn't: we have to keep going.

If we continue pushing toward shared responsibility without protecting the freedom on the other side, those strengths can eventually produce their own downsides. Consultation can become endless. Accountability can become diffuse. Governance can become bureaucracy. Consensus can become an expectation even when consensus isn't possible. Companies and product teams can lose the autonomy they need to experiment, exercise expertise, and make decisions.

Eventually, someone says, “We just need to let people build.”

And the system begins pulling back toward freedom, autonomy, expertise, and concentrated decision-making. Push far enough in that direction, and eventually the original problems return.

That's the loop that the polarity map helps us visualize.

When we're living in the downsides of one side, the benefits of the other can look like the solution. That's what creates the whiplash. We move toward the neglected pole, enjoy its benefits, eventually experience its downsides, and rediscover the value of what we left behind.

Polarity management asks a different question: How can we strengthen what's missing without losing what is valuable about where we are?

The Goal Isn't a Perfect Balance

Seeing the full map doesn't mean the answer is to split power neatly down the middle. Different situations require different amounts of freedom and responsibility.

The question is less “Which side should have the power?” and more “What does this situation require, and how do we protect the benefits of the other side while we do it?”

When the downsides of freedom and autonomy begin to appear, the answer isn't to eliminate autonomy. It's to strengthen responsibility while protecting expertise, ownership, experimentation, and the ability to act. When the downsides of collective responsibility begin to appear, the answer isn't to abandon participation. It's to clarify decision rights and streamline processes while protecting representation, accountability, and systemic understanding.

This is how organizations can begin to avoid the whiplash that sends them repeatedly from one extreme to the other. Instead of waiting until the downsides become so painful that they provoke a backlash, leaders can learn to recognize the warning signs earlier and strengthen the neglected side before the system reaches that point.

Managing the Polarity 

Recognizing the polarity is only part of the challenge. We also need to ask where in the system it can actually be managed.

Many Responsible Tech conversations happen at a high altitude. We ask what kind of technology society wants, how AI should serve the public interest, or what human-centered technology should look like. But the decisions that collectively shape those outcomes often happen much closer to the ground: within product teams, company strategies, investment decisions, governance structures, and organizational incentives.

Managing the polarity requires working at multiple altitudes. At the product level, that might mean changing who participates in research, what outcomes are measured, or how risks are considered before launch. At the organizational level, it could mean changing incentives, governance, decision rights, or definitions of success. Across an industry, shared standards and professional norms can shift expectations. And at the societal level, policy and regulation can establish boundaries when the incentives of individual organizations aren't sufficient to protect the interests of the whole.

The goal isn't to push every decision to the highest possible level. That would recreate exactly the downside we’re trying to avoid: more layers, slower decisions, and less autonomy. Instead, the challenge is to manage the polarity at the lowest level that can meaningfully address it, while creating connections to the larger system when that level alone isn't enough.

Getting Better at the Other Side of the Equation

There is another reason this matters for Responsible Tech. The technology sector has spent decades becoming extraordinarily sophisticated at the focused-action side of this polarity,the freedom to innovate, which answers the basic question: How do we help focused groups of people build things and move quickly?

That investment has worked. We're very good at it.

Responsible Tech gives us an opportunity to become equally sophisticated at the complementary question: How do we exercise responsibility to the larger system without unnecessarily sacrificing the freedom that makes innovation possible?

Fortunately, we're not starting from scratch. Participatory design, deliberative processes, collaborative decision-making, systems thinking, facilitation, co-creation, and governance models all offer ways of doing this work well. There are methods for gathering broad input without requiring consensus. There are ways to distinguish who should contribute, who should recommend, and who should decide. There are facilitation approaches designed not simply to generate ideas, but to help groups converge and move forward.

The challenge may be less about inventing these practices than making them more widely understood and building the same fluency around them that the technology sector has built around innovation.

"Include more people" isn't enough. We need to get better at knowing who to involve, when to involve them, what decisions they should influence, how their input gets used, when consensus matters, when it doesn't, and who ultimately decides.

The next stage of Responsible Tech, then, isn't simply more collaboration. It's better collaboration. It isn't simply more voices, but better ways of incorporating those voices into decisions. It isn't less autonomy, but autonomy that stays connected to the whole. And it isn't slower innovation, but innovation that can continue to move while remaining responsive to the systems it changes.

Seeing the Loop Before the Snapback

Responsible Tech has helped make the consequences of technological freedom without enough responsibility to the larger society much harder to ignore. Its push toward representation, interdisciplinary thinking, public participation, governance, and public interest is an important corrective—and in many places, that corrective still has a long way to go.

Polarity thinking doesn't challenge that work. It asks us to zoom out far enough to see what happens next.

If we can see the larger loop, we don't have to wait until today's solution becomes tomorrow's problem. We can strengthen responsibility without unnecessarily sacrificing freedom. We can share power without eliminating clear authority. And we can give the Whole greater influence without stripping the Parts of the autonomy they need to act.  

That may be one of the most important capabilities for the next stage of Responsible Tech: recognizing these cycles before they become whiplash, and becoming more deliberate about when power should be claimed, when it should be shared, and at what level those decisions need to happen.

The goal isn't to choose between freedom and responsibility. It is to build a technology ecosystem capable of both.