Publishing Information Systems Research with Engineering Rigor

Information systems research occupies a unique position at the intersection of technology, organizations, and society. It examines not only how digital systems are designed and implemented but also how they influence decision-making, organizational performance, human behavior, and broader social outcomes. As artificial intelligence, cloud computing, cybersecurity, data analytics, and digital platforms continue to transform modern life, the need for rigorous and credible information systems research has become increasingly important.

However, publishing a strong information systems paper requires more than identifying an interesting technological problem. Authors must demonstrate why the problem matters, establish a clear connection with existing scholarship, select appropriate research methods, and provide evidence that supports their conclusions. When a study involves system development, algorithm design, software implementation, or technical experimentation, engineering rigor becomes particularly important.

For researchers preparing manuscripts for Crosslink Studies (CLS), these principles provide a valuable foundation for developing research that combines scientific credibility with practical relevance. CLS emphasizes open-access scholarship, interdisciplinary collaboration, and rigorous editorial evaluation. Its publishing environment provides an opportunity for researchers to communicate meaningful contributions across computer science, engineering, information systems, and related fields.

Understanding Engineering Rigor in Information Systems Research

Engineering rigor refers to the systematic application of appropriate technical principles, methods, testing procedures, and evaluation criteria to produce reliable and defensible research outcomes.

In information systems research, rigor may involve different approaches depending on the study’s objectives. A paper examining technology adoption may require carefully designed surveys and validated measurement instruments. A study developing a cybersecurity framework may require threat modeling, implementation details, and security testing. Research proposing a new information system may need architectural documentation, usability evaluation, performance benchmarks, or comparisons with existing solutions.

A rigorous manuscript typically demonstrates:

• A clearly defined research problem.
• A defensible theoretical or conceptual foundation.
• Appropriate research design and technical methods.
• Transparent data collection and analysis.
• Reproducible or independently assessable procedures.
• Conclusions proportionate to the available evidence.

Begin with a Clear Research Problem

A technically sophisticated study can still make a limited scholarly contribution if its research problem is poorly defined. Authors should begin by identifying a specific challenge that matters to researchers, practitioners, organizations, or society. A strong problem statement should establish three elements:

The practical or scientific problem: What difficulty, limitation, or unanswered question motivates the study?

The research gap: What remains insufficiently understood or inadequately addressed in existing literature?

The intended contribution: How will the study extend knowledge, improve a technical approach, or explain an important information systems phenomenon?

Authors should avoid presenting a research gap merely as the absence of studies in a particular country, industry, or application area. Contextual novelty can be valuable, but the manuscript must explain why that context provides meaningful theoretical, methodological, or practical insight.

Connect Technical Work with Theory

Information systems research often requires a connection between technological mechanisms and the human, organizational, or institutional environments in which technology operates. For empirical studies, theory can explain relationships among constructs, support hypothesis development, and clarify why particular outcomes are expected. For design-oriented research, established concepts and prior work can help justify design decisions and define the intended contribution of an artifact. Similarly, a study proposing a new digital platform should explain more than its software architecture. It should establish which requirements the design addresses, why the selected design principles are appropriate, and what the resulting artifact contributes to existing knowledge.

Theoretical grounding should inform the research rather than appear as an isolated literature review. Authors should demonstrate how prior scholarship shapes the research questions, methodological choices, interpretation of findings, and contribution.

Choose Methods That Match the Research Question

Methodological rigor begins with selecting an approach that can answer the question being investigated. Information systems research supports several methodological traditions, including quantitative analysis, qualitative inquiry, mixed methods, design science, case studies, and controlled technical experiments. No single method is universally superior. Its suitability depends on the research objective, available evidence, and claims the authors intend to make.

For example:

• Quantitative studies should justify variable selection, measurement, sampling, statistical procedures, and robustness checks.
• Qualitative studies should explain case selection, data collection, coding procedures, analytical interpretation, and strategies for establishing credibility.
• Design science studies should identify the problem, design objectives, artifact development process, and evaluation criteria.
• Technical experiments should specify experimental conditions, datasets, baselines, performance measures, and testing procedures.
• Mixed-method studies should explain how the different forms of evidence complement one another.

