New
International Conference on Information Systems (ICIS) (2014) AI Processed Human Approved
IS Design Principles for Empowering Domain Experts in Innovation:Findings From Three Case Studies
This paper investigates how collaborative information systems can be designed to empower domain experts to configure software applications according to their specific needs. Through a qualitative three-year field study of three innovation networks, the authors observe domain experts using a wiki-based collaborative information system and derive design principles for domain expert configuration.
Problem
Cooperative innovation projects involving multiple partnering firms struggle with managing knowledge, methodical, and relational diversity. Traditional software applications are rigid and cannot easily adapt on-the-fly to the specific, evolving requirements of diverse expert specialists from different organizations.
Outcome
- Identified key design principles for domain expert configurable software, including iterative modeling, content-context relation, information re-use, function re-use, and context alignment.
- Highlighted the essential role of 'facilitators' as mediating agents who help bridge technical configuration mechanisms with business domain requirements.
- Demonstrated that domain expert configuration provides a flexible, cost-effective method to align IT support with dynamic inter-organizational innovation processes.
- Highlighted the essential role of 'facilitators' as mediating agents who help bridge technical configuration mechanisms with business domain requirements.
- Demonstrated that domain expert configuration provides a flexible, cost-effective method to align IT support with dynamic inter-organizational innovation processes.
What it means for you
- CIO / IT Executive: On Monday morning, schedule a brief meeting with your innovation network leads to discuss the potential of 'domain expert configuration' for upcoming projects, specifically asking them to identify one current pain point related to rigid software that could be addressed by such a system.
- IT Manager: On Monday morning, review your current internal documentation for any existing examples of 'facilitators' – individuals who successfully bridge technical and business needs – and plan a quick chat with one of them to understand their approach.
- Business Strategist: On Monday morning, draft a one-page concept document outlining how a more flexible, domain expert-configurable information system could accelerate a specific strategic innovation initiative, focusing on the benefits of rapid adaptation to diverse partner needs.
- Researcher: On Monday morning, identify three publicly available collaborative information systems (e.g., wikis, content management systems) that exhibit elements of 'content-context relation' or 'information re-use' and briefly document how they do so.
- Policymaker: On Monday morning, review existing procurement guidelines for IT systems to identify any clauses that might hinder the adoption of flexible, configurable solutions, and consider proposing a pilot program to test the effectiveness of domain expert configuration for inter-organizational projects.
Transcript
Host: Welcome back to A.I.S. Insights — powered by Living Knowledge. I'm Anna Ivy Summers. Today, we're diving into a fascinating research study titled "IS Design Principles for Empowering Domain Experts in Innovation: Findings From Three Case Studies." Joining me is our lead analyst, Alex Ian Sutherland. Alex, great to have you here.
Expert: Thanks, Anna. It's fantastic to be here to talk about this study.
Host: So, Alex, to kick things off, what is this study really about at its core?
Expert: At its heart, the study explores how collaborative information systems can be designed so that subject matter experts—people like engineers or material scientists—can easily configure software applications to suit their specific needs, without having to rely on software developers every time something changes.
Host: That sounds like a major bottleneck for many organizations. What is the big real-world problem these researchers were trying to address?
Expert: Exactly. When small and medium enterprises partner up in innovation networks—say, to develop a new medical device or an advanced textile—they face three major types of diversity: knowledge diversity, methodical diversity, and relational diversity. People from different companies and technical backgrounds speak different languages and use different processes. Traditional, rigid software simply cannot adapt on-the-fly to the fast-moving, dynamic requirements of these cross-company teams.
Host: So off-the-shelf tools are too stiff, but full custom software development takes too long and costs too much. How did the researchers approach studying a solution?
Expert: They conducted a three-year design science field study following three real innovation networks. These networks were working on radical new products, like a novel dampening material for motorbike helmets, a cardiovascular stentgraft, and new textile coating processes. The research team provided them with a shared, wiki-based collaborative information system. But this wasn't just a basic wiki—it was a "hybrid" wiki that allowed experts to build structured data models and customized apps directly on top of unstructured content.
Host: A hybrid wiki where domain experts can build their own mini-apps—that's fascinating. What were the key findings from observing these teams in action?
Expert: The study derived several core design principles. First is iterative modeling, which seamlessly connects informal wiki notes with structured data schemas. Second is function and information re-use, meaning teams can take complex innovation methods, like Quality Function Deployment, and turn them into reusable templates for future projects. But perhaps the most crucial finding was the importance of user roles—specifically, the role of the "facilitator."
Host: Tell us more about this facilitator role. Why are they so central to making this work?
Expert: In many tech projects, there is a gap between functional experts who understand the business process and technical domain experts who handle software configuration. The study highlighted facilitators as mediating agents. They are skilled IT professionals or consultants who work directly with domain experts to translate innovation methods into software setups. In fact, after seeing these field results, the software provider involved in the study actually altered their entire business model—shifting from custom software development toward providing facilitation services to empower clients!
Host: That is a remarkable business transformation driven directly by field research. Why does all of this matter so much for business leaders and tech managers today?
Expert: It fundamentally changes how we think about IT management in inter-firm collaborations. Instead of forcing partner companies into rigid software tools or buying separate specialized software for every new process, organizations can empower domain experts to shape their own software environment as the project evolves. It lowers total lifecycle costs, dramatically improves agility, and lets domain experts focus on driving radical innovations rather than fighting their software tools.
Host: It really sounds like a game-changer for cross-industry innovation and collaborative technology. Alex, thank you so much for breaking down this insightful study for us today.
Expert: My pleasure, Anna.
Host: And thank you all for listening to A.I.S. Insights — powered by Living Knowledge. Be sure to subscribe and join us next time as we continue to explore the ideas shaping modern technology and business strategy.
Expert: Thanks, Anna. It's fantastic to be here to talk about this study.
Host: So, Alex, to kick things off, what is this study really about at its core?
Expert: At its heart, the study explores how collaborative information systems can be designed so that subject matter experts—people like engineers or material scientists—can easily configure software applications to suit their specific needs, without having to rely on software developers every time something changes.
Host: That sounds like a major bottleneck for many organizations. What is the big real-world problem these researchers were trying to address?
Expert: Exactly. When small and medium enterprises partner up in innovation networks—say, to develop a new medical device or an advanced textile—they face three major types of diversity: knowledge diversity, methodical diversity, and relational diversity. People from different companies and technical backgrounds speak different languages and use different processes. Traditional, rigid software simply cannot adapt on-the-fly to the fast-moving, dynamic requirements of these cross-company teams.
Host: So off-the-shelf tools are too stiff, but full custom software development takes too long and costs too much. How did the researchers approach studying a solution?
Expert: They conducted a three-year design science field study following three real innovation networks. These networks were working on radical new products, like a novel dampening material for motorbike helmets, a cardiovascular stentgraft, and new textile coating processes. The research team provided them with a shared, wiki-based collaborative information system. But this wasn't just a basic wiki—it was a "hybrid" wiki that allowed experts to build structured data models and customized apps directly on top of unstructured content.
Host: A hybrid wiki where domain experts can build their own mini-apps—that's fascinating. What were the key findings from observing these teams in action?
Expert: The study derived several core design principles. First is iterative modeling, which seamlessly connects informal wiki notes with structured data schemas. Second is function and information re-use, meaning teams can take complex innovation methods, like Quality Function Deployment, and turn them into reusable templates for future projects. But perhaps the most crucial finding was the importance of user roles—specifically, the role of the "facilitator."
Host: Tell us more about this facilitator role. Why are they so central to making this work?
Expert: In many tech projects, there is a gap between functional experts who understand the business process and technical domain experts who handle software configuration. The study highlighted facilitators as mediating agents. They are skilled IT professionals or consultants who work directly with domain experts to translate innovation methods into software setups. In fact, after seeing these field results, the software provider involved in the study actually altered their entire business model—shifting from custom software development toward providing facilitation services to empower clients!
Host: That is a remarkable business transformation driven directly by field research. Why does all of this matter so much for business leaders and tech managers today?
Expert: It fundamentally changes how we think about IT management in inter-firm collaborations. Instead of forcing partner companies into rigid software tools or buying separate specialized software for every new process, organizations can empower domain experts to shape their own software environment as the project evolves. It lowers total lifecycle costs, dramatically improves agility, and lets domain experts focus on driving radical innovations rather than fighting their software tools.
Host: It really sounds like a game-changer for cross-industry innovation and collaborative technology. Alex, thank you so much for breaking down this insightful study for us today.
Expert: My pleasure, Anna.
Host: And thank you all for listening to A.I.S. Insights — powered by Living Knowledge. Be sure to subscribe and join us next time as we continue to explore the ideas shaping modern technology and business strategy.