Using the Impact Challenge to Test Business Assumptions
The International Conference 2018 brought undergraduate students together with business executives and influential leaders in New York City from November 18–20. Its program combined keynotes, executive seminars, networking, a writing competition, and an Impact Challenge centered on the future of work.
The challenge offered a practical way to examine how changing technology, workforce expectations, and business models could affect people and organizations. Rather than treating an idea as automatically valuable, participants could use the experience to ask what must be true for that idea to create meaningful impact.
Although applications for the all-expenses-paid conference are now closed, the method remains useful. Students, founders, and emerging leaders can adapt the same approach to test business assumptions before investing substantial time, money, or credibility.
Start With The Assumption
Every business concept contains beliefs about customers, problems, behavior, resources, and outcomes. A team might assume that students need a particular career service, that employers will pay for it, or that a digital platform can reach users efficiently. These statements are starting points, not established facts.
Begin by writing each assumption in plain language. Avoid broad claims such as “the future of work will change.” Replace them with specific propositions: “Final-year students will spend time comparing skill-building programs” or “Small businesses will pay for a tool that helps them identify workforce gaps.”
This distinction matters because a vague idea can produce vague evidence. A precise hypothesis gives the Impact Challenge a clear purpose and helps the team decide what to observe, measure, and revise.
Turn Ideas Into Testable Hypotheses
A strong hypothesis identifies a target group, a predicted behavior, and a measurable signal. For example: “At least six of ten students who experience this prototype will request a follow-up conversation within one week.” The prediction may be wrong, but it is concrete enough to test.
Separate the assumptions by risk. The most dangerous assumption is usually the one that could make the entire concept irrelevant. If nobody has the stated problem, polishing a presentation or building advanced technology will not rescue the business model.
The challenge format encourages teams to focus on learning rather than performance alone. A persuasive pitch is useful, but evidence from interviews, prototype trials, or partner feedback is stronger than confidence. Treat every activity as a small experiment designed to reduce uncertainty.
Design A Small Impact Experiment
An effective experiment should be fast, ethical, and limited in scope. Instead of launching a complete service, create a landing page, paper prototype, guided workshop, mock dashboard, or manual version of the proposed solution. The goal is to test the riskiest business assumption with the fewest resources.
Connect the experiment to the future-of-work theme by considering both commercial and human outcomes. A workforce product might be profitable while excluding people with limited connectivity. A training program might improve employability but require more time than participants can spare. Impact means examining who benefits, who may be overlooked, and whether the proposed change is sustainable.
| Business assumption | Low-cost test | Useful evidence | Possible decision |
|---|---|---|---|
| Students want personalized career guidance | Conduct structured interviews and offer a sample session | Repeat requests, attendance, follow-up actions | Refine the audience or service |
| Employers will pay for workforce insights | Present a mock report to selected employers | Paid pilot interest, objections, budget range | Change pricing or customer segment |
| Users can adopt the product quickly | Run a short prototype task | Completion rate, errors, support needed | Simplify the experience |
| The solution creates fairer access | Compare participation across user groups | Inclusion gaps, accessibility feedback | Redesign delivery and safeguards |
Document the test before running it. Record the hypothesis, audience, timeframe, success threshold, and method of collecting evidence. This prevents teams from changing the standard after seeing the results.
Gather Evidence From Real People
Interviews are valuable when they explore existing behavior rather than invite polite approval. Ask how someone currently solves the problem, what it costs them, and what they have already tried. “Would you use this?” often produces optimism; “Tell me about the last time this happened” usually reveals more reliable information.
Observation and prototype use can uncover friction that people do not mention. A participant may praise an idea but abandon the trial because the instructions are confusing. That behavior is not a failure of the participant. It is evidence that the proposed experience needs revision.
Keep feedback separate from interpretation. Write down what people said or did, then identify patterns afterward. A single enthusiastic comment can inspire a new question, but repeated behavior across relevant participants provides a stronger basis for a business decision.
Interpret Results Without Overclaiming
A test rarely proves an entire business model. It offers a signal about one assumption under specific conditions. If six students request more information after a workshop, that suggests interest in the topic; it does not prove they will pay for a finished product.
Look for disconfirming evidence as deliberately as positive evidence. Ask which findings challenge the original plan, whether participants behaved differently from what they reported, and whether the sample represented the intended market. Confirmation bias can make a weak concept appear validated.
Use a simple decision rule: continue, change, or stop. Continue when the evidence meets the threshold and the remaining risks are manageable. Change when the problem seems real but the audience, channel, price, or solution needs adjustment. Stop when the central assumption repeatedly fails and no credible alternative has emerged.
Present Learning As Leadership
The strongest Impact Challenge presentation would show a disciplined learning journey. Explain the initial assumption, the test, the evidence, the unexpected result, and the next decision. This structure demonstrates judgment more effectively than claiming that the original idea was perfect.
Leadership also means acknowledging limitations. State how many people participated, what the experiment could not measure, and which questions remain open. Executives and mentors are more likely to trust a team that understands the boundaries of its evidence.
For historical details about the event and its program, readers can consult the conference contact page. The larger lesson remains relevant: meaningful innovation depends on listening, testing, and adapting before scaling.
Practical Rules For Better Testing
Use these recommendations to make an assumption-testing exercise more rigorous:
- Choose the assumption that poses the greatest risk to the entire concept.
- Define one observable behavior or measurable outcome before collecting feedback.
- Test with people who resemble the intended users, buyers, or beneficiaries.
- Record negative evidence and unexpected behavior instead of filtering it out.
- End every experiment with a clear continue, change, or stop decision.
The Impact Challenge can be treated as more than a competition activity. It is a compact model for entrepreneurial learning: identify what must be true, test it in the real world, and use evidence to improve the idea. Apply that process to one current business concept, run a focused experiment, and let the results determine the next move.