Welcome to our annual programming series! In these posts, we’ll give you all the information you’ll need to propose programming for Sirens. We’ll have a post with tips, tricks, and frequently asked questions next week, and we’ll feature a post specific to each type of programming in the following weeks. On March 16, we’ll open our proposals system.
Let’s start at the beginning, shall we?
Programming, for Sirens, is the dozens of hours of papers, lectures, panels, workshops, roundtables, and afternoon classes that make up the heart of the conference. While a thousand conversations happen at Sirens every year, the true vanguards of those discussions are the brave and brilliant individuals who share their wisdom and expertise as part of our programming. See the archives to find out more about the kinds of topics and discussions that have been presented in the past.
So how does Sirens create its programming?
We don’t create the Sirens programming. You do! We don’t want Sirens to be limited by the interests, knowledge, and networking of our staff, so we invite our attendees — readers, scholars, librarians, authors, and more — to propose programming for our schedule. And each year, dozens of individuals do: they create, craft, propose, and present the lectures, papers, panels, workshops, roundtables, and afternoon classes that become the programming at Sirens.
A special note: We want our programming to represent a broad range of perspectives, experiences, and identities: readers, scholars, librarians, educators, publishing professionals, and authors, of course, but also individuals of different genders, sexualities, races, religions, and abilities. Similarly, we hope that, regardless of your vocation, your level of experience, or how many years you’ve attended Sirens, you’ll take a crack at sharing your thoughts and expertise as part of our programming. All voices matter at Sirens, including yours.
And how does Sirens choose its programming?
Each year, an independent vetting board—a diverse group of tremendous individuals who know and love Sirens—review the proposals for thoughtfulness, relevance, and inclusiveness, and then select which ones to include on that year’s programming schedule.
Thoughtfulness: This means the vetting board considers the research, logic, and sophistication of the arguments. Is the proposal well-conceived? Is the proposal well-argued? Is it interesting? Is it innovative?
Relevance: Is the topic relevant to Sirens’s overarching topic of gender and fantasy literature? The topic doesn’t need to specifically address the theme of any given year, and doesn’t have to be about gender and fantasy and literature (but if your proposal doesn’t address at least two of the three, you might want to consider how you can make your topic more relevant to the Sirens audience).
Inclusiveness: Sirens values diverse perspectives, experiences, and identities. Does your topic address an inclusive selection of literature? Do your co-presenters represent a variety of perspectives, experiences, and identities, whenever possible?
In crafting your presentation, please also consider the following:
Audience: You are likely to find your presentation audience composed of voracious, critical readers, as well as accomplished scholars, librarians, educators, authors, and publishing professionals. Further, Sirens attendees tend to be quite experienced in discussing women in fantasy literature, as well as related topics such as feminism, social sciences (and occasionally hard sciences), and writing. Please plan the sophistication and complexity of your proposal accordingly.
Repetition of Past Presentation Topics: The vetting board is familiar with programming presented at Sirens in the past, and duplicative topics are often considered less relevant. Please make sure that you have reviewed our archive page before deciding on your topic and that, if you intend to propose a similar topic, you highlight the innovation of your work in your proposal.
How does someone propose programming?
Sirens operates its own proposals system specifically for programming proposals. We’ll open this system on March 16 and close it May 15, which is this year’s deadline for proposals. After May 15, our vetting board goes to work.
Five things are needed for a proposal:
Personal information: Your name, contact information, and a third-person biography that we can use on our website and in our program book
A summary: 50–100 words about your topic and approach, which we’ll also publish on our website and in our program book (see last year’s summaries for examples)
An abstract: 300–500 words explaining your presentation and approach to the vetting board; this should be far more in depth and should demonstrate your research, analysis, and conclusion on the topic
Audiovisual requests: Information on your requested audiovisual equipment for your presentation, if any
Contact information for any co-presenters: Your co-presenters will then receive an email asking them to provide their personal information and, in the case of panels, a supplemental abstract of 300–500 words demonstrating the perspectives and expertise that they will bring to the panel
So let’s do this!
We know that the proposal process can be intimidating, especially for those new to Sirens. It takes a lot of courage to put your thoughts and analysis out there, first to a review board and then at Sirens itself. But each year, dozens of individuals screw their courage to the proverbial sticking place and, in doing so, make Sirens smarter, more thoughtful, more interesting, and just plain better.
We hope that that will include you this year!