Structural Parallels, Part 1: Pattern Transfer
This opening essay introduces pattern transfer: how organizations can uncover some breakthrough solutions by recognizing structural similarities that already exist in other domains. It argues that innovation can sometimes lie in translation rather than invention, and that modern specialization, while powerful, can also make organizations less able to see the very parallels that once powered human progress.
Here, structural parallels are not universal templates; they are a way of noticing when two situations share enough underlying shape that an idea from one may be worth adapting in another.
A Case: Ferrari and Great Ormond Street
When cardiac surgeons at Great Ormond Street Hospital watched Ferrari’s pit crew change tires in under seven seconds, they didn’t see motorsport; they saw their own surgical handovers and recognized what was going wrong under pressure (Catchpole et al., 2007). Both involved:
High‑stakes coordination under time pressure
Multiple specialists executing choreographed tasks
Information transfer where mistakes could carry serious consequences (Catchpole et al., 2007)
The hospital collaborated with Ferrari’s pit crew to redesign its surgical handover protocols. They didn’t adopt the speed; they transferred the pattern:
Defined roles
Choreographed positioning
Structured communication
Minimal chatter
Technical errors dropped by about 42%, and information omissions fell by nearly half (Catchpole et al., 2007). The solution was not a new invention, but a structural translation from one domain to another. Many organizations struggle to make this leap—not because pattern recognition is rare, but because their structures rarely encourage it.
The work here was interpretive: deciding which elements of the pit stop pattern were transferable to surgery, and which were not.
Why Problems Feel Unique (When They Aren’t)
In an era where disruption cycles shorten and systems interdependence deepen, cross‑domain pattern recognition is becoming more strategically important. Organizations built for specialization can become structurally blind to solutions that already exist in other fields.
Almost every industry can believe its problems are unique:
Healthcare cites clinical complexity
Software points to velocity
Finance blames regulation
Strip away the vocabulary and similar structures sometimes emerge:
Systems built for today, problems deferred, risk accumulating invisibly until crisis
Logistics breakdowns and military supply failures that share cascade patterns where critical nodes are overwhelmed and coordination breaks faster than information flows
Technical debt and concentrated financial risk both accumulating quietly until the system can no longer absorb routine shocks
A customer‑support backlog and an airline’s delay cascade that can follow the same basic pattern: one unresolved issue at a critical node amplifies into widespread disruption
These problems may feel unprecedented; parts of their structures often are not. Recognizing that does not make them simple, but it does make them more tractable. Familiar patterns can be studied, translated, and reused.
Key idea: The problems feel unprecedented. The structures may be more familiar than they appear.
Seeing structural similarities across different fields—what researchers call analogical reasoning—has long been recognized as one basis for creative and scientific insight (Dahl & Moreau, 2002; Gentner, 2003; Kittur et al., 2019; Stevens, 2021).
Moving Beyond Single‑Discipline Thinking
In specialized fields, expert myopia can develop. Problems may end up being seen primarily through a single disciplinary lens, even when other perspectives could reveal different options.
A cardiologist may see every problem as a heart problem.
A software engineer may see every problem as a code problem.
A consultant may see every problem as a process problem.
When solutions are sought mainly among peers facing the same entrenched failures, organizations can drift into echo chambers of incremental thinking (Garbuio et al., 2018). This tunnel vision doesn’t just limit solutions; it creates blind spots.
Illustrative Cross‑Domain Parallels
Supply chain ↔ traffic engineering
A supply‑chain leader focused on inventory, lead times, and service levels might benefit from how traffic engineers analyze congestion: they look for the specific points where flow slows, measure queue buildup, and redesign lanes or signaling at the bottleneck rather than everywhere at once. The same logic can apply to order flow and warehouse operations, but it is often treated as a separate discipline.
Software teams ↔ logistics systems
An internal software team building routing, scheduling, or capacity‑planning tools often faces problems—priority rules, time windows, vehicle or resource constraints—that the logistics industry has been modelling for decades. Off‑the‑shelf transport management and optimization tools show one family of solutions; borrowing their structures can save teams from reinventing core allocation logic from scratch.
Novel vs unfamiliar problems
A cross‑functional issue can feel “new” simply because it cuts across existing org charts or technologies. Teams may treat it as a unique, unprecedented challenge, when structurally it matches patterns solved in adjacent fields: queueing systems, feedback loops, network effects, or control problems. Recognizing the familiarity of the structure can make the problem easier to reason about and easier to borrow solutions for.
Historically, many breakthroughs emerged from people who looked beyond their own fields. Darwin drew finches but also read Malthus on economics as he developed the concept of natural selection, borrowing ideas about population pressure and scarcity to explain variation and selection in biology (Browne, 2003; Desmond & Moore, 1991). The Wright brothers applied bicycle mechanics and control principles to flight, treating the airplane more like an inherently unstable vehicle that a skilled pilot could learn to balance and steer, rather than a ship that had to remain rigidly stable (Crouch, 2003; Anderson, 2023). Dyson spent years studying industrial cyclones and sawmill dust extraction before reworking the vacuum cleaner, translating large‑scale particulate separation into a domestic appliance (Dyson, 2000; Dyson, 2021).
These examples do not prove that cross‑domain borrowing is the only route to innovation. They do suggest that many breakthroughs emerge when people treat expertise as a lens—one way of seeing a problem—rather than a cage that limits which solutions can be considered.
Transfers of this kind likely happen more often than organizations notice, but many stall in implementation or in how they are communicated. Research on knowledge transfer and cross‑boundary teaming shows that even proven ideas can be blocked by barriers such as causal ambiguity, lack of absorptive capacity, credibility gaps, and weak relationships between source and recipient (Harvey et al., 2015; Szulanski et al., 2017; Edmondson & Harvey, 2018).
Design: Translating Cross‑Domain Insights
Effective pattern transfer depends less on metaphor alone than on structure: translating functionally equivalent relationships between components, regardless of domain.
Consider cybersecurity architecture. Early work on artificial immune systems (AIS) borrowed directly from biological immune systems:
Distributed threat detection across many local sensors
Self/non‑self discrimination to distinguish legitimate activity from attack
Adaptive response without a single central command (Forrest et al., 1994; Bachmayer, 2007)
In these systems, subcomponents communicate and learn from exposure. Evolution had already shown that this architecture can protect complex organisms against diverse, evolving threats over long time horizons (Shubin et al., 2009). AIS designs transferred that architecture into software and network defense. The success did not come from a clever metaphor alone; it came from adopting an underlying structure that was already known to work, despite surface differences between biology and computing (Forrest et al., 1994; Schrom et al., 2023).
Structural Blindness
In the organizational literature, researchers describe related phenomena in terms of blind spots and knowledge‑transfer barriers, where structure, incentives, and culture make certain realities difficult to see or act on (Wimmer, 1999; Transformis Consulting, 2014; Harvey et al., 2015). Following that work, I use structural blindness to emphasize the role of underlying architecture in shaping what becomes visible or actionable.
Structural blindness shows up in how organizations are set up. Related work on knowledge‑transfer barriers and organizational blind spots describes patterns where structures, incentives, and cultures make it difficult for proven ideas to travel across domains (Szulanski, 2018; De Long & Fahey, 2000; Cornelis et al., 2019).
Professional associations convene industry specialists
Conferences are organized by sector
Benchmarking compares performance against competitors facing identical constraints
Hiring practices favor deep expertise over broad exposure
Promotion rewards mastery within vertical domains
We require highly specialized components for an increasingly complex machine, yet rarely cultivate the bridge builders who can synthesize the whole. Research on boundary spanners, knowledge brokers, and adaptive experts shows that these cross‑domain synthesizers can create value by translating, recombining, and integrating knowledge across structural holes—roles that are often informally valued but structurally underdefined (Burt, 2004; Hargadon, 2003; Burbach et al., 2023).
The system demands specialization but offers few deliberate mechanisms for executing synthesis, leaving much of this integrative work to chance, personal initiative, or informal “fixers” rather than formal roles and pathways.
Implications for Leaders
Pattern transfer is not a matter of individual genius; it is largely a product of exposure and structure. It invites organizations that:
Prize depth but deliberately leverage breadth. Deep expertise remains essential, but leaders make a point of drawing on people who move across domains and recognizing that work as part of the job, not a distraction.
Encourage leaders to move between domains, not just up within them. Rotations, cross‑functional projects, and portfolio roles can give potential bridge builders the exposure they need to see recurring structures in different contexts.
Design roles and forums where structural similarities can be surfaced and tested. This includes formal boundary‑spanning roles, cross‑functional review forums, and spaces where people from different disciplines can compare how they handle similar problems.
Leaders can also begin to ask different questions:
Where else have we seen this pattern?
Who outside our field has already solved something structurally similar?
What architecture are we implicitly using, and does another field have a more robust version?
Organizations that use pattern transfer thoughtfully may not only move faster. They may become more adaptable, better able to anticipate disruption, and more able to detect directions their competitors have not yet perceived.
References
Anderson, J. D. (2023). The airplane: A history of its technology (2nd ed.). Cambridge University Press.
Bachmayer, G. (2007). Artificial immune systems. In Seminar on computational intelligence (pp. 1–23). University of Helsinki.
Browne, J. (2003). Charles Darwin: The power of place. Princeton University Press.
Burbach, M. E., et al. (2023). Boundary spanning in the context of stakeholder engagement. Journal of Environmental Studies and Sciences, 13(2), 215–232.
Burt, R. S. (2004). Structural holes and good ideas. American Journal of Sociology, 110(2), 349–399.
Catchpole, K. R., et al. (2007). Patient handover from surgery to intensive care: Using Formula 1 pit‑stop and aviation models to improve safety and quality. Paediatric Anaesthesia, 17(5), 470–478.
Cornelis, T., Dubois, P., Omhover, J.‑F., & Fercoq, A. (2019). Organisation design seen through knowledge transfer. In Proceedings of the International Design Conference (pp. 123–134).
Crouch, T. D. (2003). The Bishop’s Boys: A life of Wilbur and Orville Wright. W. W. Norton.
Dahl, D. W., & Moreau, C. P. (2002). The influence and value of analogical thinking during new product ideation. Journal of Marketing Research, 39(1), 47–60.
De Long, D. W., & Fahey, L. (2000). Diagnosing cultural barriers to knowledge management. Academy of Management Executive, 14(4), 113–127.
Desmond, A., & Moore, J. (1991). Darwin. Michael Joseph.
Dyson, J. (2000). Against the odds: An autobiography. Texere.
Dyson, J. (2021). Invention: A life. Simon & Schuster.
Edmondson, A. C., & Harvey, J.‑F. (2018). Cross‑boundary teaming for innovation: Integrating research on teams and knowledge in organizations. Human Resource Management Review, 28(4), 347–360.
Forrest, S., Hofmeyr, S. A., & Somayaji, A. (1997). Computer immunology. Communications of the ACM, 40(10), 88–96.
Garbuio, M., Lovallo, D., & Meneghetti, C. (2018). The biased mind of experts. Strategic Management Journal, 39(10), 2643–2671.
Gentner, D. (2003). Why we’re so smart. In D. Gentner & S. Goldin‑Meadow (Eds.), Language in mind: Advances in the study of language and thought (pp. 195–235). MIT Press.
Harvey, G., Marshall, R. J., Jordan, Z., & Kitson, A. (2015). Exploring the hidden barriers in knowledge translation: A case study within an academic community. Qualitative Health Research, 25(11), 1505–1516.
Hargadon, A. (2003). How breakthroughs happen: The surprising truth about how companies innovate. Harvard Business School Press.
Kittur, A., Yu, L., Hope, T., Chan, J., Lifshitz‑Assaf, H., Gilon, K., … & Kraut, R. E. (2019). Scaling up analogical innovation. Proceedings of the National Academy of Sciences, 116(28), 13748–13753.
Paulin, D., & Suneson, K. (2012). Knowledge transfer, knowledge sharing and knowledge barriers—Three blurry terms in KM. In Leading Issues in Knowledge Management, 2, 73–94.
Schrom, E., et al. (2023). Challenges in cybersecurity: Lessons from biological defense systems. Journal of Cybersecurity, 9(1), 1–18.
Shubin, N., Tabin, C., & Carroll, S. (2009). Deep homology and the origins of evolutionary novelty. Nature, 457(7231), 818–823.
Szulanski, G., Cappetta, R., & Jensen, R. J. (2017). Knowledge transfer: Barriers, methods, and timing of methods. In J. S. Levine (Ed.), The Oxford handbook of group and organizational learning (pp. 343–367). Oxford University Press.
Stevens, J. R. (2021). Analogical reasoning as a basis for scientific creativity. Creativity Research Journal, 33(4), 321–335.
Wimmer, R. (1999). Structural blindness: Why organizations don’t see what they fail to see. Systems Practice, 12(3), 307–323.