Written for non-technical audiences of practitioners and of academicians, the Journal invites manuscripts with a strong applied orientation in topics such as strategic importance of information systems; information systems planning and policy; systems development alternatives, methods and tools; end-user systems development and management; data base design and administration; network and telecommunications design and management; role and effectiveness of the information executive; and behavioral and human resources aspects of information systems.
Because of the two audiences served by the Journal, (practitioners and academicians) special formats for manuscript publishing were adopted specifically for articles, short studies and case studies.
Articles *
Empirical papers presenting research results directly relevant to
the information systems practice. Emphasis should be on long-
term/managerial knowledge (rather than short-term/technology
issues) and on creative thinking (not just replication of
previous studies with minute variations), presented in a language
as practitioner oriented as possible but supported by empirical
evidence.
Recommended format (up to 25 pages):
1. What is the problem? Why is it relevant? (1 to 2 pages)
2. What is the argument (hypothesis)? Why is it important? What
results of your study support the argument? (8 to 10 pages)
3. What are the conclusions? How do they contribute to solving
the problem? (2 to 3 pages)
4. References: 15 to 20 references are normally sufficient, but
in any case no more than two pages.
5. Technical appendix: summary of the research question,
methodology and results. (5 to 10 pages)
Short Studies *
Exploratory studies and conceptual papers presenting results
and/or arguments of immediate applicability to information
systems practice. Emphasis on testing of existing concepts,
frameworks and methodologies, and on development and testing of
methodologies, procedures and techniques to support the
managerial use of information technology.
Recommended format (up to 10 pages):
1. What is the problem? Why is it relevant? (1 to 2 pages)
2. What is the argument? Why is it important? What results of
your study support the argument? (4 to 6 pages)
3. What are the conclusions? How do they contribute to solving
the problem? (1 to 2 pages)
4. References: 5 to 10 references are normally sufficient, but in
any case no more than one page.
Case Studies *
Descriptions of successful applications of concepts,
methodologies, etc., to improve information systems practice.
Emphasis on identification of concepts, frameworks and
methodologies that improved information systems practice, and on
the identification of factors that contributed to its successful
application.
Recommended format (up to 10 pages):
1. What is the problem? Why is it relevant? (1 to 2 pages)
2. What concept, etc., was applied? Why is it important? How
was it done? What factors may have led to success? (4 to 6
pages)
3. What was learned from the case? How can this knowledge be
transferred to other circumstances? (1 to 2 pages)
4. References: 5 to 10 references are normally sufficient, but
in any case no more than one page.
* Contributors should note
In all three categories the emphasis is on their unique
contribution to the solution (section 2) of an information
systems problem (section 1).
Articles have the content of a traditional academic manuscript (introduction, research question, methodology, results and conclusion), but presented in a practitioner-oriented format.
Footnotes are extremely discouraged. Either the subject of the footnote is important enough to be included in the regular text, or it should not be included at all.
Manuscript submission
Four copies of the manuscript should be submitted to:
Prof. Albert L. Lederer
Senior Editor
JOURNAL OF INFORMATION TECHNOLOGY MANAGEMENT
425C Business and Economics Building
Decision Sciences and Information Systems
University of Kentucky
Lexington, KY 40506-0034
(He can be reached via e-mail at lederer@ukcc.uky.edu).
Please include a cover letter requesting that the paper be considered for publication in the JITM, stating also that the manuscript has neither been published nor is under review elsewhere.
A final version of the accepted manuscript should be provided by the author(s) in both diskette (WordPerfect 5.0 and up) and printed formats. The graphs and figures should be in a WordPerfect compatible format.
Review Process
All manuscripts are screened by the Senior Editor, reviewed by at
least two Editorial Review Board members and receive a
recommendation from the Associate Editor on publication,
revision, development or rejection.
The Senior Editor will make the final decision in regard to the manuscripts based on the reviews and recommendations, and will communicate the decision to the author(s). The Associate Editors will see that manuscripts accepted for publication conform to the Journal style and format, and to the recommendations for revisions, if any.
Manuscripts conditionally accepted for development will receive special attention from the Editors and from the Editorial Review Board. These manuscripts have the potential to be publishable but are not yet at a level compatible with standards of the Journal. The Senior Editor, together with selected members of the Editorial Review Board, will work with the author(s), if the author(s) so desire, to make the document publishable. All members of the Editorial Board have made a commitment, and welcome the opportunity to participate in this special manuscript development process, whenever necessary.
The entire review process takes approximately three months to complete, from the time the article is initially submitted to the time it goes to the publisher.
References
The JOURNAL OF INFORMATION TECHNOLOGY MANAGEMENT uses the
following style for references:
1. References are numbered based on the alphabetical order of
author(s) or editor(s) names, or the title of the work for items
with no author's name.
2. Citations in the body of articles, short studies and case
studies, are made to the number of the reference, in
brackets.
Mason [7] proposed that ...
Adapted from Swanson [17, pp.363-364].
3. Entries in the reference list are made:
a. Books and working papers: author(s) name(s) (last name and
first initial), title (underlined), number (if working paper),
publisher (or school), city, state, year.
[4] Davis, G. and Olson, M., Management Information Systems,
McGraw-Hill, New York, 1985.
b. Periodicals: author(s) name(s), title (in quotes), periodical
(underlined), volume, number, date, pages.
[10] Etzioni, A. "Mixed-Scanning: A 'Third Approach' to
Decision-Making," Public Administration Review, Volume 27,
Number 2, 1967, pp.385-392.
c. Proceedings: author(s) name(s), title (in quotes), name of
conference proceeding (underlined), city, state, month and dates,
year, pages.
[11] Hamilton, S. and Ives, B. "Communication of MIS Research:
An Analysis of Journal Stratification," Proceedings of the
First International Conference on Information Systems,
Philadelphia, Pennsylvania, December 8-10, 1980, pp.220-
232.
Copyright
Articles, short studies and case studies accepted for publication
in the JOURNAL OF INFORMATION TECHNOLOGY MANAGEMENT are
copyrighted by Maximilian Press.