How to use the impact challenge to build a minimum viable product

The International Conference 2018 landed in New York on November 18–20 with a packed agenda of keynotes, executive seminars and a writing competition, but the most consequential session was the Impact Challenge. It asked one question: what would you actually build if you had a chance to reshape the future of work? Hundreds of undergraduate applicants answered with essays, prototypes and pitch decks, hoping to walk away with mentorship and a runway for their ideas.

The format rewarded action over polish. Teams had to define a problem tied to workforce disruption, sketch a credible solution and prove that real people would use it. For anyone trying to move from a written entry to a tangible product, the Impact Challenge doubles as a crash course in building a minimum viable product — a stripped-back version of your idea that tests assumptions cheaply.

For Australian applicants the challenge carries a familiar undertone. The country is wrestling with automation in its mines, the rise of the gig economy across Sydney and Melbourne, and a small business sector that already produces Canva, Atlassian and Afterpay. Programs such as Startmate, Stone & Chalk in Sydney and Fishburners have made it normal for an undergrad in Brisbane or Perth to spin up a venture alongside study, so the leap from competition entry to working product feels less foreign than it did a decade ago.

What the impact challenge really tests

Judges at the 2018 conference were not awarding points for slide aesthetics. They were listening for problem clarity, customer insight and evidence that the team could execute. The same rubric is useful for any MVP project: before committing weeks to coding, ask whether your idea addresses a pain point someone will pay to relieve.

The best entries framed the future of work in concrete terms. Rather than broad essays about automation, teams pointed to a specific population — shift workers in Melbourne warehouses, gig couriers navigating Sydney traffic, regional graduates returning to towns with thin job markets — and proposed something testable. A problem this narrow is easier to prototype against than a sweeping national narrative.

Turning your insight into a sharp problem statement

A minimum viable product only works when the problem it solves has been validated. Lean startup doctrine, popularised by Eric Ries and Steve Blank, treats customer discovery as the first milestone, not the prototype. Interviews should surface jobs to be done, frustrations and existing workarounds, because people rarely articulate their needs the way your team expects.

Australian founders tend to do well in this stage because the culture rewards direct conversation. Whether you sit down with a tradie in western Sydney, a barista in Carlton or a remote coder in Broome, the expectation is that you have a yarn, ask blunt questions and treat their answers as evidence. Document the conversations, look for patterns across a dozen interviews, and rewrite the problem until a stranger can repeat it back.

Designing the slimmest possible prototype

An MVP is not a rough version of the final product. It is the smallest experiment that can confirm or kill a core assumption. Common patterns include the concierge test, where you deliver the experience manually, the Wizard of Oz demo, where a human is hidden behind an automated interface, and the single-feature build, where one workflow ships while everything else waits.

The local ecosystem has produced several examples of this discipline. Afterpay began as a buy-now-pay-later layer stitched onto a handful of Melbourne fashion retailers before expanding. Canva launched with one template and a drag-and-drop canvas the founders could defend with conviction. The lesson: choose one painful workflow and solve it well enough that someone uses it twice.

Validating with real Australians before you build

Validation belongs before build, not after. Australian consumer behaviour has its own quirks: high smartphone penetration, an early embrace of contactless payments and a healthy scepticism toward brands that oversell. Test your prototype against students from UNSW and UTS, hospitality workers in Brisbane's Fortitude Valley, or remote employees linked to Perth's mining sector.

Pay attention to the Australian Consumer Law guarantees when sketching commercial pilots. If a customer can pay for your service, even in beta, you owe them clear terms, refund pathways and privacy disclosures. Building these in from day one will save a difficult ACCC conversation later and reassure pilot users you take their trust seriously.

Building in 48 hours: a founder's playbook

Most Impact Challenge teams will not have months. A weekend sprint is realistic if the scope is honest. Lock the team in a room — a quiet corner of Fishburners, a borrowed studio at Melbourne Connect, or a flat in Adelaide — and agree on the one feature that must work by Sunday evening. Everything else is cut.

Modern no-code tools make this sprint short. A clickable prototype in Figma, a back-end in Airtable, automation stitched together with Zapier and a public landing page in Carrd will demonstrate traction without a developer in sight. Reserve custom code for the part of the product where off-the-shelf tools fall short. Ship the demo URL, capture sign-ups and treat the result as a starting point rather than a finish line.

Measuring traction and knowing when to pivot

An MVP earns its keep the moment you start learning from real usage. Define a handful of leading indicators — activation rate, week-two retention, share of pilot users who refer a colleague — and review them weekly. Resist the urge to add features until those metrics move.

If the numbers are stubborn, the data is telling you something. Pivot the audience, pivot the problem or pivot the solution, but do not pretend the experiment worked. The Australian Bureau of Statistics publishes regional employment and industry data that can reframe your hypothesis cheaply, and Australian Financial Review startup coverage can show where similar teams are gaining traction. Use those resources before assuming the market is wrong.

Recommendations for participants from Sydney to Perth

• Pick one slice of the future of work you can describe in a single sentence and refuse to widen it.
• Run at least twelve customer interviews before any code is written, and record the quotes that surprised you.
• Choose a prototype pattern that lets you ship within a weekend, even if the back end is a shared spreadsheet.
• Use Stone & Chalk, Fishburners or a university incubator for free desk space and feedback sessions instead of renting an office.
• Track three leading metrics from the first sign-up and review them every Monday morning with the full team.
• Apply for the Accelerating Commercialisation grant or your university's venture fund before seeking private capital, since Australian grant money is non-dilutive.
• Treat every pilot customer as a co-designer; their willingness to keep talking is the real MVP signal.

A practical takeaway: the Impact Challenge is not really about the conference judges. It is a forcing function to turn a written idea into something a stranger can click, sign up for or buy within seven days. The teams that win are usually the ones whose MVP is already in someone else's hands by the time the keynote ends.