Programme in development · Open problems
Innovation Challenges
Programme in development
Translate a real problem into a bounded, researchable and safe short-cycle brief so learners and the problem owner both gain evidence.
01 / Programmes
What makes a sound challenge brief
State the context, affected people, current alternatives, available information, constraints and the learning result being sought.
Do not prescribe a single answer, demand delivery before the evidence exists or substitute a campaign line for a problem statement.
02 / Programmes
Proposed process
The problem owner explains the context; teams research and clarify; a mid-cycle low-cost prototype or concept test produces feedback.
The final review presents evidence, limitations and next steps. Visual polish must not conceal an untested claim.
03 / Programmes
Responsibility of the problem owner
Provide information that can be used lawfully, name an accountable feedback contact and state what must remain private.
If an operational deliverable is expected, a separately paid professional engagement is appropriate; a learning challenge is not free procurement.
04 / Programmes
Rights and safety
Background IP, new work, attribution, confidentiality and data use must be stated before applications. Teams need not disclose sensitive ideas before accepting terms.
Where minors participate, the brief, communications, site visits and tool use require age-appropriate risk review.
05 / Programmes
Current status
No challenge brief, sponsor, deadline or prize has been formally announced. Any future challenge will have a page with complete rules.
Publishing this concept does not imply support from a company, university or investment organisation.