MIS Quarterly Executive (2015) AI Processed Human Approved
Role of Information Systems in Empowering Innovation Networks
This study investigates how information systems (IS) support open innovation networks among small and medium-sized enterprises (SMEs). Through a three-year case study of an inter-organizational medical device project developing a cardiovascular stent graft, the authors examine the key IS functionalities required across the open innovation process.
Problem
Developing complex products increasingly requires open innovation networks where independent firms pool their specialized expertise and resources. However, conventional enterprise applications are not designed for open innovation, creating a gap in understanding how to select, configure, and maintain a shared IS infrastructure across diverse network partners.
Outcome
- Identifies five key IS functionalities critical for innovation networks: collaborative work environments, knowledge maps, knowledge spaces, innovation procedure toolkits, and social media platforms.
- Reveals that network success stems from pragmatically using a diverse set of accessible IS tools to form a shared infrastructure rather than relying on a single complex system.
- Delivers nine practical guidelines for CIOs to manage IS infrastructure across the co-shaping, co-performing, and co-opting phases of open innovation networks.
- Reveals that network success stems from pragmatically using a diverse set of accessible IS tools to form a shared infrastructure rather than relying on a single complex system.
- Delivers nine practical guidelines for CIOs to manage IS infrastructure across the co-shaping, co-performing, and co-opting phases of open innovation networks.
What it means for you
- CIO / IT Executive: On Monday morning, initiate a review of our existing IS tools to identify at least three readily accessible platforms (e.g., cloud-based project management, secure file sharing, internal wiki) that can be quickly configured to support a collaborative work environment for our next cross-company project, prioritizing ease of adoption for all partners.
- IT Manager: On Monday morning, assess the user-friendliness and integration capabilities of our current knowledge management system and identify any gaps. Then, plan a quick training session for a pilot group of users demonstrating how to tag and categorize project-related documents to build a rudimentary 'knowledge map' for our innovation network.
- Business Strategist: On Monday morning, draft a brief outline of key innovation challenges and opportunities for our next external collaboration, and then identify which of the five identified IS functionalities (collaborative work environments, knowledge maps, knowledge spaces, innovation procedure toolkits, and social media platforms) would be most impactful in addressing these specific challenges, focusing on pragmatic tool selection.
- Researcher: On Monday morning, begin cataloging and categorizing the publicly available 'innovation procedure toolkits' or best practice guides that could be shared or adapted for our current project, focusing on those with clear, step-by-step instructions that can be easily integrated into a shared digital space.
- Policymaker: On Monday morning, draft a short proposal for an initiative that encourages or provides resources for SMEs to adopt cloud-based collaborative platforms, specifically highlighting how these platforms can support cross-organizational knowledge sharing and innovation within their respective industries.
Transcript
Host: Welcome to A.I.S. Insights — powered by Living Knowledge. I'm your host, Anna Ivy Summers. Today, we're exploring an insightful study titled "Role of Information Systems in Empowering Innovation Networks." Joining me is our expert analyst, Alex Ian Sutherland. Welcome, Alex!
Expert: Thanks, Anna! It's great to be here.
Host: Alex, this study looks at how small and medium-sized enterprises—or SMEs—use information systems to collaborate and innovate together. What is the core problem the research addresses?
Expert: Well Anna, bringing a novel, complex product to market is a massive undertaking. Traditionally, only huge corporations had the internal resources and R&D budgets to manage everything in-house. Today, even large firms depend on network partners. For smaller companies, forming an "open innovation network" is often the only effective way to compete with industry giants.
Host: But managing a network of independent companies must bring its own set of challenges, right?
Expert: Absolutely. Most traditional enterprise software is designed for a single organization, not for open innovation across corporate boundaries. Partnering firms face huge gaps in knowing how to select, configure, and maintain a shared IT setup without compromising their intellectual property or drowning in coordination chaos.
Host: So how did the researchers investigate this issue?
Expert: They conducted a deep, three-year case study following a European innovation network centered around a Czech medical device firm called Medcorp. The goal was to develop a next-generation cardiovascular stent graft using an innovative nickel-titanium composite called Nitinol.
Host: And because that required expertise in textiles, wire processing, specialized machinery, and clinical research, no single firm could tackle it alone.
Expert: Exactly. Over three years, the researchers conducted more than 50 interviews and analyzed hundreds of project documents to track how these firms used information systems across the entire project lifecycle.
Host: What were the most striking findings from observing this network?
Expert: The biggest takeaway was that success didn't come from deploying a single, highly complex enterprise software system. Instead, the network succeeded by pragmatically combining a diverse set of accessible, flexible tools into a shared IS infrastructure.
Host: That is really practical. What specific system functionalities made up this infrastructure?
Expert: The study highlights five key functionalities. First, Collaborative Work Environments—such as wiki-based workspaces—for central project management and team communication. Second, Knowledge Maps, which graphically lay out each partner's expertise, value chain contribution, and technical role.
Host: So a Knowledge Map acts like an interactive directory of who knows what across the network?
Expert: Precisely. Third are Knowledge Spaces, which sit on top of the collaborative workspace to store deep technical parameters and definitions so everyone speaks the same language. Fourth, Innovation Procedure Toolkits, which offer structured problem-solving methods like Quality Function Deployment or TRIZ when technical roadblocks occur. And fifth, Social Media platforms to identify new external partners and track market trends.
Host: That sounds like a powerful combination. How can business leaders and CIOs translate this into actionable strategy?
Expert: The study breaks down practical guidelines across three phases of open innovation: co-shaping, co-performing, and co-opting. In the co-shaping phase, when forming the network, CIOs should use tools like Knowledge Maps to map the ecosystem and position their firm's capabilities as distinct services.
Host: What about the second phase, co-performing, when the actual product development happens?
Expert: That's where alignment is key. CIOs need to establish joint project and innovation management through shared workspaces and toolkits. This keeps teams agile while ensuring technical workflows and parameters remain synchronized across all firms.
Host: And what should happen in the final phase, co-opting?
Expert: In the final phase, the focus shifts to ensuring regulatory compliance—like FDA standards—and preserving the shared IT infrastructure for future projects. This allows partners to turn a single product success into long-term competitive capability.
Host: So the central lesson for business leaders is that innovating in networks isn't about buying expensive new software, but about orchestrating accessible tools strategically across the project lifecycle.
Expert: Spot on, Anna. It's about building an ecosystem of IT services that fosters trust, clear coordination, and continuous learning across organizational borders.
Host: Fantastic insights, Alex. Thank you so much for breaking down this study for us today. And thank you to our listeners for tuning in to A.I.S. Insights — powered by Living Knowledge. Until next time!
Expert: Thanks, Anna! It's great to be here.
Host: Alex, this study looks at how small and medium-sized enterprises—or SMEs—use information systems to collaborate and innovate together. What is the core problem the research addresses?
Expert: Well Anna, bringing a novel, complex product to market is a massive undertaking. Traditionally, only huge corporations had the internal resources and R&D budgets to manage everything in-house. Today, even large firms depend on network partners. For smaller companies, forming an "open innovation network" is often the only effective way to compete with industry giants.
Host: But managing a network of independent companies must bring its own set of challenges, right?
Expert: Absolutely. Most traditional enterprise software is designed for a single organization, not for open innovation across corporate boundaries. Partnering firms face huge gaps in knowing how to select, configure, and maintain a shared IT setup without compromising their intellectual property or drowning in coordination chaos.
Host: So how did the researchers investigate this issue?
Expert: They conducted a deep, three-year case study following a European innovation network centered around a Czech medical device firm called Medcorp. The goal was to develop a next-generation cardiovascular stent graft using an innovative nickel-titanium composite called Nitinol.
Host: And because that required expertise in textiles, wire processing, specialized machinery, and clinical research, no single firm could tackle it alone.
Expert: Exactly. Over three years, the researchers conducted more than 50 interviews and analyzed hundreds of project documents to track how these firms used information systems across the entire project lifecycle.
Host: What were the most striking findings from observing this network?
Expert: The biggest takeaway was that success didn't come from deploying a single, highly complex enterprise software system. Instead, the network succeeded by pragmatically combining a diverse set of accessible, flexible tools into a shared IS infrastructure.
Host: That is really practical. What specific system functionalities made up this infrastructure?
Expert: The study highlights five key functionalities. First, Collaborative Work Environments—such as wiki-based workspaces—for central project management and team communication. Second, Knowledge Maps, which graphically lay out each partner's expertise, value chain contribution, and technical role.
Host: So a Knowledge Map acts like an interactive directory of who knows what across the network?
Expert: Precisely. Third are Knowledge Spaces, which sit on top of the collaborative workspace to store deep technical parameters and definitions so everyone speaks the same language. Fourth, Innovation Procedure Toolkits, which offer structured problem-solving methods like Quality Function Deployment or TRIZ when technical roadblocks occur. And fifth, Social Media platforms to identify new external partners and track market trends.
Host: That sounds like a powerful combination. How can business leaders and CIOs translate this into actionable strategy?
Expert: The study breaks down practical guidelines across three phases of open innovation: co-shaping, co-performing, and co-opting. In the co-shaping phase, when forming the network, CIOs should use tools like Knowledge Maps to map the ecosystem and position their firm's capabilities as distinct services.
Host: What about the second phase, co-performing, when the actual product development happens?
Expert: That's where alignment is key. CIOs need to establish joint project and innovation management through shared workspaces and toolkits. This keeps teams agile while ensuring technical workflows and parameters remain synchronized across all firms.
Host: And what should happen in the final phase, co-opting?
Expert: In the final phase, the focus shifts to ensuring regulatory compliance—like FDA standards—and preserving the shared IT infrastructure for future projects. This allows partners to turn a single product success into long-term competitive capability.
Host: So the central lesson for business leaders is that innovating in networks isn't about buying expensive new software, but about orchestrating accessible tools strategically across the project lifecycle.
Expert: Spot on, Anna. It's about building an ecosystem of IT services that fosters trust, clear coordination, and continuous learning across organizational borders.
Host: Fantastic insights, Alex. Thank you so much for breaking down this study for us today. And thank you to our listeners for tuning in to A.I.S. Insights — powered by Living Knowledge. Until next time!