01
Understand
Learn the context, the user and what has already been attempted.
The method
From problem statement to working solution.
Not a competition. Not a one-time project. A structured build-and-validation environment where the work is judged by what the team can prove.
The complete system
The Udyaan engine.
01Assemble
The right people.
- 01
Problem
A meaningful challenge enters from industry, research or a builder.
- 02
People
Students bring curiosity, capability and a reason to care.
- 03
Team
The problem brings the right disciplines together.
02Build & validate
The work. The proof.
- 04
Build
Research becomes a prototype, with mentors in the loop.
- 05
Validate
Test the solution with users, evidence and real constraints.
03Take it forward
A next step that fits.
- 06
Outcome
Adoption, research or a credible next step for the team.
- 07
Venture
When the evidence supports it, keep building.
When the opportunity is validated
Build. Get feedback. Test again.
A venture is one possible outcome. Evidence decides the next move.
01 / Do the work
Build against reality.
The method stays consistent. The time, team and resources depend on the problem. Each stage produces something the next decision can use.
02
Investigate
Talk to people closest to the problem. Gather evidence and test assumptions.
03
Frame
Define a focused problem statement and agree what success would look like.
04
Build
Create the simplest prototype, process, model or service that tests the idea.
05
Test
Put the solution into a real context and observe what happens.
06
Iterate
Use the evidence to improve. Keep what works and change what does not.
07
Validate
Decide whether the technical, user and commercial evidence supports continuation.
08
Present
Show the approach, limitations, proof and a clear next step.
The programme calendar
A four-week sprint inside a longer journey.
The existing interdisciplinary sprint gives the work an execution rhythm. Validation and venture continuation can extend beyond it; the project determines the next stage.
- Week 01Research + strategy
- Week 02Prototype + testing
- Week 03Production + policy
- Week 04Exhibit + next steps
02 / Stay connected to the problem
You build. Experts challenge. The owner responds.
Student team
Owns the research, decisions, prototypes, testing, iteration and final proof.
Mentor
Brings experience, questions assumptions and helps the team make stronger decisions.
Problem owner
Provides context, constraints and feedback on whether the solution is useful in practice.
Build. Get feedback. Improve. Test again. Agree review points with the mentor and problem owner when the brief is scoped.
03 / Evidence gates
A prototype is
not yet a venture.
The next move should be based on evidence, not momentum. A team may need to revisit earlier assumptions before progressing.
- 01
Technical validation
Demonstrate feasibility, reliability and performance within the agreed constraints.
- 02
User validation
Test whether the solution addresses a real need and can be used in context.
- 03
Market validation
Establish a credible need, customer or adoption pathway.
- 04
Commercial validation
Explain the value created, costs involved and reason to continue.
04 / Decide what comes next
Follow the evidence, not a fixed ending.
Continue. Iterate. Adopt. Research. Spin out. Every serious project should leave with a clear next step, even when that step is not a company.
Company adoption
A problem owner chooses to pilot, adopt or pay for a solution that creates value.
Research & IP
The evidence opens a research pathway, intellectual property opportunity or further technical development.
Student venture
A validated opportunity and a team willing to continue can become the foundation of a new venture.
For the work worth continuing
A practical path to a venture.
ProblemSolutionPrototypeValidationMVPCustomerVenture
Progress depends on evidence, an owner willing to continue and the relevant university and partner agreements. Funding or incorporation is not guaranteed.
The next step is yours
Build something
the world can use.
Find the problem. Build the solution. Prove it.
Then decide how far to take it.