FACULTY DEVELOPMENT DIVISION CALL FOR PAPERS
Please note that we would like to encourage anyone who has questions or concerns about submitting to this call to contact Homero Murzi, program chair (hmurzi@vt.edu) or Michelle Soledad, program chair-elect (soledadmm@vt.edu).
Summary Points from this Call for Papers:
● The Faculty Development Division (FDD) encourages submissions related to faculty and faculty development.
● The type of paper
MUST be listed in the first sentence of your abstract. We accept multiple types of papers including: Work in Progress Papers, Lessons Learned Papers (4-page limit each), Evidence-based Practice Papers, Research Papers, Theory Papers, and Panel Papers (12-page limit each). See more details
here.
● The preferred presentation style
MUST be listed in the last line of your abstract. It is expected that these papers will catalyze engagement with our community, hence, we are encouraging authors to consider the format of the paper presentation early in the creation process. Multiple presentation suggestions are listed in the Call. See more details
here.
● The FDD is also looking for
Workshops and
Special Sessions. To submit a proposal for a workshop or special session, email the FDD Program Chair (
hmurzi@vt.edu). Details on Workshop and Special Session proposals can be found
here.
The Faculty Development Division (FDD) seeks Paper, Special Session, and Workshop proposals on topics related to the FDD’s primary objectives. These objectives are: Laying a foundation for increased engagement and advancement as a community of practice and scholarship; Aiding in the research-to-practice cycle through faculty development; Furthering faculty development community discussion and plans toward addressing the community’s emergent interests; Sharing knowledge relevant to our professions as faculty developers and faculty development programs; and Generating ideas for collaborations in meeting challenges, interests, and goals.
“Faculty Development” is a common term within academia to describe professions, practices, and initiatives which are intended to foster the professional learning and growth of educators. Our division subscribes to this view and wants to foster a community of all educators who influence the learning of engineers along with those who have formal faculty appointments. We also honor the breadth of professions and roles that contribute formally and informally to the faculty development of engineering educators: administrators, educators, researchers, mentors, peers, as well as those with explicit roles as faculty developers. We would like to highlight that faculty development is generally thought of as teaching development, but can also include research, service, leadership, or equity, diversity, and inclusion development as well. The FDD encourages submissions around all aspects of faculty development.
Presentation Formats
One of the goals of the FDD is to encourage innovative dissemination of research and practice through non-traditional presentations at ASEE. We encourage all authors to consider including different engagement strategies such as interactive discussions and live audience engagement (e.g., using polls) in their ASEE presentations, and to keep that goal in mind when writing your paper. To further this purpose, we would like authors to think about how they will present their paper while writing their paper. We are requiring authors to identify their preferred presentation method in the last line of their abstract. This will help the program chair to arrange papers into sessions.
Some suggested presentation methods include:
● Round table discussion: Presenters present to those seated at their table, leaving ample time for discussion among those at the table.
● Poster: Presenters will provide an overview of their paper, using a poster to foster dialogue.
● Mini-demonstration: Using your presentation time to have an active demonstration of the key elements from your paper.
● Traditional lecture: You have 12–20 minutes to present and make the audience want to read your paper.
● Other (please specify in your abstract): Be creative! We’re open to other strategies to present your work. Just tell us a little bit about it. Please feel free to consult the ASEE Presentation Playbook for more ideas!
We also encourage you to collaborate with colleagues to create panels or special sessions that highlight research or practice around faculty and faculty development. If you are interested in a non-traditional session, please contact the FDD Program Chair, Homero Murzi (
hmurzi@vt.edu).
Submission categories
There are three categories of submissions: Paper, Special Session, and Workshop.
1. Papers: Manuscripts that further the FDD objectives stated above. There are six types of papers that will be considered. The type of paper should be included in the first line of your abstract. Minor allowances may be made at the Program Chair’s discretion, but excessively long papers may be rejected without review.
o Work in Progress (WIP) Paper: These short papers (4 page limit) are on studies at an early to intermediate stage for which authors are seeking feedback from the community. WIPs will be presented as a poster or a lightning talk. Please specify your preference in the last line of your abstract.
o Lessons Learned Paper: These short papers (4 page limit) should highlight practices that faculty developers would like to share with their colleagues. They should be short summaries of the practice and the lessons learned by the faculty developers. Lessons Learned papers will be presented as a poster or a lightning talk. Please specify your preference in the last line of your abstract.
o Research Paper: Research studies should provide a complete description of a research study including motivation and background, purpose, relevant prior work, theoretical framework(s), methods, results, and implications (12 page limit).
▪ Research paper topics may include but are not limited to: faculty-centered studies that help explore the faculty experience; faculty perceptions of teaching, research, or service; studies about faculty developers and their experience.
o Theory Paper: Review or theory-focused paper; must include relevant prior work and literature citations (12 page limit).
▪ Theory paper topics may include but are not limited to: theoretical models for change, faculty development, educational development; literature reviews and exploratory papers that bring forward or synthesize a new idea that is relevant to the faculty or faculty development profession and/or practice.
o Evidence-Based Practice Paper: Instruction-focused paper about a faculty development project and its implications for other engineering faculty developers and faculty. Consider including relevant prior work and literature citations, an outline of the practice, implementation recommendations, and any assessment results (12 page limit).
▪ Evidence-Based Practice Paper topics may include but are not limited to: Practice techniques across a variety of genres - workshop, consultation, facilitation, learning community, any intervention; highlighting effective research-to-practice translations; center models, strategies, and organizational problem solving; the use of university data or local research in faculty development.
o Panel Papers: In an effort to have more innovative presentations at ASEE, we are encouraging informal panel sessions. To do this, you will need to seek out colleagues (use of the Engr-POD listserv is encouraged) who are willing to write a paper around a panel topic of your choosing. A panel may focus on similar practice or opinion (based on research) papers. Four to six authors will need to write independent papers, which will be peer reviewed. At the session, all authors will serve on a panel during the presentation time in place of traditional paper presentations (12 page limit). You will need to identify the panel title in the first sentence of your abstract. You are also encouraged to provide a common panel summary paragraph in the introduction of your paper to help readers and reviewers contextualize the papers as part of a panel session.
▪ Panel paper topics may include but are not limited to: Faculty Development Center models; Administrative concerns around faculty development; Structuring Communities of Practice; Strategies for encouraging faculty participation in faculty development.
The type of paper (WIP, Lessons Learned, Research, Theory, Evidence-Based Practice, or Panel) MUST be identified in the first sentence of the abstract. All Papers will be “publish-to-present,” meaning:
o All abstracts and papers must be submitted through ASEE’s System.
o A favorable peer-review of a submitted abstract will lead to an invitation to submit a short/full paper. A favorable peer review of a submitted paper will lead to acceptance.
o Only accepted papers will be considered for inclusion to be presented at the Conference.
o Presentation of the paper at the Conference is required for publication of the paper in the Conference proceedings. Formats for presentations are encouraged to be interactive. Presenters are encouraged to practice the strategies they are presenting about to engage the audience.
o Authors of accepted Research, Theory, or Evidence-Based Practice Papers must identify their preferred presentation method in the last line of their abstract.
o All WIP and Lesson Learned papers will be assigned to a poster session or lightning talk to facilitate discussions. Authors should note their preference in the last line of the paper abstract. FDD Poster Sessions may or may not be at the same time as other poster sessions during the conference.
-
Special Sessions: 90-minute sessions with non-traditional formats occurring during the regular Conference program that explore a topic in depth. Special Sessions should have explicitly stated learning goals that cannot be met in a traditional paper presentation. Special sessions are 90 minutes in length. They do not require a paper submission. A limited number of FDD Special Sessions will be accepted for the Conference program.
-
Workshops: 2-hour or 4-hour sessions on the Wednesday of the Conference. Workshops provide attendees an opportunity to learn about a topic in depth and ways to apply the knowledge to their own settings.
Guidelines for Submissions
Considerations for abstracts
Abstracts and Papers should follow the ASEE Abstract Format guidelines (
https://www.asee.org/events/Conferences-and-Meetings/2023-Annual-Conference/Paper-Management/2023-Authors). The abstract should contain sufficient information to enable reviewers to determine its suitability for presentation in the FDD. FDD uses a blind review process when reviewing abstracts and papers, and it is the authors’ responsibility to ensure that the requirements for blind review are met. Authors’ names and institutions should not be included in the text, file name, or document properties of an abstract or paper submitted for review.
There are six types of paper submissions: Work in Progress (WIP), Lessons Learned, Research, Theory, Evidence-Based Practice, or Panel. YOU MUST INCLUDE THE TYPE OF PAPER YOU ARE PROPOSING IN THE FIRST SENTENCE OF YOUR ABSTRACT. (For example, “This research paper describes the study of…” or “This work in progress describes a proposal for studying...”). As noted above, FDD also requires authors to identify their preferred presentation method in the last line of their abstract. For panel papers, you must also include the panel topic for grouping by the program chair.
1) Work in Progress (WIP): These short papers (4 page limit) are on studies that are at an early to intermediate stage for which authors are seeking feedback from the community. WIP abstracts should address the motivation and background of the work, methods, results (or anticipated results), and significance. WIPs MUST also include the abbreviation “WIP: ” at the beginning of the title.
2) Lessons Learned: These short papers (4 page limit) should highlight practices that faculty developers would like to share with their colleagues. They should be short summaries of the practice and the lessons learned by the faculty developers. Lessons Learned MUST also include the words “Lessons Learned” at the beginning of the title.
3) Research: New findings, situated in the context of prior findings and models, including motivation and background of the work, methods, results, and implications of the work and/or future directions for research (12 page limit).
4) Theory: Reviews, meta-analyses or other theory-focused work, situated in the context of previous literature to reveal relationships, patterns or models, or extend existing theories. Theory abstracts should address the motivation and background of the work, theoretical framework(s) and sources, and significance (12 page limit).
5) Evidence-based Practice: Analysis of one or more engineering education practices, including teaching approaches, uses of instructional technologies, institutional strategies to support student success, etc.), including design rationale, assessment methods, evidence of effectiveness and/or achievement of desired outcomes (12 page limit).
6) Panel: Opinion, example practice, model or other individual topic that will be grouped by topic with other submissions self-identified for panel presentation (12 page limit).
The criteria for abstracts listed above serve as the review criteria within each category. Literature citations should not be included in the abstract. Authors’ names or institution names should not be included in the abstract, filename, or document properties. It is the author’s responsibility to ensure that the requirements for blind review are met.
Considerations for paper drafts
Authors of accepted abstracts will be required to submit a full paper manuscript that should meet ASEE Paper Format guidelines (
https://www.asee.org/events/Conferences-and-Meetings/2023-Annual-Conference/Paper-Management/2023-Authors) Papers will be evaluated using criteria within each type as listed above, and the general criteria in the list below. Papers that fail to meet all of the criteria may still be considered acceptable based on potential to further the FDD objectives. General evaluation criteria for all paper types:
● The submission is complete. Authors should not expect to make substantial changes in a manuscript following its acceptance.
● The submission is likely to interest a broad group of engineering education faculty development researchers and/or practitioners or has broad implications for the engineering education faculty development community.
● The submission builds upon relevant references and bodies of knowledge.
● The findings or ideas presented are generalizable or transferable to other settings.
● The submission is clear and coherent.
● The submission is original and innovative.
● The submission advances engineering education research and/or practice.
WIPs and Lessons Learned short papers are expected to be no more than 4 pages in length and full papers are expected to be no more than 12 pages in length.
Special Session Proposals
Proposals for Special Sessions submitted through the FDD should be sent directly to the FDD Program Chair (
hmurzi@vt.edu) and
not through the ASEE system.
The deadline for submitting special session proposals is going to be in December. Proposals should include the following information:
● A description of the session, including its purpose, format, learning goals, content, and activities.
● An explanation of why the non-traditional format is needed to accomplish the learning goals.
● A list of presenters/facilitators and their contact information, along with a brief justification for their ability to successfully accomplish the stated goals.
Workshop Proposals
Proposals for Workshops submitted through the FDD should be sent directly to the FDD Program Chair (
hmurzi@vt.edu) and
not through the ASEE system.
The deadline for submitting workshop proposals is going to be in December. Proposals will be reviewed and selected by FDD to be forwarded for further consideration by ASEE, which makes the final decision. Acceptance of a Workshop proposal by FDD does not guarantee that it will appear in the final program. Proposals should include the following information:
● A description of the session, including its purpose, format, learning goals, content, and activities.
● A schedule.
● A list of presenters/facilitators and their contact information, along with a brief justification for their ability to successfully accomplish the stated goals.
If you would like a 4-hour workshop spanning both session times, you must also include an explicit justification for why the longer session is necessary.
If the workshop is approved by FDD reviewers, it is then submitted to ASEE by the Program Chair. The submission to ASEE will include additional information such as estimated attendance, estimated ticket cost and responsible party to subsidize the expense if tickets don’t cover the entire cost of the event (ASEE charges for the room, audio-visual, etc.), expected food and beverage requests, and audio-visual needs.
For more information, please contact the Program Chair or Program Chair-elect:
Homero Murzi, Ph.D.
Virginia Tech, Department of Engineering Education
FDD Program Chair 2022-2023
Michelle Soledad, Ph.D.
Virginia Tech, Department of Engineering Education
FDD Program Chair-elect
Download PDF
Back
