How practitioner expertise is reshaping the design of mediation systems.
The Invisible Work of Mediation
Mediation is meant to serve people, yet all too often it is guided by something that receives far less attention: the administrative systems and embedded processes surrounding it. As technology takes on an ever-increasing role in dispute resolution, the success of mediation depends on skilled neutrals and engaged parties, as well as constructive, efficient processes that foster productive dialogue and durable resolution.
As legal organizations modernize, much of the conversation has focused on technology—artificial intelligence, workflow automation, and next-generation case management platforms. Those developments matter, but they also risk obscuring more fundamental questions. Before any organization decides what technology to build, it must define what kind of experience they want that technology to support.
Systems Shape Mediation Before Mediation Begins
Scheduling, communication, document management, billing, and case administration are often treated as operational functions rather than part of the mediation process itself. In practice, they influence nearly every stage of a dispute. They shape how mediators prepare, how administrators coordinate matters, and how parties experience mediation long before substantive conversations begin. When these systems work well, they remove unnecessary administrative burden. When they do not, they compete for attention with the work mediation is intended to accomplish.
That is not simply a question of product functionality. It is an institutional question. Organizations inevitably design technology around the assumptions they hold about their work. Over time, those assumptions become embedded in workflows, administrative structures, and software, even as practice evolves. As a result, systems can reinforce organizational habits long after the conditions that produced them have changed.
Understanding those assumptions requires looking beyond technical requirements to re-evaluate the realities of everyday practice. Frontline practitioners experience the workarounds, duplicated effort, and fragmented information that rarely appear in process maps but fundamentally shape how mediation functions in practice. Their value is not that they always know the right solution. Rather, they expose institutional blind spots that organizations often stop questioning because they have become part of normal operations.
Building Platforms to Fit the People Behind the Process
Technology projects often begin with requirements gathering. Users are interviewed, workflows are mapped, and feature requests are translated into technical specifications before development begins. The process is disciplined and often effective, but it also reflects an important assumption: that understanding the work and designing the system are largely separate activities.
The American Arbitration Association® (AAA®) recently explored this challenge while designing its next-generation mediation case management platform. Rather than beginning with software specifications, it convened mediation administrators, product leaders, user experience designers, technologists, and innovation specialists before development began. The objective was not to define features, but to examine how mediation is administered, where administrative complexity accumulates, and which long-standing assumptions might deserve reconsideration.
Designed and facilitated by AAA Vice President of Innovation Bryan Corbett, the resulting Mediation Design Hackathon did not replace product scoping, management, or user research. Instead, it accelerated an earlier stage of discovery by surfacing assumptions that conventional requirements gathering often overlook and deliberately slowed the rush toward solutions.
Participants began by identifying recurring sources of friction and reframing them as "How might we..." questions before discussing technology. That sequence mattered. Organizations often improve existing workflows without asking whether the workflows themselves still reflect how the work is actually performed.
The initiative reflects a broader effort to ensure the organization's technology evolves symbiotically with mediation practice. It also highlighted a question that extends well beyond a single platform: how can legal institutions ensure they are designing systems around the realities of dispute resolution rather than around organizational structures that may no longer serve them?
Looking Beyond the Technology
Designers and technologists bring a different perspective, helping question assumptions that practitioners themselves may have stopped noticing. Together, those perspectives create opportunities to rethink systems rather than simply refine them.
As Corbett observed, "The mediation team are the experts. They know the pain points. They know what the customers and the mediators are asking for." The workshop treated that expertise not as feedback to validate design decisions, but as evidence capable of reshaping the questions asked before design began.
Designing Around the Dispute
The workshop generated nearly 200 ideas spanning scheduling, billing, document management, communication, case records, and administrative coordination. More revealing than the number of ideas, however, was their consistency. Independent groups repeatedly converged on the same underlying priorities despite approaching the problems from different perspectives.
Participants were not simply asking for better versions of existing tools. Viewed individually, their suggestions may seem like practical improvements. Viewed together, the recommendations pointed toward a broader shift in perspective. They repeatedly described systems that could absorb unnecessary administrative work before it accumulates. Scheduling should coordinate participants rather than generate additional email exchanges. Billing should exist naturally within case administration instead of functioning as a separate workflow. Information should remain connected throughout the life of a dispute rather than requiring administrators and mediators to repeatedly reconstruct context.
One discussion ended up reframing the design challenge entirely. Participants questioned why mediation and arbitration involving the same parties and the same underlying conflict are typically maintained as separate administrative records. Those distinctions exist for legitimate procedural reasons, and the workshop did not suggest otherwise. Instead, participants raised a different question: while administrative separation may be necessary, does it require a fragmented experience for the people moving through the dispute resolution process?
Institutions naturally organize technology around cases, departments, and administrative responsibilities because those structures reflect how the organization operates. Parties experience a dispute, not an organizational chart. The workshop suggested that improving mediation may depend less on eliminating necessary administrative distinctions than on designing systems that preserve continuity across them.
This insight extends beyond mediation. Organizations inevitably encode assumptions about their work into the systems they build. Those assumptions often become visible only when practitioners, designers, and technologists examine the work together from different perspectives. The workshop did not establish that one methodology is superior. It illustrated how deliberately questioning institutional assumptions can reveal opportunities that conventional product discovery might never uncover.
By the end of the session, the most valuable outcome was not a prioritized feature list. It was a shared understanding of what the platform should accomplish. As Tracey Frisch, Division Vice President of Mediation, observed, the objective is to create "fewer pain points" for administrators, mediators, and parties alike—to "get out of the way of the mediation process itself." Her observation underscores an important distinction. Efficiency matters because it creates more capacity for the work that depends on human judgment, communication, and trust.
Learning Before Building
For many organizations, modernization begins by digitizing existing processes. Paper becomes digital, workflows become automated, and information becomes easier to manage. Those advances improve efficiency, but they do not necessarily challenge the assumptions underlying the systems themselves. Existing practices can become more efficient without improving outcomes.
The workshop suggested a different starting point. Rather than asking how technology might improve existing workflows, participants examined whether those workflows reflected how mediation is experienced in practice. The objective was not to eliminate every point of friction. Mediation appropriately depends on documentation, procedural safeguards, and careful coordination. The question was which forms of administrative complexity support those goals and which simply compete with them.
The workshop also pointed toward a different role for AI than the one that often dominates discussions of legal innovation. Once participants had identified the problems they wanted to solve, AI-assisted design tools helped translate ideas into workflows and prototypes that could be evaluated and refined together. In this context, AI did not determine priorities or generate solutions. It accelerated learning by making assumptions visible earlier in the design process, while there was still time to question them.
Whether that approach consistently produces better products remains an open question. Product quality depends on many factors beyond a single workshop. What the experience does suggest, however, is that AI can support organizational learning as well as operational efficiency, particularly when it is used to examine existing systems before those systems become software.
Beyond One Platform
Although the workshop was designed to inform the AAA's future mediation platform, the questions it raised extend well beyond mediation. Courts, legal aid organizations, law firms, and dispute resolution providers are all redesigning systems while simultaneously integrating AI. Their challenge is not simply deciding which technologies to adopt. It is ensuring those technologies reflect how people actually experience legal processes rather than how institutions have historically organized them.
The workshop did not establish that one innovation methodology is superior, nor that practitioners always know the right answer. It suggested something more modest, but perhaps more important: organizations are more likely to identify meaningful opportunities for improvement when they deliberately question assumptions that have become embedded in everyday operations before those assumptions become embedded in technology.
Institutions inevitably encode their understanding of work into the systems they build. As legal organizations continue modernizing mediation and other forms of dispute resolution, the more important question may not be how quickly they adopt new technologies, but whether they are challenging the right assumptions before those technologies become the foundation of future practice.