How to use the Impact Challenge to validate a business model

The Impact Challenge at the International Conference 2018 was designed around a demanding question: can a young team turn a significant workforce problem into a workable business idea? Across three days in New York City, undergraduate participants could investigate disruption, test assumptions, speak with experienced leaders and shape a response with measurable impact.

Although the conference ran from 18–20 November 2018 and its application period is now closed, the challenge remains a useful model for rapid business validation. Its value was not in producing a polished pitch alone. It was in helping participants discover whether a customer problem was real, whether a proposed solution was useful and whether the economics could support it.

What validation really means in a compressed challenge

Business validation is the process of testing the riskiest beliefs behind a venture before investing heavily in development. Those beliefs might concern the customer, the urgency of the problem, the solution, the price or the route to market. A strong three-day process does not prove that a company will succeed. It produces enough evidence to decide what deserves further testing.

For Australian students and emerging founders, this distinction matters. A clever concept aimed at “the workforce” is too broad to validate. A specific proposition, such as helping hospitality employers in inner Melbourne fill short-notice shifts, gives a team something concrete to investigate. The target user, buying context and likely competitors become easier to identify.

The challenge format also rewards learning speed. Interview notes, landing-page responses and conversations with executives are more useful than confident opinions. Evidence that changes the original idea is a positive result, because it prevents a team from building an attractive answer to the wrong problem.

Start with a local problem worth testing

A practical starting point is a visible change in how Australians work. Small businesses in Sydney may struggle to recruit reliable staff during seasonal peaks. Regional employers near Newcastle or Cairns may face skills shortages that cannot be solved by simply advertising on a major job board. In Melbourne, a long commute by tram or train can make flexible scheduling valuable for students and casual workers.

Teams should narrow the challenge to one group and one painful situation. “Improving employment” is a mission. “Helping independent cafés in Brisbane reduce last-minute roster gaps” is a testable business problem. Speaking with café owners, supervisors and workers may reveal that the real issue is payroll administration, transport, training or staff retention rather than recruitment itself.

Local language can help build trust. An Australian participant might hear that a process is “a bit of a pain” or that a manager needs a solution that works “by the arvo”. These casual comments can expose urgency, but they must be translated into measurable behaviour. Ask what the person currently does, what it costs and what would make them change.

Signals that a problem is worth testing

Turn assumptions into a testable model

A business model links a customer problem to a solution, revenue source and delivery method. During a short challenge, teams should avoid filling every box of a traditional business-plan template. Instead, they should identify the two or three assumptions most likely to make the idea fail.

For example, a platform for matching regional apprentices with employers may depend on employers being willing to pay, apprentices completing their profiles and training providers sharing information. The team can rank these assumptions by risk. Testing the payment question is usually more valuable than debating brand colours or writing detailed five-year forecasts.

A simple value proposition should explain who receives value, what changes for them and why the proposed approach is preferable. It might promise fewer unfilled shifts, faster access to specialist skills or a clearer pathway into work. The wording should be specific enough to test in interviews, a mock-up or a short online experiment.

Pricing deserves early attention in Australia’s relatively concentrated markets. A small business may prefer a low monthly subscription, while a government-funded organisation may require a formal procurement process. GST, data privacy, insurance and the cost of reaching customers can also affect viability. These are not reasons to abandon an idea; they are assumptions that need to be recorded.

High-risk assumptions to examine

Use three days as a rapid evidence cycle

On the first day, the team can define the customer, map the current experience and conduct focused interviews. The aim is to learn how people behave now, not to persuade them that a new idea is brilliant. Useful prompts include asking about the last time the problem happened, the workaround used and the consequences of leaving it unresolved.

The second day should convert those findings into a minimum viable test. This could be a clickable prototype, a service blueprint, a spreadsheet-assisted pilot, a sign-up page or a role-play of the proposed service. A team exploring flexible work could manually match a small group of workers with employers before building software. Manual delivery reveals whether the underlying service is valuable.

The third day is for testing willingness to act. Positive comments are weak evidence unless they lead to a measurable commitment, such as sharing contact details, booking a follow-up call, agreeing to a pilot or paying a small deposit. Feedback from an executive mentor can help identify commercial risks, while potential users provide the clearest signal about practical usefulness.

A strong evidence log records what was expected, what happened and what changed. If ten interviews produce eight polite compliments but no sign-ups, the team should treat that as a warning. If several users attempt to solve the problem immediately, the proposition may deserve deeper investigation.

Measure traction without mistaking enthusiasm for demand

Validation metrics should match the business model. A consumer service might track sign-ups, repeat use or referrals. A business-to-business product could track meetings with decision-makers, pilot agreements and the estimated value of a contract. A social enterprise may also measure employment outcomes, access or retention alongside revenue.

Teams should separate evidence from assumptions in their final presentation. “Twenty students said flexible work matters” is evidence of interest. “Students will pay $15 a month” remains an assumption until a payment test supports it. This discipline makes a pitch more credible because it shows the judges exactly what is known and what still needs work.

Australian market conditions make customer access especially important. A service tested with university students in Sydney may not transfer neatly to a regional town, where relationships, transport and local employers shape adoption. A solution for councils or public agencies may have a promising social benefit but a long sales cycle. The business model must reflect these realities rather than treating Australia as one uniform market.

The most useful outcome may be a pivot. Interviewees might value the service but identify employers, training organisations or councils as the paying customers. Alternatively, a technology product may become a managed service first. Changing direction during the challenge is evidence that the process is working.

Make the final decision practical

By the end of the three days, the team should be able to state what it tested, who responded, what evidence appeared and what remains uncertain. It should also make a clear decision: continue with a defined next experiment, narrow the customer segment, change the offer or stop pursuing the idea.

The International Conference 2018 connected undergraduates with business executives, influential leaders, networking opportunities, executive seminars and a writing competition as well as the Impact Challenge. That wider setting matters because validation improves when different perspectives are brought into the process. A founder may understand the customer problem, an executive may spot an impossible sales assumption and a peer may suggest a simpler prototype.

For an Australian participant adapting the method today, the practical takeaway is straightforward: choose one local workforce problem, identify the riskiest assumption, test it with real people and record behaviour rather than compliments. Three focused days can replace a large amount of speculation with a defensible next step.