Demonstrate Technical Performance with Credible Evidence

When a manuscript proposes a new algorithm, software framework, information system, or engineering solution, its technical claims must be supported by suitable evaluation. A common weakness is presenting a proposed system’s features without demonstrating that it performs as intended. Describing an application as efficient, secure, scalable, or accurate does not establish those properties. Evaluation should be designed around the claims being made.

For a machine-learning study, relevant evidence might include appropriate baseline comparisons, precision and recall, computational cost, and performance on independent test data. For a network architecture, latency, throughput, reliability, and resource utilization may be more relevant. For a user-facing information system, usability testing and task-completion measures may be essential.

Authors should consider the following questions:

• Are the evaluation metrics appropriate for the research objective?
• Are the comparison methods relevant and fairly implemented?
• Are datasets and experimental conditions clearly documented?
• Are repeated experiments or uncertainty estimates needed?
• Do the results support the claimed improvement?
• Are potential weaknesses and trade-offs acknowledged?

Strengthen Reproducibility and Research Transparency

Reproducibility and transparency allow other researchers to evaluate, verify, and extend published findings. These principles are especially important when results depend on computational procedures, software implementations, or complex analytical pipelines. Authors should document their methods in enough detail to make the research independently assessable. Where appropriate and ethically permissible, supporting materials may include datasets, source code, configuration files, survey instruments, experimental protocols, and supplementary analyses.

Researchers should also describe relevant preprocessing steps, software versions, parameter settings, exclusion criteria, and evaluation procedures. Any restrictions on data or code access should be explained clearly.

Present Results Without Overstating Their Meaning

The results section should communicate findings clearly, while the discussion should explain their significance. Authors should distinguish observed results from interpretations, assumptions, and proposed applications. A statistically significant relationship does not automatically establish causality, and improved performance in one experimental setting does not guarantee superior performance in every real-world environment. Effective results reporting includes appropriate tables and figures, transparent comparisons, and explanations of unexpected findings. Where relevant, authors should report uncertainty, effect sizes, sensitivity analyses, or limitations affecting interpretation.

A useful discussion addresses three questions:

1. What do the results demonstrate?
2. How do they compare with previous research?
3. What are their theoretical, technical, or practical implications?

Make the Contribution Clear to Editors and Reviewers

A manuscript should communicate its contribution explicitly rather than expecting reviewers to infer it from technical complexity. Contributions may include a new theoretical explanation, a validated research model, an improved engineering method, a carefully evaluated system, or evidence that challenges existing assumptions. A study may offer more than one contribution, but each should be supported by the research.

Before submission, authors should verify that the introduction, methodology, results, and conclusion tell a consistent story. The abstract should accurately summarize the problem, approach, principal findings, and contribution.

Authors should also check that the manuscript fits the target journal’s aims and scope and follows its submission requirements. CLS provides information for authors and a peer-review process intended to assess manuscript suitability, research quality, and scholarly contribution. Reviewing the relevant journal guidelines before submission helps authors prepare a more appropriate manuscript.

Conclusion

Publishing information systems research with engineering rigor requires a balanced commitment to theory, technical quality, methodological transparency, and meaningful contribution. A sophisticated system or promising analytical result is valuable, but its scholarly significance depends on the strength of the problem formulation, the appropriateness of the methods, and the quality of the supporting evidence.

Researchers can strengthen their manuscripts by defining clear research questions, connecting technical work with established scholarship, evaluating proposed solutions systematically, documenting procedures transparently, and interpreting results responsibly. For Crosslink Studies, these principles align with the broader goal of supporting accessible, credible, and interdisciplinary research. By combining engineering discipline with thoughtful scholarly inquiry, authors can produce information systems research that is not only technically convincing but also reproducible, relevant, and capable of advancing knowledge across academic and professional communities.