{"id":"921b732c-8b00-4a73-bf8c-c017c260d36f","arxiv_id":"2411.17768","paper_version":1,"verdict":"CONDITIONAL","confidence":"MODERATE","novelty_score":4.0,"correctness_risk":"medium","formal_verification":"none","parameter_count":0,"one_line_summary":"A content analysis of practitioner interviews identifies four categories of barriers (technological, economic, regulatory, organizational) to integrating design for assembly into modular architectures built with Modular Function Deployment.","lead":"Researchers interviewed Swedish manufacturing practitioners and students to find why Design for Assembly principles are rarely used when companies build modular product architectures. They grouped the obstacles into four categories, technological, economic, regulatory, and organizational, as a starting point for companies and tool developers.","discovery_kind":"extension","skeptic_critique":{"model":"deepseek-v4-flash","headline":"TERO categories may be pre-structured by the focus group protocol and prior literature rather than emergent from content analysis, since the seven-to-four grouping is undocumented.","rationale":"I read the paper as an exploratory qualitative study that aims to provide a structured overview of barriers. The authors are transparent about limitations, and the practical insights from practitioners are plausibly useful. However, the claim that the TERO model was 'identified through content analysis' requires that the categories be grounded in the data. The two documented problems - pre-structured prompts and an undocumented grouping step - make the taxonomy's empirical status uncertain. This is not a claim of misconduct; it is a standard question of methodological transparency in qualitative research. The reader's verdict of CONDITIONAL is appropriate; the paper would need to supply the coding protocol and demonstrate reliability before the central claim can be accepted as an empirical finding. My concern is more specific than sample representativeness, so agreement is partial.","tokens_in":16600,"tokens_out":3632,"duration_ms":34218,"concrete_test":"Obtain the de-identified transcripts and the seven-theme coding (the stated unit of analysis is the group/individual). Have two independent coders, blinded to the TERO framework, redo the open coding on a random 25% of the data and then attempt to collapse the resulting themes into four categories using only the paper's description of TERO. Compute Cohen's kappa on the theme-to-category assignment. If kappa is below 0.6, or if 'regulatory' and 'economic' themes do not emerge from the data without the interview prompts, the TERO taxonomy is not a reliable content-analysis finding and the conceptual model should be presented as a researcher-proposed synthesis, not an empirical result.","verdict_should_be":"UNCHANGED","load_bearing_attack":"The central claim is that content analysis of practitioner discussions identified four major barrier categories (TERO). The load-bearing requirement is that these categories are an output of the analysis, not an input to it. Two features of the manuscript undercut that requirement. First, the data collection instrument is already TERO-laden: Appendix B item 2 of the focus group structure explicitly asks about 'organizational or technical barriers,' pre-naming two of the four categories, and the interview protocol prompts AI use and DFX considerations that map onto regulatory and technological concerns. The Theoretical background also states that the literature review 'provided the main topics of discussion,' so the discussion is scaffolded by the authors' prior framework. Second, the Results section first presents seven themes (assembly strategy, advanced technologies, collaboration, design, workforce, information/visuals, performance evaluation), then states these 'can be further grouped into four main thematic categories' without showing the coding rule, the mapping, or any reliability check. If the grouping is an arbitrary post-hoc partition, or if the categories mainly reflect the prompts, then the paper's claim to have 'identified' TERO through content analysis is not supported, even for the ten participants. The sample-size limitation the authors acknowledge is secondary; the more immediate issue is construct validity within the sample.","agreement_with_reader":"partial"},"referee_report":{"model":"deepseek-v4-flash","summary":"This paper reports a qualitative, exploratory study of barriers to integrating Design for Assembly (DFA) into modular product architectures developed with Modular Function Deployment (MFD). The authors conducted a focus group with ten participants (industry practitioners, one researcher, and students) and five follow-up interviews with a subset of the practitioners, then applied content analysis to the transcripts. The results are presented as seven themes (assembly strategy, advanced technologies, collaboration, design, workforce, information and visuals, performance evaluation), which are then grouped into four barrier categories—technological, economic, regulatory, organizational (TERO)—forming a conceptual model. The paper argues that multidisciplinary collaboration is central to overcoming these barriers and frames the model as a guide for practitioners and a foundation for future research.","tokens_in":16805,"tokens_out":5001,"duration_ms":46194,"significance":"If the TERO taxonomy were demonstrably an emergent outcome of the content analysis, this paper would provide a useful structured vocabulary for studying DFA-MFD integration and a convenient starting point for companies. It is valuable that the authors report direct practitioner quotes, document the focus-group and interview protocols in appendices, and are transparent about generalizability, researcher bias, and review limitations. The proposed conceptual model, however, is only as strong as the evidence that the categories were derived from the data rather than imposed by the data-collection instrument and the authors' prior literature review. Because that evidence is not currently provided, the contribution remains plausibly useful but is not established by the analysis as reported.","major_comments":[{"comment":"The claim that TERO categories were 'identified through content analysis' is undercut by the design of the data-collection instrument. The text states that the authors' previous literature review 'provided the main topics of discussion for qualitative data collection,' and Appendix B's focus-group topic (2) explicitly asks about 'organizational or technical barriers,' naming two of the four categories before data collection. The interview protocol also prompts for DFX and AI considerations, which map onto the technological and regulatory categories. As a result, the TERO labels are plausibly inputs to the data-generation process rather than outputs of the content analysis. To support the stated claim, the paper should provide evidence that the coding scheme was developed independently of these labels (e.g., an open-coding phase with a codebook and a clear indication of when TERO labels were first introduced), or it should reframe the contribution as a literature-based framework whose relevance is illustrated by practitioner discussion.","section":"Theoretical background; Methodology/Data collection; Appendix B"},{"comment":"The step from seven themes to four TERO categories is not documented. The paper states that 'the limitations identified through content analysis can be further grouped into four main thematic categories' but does not give the grouping rule, a crosswalk from themes (or codes) to categories, or any reliability check. The mapping is also not self-evident: Table 2 contains no theme named 'economic' or 'regulatory,' and themes such as collaboration, workforce, and information/visuals could all fall under 'organizational' or under distinct categories depending on the rule chosen. Without a coding audit trail, or at least a table showing which codes and quotes support each of the four categories, the TERO taxonomy is underdetermined by the reported analysis.","section":"Results, Conceptual model development; Table 2"},{"comment":"The limitations section acknowledges generalizability and researcher bias but does not address the more specific circularity risk: the same literature review that shaped the focus-group and interview topics is later used, together with the primary data, as part of the evidence base for the conceptual model (Theoretical background; Methodology). This is a load-bearing validity concern because it directly affects whether the 'identified' categories are an empirical result. The authors should either provide a concrete mitigation (e.g., a separate confirmatory coding pass in which the TERO labels were not visible) or explicitly recharacterize the model as a synthesis of literature and illustrative practitioner insights rather than as an emergent content-analysis finding.","section":"Discussion, Limitations and future work"}],"minor_comments":[{"comment":"The sentence citing '[30, 31]' as 'studies to perform content analysis' appears to be a citation error: references [30] and [31] are design-for-disassembly papers, not methodological sources on content analysis. The authors should cite [35] or another recognized content-analysis methods reference at that point.","section":"Methodology, Data analysis"},{"comment":"The manuscript contains the placeholders '[Fig, 1 around here]' and '[Fig. 2 around here]' but the actual figures are not visible in the text provided; the final submission must include the figures with clear labels and sufficient resolution, since Fig. 2 is the conceptual model that the conclusions rely on.","section":"Figures"},{"comment":"The abstract and conclusions state that the study 'identified four major categories' without hedging, which is stronger than the exploratory evidence warrants; a phrase such as 'proposes a preliminary categorization' would better match the acknowledged limitations.","section":"Abstract; Conclusions"}],"recommendation":"major_revision","confidential_remarks":"The manuscript is within scope for an engineering design or production engineering journal, and the practitioner-access component is a strength. The decisive issue is construct validity: the TERO categories appear to be partly pre-structured by the protocol and prior literature, and the coding procedure is not documented. This is fixable by providing a coding audit trail or by reframing the contribution as a literature-based framework with illustrative practitioner input. I would not reject outright, but the current version overstates what the content analysis supports."},"author_rebuttal":null,"desk_editor":{"model":"deepseek-v4-flash","letter":"This paper is best read as an exploratory qualitative study of why Design for Assembly (DFA) is hard to integrate into modular product architectures built with Modular Function Deployment (MFD). What it actually contributes is new primary data: a two-hour focus group with ten mostly Swedish practitioners and students, plus five follow-up interviews, presented as seven themes (assembly strategy, advanced technologies, collaboration, design, workforce, information/visuals, performance evaluation) with concrete quotes. That material is useful, and the authors are honest about generalizability limits and researcher bias.\n\nThe soft spot is the paper's central claim. The abstract says content analysis 'identified' four barrier categories: technological, economic, regulatory, organizational (TERO). But reading the methods and appendices, those categories look less like an emergent finding and more like an input. The focus group structure explicitly asks about 'organizational or technical barriers' (two of the four), the interview protocol prompts topics that map onto the others, and the authors state their prior literature review 'provided the main topics of discussion.' The results then jump from seven themes to four 'thematic categories' without showing the coding rule or mapping. That is a construct-validity gap inside the sample, not just a sampling-size issue.\n\nThe paper does not collapse from this. The seven themes stand on their own as a reasonable description of what this group raised, and the TERO model is a plausible organizational device. But 'identified' overstates what the evidence supports. The authors should either reframe the claim as 'proposed' or 'structured,' or provide a transparent coding trail—the decision rules, the theme-to-category mapping, and any reliability check.\n\nFor whom: practitioners and researchers working on DFA/MFD will find a compact summary of real-world obstacles and a starting point. It is not a breakthrough and the taxonomy resembles TOE/PESTLE, but the empirical synthesis is new.\n\nI'd send it to review, but with clear expectations of major revision around the inference from data to categories.","headline":"Useful exploratory data on DFA-MFD barriers, but the TERO taxonomy is seeded by the research instruments rather than clearly emergent from the data.","tokens_in":17316,"tokens_out":1706,"would_cite":false,"duration_ms":16572,"reading_group":"maybe","serious_thinker":"yes","would_accept_peer_review":true},"rs_alignment":null,"lean_confirmation":null,"pith_extraction":{"msc":[],"pacs":[],"model":"deepseek-v4-flash","headline":"Design for Assembly in modular architectures is blocked by four categories of barriers: technological, economic, regulatory, and organizational.","keywords":["modular product architecture","design for assembly (DFA)","content analysis","practitioner interviews","modular function deployment (MFD)","barriers to adoption","conceptual model","mass customization"],"falsifier":"A broad, pre-registered survey of modular product development teams in different countries and sectors that fails to reproduce the four TERO categories, or that surfaces a major barrier not fitting any of them, would directly undermine the model's claim to completeness.","tokens_in":16377,"feed_emoji":"🧩","tokens_out":3779,"duration_ms":31047,"temperature":0.7,"pith_summary":"This paper investigates why Design for Assembly (DFA) is rarely integrated when companies create modular product architectures using Modular Function Deployment (MFD). Through content analysis of a focus group and follow-up interviews with industry practitioners, the authors identify four categories of barriers: technological, economic, regulatory, and organizational (TERO). They argue that these barriers must be addressed jointly and that multidisciplinary collaboration is essential for informed decision-making in the early design phase. A sympathetic reader would care because the resulting conceptual model gives companies a structured starting point for making modular products easier and cheaper to assemble.","feed_headline":"Four barrier types block design-for-assembly in modular products","feed_subtitle":"Technological, economic, regulatory, and organizational hurdles companies face when linking DFA to MFD-based design.","key_machinery":"The central object is the TERO conceptual model, a taxonomy that groups content-analysis codes into four barrier categories: Technological, Economic, Regulatory, and Organizational. It is derived inductively from a two-hour focus group with ten participants, five follow-up semi-structured interviews, and prior literature, and it serves to simplify and structure the heterogeneous challenges practitioners report. The model's function is to give companies and researchers a common vocabulary for diagnosing why DFA adoption stalls and for targeting future support tools.","core_discovery":"On the authors' own terms, the central discovery is that the obstacles to integrating DFA into MFD-based modular product development are not merely technical but cluster into four named thematic groups. Technological barriers concern limits of current tools and the difficulty of embedding assembly, recyclability, and hazardous-material considerations into the architecture. Economic barriers include the cost of new technology, uncertain return on investment, and conflicting supply-chain incentives. Regulatory barriers cover compliance, data confidentiality, and emerging AI legislation. Organizational barriers include resistance to change, siloed knowledge, and inadequate training. The authors further claim that cross-functional collaboration among designers, operators, suppliers, and maintenance staff is the single most important mechanism for overcoming these barriers.","pith_inferences":["By extension, the TERO categories are likely not exclusive to MFD: any modular product development method that postpones assembly considerations could exhibit similar barrier groups, so the taxonomy may transfer to other modularization approaches.","The sample is concentrated among Swedish manufacturing practitioners, so the relative weight of the four barrier types probably varies by region, industry, and company size; a quantitative survey would reveal which categories dominate in other settings.","If multidisciplinary collaboration is the key lever, then a testable prediction is that MFD teams with formal cross-functional reviews in the conceptual phase should show measurably fewer assembly-driven design changes later.","The paper's claim that quantitative data are scarce in early MFD stages points to a concrete extension: instrumenting MFD projects to track when assembly metrics become available could validate the barrier and guide new tooling."],"forward_implications":["If the TERO model is right, companies can diagnose stalled DFA integration by locating which of the four barrier groups is active, rather than treating assembly problems as purely technical.","The finding that multidisciplinary collaboration is essential implies that cross-functional teams, involving operators and suppliers early, should be a standard part of MFD projects.","The emphasis on limited quantitative data in early MFD stages suggests that tools for estimating assembly metrics at the conceptual phase would address a recurring economic and technological barrier.","Regulatory concerns, especially data confidentiality and AI compliance, will become a growing constraint on AI-driven design support.","The model provides a basis for benchmarking and for developing targeted guides, metrics, and indices to support adoption."],"supporting_citations":[{"why":"Defines the Modular Function Deployment method, the target method whose assembly integration is being studied.","marker":"[8]"},{"why":"Previous literature review that frames the research gaps and supplies the topic clusters used to structure the focus group and interviews.","marker":"[15]"},{"why":"Establishes Design for Assembly as the key design-for-manufacture approach, the concept whose adoption is being examined.","marker":"[17]"},{"why":"Provides the thematic analysis method used for the content analysis of the qualitative data.","marker":"[34]"},{"why":"Supplies the focus group methodology that underpins the primary data collection.","marker":"[39]"}],"fun_headline_variants":["TERO barriers stall DFA integration in modular architecture","Study pinpoints tech, economic, regulatory, and organizational hurdles to DFA","Assembly-friendly modular design: four barrier groups identified","Why design-for-assembly lags in modular products: four barrier types"],"cache_read_input_tokens":3200,"weakest_assumption_plain":"The study assumes that one two-hour focus group of ten participants, mostly Swedish practitioners, plus five follow-up interviews, is enough to identify the major barriers to DFA–MFD integration across industry.","fun_headline_variants_meta":{"raw":{"variants":["TERO barriers stall DFA integration in modular architecture","Study pinpoints tech, economic, regulatory, and organizational hurdles to DFA","Assembly-friendly modular design: four barrier groups identified","Why design-for-assembly lags in modular products: four barrier types"]},"model":"deepseek-v4-flash","effort":"low","cost_usd":0.000401,"raw_usage":{"total_tokens":2076,"prompt_tokens":911,"completion_tokens":1165,"prompt_tokens_details":{"cached_tokens":384},"prompt_cache_hit_tokens":384,"prompt_cache_miss_tokens":527,"completion_tokens_details":{"reasoning_tokens":1094}},"tokens_in":527,"tokens_out":1165,"duration_ms":10787,"temperature":1.0,"reasoning_tokens":1094,"cache_read_input_tokens":384,"cache_creation_input_tokens":0},"cache_creation_input_tokens":0},"created_at":"2026-08-12T12:22:57.511198+00:00","model_set":{"reader":"deepseek-v4-flash"},"falsifier":"A broad, pre-registered survey of modular product development teams in different countries and sectors that fails to reproduce the four TERO categories, or that surfaces a major barrier not fitting any of them, would directly undermine the model's claim to completeness.","supporting_citations":[{"cited_title":"Modular Function Deployment: A Method for Product Modularisation,","cited_arxiv_id":null,"evidence_quote":"Defines the Modular Function Deployment method, the target method whose assembly integration is being studied."},{"cited_title":"Towards the Definition of Assembly- Oriented Modular Product Architectures: A Systematic Review,","cited_arxiv_id":null,"evidence_quote":"Previous literature review that frames the research gaps and supplies the topic clusters used to structure the focus group and interviews."},{"cited_title":"Design for Assembly—The Key to Design for Manufacture,","cited_arxiv_id":null,"evidence_quote":"Establishes Design for Assembly as the key design-for-manufacture approach, the concept whose adoption is being examined."},{"cited_title":"Focus Group Methodology: A Review,","cited_arxiv_id":null,"evidence_quote":"Supplies the focus group methodology that underpins the primary data collection."}],"review_version":1}