Overview of secondary data sources and their analytical role in the study
| Type of document | Description | No. of documents | Firm size category | Innovation institutionalization | Cases used | Role in analysis |
|---|---|---|---|---|---|---|
| Internal innovation reports | Project summaries, innovation rationales, development timelines and post-project reflections | 18 | Large; Small–medium | Highly formalized (large firms); selectively formalized (small–medium firms) | All cases | Used to contextualize innovation activities and triangulate interview narratives |
| Customer feedback summaries | Aggregated customer satisfaction surveys, innovation evaluation reports and feedback dashboards | 9 | Large | Highly formalized | 2 cases | Informed interpretation of customer-perceived innovativeness based on documented customer evaluations |
| Product and service retrospectives | Post-launch reviews of product, service or solution development processes | 11 | Large; Small–medium | Moderately to highly formalized | 3 cases | Supported identification of co-creation configurations and interaction patterns |
| Co-creation and collaboration records | Workshop materials, joint development documentation and collaboration logs | 7 | Large; Small–medium | Practice-oriented; partially formalized | 2 cases | Provided evidence of customer involvement and interactional resource integration |
| Technical documentation and service blueprints | Descriptions of system integration, service processes and customer use contexts | 16 | Large | Highly formalized | 4 cases | Enabled analysis of co-implementation practices and adaptation mechanisms |
| Marketing and public communications | Websites, brochures, presentations and public innovation narratives | 14 | Large; Small–medium | Formalized external signaling | All cases | Used to contextualize innovation signaling and external visibility of innovativeness |
| Reflexive field notes and analytic memos | Researcher notes capturing interaction dynamics, tone and contextual observations | 12 | Analytical (researcher generated) | All cases | Integrated into coding to enhance interpretive depth and reflexivity |
| Type of document | Description | No. of documents | Firm size category | Innovation institutionalization | Cases used | Role in analysis |
|---|---|---|---|---|---|---|
| Internal innovation reports | Project summaries, innovation rationales, development timelines and post-project reflections | 18 | Large; Small–medium | Highly formalized (large firms); selectively formalized (small–medium firms) | All cases | Used to contextualize innovation activities and triangulate interview narratives |
| Customer feedback summaries | Aggregated customer satisfaction surveys, innovation evaluation reports and feedback dashboards | 9 | Large | Highly formalized | 2 cases | Informed interpretation of customer-perceived innovativeness based on documented customer evaluations |
| Product and service retrospectives | Post-launch reviews of product, service or solution development processes | 11 | Large; Small–medium | Moderately to highly formalized | 3 cases | Supported identification of co-creation configurations and interaction patterns |
| Co-creation and collaboration records | Workshop materials, joint development documentation and collaboration logs | 7 | Large; Small–medium | Practice-oriented; partially formalized | 2 cases | Provided evidence of customer involvement and interactional resource integration |
| Technical documentation and service blueprints | Descriptions of system integration, service processes and customer use contexts | 16 | Large | Highly formalized | 4 cases | Enabled analysis of co-implementation practices and adaptation mechanisms |
| Marketing and public communications | Websites, brochures, presentations and public innovation narratives | 14 | Large; Small–medium | Formalized external signaling | All cases | Used to contextualize innovation signaling and external visibility of innovativeness |
| Reflexive field notes and analytic memos | Researcher notes capturing interaction dynamics, tone and contextual observations | 12 | Analytical (researcher generated) | All cases | Integrated into coding to enhance interpretive depth and reflexivity |
(1) A “document” refers to a distinct organizational or research artefact (e.g. report, presentation, dashboard, workshop record or analytic memo), regardless of length or format
(2) Secondary data sources were used to triangulate interview material and to capture how customer evaluations of innovativeness are articulated, stabilized and mobilized within organizational and ecosystem practices
(3) In two cases, customer feedback summaries and innovation evaluation reports provided direct evidence of customer-perceived innovativeness, complementing interview accounts from supplier representatives with access to these materials
(4) Differences in the availability of customer evaluation data across cases reflect ecosystem roles, governance arrangements and documentation practices rather than analytical emphasis or data prioritization
Sharing content requires targeting cookies to be enabled. Please update your cookie preferences to use this feature.