When Domains Collide: An Activity Theory Exploration of Cross-Disciplinary Collaboration
This study employs Activity Theory to analyze a mixed-method investigation of cross-disciplinary software development, identifying specific expectations and mapping 21 resulting frictions between domain experts and software developers to provide actionable insights for improving collaboration and infrastructure design.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are building a massive, high-tech spaceship.
On one side, you have the Engineers (Software Developers). They are obsessed with the ship's structure, safety protocols, fuel efficiency, and making sure every bolt is tightened to the exact same standard. They speak a language of strict rules, blueprints, and long-term maintenance.
On the other side, you have the Scientists (Domain Experts). They are the astrophysicists and biologists who know exactly what the ship needs to do to find new planets or cure diseases. They speak a language of discovery, rapid experimentation, and "let's try this crazy idea right now."
In the old days, these two groups worked in separate rooms. The Scientists would hand a messy sketch to the Engineers, who would lock themselves in a room for months to build the ship.
But today, things have changed. They are now in the same room, working side-by-side, sharing the same tools, and even writing code together. This is called Cross-Disciplinary Software Development (CDSD).
The paper you asked about investigates what happens when these two very different worlds collide in the same room.
The Problem: "When Domains Collide"
When these two groups work together, they don't just have different skills; they have different philosophies.
- The Engineer thinks: "If we don't write a perfect manual and test every single button, the ship might crash in five years."
- The Scientist thinks: "If we don't test this idea right now, we might miss a discovery forever. I'll fix the mess later!"
Because they are working so closely, these differences don't just cause small misunderstandings; they cause friction. It's like two people trying to drive a car where one is trying to drive on the left side of the road and the other on the right. They are both trying to get to the same destination, but they are constantly bumping into each other.
The Tool: "Activity Theory" (The Detective's Map)
To understand why they are bumping into each other, the researchers used a special map called Activity Theory.
Think of this map as a way to look at a team not just as "people," but as a system made of six moving parts:
- The Goal: What are we building?
- The Tools: What software and machines are we using?
- The Rules: What are the laws of the land (e.g., "Code must be reviewed")?
- The Team: Who is involved?
- The Work Split: Who does what?
- The Community: How do we trust each other?
The researchers used this map to find exactly where the "bumps" were happening.
What They Found: The Expectation Gap
The team interviewed 24 people (12 Engineers and 12 Scientists) and then surveyed nearly 300 more. They found that both sides have a list of things they expect from the other, but these lists often don't match up.
What Engineers expect from Scientists:
- "Please write down what you want clearly." (Scientists often just say, "Make it work.")
- "Please treat the code like a library book, not a napkin you can scribble on." (Scientists often write "messy" code to test ideas fast.)
- "Please understand our tools." (Scientists often use tools the Engineers built, but don't know how they work.)
What Scientists expect from Engineers:
- "Please make my code look professional and fast." (Scientists want their messy prototypes turned into polished products.)
- "Please help me fix the technical stuff so I can focus on the science."
- "Please learn a little bit about my science so you don't ask stupid questions."
The 21 "Friction Points"
When these expectations clash, 21 specific types of friction appear. Here are the big ones, explained simply:
- The "Speed vs. Safety" Clash: Scientists want to move fast and break things to learn. Engineers want to move slow and build things that last. This creates Technical Debt (a pile of messy code that needs to be fixed later).
- The "Who Owns This?" Confusion: In the old days, the Scientist handed off the work, and the Engineer took over. Now, they share ownership. But sometimes, the Scientist thinks, "That's not my job," and the Engineer thinks, "I didn't write that, so I won't fix it."
- The "Black Box" Problem: Scientists often don't understand the complex tools the Engineers use, and Engineers don't understand the deep science the Scientists are doing. It's like a chef and a farmer trying to cook a meal together without speaking the same language.
- The "Documentation" Nightmare: Engineers need manuals to understand the code. Scientists often skip writing them because they are in a rush. This leaves the Engineers guessing, "What does this button do?"
The Solution: How to Fix the Collision
The paper suggests that we can't just tell people to "get along." We need to change how we build these teams.
- For Researchers: We need to invent new ways for these teams to work together, maybe using AI to act as a translator between the "Science language" and the "Engineering language."
- For Tool Builders: We need to build software that helps. Imagine an AI assistant that says, "Hey, you're writing code too fast for the safety rules. Here's a quick fix," or "You forgot to write a note about why you did this."
- For Teams: Before starting a project, sit down and agree on the "Rules of the Road."
- Agreement: "We will write code fast, but we will clean it up every Friday."
- Agreement: "The Scientist will explain the 'Why,' and the Engineer will explain the 'How,' and we will both listen."
The Bottom Line
The paper concludes that these teams don't fail because people aren't smart enough. They fail because they are philosophically different.
It's not about ability; it's about alignment. If you want a spaceship that flies to Mars and discovers new life, you can't just throw an Engineer and a Scientist in a room and hope for the best. You have to build a bridge between their two worlds, acknowledge their differences, and create a new set of rules that works for both of them.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.