top of page
< Back

Essay

From Individual Scripts to Shared Language Systems

K. Todd Houston, Ph.D.

2026-08-16

Individual communication tools can help people enter difficult moments differently, but organizational change requires a larger architecture. This essay develops the Shared Language System: a cue joined to shared meaning, a receiving response, a legitimate pathway, practice, and implementation support.

Communication training often begins with the individual. Learn to speak more clearly. Ask a better question. Set a boundary. Give feedback. Use a script. These tools can be valuable, especially when they reduce the cognitive burden of finding words under pressure. But an organization cannot become more participatory merely by distributing better sentences.


The problem is straightforward: an individual can change what is said without changing what happens next.


A nurse can learn to name a concern. A faculty member can learn to challenge an assumption. A student clinician can learn to request clarification. A manager can learn to invite dissent. Yet if the organization has no shared interpretation of those moves, no expected response, and no pathway for follow-through, the new language remains fragile. Its success depends on the skill, status, timing, and persistence of the person who uses it.


The Language Project calls the larger architecture a Shared Language System.


The difference between a script and a system

A micro-script is a brief, intentional cue or retrieval scaffold. A Shared Language System is organizational infrastructure that makes a cue interpretable and actionable across people and settings. Its proposed components are:


  • Cue — a short phrase, question, or signal that can be retrieved and used in a consequential moment.

  • Shared meaning — an agreed understanding of what the cue signals and what it does not mean.

  • Receiving response — a predictable way that colleagues, supervisors, or leaders are expected to respond.

  • Pathway — a legitimate next step for clarification, review, escalation, pause, repair, or action.

  • Practice — opportunities to rehearse the cue and response before high-pressure use.

  • Implementation support — leadership attention, monitoring, reinforcement, and revision as the system is used.


This structure reflects a central insight from organizational research: recurring patterns matter. Organizational routines can stabilize behavior while also adapting through performance (Pentland & Feldman, 2005). Voice research shows that whether people speak is influenced not only by having something to say, but by expectations about risk, efficacy, hierarchy, and response (Detert & Edmondson, 2011; Morrison, 2023). Psychological safety research likewise points to the importance of interpersonal conditions for learning behavior and risk-taking (Edmondson, 1999).


A simple example from clinical education

Consider an academic program in speech-language pathology that wants students to identify potential clinical risks sooner. The program could teach the sentence, “I want to flag a concern.” That is useful, but it leaves several questions unanswered. What counts as a concern? Is the phrase appropriate during a session, in a supervision meeting, or both? What should the supervisor do when the phrase is used? Can the student request a pause? What happens if the supervisor disagrees? Is there another route when the concern involves the supervisor?


Now imagine the program adopts a shared cue: “I need a second look.” Everyone—students, supervisors, faculty, and clinic staff—learns that the phrase means: “I have noticed information that may affect the current interpretation or plan, and I am requesting a brief review before closure.” The receiving response is standardized: “Tell me what you are seeing.” If the concern cannot be resolved in the moment, the pathway identifies who reviews it and by when. Students practice the cue in simulation. Supervisors practice receiving it without treating the request as defiance.


The language is still small. The infrastructure is not.


Why the receiving response may be the most important component

Organizations frequently focus on the speaker: be courageous, be concise, be constructive. Yet the first organizational response after a person speaks can become data for future participation. If a leader asks a genuine follow-up question, makes room for uncertainty, and explains what will happen next, the organization teaches one lesson. If the leader becomes defensive, changes the subject, or invites input but never follows up, the organization teaches another.


This suggests a reciprocal model: participation is not a single act. It is a sequence. Language enables or constrains an initial move; the organization responds; the response becomes learning; learning shapes expectations; expectations influence future participation.


Language → Participation → Organizational Response → Learning → Expectation → Future Participation


Over time, recurring sequences may become cultural patterns. This is not because language alone causes culture. Rather, language is one observable part of the larger system through which expectations are reinforced.


The danger of standardizing language

Shared language can also become controlling. A script can turn into a requirement that people package dissent in the institution’s preferred vocabulary before it will be heard. A “safe” phrase can become a euphemism that reduces urgency. A standardized cue can privilege fluent insiders and disadvantage people who communicate differently.


For that reason, a Shared Language System should not make one phrase the only legitimate route to participation. The cue is an access point, not a gatekeeping device. Organizations should preserve multiple routes for raising concerns, asking questions, requesting accommodation, dissenting, and escalating.


Design principles

A useful Shared Language System should be easy to retrieve, difficult to misinterpret, and connected to real authority. It should make the receiving behavior as explicit as the speaking behavior. It should work across status differences rather than only among peers. It should be practiced in conditions that resemble actual use. And it should be reviewed against lived experience: Who uses it? Who does not? What happens after use? What unintended burdens has it created?


Implementation-intention research supports the general value of linking anticipated situations to planned responses (Gollwitzer, 1999), but organizational use requires another layer. The “if-then” plan cannot stop with the speaker. The system also needs an “if-then” plan for the receiver: If a colleague uses this cue, then I know how to respond.


From communication skill to organizational capability

The shift from individual scripts to Shared Language Systems changes the unit of intervention. The question is no longer only, “Can this person communicate effectively?” It becomes, “Has the organization made useful participation portable?”


Portability matters. A student should not need to relearn the rules of speaking up with every supervisor. An employee should not depend entirely on whether a particular manager is unusually receptive. A clinician should not have to invent an escalation phrase in the middle of a safety concern. Shared systems reduce some of that variability by making key participation moves recognizable across contexts.


The concept remains provisional. Shared Language Systems require direct testing: whether they improve retrieval, voice quality, coordination, learning, or decision processes; whether they introduce new rigidity; and whether the effects differ across power, culture, profession, and setting.

Working proposition: Individual scripts help people enter moments. Shared Language Systems attempt to make the organization ready for what happens after they enter.

 

References

Pentland, B. T., & Feldman, M. S. (2005). Organizational routines as a unit of analysis. Industrial and Corporate Change, 14(5), 793–815. https://doi.org/10.1093/icc/dth070


Detert, J. R., & Edmondson, A. C. (2011). Implicit voice theories: Taken-for-granted rules of self-censorship at work. Academy of Management Journal, 54(3), 461–488. https://doi.org/10.5465/amj.2011.61967925


Morrison, E. W. (2023). Employee voice and silence: Taking stock a decade later. Annual Review of Organizational Psychology and Organizational Behavior, 10, 79–107. https://doi.org/10.1146/annurev-orgpsych-120920-054654


Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350–383. https://doi.org/10.2307/2666999


Gollwitzer, P. M. (1999). Implementation intentions: Strong effects of simple plans. American Psychologist, 54(7), 493–503. https://doi.org/10.1037/0003-066X.54.7.493

bottom of page