Presentation |
Team members demonstrate cohesion and effort
|
Not polished
| 1 | 2 | 3 | 4 | 5 |
Clearly polished
|
Creativity and ingenuity of the idea
|
Not a unique solution
| 1 | 2 | 3 | 4 | 5 |
A unique solution
|
Story of the team moving from problem to solution
|
Unclear progression
| 1 | 2 | 3 | 4 | 5 |
Clear progression
|
Applicability |
What is the problem, and why is it important?
|
Not well described
| 1 | 2 | 3 | 4 | 5 |
Clearly described
|
Ability to articulate pain point(s) around the problem. |
Unable to articulate
| 1 | 2 | 3 | 4 | 5 |
Well-articulated
|
Clearly defined use-case that matches articulated pain points. |
No use-case
| 1 | 2 | 3 | 4 | 5 |
Clearly defined
|
Sustainability |
Plans for a beta version are clearly laid out
|
No plans
| 1 | 2 | 3 | 4 | 5 |
Clearly laid out
|
Path to market
|
No path
| 1 | 2 | 3 | 4 | 5 |
Clear path
|
Business model/scalability/distribution
|
No model
| 1 | 2 | 3 | 4 | 5 |
Clear model
|
Feasibility |
Solution provided is technically sound
|
Major technical flaws
| 1 | 2 | 3 | 4 | 5 |
Technically sound
|
Team identified next steps to take
|
None identified
| 1 | 2 | 3 | 4 | 5 |
Identified next steps
|
Feasibility of implementation in the local health system
|
Unfeasible
| 1 | 2 | 3 | 4 | 5 |
Very Feasible
|
Equity |
Solution positively impacts individuals, institutions and/or the community
|
No impact
| 1 | 2 | 3 | 4 | 5 |
Strong Impact
|
Solution harnesses local resources and capacities
|
Does not use local resources
| 1 | 2 | 3 | 4 | 5 |
Uses resources
|
Solution has a perceived meaningful value
|
No perceived value
| 1 | 2 | 3 | 4 | 5 |
Strong perceived value
|
Impact |
Positive economic impact on individuals, institutions and community
|
No impact
| 1 | 2 | 3 | 4 | 5 |
Strong, positive impact
|
Wellness impact on individuals, institutions and community
|
No impact
| 1 | 2 | 3 | 4 | 5 |
Strong, positive impact
|