ISR reviewers reward work that enters an ongoing IS conversation and changes it, not work that merely spots an unfilled cell in a table. Identify the specific stream — e.g., platform competition, digital labor, IT and firm value, security economics, recommender/algorithmic systems, knowledge collaboration, digital transformation — and state what that stream currently believes, what tension or anomaly you address, and how your result moves it.
ISR's defining mission is intradisciplinary: it prizes work that integrates behavioral, design-science, economic, and organizational perspectives rather than single-paradigm contributions. Positioning is where you make that bridge visible. Strong moves include:
Name both conversations and show the seam you stitch. This is what distinguishes an ISR-grade front end from a competent single-silo review.
Because ISR draws on cognitive psychology, economics, computer science, operations research, design science, organization theory, sociology, and strategic management, it is tempting to cite only the reference discipline. ISR expects you to engage the IS scholarship that owns the phenomenon and to show how the IT artifact makes this an IS contribution, not a borrowed one.
Run this as a concrete capability pass. First lock the digital artifact or system, user/firm behavior, identification or design evidence, and IS-theory contribution; then test whether the manuscript addresses IS reviewers who expect digital-technology theory, empirical or design leverage, and implications for organizations or markets.
claim / evidence / blocker / next edit rows so the next pass can patch the manuscript directly.resources/official-source-map.md for volatile rules and name the one unresolved fact that could change the recommendation.【Conversation(s)】[...]
【Current belief / tension】[...]
【Intradisciplinary bridge】perspectives joined: [...]
【IS engagement】owns-the-phenomenon cites present? [...]
【IT-artifact framing】[...]
【Next step】isr-methods or isr-contribution-framing