The IASSIST 2017 Ignite Sessions and Five-Minute Data Stories
The IASSIST 2017 conference, held at the University of Kansas in Lawrence from 23 to 26 May, explored “Data in the Middle: The Common Language of Research”. Within that wider programme, the Ignite sessions offered a brisk alternative to conventional conference presentations. Speakers had roughly five minutes to communicate a research idea, a data problem, a discovery, or a practical lesson before the audience moved to the next story.
The format placed unusual pressure on selection and structure. A presenter could not rely on a long methods section, a sequence of dense charts, or a detailed literature review. The strongest contributions needed a clear point, carefully chosen evidence, and a memorable explanation of why the data mattered to researchers, institutions, or communities.
For an archived conference website, the Ignite material is valuable because it captures more than a list of talks. It shows how data professionals were thinking about communication in 2017, when big data, machine learning, digital agriculture, and global food security were becoming increasingly connected. The sessions sit within a programme concerned with data as a shared language across disciplines.
That idea remains relevant for Australian universities, government departments, libraries, and research organisations. A data specialist in Canberra may need to explain a project to policymakers, while a digital agriculture team in regional New South Wales may be speaking to growers who want practical results rather than technical terminology. Five-minute storytelling provides a useful model for making complex evidence understandable without stripping away its meaning.
What Made The Ignite Format Distinct
Ignite presentations are built around constraint. Speakers generally work with a tightly controlled time limit and a rapid sequence of slides, often advancing automatically. The structure prevents a presentation from expanding into a conventional lecture and encourages the speaker to decide what the audience must remember.
This produces a different kind of preparation. Instead of asking how much information can fit into a session, the presenter asks which single argument deserves attention. A useful story might focus on an unexpected pattern in a dataset, a barrier to data sharing, a failed assumption, or the human consequence of a technical decision. Supporting details remain important, but they serve the central message.
The format also changes the relationship between visual material and speech. Slides need to be legible almost immediately, with charts simplified enough to understand at a glance. A photograph, map, short quotation, or single number can carry more weight than a crowded dashboard. The speaker supplies context, while the screen creates rhythm and reinforces the progression of the story.
For an audience, this creates variety. A session can move rapidly between disciplines, institutions, and research problems. That pace may feel demanding, yet it encourages active listening. Each presentation becomes a compact case study in how people use, interpret, preserve, or explain data.
Building A Story From Evidence
A successful five-minute data story usually has a recognisable arc. It begins with a problem or tension, introduces the evidence, shows what changed or was discovered, and finishes with a consequence. This does not mean forcing every project into a dramatic narrative. It means giving the audience a logical path through unfamiliar material.
The opening needs to establish relevance quickly. “Our archive contains 40 years of records” is a fact, but “Researchers could not compare 40 years of records because the same place had three different names” creates a problem that listeners can understand. Specificity gives data a human scale. It also helps audiences see why a technical issue deserves attention.
The middle of the presentation should contain a small number of well-chosen observations. A single graph with a strong trend may be more persuasive than six charts with weak connections. If uncertainty, missing values, or bias affect the interpretation, those limits should be stated clearly. Concision does not justify oversimplification; it requires disciplined explanation.
The final moments should answer the practical question, “What follows from this?” The answer may involve a new research direction, a policy decision, a better metadata standard, or a warning about misuse. A presentation about deep learning, for example, becomes more useful when it explains how model performance affects real research practice, rather than treating accuracy as the only measure of success.
Research Themes Behind The Stories
The conference programme connected Ignite-style communication with several major areas of data-intensive research. Big data raised questions about scale, storage, discoverability, and responsible reuse. Deep learning brought attention to automated classification and prediction, while also highlighting the need for transparent training data and careful validation.
Digital agriculture added a strong applied dimension. Sensors, satellite imagery, soil measurements, weather records, and farm management systems can create valuable evidence about crop performance and resource use. Yet a technically impressive system must still work in local conditions, fit existing routines, and produce information that farmers can trust. The best short presentations would therefore connect infrastructure with decisions made in the field.
Global food security provided another example of why data needs a common language. Food production, climate, trade, health, and population research use different methods and vocabularies. A concise data story can reveal how these areas intersect, but it must avoid implying that one dataset can solve a complex social problem by itself.
These themes also invite discussion of stewardship. Researchers need to know who collected the data, which populations may be represented poorly, what permissions apply, and how future users will interpret the material. In Australia, this includes attention to Indigenous data sovereignty and the rights of Aboriginal and Torres Strait Islander communities to govern how data about them is collected, accessed, and used.
Why The Format Matters In Australia
Australian research communication often crosses large geographic and institutional distances. A project team may include specialists in Melbourne, a field station near Dubbo, a policy unit in Canberra, and community partners in northern Queensland. A short, coherent explanation can help people with different roles understand the same evidence before they move into detailed discussion.
The local research market also places pressure on data services. Universities and publicly funded institutes increasingly need outputs that are findable, reusable, and supported by reliable metadata. National infrastructure such as the Australian Research Data Commons has helped make data management a visible part of research practice, while funding and assessment environments encourage researchers to demonstrate broader value.
Legal and ethical settings add another layer. Australian projects may need to consider the Privacy Act 1988, institutional ethics requirements, contractual restrictions, and specific community governance expectations. A five-minute presentation cannot explain every obligation, but it can make responsible handling part of the story instead of treating compliance as an afterthought.
Everyday communication habits matter as well. Australian audiences often appreciate a direct explanation, practical examples, and a clear sense of what action is required. A presentation aimed at a Sydney policy team may need to land during a busy working day; a presentation for agricultural researchers may need to respect seasonal pressures and regional connectivity. Concise storytelling is useful because it fits the way many professional audiences consume information: quickly first, then in greater depth when the issue proves relevant.
An Archive Of Practice And Possibility
The IASSIST archive places the Ignite sessions within a broader event environment that included plenaries, workshops, practical attendee information, and an exhibit hall. That setting matters because data communication is shaped by tools as well as ideas. Repository platforms, visualisation software, metadata services, and research support systems all influence what a presenter can show and what an audience can understand.
Readers exploring the conference materials can also see how the exhibition connected data scientists with services designed to support their work. The archived exhibit hall resources help place the short talks within a professional ecosystem of platforms, vendors, libraries, and infrastructure providers. A five-minute story may begin with a research challenge, but its solution can depend on preservation, access, computing, or visualisation services.
The format is especially useful when comparing different forms of conference communication. A poster allows people to pause and inspect detail; a conventional talk gives the speaker time to develop a method; an Ignite presentation creates momentum and prioritises recall. None is universally better. Each serves a different purpose and asks the researcher to make different choices about evidence.
| Presentation style | Main strength | Typical limitation | Best use |
|---|---|---|---|
| Ignite presentation | Clear, memorable central message | Little time for technical detail | Introducing an idea, result, or data challenge |
| Conventional conference talk | Space for methods and interpretation | Audience attention can decline | Explaining a complete research project |
| Academic poster | Self-paced visual detail | Presenter may not be available throughout | Displaying findings for informal discussion |
| Demonstration | Shows a tool or workflow in action | Can depend on technology working well | Explaining platforms, software, or services |
| Panel discussion | Brings several perspectives together | Individual arguments may remain brief | Exploring policy, ethics, or shared problems |
Practical Principles For A Strong Data Story
Preparing an Ignite presentation requires more than shortening a longer talk. A speaker needs to rebuild the material around one promise to the audience. The promise might be that listeners will understand why a dataset was difficult to reuse, how a model changed a decision, or why a small metadata improvement produced a large research benefit.
Visual design should support that promise. Large type, restrained colour, meaningful labels, and one idea per slide make rapid presentations easier to follow. A chart should show the comparison that matters, rather than every available variable. When a photograph or quotation is used, it should contribute evidence or emotion rather than function as decoration.
The following principles help keep a five-minute presentation focused:
- Choose one central claim and remove material that does not strengthen it.
- Open with a concrete problem, observation, or consequence rather than background history.
- Use a small number of readable visuals with labels that make sense without specialist knowledge.
- Explain uncertainty, missing data, and ethical limits in plain language.
- Rehearse with automatic slide timing and leave enough space for the final message.
- End by stating what the audience should remember, reconsider, or do next.
The enduring value of the IASSIST 2017 Ignite sessions lies in their treatment of data communication as a research skill. A dataset becomes useful when people can interpret it, question it, and connect it to a decision. Five minutes is a severe limit, yet it can reveal whether a project has a clear purpose and whether its evidence can travel across disciplinary boundaries.
At the Conference
What attendees experienced in Lawrence
Plenary Sessions
Keynotes from Daniel Reed on data, technology, and culture, and Jennifer Clarke on digital agriculture and the Midwest Big Data Hub.
Workshops
Full-day technical workshops on Tuesday, May 23. Morning sessions ran 9:00–12:00 and afternoon sessions 13:00–16:00. Laptops were required.
Social Events
An opening reception at The Oread, a banquet, and an optional post-conference tour of Kansas City including Crescent Moon Winery.
Venue & Accommodations
Where the conference took place
Kansas Union
University of Kansas campus, Lawrence. Main conference venue with check-in on the 4th and 5th floor lobbies.
The Oread
1200 Oread Avenue, Lawrence. Hosted the opening reception and offered a room block for attendees.
The Eldridge
701 Massachusetts Street, Lawrence. A partner hotel with a reserved room block for conference guests.
Springhill & TownePlace Suites
Marriott properties in Lawrence with room blocks reserved under the "KU IASSIST Conference" name.
Program Highlights
Sessions and activities
Getting Here
Lawrence, Kansas
Kansas Union · University of Kansas
1301 Jayhawk Blvd, Lawrence, KS 66045
Kansas City International Airport (MCI) is approximately 50 minutes by car. Lawrence Transit Routes 10 and 11 served the area ($1 exact change).
Plan Your Stay
Accommodation options that were available
The Eldridge
701 Massachusetts Street, Lawrence, KS 66044. Room block now closed.
The Oread
1200 Oread Avenue, Lawrence, KS 66044. Room block now closed.
Springhill Suites
Marriott property. Room block reserved under "KU IASSIST Conference."
TownePlace Suites
Marriott property. Room block reserved under "KU IASSIST Conference."