Making the Case for a Dedicated Innovation Team

Innovation can look accidental in foodservice. A supplier suggests a faster preparation method, a customer requests a lighter meal, or a store manager adapts a service model after watching the queue. FARE Conference 2017 in Dallas, Texas, held from 26 to 28 June, gathered operators, suppliers, executives and specialists from restaurant, convenience, healthcare, education and recreation. Educational sessions, keynote perspectives and supplier exhibits created a setting for practical questions about moving good ideas into daily operations.

Many businesses already innovate constantly. They adjust menus around seasonal supply, introduce delivery channels, respond to staffing shortages and redesign loyalty offers. What often remains missing is a consistent mechanism for deciding which changes deserve investment and which should be abandoned. That distinction matters as Australian operators face skilled-labour pressure, volatile input costs, intense rents and customers who expect both speed and personal service.

A dedicated innovation team provides that mechanism. It is a small, cross-functional group with a standing remit to identify valuable opportunities, organise evidence, run controlled trials and recommend wider adoption. It does not sit apart from operations or replace chefs, buyers, restaurant managers and marketing specialists. Instead, it gives their expertise a shared structure, protected time and access to decision-makers.

Building such a team requires more than collecting bright ideas. The organisation must define the problem it owns, the resources it controls and the evidence that will justify scale. Australian conditions make this especially important. A concept that works in a dense Melbourne laneway, a busy Sydney CBD site or a regional hospitality business may need a different operating design, supply plan and risk assessment before it reaches customers.

From conference ideas to an operating model

FARE’s combination of educational sessions and supplier exhibits gives implementation questions a natural place to emerge. What does a change cost? Which team must own it? What would make a pilot fail? An innovation team turns those questions into a repeatable operating rhythm rather than leaving them to chance, connecting the conference floor with decisions inside the organisation.

Its work can follow a simple sequence. It captures signals from customers, staff, suppliers and data, then frames each opportunity around a customer problem and commercial constraint. The team tests the smallest credible version, records what happens and recommends one of three actions: stop, adapt or scale. A disciplined pipeline keeps promising experiments moving without forcing every idea into the business.

This model gives conference learning a second life. A session may introduce a concept, but local validation still requires frontline judgement, reliable measurement and leadership commitment. Peer relationships developed through FARE can become useful here. Operators can compare approaches with colleagues, suppliers can contribute trial resources, and advisers can challenge assumptions. The team connects external insight to internal action.

The business case for a focused mandate

A focused team must earn its place in the budget. Its return may not appear as a new menu item or app. Better forecasting can reduce waste; redesigned preparation can release paid hours for service; faster service can improve table turnover; and clearer offers can raise repeat visits. Finance should value these gains alongside revenue, using conservative assumptions and separating incremental benefits from work already planned.

Local competition sharpens the opportunity. Sydney operators often work with high rents, constrained footprints and thin margins on premium items, so small improvements matter. Melbourne’s dense laneway hospitality and sophisticated specialty-coffee culture raise expectations for consistency and speed. Brisbane adds a substantial visitor market and a strong outdoor dining scene. In each case, a team can test whether a new format improves throughput or customer satisfaction before committing to expensive rollout.

Different FARE audiences need different measures. A healthcare operator may prioritise lunch-time queues and reliable nutrition information. An education caterer may focus on uptake, waste and compliance. A convenience network may value rapid service and basket size. A recreation venue may look for flexible options that serve busy families. By concentrating on a defined segment, the innovation team can build a business case that reflects the actual economics and purpose of that operation.

Building a team that can deliver

The right membership combines capable people with authority to act. A practical core includes an operations leader, a chef or menu developer, a buyer, a customer or brand voice, and someone who can analyse commercial data. Finance, technology and frontline managers contribute when the work demands their expertise. Customer-facing staff should have a permanent voice, because ideas that create extra work during service rarely survive the rush.

Clear responsibilities prevent the team from becoming another meeting. One member might own insight and customer research, another experiments, and another commercial analysis, while a leader protects resources and decides on scale. Suppliers can join particular trials as partners without controlling the brief. External food technologists, accessibility advisers or design specialists can extend the perspective for defined projects.

Physical environments deserve the same attention as digital interfaces. The growth of minimalist frameless glass doors in Kazakhstan’s new architecture illustrates how visual simplicity can shape how people perceive and move through a space. The lesson is not to copy a look. It is to examine every point where layout, lighting and presentation either reduce friction or add to it.

The team also needs a regular forum. A short weekly review can unblock active tests, while a monthly decision meeting can compare results, stop weak ideas and release funding for stronger ones. People should be able to challenge a favourite concept without damaging working relationships. Leaders who welcome scrutiny model the behaviour they expect from staff, particularly when evidence points away from an expensive pilot.

