Come to the Info Sessions for Real-Time FAQ
Dates and locations for the Info Sessions is located on the Home page.
If after reading through this page and the Details page you still have questions, please email:
hacking4diplomacy-staff@lists.stanford.edu
If after reading through this page and the Details page you still have questions, please email:
hacking4diplomacy-staff@lists.stanford.edu
General
Can my team have more or less than four students?
Each team must include four matriculated Stanford students. You can have people helping your team who are or are not Stanford students but they will be unable to enroll in the class or be present for class sessions. Enrollment in the class is only open to matriculated Stanford students.
** If you are not a student but are interested in providing technical advice to a team, email Joe Felter (jfelter@stanford.edu) letting him now which of the specific problems you are best suited to advise on, your company, position, LinkedIn profile, and contact info.
What's the right mix of skills for my team?
We've found that the optimal mix for a team includes two students who have technical backgrounds appropriate for the problem statement. Teams can then round out their memberships with other disciplines, areas of expertise, and backgrounds.
For the application, should I choose a specific problem or do I apply for all problems?
Please choose one or two problems to apply for. As applications will be evaluated by whether the team is capable of solving the particular problem, different teams will be better suited to different problems. This will be covered in more detail at the info sessions.
I have an idea/project that I think the State Department/government would be interested in. It doesn't fit one of the problem topics, can I still apply for this class?
Please contact Jeremy Weinstein and Zvika Krieger as soon as possible to see if it is possible to identify an organization to sponsor your project.
What is the difference between this class and E245 (the Lean Launchpad)?
In the ENGR 245 Lean LaunchPad class taught in the Winter Quarter, student teams come to class with a vision of a product or service they’d like to build. In this Hacking for Diplomacy class, student teams select from an existing set of problems provided by the Department of State. Although teams pick a problem to solve, Hacking for Diplomacy is not a product incubator for a specific technology solution. Instead, it provides teams with a deeper understanding of selected problems, the challenges of getting them out to the field, and the host of potential technological solutions that might be arrayed to solve them.
What is the difference between this class and the Hacking for Defense class?
In the Hacking for Defense class offered in the spring quarter, students select from an existing set of problems provided by the Department of Defense and Intelligence community. In Hacking for Diplomacy, students will be working with and selecting problems from a list provided by the State Department. One of the unique challenges of partnering with the State Department on tech-enabled solutions to foreign policy challenges is that, unlike DoD and the IC, the State Department doesn't have a large infrastructure for seeding and procuring tech solutions. So learning how to innovate and deploy solutions in a smaller bureaucracy without massive resources will be one of the real challenges that students explore.
Do I have to be a US citizen to take this class?
No, all nationalities are welcome.
Do I have to have previous experience with the Department of State or other US Government Agencies?
No prior government experience required. The class has a set of mentors and advisers to assist the teams.
How will we figure out who to talk to at the State Department?
Each team will have a sponsor in the State Department. They are the providers of the problem and will be making initial introductions for you.
How much time per week will I be spending on this class?
While the class meets once a week for three hours, students regularly spend 10-15 hours each talking to customers and building minimal viable products. Do not take this class if you cannot commit the time.
Each team must include four matriculated Stanford students. You can have people helping your team who are or are not Stanford students but they will be unable to enroll in the class or be present for class sessions. Enrollment in the class is only open to matriculated Stanford students.
** If you are not a student but are interested in providing technical advice to a team, email Joe Felter (jfelter@stanford.edu) letting him now which of the specific problems you are best suited to advise on, your company, position, LinkedIn profile, and contact info.
What's the right mix of skills for my team?
We've found that the optimal mix for a team includes two students who have technical backgrounds appropriate for the problem statement. Teams can then round out their memberships with other disciplines, areas of expertise, and backgrounds.
For the application, should I choose a specific problem or do I apply for all problems?
Please choose one or two problems to apply for. As applications will be evaluated by whether the team is capable of solving the particular problem, different teams will be better suited to different problems. This will be covered in more detail at the info sessions.
I have an idea/project that I think the State Department/government would be interested in. It doesn't fit one of the problem topics, can I still apply for this class?
Please contact Jeremy Weinstein and Zvika Krieger as soon as possible to see if it is possible to identify an organization to sponsor your project.
What is the difference between this class and E245 (the Lean Launchpad)?
In the ENGR 245 Lean LaunchPad class taught in the Winter Quarter, student teams come to class with a vision of a product or service they’d like to build. In this Hacking for Diplomacy class, student teams select from an existing set of problems provided by the Department of State. Although teams pick a problem to solve, Hacking for Diplomacy is not a product incubator for a specific technology solution. Instead, it provides teams with a deeper understanding of selected problems, the challenges of getting them out to the field, and the host of potential technological solutions that might be arrayed to solve them.
What is the difference between this class and the Hacking for Defense class?
In the Hacking for Defense class offered in the spring quarter, students select from an existing set of problems provided by the Department of Defense and Intelligence community. In Hacking for Diplomacy, students will be working with and selecting problems from a list provided by the State Department. One of the unique challenges of partnering with the State Department on tech-enabled solutions to foreign policy challenges is that, unlike DoD and the IC, the State Department doesn't have a large infrastructure for seeding and procuring tech solutions. So learning how to innovate and deploy solutions in a smaller bureaucracy without massive resources will be one of the real challenges that students explore.
Do I have to be a US citizen to take this class?
No, all nationalities are welcome.
Do I have to have previous experience with the Department of State or other US Government Agencies?
No prior government experience required. The class has a set of mentors and advisers to assist the teams.
How will we figure out who to talk to at the State Department?
Each team will have a sponsor in the State Department. They are the providers of the problem and will be making initial introductions for you.
How much time per week will I be spending on this class?
While the class meets once a week for three hours, students regularly spend 10-15 hours each talking to customers and building minimal viable products. Do not take this class if you cannot commit the time.
Team Formation & Ideas
Who owns the intellectual property tested in the Mission Model?
If you’re working with a Stanford related-technology (i.e. either research from one of the team members or University IP), you must check with the Office of Technology, Licensing to understand Stanford ownership rights in any resulting IP.
I feel my idea / Mission Model may become a real company and the "next killer app" and I want to own it myself what should I do?
A number of startups have come out of the Lean LaunchPad/Hacking for Defense classes. However, this is a team-based class. While you're in these classes your slides, notes, and findings will be shared with your team. There are no Non-Disclosure Agreements (NDA's.) Your team owns everything done in class. Discuss Intellectual Property rights with your team from the beginning. If you can’t come to agreement with the team, join another team, pick another project, or drop the class. Remember anything you do and learn in the class is public.
Will my Intellectual Property rights be covered under non-disclosures when I discuss my ideas with the class?
NO. This is an open class. There are no non-disclosures. All your presentations and Customer Discovery and Validation notes, business model canvas, blogs and slides can, and most likely will, be made public. This class is not an incubator. At times you will learn by seeing how previous classes solved the same class of problem by looking at their slides, notes and blogs.
Keep in mind that successful companies are less about the original idea and more about the learning, discovery and execution. (That’s the purpose of this class.) Therefore you must be prepared to share your ideas openly with the class. It is a forum for you to "bounce" your ideas off your peers.
I’m not comfortable sharing what I learn with others, what should I do?
Don’t take this class. This class is not an incubator. At times you will learn by seeing how previous classes solved the same class of problem by looking at their slides, notes and blogs.
If you’re working with a Stanford related-technology (i.e. either research from one of the team members or University IP), you must check with the Office of Technology, Licensing to understand Stanford ownership rights in any resulting IP.
- You own what Intellectual Property (patents, hardware, algorithms, etc.) you brought to class with you. No one (other than Stanford) has claim to anything you brought to class.
- You all own any intellectual property developed for the class (such as code for a web-based project) developed during class. You are agreeing to open-source your class developed assets. Your Department of State (DoS) sponsor will have access to those materials.
- You and your team members need to disclose to each other and your DoS sponsor what IP/Licensing rights any company you’ve worked at has to inventions you make at school.
- If any of you decide to start a company based on the class, you own only what was written and completed in the class. You have no claim for work done before or after the class quarter.
- If a subset of the team decides to start a company, they do NOT “owe” anything to any other team members for work done in and during the class. All team members are free to start the same company, without permission of the others. (We would hope that a modicum of common sense and fairness would apply.)
- By taking this class you have agreed to these terms with your team. You may decide to modify these terms before the class by having all team members agree in writing before the team is accepted in the class.
I feel my idea / Mission Model may become a real company and the "next killer app" and I want to own it myself what should I do?
A number of startups have come out of the Lean LaunchPad/Hacking for Defense classes. However, this is a team-based class. While you're in these classes your slides, notes, and findings will be shared with your team. There are no Non-Disclosure Agreements (NDA's.) Your team owns everything done in class. Discuss Intellectual Property rights with your team from the beginning. If you can’t come to agreement with the team, join another team, pick another project, or drop the class. Remember anything you do and learn in the class is public.
Will my Intellectual Property rights be covered under non-disclosures when I discuss my ideas with the class?
NO. This is an open class. There are no non-disclosures. All your presentations and Customer Discovery and Validation notes, business model canvas, blogs and slides can, and most likely will, be made public. This class is not an incubator. At times you will learn by seeing how previous classes solved the same class of problem by looking at their slides, notes and blogs.
Keep in mind that successful companies are less about the original idea and more about the learning, discovery and execution. (That’s the purpose of this class.) Therefore you must be prepared to share your ideas openly with the class. It is a forum for you to "bounce" your ideas off your peers.
I’m not comfortable sharing what I learn with others, what should I do?
Don’t take this class. This class is not an incubator. At times you will learn by seeing how previous classes solved the same class of problem by looking at their slides, notes and blogs.
Resources Available
What kind of support will our team have?
The teaching team consists of professors, experienced government professionals, and multiple Course Assistants. Each team will be assigned two mentors and a liaison. A mentor is an experienced defense/IC official, investor or consultant assigned to your team. They’ve volunteered to help with the class and your team because they love hard problems, love startups and appreciate the importance of addressing problems facing the DoS. Their job is to guide you as you get out of the building and to interface effectively with your DoS sponsors.
How often can we/should we meet with our mentor?
Your mentor is expecting to meet with you at least every week face-to-face or by Skype. You can email them or meet with them more often if they have time.
Can I talk to a mentor not assigned to my team?
By all means, do so. All the mentors are happy to help. However they cannot support your team full time unless your mentor decides to swap places with them.
I have a busy schedule and my mentor can’t meet when I want them to.
Mentors have day jobs. Asking them to meet or reply to you ASAP is not acceptable. So plan ahead to allow for a reasonable amount of time for a reply or meeting. Be concise with your request and be respectful of their time.
I need help now.
You first stop is your TAs. Email or sit down with them during the week if you have a problem. Your professors have office hours every (Time TBD). If you need something resolved sooner, email us.
The teaching team consists of professors, experienced government professionals, and multiple Course Assistants. Each team will be assigned two mentors and a liaison. A mentor is an experienced defense/IC official, investor or consultant assigned to your team. They’ve volunteered to help with the class and your team because they love hard problems, love startups and appreciate the importance of addressing problems facing the DoS. Their job is to guide you as you get out of the building and to interface effectively with your DoS sponsors.
How often can we/should we meet with our mentor?
Your mentor is expecting to meet with you at least every week face-to-face or by Skype. You can email them or meet with them more often if they have time.
Can I talk to a mentor not assigned to my team?
By all means, do so. All the mentors are happy to help. However they cannot support your team full time unless your mentor decides to swap places with them.
I have a busy schedule and my mentor can’t meet when I want them to.
Mentors have day jobs. Asking them to meet or reply to you ASAP is not acceptable. So plan ahead to allow for a reasonable amount of time for a reply or meeting. Be concise with your request and be respectful of their time.
I need help now.
You first stop is your TAs. Email or sit down with them during the week if you have a problem. Your professors have office hours every (Time TBD). If you need something resolved sooner, email us.
Team Dynamics
What roles are in each team?
Traditionally, each team member is part of the “customer development team”. You have to figure out how to allocate the work.
What if my team becomes dysfunctional?
Prepare to work through difficult issues. If the situation continues, approach the teaching team. Do not wait until the end of the quarter to raise the issue.
What if one of my teammates is not "pulling his/her weight"?
Try to resolve it within your team. If the situation continues longer than a week, please approach the teaching team. Final grades will also reflect individual participation and contribution.
What kind of feedback can I expect?
Continual and relentlessly direct feedback weekly. Substandard quality work will be immediately brought to your attention
Traditionally, each team member is part of the “customer development team”. You have to figure out how to allocate the work.
What if my team becomes dysfunctional?
Prepare to work through difficult issues. If the situation continues, approach the teaching team. Do not wait until the end of the quarter to raise the issue.
What if one of my teammates is not "pulling his/her weight"?
Try to resolve it within your team. If the situation continues longer than a week, please approach the teaching team. Final grades will also reflect individual participation and contribution.
What kind of feedback can I expect?
Continual and relentlessly direct feedback weekly. Substandard quality work will be immediately brought to your attention