New
AI Processed Human Approved
How do combinations of different tools and routines help partner companies coordinate when developing new products?
Key findings
- Demonstrates that coordination across organizational boundaries is rarely driven by single, isolated tools, but rather through combinations of artifacts and routines termed composite boundary objects (CBOs).
- Shows that effective collaboration emerges from the combined interplay of material objects (such as prototypes and central IT platforms), abstract concepts (such as shared product visions), and informal work routines.
- Finds that cross-organizational coordination can emerge organically through everyday interactions, even when such coordination was not deliberately planned in advance.
- Reveals that composite boundary objects are temporary and evolve across project milestones, requiring managers to support flexible environments of communication rather than focusing on standalone software applications.
What it means for you
- CIO / IT Executive: Stop investing in standalone software silos and schedule a meeting with cross-company project leads on Monday morning to audit how your central IT platforms, shared physical prototypes, and communication routines are currently integrated to support external partners.
- IT Manager: On Monday morning, map out the digital tools and informal communication channels your team uses with external partners, and set up a shared digital workspace that links these tools directly to ongoing physical prototyping milestones.
- Business Strategist: On Monday morning, draft a flexible collaboration framework for your new product development project that combines shared product visions with routine check-ins, rather than relying on rigid, pre-planned coordination structures.
- Researcher: On Monday morning, design a qualitative study protocol to trace how digital platforms, physical prototypes, and informal routines co-evolve across specific milestones in inter-organizational innovation projects.
- Policymaker: On Monday morning, revise your innovation grant evaluation criteria to reward collaborative consortia that demonstrate flexible, multi-layered coordination mechanisms—such as combined digital and material artifact routines—rather than funding isolated software tools.
Summary
This study examines how cross-company teams coordinate and share knowledge during collaborative new product development. The authors conducted an in-depth qualitative case study following three partner firms in Italy over two years as they developed a novel safety helmet. Through 17 episodic interviews, the researchers analyzed how various tools, routines, and materials interacted to support cross-boundary collaboration.ProblemCollaborative knowledge creation across partner organizations is uncertain and complex, particularly in the fuzzy front-end of innovation projects. While research recognizes the importance of individual tools like spreadsheets or databases in bridging knowledge gaps, it largely ignores how diverse digital systems, communication routines, and working arrangements interact together to enable coordination.
Transcript
Host: Welcome to A.I.S. Insights — powered by Living Knowledge. I'm Anna Ivy Summers, and today we're exploring how companies can truly collaborate and innovate together when developing breakthrough products. We are diving into a fascinating study titled "Composite Boundary Objects In Inter-Organizational Innovation Activities" by Sven-Volker Rehm and Lakshmi Goel. Joining me today to unpack this research is our analyst, Alex Ian Sutherland. Welcome, Alex!
Expert: Thanks, Anna. It's great to be here. This study tackles a really critical question: when multiple organizations team up to invent something radically new, how do their teams actually coordinate and make sense of each other's specialized knowledge?
Host: That brings us straight to the big problem. We hear so much about open innovation and strategic partnerships, but the early stages of new product development—often called the "fuzzy front end"—can be chaotic. Alex, why is cross-firm knowledge sharing so difficult in practice?
Expert: Well, in these early stages, teams are dealing with high novelty and lots of tacit knowledge—expertise that lives in people's heads rather than in a neat manual. Traditional research often suggests that teams bridge these divides using what scholars call "boundary objects"—things like a shared database, a spreadsheet, or a technical blueprint that gives everyone a common language. But in the real world, innovation doesn't happen around a single, isolated piece of software. Teams juggle chat apps, CAD files, shared repositories, physical prototypes, and informal conversations. The problem is that prior research overlooked how all these different tools and routines interact together to produce coordination.
Host: So instead of looking at one software tool in a vacuum, we need to understand the whole ecosystem of tools and habits. How did the authors study this dynamic in action?
Expert: The authors took a qualitative approach, following an innovation project in Italy over two full years. The project brought together three different small and mid-sized companies: a chemical company, a product design and prototyping firm, and an engineering service provider. They formed a virtual team tasked with developing a completely new type of motorcycle safety helmet. The researchers conducted seventeen in-depth, episodic interviews, asking the team leaders to reconstruct specific breakthrough moments, conflicts, and everyday milestones.
Host: A virtual team inventing a high-tech safety helmet from scratch across three distinct industries sounds like a prime environment for miscommunication! What did the study find?
Expert: The central finding is that coordination across organizational lines is rarely driven by a single, standalone tool. Instead, it emerges through what the authors define as "composite boundary objects," or CBOs. A composite boundary object is a temporary portfolio of artifacts, work routines, and communication processes working together.
Host: Could you walk us through an example of how that works?
Expert: Absolutely. Take their first composite boundary object, which centered on prototype performance testing. The team ran physical impact tests on helmet materials. That test wasn't just a physical artifact; its results were uploaded to a newly introduced digital platform, which connected back to the team's shared vision of disrupting the motorcycle racing market. The physical prototype, the data tables on the platform, and the shared vision combined into a single composite structure. That combination triggered deep learning across syntactic, semantic, and pragmatic boundaries, motivating the team to keep refining their goals together.
Host: It wasn't just the IT platform or the physical helmet on its own; it was the combination of the physical test, the digital repository, and that shared vision. And what's especially interesting is that this coordination wasn't strictly planned from the start, right?
Expert: Exactly. That's another vital insight. Coordinated teamwork emerged organically through spontaneous events. In another instance, an engineer saw a published market test in a trade magazine showing competitors failing safety tests. He immediately jumped on a Skype call to share the news, logged it on the platform, and used it to align their marketing story. The news article, the impromptu call, and the platform worked in concert. The study shows that composite boundary objects are often temporary—they form around specific incidents, serve their purpose in aligning the partners, and evolve or dissolve as the project moves forward.
Host: That brings us to why this matters so much for business leaders and project managers. What are the key takeaways for companies managing joint innovation ventures?
Expert: First, stop searching for a single "silver bullet" enterprise tool to fix collaboration. Managers often invest heavily in a central platform and wonder why cross-firm alignment is still struggling. This study demonstrates that digital platforms only create value when they interlock with team routines, material artifacts, and shared emotional goals. Second, managers need to design and support flexible communication environments rather than rigid software setups. You have to allow teams the freedom to combine informal habits, like quick video calls, with formal data storage and physical testing. Recognizing that coordination structures are fluid and incident-driven helps leaders guide projects through uncertainty without stifling creativity.
Host: It's all about fostering an environment where tools, routines, and vision reinforce one another. To wrap up: successful cross-company innovation doesn't rely on isolated tools; it thrives on composite boundary objects that emerge dynamically to bridge knowledge gaps. Alex, thank you so much for breaking down this insightful study for us.
Expert: My pleasure, Anna.
Host: And thank you to our listeners for tuning in to A.I.S. Insights — powered by Living Knowledge. Join us next time as we continue exploring actionable insights from cutting-edge business and technology research. Stay curious!
Expert: Thanks, Anna. It's great to be here. This study tackles a really critical question: when multiple organizations team up to invent something radically new, how do their teams actually coordinate and make sense of each other's specialized knowledge?
Host: That brings us straight to the big problem. We hear so much about open innovation and strategic partnerships, but the early stages of new product development—often called the "fuzzy front end"—can be chaotic. Alex, why is cross-firm knowledge sharing so difficult in practice?
Expert: Well, in these early stages, teams are dealing with high novelty and lots of tacit knowledge—expertise that lives in people's heads rather than in a neat manual. Traditional research often suggests that teams bridge these divides using what scholars call "boundary objects"—things like a shared database, a spreadsheet, or a technical blueprint that gives everyone a common language. But in the real world, innovation doesn't happen around a single, isolated piece of software. Teams juggle chat apps, CAD files, shared repositories, physical prototypes, and informal conversations. The problem is that prior research overlooked how all these different tools and routines interact together to produce coordination.
Host: So instead of looking at one software tool in a vacuum, we need to understand the whole ecosystem of tools and habits. How did the authors study this dynamic in action?
Expert: The authors took a qualitative approach, following an innovation project in Italy over two full years. The project brought together three different small and mid-sized companies: a chemical company, a product design and prototyping firm, and an engineering service provider. They formed a virtual team tasked with developing a completely new type of motorcycle safety helmet. The researchers conducted seventeen in-depth, episodic interviews, asking the team leaders to reconstruct specific breakthrough moments, conflicts, and everyday milestones.
Host: A virtual team inventing a high-tech safety helmet from scratch across three distinct industries sounds like a prime environment for miscommunication! What did the study find?
Expert: The central finding is that coordination across organizational lines is rarely driven by a single, standalone tool. Instead, it emerges through what the authors define as "composite boundary objects," or CBOs. A composite boundary object is a temporary portfolio of artifacts, work routines, and communication processes working together.
Host: Could you walk us through an example of how that works?
Expert: Absolutely. Take their first composite boundary object, which centered on prototype performance testing. The team ran physical impact tests on helmet materials. That test wasn't just a physical artifact; its results were uploaded to a newly introduced digital platform, which connected back to the team's shared vision of disrupting the motorcycle racing market. The physical prototype, the data tables on the platform, and the shared vision combined into a single composite structure. That combination triggered deep learning across syntactic, semantic, and pragmatic boundaries, motivating the team to keep refining their goals together.
Host: It wasn't just the IT platform or the physical helmet on its own; it was the combination of the physical test, the digital repository, and that shared vision. And what's especially interesting is that this coordination wasn't strictly planned from the start, right?
Expert: Exactly. That's another vital insight. Coordinated teamwork emerged organically through spontaneous events. In another instance, an engineer saw a published market test in a trade magazine showing competitors failing safety tests. He immediately jumped on a Skype call to share the news, logged it on the platform, and used it to align their marketing story. The news article, the impromptu call, and the platform worked in concert. The study shows that composite boundary objects are often temporary—they form around specific incidents, serve their purpose in aligning the partners, and evolve or dissolve as the project moves forward.
Host: That brings us to why this matters so much for business leaders and project managers. What are the key takeaways for companies managing joint innovation ventures?
Expert: First, stop searching for a single "silver bullet" enterprise tool to fix collaboration. Managers often invest heavily in a central platform and wonder why cross-firm alignment is still struggling. This study demonstrates that digital platforms only create value when they interlock with team routines, material artifacts, and shared emotional goals. Second, managers need to design and support flexible communication environments rather than rigid software setups. You have to allow teams the freedom to combine informal habits, like quick video calls, with formal data storage and physical testing. Recognizing that coordination structures are fluid and incident-driven helps leaders guide projects through uncertainty without stifling creativity.
Host: It's all about fostering an environment where tools, routines, and vision reinforce one another. To wrap up: successful cross-company innovation doesn't rely on isolated tools; it thrives on composite boundary objects that emerge dynamically to bridge knowledge gaps. Alex, thank you so much for breaking down this insightful study for us.
Expert: My pleasure, Anna.
Host: And thank you to our listeners for tuning in to A.I.S. Insights — powered by Living Knowledge. Join us next time as we continue exploring actionable insights from cutting-edge business and technology research. Stay curious!