The Destinations International Business Operations Summit 2026 is scheduled for October 26–28 in Oklahoma City, Oklahoma, according to Destinations International’s official event listing.
The attendance decision should start with an operating problem, not the travel calendar. Use this guide to decide who to send, which questions to bring, and what your team should be able to do differently afterward.
Who should attend—and who can skip it?
The organizer’s 2026 summit description identifies professionals in finance, human resources, operations, and technology as the event’s audience. For a destination marketing organization (DMO), start by considering the person who owns the problem you want to solve.
A CEO does not need to attend simply because the event is on the industry calendar. A finance lead, operations director, or technology owner may be the better delegate when that person can ask detailed questions and carry a decision forward.
Match the delegate to the decision
| Role | Consider attending when | Bring this question |
|---|---|---|
| Finance leader | You need to compare budgeting, reporting, or purchasing approaches. | Which decision would better cost visibility help us make? |
| Human resources leader | You are reviewing staffing, role clarity, or team development. | Where are responsibilities unclear or work getting stuck? |
| Operations leader | You need to improve approvals, handoffs, or shared processes. | Which recurring delay should we address first? |
| Technology leader | You are assessing systems, integrations, or vendor requirements. | What must a new system connect to, and who will maintain it? |
| CEO or marketing leader | A business decision spans marketing, finance, staffing, and technology. | Who needs to agree before this change can move forward? |
For tourism operators and suppliers, make the attendance case around specific conversations. Identify the people you want to meet and confirm that a meeting is possible before treating the trip as a sales opportunity.
Investors should use the same test. A destination-industry event is not, by itself, a reason to expect investment opportunities. Attend only when the program and planned conversations support a defined research or relationship goal.
Consider skipping the trip if your only goal is a broad marketing overview, you cannot identify a relevant operating question, or nobody has time to use the findings afterward.
What should shape your agenda?
Use finance, human resources, operations, and technology as the first filter when reviewing the summit agenda. Then narrow your choices to the decisions your organization actually faces. The questions below are a planning lens, not a substitute for the organizer’s session schedule.
Where does budget ownership break down?
Bring a real purchasing or reporting problem. Perhaps marketing requests a new platform, finance needs a clearer business case, and operations will own the rollout. Ask how another organization assigns responsibility across those steps.
Write down what you need to learn before choosing a session. “Understand technology costs” is broad. “Decide who owns renewal reviews and how departments share costs” gives you a useful question to ask.
Which staffing or process problem needs attention?
Choose a recurring issue rather than a general interest in better teamwork. It might be a slow approval, an unclear role, or a task that depends on one person’s memory.
Ask peers to explain the process, not just the result. Who starts the work? Who can approve it? What happens when the owner is away? These details give your team something concrete to assess after the event.
What must change before you buy another system?
Prepare a short account of your current tools, their owners, and the work they support. If you are considering a replacement, list the functions you need and the connections it must preserve.
Keep the discussion grounded in implementation. Ask about staff time, training, data access, contract terms, and ongoing ownership. A feature that looks useful still needs someone to run it.
How should you evaluate speakers, exhibitors, and meetings?
Use the organizer’s 2026 summit page when checking speakers, session descriptions, and any exhibitor or partner information. Match each planned conversation to a question you need answered.
For speakers, look beyond the job title. Review whether the session description addresses your problem and whether the speaker’s role gives them relevant experience. Prepare a question that invites an example of a decision, process, or tradeoff.
If you are planning supplier meetings, confirm that the company is participating and arrange the conversation directly. Do not build a travel budget around a presumed exhibitor roster or an attendee list from another year.
Separate learning from purchasing. A useful first conversation can establish requirements, constraints, and next steps without becoming a commitment to buy. Ask what information the supplier would need to scope the work accurately.
Keep your meeting plan realistic. Leave room to record what you learned and decide whether a follow-up is worth scheduling. A full calendar is not the same as a productive trip.
Is the summit worth the time and travel cost?
It may be worth attending when the trip supports a decision your organization is ready to make. The case is weaker when the goal is simply to gather ideas with no owner, deadline, or route to action.
Build the budget from the actual registration terms and your own travel needs. Include transportation, lodging, meals not covered by registration, local travel, and staff time. Include preparation and follow-up time, not just the days away.
Then compare attendance with other ways to answer the same question. Could a direct peer conversation, vendor discussion, or internal working session resolve it? Choose the event when the program and planned meetings offer something those alternatives do not.
For example, a team reviewing a system purchase could use the trip to test its requirements with peers and suppliers. That is a clearer purpose than “learn about technology.” The expected output might be a revised requirements document—not an immediate purchase or a promised financial return.
Before booking, finish this sentence: “We are sending this person to help decide ___, and they will return with ___.” If the blanks remain vague, sharpen the case first.
What should destination marketers bring?
A CMO should bring questions that connect marketing work to the people, budgets, and systems behind it. Focus on the operating decisions you share with other departments rather than treating the event as a campaign workshop.
Start with measurement. Which results does your leadership team use to make decisions? Who owns the data? What can each report support—and what falls outside its scope? Percepture’s attribution and analytics services provide a related resource for this reporting workstream.
Next, map the handoffs between channels. Who approves the message, manages the assets, handles inquiries, and reports back to leadership? When planning work across channels, keep omnichannel marketing connected to those responsibilities rather than treating it as a list of platforms.
Bring a one-page brief with the decision, current constraint, departments involved, and information you still need. Leave sensitive contracts, personal data, and confidential budget details out of materials intended for casual peer conversations.
How do you turn the trip into a decision?
Before booking, assign one decision owner and agree on what the delegate should bring back. That could be a shortlist of requirements, a process comparison, or a recommendation to keep the current approach.
During the summit, separate observations from promises. Record who supplied the information, what conditions applied, and which details deserve a follow-up. Keep your own interpretation distinct from a speaker’s or supplier’s statement.
Afterward, give the team a short decision note rather than a folder of slides. Explain the original question, the useful findings, the remaining gaps, and the proposed next action. Identify who owns that action and when the team will review it.
Keeping the current system can be a valid outcome. So can narrowing the scope of a proposed change. Judge the trip by whether it helps your team make a clearer operating decision—not by the number of sessions attended or contacts collected.
About Bob Generale
Bob Generale is President of Percepture.
