What successful attendees do the day after the conference ends

FARE Conference 2017 closed its three-day programme in Dallas on 28 June, bringing together foodservice operators, suppliers and executives from restaurant, convenience, healthcare, education and recreation operations. Between keynotes, educational sessions, networking and supplier exhibits, attendees accumulated a large volume of useful material. The difference between a productive event and an expensive memory often lies in what happens once everyone leaves the venue.

For Australian delegates, following up from Dallas also means managing time zones and returning to a market with distinctive costs, regulations and operating conditions. A crowded notebook can look identical whether it came from Melbourne or Brisbane, yet the action it should trigger may differ. The strongest post-conference follow-up converts conference takeaways into a small set of relevant decisions, conversations and tests that can survive the flight home.

Turn conference energy into clear priorities

Successful attendees resist the urge to act on every idea they encountered. They review their notes and identify the two or three developments most relevant to their organisation. This might be a staffing model for a multi-site restaurant group, a purchasing strategy for aged care, or a way to improve grab-and-go sales at a convenience store. The objective is priority rather than volume.

A useful debrief asks four questions about each item: What was observed? Why does it matter locally? What could change? Who needs to be involved? These questions convert broad insights into practical action. They also help attendees separate a genuinely useful idea from a supplier promise, an interesting presentation and an operational problem that their business already knows how to solve.

Contacts are then prioritised around mutual intent. Notes should record the person’s role, the issue discussed and a possible next step, rather than only a name and organisation. That list can include a fringe but potentially useful lead, such as Bitcoin payment ideas, alongside more familiar workforce or menu innovations. An Australian “arvo debrief” can be informal, but every contact should still have a clear reason for future contact.

Capture details while they remain useful

The most valuable notes are created within 24 hours of the conference ending. Flight schedules and exhaustion can blur session details quickly, so attendees photograph permitted slides, review their calendar and write a brief voice memo while events are still fresh. They separate direct quotations from personal interpretations and flag any figure that needs verification before it reaches a business case.

Written notes also make contact follow-up more effective. A generic message saying “Great to meet you in Dallas” rarely prompts a response; a short reference to a shared operational problem does. For supplier or networking conversations, FARE’s advice on crafting a compelling elevator pitch can help attendees explain their need in a few clear sentences. Each message should contain one relevant point and one realistic request.

Every selected action is then transferred into a simple plan. It needs an owner, a deadline, a measure of success and a date for review. A menu idea might be tested in one Brisbane café for four weeks, while a procurement idea might require quotes from two suppliers. This structured handoff turns scattered conference notes into work that colleagues can understand, support and evaluate.

Compare passive attendance with active follow-up

Most conference days create plenty of activity, but activity alone does not guarantee progress. The useful distinction is between collecting information and deciding what happens next. A structured comparison shows how common reactions can be converted into stronger post-event habits.

Follow-up area Common conference-day reaction Day-after action Why it matters
Notes Save slides, photos and brochures Consolidate them into observations, implications and proposed actions Produces a brief people can actually use
Contacts Exchange cards and promises Send a personalised note with context and one clear next step Builds a relationship beyond the booth
Supplier discussions Collect promises and product sheets Set criteria, owners, costs and a decision date for any trial Converts interest into a measurable proposal
Ideas Record many possibilities Select one or two experiments tied to a service problem Limits distraction and supports learning
Timing Say “catch up soon” Book the review date before leaving the follow-up list Makes accountability visible

The pattern is simple: successful attendees add a decision, owner or timetable to what would otherwise remain passive. This does not mean every idea deserves implementation. It means each promising idea receives enough consideration to determine whether it should be tested, monitored or discarded.

A priority check keeps the plan manageable. Relevance to current operations, expected customer benefit, implementation effort and available evidence are useful filters. A high-impact idea with no owner or supporting data may need to wait. A smaller change with a clear operational owner may deliver faster value and build confidence for larger work.

Adapt conference learning for Australian operations

Australian implementation starts with local market conditions rather than copying a Dallas example verbatim. Operators should consider the Australian dollar, exchange-rate exposure on imported equipment and the effect of freight from major overseas suppliers. The food safety codes applied by state and territory governments also differ, so an idea adopted in Texas may require adjustment before it can be used in New South Wales, Victoria or Queensland.

Scale and geography require another layer of judgement. A concept tested in a high-volume Sydney or Melbourne venue may face different staffing, rent and demand conditions in regional Australia. Award structures, penalty rates, staff turnover and delivery distances can materially affect the business case. Operators in Brisbane and Sydney may share a time zone, while teams in Perth coordinate several hours earlier. Seasonal planning also differs because June is winter across much of southern Australia.

Communication style should be adapted without losing precision. Australians often use direct, conversational language in a team catch-up: “Let’s park that for now”, “send it through when you can” and “no worries” can all appear in an informal debrief. The accompanying email should still state the owner, deadline and requested decision. Local sounding does not need to mean vague. A clear action in plain English is more useful than industry jargon or an elaborate presentation that nobody revisits.

Build a repeatable day-after action plan

The day after the conference should have a defined rhythm. Successful attendees reserve time for it before checking every supplier email or reopening their inbox. That protected period allows them to process the strongest insights, communicate with relevant colleagues and arrange the first conversations. The routine works across segments because it focuses on decisions rather than the length of the conference programme.

The following habits produce the most consistent follow-up:

The next working day can then move from private notes to shared ownership. Operations managers can discuss the pilot during the morning handover, suppliers can receive the requested information, and executives can approve the decision criteria. This avoids the common pattern where an attendee returns with valuable insights but colleagues regard them as conference stories rather than business priorities.

Make the commitment now: reserve the debrief, appoint the action owners and register the team for the next FARE event. A planned follow-up turns an international conference into a practical operating plan rather than a memorable trip that ends when the final session does.