Testing ideas with Australian conditions

Trials should occur where the proposition will meet its customer. Melbourne’s compact hospitality venues and strong café culture can support tests of new drinks, compact service formats and queue technology, but operators should account for limited preparation space and tight peaks. Brisbane’s outdoor dining culture provides another setting to test weather-dependent service, shade, menu speed and guest flow, rather than judging the concept in a quiet test kitchen.

Regional conditions reveal risks that central teams can overlook. Perth-based operators may serve mining, maritime and dispersed workforces where travel time, freight lead times and connectivity shape what is feasible. A prototype built for a flagship metropolitan site may fail without local stock, simpler technology or a fallback process. Field trials in remote locations can expose those dependencies before expansion creates costly disruption.

Adelaide and South Australia’s food and wine culture offer a different pathway to collaboration. Shared plates, seasonal produce and regional suppliers can inspire menu trials that feel locally relevant, while producers can help test ingredient quality at scale. Consumer protection remains non-negotiable: any launch must meet Food Standards Australia and New Zealand requirements, Australian Consumer Law obligations and allergen-labelling rules, with separation and cleaning controls verified in the actual service environment.

Local sourcing can broaden the idea beyond familiar favourites. First Nations food businesses and growers offer ingredients such as finger lime, lemon myrtle and wattleseed, bringing distinctive flavour and cultural value to menu development. The team should establish provenance, consistent supply and appropriate intellectual-property agreements. A culturally responsible approach strengthens the proposition and reduces the risk of treating traditional knowledge as a marketing device.

Measuring progress beyond novelty

Measurement keeps innovation from becoming a showcase for untested ideas. The team should track balanced indicators: opportunities screened, time taken to reach a credible result, pilots stopped early, and concepts that move into sustained operations. Each project also needs outcome measures tied to its purpose, such as waste, labour minutes, queue time, average spend, repeat visits or service accuracy.

Baselines must be captured before change begins, and results should be reported honestly. A food-cost improvement is different from a one-week popularity spike; online orders may rise while service errors rise with them. Finance and operations can agree on thresholds in advance, including the performance required for rollout and the point at which a test should stop. This removes pressure to rescue a weak concept because a sponsor is attached to it.

Numbers work best with structured human feedback. Short debriefs with customers, restaurant teams, delivery drivers and suppliers can explain why a metric moved. Peer exchanges often add the most useful detail: what another operator changed, what it cost and which assumption failed. An innovation team can convert those conversations into a shared evidence library, preserving the reasoning behind each decision and making future learning searchable.

Removing barriers to change

Resistance usually reflects sensible questions about workload, priorities and trust. Staff may see a new concept as a device to extract more labour, while managers may fear disruption during busy trading. Leaders should acknowledge those concerns and involve the people who will operate the change. The brief should state what will stop, what will be measured and whether frontline staff helped shape the test. Credibility grows when the team solves a real problem rather than manufacturing a showcase.

Budget pressure can be answered with staged commitments. Reserve a modest fund for discovery and small trials, then release larger amounts only when evidence supports expansion. Make the cost of testing visible, including staff time and supplier support, and set a stop-loss limit for each project. In a tight Australian market, this uses capital carefully and preserves credibility when a promising idea fails.

Change also reaches beyond one venue. Franchisees, independent operators and staff representatives may each hold a legitimate interest in how a new model works. When a trial affects rosters, workloads or service roles, involve the relevant representatives early and document the agreed arrangements. The goal is a fair process, clear accountability and evidence that operational gains are being shared rather than captured by the centre.

Scaling a successful pilot introduces fresh risks. A recipe that works at one site may depend on an exceptional chef; an ordering platform may not suit older devices; a new supplier may struggle with peak demand. The team should create a rollout plan covering training, equipment, communication, backups and post-launch review. It should also communicate when a result applies only to a specific site, customer group or operating condition.

Turning insight into coordinated action

The case for a dedicated team rests on continuity. It gives ideas a fair hearing, protects time for frontline knowledge and creates a route from evidence to investment. Keep it small enough to move quickly and connected enough to make change stick.

FARE Conference 2017 offered a valuable model: practical sessions, candid operator exchanges, supplier demonstrations and learning across diverse service settings. Apply that learning with your own customers, teams and constraints. Sponsor relationships can provide expertise or trial support, while the organisation retains ownership of the problem and decision.

Move from interest to a practical proposal: name one operational problem, one customer benefit and one measurable result. Give the team a leader, a protected budget and a first review date. Bring the brief to your next FARE community conversation, then begin with a small test designed to earn wider support.