Skip to content

Professional Development

Turn your experience into a conference proposal for a new industry

Experience from another field can be useful to conference delegates when you connect it to a problem they recognize. Build a proposal around audience needs, credible evidence, and the organizer's actual criteria.

Two women discuss a materials sample in an empty auditorium near a stage.

You have solved a difficult problem at work and notice a conference in another industry discussing something similar. Your experience might help its audience. The challenge is explaining that connection without claiming expertise you have not earned.

Start with the attendees’ work. A proposal earns consideration by showing what they will learn, why you can teach it, and how the session fits the event. Your career story can provide evidence, but it needs an audience-facing purpose.

Check whether the invitation includes you

Read the current call for proposals and its submission rules before developing a full talk. Check eligible speakers, topics, audience level, session length, deadlines, required materials, and attendance arrangements. Some events welcome practitioners from many settings; others require a specific affiliation, product experience, or technical contribution.

PyCon US announced its 2027 call on November 17, 2026, for its in-person conference in Long Beach, California. The organizers invite proposals relevant to Python from speakers across experience levels. They list December 19, 2026, as the submission deadline. Check the official proposal guidelines for any updates and allow time to submit before the cutoff.

Other calls illustrate boundaries. NAB’s September 2026 announcement for its 2027 Broadcast Engineering and IT Conference listed defined technical focus areas and excluded proposals promoting company products or services. Its stated October deadline has passed. Use such criteria to understand fit, rather than assuming a general leadership talk belongs in a technical program.

Translate the problem, then test the connection

Write one sentence about a problem the target audience recognizes. Then write one about what your experience can contribute. If the connection depends on replacing every industry-specific word while ignoring different constraints, the proposal needs more work.

Imagine a warehouse operations analyst who built a small Python tool to check inconsistent supplier files. She wants to speak to developers rather than logistics managers. “Our warehouse transformation” emphasizes her organization. “Check inconsistent input files before they disrupt a daily workflow” identifies a problem that another audience might recognize.

She should still establish technical relevance: what the tool checked, how failures were handled, and which decisions remained with people. She can explain warehouse constraints without implying that a method tested there meets the requirements of a hospital, bank, or other unfamiliar setting.

Look at previous programs and the current tracks. Ask one person familiar with the target industry whether your proposed problem and vocabulary make sense. Ask what would be missing for that audience, not whether the idea sounds impressive. Use their feedback to revise the proposal before submitting it to the organizers.

Offer a session the committee can evaluate

Blackbaud’s January 2026 guidance for bbcon applicants asked speakers to identify audience expertise, explain relevance, and specify learning objectives. That event’s application cycle is over, but the organizer’s explanation offers a useful test: what could participants do afterward that they could not do before?

For the analyst’s session, possible outcomes are identifying common input inconsistencies, choosing checks before processing, and designing a useful failure message. These are concrete enough to shape an outline. They also expose missing content: if she cannot demonstrate a useful failure message, she should revise the promise or develop that part of the session.

Draft an abstract around the audience’s problem, your approach, the evidence you will show, and the takeaways. Include enough detail for reviewers to judge substance. Describe whether the session is a case study, demonstration, discussion, or workshop, and make its scope plausible within the allotted time.

Keep claims proportional to the evidence. Explain what you directly did and what collaborators contributed. If you measured results, describe the comparison and limitations accurately. An unsuccessful attempt and what changed can be useful material; there is no need to invent a dramatic percentage improvement.

Check permission and commitment before submitting

Confirm that you can share the underlying work, including screenshots, code, client references, and results. Remove confidential details and obtain any required organizational permission. Agree on contributions and attendance with a proposed co-presenter. Check recording terms, travel responsibilities, accessibility arrangements, and rules on writing assistance, including AI tools.

Submit in the required format, then retain a copy and the notification date. If the proposal is declined, ask for feedback where offered and consider another suitable event or format. A well-developed proposal gives organizers something clear to assess. Selection still depends on their program, available places, and judgment.

More to read

Browse insights