List five takeaways from Guy Kawasaki’s talk and explain exactly how you will integrate that concept/construct/strategy into your project. Make it compelling. Don’t write generic forgettable text.

 

1. 10, 20, 30 rule. Have 10 slides, 20 mins, and the smallest font is 30 pt. I really found this as a good way to think about how to give a presentation from a formation point of view. We hope to implement this rule when it comes to our presentations to help us move to have a more condensed clear and understood presentation.
2. Don’t use the Dilbert mission statement generator have a mantra, that we can use to invite people to actually understand what we are doing. What we are doing from an academic point is easy to explain, but from a simplistic point of view, we need a mantra to simplify it and allow other people to quickly understand what we doing.
3. Let 100 flowers blossom. In our case, this means to sort not to worry about the worry about who we get the data from, or whether or not we get the data. We should work with what we can get data wise and who we can get to survey.
4. Don’t listen to the bozo’s/you don’t know what will work or won’t. There have been a lot of people who have told us that there is no way to really do what we plan to do very accurately. honestly, half the time I am not even sure we will be able to do it, but as long as we keep working and trying we will learn and find out new knowledge.
5. Milestone assumptions tasks. This one is pretty obvious in regard to what to after last weeks blog. We have to first decide what we need to get done. Then we need to figure out what we are assuming, which we sort of did last week. Then we need to figure out how we will confirm the assumption and complete our milestones, which we sort of talked about last week.

 

In partnership with one or at most two team members, present a business model canvas for your venture.