Hacking Dermatology is launching a new round of team building and funding in 2019!
We are inviting you - dermatologists, scientists, clinicians, engineers, developers, patients, business strategists, and anyone who is interested in the topic - to participate in the challenge statement development round. This will take place between February and March 2019. Keep reading to learn more!
At the 2018 hackathon, teams developed solutions to the challenge statements that were developed by a group of mentors and field experts. You can read about these challenge statements here. In 2019, we are opening participation in this process to a wider group of stakeholders. We want YOU to tell us what the most pressing, urgent needs are related to dermatology and diagnostics, treatment, and delivery of care.
You can participate by going to pigeonhole.at (passcode: DERM). Add your own challenge statement suggestions + vote on statements that others have uploaded. The first round of contributing and voting will be open between 2/18 and 3/14. In late March, there will be an opportunity to vote on the top 10 challenge statements from round 1.
Help us spread the word about this by getting your derm-networks involved, and add your voice to the effort before March 14.
A challenge statement (sometimes also referred to as a problem statement) defines a particular challenge or issue of importance both to the experts writing it and the participants attending the hackathon. The best challenge statements meet a real need, compel participants to take action, and inspire a creative solution that could not otherwise be developed. They are clear, actionable, and linked to impact.
A challenge statement is a hackathon call to action. It provides a clear, concise goal for participants and helps them to understand the aims and terms of the prize/challenge. In general, a challenge statement includes the objective of the hackathon (the what) and the criteria that will be used to assess if the objective has been met (the how).
What are important characteristics of a dynamite challenge statement?
Clarity: The better the challenge statement, the better the product you’ll likely end up with at the hackathon. It should be clear, actionable and linked to impact.
Concise communication: It is helpful to write a one-sentence tagline (or a short paragraph) for your challenge. Communication is key, and this will help you strike a chord with people who are viewing a lot of different opportunities.
Context and background: Every great challenge provides some context to what it is, why it’s important and why the solution matters. Is it a real need? Will the solution actually be used? Who is involved? Etc.
Be descriptive, but not prescriptive: Often times people write challenge statements with a solution in mind. These are far less inspiring than challenge statements that provide room for the hackathon participants to not only meet the basic requirements, but also innovate beyond what was originally imagined.
Avoid identifying specific solutions: As you work to define your problem, it will be impossible not to think about solutions. In fact, working through possible solutions can help to deepen your understanding of the issue at hand. What you want to avoid is focusing too much on a specific solution or you may end up introducing bias into the challenge design and limiting innovation.
Scope of work: The problem statement needs to be something that a small team can move the needle on over a weekend. This gives the team a specific goal, an opportunity to iterate on their solution, and a way to measure their progress. Broadly scoped statements can lead to false starts as the team figures out their approach and reduces hacking time.