├── .gitignore ├── AUTHORS.md ├── LICENSE.txt ├── README.md ├── docs ├── Makefile ├── conf.py ├── index.md ├── index.rst └── pie-cookbook-0.9.md ├── drafts ├── 0.9 │ └── pie-cookbook-0.9.md ├── archive │ ├── 0.9 │ │ ├── next-version-working-draft-tactical.md │ │ ├── working-draft-appendix.md │ │ ├── working-draft-contextual.md │ │ ├── working-draft-glossary.md │ │ └── working-draft-tactical.md │ └── working-draft.md ├── community │ └── community.md └── current │ ├── next-version-working-draft-tactical.md │ ├── pie-cookbook-working-draft.md │ ├── working-draft-appendix.md │ └── working-draft-glossary.md ├── fedwiki ├── .gitignore ├── README.md ├── outline.rb ├── pages │ └── .keep ├── preserve.sh ├── preview.sh ├── publish.sh ├── status │ └── favicon.png ├── transform.rb └── welcome │ ├── ward-cunningham │ └── welcome-visitors ├── notes ├── community │ ├── README.md │ └── archive │ │ ├── 2016-05-23-Initial-Community-Content-Sprint.md │ │ ├── Sometimes the space you can charge for is not the space you.md │ │ ├── brands-role-in-community.md │ │ ├── building-community.md │ │ ├── cocktails.md │ │ ├── community-as-an-asset.md │ │ ├── community-notes.md │ │ ├── culture-of-the-community.md │ │ ├── curated-coworking.md │ │ ├── environmental-scan.md │ │ ├── starting-accelerator.md │ │ └── startup-communities.md ├── context │ ├── README.md │ ├── archive │ │ ├── building-startup-accelerator.md │ │ ├── context-definitions.md │ │ └── preface.md │ └── foreword.md ├── funding │ └── README.md ├── github │ ├── howto-github-img │ │ ├── 000-forkrepo.gif │ │ ├── 001-forkedrepo.png │ │ ├── 002-creatingnewfile.gif │ │ ├── 003-editingexisting.gif │ │ ├── 004-forkaheadofmaster.png │ │ ├── 005-createpullrequest.png │ │ ├── 006-createpullrequestbutton.png │ │ ├── 007-pullrequestscreen.png │ │ ├── 007a-openpullrequest.png │ │ ├── 008-commitsbehind.png │ │ ├── 009-switchthebase.png │ │ ├── 010-createreversepullrequest.png │ │ ├── 011-reversepullrequestform.png │ │ ├── 012-pullrequesttab.png │ │ └── 013-acceptpullrequest.png │ └── howto-github.md ├── logistics │ ├── 00_README.md │ ├── 01_index.md │ ├── archive │ │ ├── cadence-timing.md │ │ ├── guide-mentors-meeting-with.md │ │ ├── logistics-demo-day.md │ │ ├── logistics-enforced-socializing-with-peers.md │ │ ├── logistics-family-dinner.md │ │ ├── logistics-lunch-and-learns.md │ │ ├── logistics-post-mortem.md │ │ ├── logistics-typical-week.md │ │ ├── onboarding-startups.md │ │ ├── onboarding.md │ │ └── pie-staff-roles-responsibilities.md │ ├── letter-application-one-week.md │ ├── letter-applications-open.md │ ├── letter-applications-two-weeks.md │ ├── letter-demo-day-follow-up.md │ ├── letter-demo-day-invite.md │ ├── letter-demo-day-livestream-reminder.md │ ├── letter-demo-day-logistics.md │ ├── letter-technical-issues.md │ ├── onboarding-acceptance-letter.md │ ├── onboarding-what-to-expect.md │ ├── onboarding-what-youre-getting-in-to.md │ └── pie-application-cheat-sheet.md ├── mentors │ ├── 00_README.md │ ├── 01_index.md │ └── archive │ │ ├── common-sense.md │ │ ├── mentor-integrity.md │ │ ├── mentoring-mentors.md │ │ ├── mentoring.md │ │ ├── mentors-activating.md │ │ ├── mentors-bad-actors.md │ │ ├── mentors-coaching-on-speaking.md │ │ ├── mentors-matchmaking-vs-speed-dating.md │ │ ├── mentors-time-commitment.md │ │ └── mentors-vs-advisors.md ├── misc │ ├── README.md │ ├── accidents │ │ ├── contest-404.md │ │ └── happy-accidents-food.md │ ├── archive │ │ ├── be-intentional.md │ │ ├── drawing-inspiration.md │ │ └── how-to-use-this-cookbook.md │ └── mistakes │ │ ├── mentors-corporate.md │ │ ├── mentors-homogenous.md │ │ ├── mistakes-were-made-hubris.md │ │ └── mistakes-were-made-ignoring-our-thesis.md ├── outline.md ├── partnerships │ └── README.md ├── pie │ ├── README.md │ ├── archive │ │ └── history-pie.md │ ├── instigators.md │ ├── kickstarter │ │ ├── kickstarter-pie-cookbook-main.md │ │ ├── kickstarter-pie-cookbook-update-01.md │ │ ├── kickstarter-pie-cookbook-update-02.md │ │ ├── kickstarter-pie-cookbook-update-03-backer.md │ │ ├── kickstarter-pie-cookbook-update-04.md │ │ ├── kickstarter-pie-cookbook-update-05.md │ │ ├── kickstarter-pie-cookbook-update-06.md │ │ ├── kickstarter-pie-cookbook-update-07.md │ │ ├── kickstarter-pie-cookbook-update-08.md │ │ ├── kickstarter-pie-cookbook-update-09.md │ │ ├── kickstarter-pie-cookbook-update-10.md │ │ ├── kickstarter-pie-cookbook-update-11.md │ │ ├── kickstarter-pie-cookbook-update-12.md │ │ ├── kickstarter-pie-cookbook-update-13.md │ │ ├── kickstarter-pie-cookbook-update-14.md │ │ ├── kickstarter-pie-cookbook-update-15-backer.md │ │ ├── kickstarter-pie-cookbook-update-16.md │ │ ├── kickstarter-pie-cookbook-update-17-backer.md │ │ ├── kickstarter-pie-cookbook-update-18.md │ │ ├── kickstarter-pie-cookbook-update-19.md │ │ ├── kickstarter-pie-cookbook-update-20.md │ │ ├── kickstarter-pie-cookbook-update-21-backer.md │ │ ├── kickstarter-pie-cookbook-update-22.md │ │ ├── kickstarter-pie-cookbook-update-23-backer.md │ │ ├── kickstarter-pie-cookbook-update-31.md │ │ └── kickstarter-pie-cookbook-update-32.md │ ├── pie-lead-in.md │ ├── sidebar-fresh-pie.md │ ├── sidebar-getting-even-more-creative.md │ ├── sidebar-pie-from-side-project-to-startup.md │ ├── staffing.md │ └── standups │ │ └── 20160404.md ├── space │ ├── README.md │ └── space-minimal-valuable.md └── startups │ ├── README.md │ ├── startups-educating.md │ └── startups-selecting.md └── source ├── documents ├── 1776-Innovation-that-Matters-2016.pdf ├── HOW-TO-SET-UP-A-SUCCESSFUL-UNIVERSITY-START-UP-INCUBATOR-RK2.pdf ├── ICIC_JPMC_Incubators_post.pdf ├── Mentor Protege 20140609.docx ├── a16z-VC-economics.md ├── pie-Demo-Day-Run-of-Show.xlsx ├── pie-offer-letter.doc ├── pie-statement-of-capitalization.doc └── rfpOregonInc.docx ├── images ├── 2009-07-01 14.20.24.jpg ├── 2009-07-01 14.20.29.jpg ├── 2009-07-01 14.20.34.jpg ├── 2009-07-01 14.20.38.jpg ├── 2009-09-11 13.45.53.jpg ├── 2009-10-07 19.15.38.jpg ├── 2009-10-29 17.13.54.jpg ├── 2010-04-05 12.20.22.jpg ├── 2011-03-05 20.31.38.jpg ├── 2011-03-08 09.30.51.jpg ├── 2011-08-12 13.25.01 HDR.jpg ├── 2011-08-19 10.48.05 HDR.jpg ├── 2011-08-25 09.47.23.jpg ├── 2011-08-25 09.55.10.jpg ├── 2011-09-07 23.27.14.jpg ├── 2011-09-09 08.15.32.jpg ├── 2011-09-15 12.25.36.jpg ├── 2011-09-15 20.40.13.jpg ├── 2011-09-20 14.01.56.jpg ├── 2011-09-22 10.51.52.jpg ├── 2011-10-27 18.16.36.jpg ├── 2011-11-14 20.32.36.png ├── 2012-01-22 19.38.58.jpg ├── 2012-04-27 19.29.38.jpg ├── 2012-05-21 17.10.02.jpg ├── 2012-05-23 12.15.06.jpg ├── 2012-06-04 10.59.47.jpg ├── 2012-06-12 20.13.26.jpg ├── 2012-07-16 19.51.14.jpg ├── 2012-07-17 12.50.12.jpg ├── 2012-10-05 10.02.29.jpg ├── 2012-12-15 09.34.28.jpg ├── 2013-10-02 15.51.46-2.jpg ├── 2013-10-09 09.33.27-2.jpg ├── 2013-10-10 14.15.25-2.jpg ├── 2014-06-21 13.30.43.jpg ├── 2014-10-24 22.51.34-1.jpg ├── 2015-03-01 12.20.18.jpg ├── 2015-03-12 11.52.18.jpg ├── 2015-03-13 15.53.50.jpg ├── 2015-03-13-13.55.06.jpg ├── 2015-03-14 12.10.41.jpg ├── 2015-03-14 13.06.04.jpg ├── 2015-03-14 13.46.57.jpg ├── 2016-04-16 12.28.42-2.jpg ├── 6105242576_fb52ed9c20_b.jpg ├── OSB_010.jpg ├── PIE-CENTRL-interior-2015.jpg ├── PIE-Logo.zip ├── PIE-Nike-open-data-hack.jpg ├── PIE-Renny_Gleeson-cofounder.jpg ├── PIE-sketch-2009.jpg ├── all-the-feels.jpg ├── appthwack-founders-lab-1000.png ├── flowchart-community-engagement.jpg ├── logo-portland-modern-manufacturing-collective.pdf ├── osb-demo-day-2015.jpg ├── photo-repositories.md ├── pie-active-cropped.jpg ├── pie-alum-column.jpeg ├── pie-clearing-out-cropped.png ├── pie-countdown-clock.jpg ├── pie-demo-day-2013-bw.jpg ├── pie-gowalla_400x400.png ├── pie-highback-leather-chairs.jpg ├── pie-ikea-melltorp-table-white.JPG ├── pie-kickstarter-hat-socks.jpg ├── pie-kitchen-table.jpg ├── pie-light-switches-xolotl.jpg ├── pie-pie-gleeson.jpg ├── pieAcceleratorEmotionalRollerCoaster.001.png ├── pieAcceleratorEmotionalRollerCoasterMonth01Detail.png ├── pieAcceleratorEmotionalRollerCoasterMonth02Detail.png ├── pieAcceleratorEmotionalRollerCoasterMonth03Detail.png ├── pieAcceleratorEmotionalRollerCoasterPreAccelerator-Detail.png ├── pieAcceleratorEmotionalRollerCoasterPreAccelerator.png ├── pieActiveSpace.jpg ├── pieEmptySpace.jpg ├── pieFrontDoor.jpg ├── pieKirstenRick.jpg ├── slideshow-full-00 copy.png ├── slideshow-full-00.png ├── slideshow-full-01.png ├── slideshow-full-02.png ├── slideshow-full-03.png ├── slideshow-long-mentors-00.png ├── slideshow-long-space-01.png ├── slideshow-long-space-02.png ├── slideshow-long-space-03.png ├── slideshow-long-space-04.png ├── slideshow-long-startups-00.png ├── supportland-demo-day-pie.jpg └── way-is-shut.gif ├── presentations └── osbMeeting2015.pdf ├── reference.md └── videos └── video-repositories.md /.gitignore: -------------------------------------------------------------------------------- 1 | 2 | .DS_Store 3 | docs/_build 4 | 5 | docs/id_rsa_cmd.pub 6 | 7 | docs/id_rsa_cmd 8 | -------------------------------------------------------------------------------- /AUTHORS.md: -------------------------------------------------------------------------------- 1 | # Advice to Authors 2 | 3 | This work enters the commons based on real experience and an sincere willingness to share. 4 | We hope that there will be many authors over time and that they will make sharing ever easier. 5 | Here several downstream technologists offer their advice on how to make the work more meaningful to a broader audience. 6 | 7 | ### Voice 8 | 9 | This work has its genesis in a singular event. This becomes our template. 10 | But from here on out authors are welcome to speak of "we" without being all that sure who we are. 11 | Our readers will be aware that there are more than one voice here. 12 | Avoid the desire to be too specific. We write as a community united. 13 | 14 | ### Media 15 | 16 | We resist referencing content that cannot become part of this commons due to incompatible license, format or retention. 17 | Citations should reference works that can be included with our paragraphs in this repository. 18 | We accept markdown linking conventions and well known web formats that can be near universally rendered and reused. 19 | 20 | ### Downstream 21 | 22 | We expect our words to be read in a variety of formats. 23 | We author in github flavored markdown because the format is easily interpreted and the company supports open works as our own. 24 | Various reformulations will reach a broader audience and we happily accommodate their specific authoring needs. 25 | 26 | - GitHub flavored markdown. 27 | - Read the Docs by natural import. 28 | - Federated Wiki by mechanical translation. 29 | - Ebook formats to be determined. 30 | 31 | Here experts in the various formats describe writing conventions that will make best use of their mediums. 32 | We hope to meet all requirements simultaneously by a single document. 33 | We may make some exceptions but each levies a tax of distraction taking mental cycles from producing the best product. 34 | 35 | ### GitHub Markdown 36 | 37 | Cited works should be included in the repository and cited as such with a relative link and default protocol. 38 | This requires shared be checked into this repo and addressed with addresses that begin with a single slash (/}. 39 | 40 | ### Read the Docs 41 | 42 | Our tooling is having issues with the multiple H1's as we generate TOC’s from the headers. 43 | 44 | (explain the ideal here.) 45 | 46 | ### Federated Wiki 47 | 48 | This wiki expects document sections and subsections to stand alone as citable and quotable advice. 49 | We expect both # and ## titles to describe their content concisely and free of context outside of general engineering terminology. 50 | Both top-level sections are expected to begin with a shore paragraph defining the content within. 51 | We expect these paragraphs, the synopsis for sections, to read well when transcluded into the table of contents. 52 | 53 | ### Ebook formats 54 | 55 | (to be determined) 56 | 57 | ### Contributions 58 | 59 | We expect users of this material to have many of their own experiences that are valuable and worth sharing in their own right 60 | Individual communities will write to their own audiences. 61 | When this writing becomes recognizingly important we ask that it be generalized to fit a broader audience. 62 | The GitHub markdown and GitHub pull request formalisms will remain the preferred update process independent of downstream format. 63 | 64 | We further expect downstreams to follow at least major revisions and have timely releases in their own preferred format. 65 | Effective automation will simplify this so long as all authors consider the various constraints mentioned above. 66 | 67 | We are also happy to hear of successes and/or improvements independent of revisions to this work. 68 | 69 | Keep in touch. 70 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Welcome to the PIE Cookbook 2 | Howdy. We're [PIE](http://piepdx.com/), an ongoing experiment that began as a collaboration between the Portland, Oregon, US, startup community and [Wieden+Kennedy](http://wk.com/), the largest privately held creative agency in the world and creators of such iconic work as [Nike's "Just Do It,](https://en.wikipedia.org/wiki/Just_Do_It)" the [Coca-Cola polar bears](http://www.wk.com/campaign/polar_bowl/from/cocacola), and [the Old Spice Guy](http://www.wk.com/campaign/old_spice_man_man). Throughout its history, PIE has served as an early stage startup accelerator, a coworking space, a hub for community, a home away from home for visiting entrepreneurs and technologists, and a consultancy for incubator and accelerator programs from around the world. Now, we're sharing all that we've learned during nearly a decade of working with startups. We're calling it, the **PIE Cookbook**. 3 | 4 | ## Current focus (Updated December 7, 2017) 5 | 6 | **CURRENT VERSION: [PIE COOKBOOK 0.9 BETA](https://github.com/piepdx/pie-cookbook/blob/master/docs/pie-cookbook-0.9.md)** 7 | 8 | We are currently focused on: 9 | 10 | 1. Beta testing the [working draft](https://github.com/piepdx/pie-cookbook/blob/master/drafts/current/pie-cookbook-working-draft.md) and identifying gaps in content 11 | 2. Continuing to revise content in preparation for the PIE Cookbook 1.0 release. 12 | 13 | ## Creating the PIE Cookbook 14 | We’d love to have you join us in building the **PIE Cookbook**, an open source guide designed to help anyone, anywhere build the startup accelerator of their dreams. Why are we doing this? Because we believe that each and every community — with the right tools — has the potential to assist and accelerate its most promising folks further and faster toward success. 15 | 16 | And that’s good for everyone. 17 | 18 | By joining this project, you’ll gain access to everything we’ve learned from nearly a decade of accelerating startups, building relationships that strengthen community, and facilitating creative output. What’s more — since this is an open source project — you’ll have the opportunity take part in creating the most effective documentation for building, managing, and running a successful startup accelerator for your community — whatever that community may be. 19 | 20 | ## Getting started 21 | New to Github? @MugofPaul has created [a guide to help you get your bearings and learn how to contribute to the project](https://github.com/piepdx/pie-cookbook/blob/master/notes/github/howto-github.md). 22 | 23 | ## Advice for authors 24 | PIE alum and mentor @WardCunningham has provided some [advice for contributing authors](https://github.com/piepdx/pie-cookbook/blob/master/AUTHORS.md). 25 | 26 | ## Feedback 27 | We are looking forward to building this content with you. That's why we're doing this development on Github. (The actual book will reside somewhere that's more approachable.) 28 | 29 | There are three primary ways to provide feedback: 30 | 31 | 1. Join the [PIE Cookbook Slack](https://docs.google.com/forms/d/e/1FAIpQLSf7JnbN4beYeFMRo_dV4KH2TWMiWkD1KfAajJ0mT5m_w32Tfw/viewform). 32 | 2. Use the [PIE Cookbook Issues on Github](https://github.com/piepdx/pie-cookbook/issues) to comment on the content under development and track the ongoing development. 33 | 3. [Fork the repository](https://github.com/piepdx/pie-cookbook/blob/master/docs/howto-github.md), make edits, and submit pull requests. 34 | 35 | ## Structure 36 | The PIE Cookbook repository is divided into the following directories: 37 | 38 | - [/docs](https://github.com/piepdx/pie-cookbook/tree/master/docs) — Home of the master PIE Cookbook document, which feeds Read the Docs 39 | - [/drafts](https://github.com/piepdx/pie-cookbook/tree/master/drafts/) — Written content that has not yet been added to the master PIE Cookbook document 40 | - [/notes](https://github.com/piepdx/pie-cookbook/tree/master/notes/) — Notes about the project, topics to be written, feedback from participants, distillation of source materials, and parking lot items. Also, home of the [outline](https://github.com/piepdx/pie-cookbook/blob/master/notes/outline.md) governing the topics for this project. 41 | - [/source](https://github.com/piepdx/pie-cookbook/tree/master/source/) — Relevant URLs, documents, and source materials that inform the content of the PIE Cookbook 42 | 43 | ## Kickstarter 44 | This project began as a [Kickstarter campaign](https://www.kickstarter.com/projects/turoczy/pie-cookbook-an-open-source-guide-for-startup-acce) to help us attract a community of contributors who are interested in participating in this project. That campaign successfully completed on April 1, 2016. It is archived under [/notes/pie/kickstarter](https://github.com/piepdx/pie-cookbook/tree/master/notes/pie/kickstarter) for historical reference. 45 | 46 | ## About PIE 47 | For more details on who we are, visit [PIE](http://piepdx.com), follow [PIE on Github](https://github.com/piepdx), [Twitter](http://twitter.com/piepdx), or [Facebook](http://facebook.com/piepdx), or [read some of our thoughts on Medium](https://medium.com/portland-incubator-experiment). 48 | 49 | This work is licensed under [Creative Commons Attribution 4.0 International License (CC BY 4.0)](https://github.com/piepdx/pie-cookbook/blob/master/LICENSE.txt) -------------------------------------------------------------------------------- /docs/index.md: -------------------------------------------------------------------------------- 1 | # Pie Cookbook 2 | 3 | Welcome to the cookbook. 4 | -------------------------------------------------------------------------------- /docs/index.rst: -------------------------------------------------------------------------------- 1 | Welcome to PIE Cookbook 2 | ======================= 3 | 4 | .. toctree:: 5 | :maxdepth: 2 6 | :glob: 7 | 8 | * 9 | 10 | GitHub 11 | ------- 12 | 13 | You can find this document on GitHub: https://github.com/piepdx/pie-cookbook 14 | -------------------------------------------------------------------------------- /drafts/archive/0.9/working-draft-appendix.md: -------------------------------------------------------------------------------- 1 | ## Appendix 2 | 3 | 132. PIE statistics 4 | 133. PIE class breakdowns 5 | 134. Coworking 6 | 135. 88 inc 7 | 135. AppFog (acquired) 8 | 136. Bac'n (acquired) 9 | 137. Bass Masta (acquired) 10 | 138. COLOURlovers (acquired) 11 | 139. Dovie 12 | 140. Epipheo 13 | 141. Geoloqi (acquired) 14 | 142. Glider (acquired) 15 | 143. Gorlochs 16 | 144. Here File, File 17 | 145. Kickball 18 | 146. Kickstarter 19 | 147. LucentPDX 20 | 148. Maurerville 21 | 149. Mugasha 22 | 150. Paleo Plan (acquired) 23 | 151. Refresh Media 24 | 152. Showyou 25 | 153. Silicon Florist 26 | 154. Simple (acquired) 27 | 155. Sprintly (acquired) 28 | 156. Subscription Tools 29 | 157. Tindie (acquired) 30 | 158. Uncorked Studios 31 | 159. Urban Airship 32 | 160. VodPod (acquired) 33 | 161. Temporary 34 | 162. Twitter 35 | 163. Burbn/Instagram 36 | 164. PieLab 37 | 134. Apple PIE 38 | 135. Applications 39 | 136. Submitted 40 | 137. Second round 41 | 138. Interview round 42 | 139. Companies 43 | 140. Adyapper 44 | 140. Athletepath 45 | 141. Cloudability 46 | 141. DailyPath 47 | 142. Mopix 48 | 143. Revisu 49 | 142. Spotsi 50 | 143. Stayhound 51 | 144. VendScreen (acquired) 52 | 140. Mentors in residence 53 | 141. Ward Cunningham 54 | 142. Geoloqi 55 | 143. Staff 56 | 144. Rick Turoczy 57 | 145. Renny Gleeson 58 | 135. Blueberry PIE 59 | 136. Applications 60 | 136. Submitted 61 | 137. Second round 62 | 138. Interview round 63 | 139. Companies 64 | 140. AppThwack (acquired) 65 | 140. Code Scouts 66 | 141. dot dot dash (formerly Stublisher) 67 | 142. KS12 68 | 143. Little Bird 69 | 144. Lytics 70 | 144. Vadio 71 | 140. Mentors in residence 72 | 141. Staff 73 | 142. Rick Turoczy 74 | 143. Kirsten Golden 75 | 136. Coconut Creme PIE 76 | 137. Applications 77 | 136. Submitted 78 | 137. Second round 79 | 138. Interview round 80 | 139. Companies 81 | 140. Cloneless 82 | 140. Fleck 83 | 141. Orchestrate (acquired) 84 | 141. Smart Mocha (acquired) 85 | 142. Stand In 86 | 140. Switchboard 87 | 141. Teak 88 | 140. Mentors in residence 89 | 141. Staff 90 | 142. Rick Turoczy 91 | 143. Kirsten Golden 92 | 137. Derby PIE 93 | 138. Applications 94 | 136. Submitted 95 | 137. Second round 96 | 138. Interview round 97 | 139. Companies 98 | 140. Cairns 99 | 141. Droplr 100 | 142. Krumplr 101 | 143. Nutmeg (acquired) 102 | 144. Outdoor Project 103 | 145. Read the Docs 104 | 146. Shop Tender 105 | 144. Supportland 106 | 145. WANT 107 | 146. WorldState 108 | 147. XOBXOB 109 | 140. Staff 110 | 141. Rick Turoczy 111 | 142. Kirsten Golden 112 | 143. Tool Kit 113 | 132. Equipment list for space 114 | 133. Application forms 115 | 134. Assessment forms 116 | 132. Term sheets 117 | 133. Pro forma for the accelerator 118 | 134. Pro forma for the startups 119 | 135. Speeches we give time and time again 120 | 136. First day 121 | 137. How to meet 122 | 138. MVP: Minimum Valuable Product 123 | 139. Resources 124 | 140. YC open sourced documents 125 | 141. Techstars open sourced documents 126 | 142. Fostering a thriving ecosystem 127 | 143. http://www.techstars.com/content/regions/latin-america/white-paper-announcing-5-ingredients-fostering-thriving-startup-ecosystem/ 128 | 144. Pitching 129 | 145. https://nathanjeffery.net/pitch-ssg/ 130 | 146. Mentor “No solicitation” agreement 131 | 147. Request: https://github.com/piepdx/pie-cookbook/issues/2#issuecomment-213525588 132 | 148. Document: https://github.com/piepdx/pie-cookbook/blob/master/source/documents/Mentor%20Protege%2020140609.docx 133 | 143. Community 134 | 144. Startup Revolution 135 | 143. Startup Communities 136 | 140. Slack 137 | 141. http://slack.com 138 | 142. Switchboard 139 | 143. http://switchboardhq.com/ 140 | 142. IRL 141 | 143. Calagator http://calagator.org 142 | 143. http://beerandpizza.co/ 143 | 144. Meetup 144 | 141. Reportedly 145 | 142. http://reportedly.co 146 | 144. Read the Docs (you're soaking in it) 147 | 145. http://readthedocs.org 148 | 142. Google Docs 149 | 143. AngelList 150 | 144. http://angel.co 151 | 145. MentorDB 152 | 146. Dashboard 153 | 147. https://dashboard.io/ 154 | 144. PIE countdown clock 155 | 145. Open source 156 | 146. https://github.com/piepdx/board 157 | 144. Perks 158 | 145. Amazon Web Services 159 | 146. Softlayer 160 | 147. Google for Entrepreneurs 161 | -------------------------------------------------------------------------------- /drafts/archive/0.9/working-draft-glossary.md: -------------------------------------------------------------------------------- 1 | # Glossary 2 | 3 | This glossary is designed to help define regularly used terms that have a fairly static definition. In other words (ha!), these terms are not generally up to interpretation. So we will provide the standard definitions here. 4 | 5 | - associates (VC) 6 | - cap table 7 | - equity 8 | - follow-on capital 9 | - partners (VC) 10 | - pro rata 11 | - tl;dr -------------------------------------------------------------------------------- /drafts/current/working-draft-appendix.md: -------------------------------------------------------------------------------- 1 | ## Appendix 2 | 3 | 132. PIE statistics 4 | 133. PIE class breakdowns 5 | 134. Coworking 6 | 135. 88 inc 7 | 135. AppFog (acquired) 8 | 136. Bac'n (acquired) 9 | 137. Bass Masta (acquired) 10 | 138. COLOURlovers (acquired) 11 | 139. Dovie 12 | 140. Epipheo 13 | 141. Geoloqi (acquired) 14 | 142. Glider (acquired) 15 | 143. Gorlochs 16 | 144. Here File, File 17 | 145. Kickball 18 | 146. Kickstarter 19 | 147. LucentPDX 20 | 148. Maurerville 21 | 149. Mugasha 22 | 150. Paleo Plan (acquired) 23 | 151. Refresh Media 24 | 152. Showyou 25 | 153. Silicon Florist 26 | 154. Simple (acquired) 27 | 155. Sprintly (acquired) 28 | 156. Subscription Tools 29 | 157. Tindie (acquired) 30 | 158. Uncorked Studios 31 | 159. Urban Airship 32 | 160. VodPod (acquired) 33 | 161. Temporary 34 | 162. Twitter 35 | 163. Burbn/Instagram 36 | 164. PieLab 37 | 134. Apple PIE 38 | 135. Applications 39 | 136. Submitted 40 | 137. Second round 41 | 138. Interview round 42 | 139. Companies 43 | 140. Adyapper 44 | 140. Athletepath 45 | 141. Cloudability 46 | 141. DailyPath 47 | 142. Mopix 48 | 143. Revisu 49 | 142. Spotsi 50 | 143. Stayhound 51 | 144. VendScreen (acquired) 52 | 140. Mentors in residence 53 | 141. Ward Cunningham 54 | 142. Geoloqi 55 | 143. Staff 56 | 144. Rick Turoczy 57 | 145. Renny Gleeson 58 | 135. Blueberry PIE 59 | 136. Applications 60 | 136. Submitted 61 | 137. Second round 62 | 138. Interview round 63 | 139. Companies 64 | 140. AppThwack (acquired) 65 | 140. Code Scouts 66 | 141. dot dot dash (formerly Stublisher) 67 | 142. KS12 68 | 143. Little Bird 69 | 144. Lytics 70 | 144. Vadio 71 | 140. Mentors in residence 72 | 141. Staff 73 | 142. Rick Turoczy 74 | 143. Kirsten Golden 75 | 136. Coconut Creme PIE 76 | 137. Applications 77 | 136. Submitted 78 | 137. Second round 79 | 138. Interview round 80 | 139. Companies 81 | 140. Cloneless 82 | 140. Fleck 83 | 141. Orchestrate (acquired) 84 | 141. Smart Mocha (acquired) 85 | 142. Stand In 86 | 140. Switchboard 87 | 141. Teak 88 | 140. Mentors in residence 89 | 141. Staff 90 | 142. Rick Turoczy 91 | 143. Kirsten Golden 92 | 137. Derby PIE 93 | 138. Applications 94 | 136. Submitted 95 | 137. Second round 96 | 138. Interview round 97 | 139. Companies 98 | 140. Cairns 99 | 141. Droplr 100 | 142. Krumplr 101 | 143. Nutmeg (acquired) 102 | 144. Outdoor Project 103 | 145. Read the Docs 104 | 146. Shop Tender 105 | 144. Supportland 106 | 145. WANT 107 | 146. WorldState 108 | 147. XOBXOB 109 | 140. Staff 110 | 141. Rick Turoczy 111 | 142. Kirsten Golden 112 | 143. Tool Kit 113 | 132. Equipment list for space 114 | 133. Application forms 115 | 134. Assessment forms 116 | 132. Term sheets 117 | 133. Pro forma for the accelerator 118 | 134. Pro forma for the startups 119 | 135. Speeches we give time and time again 120 | 136. First day 121 | 137. How to meet 122 | 138. MVP: Minimum Valuable Product 123 | 139. Resources 124 | 140. YC open sourced documents 125 | 141. Techstars open sourced documents 126 | 142. Fostering a thriving ecosystem 127 | 143. http://www.techstars.com/content/regions/latin-america/white-paper-announcing-5-ingredients-fostering-thriving-startup-ecosystem/ 128 | 144. Pitching 129 | 145. https://nathanjeffery.net/pitch-ssg/ 130 | 146. Mentor “No solicitation” agreement 131 | 147. Request: https://github.com/piepdx/pie-cookbook/issues/2#issuecomment-213525588 132 | 148. Document: https://github.com/piepdx/pie-cookbook/blob/master/source/documents/Mentor%20Protege%2020140609.docx 133 | 143. Community 134 | 144. Startup Revolution 135 | 143. Startup Communities 136 | 140. Slack 137 | 141. http://slack.com 138 | 142. Switchboard 139 | 143. http://switchboardhq.com/ 140 | 142. IRL 141 | 143. Calagator http://calagator.org 142 | 143. http://beerandpizza.co/ 143 | 144. Meetup 144 | 141. Reportedly 145 | 142. http://reportedly.co 146 | 144. Read the Docs (you're soaking in it) 147 | 145. http://readthedocs.org 148 | 142. Google Docs 149 | 143. AngelList 150 | 144. http://angel.co 151 | 145. MentorDB 152 | 146. Dashboard 153 | 147. https://dashboard.io/ 154 | 144. PIE countdown clock 155 | 145. Open source 156 | 146. https://github.com/piepdx/board 157 | 144. Perks 158 | 145. Amazon Web Services 159 | 146. Softlayer 160 | 147. Google for Entrepreneurs 161 | -------------------------------------------------------------------------------- /drafts/current/working-draft-glossary.md: -------------------------------------------------------------------------------- 1 | # Glossary 2 | 3 | This glossary is designed to help define regularly used terms that have a fairly static definition. In other words (ha!), these terms are not generally up to interpretation. So we will provide the standard definitions here. 4 | 5 | - associates (VC) 6 | - cap table 7 | - equity 8 | - follow-on capital 9 | - partners (VC) 10 | - pro rata 11 | - tl;dr -------------------------------------------------------------------------------- /fedwiki/.gitignore: -------------------------------------------------------------------------------- 1 | pages 2 | status 3 | -------------------------------------------------------------------------------- /fedwiki/README.md: -------------------------------------------------------------------------------- 1 | # Publish to Federated Wiki 2 | These scripts provide a tuneable transformation from the draft markdown to federated wiki json schema. 3 | We expect to rerun the translations throughout the beta period as the work and the transformer evolve. 4 | The book's 1.0 release will become the starting point for divergent evolution within the federation. 5 | We hope that the best contributions there find there way back here to github. 6 | 7 | [pie.fed.wiki](http://pie.fed.wiki) 8 | 9 | # Operation 10 | Install wiki for local preview. 11 | ``` 12 | npm install -g wiki 13 | ``` 14 | Transform, preview and possibly edit result at localhost:3010 15 | ``` 16 | ruby transform.rb 17 | sh preview.sh 18 | ``` 19 | Preserve local edits to welcome pages in source control. 20 | ``` 21 | sh preserve.sh 22 | ``` 23 | Publish to the federation with sufficent ssh credentials. 24 | ``` 25 | sh publish.sh 26 | ``` 27 | 28 | # Method 29 | We use the outline formatter to understand how the work has been organized and what whole-line markdown has been employed. 30 | We map this to wiki story items by adjusting code in the transformer. 31 | We've authored several pages in wiki and saved copies of them in the welcome directory so that they survive retransformations. 32 | 33 | Issues specific to wiki or this transformation process are wecome in this [github fork](https://github.com/WardCunningham/pie-cookbook). 34 | -------------------------------------------------------------------------------- /fedwiki/outline.rb: -------------------------------------------------------------------------------- 1 | # summarize the markup of the docs 2 | # usage: ruby outline.rb 3 | 4 | File.read('../docs/pie-cookbook-0.9.md',:encoding=>'utf-8').split(/\n\s*/).each do |line| 5 | if line[0] == '#' 6 | puts "\n",line 7 | else 8 | print line[0] unless line.match /^[a-zA-Z]/ 9 | puts line.split().map {'.'}.join 10 | end 11 | end 12 | puts -------------------------------------------------------------------------------- /fedwiki/pages/.keep: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/fedwiki/pages/.keep -------------------------------------------------------------------------------- /fedwiki/preserve.sh: -------------------------------------------------------------------------------- 1 | # save preview edits to welcome pages in source control 2 | # usage: sh preserve.sh 3 | cp pages/welcome-visitors pages/ward-cunningham welcome -------------------------------------------------------------------------------- /fedwiki/preview.sh: -------------------------------------------------------------------------------- 1 | # launch localhost:3010 server to preview site 2 | # usage: sh preview.sh 3 | wiki -p 3010 -d . --security_legacy -------------------------------------------------------------------------------- /fedwiki/publish.sh: -------------------------------------------------------------------------------- 1 | # publish welcome and pages to public site replacing all existing content 2 | # usage: sh publish.sh 3 | 4 | ssh asia 'rm .wiki/pie.fed.wiki/pages/*' 5 | scp pages/* asia:.wiki/pie.fed.wiki/pages 6 | ssh asia 'rm .wiki/pie.fed.wiki/status/sitemap.*' 7 | -------------------------------------------------------------------------------- /fedwiki/status/favicon.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/fedwiki/status/favicon.png -------------------------------------------------------------------------------- /fedwiki/transform.rb: -------------------------------------------------------------------------------- 1 | # translate and upload to pie.fed.wiki 2 | # usage: ruby transform.rb 3 | 4 | require 'open3' 5 | require 'json' 6 | 7 | # wiki utilities 8 | 9 | def random 10 | (1..16).collect {(rand*16).floor.to_s(16)}.join '' 11 | end 12 | 13 | def slug title 14 | title.gsub(/\s/, '-').gsub(/[^A-Za-z0-9-]/, '').downcase() 15 | end 16 | 17 | def clean text 18 | text.gsub(/’/,"'") 19 | end 20 | 21 | def url text 22 | text.gsub(/(http:\/\/)?([a-zA-Z0-9._-]+?\.(net|com|org|edu)(\/[^ )]+)?)/,'[http:\/\/\2 \2]') 23 | end 24 | 25 | def domain text 26 | text.gsub(/((https?:\/\/)(www\.)?([a-zA-Z0-9._-]+?\.(net|com|org|edu|us|cn|dk|au))(\/[^ );]*)?)/,'[\1 \4]') 27 | end 28 | 29 | def titalize text 30 | excluded = %w(the this that if and or not may any all in of by for at to be) 31 | text.capitalize! 32 | text.gsub! /[\[\]]/, '' 33 | text.gsub(/[\w']+/m) do |word| 34 | excluded.include?(word) ? word : word.capitalize 35 | end 36 | end 37 | 38 | 39 | # journal actions 40 | 41 | def create title 42 | @journal << {'type' => 'create', 'id' => random, 'item' => {'title' => title}, 'date' => Time.now.to_i*1000} 43 | end 44 | 45 | def add item 46 | @story << item 47 | @journal << {'type' => 'add', 'id' => item['id'], 'item' => item, 'date' => Time.now.to_i*1000} 48 | end 49 | 50 | 51 | # story emiters 52 | 53 | def paragraph text 54 | return if text =~ /^\s*$/ 55 | text.gsub! /\r\n/, "\n" 56 | add({'type' => 'paragraph', 'text' => text, 'id' => random()}) 57 | end 58 | 59 | def pagefold text, id = random() 60 | text.gsub! /\r\n/, "" 61 | add({'type' => 'pagefold', 'text' => text, 'id' => id}) 62 | end 63 | 64 | def markdown text 65 | add({'type' => 'markdown', 'text' => text, 'id' => random()}) 66 | end 67 | 68 | def html text 69 | add({'type' => 'html', 'text' => text, 'id' => random()}) 70 | end 71 | 72 | def page title 73 | @story = [] 74 | @journal = [] 75 | create title 76 | yield 77 | page = {'title' => title, 'story' => @story, 'journal' => @journal} 78 | path = "pages/#{slug(title)}" 79 | File.open(path, 'w') do |file| 80 | file.write JSON.pretty_generate(page) 81 | end 82 | end 83 | 84 | 85 | # transformation 86 | 87 | def ref title 88 | doc = 'https://github.com/WardCunningham/pie-cookbook/blob/master/docs/pie-cookbook-0.9.md' 89 | "[#{doc}##{slug(title)} .]" 90 | end 91 | 92 | `rm pages/*` 93 | @lines = File.read('../docs/pie-cookbook-0.9.md',:encoding=>'utf-8').split(/\n\s*/) 94 | it = {} 95 | toc = ["We assemble this page while transforming the remainder of the work. The work's own contents, assembled by other means, appears among the following."] 96 | 97 | while @lines.length > 0 98 | line = @lines.shift 99 | if m = line.match(/^# +(.*)$/) 100 | toc << "# [[#{titalize m[1]}]] #{ref m[1]}" 101 | toc << @lines[0] 102 | pge = it[titalize m[1]] = [] 103 | elsif m = line.match(/^## +(.*)$/) 104 | sub = m[1] 105 | sub = "Original #{m[1]}" if m[1] == 'Table of contents' 106 | toc << "[[#{titalize sub}]] #{ref m[1]}" 107 | pge = it[titalize sub] = [] 108 | else 109 | pge << line 110 | end 111 | end 112 | 113 | it['Table of Contents'] = toc 114 | it.each do |title, story| 115 | page title do 116 | story.each do |line| 117 | line.gsub! /\[(.*?)\]\((.*?)\)/, '[\2 \1]' 118 | line.gsub! /\[#.*? (.*?)\]/, '[[\1]]' 119 | if m = line.match(/^(#|\-|\*)/) 120 | markdown line 121 | elsif m = line.match(/^>\s*(.*)$/) 122 | html "
#{m[1]}
" 123 | elsif m = line.match(/^!\[(\/.*?) .*?\]/) 124 | html "" 125 | else 126 | paragraph line 127 | end 128 | end 129 | end 130 | end 131 | 132 | `cp welcome/* pages` -------------------------------------------------------------------------------- /notes/community/README.md: -------------------------------------------------------------------------------- 1 | # README.md 2 | We'll use this section to capture notes as we're brainstorming about a certain topic — and potentially other spots throughout the development of the documentation. 3 | 4 | It's just one big parking lot. 5 | 6 | To prevent any confusion with versioning, any content from this section that has already moved downstream to the document, itself, will be captured in the /archive directory under each topic. 7 | 8 | NOTE: This may result in different iterations of the same concept appearing in multiple files over time. We will normalize this as the content moves downstream into the final documentation. 9 | -------------------------------------------------------------------------------- /notes/community/archive/2016-05-23-Initial-Community-Content-Sprint.md: -------------------------------------------------------------------------------- 1 | # Community 2 | Capturing some of the initial thinking and brainstorming around the topic of "community." 3 | 4 | ## Discussion 5 | 6 | - The accelerator should be a reflection of the community 7 | - It's a means of catalyzing existing community 8 | - Be honest about your community 9 | - You can only work with what you've got 10 | - You have to start with the ingredients your community has, but you don't need to follow the existing community momentum 11 | - You're allowed to bring different ingredients into the community, but the initial activity must start with existing assets 12 | - Some of your community assets may have never combined before (e.g., Portland startup community and W+K), but they're still both assets to be considered 13 | - Once that community is identified, how do you engage with it? 14 | 15 | ## Outline 16 | 17 | - 1.i.a. 18 | - 1.i.h. Risks 19 | - 1.ii.e.b. Community 20 | - 1.iii.b.a.a. Startup Communities 21 | - 3. Kitchen Prep 22 | - 4.ii.a. Community 23 | - 4.v.a. Cocktails (community engagement) 24 | - 4.v.b. Hors d'oeuvre (Hackathons, events, coworking) 25 | - Appendix 11.vi. Community -------------------------------------------------------------------------------- /notes/community/archive/brands-role-in-community.md: -------------------------------------------------------------------------------- 1 | # Brands are part of the community, independent of the community, and a community in their own right — all at the same time 2 | 3 | One of the most challenging aspects of working with brands — our lingo for for-profit corporations — is that they can play multiple roles in a community, no role whatsoever, or perform as an insular community all by themselves. This makes them both an intriguing and attractive partner for accelerators — but can make them an equally frustrating partner, as well. 4 | 5 | Proceed with caution. But definitely proceed if the opportunity avails itself. 6 | 7 | ## Part of the community 8 | 9 | ## Independent of the community 10 | 11 | ## Brand as community 12 | 13 | Like any community, brands have to honestly assess what assets they bring to the table, as far as accelerators go. In our experience, this process can be as difficult — if not mores — than a typical community assessing its strengths and weaknesses. 14 | 15 | Generally, this assessment results in two outcomes — neither of which is terribly honest. 16 | 17 | One outcome is that the brand thinks it has every asset at its disposal. And therefore, can engage in any type of accelerator it chooses. This hubris, while understandable, is often incorrect. No matter how global the brand, it is highly likely that the brand is expert in certain areas. And it is this expertise that the brand show focus on as the key asset. 18 | 19 | Even more challenging? This key asset is often the thing the brand finds to be the most boring part of its business. 20 | 21 | We'll get into that later. 22 | 23 | The second outcome is the polar opposite of the first. And it occurs with all sizes of companies, even global brands. That outcome is the assumption that the company isn't "innovative" or that it has no assets that would be of use to a startup or early stage founder. 24 | 25 | These are brands that either 1) choose not to play at all or 2) determine the only way to engage with the startup community is to outsource the effort to a third party that "gets it." 26 | 27 | Like the first outcome, this flawed assumption is a result of the brand not being honest about what assets it possesses and how those assets might be applied to help startups. 28 | -------------------------------------------------------------------------------- /notes/community/archive/cocktails.md: -------------------------------------------------------------------------------- 1 | # Cocktails 2 | 3 | (Setting up the analogy for the community engagement portion of the PIE Cookbook.) 4 | 5 | A lot of folks dive into this whole accelerator thing thinking they can just start with the accelerator. 6 | 7 | "Hey! Hey you! We’ve got an accelerator. Come get accelerated and stuff!" 8 | 9 | It doesn’t work that way. Any more than starting your fancy dinner party with a big ol’ main course gets the conversation going. 10 | 11 | That’s why you need to do some work warming up the crowd. And getting people to know one another before you dive into a more intimate setting like an accelerator. Otherwise, it will just be a bunch of people sitting around quietly chewing their food. Uncomfortably. And you’ll feel like a complete failure. 12 | 13 | So how do you break the ice? Here are some ideas that PIE used in the early days to get the conversation going. 14 | -------------------------------------------------------------------------------- /notes/community/archive/community-as-an-asset.md: -------------------------------------------------------------------------------- 1 | Community is not an asset that you mine indiscriminately like some wealthy oil baron. Community is the sourdough starter. Community is where you leave some part of you behind to make the next event — even the next encounter — even better. -------------------------------------------------------------------------------- /notes/community/archive/community-notes.md: -------------------------------------------------------------------------------- 1 | 2 | # Community 3 | 4 | When we talk about community, we are talking about physical community. A group of people coming together in a shared space or consistent, shared experience some kind, in a consistent physical location, where actual people interact with other actual people. 5 | 6 | ## Random collisions? 7 | 8 | **An accelerator needs a community, but it will not create one**. 9 | 10 | Lots of accelerators get started with the quixotic notion that an accelerator will attract vibrant, excited entrepreneurs wherever the shingle gets hung out. 11 | 12 | But the simple reality is that an accelerator project will not create a community. 13 | 14 | Instead, you are carving out a subset of an existing community to create a more tightly knit one. But that initial community must exist for there to be any subset of it. 15 | 16 | Startups won’t magically know about a new one and be interested - especially if there’s no existing track record of previous success; time-strapped VC’s will not be drawn magically, mentors will not always see it as their civic duty to give free time to a bunch of long shots, government and local entities are typically focused on job creation which is often a lagging indicator. It's highly likely that your first ‘demo day’, should you choose to have one, will not be oversubscribed. Because communities don't work that way. 17 | 18 | Communities are particular. Communities are fueled by shared purpose.Think about the ones that matter to you - school, work, religion, family. Shared purpose makes small talk easy. So before you start your accelerator, think long and hard about the community you hope to catalyze. 19 | 20 | Because while an accelerator won’t create a community, it can be a powerful catalyst for existing ones, or supercharge a nascent one. 21 | 22 | 23 | ## Accelerator as Community Catalyst 24 | 25 | 26 | Be honest about the community you have 27 | 28 | “Trying to create the next Silicon Valley” 29 | 30 | 31 | ...but dont be trapped by the community you have 32 | Had we taken the pulse of the community alone, we’d have started an Open Source accelerator 33 | 34 | 35 | Consider mixing and matching community components to catalyze new territories 36 | 37 | PIE grew out of a community. A few of them, actually. A disgruntled OpenSource gang, some frustrated co-founders, an agency community looking to engage meaningfully with startups. 38 | 39 | Why would a brand give a shit? Outcomes? Issues? Opportunities? 40 | Hack days 41 | 42 | “Free R&D” 43 | 44 | Everyone hates the innovator -------------------------------------------------------------------------------- /notes/community/archive/curated-coworking.md: -------------------------------------------------------------------------------- 1 | # Curated coworking 2 | 3 | Via @enam 4 | 5 | I am adding this because it applies to our venture of curated co-working, I am curious about the process you used for a curated co-working location (back when that described what you were). Our goal is one of high quality curated membership. 6 | 7 | I imagine the topic of curation applies to the incubator situation as well and that many backers would be interested to get a window into the process for soliciting and vetting members/participants that you have found to be most successful. 8 | 9 | Via @turoczy 10 | 11 | Thanks for suggesting this! We definitely have plans to touch on that experiment in PIE's history but we'll make sure to be more explicit about how the curated coworking worked. I think the most important thing we learned is that coworking and community development, rather than being complementary, are often at odds with one another. 12 | 13 | https://github.com/piepdx/pie-cookbook/issues/3 14 | -------------------------------------------------------------------------------- /notes/community/archive/environmental-scan.md: -------------------------------------------------------------------------------- 1 | # Taking an environmental scan 2 | 3 | So we keep hammering on this "you have to build an accelerator *within* an existing community" point. Because we think it's important. But once you've identified the community that is to be the protective ecosystem in which you will build your accelerator, what then? 4 | 5 | Well, recognizing the community is just the first step. Next, you have to assess the community. What are its assets? What are its shortcomings? 6 | 7 | Before you get visionary, you need to be realistic. So let's start there. With reality. 8 | 9 | This can be fairly ad hoc. You don't need to engage with a bunch of high priced consultants to run focus groups and surveys on your community. Or anthropologists, sociologists, and economists who embed themselves within your community. If you want to do formal, do formal. But it doesn't have to be. 10 | 11 | What you're hoping to answer is two very simple questions: 12 | 1. What resources does your community have? Or, to put it another way, where are the opportunities? 13 | 2. What resources are we missing? In other words, where are the gaps? 14 | 15 | ## Existing resources 16 | 17 | A resource is great. But they fall on a spectrum. And understanding how mature that resource is can be critical. 18 | 19 | You may have a few angel investors in town. But that doesn't mean you have an investment community. You may have a few startups in your community. That doesn't mean you have deal flow. 20 | 21 | Even more importantly, are these resources even accessible? 22 | 23 | The apparel industry in Portland, for example — with Nike, Adidas, Columbia, and Under Armour, among others, all boasting significant reach in town — is a hugely valuable asset. But for the most part, that asset of knowledge and an extremely seasoned mentor pool is largely inaccessible to many of the communities in Portland. 24 | 25 | Since it's an asset that can only be accessed by a small subset of the broader community — and since that isn't our community — it's not really an asset. 26 | 27 | So if we got some cockamamie scheme to try to build an apparel accelerator we'd be out of luck. That's not our community. Those aren't our people. And we're not their's. And as such, we'd have no ability to activate that asset. 28 | 29 | What's that mean? That's right. That's not really an asset, is it? To put it another way, an asset is only an asset if your community and accelerator can immediately leverage those resources. 30 | 31 | People most often seem to stumble here in terms of capital. If we had a dollar for every accelerator that tried to start a helping a highly capital intensive market with little to no capital assets at their disposal, PIE would be a late stage venture fund. 32 | 33 | If you don't have capital, don't engage in pursuits that capital intensive. If you don't have the asset, don't plan on that asset somehow becoming magically available. Anymore than you should expect community to magically form around an accelerator. 34 | 35 | Use, as the phrase goes, what you've got. 36 | 37 | ## Multipurpose every asset you can 38 | 39 | What's more, it's highly likely that you're not going to just want to use that asset in a single way. You want to get as much combined value out of each asset as you can. And to ensure that the asset is deriving value from he relationship. 40 | 41 | So ideally, you'll be seeking to leverage those assets in four ways: 42 | - To the benefit of the early stage founders 43 | - To the benefit of the asset 44 | - To the benefit of the accelerator 45 | - To the benefit of the community as a whole 46 | 47 | ## Existing gaps 48 | Where are the gaps? 49 | Are they solvable? 50 | How entrenched are they? 51 | Create one of those annoying Venn diagrams, because those things are a thing for a reason. They actually can help you visualize where the opportunity exists. 52 | Then you can get visionary 53 | 54 | # Having a problem assessing the community assets and needs? 55 | 56 | Starting a coworking space is a great way to start to unearth some of the assets and gaps in the community. -------------------------------------------------------------------------------- /notes/community/archive/startup-communities.md: -------------------------------------------------------------------------------- 1 | If you haven't read Startup Communities by Brad Feld, please take the time to do so. Many of the things we did accidentally in Portland — or things which happened by luck — are clearly articulated in the book. If you're working to develop and support a nascent community, Feld's book provides a critical roadmap for that development — as well as delineating a timeline for how long you should expect that development to take. -------------------------------------------------------------------------------- /notes/context/README.md: -------------------------------------------------------------------------------- 1 | # README.md 2 | We'll use this section to capture notes as we're brainstorming about a certain topic — and potentially other spots throughout the development of the documentation. 3 | 4 | It's just one big parking lot. 5 | 6 | To prevent any confusion with versioning, any content from this section that has already moved downstream to the document, itself, will be captured in the /archive directory under each topic. 7 | 8 | NOTE: This may result in different iterations of the same concept appearing in multiple files over time. We will normalize this as the content moves downstream into the final documentation. 9 | -------------------------------------------------------------------------------- /notes/context/archive/context-definitions.md: -------------------------------------------------------------------------------- 1 | # Definitions 2 | 3 | We feel that it is extremely important to have a consistent set of language to describe the concepts and participants in this process. Without clear definitions, we run the risk of miscommunication — even when we think that we’re speaking the same language. 4 | 5 | For that reason, we're going to provide you with some definitions of terms that are regularly used throughout the PIE Cookbook. Please note that, like all things in this document, we are simply providing this as a reference. We would encourage you to create your own set of definitions for your specific needs. 6 | 7 | ## Community 8 | Community can refer to any group of individuals who hold common goals and are motivated to collaborate to achieve those goals. There is no specified size for a community. And communities can be nested within other communities — or overlap. Therefore, it is always important to test the assumptions of toward what the "community" is working. 9 | 10 | > e.g., The Portland technology community has subsets like the Portland open source community and the Portland tech startup community. There is significant crossover between the open source community and the tech startup community, but they do not share exactly the same goals. 11 | 12 | A community simply has to have a focus. It can revolve around concepts, ideals, goals, brands, or any combination thereof. We see community, at its essence, as a group of people with a shared, collaborative vision. 13 | 14 | ## Incubator 15 | An incubator is a protected work environment designed to shelter founders and ideas as they work to realize concepts and prototypes. There is no "business" yet. There are simply ideas and potential. 16 | 17 | Incubators are designed to help early stage ideas survive longer than they would in the wild, independent of shelter. As such, an incubator does not accurately reflect the stressors and turmoil of the real world. Instead, it seeks to shield founders from reality by providing resources that best ensure its likelihood of finding commercial applications of its concept(s). This is by design. 18 | 19 | > e.g., University tech transfer programs tend to be a good example of incubators 20 | 21 | Although PIE has "incubator" in its name, that's a misnomer. We simply couldn't come up with a phrase that worked for PAELLA. 22 | 23 | ## Accelerator 24 | An accelerator is a semi-protective environment that behaves as a microcosm of the real world, at a highly increased rate of speed. It is designed to help founders rapidly address issues impacting their businesses — and help them to better understand how to deal with personalities and adversity in the real world. 25 | 26 | > Accelerators are not designed to protect founders from the elements of the startup world. They are designed to expose founders to those elements, time and time again in rapid succession. 27 | 28 | To quote Techstars, accelerators, by their very nature, are designed to help companies "do more, faster." They are designed to make founders uncomfortable. And to push founder to do and achieve more — or fail — more rapidly than they would be capable of on their own. 29 | 30 | ## Mentor 31 | ## Advisor 32 | ## Investor 33 | ### Angel 34 | ### Venture Capital 35 | ### Institutional Capital 36 | ### Private Equity 37 | ## Startup 38 | ## Founder 39 | ## Resident 40 | ## Patron 41 | ## Sponsor 42 | ## Partner 43 | -------------------------------------------------------------------------------- /notes/context/foreword.md: -------------------------------------------------------------------------------- 1 | # Foreword 2 | 3 | TBD 4 | -------------------------------------------------------------------------------- /notes/funding/README.md: -------------------------------------------------------------------------------- 1 | # README.md 2 | We'll use this section to capture notes as we're brainstorming about a certain topic — and potentially other spots throughout the development of the documentation. 3 | 4 | It's just one big parking lot. 5 | 6 | To prevent any confusion with versioning, any content from this section that has already moved downstream to the document, itself, will be captured in the /archive directory under each topic. 7 | 8 | NOTE: This may result in different iterations of the same concept appearing in multiple files over time. We will normalize this as the content moves downstream into the final documentation. 9 | -------------------------------------------------------------------------------- /notes/github/howto-github-img/000-forkrepo.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/notes/github/howto-github-img/000-forkrepo.gif -------------------------------------------------------------------------------- /notes/github/howto-github-img/001-forkedrepo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/notes/github/howto-github-img/001-forkedrepo.png -------------------------------------------------------------------------------- /notes/github/howto-github-img/002-creatingnewfile.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/notes/github/howto-github-img/002-creatingnewfile.gif -------------------------------------------------------------------------------- /notes/github/howto-github-img/003-editingexisting.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/notes/github/howto-github-img/003-editingexisting.gif -------------------------------------------------------------------------------- /notes/github/howto-github-img/004-forkaheadofmaster.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/notes/github/howto-github-img/004-forkaheadofmaster.png -------------------------------------------------------------------------------- /notes/github/howto-github-img/005-createpullrequest.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/notes/github/howto-github-img/005-createpullrequest.png -------------------------------------------------------------------------------- /notes/github/howto-github-img/006-createpullrequestbutton.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/notes/github/howto-github-img/006-createpullrequestbutton.png -------------------------------------------------------------------------------- /notes/github/howto-github-img/007-pullrequestscreen.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/notes/github/howto-github-img/007-pullrequestscreen.png -------------------------------------------------------------------------------- /notes/github/howto-github-img/007a-openpullrequest.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/notes/github/howto-github-img/007a-openpullrequest.png -------------------------------------------------------------------------------- /notes/github/howto-github-img/008-commitsbehind.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/notes/github/howto-github-img/008-commitsbehind.png -------------------------------------------------------------------------------- /notes/github/howto-github-img/009-switchthebase.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/notes/github/howto-github-img/009-switchthebase.png -------------------------------------------------------------------------------- /notes/github/howto-github-img/010-createreversepullrequest.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/notes/github/howto-github-img/010-createreversepullrequest.png -------------------------------------------------------------------------------- /notes/github/howto-github-img/011-reversepullrequestform.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/notes/github/howto-github-img/011-reversepullrequestform.png -------------------------------------------------------------------------------- /notes/github/howto-github-img/012-pullrequesttab.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/notes/github/howto-github-img/012-pullrequesttab.png -------------------------------------------------------------------------------- /notes/github/howto-github-img/013-acceptpullrequest.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/notes/github/howto-github-img/013-acceptpullrequest.png -------------------------------------------------------------------------------- /notes/logistics/00_README.md: -------------------------------------------------------------------------------- 1 | # README.md 2 | We'll use this section to capture notes as we're brainstorming about a certain topic — and potentially other spots throughout the development of the documentation. 3 | 4 | It's just one big parking lot. 5 | 6 | And since we're winding up with a lot of disparate notes as we build this out, we've decided to add [an index to help folks get through the content](01_index.md). We'll do our best to keep this document up-to-date as more notes are added. 7 | 8 | To prevent any confusion with versioning, any content from this section that has already moved downstream to the document, itself, will be captured in the /archive directory under each topic. 9 | 10 | NOTE: This may result in different iterations of the same concept appearing in multiple files over time. We will normalize this as the content moves downstream into the final documentation. 11 | -------------------------------------------------------------------------------- /notes/logistics/01_index.md: -------------------------------------------------------------------------------- 1 | # Index 2 | 3 | - [Staff roles and responsibilities](archive/pie-staff-roles-responsibilities.md) 4 | - [Creating a cadence](archive/cadence-timing.md) 5 | - [What to expect when you're expecting a startup](archive/onboarding-startups.md) 6 | - [Meeting with Mentors](archive/guide-mentors-meeting-with.md) 7 | - [Typical week](archive/logistics-typical-week.md) 8 | - [Family Dinner](archive/logistics-family-dinner.md) 9 | - [Lunch and Learns](archive/logistics-lunch-and-learns.md) 10 | - [Bonding](archive/logistics-enforced-socializing-with-peers.md) 11 | - [Demo Day](archive/logistics-demo-day.md) 12 | - [Post mortem](archive/logistics-post-mortem.md) 13 | 14 | ## Communications with startups 15 | 16 | ### Recruiting startups 17 | 18 | - [Application/Cheat sheet](pie-application-cheat-sheet.md) 19 | - [Open applications](letter-applications-open.md) 20 | - [Applications due (two weeks out)](letter-applications-two-weeks.md) 21 | - [Applications due (one week out)](letter-application-one-week.md) 22 | - [Mistakes were made](letter-technical-issues.md) 23 | 24 | ### Onboarding startups 25 | 26 | - [Onboarding](archive/onboarding.md) 27 | - [Acceptance letter](onboarding-acceptance-letter.md) 28 | - [What to expect](onboarding-what-to-expect.md) 29 | - [What you're getting yourself into](onboarding-what-youre-getting-in-to.md) 30 | 31 | ## Demo Day communications 32 | 33 | - [Invitation](letter-demo-day-invite.md) 34 | - [Reminder](letter-demo-day-logistics.md) 35 | - [Livestream](letter-demo-day-livestream-reminder.md) 36 | - [Follow up](letter-demo-day-follow-up.md) -------------------------------------------------------------------------------- /notes/logistics/archive/guide-mentors-meeting-with.md: -------------------------------------------------------------------------------- 1 | # Meeting with mentors 2 | 3 | Are you interested in engaging with mentors? Good. That's what we're here to do. 4 | 5 | Here are a some tips: 6 | 7 | ## OVERALL 8 | - These folks are volunteering their time because they want to give back to the community. Please be cognizant and respectful of this contribution. 9 | - Please understand that while our program is a priority for them, they have day jobs and families and whatnot. 10 | - Following the deep dive meetings, management has compiled a list of mentors who will be helpful to your startup. We will make those introductions on an ongoing basis. Please use one of the two methods below for engaging with those mentors. 11 | - If you’re not finding mentors who meet your needs, please alert management with your concerns and we will recruit mentors to assist with your particular situation. 12 | - Shit happens. Sometimes they’ll need to cancel and/or reschedule. 13 | 14 | ## OFFICE HOURS 15 | - Keep tabs on the Office Hours page and be on the lookout for mentors who you find interesting 16 | - If management staff sees a mentor with office hours who would be beneficial for you, we’ll generally nudge you to set up some time. 17 | - Once you’ve secured time, confirm the time and place via email. Mentors are busy and sometimes a single email gets lost in the fray. 18 | - Do one last follow up/confirmation via email evening before/morning of your meeting. 19 | - Following the Office Hours, send a follow up email touching on any salient points. 20 | - Fill out the mentor feedback form 21 | https://docs.google.com/forms/d/1vwn3OQRAiZbGaDNYUt38BOkdPVqnmMG77qRLJMXFnW0/viewform 22 | 23 | ## AD HOC MENTOR MEETINGS 24 | 25 | Need an intro? 26 | 27 | The database was designed to be an easy way of searching through the mentor network. Feel free to search through and find folks who are of interest to you. 28 | 29 | Ping management with requests for introduction or schedule time via mentor’s office hours 30 | 31 | Once you’re introduced… 32 | 33 | - Once management makes an email introduction, immediately follow up to schedule a time and place with the mentor. 34 | - Do one last follow up/confirmation via email evening before/morning of your meeting. 35 | - Following the Office Hours, send a follow up email touching on any salient points. 36 | - Fill out the mentor feedback form 37 | 38 | 39 | 40 | 41 | -------------------------------------------------------------------------------- /notes/logistics/archive/logistics-enforced-socializing-with-peers.md: -------------------------------------------------------------------------------- 1 | # Encouraging/enforcing bonding with peers 2 | 3 | This is an important part of our program and one that we feel is often overlooked by others. We believe that we aren’t just graduating individual companies from our program, but collaborative groups who will improve and enhance our existing community. 4 | 5 | But this doesn't necessarily happen organically. It takes effort. And intent. That's why we've learned to put time into creating opportunities that enable those peer bonds to form, even on a short timescale. 6 | 7 | We've also learned that it’s important to use a range of bonding activities. A beer or cocktail is fine every once in a while, but it's important to break out of the startup stereotype. Plan activities that don’t just involve drinking. Heck, maybe even plan some activities that are healthy (gasp) or educational. 8 | 9 | The basic rule is: Be inclusive. And provide a range of options. Not every option will work for every participant. 10 | 11 | Below is a list of things we’ve done. 12 | 13 | ## Activity examples 14 | 15 | ### Cooking class 16 | With a name like PIE, it should come as little surprise that a number of our activities revolve around food. And when you have that much creative talent in one room, sometimes it's refreshing to give folks a different outlet for that creativity — especially one that doesn't involve banging on a keyboard. 17 | 18 | One activity that met both our food and creativity needs was a cooking class. For the first couple of years, we partnered with a local food accelerator that had commercial kitchen space. They put together a menu, taught our founders to prepare a dish from scratch, and then the entire group had the opportunity to share in the creations, family style. 19 | 20 | Everyone — no matter how well attuned they were to a kitchen — was out of his or her element. And it put everyone on equal footing. Best of all, there were always a few unexpected surprises when we discovered the true chefs in our midst. 21 | 22 | Each year we did this resulted in the best family dinner of the class. 23 | 24 | ### Alumni vs new class kickball or picnic 25 | ### Away from the computer/office activities 26 | ### Mixers + happy hours 27 | we’ve done hot sauce tasting, cheese and wine pairings, etc 28 | 29 | ### Family open house 30 | a lot of program companies have families. It’s nice to give family and friends an opportunity to check out the space 31 | 32 | Admittedly we could do a better job of fostering the community among all of our classes, but at the very least there is an understanding that they can count on one another for support. 33 | -------------------------------------------------------------------------------- /notes/logistics/archive/logistics-lunch-and-learns.md: -------------------------------------------------------------------------------- 1 | # Lunch and Learns 2 | 3 | Sometimes a mentor talk, other times a workshop, lunch and learns are scheduled twice a week during the three month program during the lunch hour. Speakers can range from founders with anecdotal “war stories” to subject matter experts. We often bring our higher profiled mentors in for these talks, as it is easier to schedule for them. These are some of the most valuable learning opportunities of the program. 4 | 5 | Despite how straightforward these sessions sound, we’ve discovered a few snags. There is a chance that any given topic, might not be something a company is dealing with that particular day or week, but trust us, they will – and when they are dealing with it, they might not have a chance to meet with that mentor again. This is one of those; take advantage of the opportunity while you have it, moments. 6 | 7 | Teams will be busy and claim they just don’t have the time for another meeting. Again, see above. These opportunities aren’t always on the table so they should be treated as such. 8 | 9 | Active engagement is crucial for the companies and for the speakers. A silent room means that your companies aren’t paying attention or asking questions and maybe even more importantly, it means that your speaker is wasting their time and becoming less and less likely to mentor for your program again. We ask our companies to step away from their machines and actively listen / take notes when during the session – it’s only an hour. 10 | 11 | Oh, and don’t forget to supply lunch – as it’s in the name and presents an opportunity for peer mentoring among the companies or a chance to talk more with the speaker. We’ve found it's best served before the talk. 12 | 13 | This doesn’t have to be mentor led. This can be peer led. Some of the most interesting lunch and learns are peer led. 14 | 15 | Example topics: 16 | - Getting the most out of an accelerator 17 | - Pricing Model roundtable – multiple mentors 18 | - The importance of documentation 19 | - Minimum “Valuable” Product 20 | - Founder Talks 21 | - Business Development 101 22 | - Presenting 101 23 | - PR 101 -------------------------------------------------------------------------------- /notes/logistics/archive/logistics-post-mortem.md: -------------------------------------------------------------------------------- 1 | # Post mortem 2 | 3 | If you’ve done your work on pitch practice correctly, your startups will be primed to turn the tables on you. 4 | 5 | > “You critiqued my pitch? Let me critique your job.” 6 | 7 | At PIE, we even couch it as such. Like pitch practice, PIE staff may not respond to any criticism during the post mortem. We can take notes and ask for clarification on feedback. But we are not permitted to try to explain away any blemishes the startups describe. Nor are we allowed to defend our actions. 8 | 9 | Not saying that all of the feedback is negative. Quite the opposite. But after the first thirty minutes or so, the founders start to run out of niceties. And then they get down to provide the truly valuable feedback. 10 | 11 | We receive feedback over the course of an hour to ninety minutes from each startup, preferably with all members of the founding team. If necessary, we meet with founders separately and then consolidate the feedback. 12 | 13 | Then we look for common themes and concerns. We place role-specific elements into buckets. Like if the CTOs all referenced a particular aspect of the program. Or if the majority of the CEOs had a similar complaint. 14 | 15 | We're looking for things that we need to change to make the program more effective. Not easier. Not less stressful. But more effective. 16 | 17 | To this end, we can almost guarantee that one of the most consistent pieces of feedback you will receive throughout the post mortem process is “I wish you would have told us [x] sooner” or “If only I’d be taught [x] earlier in the class.” 18 | 19 | Rest easy. Had you told them any earlier, they wouldn’t have heard you. They would have ignored it. Or they would have believed that the problem would never affect them. 20 | 21 | Don’t believe us? Try telling your next class earlier and see what happens. 22 | 23 | -------------------------------------------------------------------------------- /notes/logistics/archive/logistics-typical-week.md: -------------------------------------------------------------------------------- 1 | # Typical week in PIE 2 | 3 | We often get asked, "What's a typical week like in an accelerator?" And while the term "typical week" is an oxymoron for PIE, there are some things that occur with enough regularity — and provide enough structure for participants — that we can describe them. 4 | 5 | So here's an imperfect look at a typical week at PIE: 6 | 7 | ## Monday 8 | 9 | 8:00AM 10 | Staff arrives, meets about week's upcoming events. Some startups are already working. 11 | 12 | 10:00AM 13 | Workspace is full. All startups have arrived. Staff holds one-on-one meetings with each team. 14 | 15 | 5:00PM 16 | Family Dinner starts. Founders and staff leave the workspace to have dinner together. Non-founding team members remain in the space working. 17 | 18 | 7:00PM 19 | Family Dinner ends. Startups return to workspace and continue working. Staff returns to space. Compares notes. Continues peer mentoring momentum from Family Dinner. 20 | 21 | 8:00PM Workspace is about half full with the founders who prefer the late shift. Staff remains online in the chat room or accessible via email. 22 | 23 | ## Tuesday 24 | 25 | 8:00AM Staff arrives. Continues making mentor connections for startups based on issues raised during family dinner. Typically two or three mentors per startup per issue. 26 | 27 | 10:00AM Workspace is full. 28 | 29 | 12:00PM Catered lunch in the workspace. Some startups sit together and chat. Others simply eat at their desks. (Their is no required socializing. Just a request that the founders take time to eat.) 30 | 31 | 1:00PM Anecdotal founder story from a PIE mentor, followed by Q&A. 32 | 33 | 2:30PM Return to work. Mentors often remain behind to continue the conversation with a startup or two. 34 | 35 | 7:00PM Staff and startups start to thin out in the workspace. Staff remains online in the chat room or accessible via email. 36 | 37 | ## Wednesday 38 | 39 | 8:00AM Work day for startups and staff. Staff arrives. Checks in on progress. Spends day meeting with mentors, potential mentors, alums, and future recruits. 40 | 41 | 10:00AM Startups working in the workspace. 42 | 43 | 11:00AM Random visitor pings staff. Staff invites the visitor to grab a desk and hang out in PIE for the day. 44 | 45 | 1:00PM Random visitor provides an informal talk and Q&A for startups. 46 | 47 | 2:30PM Startups working in workspace. Staff meetings with W+K account and creative teams. 48 | 49 | 5:00PM Startups encouraged to attend a targeted community event and spend time networking with the rest of the Portland tech community. Staff suggests they drag the random visitor along for the ride. 50 | 51 | 8:00PM Startups return to space and continue working and discuss event. Or opt to grab drinks with the random visitor. 52 | 53 | ## Thursday 54 | 55 | 8:00AM Staff arrives. Startups start to roll in. 56 | 57 | 12:00PM Catered lunch in the workspace. 58 | 59 | 1:00PM Workshop based on common problem all startups are experiencing. Staff, mentors, and peer-to-peer engagement encouraged. 60 | 61 | 3:00PM Startups return to work. Small groups break off to work on issues that arose during the workshop. 62 | 63 | 7:00PM Staff departs. Space starts to clear out. 64 | 65 | ## Friday 66 | 67 | 8:00AM Staff arrives. Startups start to roll in. 68 | 69 | 10:00AM Staff learns that there is an investor in town to meet with a PIE alum. Staff invites the investor to run the gauntlet. Investor agrees. Startups are given 15 minutes each to meet with the investor. 70 | 71 | 12:00PM Staff talks with startups about what happened, what went well, what could be better. 72 | 73 | 4:00PM Happy Hour with PIE mentors, alums, and community members. 74 | 75 | 7:00PM Happy Hour winds down. Startups go back to work. 76 | 77 | 8:00PM Founders who clicked with the investor meet up to continue the conversation 78 | 79 | ## Saturday and Sunday 80 | 81 | Staff and startups in space sporadically. No scheduled events. 82 | 83 | 84 | 85 | -------------------------------------------------------------------------------- /notes/logistics/archive/onboarding-startups.md: -------------------------------------------------------------------------------- 1 | # Onboarding new startups 2 | 3 | It’s important to recognize that this is a large transition for your companies. Some might have even relocated completely to participate in your program. And if they haven’t, well, going from planning your own schedule and working out of a coffee shop, to a structured accelerator program is still a big transition. 4 | 5 | Do what you can to help mitigate an issues your teams might have as they join you. Some welcome wagon items may include 6 | - Housing suggestions or referrals 7 | - Maps of the city 8 | - Information on public transportation 9 | - Places to eat or grocery shop 10 | 11 | What would you want to know if you were moving to a new city or even a new office? Your teams will want to know that too. 12 | 13 | ## Take it slow 14 | 15 | We’ve found that too much scheduling the first few days can lead to a bumpy kickoff for companies starting the program. The first day of your program should be dedicated to introducing teams to one another, giving an office tour, letting people get settled and then finally, letting them get to work. 16 | 17 | We recommend providing documentation and creating some sort of reference for startups so they know what to expect as the program becomes more structured. It’ll also help them be clear on deadlines for deliverables and the expectations for them. 18 | 19 | Here’s how we’ve used: 20 | - [What you’re getting yourself in to](/notes/logistics/onboarding-what-youre-getting-in-to.md) 21 | - [Woohoo! Here’s what to expect on your first day](/notes/logistics/onboarding-what-to-expect.md). (Along with acceptance letter) 22 | 23 | Consider providing these docs along with a welcome basket of swag. Again, it’s about making folks feel welcome. The more comfortable your teams feel in the space the sooner they’ll be able to hit the ground running and work — and begin building up the trust that will enable them to succeed in this environment. -------------------------------------------------------------------------------- /notes/logistics/archive/onboarding.md: -------------------------------------------------------------------------------- 1 | 2 | # Onboarding 3 | 4 | One of the biggest mistakes most accelerators make — and we've made it a few times — is with onboarding. Or, to put it another way, assuming that participants realize what the accelerator is designed to do, what resources are available, and how to make best use of those resources. 5 | 6 | If you're building an early stage tech accelerator, you can sometimes skate by without doing a great deal of onboarding. And just get lucky. 7 | 8 | Why? Because most early stage tech companies are familiar with the concept of accelerators. They know what they are designed to do. And they understand, at a high level, what they're supposed to get out of the accelerator. 9 | 10 | Other industries? Not so much. The accelerator is not a common concept. So we've found that assuming folks will know how to engage is a huge mistake. You have to tell them. 11 | 12 | -------------------------------------------------------------------------------- /notes/logistics/letter-application-one-week.md: -------------------------------------------------------------------------------- 1 | Folks, 2 | 3 | We've officially hit the one week countdown. Stressful, but you're good to go though right? You just like to experience the rush of waiting until the last possible second to hit submit? 4 | 5 | I get it. Most big decisions for your company, and probably life in general, are best handled with a heavy dose of procrastination. 6 | 7 | So procrastinate away my friends! Just make sure you're fully prepared when you sit down to finish that application. Here is a little to-do list to make sure you live up to the ultimate last-minute submitter status title. 8 | 9 | 1. Read our FAQ blog post - everything you've wanted to ask about the program, but were waiting until the last minute: 10 | http://blog.piepdx.com/2014/04/22/youve-got-questions-weve-got-answers-some-faqs-about-pie/ 11 | 12 | 2. Review the application cheat sheet - don't worry, we can only see viewers as "Anonymous Frog" or Rick's personal favorite, "Anonymous Chupacabra" so your secret preparedness will in fact, be secret: 13 | https://docs.google.com/a/piepdx.com/document/d/1c3PeneF5lVc7yCFtIM8OIUyF3X3bJkq3i1wTMTH7wng/edit 14 | 15 | 3. Chat with a mentor - if you do item number two, you'll know that we love referrals from our mentors. Bonus, if the FAQ didn't answer all of your questions they could be a good resource. I like to call this a two birds, one stone, to-do task. For a list of mentors, check: 16 | http://blog.piepdx.com/portfolio/ and http://blog.piepdx.com/portfolio/ 17 | 18 | If you do those three things, you'll definitely be ready for the most important one. Ready for it? 19 | 20 | 4. Actually fill out the application and hit submit: 21 | https://piepdx.typeform.com/to/YGfzVn 22 | 23 | That's it. It's really just that simple. Four easy to-do items and you could be on your way to joining the 2014 class of PIE. 24 | 25 | So get on it. Because we're really looking forward to meeting you and your awesome team. 26 | 27 | Sincerely, 28 | -------------------------------------------------------------------------------- /notes/logistics/letter-applications-open.md: -------------------------------------------------------------------------------- 1 | Dear awesome entrepreneur or PIE-curious type who has signed up for our mailing list, 2 | 3 | Hope you're doing well. How is your startup? Oh. Really? That's awesome. This is fortuitous timing then... 4 | 5 | PIE (Portland Incubator Experiment) — a startup accelerator that gives you some cash, three months of intensive mentorship, and up to nine months of office space — has opened applications for our 2014 class. 6 | 7 | We'd love to have you apply to be part of it: 8 | http://piepdx.com 9 | 10 | What's PIE? It is a startup accelerator run in collaboration with Wieden+Kennedy, arguably one of the most creative communications companies in the world. We've been home to alums like Orchestrate, Urban Airship, Simple, Cloudability, Lytics, Switchboard, and more. 11 | 12 | And we're hoping to be the home for your startup. 13 | 14 | How do we make that happen? Well, you have to apply. The PIE application form features many of the standard incubator/accelerator questions. Be prepared to talk about the awesome product you're building, the dream team you've got behind it, and even why you think you'd be a good addition to the PIE portfolio. 15 | 16 | Please submit your application either via the PIE site (http://piepdx.com) or via AngelList (URL). 17 | 18 | Long story short, we'd love to help you succeed. So, if you're sitting there working on your dream, you owe it to yourself to throw your hat into the ring for the next class of PIE. It could be that push you need to make your startup fantasy into a reality. 19 | 20 | Deadline is [DATE]. (Class begins in [DATE].) So don't wait! 21 | 22 | We're looking forward to seeing your application. 23 | 24 | Hugs and kisses, 25 | -------------------------------------------------------------------------------- /notes/logistics/letter-applications-two-weeks.md: -------------------------------------------------------------------------------- 1 | Hi there friend, 2 | 3 | Can you believe there are 14 days left until PIE applications close? That is literally 336 hours you can use to write the Best. Application. Ever. 4 | 5 | (Please don't spend 336 hours filling out the application. It's not that long!) 6 | 7 | Oh, but you're having writers block? Not sure if PIE is right for you? Can't decide what to have for lunch today... that is always a tough one! Well fear not, we've got some light reading material over at the PIE blog that just might help you with your woes. 8 | 9 | Try this one for some advice on picking the best accelerator for you: 10 | http://blog.piepdx.com/2014/04/07/how-to-pick-the-best-accelerator-for-you/ 11 | 12 | Need to hear from an alum? Orchestrate's CEO, Tony Falco has got you covered: 13 | http://blog.piepdx.com/2014/04/10/life-after-pie-a-look-back-with-orchestrate/ 14 | 15 | Gathering your thoughts? Try out the application cheat sheet: 16 | https://piepdx.typeform.com/to/YGfzVn 17 | 18 | Still need help with lunch? Me too! Let me know what you decide on. 19 | 20 | Get going already. Apply today: 21 | https://piepdx.typeform.com/to/YGfzVn 22 | 23 | Thanks in advance, -------------------------------------------------------------------------------- /notes/logistics/letter-demo-day-follow-up.md: -------------------------------------------------------------------------------- 1 | Hi there, 2 | 3 | Still recovering from your sugar overdose this weekend? Us too. Between that and this rainy Portland weather, we've decided to declare today a PIE Demo Day nostalgia day. 4 | 5 | Care to join us? 6 | 7 | Great. Grab a mug of something warm and get ready to dive in. 8 | 9 | * See all of the pitches from the PIE 2014 startups: 10 | https://www.youtube.com/playlist?list=PLFDgm_9P62ut5sSOPTMMoiz8Xb2z-nJdz 11 | * Get more info on each company: 12 | http://docs.piepdx.com/ 13 | * Got a few favorites? Don't forget to support them on Product Hunt: 14 | http://www.producthunt.com/e/pie-demo-day-2014 15 | 16 | Spoiler alert: after watching these startups on stage at PIE Demo Day, you'll probably be motivated to up your game and get back to work. You have been warned. 17 | 18 | Hang in there, keep up the good work, and we'll talk to you soon. 19 | 20 | Take care, 21 | PIE Management 22 | 23 | -------------------------------------------------------------------------------- /notes/logistics/letter-demo-day-invite.md: -------------------------------------------------------------------------------- 1 | Reader! 2 | 3 | Is that you? It's been so long since we've last talked I barely recognized you. Looks like you had a great summer. Us? Well, thanks for asking. Our summer has been a busy one. But we're excited to share it with you. 4 | 5 | Have you been keeping up with our blog? The PIE team has been working on some interesting experiments this year — solo founders, teen entrepreneurs, and more. 6 | 7 | Solo founders: 8 | http://blog.piepdx.com/2014/08/05/announcing-pie-class-of-2014/ 9 | 10 | Teen founders: 11 | http://blog.piepdx.com/2014/08/20/introducing-pies-teen-founders/ 12 | 13 | Sound interesting? Want to know more? Well, you're in luck. You can hear about all of the experiments, projects, and awesome startups at our annual PIE Demo Day. 14 | 15 | https://piedemoday2014.eventbrite.com 16 | 17 | And it's not much longer now. In fact, we know that PIE Demo Day is in 23 days, 23 hours, 36 minutes or so and counting. Because to keep the pressure palpable, we've created a bot to constantly remind the teams just how much… err little time they've got left until they're on stage. 18 | 19 | I mean, just in case the looming countdown clock near the kitchen isn't motivation enough. 20 | 21 | But the pressure isn't just on them, dear email list subscriber. No, no. Now, it's your turn to race the clock, as well. Because these PIE Demo Day tickets? They aren't going to last forever. 22 | 23 | Please join us October 24th at 2pm at the Gerding Theatre in Portland, Oregon, when we'll debut the companies of our 2014 class. 24 | 25 | We'd love to have you there. RSVP today! 26 | https://piedemoday2014.eventbrite.com 27 | 28 | See you soon! 29 | Kirsten & the PIE team 30 | http://piepdx.com 31 | 32 | P.S. Did we mention that PIE is five years old? We'll have some interesting things happening at Demo Day to celebrate. *hint hint* 33 | 34 | -------------------------------------------------------------------------------- /notes/logistics/letter-demo-day-livestream-reminder.md: -------------------------------------------------------------------------------- 1 | Howdy, 2 | 3 | Hope you’re doing well. Us? Well, we're more than a little excited. 4 | 5 | It’s hard to believe, but the last three months has completely flown by. And now, it’s time for PIE Demo Day 2014. Even better news? You can join us. Right from the comfort of your laptop or mobile device. 6 | 7 | Join us today, October 24, 2014, at 2PM PT (9PM GMT): 8 | http://blog.piepdx.com/2014/10/24/pie-demo-day-2014-livestream/ 9 | 10 | And if you like what you see and want to tell others about it, feel free to share your thoughts using the hashtag #piedemo. 11 | 12 | We’re looking forward to seeing you. 13 | 14 | Thanks in advance, 15 | PIE Management 16 | 17 | -------------------------------------------------------------------------------- /notes/logistics/letter-demo-day-logistics.md: -------------------------------------------------------------------------------- 1 | Oh hey there, 2 | 3 | What are you doing on Friday? Just checking to see if you had any ideas. It's not a big deal or anything. It's just Friday. 4 | 5 | Wait... Oh gosh, Friday is PIE Demo Day 2014! How silly of us to forget. You're coming right? Oh good! We're so glad you got your ticket before they sold out. 6 | 7 | You did, right? 8 | 9 | It's going to be awesome. This year’s Demo Day will feature presentations from our portfolio companies and highlights from our latest experiments. We’ll also take a look back at five years of PIE and the amazing startups with whom we have had the pleasure to work. 10 | 11 | Having the event sell out so quickly made us both happy and sad. You see, we like to think of Demo Day as a community event. We want everyone to be there. But running out of room put a bit of a damper on that. 12 | 13 | But turn that frown upside down. We're happy to announce that our friends at eBay have been kind enough to host a PIE Demo Day simulcast. They have room for 100 folks to join them! So that even more of the community can enjoy PIE Demo Day in person. 14 | 15 | ## PIE Demo Day 2014 – Simulcast 16 | Friday, October 24 1:30–4pm 17 | eBay Community Lounge 18 | http://piedemoday2014simulcast.eventbrite.com 19 | 20 | Can't make it in person? Don't worry, we'll come to you! Just click on the link below to join the PIE Demo Day livestream and you can enjoy the event from the comfort of your own laptop or mobile device. Magical. 21 | 22 | ## PIE Demo Day (livestream) 23 | October 24, 2014 at 2PM Pacific (9PM GMT) 24 | http://new.livestream.com/accounts/10263183/events/3497048/ 25 | 26 | So whether you're with us at the theater, hanging out with our friends at eBay, or watching us on your favorite device at your favorite location, we look forward to sharing with you the awesomeness of the last five years of PIE. 27 | 28 | Best, 29 | PIE management 30 | 31 | ps: We're also celebrating our five year anniversary. We like bourbon, but, if you're traditional, you can get us some sort of wood carving. 32 | -------------------------------------------------------------------------------- /notes/logistics/letter-technical-issues.md: -------------------------------------------------------------------------------- 1 | # Should you have technical issues… 2 | 3 | You're running as fast as a startup. Sometimes, things can go wrong. It happens. And it's happened to PIE a lot. A lot. So we thought we would provide a sample "Oopie" letter for you to use. Because you're going to screw up. Get used to it. 4 | 5 | ## SUBJECT: We screwed up. Let's fix this. 6 | 7 | **************************************** 8 | NOTE: We're contacting you regarding applications for the PIE class of 2014, which closed April 30, 2014. If you did not apply for this class, please feel free to disregard this message. 9 | **************************************** 10 | 11 | Howdy, 12 | 13 | At PIE, we like startups. It's why we started this whole experiment in the first place. So, whenever we have the chance, we opt for using startup products as part of our process. Whether they are PIE companies or not. 14 | 15 | We just like supporting startups. 16 | 17 | Most of the time, taking these calculated risks is positive all around, for both PIE and the startup. But every once in a while we encounter some issues. Which brings us to today's email. 18 | 19 | Unfortunately, we are experiencing an issue on the application platform we tried out for this class. A handful of folks have reached out to us, seeking confirmation that their application went through, as they did not receive the confirmation email. When we went searching, those folks didn't turn up in the database. 20 | 21 | ### CURRENT SITUATION 22 | 23 | We're still working to diagnose the problem. And applications have officially closed. But given the issues, we are now put in the uncomfortable position of having to ask these already overtaxed entrepreneurs to resubmit their applications. 24 | 25 | Again, this has only been an issue for folks who 1) Submitted their application via the PIE site and 2) Did NOT receive an email confirmation. If you applied via AngelList, you're good to go. Additionally, if you applied via Google Docs, you are okay. 26 | 27 | The startup is working with us to figure out the problem, but there is no simple explanation or reason why. Long story short, we're embarrassed and sorry and still trying to figure out how to resolve the issue and retrieve the data. 28 | 29 | But at least they're getting some good bug reports, right? (That's what we call looking at the bright side.) 30 | 31 | ### NEXT STEPS 32 | 33 | For those of you who are affected by this issue, again we apologize. We've created a Google Form to apply to PIE as a backup. If you are among those folks affected and would like to resubmit that way, you may. We will keep that form live until May 6 so that you have some breathing room. 34 | https://docs.google.com/spreadsheet/viewform?formkey=dF90R1RzODQ1VHhNVzB1UnZzMTNxN1E6MA 35 | 36 | Alternately, if you completed the cheat sheet, we will happily take that in place of the formal application. As this is an issue on our side of things, no one will be penalized. Please try to get that to us as soon as you can. 37 | 38 | We know how stressful applying can be. We want you to know that we are doing everything in our power to find a solution, because we value the time and effort you spent working on them. 39 | 40 | Please feel free to reach out with any questions. Thank you for your patience and understanding while we sort this out. 41 | 42 | And again, our apologies. We're truly sorry to be in this situation with you. 43 | 44 | Sincerely, 45 | 46 | 47 | 48 | -------------------------------------------------------------------------------- /notes/logistics/onboarding-acceptance-letter.md: -------------------------------------------------------------------------------- 1 | # Acceptance letter 2 | 3 | Hello [NAME] 4 | 5 | We'd like to take a minute and thank you for your patience while we took the time to review the applicants with our mentors and program partners. Their insight was immensely valuable and we didn't want to miss out on the opportunity to engage them. 6 | 7 | At this point, we would like to extend an offer to the [YOUR COMPANY] team to join us for this next class of [PROGRAM NAME], starting [DATE], pending completion of due diligence. Attached you'll find an offer letter outlining our terms, along with due dates, as well as a standard background check form and a statement of capitalization document. The due dates are firm and meeting them allows you to get the most out of the program right out the gate. That said, we always enjoy playing favorites with teams who get their documentation submitted early. 8 | 9 | Let me know if you have any questions. 10 | 11 | Thanks 12 | 13 | -- 14 | [NAME] 15 | [TITLE / PROGRAM NAME] 16 | 17 | Attached: 18 | - [Offer letter](/source/documents/pie-offer-letter.doc) 19 | - [Statement of Capitalization](/source/documents/pie-statement-of-capitalization.doc) -------------------------------------------------------------------------------- /notes/logistics/onboarding-what-to-expect.md: -------------------------------------------------------------------------------- 1 | # Getting Started 2 | 3 | We’re excited to have you finally join us at [PROGRAM NAME] in a few weeks. Before you get here, you might find the following helpful. Have a read and feel free to reach out with any questions. 4 | 5 | First up, check to make sure you’ve had submitted all of these forms: 6 | 7 | - Offer letter + Contract 8 | - Background Check forms 9 | - General Info Form: Contact / T-shirt sizes / Food 10 | - Non-disclosure Agreement 11 | - Anything else? 12 | 13 | When you arrive on [START DATE], you’ll find a pod set up for your company. Feel free to make that pod yours—some people bring their monitors, photos, flowers, foot hammocks...whatever makes you comfortable. We’ll take you on a brief tour and give you info on facilities/timeline. 14 | 15 | [details on what to bring] 16 | 17 | [details on what’s provided] 18 | 19 | [what Friday would look like. Run of show.] 20 | 21 | It’s pretty free form. Your company is still your company, so plan on working away and keep building your product. Other items on the schedule our first week is here. 22 | 23 | - Family Dinner on [DATE AND TIME]. 24 | - Lunch and Learns at [DATE AND TIME] 25 | 26 | [Good to Know FAQS] 27 | 28 | [OFFICE RULES, GOOD TO KNOW INFO. WIFI NETWORKS AND PASSWORDS] -------------------------------------------------------------------------------- /notes/logistics/onboarding-what-youre-getting-in-to.md: -------------------------------------------------------------------------------- 1 | # What you’re getting yourself into. 2 | 3 | Now that we’ve sparked your interest, let’s get into some of the nitty gritty of what this whole [PROGRAM NAME] thing might look like. Here’s what to expect and what’s expected—perhaps it’s just what you’ll need to succeed. ;) 4 | 5 | ## What to expect from us? 6 | 7 | Startups are at various points in their growth when they arrive. Some need critical legal help, others HR, and some just need to slog away with developing their product. For that reason, you’ll find that 8 | 9 | [PROGRAM NAME] is a relatively hands off program. Yes, there are plenty of resources — mentors, [PARNTNERSHIP NAMES], [MANAGEMENT NAMES], your peers — who are waiting to help you, but generally, we’ll wait for you to ask before we get busy trying to connect you with resources you’ll need to be get through your unique crisis/cloud of questions. 10 | 11 | That said, we do get you into a groove leading up to demo day with a schedule of mentor talks / workshops for topics and areas we think everyone will benefit from. You can expect spontaneous events as opportunities or needs arise, but here’s a brief rundown of some of the regulars: 12 | 13 | ## Lunch and Learns (Tuesdays + Thursdays until demo day) 14 | 15 | Yes. LUNCH. We’ll provide lunch and we’ll also use the hour to listen to a speaker—their advice for habits worth stealing and mistakes to avoid, tips and tricks, or more focused topics. Sometimes, it’ll be structured like a workshop where we figure out pricing models, PR tactics, or dig into some investor insight. No matter what, it’ll be helpful. 16 | 17 | ## Family Dinner (Monday nights) 18 | 19 | Being a founder is tough. Shit happens, and with so many things going on, there’s bound to be a moment (or likely quite a few) where you’re stuck—you have a problem, need help, need a second opinion. 20 | 21 | Welcome to family dinner. You’re now in a room full of brilliant people facing similar problems — what’s said in the room stays in the room and there’s bound to be someone here who can give you a hand. 22 | 23 | ## Opportunities galore 24 | 25 | We’ll have spontaneous events and deliverables that’ll be off schedule. Mentors will visit and investors will drop in. You’ll be busy and it’ll prob get stressful at times, but you can expect us to count on you to make the most of these opportunities. I mean, that’s why you’re applying in first place, right? Because you’re hungry to grow, connect, and collaborate. 26 | 27 | ## What’s expected of you? 28 | 29 | There are hundreds that apply to be part of the program, and while we’d love to get involved with way more than just 6-10 startups, it’s impossible at this stage. So if you’re here, we hope it’s not just because you want some good food and free office space. We’re looking for startups that are eager to grow, willing to listen, and looking for ways to pull their peers up with them. 30 | 31 | To graduate you’ll need to have product in market by the end of the three months and being used by people beyond friends and family. To get on stage and tell your story at demo day, well, you’re going to need a story. And a good one. Don’t worry, we’ll help with that. Speaking of things you need to have done, here’s our timeline to make sure we all hit the target by demo day: 32 | 33 | ### Timeline: 34 | 35 | #### Month 1: Product 36 | 37 | Talk to potential customers. Figure out what the problem is you’re really trying to solve. Build, build, build. Experiment, fail, learn, repeat. Done is better than perfect cause you’re gonna need to move fast. Schedule time with mentors who can help you with UX or deeper issues that you’re facing. 38 | 39 | #### Month 2: Projections and Pricing 40 | 41 | There’s more to your company than just a product…. or at least there should be. How are your going to make money? What’re your plans for growth? Are you planning to hire? Forecasting will help keep you afloat and by the end of this phase we’re all going to want to hear your plan. 42 | 43 | #### Month 3: Pitch 44 | 45 | Everyday, you’re telling people about your product. Investors, customers, collaborators. You’ll be telling this story for the rest of your company’s life, so don’t you think it’s worth honing in on this story? We’ll spend many, many hours working with you to craft your story in a way that’s authentic, yet powerful. You’ll help your peers and they’ll help you—you’ll be proud of yourself and of them. 46 | 47 | Sound like a busy few months? Yep. Might even be safe to say that other things on your agenda will naturally take a back seat for the duration of the program. You’ll likely have earlier mornings and later nights, but the startup hustle will keep you going. It’ll be one heck of a ride, and we can’t wait to hopefully have you here with us. -------------------------------------------------------------------------------- /notes/mentors/00_README.md: -------------------------------------------------------------------------------- 1 | # README.md 2 | We'll use this section to capture notes as we're brainstorming about a certain topic — and potentially other spots throughout the development of the documentation. 3 | 4 | It's just one big parking lot. 5 | 6 | And since we're winding up with a lot of disparate notes as we build this out, we've decided to add [an index to help folks get through the content](index.md). We'll do our best to keep this document up-to-date as more notes are added. 7 | 8 | To prevent any confusion with versioning, any content from this section that has already moved downstream to the document, itself, will be captured in the /archive directory under each topic. 9 | 10 | NOTE: This may result in different iterations of the same concept appearing in multiple files over time. We will normalize this as the content moves downstream into the final documentation. 11 | -------------------------------------------------------------------------------- /notes/mentors/01_index.md: -------------------------------------------------------------------------------- 1 | # Index 2 | 3 | - [Notes on mentoring](archive/mentoring.md) 4 | - [Mentors vs Advisors](archive/mentors-vs-advisors.md) 5 | - [Mentoring the mentors](archive/mentoring-mentors.md) 6 | - [Common sense is not common](archive/common-sense.md) 7 | - [Bad actors](archive/mentors-bad-actors.md) 8 | 9 | ## Mistakes 10 | - [Homogenous mentors](../misc/mistakes/mentors-homogenous.md) 11 | - [Corporate mentors](../misc/mistakes/mentors-corporate.md) 12 | 13 | ## Logistics 14 | 15 | - [Time commitment](archive/mentors-time-commitment.md) 16 | - [How to activate mentors](archive/mentors-activating.md) 17 | - [Preparing mentors to speak to startups](archive/mentors-coaching-on-speaking.md) 18 | - [Speed dating vs Matchmaking](archive/mentors-matchmaking-vs-speed-dating.md) 19 | 20 | ## Snippet 21 | 22 | - [Mentor integrity](archive/mentor-integrity.md) -------------------------------------------------------------------------------- /notes/mentors/archive/common-sense.md: -------------------------------------------------------------------------------- 1 | # “Common sense” is not common 2 | 3 | As I was working on my “Mentoring the Mentors” post for PIE, I recalled an older piece of mine where I dug into the whole “common sense” fallacy. It seemed timely and, potentially, helpful. So, I’m sharing some of those thoughts, after a little bit of refreshing the content. 4 | 5 | > Common sense. It seems so, well, common.But fact of the matter is that it’s not. 6 | 7 | I mean, common common sense is prevalent. I’ll give you that. Those widely held understandings. And things that most people seem to know. Sense that is common across a community or population. Yes, that exists. Common common sense is common. 8 | 9 | But your common sense? Nope. Not common, at all. 10 | 11 | You see, your common sense is different than everyone else’s common sense. And that’s because your common sense is based on the experience and insights that you have derived from doing the same thing, day in and day out. Or by being part of something for a period of time. Or from repeatedly trying, failing, and iterating. 12 | 13 | > Your common sense is a byproduct of your focus, your vantage, and your experience. 14 | 15 | And because of that, it is completely subjective. In fact, even if I were doing exactly the same thing you’re doing, day in and day out, the same things that are obvious to you wouldn’t necessarily be obvious to me. Even worse, I might have my own cadre of common sense that I thought you should already know. 16 | Common sense is, counterintuitively, uncommon. 17 | 18 | So that stuff that seems so obvious? It’s not. And that forehead-slapping “What is that person thinking? Isn’t it obvious that you do [or don’t do] that?” response you have on a regular basis? Whatever it is that is so painfully obvious to you may not even register for the person you’re observing. 19 | 20 | Like it or not, we are all victims of the “curse of knowledge.” And that’s really difficult to shake. And it’s nearly impossible to unthink or unknow. 21 | 22 | And that’s why, be it for business or mentoring or whatever, I am constantly challenged — and fail regularly — to do two things: 23 | 24 | ### 1) Stop assuming intuitive leaps have been made. 25 | 26 | I have a really bad tendency to assume that everyone has already thought about what I’m thinking about. As such, I assume that they’re making the same intuitive leaps I am. So I don’t say anything. Or share thoughts. 27 | 28 | The problem with this is that — more often than not — they aren’t making those leaps. It’s not because I’m smarter. (That, I can guarantee.) It’s just because I’m working with my set of common sense. So, even if it feels like I’m backtracking, I’m working to start with the reasoning behind my thinking. To ensure that everyone is on the same page. 29 | 30 | What’s more, I’m really trying to focus on beginning at the introductory level — the 101 — and go from there. Without being pedantic or dismissive. Because you can’t just jump into the deep end of the pool and assume that everyone knows how to swim. 31 | 32 | ### 2) Over-communicating what I think I know. 33 | 34 | If I’m not sure where my peers stand, then the onus is on me to be more effective at communicating. And I need to be more conscious and deliberate about sharing my opinions. No matter how small our company or our organization, we should be over-communicating when telling one another what is important, how we think things should be done, and how we have learned to get there. 35 | 36 | Even better? We should be documenting what we know to provide a common lexicon for those discussions and a foundation for new folks entering the fray. 37 | The value of our common sense lies in the very fact that we have produced it from our unique vantage. And because of that we need to, first, understand that it has very real and intrinsic value, even if we don’t perceive that it does. And second, we need to do a better job of sharing it and not assume that it’s common. 38 | 39 | > We need to get away from assuming that “Everyone else knows this stuff. I’m nothing special.” 40 | 41 | You know more about what you do than I do, or he does, or she does, or they do. In fact, we’re all incredibly ignorant of your unique flavor of common sense. And we would all be better off with you sharing those insights which you incorrectly assume we have already had. 42 | 43 | > That thing that seems so completely obvious to you? It isn’t to the rest of us. Your common sense isn’t common. -------------------------------------------------------------------------------- /notes/mentors/archive/mentor-integrity.md: -------------------------------------------------------------------------------- 1 | # Mentor Integrity 2 | 3 | Via @bwenamai: 4 | 5 | Under Mentors.... discussion about mentors with their hands out, how to deal with mentors asking for fees, mentor integrity, that being a mentor is not necessarily an endorsement of character by the accelerator 6 | 7 | https://github.com/piepdx/pie-cookbook/issues/2 -------------------------------------------------------------------------------- /notes/mentors/archive/mentoring.md: -------------------------------------------------------------------------------- 1 | # Notes on mentoring 2 | 3 | "Accelerator" can be a misnomer, in some cases. Accelerators are actually about slowing down, making connections, and contributing to community. They're about making busy people focus. About creating lines where there are only dots. 4 | 5 | If they accelerate anything, they accelerate connection. For both those mentors who choose to participate. As well as for the founders who are selected. 6 | 7 | We need to stop focusing on accelerating business and spend far more time and energy accelerating connections and value. For founders. And for our community. 8 | 9 | Mentorship is messy. And honest. And weird. Because it is human. 10 | 11 | It does not scale. It cannot be automated. And yet, if left to its own devices, it won't happen. Mentorship rarely happens organically. 12 | 13 | It doesn't have metrics. Or milestones. Or process. 14 | 15 | But it does have technique. It does have examples. And guidelines. And guardrails. For both the mentors and those being mentored. And for peers. 16 | 17 | ## In Practice (via @eighteyes) 18 | Mentoring is an alignment of perspective. Here, you have to take the life experiences of another person, and have them understand your perspective. As a mentor, you must take the time to know a person, how a person thinks, what their experience is. A handy way to approach this is to speak about complicated material in the form of metaphors. 19 | 20 | ### Metaphors are powerful teaching tools (via @eighteyes) 21 | Think about when you have learned a difficult subject. When it started, you had a slight familiarity with the subject, say 20% of the related material was understood. Here you stumbled around in the dark, with prior knowledge and experience as a candle lighting the way. Then you find it, that one critical insight your mind needed to begin to understand the other 80%. 22 | 23 | Metaphors can help to provide that critical insight by bridging the experience gap using imagination. 24 | 25 | > Example: 'Marketing is like a river. It is comprised of millions of little efforts, or drops, which gather in different channels, or tributaries, to bring customers to your business, like cargo to port' 26 | 27 | From here, you have a framework to begin to explain the practices of Marketing to someone with no experience. This is done by translating the language of a particular industry into a reference they are familiar with so you can begin to have a conversation about more abstract topics. 28 | 29 | ### Industry Language (via @eighteyes) 30 | As professionals, we depend on language to determine the expertise of others and evaluate our own progress. If a designer is talking about figure-ground relationships, while a data scientist is talking about k-clustering, they each may have a passing familiarity with the expertise of the other, but not the deep experience necessary to truly understand what it means to work with these ideas. 31 | 32 | As a mentor, is important to have a deep understanding of one or several subject matters, and a conversational familiarity with others. These are all touchpoints where you can convey your experience to someone else, using terms and ideas they already understand. 33 | 34 | ### Share freely (via @eighteyes) 35 | Entrepreneurship often involves the challenge of connecting discrete ideas, so during a mentorship it is extremely important to share whatever information seems relevant, even if it is not topical to the established mentoring relationship. Knowledge does not fit neatly into boxes, it broadly crosses many connections. You never know what may `click` for someone else, it is best to flow with the conversation instead of following a script. 36 | 37 | ### Learn Openly (via @eighteyes) 38 | One of the amazing things about people is that everyone sees their own connections and brings their own experiences. Young people especially, are more fluid in their thoughts, and have more free time to deeply pursue interests. Make time to listen, when you're scheduling time to talk. 39 | -------------------------------------------------------------------------------- /notes/mentors/archive/mentors-activating.md: -------------------------------------------------------------------------------- 1 | # How to activate mentors 2 | 3 | At PIE, we used four different means of activating mentors by getting them engaged with startups. How we worked with the mentors depended on both the mentor preference as well as the startup's or founder's immediate needs. 4 | 5 | We’ll take you through each of these elements from least amount of engagement to most engagement between founder and mentor. 6 | 7 | ## Presentation with Q&A 8 | 9 | ### For the mentor 10 | ### For the founders 11 | 12 | ## Workshops 13 | 14 | ### For the mentor 15 | ### For the founders 16 | 17 | ## Speed dating or running the gauntlet 18 | 19 | ### For the mentor 20 | ### For the founders 21 | 22 | ## Hands on 23 | 24 | ### 1:1 25 | 26 | #### For the mentor 27 | #### For the founders 28 | 29 | ### 1:Company 30 | 31 | #### For the mentor 32 | #### For the founders 33 | 34 | ### Many:Company 35 | 36 | #### For the mentor 37 | #### For the founders 38 | 39 | 40 | 41 | 42 | -------------------------------------------------------------------------------- /notes/mentors/archive/mentors-bad-actors.md: -------------------------------------------------------------------------------- 1 | 2 | # Bad actors 3 | 4 | One of the most challenging things about attempting to manage community — and then activating that community in the form of an accelerator — is the presence of bad actors. 5 | 6 | When we say "bad actors," we mean individuals who are more interested in personal gain than the gain of the community or the founders in your program. It happens. Sometimes it's intentional. Often it's not. 7 | 8 | So how do you deal with it? 9 | 10 | Well, we recommend follow Brad's advice in Startup Communities. The community has to be open to everyone. You have to welcome everyone. And you have to build the type of community that rewards good behavior. And discourages bad behavior. 11 | 12 | But even with all of that working, bad actors still enter the fray. So what to do? 13 | 14 | Honestly, from an accelerator standpoint, sometimes bad actors are more beneficial than one would think. 15 | 16 | Let's provide an example. 17 | 18 | One class of PIE, we had arranged to have a serial founder come into to present to the class. The founder was currently employed by another company and, as such, took our invitation to mean we were interested in hearing about that company. And not the founder's journey with previous companies. 19 | 20 | Shame on us for not setting the context correctly. Lesson learned. 21 | 22 | With that misunderstanding as the impetus, things went from bad to worse. With and swirling schedule and multiple overlapping commitments, the founder canceled at the last minute. But rather than leaving us hanging, the founder decided to send an alternate speaker. The person the founder sent was a salesperson for the company. 23 | 24 | So through no fault of the founder and no fault of the salesperson, we wound up in a bad actor situation. 25 | 26 | Our founders showed up dutifully to hear a founder talk about their experiences, challenges, and failures. But what they got, instead, found was a sales pitch for a product they neither wanted nor, honestly, needed. 27 | 28 | And no matter how much staff would try to redirect the speaker — "Hey that's great. Maybe you can talk a little bit about what it's like to be in a sales role for this kind of company…?" — the sales pitch continued. "What do you do when an audience isn't receptive to your sales pitch?" Still continuing. "When do you walk away from a pitch?" And on and on. 29 | 30 | There was no derailing it. 31 | 32 | So when it was over, the staff scurried to tie it off and hustle the speaker out the door. 33 | 34 | The PIE founders were, understandably, miffed. And any number of conversations were sparked by that experience. Some critical of the program for allowing it to happen. Some critical of the company and the former founder for sending that presenter. Some for the presenter not cluing into the environment. 35 | 36 | It became a running gag for the remainder of the class. 37 | 38 | But you know what? It resulted in a lot of good conversations. A lot. Like an irritant creating a pearl, the poorly placed and unintentional bad actor had not only created a context for interesting discussion, the salesperson had unintentionally become a common enemy against which every one of the founders in that class could rail. 39 | 40 | It went from a negative to a teaching moment. 41 | 42 | Best of all, it occurred in a safe environment. Somewhere that the founders could discuss what happened. Why it happened. And why it was bad. And that made it incredibly valuable on any number of fronts. 43 | 44 | And with this happy accident it dawned on us that these founders were going to encounter these situations out in the wild. And now they would be better equipped to handle them when they occurred. 45 | 46 | And so we started introducing bad actors intentionally. To recreate those interesting moments of conversation and learning. 47 | 48 | -------------------------------------------------------------------------------- /notes/mentors/archive/mentors-matchmaking-vs-speed-dating.md: -------------------------------------------------------------------------------- 1 | 2 | # Speed dating vs Matchmaking 3 | 4 | When it comes to mentor engagement, no topic is more ripe for discussion — and more likely to rile opinions — than the pros and cons of speed dating and matchmaking. But before we get into that, let's explain what we mean by the terms. 5 | 6 | ## Speed dating 7 | 8 | With this format, either startup or mentor is assigned a location, usually a conference room or section of a larger worker area. The other party is then assigned the task of moving from station to station to meet with one another. This usually occurs on a very short timeframe, most commonly between 15 and 30 minutes. 9 | 10 | There is usually a smattering of mentor types, expertise, and skills in these situations, given people's busy schedules. It's often a "we'll take who we can get" approach. 11 | 12 | The process is designed to make efficient use of time for both mentors and startups, giving each party the chance to briefly meet the other. And to give mentors a general lay of the land for the cohort as a whole. It also avails the opportunity for each party to identify folks with whom they would like to be working. 13 | 14 | ## Matchmaking 15 | 16 | With matchmaking, introductions between startup and mentor are intentional, based on a series of factors, such as: 17 | - Current problems plaguing the founders 18 | - Stage of the product or company 19 | - Skill set and expertise of the mentor 20 | - Personality of the founders 21 | - Personality of mentor 22 | - Likelihood of availability 23 | 24 | There is no set day or timeframe. Staff introduces the startup and mentor and leaves it the startup to schedule the meeting. Staff then follows up with both mentor and startup to understand the outcomes of the meeting and to help decide next steps. 25 | 26 | ## So which is it? Both. 27 | 28 | At PIE, we believe that each model has its pros and cons, which is why we have always opted to run a hybrid model. Most accelerators try to do the same. In my mentoring experience, however, more programs seem to lean more heavily on speed dating than matchmaking. -------------------------------------------------------------------------------- /notes/mentors/archive/mentors-time-commitment.md: -------------------------------------------------------------------------------- 1 | # Time commitment 2 | 3 | Once you’ve chosen to work with a mentor, your most important job is to understand that mentor’s level of time commitment. Some mentors will want to help but have absolutely no time. Other mentors will be willing to show up for office hours several times a week. It runs the gamut. Your challenge is making the best use of the time they are willing to commit so that they are deriving value from their participation. 4 | 5 | ## Sliding scale 6 | 7 | At PIE, we found the best way to help assess a mentor's availability was to present a sliding scale. Where the minimal level of commitment was fairly low and the maximum level of commitment was decided by the mentor. Just as importantly, we used other mentors as examples — which provided even more context for their potential engagement. 8 | 9 | Our lowest time commitment was "Be willing to grab coffee with one of our startups. Roughly 30 minutes. One time." That was it. 10 | 11 | At the upper end of the scale was "Hold office hours at PIE on a regular basis. Or just work out of the space regularly and be open to interruption. [Mentor name] at [Startup] has done this to great effect and is consistently one of our most popular mentors." 12 | 13 | ## Mutual respect 14 | 15 | And if you do it right? You’ll find they’ll be a lot more willing to commit more time to the program in future class. Culture of trust and all that. 16 | 17 | Respect mentors’ time and they will repay that respect with more time. 18 | -------------------------------------------------------------------------------- /notes/mentors/archive/mentors-vs-advisors.md: -------------------------------------------------------------------------------- 1 | # Do you need a Mentor or do you need an Advisor? 2 | 3 | Like many industries, the startup world is rife with terminology that holds special meaning to individuals who are well versed in its own cryptic lexicon. For that reason, we often fall into situations where we assume we’re on the same page as one of our similarly immersed counterparts. And — like most assumptions — that can cause problems. We believe that communication and clarity are vital, so we’re always looking for ways to get everyone speaking the same language. 4 | 5 | One area of muddy definitions and confusion that we encounter time and time again is with “Mentors” and “Advisors.” In the vein of clarification, we thought we would take a few minutes to split hairs and explain the difference between these two roles, from a PIE perspective. 6 | 7 | > The primary difference between a mentor and an advisor is that the former is chiefly tasked with providing opinions on problems and the latter is tasked with resolving those issues. 8 | 9 | ## Mentors 10 | 11 | Obviously, as an early stage startup accelerator, we spend far more time with mentors than advisors. In our world, we define a Mentor as an individual who volunteers his or her time to provide a startup with opinions, criticism, and feedback on problems, opportunities, or quandaries. 12 | 13 | Mentors tend to provide feedback in the form of “If I were in your shoes…”, “Here’s what I’d suggest…”, or “I remember being in a similar situation. Here’s how we handled it….” 14 | 15 | Therefore, mentors should… 16 | 17 | - Give first 18 | - Volunteer their feedback free of charge 19 | - Provide feedback on a wide range of issues and opportunities with the startup 20 | - Speak from previous experience tempered with a knowledge of current market conditions 21 | - Openly share mistakes and missteps from their past experience 22 | - Remove their “brand hat” or “title” as needed, i.e., sometimes a mentor is “a CEO” and sometimes that same mentor is simply a “user,” “successful business person,” or “someone who has seen a lot.” 23 | - Float in and out of a startup’s purview, enabling the mentor to provide fresh perspectives on problems as they change 24 | - Be used en masse to simultaneously provide a variety of viewpoints on specific problems or opportunities — the more opinions, the better— even if it winds up causing the classic “[mentor whiplash](http://avc.com/2013/07/mentorinvestor-whiplash/)” 25 | 26 | ## Advisors 27 | 28 | Conversely, we define an Advisor as an individual who is compensated —either in the form of equity or cash — by a startup in exchange for effort on solving a specific issue with the company or who is charged with assisting the founding team with a variety of issues. 29 | 30 | Therefore, advisors should… 31 | 32 | - Always be compensated for their efforts 33 | - Work to earn that compensation 34 | - Focus on specific areas that are in the advisor’s wheelhouse 35 | - Provide strategic value to the startup that is recognizable to potential investors or other advisors 36 | - Be expected to contribute effort to solving problems 37 | - Be held accountable for contributing time to the helping a startup make progress or resolve issues 38 | - Be used by the startup in a fashion that is equitable to the amount of compensation 39 | - Provide more than advice or guidance 40 | - Continue to provide value to the startup throughout their tenure 41 | 42 | ## Pick the right person for the job 43 | 44 | To recap, if you’re working with a **mentor**, ask them for advice, not effort. They’re volunteers. They’re not being paid to help you. They’re providing their insights with the hopes that others will not have to suffer the same pains the mentor has. 45 | 46 | If you’re working with an **advisor**, it’s fine to ask for advice, but you should also expect them to do work — and hold them accountable to that expectation. And you should recognize that they are a direct reflection on you and your company. Don’t take on advisors on a whim. Anymore so than you would take on a cofounder lightly. 47 | 48 | Mentors volunteer; advisors are paid. Mentors advise; advisors work. -------------------------------------------------------------------------------- /notes/misc/README.md: -------------------------------------------------------------------------------- 1 | # README.md 2 | We'll use this section to capture notes as we're brainstorming about a certain topic — and potentially other spots throughout the development of the documentation. 3 | 4 | It's just one big parking lot. 5 | 6 | To prevent any confusion with versioning, any content from this section that has already moved downstream to the document, itself, will be captured in the /archive directory under each topic. 7 | 8 | NOTE: This may result in different iterations of the same concept appearing in multiple files over time. We will normalize this as the content moves downstream into the final documentation. 9 | -------------------------------------------------------------------------------- /notes/misc/accidents/contest-404.md: -------------------------------------------------------------------------------- 1 | # 404: Origins 2 | 3 | Despite each company's accelerator experience being its own special 'world of hurt', we've learned over the years that the collective morale of the class has its own fairly predictable peaks and troughs. We didn't realize that in our first year, but there it was - two-thirds of the way through the program the punch list of fixes and to-do's seemed to be getting longer (and redder) and the high of collective world-beating ("yay! we're in! there's a coffee machine!") had faded to a semi-sullen slog. Stuff was getting done, but the joy was out of it. And this was one month before demo day, when the companies needed to be nailing there products, propositions and pitches. 4 | 5 | Rick and I were walking the floor, checking in on the companies, and found that one of the engineers in AthletePath, a startup focused on community and services for cyclists, runners and crazy triatheletes, had found a 'so-bad-its-awesome' video of a [cyclocross athlete eating it](https://www.youtube.com/watch?v=bEGAIYKTZ9w) during a competition and embedded it in Athletepath's 404 page. 6 | 7 | With that simple ship, we realized that he'd not just found a video that was true and authentic to what they were all about as a company - he'd stumbled onto the perfect way to precisely and emotionally represent the feeling of a surprise bad experience with a service you loved. No-one else in the program had tackled the 404 page in quite the same way - or given it much thought. Most had default pages - those 404 pages that blame the victim ("you've arrived on this page in error") rather than take responsibility ("whoops - we let you down"). When you spend all your time thinking about what your service is, you can forget to think about what it isn't - and that was when the idea came to us. 8 | 9 | On the spot, we announced the 404 contest - a 24 hour competition for the best 404 page, as decided by a vote of the participating startups and mentors. 10 | 11 | I described it as a chance to make real the 'hole in your heart' that would be left when that thing you love was taken away. A chance to use a little detail to reinforce their vision - and to reassure their customers that the people behind the thing they loved really cared about them and their experience. Our startups had spent two months laser-focused on what they were - for twenty-four hours, we asked them to focus on what they WEREN'T. 12 | 13 | The energy in the place went from zero to ridiculous. I remember the buzz of conversation, the whir of rolling chairs and tabletops being cleared. Everyone was super crisp, excited, and engaged. We heard laughter again - nervous quiet then genuine and loud. Good constructive arguing. And surprise - "taking people's eyes off the ball" by thinking about what they were NOT forced important clarifying conversations for founder teams around issues they'd been consciously and unconsciously struggling with for weeks. 14 | 15 | It's fair to say that that contest spurred more forward progress in twenty-four hours than we'd seen in the two previous weeks. 16 | 17 | The results ranged from inspiring and heartfelt to funny to genuinely useful. When the vote was taken - loudly, good naturedly and with surprising conviction - the "why" something won became as important as what had one, as we talked about mission, vision and expression. The 404 contest was a communal bonding event worth every penny of the $404 dollar prize we awarded to the winners - who promptly used their winnings to buy everyone drinks. 18 | 19 | Best of all, the playful intensity cleared all the bullshit out of the room. People were exhausted, but they were in this together now, in a way they hadn't been before, and the energy level kicked up just in time for the final month of the program. 20 | 21 | The 404 contest transformed PIE from a zero-sum game of who was going to "win" the program to a community rooting for each other to kick ass. And along the way became a PIE tradition. -------------------------------------------------------------------------------- /notes/misc/accidents/happy-accidents-food.md: -------------------------------------------------------------------------------- 1 | # Food 2 | We learned to use food as a tool in our program because breaking bread with one another fosters a sense of community. 3 | 4 | When you feel engaged with your community, you are more likely to lean on them for support. It is our job as management to provide support for your companies, and support goes beyond the scope of business. 5 | 6 | It's important for management to take the metaphorical temperature of the program class from time to time and see if there is a need to provide stress relief. 7 | 8 | - Did folks have a slammed week of meetings? 9 | - So much pitch practice they want to walk away from it all? 10 | - Tension between founders? 11 | 12 | The answer to all of these problems is food, at least on some level. You’ll get more out of folks if you are able to empathize with them and take a breather every now and again. But we don’t just eat food, we make food together. We find time in the program to take a group cooking class, on one of the regularly scheduled family dinner nights, and we work together to create that night's meal. 13 | 14 | It's a real bonding experience and gives us an opportunity to connect on another level - a human level. 15 | -------------------------------------------------------------------------------- /notes/misc/archive/be-intentional.md: -------------------------------------------------------------------------------- 1 | # Be intentional 2 | 3 | So much of what occurs in an accelerator environment appears to happen organically and dynamically. But appearances, as they say, can be deceiving. And can belie all of the prior effort that has been invested prior to the accelerator environment. 4 | 5 | To be successful, you must be intentional. And work with the intent of making stuff happen. Not just letting stuff happen. -------------------------------------------------------------------------------- /notes/misc/archive/drawing-inspiration.md: -------------------------------------------------------------------------------- 1 | # Drawing inspiration from other chefs 2 | 3 | There are a benefits to starting something after people have already tested the waters. You’re getting the chance to take advantage of learnings from predecessors to inform the organization you’re trying to build. 4 | 5 | We tried to do the same thing. But when we started thinking about PIE as an accelerator, we weren’t quite as lucky. Much like when we started the coworking space, there were few models from which to select—and none of them had proven whether the model would actually pencil out. (Many of them still haven’t.) 6 | 7 | So we just had to take our best guess from the available options. But unlike you with hundreds of successful accelerator programs from which to choose, we had, well, two. Those two models were still in their early existence but they made the most sense to us. And seemed most in line with what we were trying to accomplish. So we took a risk. And tried to glean as much as we could from what they were doing and apply those concepts to our program. 8 | 9 | Now the names of our inspirational chefs — our Julia Child and James Beard as it were — aren’t going to be surprising to you, in this day and age. The two programs we chose to serve as role models were — now obvious thanks to their continued success — Y Combinator and TechStars. 10 | 11 | Things weren’t as obvious back then as they are today. There was little indication at that time that these two entities would become the juggernauts of startup acceleration that they are today. 12 | 13 | We just got lucky. 14 | 15 | Note: This is a recurring theme. 16 | 17 | Looking back, we also made a decidedly important decision by accident. 18 | 19 | You see, we knew we couldn’t recreate the perceived effectiveness of either of those programs, wholesale. Because we didn’t have all of the necessary ingredients at our disposal. Nor were we in a region that would provide all of those elements. 20 | 21 | So rather than selecting one program after which to pattern ourselves in a cookie-cutter fashion we chose to instead dissect each program and take only the elements which we felt best resonated with our audience—and that we had a chance of effectively emulating. 22 | 23 | That is, it did us no good to strive to set up the program up as the onramp to the Silicon Valley elite and a bevy of investors—because we didn’t have the access that would have enabled this. Instead, we took only the parts of each program we had the ingredients to effectively recreate. 24 | 25 | Kind of like borrowing a cup of sugar from your neighbor. -------------------------------------------------------------------------------- /notes/misc/archive/how-to-use-this-cookbook.md: -------------------------------------------------------------------------------- 1 | 2 | # How to use this cookbook 3 | 4 | Like many cookbooks, there’s no one way to use this book. But we have designed it with two particular use cases in mind: 5 | 6 | 1. If you are intrigued by the idea of starting an accelerator but have absolutely no idea where to start—or, worse yet, are paralyzed by a fear of failure that’s preventing you from taking the leap—this book will guide you step-by-step through the iterations that PIE followed, highlighting mistakes we made along the way and culminating with the process we use to run our accelerator today. 7 | 2. If you have already started an accelerator but are feeling like you could be doing better, this book will allow you to jump to sections that apply to specific areas of your program that you’re looking to improve. 8 | 9 | Like any cookbook, this book provides the recipes that worked for PIE. They may or may not work for your organization. And your special adaptations are what make the recipe work for you. 10 | 11 | With that in mind, it is our intention to: 12 | 13 | - Arm you with enough knowledge to be dangerous. And to break things. 14 | - Give you enough insight into our process for you to internalize it, change it, and create your own way of doing things. 15 | - Encourage you to communicate back to us what worked and what didn’t. So that we can create a more compelling cookbook for everyone that is just as crazy as we are. 16 | -------------------------------------------------------------------------------- /notes/misc/mistakes/mentors-corporate.md: -------------------------------------------------------------------------------- 1 | # Corporate mentors 2 | 3 | Spending time mentoring was neither in their job description nor a KPI for their group. If you even know what a KPI is, then you know what we’re talking about. 4 | 5 | Lesson learned: You can build a $1 million company faster than you can schedule a meeting with corporate contacts—even if they’re really solid contacts. 6 | -------------------------------------------------------------------------------- /notes/misc/mistakes/mentors-homogenous.md: -------------------------------------------------------------------------------- 1 | # Homogenous mentors 2 | 3 | When we started, we assumed that the best mentors for tech startup founders would be tech startup founders and only tech startup founders. This was flawed. 4 | 5 | What we discovered was that a more diverse mentor community was needed. Successes, failure, founders, users, and more were needed. And that provided us with a far more beneficial mentor group than if they had all been expert. 6 | 7 | But the experts were pretty awesome too. -------------------------------------------------------------------------------- /notes/misc/mistakes/mistakes-were-made-hubris.md: -------------------------------------------------------------------------------- 1 | # Hubris 2 | 3 | As the PIE accelerator garnered more recognition and our reputation grew, we fell into a very smug trap. 4 | 5 | With hundreds of applications flooding in the door from “every continent except Antarctica” and PIE landing in “Top Startup Accelerator” rankings around the Web, we lost sight of one of our key goals: to make it easier to build a startup in Portland. 6 | 7 | Or maybe we failed to put the words in the right order: to make it easier for Portland startups to build. 8 | 9 | Extending our recruiting worldwide in an effort to garner an ever higher number of applications did nothing to change the dynamic of the program. And while it may have helped the perception that Portland was becoming a viable town for startups, it did little to impact the reality of building a business here. 10 | 11 | What’s more, the numbers never really played out. 12 | 13 | Year after year, despite the amount of outreach and promotions, we always got around 400 applications for the PIE class. 14 | 15 | Now, one can argue that—in a world where a new accelerator launched every single day—static application numbers could be perceived as an upward trend. However, we can easily argue right back that for every accelerator started that day, 100 startups were started. 16 | 17 | Of those 400 applications, on average, 60% of them came from outside of Portland. Every year. No matter what we did. 18 | 19 | By the time we made it through the selection process and made offers to companies, the number of founders who had come from outside of Portland—we often encountered cases where one founder lived in Portland and other founders chose to relocate—that 25% of PIE founders, class by class, came from outside the region. 20 | 21 | And when class was over? The overwhelming majority of startups that relocated to Portland to participate in PIE relocated right back home when they were done. 22 | 23 | Long story short, this worldwide focus was not providing any tangible impact on the Portland startup scene. Nor was it making it easier for Portland startups. 24 | 25 | That hubris knocked us off track. And honestly, it took the concept of this book to get us back on track. 26 | 27 | **Lesson learned: Don’t lose sight of your original goal.** -------------------------------------------------------------------------------- /notes/misc/mistakes/mistakes-were-made-ignoring-our-thesis.md: -------------------------------------------------------------------------------- 1 | # Ignoring our thesis 2 | 3 | It didn’t take long for us to discover that PIE was actually very good at one type of technology startup: 4 | 5 | > Business-to-Business platforms and enabling technology. 6 | 7 | We had the mentors to support it. We had the alums to help with the peer mentoring and connections. And we had a patron who was expert at succeeding as a behind-the-scenes partner for any number of brands. 8 | 9 | In the world of venture capital and early stage startups, discovering a theme like this and defining it as a touchpoint for both how and with whom you do business is called a "thesis." And those investors who create and stick to a compelling thesis retain focus, thematically complementary companies in their portfolio, and a lens through which they assess every opportunity. 10 | 11 | It's just good business. Do what you know. Stick to what you know. Everyone wins. 12 | 13 | But despite our best efforts, we never did a good job of sticking to that thesis. We even got to the point of telling startups "We're not good at this. So please don't apply." But it didn't help. In fact, sometimes, that only made it worse. 14 | 15 | And so we continually fell into the trap of going off-thesis. Granted, we hedged with “well this is an experiment” and “the market is constantly evolving.” 16 | 17 | We were an accelerator that was good with business-to-business. It was exceedingly obvious. And yet what did we do with every single class? 18 | 19 | That’s right. We took on consumer facing technology as each class. Consistently. 20 | 21 | Was this good for them? Potentially. Was it good for us? Only in continuing to prove that we couldn't move the needle in that industry as much as we had hoped. 22 | 23 | Stick to your thesis. You'll be better for it. More importantly, so will you startups. 24 | 25 | -------------------------------------------------------------------------------- /notes/partnerships/README.md: -------------------------------------------------------------------------------- 1 | # README.md 2 | We'll use this section to capture notes as we're brainstorming about a certain topic — and potentially other spots throughout the development of the documentation. 3 | 4 | It's just one big parking lot. 5 | 6 | To prevent any confusion with versioning, any content from this section that has already moved downstream to the document, itself, will be captured in the /archive directory under each topic. 7 | 8 | NOTE: This may result in different iterations of the same concept appearing in multiple files over time. We will normalize this as the content moves downstream into the final documentation. 9 | -------------------------------------------------------------------------------- /notes/pie/README.md: -------------------------------------------------------------------------------- 1 | # README.md 2 | We'll use this section to capture notes as we're brainstorming about a certain topic — and potentially other spots throughout the development of the documentation. 3 | 4 | It's just one big parking lot. 5 | 6 | To prevent any confusion with versioning, any content from this section that has already moved downstream to the document, itself, will be captured in the /archive directory under each topic. 7 | 8 | NOTE: This may result in different iterations of the same concept appearing in multiple files over time. We will normalize this as the content moves downstream into the final documentation. 9 | -------------------------------------------------------------------------------- /notes/pie/instigators.md: -------------------------------------------------------------------------------- 1 | # Instigators 2 | 3 | It is impossible to overstate the value of the instigator in this process. 4 | 5 | With PIE and with every other accelerator with whom we've worked, the instigator has been a critical participant. -------------------------------------------------------------------------------- /notes/pie/kickstarter/kickstarter-pie-cookbook-update-01.md: -------------------------------------------------------------------------------- 1 | # Wow! Thank you SO much! The PIE Cookbook is happening. 2 | 3 | (cue screaming) 4 | 5 | Whoof. 6 | 7 | We really appreciate all of you who have contributed to the campaign in these early hours. Thank you! We're truly looking forward to working with you. 8 | 9 | Thanks, again, 10 | Rick -------------------------------------------------------------------------------- /notes/pie/kickstarter/kickstarter-pie-cookbook-update-02.md: -------------------------------------------------------------------------------- 1 | # Unnecessarily proprietary 2 | 3 | Howdy folks, 4 | 5 | I'm still floored by this. We only just completed 24 hours of being live and the response has been incredibly humbling. Thank you SO much! 6 | 7 | In that light, I wanted to share a bit more. It's hard to capture, in words, what this campaign means to PIE. And what it means to me personally. But I tried. And it wound up being a lot of words. A. LOT. 8 | 9 | I won't subject you to my tortured prose, here. But if you're curious about some of the thinking and inspiration behind this project, please take a look at "[Unnecessarily proprietary: Why I'm insanely excited to open source our learnings from PIE](https://medium.com/portland-incubator-experiment/unnecessarily-proprietary-a709e850d8f4#.mv49oquej)." 10 | 11 | More soon! 12 | 13 | Take care, 14 | Rick 15 | 16 | -------------------------------------------------------------------------------- /notes/pie/kickstarter/kickstarter-pie-cookbook-update-03-backer.md: -------------------------------------------------------------------------------- 1 | # The pins are in (Backers only) 2 | 3 | Thanks so much to our friends at One Inch Round for their always awesome work. As a backer, you're going to look good sporting this pin. 4 | 5 | I mean, you already look good. You're going to look even better. -------------------------------------------------------------------------------- /notes/pie/kickstarter/kickstarter-pie-cookbook-update-04.md: -------------------------------------------------------------------------------- 1 | # What about your accelerator project is keeping you up at night? 2 | 3 | With all of the political discourse on social, we got to thinking about running an exit poll or two of our own. Don't worry. It's not about candidates. It's about something that's near and dear to our startup accelerator hearts. 4 | 5 | The question? If you're thinking about building a startup accelerator, what's keeping you up at night? 6 | 7 | [As far as Twitter goes, early indicators are that funding is the biggest question mark for many folks](https://twitter.com/piepdx/status/705076716390100992). Are you feeling the same way? 8 | 9 | We're looking forward to answering questions about how to fund accelerator activity — and who you should ask — in the PIE Cookbook. So if that's important to you, make sure to use your votes to pick that topic as one of the first subjects we cover. 10 | 11 | More soon! 12 | 13 | Take care, 14 | Rick -------------------------------------------------------------------------------- /notes/pie/kickstarter/kickstarter-pie-cookbook-update-05.md: -------------------------------------------------------------------------------- 1 | # What startup accelerators really do 2 | 3 | You may have already seen this, but we wanted to share this great piece by [Ian Hathaway](https://twitter.com/IanHathaway) entitled "[What startup accelerators really do](http://www.ianhathaway.org/blog/2016/3/1/startup-accelerators)." 4 | 5 | If you're interested in the PIE Cookbook because you're thinking about starting an accelerator, his piece — as well as a [recent research report by the Brookings Institution](http://www.brookings.edu/research/papers/2016/02/17-startup-accelerator-programs-hathaway) — are well worth the read. Even if you're just curious about accelerators, they're worth your time. 6 | 7 | > Accelerators are playing an increasing role in startup communities throughout the United States and beyond. Early evidence demonstrates the significant potential of accelerators to improve startups’ outcomes, and for these benefits to spill over into the broader startup community. However, the measurable impact accelerators have on performance varies widely among programs — not all accelerators are created equally. Quality matters. 8 | 9 | For more, visit "[What startup accelerators really do](http://www.ianhathaway.org/blog/2016/3/1/startup-accelerators)." -------------------------------------------------------------------------------- /notes/pie/kickstarter/kickstarter-pie-cookbook-update-06.md: -------------------------------------------------------------------------------- 1 | # Pacific Northwest Capital Scan recommends investing in accelerators 2 | 3 | Oregon performs a biennial "capital scan" both to determine the impact of investment in the region and to identify opportunities and gaps for future investment. This year's capital scan identified the following as the primary opportunity for the region: 4 | 5 | > #1: Invest in the foundational building blocks of the company formation ecosystem: entrepreneurial support organizations, accelerators, co-working spaces and the communities that form around them; the seeds that create viable returns/mission-aligned investment opportunities. 6 | 7 | If you're thinking about building an accelerator, we thought the findings in the latest capital scan would be valuable to you — whether you live in the Pacific Northwest United States or not. 8 | 9 | [Download the 2016 Pacific Northwest Capital Scan (PDF)](http://investcanopy.com/wp-content/uploads/2016/03/Canopy_PNW-Capital-Scan.pdf) -------------------------------------------------------------------------------- /notes/pie/kickstarter/kickstarter-pie-cookbook-update-07.md: -------------------------------------------------------------------------------- 1 | # Stretch goal #1: Chats, hangouts, and meet ups… oh my! 2 | 3 | You knew it was coming. It’s almost like a Kickstarter tradition or something. That’s right! It’s time for stretch goals. 4 | 5 | But you know us. This is an experiment. We’ve got to do this… differently. 6 | 7 | As we said, this isn’t about holding your feet to the fire. And this isn’t about the dollar total.It’s about the number of backers. It's about building community. 8 | 9 | Because the more varied the voices? The more valuable the PIE Cookbook becomes. And the more diverse the questions? The more likely we are to enable more people to help startups. And the more people who believe in the power of accelerators? The more potential to have the kinds of accelerators we all want — and need — to further our chosen creative pursuits. Tech, art, design, employees, food, beverage, writing, apparel, culture, students… whatever. 10 | 11 | It’s about collaborating. It’s about building a collection of best practices that can help anyone, anywhere accelerate anything. And it's about celebrating communities that want to support their founders, startups, mentors, and investors. Communities that want to embrace opportunities. Communities that want to provide their members with the greatest chances of success. Whether they want to build an accelerator or not. 12 | 13 | With that in mind, our stretch goals aren’t going to be based on getting more money. They’re going to be based on getting more people involved. 14 | 15 | ## Our goal is people… it’s people! 16 | 17 | That's right. We're after something money can't buy. We want the chance to meet — and hopefully spend time with — your startup community. 18 | 19 | With that in mind, here’s the pitch for our first Stretch Goal: 20 | 21 | - If your town gets 25 backers — as ranked by Kickstarter’s community metrics for this project — we’re inviting all of you to a 90 minute Slack chat about your startup scene. What’s that? Yes. You're correct. To have that chat, that would mean that you would get access to the PIE Cookbook Slack. And your very own #town channel. NOTE: We will not name the channel #town. We’ll actually name it for your town. 22 | - If your town gets 50 backers, we’ll get even more personal by inviting all of you to a 90 minute Google Hangout so we can talk through your most pressing questions and most immediate opportunities for helping startups. Plus, you'll get access to the PIE Cookbook Slack with a channel for your town. 23 | - If your town gets 100 backers, there’s no “virtual” about it. We’re coming to visit you in person so we can experience your amazing startup scene face-to-face. And, of course, you’ll also get access to the PIE Cookbook Slack and a channel for your town. 24 | 25 | Wait what? Yep. You heard that right. If your town boasts 100 or more backers for this project, that’s exactly the kind of town we want to visit. PIE cofounders Renny Gleeson and Rick Turoczy will travel to you. So we can hang out with your community. And discuss accelerators, startups, and whatnot, in person. 26 | 27 | When do we meet? It’s your community. You tell us. It can be early morning, midday, happy hour… whenever. It’s whatever works for the culture of your community. Maybe you’re a brunch town like Portland. Maybe you’re more an evening get-together sort of place. Maybe happy hours are your thing. Whatever works for you. 28 | 29 | So gather 25 of your peers and we’ll all jump in Slack. If your town has 50 people backing the project, we’ll host a Google Hangout to chat with one another. And if you get 100 people from your awesome startup community to back the project, we’ll travel to you. To hang out. And to chat face-to-face. 30 | 31 | How close is your town to hitting the stretch goal? We'll keep everyone up-to-date but you can always [check the community metrics for the PIE Cookbook campaign](https://www.kickstarter.com/projects/turoczy/pie-cookbook-an-open-source-guide-for-startup-acce/community). 32 | 33 | No dollar goal. No stretch funding goal. Just people. Whether folks back at the $1 level or contribute something more, we'll count them all equally. It doesn’t matter how much money your community contributes to the project. It simply matters how many people from your community participate in the PIE Cookbook Kickstarter campaign. (That said, the tshirts are pretty nice.) 34 | 35 | Ahem. 36 | 37 | Let’s expand the PIE Cookbook community. Let's hang out with your community. And if you happen to get all of your peers, mentors, and startups involved? We are so there. In person. With all of our awful PIE puns. -------------------------------------------------------------------------------- /notes/pie/kickstarter/kickstarter-pie-cookbook-update-08.md: -------------------------------------------------------------------------------- 1 | # PIE cofounder Renny Gleeson on why he's excited about the PIE Cookbook 2 | 3 | I think we could publish, all day every day, on why we're excited about this project. But we'll try to keep it under control. I mean, if you want more, [we're more than happy to sit down and chat with you about it](http://us1.campaign-archive1.com/?u=c5424c73e2781898d4f179b85&id=f12f27d122). 4 | 5 | In the meantime, here's the latest from Renny Gleeson, cofounder of PIE, on why he's excited about the PIE Cookbook project: 6 | 7 | > In the evolving, tech-fueled innovation space, brands need more tools than just a checkbook to thrive. Don’t just buy innovation, build it. … 8 | 9 | > The PIE Cookbook is an open-source, organically-grown, Kickstarted set of actionable insights and principles to help anyone accelerate anything they want. We are inviting our broader innovation community (old and new) to help us make accelerating great ideas a little less hard. It’s a toolset to enable brands to get more out of the accelerator format. More learning. More innovation. More collaboration. More community. 10 | 11 | For more, see Renny's post "[Brands are more than a checkbook](https://medium.com/portland-incubator-experiment/brands-are-more-than-a-checkbook-or-why-i-m-excited-about-the-pie-cookbook-9ab068a4eb98#.p6fkzpsmi)" on Medium. -------------------------------------------------------------------------------- /notes/pie/kickstarter/kickstarter-pie-cookbook-update-09.md: -------------------------------------------------------------------------------- 1 | # We're working to hold ourselves to the same standards as we do our startups 2 | 3 | When we're working with startups at PIE, we can often be overly critical. It happens. It's with the best intentions, but it happens. 4 | 5 | So we thought it was only fair that we turn that same harsh lens on ourselves. And critique how this project is working. And what we're learning. [And where we've screwed up](https://medium.com/portland-incubator-experiment/how-we-screwed-up-our-kickstarter-campaign-3f9ec20fbc12#.zfizpvvch). 6 | 7 | > You see, we’re always talking about all of the errors we’ve made with PIE. And how we’ve learned from them. So this — this screw up — seemed like a perfect “teaching opportunity.” And a way to be completely transparent about the campaign. Because when you’re proposing a project that you’ll be creating out in the open it makes sense to actually be open about the entire journey — not just the good, happy parts. 8 | 9 | For more, read "[How we screwed up our Kickstarter campaign… and how we’re working to fix it midstream](https://medium.com/portland-incubator-experiment/how-we-screwed-up-our-kickstarter-campaign-3f9ec20fbc12#.zfizpvvch)." -------------------------------------------------------------------------------- /notes/pie/kickstarter/kickstarter-pie-cookbook-update-10.md: -------------------------------------------------------------------------------- 1 | # We're stretching our first stretch goal: Upgrading to Stretch goal #1.1 2 | 3 | After we launched our first stretch goal for this project, I got feedback from a personal mentor of mine, Joe Maruschak. (Joe is a huge contributor to the Eugene, Oregon, startup community, working tirelessly on efforts like RAIN, among numerous other things.) 4 | 5 | He liked where PIE was going with the stretch goal idea. But he had some feedback that would enable us to make that stretch goal even better. (And luckily, we were in Slack, so we were able to capture all of his awesome feedback.) 6 | 7 | So we’re implementing that. Immediately. 8 | 9 | For context, our first stretch goal was that PIE will travel to meet with any community that gets 100 people to back the PIE Cookbook — even if they’re all $1 backers. 10 | 11 | Now, we're stretching Stretch goal #1. Upgrading it, if you will, to Stretch goal #1.1. (Yes, stretching a stretch goal is meta. We're an accelerator for accelerators. What do you expect?) 12 | 13 | So now, if your community can round up 100 backers, we’ll come visit your community in person plus… 14 | 15 | - Your community will get a special PIE tchotchke, available only to towns that reach 100 backers. 16 | - We’ll keep track of your community's progress and use PIE’s resources to raise the visibility of all of the awesome things happening in your community. 17 | - We’ll work to connect the dots among all of the amazing leaders in your communities to ensure you will always have access to the best and brightest from the world of accelerators. 18 | - While we're in town, we'll meet with community leaders — be they business, investment, economic development, government, higher education, or otherwise — to answer questions and provide context for the community benefits of the accelerator model. 19 | - We’ll highlight your community as an example in the PIE Cookbook, itself, and update the content with your progress as time goes on. 20 | 21 | Sound good? Good. So get on that. You’ve got a community to activate. And we’ll look forward to seeing you and your awesome community in person, soon. -------------------------------------------------------------------------------- /notes/pie/kickstarter/kickstarter-pie-cookbook-update-11.md: -------------------------------------------------------------------------------- 1 | # Stretch Goal #2: Help us celebrate Pi Day by helping nonprofit Caldera 2 | 3 | Part of the appeal of Kickstarter is the looming deadline. Racing against the clock. Can your favorite project raise the funds it needs to become a reality — before time runs out? 4 | 5 | Well that got us to thinking… what if stretch goals worked the same way? 6 | 7 | With that in mind, Stretch Goal #2 will end when Pi Day — March 14… you know, 3.14 — ends. It’s a campaign within a campaign. The goal? We’re going to be donating all proceeds (minus the cost of producing and shipping your selected reward) raised during Pi Day to one of our favorite nonprofits, [Caldera](http://calderaarts.org/). 8 | 9 | Not familiar with Caldera? They believe in the power of creativity — and its ability to change lives. 10 | 11 | > Caldera’s mission is to be a catalyst for the transformation of underserved youth through innovative, year-round art and environmental programs. 12 | 13 | > Focusing on youth from both urban and rural communities with limited access to educational, economic, and physical resource opportunities, Caldera nurtures individual creativity to ignite self-expression and transform the way young people engage in their lives, families, and communities. 14 | 15 | What inspired us to raise money for Caldera? We’re harkening back to one of PIE’s earliest experiments, 30 Hour Day, the first ever 30 hour livestreamed telethon — hosted at PIE — that helped raise money for local charities. During those 30 hours, we managed to raise nearly $10,000 in cash, food, and toys. We’re sincerely hoping we can do something equally meaningful for Caldera. 16 | 17 | There’s no better day to back the PIE Cookbook given that your dollar earns you a vote, moves your community one step closer to Stretch Goal #1, and ultimately helps a great cause like Caldera. 18 | 19 | Everybody wins. And we and Caldera greatly appreciate your generosity. 20 | 21 | Happy Pi Day! 22 | Renny and Rick 23 | 24 | P.S. If you would like all of your funds to go to Caldera, we suggest skipping the socks, hats, and shirts, and backing the project at $3.14 — or your preferred dollar amount. -------------------------------------------------------------------------------- /notes/pie/kickstarter/kickstarter-pie-cookbook-update-12.md: -------------------------------------------------------------------------------- 1 | # Stretch Goal 3.14: Let’s get cooking 2 | 3 | Howdy Kickstarter types! 4 | 5 | Hope you’re doing well. Our community around this project keeps growing with awesome people from all over the world. To keep it going, we’ve just created another stretch goal focused on getting even more awesome folks involved. 6 | 7 | As we’ve said a few times, we’re more interested in community than capital. So just like Stretch Goal 1 and Stretch Goal 1.1 — get 100 people from your community to back (even if it’s just $1) and PIE will come visit your town, in person — we’re using this stretch goal to encourage even more people to join this project. 8 | 9 | (Speaking of Stretch Goal 1.1, the folks in London are rallying support in their community (https://twitter.com/macfarbt/status/709842287178686467). We’re hoping your community can do the same. We're really looking forward to meeting with a bunch of awesome startup communities out there.) 10 | 11 | So here it goes… 12 | 13 | We’ve said from the outset that we’re pursuing this project whether it’s funded or not. Well, it’s currently funded and it looks like this project should complete successfully in a couple of weeks. So what are we waiting for? We should get cooking. 14 | 15 | If we can hit 314 backers, we’ll do just that. Once the Kickstarter backer counter reaches 314 people — regardless of the amount raised — we’ll open up our Github repository so you can start following the project. And we’ll invite every PIE Cookbook backer to join our new PIE Cookbook Slack instance so that you can start collaborating with us — and 314+ of your startup accelerator peers — in real time, before anyone else gets the chance to join. 16 | 17 | Tell your colleagues, friends, and community members. Once we get to 314 backers, we’re kicking off the project. And we can all get cooking, sooner rather than later. -------------------------------------------------------------------------------- /notes/pie/kickstarter/kickstarter-pie-cookbook-update-13.md: -------------------------------------------------------------------------------- 1 | # New backer reward level added 2 | 3 | As we work to build up this community of awesome folks, we're always looking for ways to encourage more people to participate. And collaborate. Sometimes it's just cajoling. And sometimes it's proposing interesting stretch goals. But the tried and true method is solid backer rewards. 4 | 5 | With that in mind, we wanted to let you know that we've added a new backer reward level, "Fill up on Portland tech." Backing at that $75 reward level will secure you one ticket to TechfestNW, the annual Portland tech event that PIE helped cofound, being held April 25-26, 2016, in beautiful Portland, Oregon. 6 | 7 | But you better act fast. Supplies are limited. 8 | 9 | For more on the event, see http://techfestnw.com/. -------------------------------------------------------------------------------- /notes/pie/kickstarter/kickstarter-pie-cookbook-update-14.md: -------------------------------------------------------------------------------- 1 | # No interest in building a startup accelerator like PIE? Good. 2 | 3 | We've been chatting with lots of folks about the PIE Cookbook. Including discussing our motivations for open sourcing the document and encouraging others to start accelerators. 4 | 5 | And while those conversations have been awesome — one on one — it's become painfully obvious that we haven't done such a good job of broadly conveying those themes. To solve that, [we thought that jotting down some of our thoughts might be helpful](https://medium.com/portland-incubator-experiment/no-interest-in-building-a-startup-accelerator-like-pie-good-f31ecbd14e05#.491zrsk8t). 6 | 7 | > With that in mind, please don’t try to recreate PIE. In fact, we would hate for you to bake our flavor of PIE. This isn’t a sleeve of prepared cookie dough that you halfheartedly slice onto a cookie sheet. This is a “Bake your own” proposition. 8 | 9 | > This is a recipe. And everyone has their own unique ingredients. This is about rolling up your sleeves and getting your hands in the mix. Making the recipe yours. Experimenting, manipulating, iterating, exploring, and improving. 10 | 11 | The world needs more variety — not less. And together, we all get better. 12 | 13 | For more of our thoughts, please read "[No interest in building a startup accelerator like PIE? Good.](https://medium.com/portland-incubator-experiment/no-interest-in-building-a-startup-accelerator-like-pie-good-f31ecbd14e05#.491zrsk8t)" -------------------------------------------------------------------------------- /notes/pie/kickstarter/kickstarter-pie-cookbook-update-15-backer.md: -------------------------------------------------------------------------------- 1 | # Achievement unlocked! Let’s get cooking (Backers only) 2 | 3 | Wow. You are AWESOME! 4 | 5 | Roughly 48 hours ago, we added a new stretch goal. The objective? Get more people joining the community. How? By offering to start this project early if we hit 314 backers. 6 | 7 | And guess what? You did it. We have more than 314 backers! That means that the PIE Cookbook is now live. 8 | 9 | And while there isn't much to see at this point, as a backer, you now have access to the PIE Cookbook Github repository (https://github.com/piepdx/pie-cookbook) and the PIE Cookbook Slack instance. 10 | 11 | *NOTE: We do not have access to your email address. Please feel free to message me on Kickstarter (or you can just reply to your initial thank you email) with the email address that you’d prefer to use. We will manually add you to the PIE Cookbook Slack.* 12 | 13 | While we're super excited to be kicking off the project — two weeks early — let’s not forget that we're still two weeks away from the campaign ending. And that means that there is still work to do. 14 | 15 | First, we’re convinced that there are other communities out there who could derive value from the PIE Cookbook — but most of them have never even heard of the project. If you can help spread the word, we’ll all be better for it. So thank you, in advance, for doing that. 16 | 17 | Second, over the next two weeks, you still have the opportunity to rally your community around our first stretch goal. We’re committed to traveling to meet any community that gets 100 backers for this project (even if those backers are at $1 a piece). So if you’d like to see PIE in person, get your community involved. And we’ll be there. 18 | 19 | If you want an example for inspiration, you should see what the communities of Eugene and Corvallis, Oregon are doing. 20 | 21 | Thanks again for all of your support, kindness, and willingness to engage in this experiment with us. 22 | 23 | Let's get cooking! -------------------------------------------------------------------------------- /notes/pie/kickstarter/kickstarter-pie-cookbook-update-16.md: -------------------------------------------------------------------------------- 1 | # Eugene and Corvallis at it again, and now, London calling 2 | 3 | For those of you in the Pacific Northwest, news of Eugene and Corvallis competing with one another will be no surprise. (For those of you who aren't… Eugene, home of the University of Oregon, and Corvallis, home of Oregon State University, have an ongoing rivalry that spans more than a century.) We just didn't expect that rivalry to flare up around our little old project. But if that means we get to meet more awesome startup types, so be it! 4 | 5 | For those of you keeping score at home, Eugene is edging ever closer to the century mark in backers, meaning that PIE gets to come visit. Corvallis has almost unlocked the Slack chat stretch goal. 6 | 7 | In related news… Today, London entered the fray, posting a call to rally backers and get the PIE crew on the other side of the pond. They've already arranged with coworking space WeWork Chancery Lane to host. 8 | 9 | It's not too late to get your community involved. Remember, all it takes is 100 backers. Even if those backers only contribute one dollar each. (100 x $1 = PIE) You heard that correctly. One hundred backers and PIE cofounders Renny and Rick will come visit your town to help your startup community however we can. 10 | 11 | We'd love an excuse to come visit you! 12 | 13 | *REMINDER: Since we're over 314 backers, the PIE Cookbook repository is open on Github. And the PIE Cookbook Slack is now open for business. Just drop us a note with your preferred email address and we'll get you invited.* -------------------------------------------------------------------------------- /notes/pie/kickstarter/kickstarter-pie-cookbook-update-17-backer.md: -------------------------------------------------------------------------------- 1 | # Join us on Slack! (Backers only) 2 | 3 | Just a reminder that if you're a backer, you have unlocked early access to the PIE Cookbook Slack instance. And if you're from Corvallis, Eugene, or Portland, you've already unlocked the Slack stretch goal that gives you your own channel on our Slack. 4 | 5 | To be added to Slack, just send me a note with your preferred email address and I'll send you an invite. 6 | 7 | Know someone else who should be joining this conversation? There are only a few more days before the campaign ends. So please, tell your friends. Because we'd love to come visit you in person. All it takes is a buck. -------------------------------------------------------------------------------- /notes/pie/kickstarter/kickstarter-pie-cookbook-update-18.md: -------------------------------------------------------------------------------- 1 | # Closeout sale: We’re slashing 33% off of our Stretch Goal 2 | 3 | The past month has been amazing! So many great people. And we've been completely humbled by the outpouring of support. 4 | 5 | But as much as we hate to admit it, our time here on Kickstarter is winding down. We’ve only got about a week to go. But we’ve still got a warehouse full of Stretch Goals. And these Stretch Goals aren’t going to stretch themselves. 6 | 7 | But get ready to be happy. Because our loss is your gain. Act now and you and your startup community can get these brand new, full featured Stretch Goals… at a fraction of the original Stretch Goal number. 8 | 9 | We’re talking specifically about Stretch Goal 1. You know, the Stretch Goal that gets PIE cofounders Renny and Rick to travel to your town once you hit 100 backers — even if those backers only contribute $1 each? 10 | 11 | Admittedly, that stretch goal may have been a bit of a stretch. But we’d still love nothing more than to come visit you. So since it's the last week of the campaign, we're going to make that Stretch Goal better than ever. 12 | 13 | How? By slashing that Stretch Goal by 33%. 14 | 15 | That’s right! Now any town that gets 66 backers — at any level — will be getting an in person visit from PIE. Not possible? Tell that to the awesome startup community in Eugene, Oregon. They've already exceeded that Stretch Goal and secured an in-person visit from PIE. And we know that your community can too! (NOTE: The discounted Stretch Goal of 66 backers guarantees an in-person visit from Renny or Rick. It’s discounted, after all. Renny and Rick are still guaranteed for 100+ backer towns.) 16 | 17 | But wait! There’s more! Back the project today. Hit Stretch Goal 1 with 66 backers… and we’ll throw in Stretch Goal 1.1 at no extra charge. It’s like hitting two Stretch Goals for fewer people than one. 18 | 19 | Act now! This deal won’t last forever. (Seriously, I mean, the campaign ends on April 1, 2016.) 20 | 21 | We’d love to come visit you and your awesome startup community. So just get 66 backers — at any amount — and PIE will visit your town. -------------------------------------------------------------------------------- /notes/pie/kickstarter/kickstarter-pie-cookbook-update-19.md: -------------------------------------------------------------------------------- 1 | # Another learning opportunity: 500 Startups Venture Capital Unlocked: Accelerator edition 2 | 3 | Howdy backers! 4 | 5 | Given your curiosity about startup accelerators, we thought this offer from our friends at 500 Startups might be of interest to you, as well. It's the [500 Startups Venture Capital Unlocked: Accelerator edition](http://500.co/announcing-vc-unlocked-accelerator-edition/). 6 | 7 | > In Venture Capital Unlocked: Accelerator edition, current and aspiring accelerator managers will take a 1 week deep dive into everything it takes to start and run a successful program. 8 | 9 | > It will be taught by 500 founding partners Christine Tsai and Dave McClure, along with managing partner Bedy Yang and various investment partners involved in running 500’s accelerator (Marvin Liao, Elizabeth Yin, Sean Percival and many others). They will offer an inside look at the 500 Startups accelerator playbook for the first time. 10 | 11 | If you're interested, here's the preliminary agenda for the week-long bootcamp. 12 | 13 | For more information or to apply, visit 500 Startups. 14 | 15 | NOTE: PIE is not affiliated with this program. We're just passing it along because it seems interesting :) 16 | 17 | P.S. We still have a few days to go on the PIE Cookbook campaign. So please tell your friends. We're still hoping to add some more awesome towns to our road trip! -------------------------------------------------------------------------------- /notes/pie/kickstarter/kickstarter-pie-cookbook-update-20.md: -------------------------------------------------------------------------------- 1 | # What's working in startup acceleration? 2 | 3 | Howdy! 4 | 5 | We wanted to make sure that folks saw a recent report from the Global Accelerator Learning Initiative. The report, entitled "What’s Working in Startup Acceleration Insights from Fifteen Village Capital Programs," details specific impacts of accelerator programs and predicts what's to come in the world of accelerators. 6 | 7 | > Ultimately, this report aims to provide accelerator program managers and funders with practical lessons and insights to consider for their own programs, based on the experiences and analysis of these fifteen Village Capital programs. Through this and other research efforts, we hope to stimulate more evidence-based learning and practice improvements in the entrepreneurial acceleration sector. 8 | 9 | [Download the report (PDF)](https://c.ymcdn.com/sites/ande.site-ym.com/resource/resmgr/GALI/GALI_Report_032816.pdf) 10 | 11 | Hope that helps, 12 | Rick -------------------------------------------------------------------------------- /notes/pie/kickstarter/kickstarter-pie-cookbook-update-21-backer.md: -------------------------------------------------------------------------------- 1 | # This is just the beginning of the conversation (Backers only) 2 | 3 | Thanks again to all of you who have helped support this project with your time, effort, and hard-earned money. We really really appreciate it. 4 | 5 | As you can probably tell from our overly communicative Kickstarter campaign, keeping the lines of communication open is really important to us. With that in mind, we wanted to highlight a few of the ways we'd like to stay in touch with you as this campaign moseys off into the sunset in about 24 hours. 6 | 7 | - PIE Cookbook Slack: We've established a Slack instance specifically for backers. If you're not familiar with Slack, that's cool. No worries. This will be a good intro. It's a really easy to use chat room. Not only will it help you stay in contact with us, it will help you stay connected to your peers. (Eugene and Corvallis, Oregon, have already been going back and forth and scheming using Slack.) If you're interested in joining us, please send us your preferred email address and we'll get you added. (We cannot see your email address on Kickstarter.) 8 | - PIE Cookbook on Github: This is an open source project, after all, so we'll be building it out in the open. Never used Github? It's basically a place for us to share all of our files and stuff with you. Not feeling comfortable with that level of geekiness? No worries. We're going to keep everything text based. If you set up a Github account, you can follow our progress. Or you can just stay tuned to the #github room on the Slack instance. 9 | - Monthly standups: We'll plan on having monthly (virtual) standups in the Ask Me Anything (#ama) room on Slack. Everyone is welcome to attend, ask questions, air grievances, complain about my grammar… whatever. Our first standup will be Monday, April 4, 2016 at 10:00AM Pacific Time (-07:00GMT). Can't make it? Feel free to propose questions at your convenience in the #ama room. And we'll make sure everything is archived for your reference, following the standup session. 10 | - Kickstarter updates: Just because the campaign is over doesn't mean we're through using Kickstarter. Even if you don't participate in any of the options above — which is totally fine — we'll still provide regular updates for you here. 11 | - The usual spots: For a lot of you, Kickstarter is new. So you might not be comfortable with this being your communication platform. If you're more likely to interact with us on social channels, please feel free to follow PIE on Twitter or like PIE on Facebook. Prefer email? We've got you covered. Visit the PIE site and scroll down to the bottom of the page. Or you can sign up here. 12 | 13 | Thanks again! We're looking forward to working with you. And getting your feedback. Not much longer now and we'll be building out the PIE Cookbook! But there's still plenty of time to send folks our way or encourage your peers to join in the fun. 14 | 15 | More soon! 16 | 17 | Thanks in advance, 18 | Rick -------------------------------------------------------------------------------- /notes/pie/kickstarter/kickstarter-pie-cookbook-update-22.md: -------------------------------------------------------------------------------- 1 | # Thank you so much for making this crazy experiment a reality 2 | 3 | Wow. Thank you. Thank you for believing in this effort. Thank you for supporting this crazy idea. Thank you for encouraging us to give away everything we've learned over the past eight years with the hopes that it will help someone else do something amazing and awesome for someone else amazing and awesome. 4 | 5 | Thank you. Thank you. Thank you. 6 | 7 | I can't help but think that this is a moment to take a deep breath and reflect. I'm humbled by the community that has come together around this project. And I'm proud to be among you. This is a big deal. And I'm going to take a few minutes to take that in. 8 | 9 | Maybe even a weekend :) 10 | 11 | Because like so many things in the startup world, this thing that appears to be an achievement, an accomplishment, a finish line, is — in reality — another starting line. And I can't wait to start the next leg of this race. 12 | 13 | I'm really really happy to have the opportunity to work on this with you. Thank you again. 14 | 15 | Love, 16 | Rick 17 | 18 | P.S. SQUEEE! Be on the lookout for those backer surveys! -------------------------------------------------------------------------------- /notes/pie/kickstarter/kickstarter-pie-cookbook-update-23-backer.md: -------------------------------------------------------------------------------- 1 | # Quick update on our first week of post-funding progress 2 | Howdy, 3 | 4 | Hope you had a good week, free from my constant updates. Just so we don't drop into complete radio silence, I wanted to provide a quick update for everyone. 5 | 6 | * We're in the midst of building the backer surveys. Be on the lookout for those next week. We need your help choosing where to start this whole thing. Plus, you'll have the opportunity to tell us which town gets credit for your participation — and might qualify for an in-person visit from PIE. 7 | * If you're not already on the PIE Cookbook Slack, you should have an invite waiting for you in the email associated with your Kickstarter account. (It may have wound up in spam.) Please join up as soon as you can as more than 200 of us are already delving into PIE Cookbook stuff over there. 8 | * We're finalizing designs on the socks (for all of you who were smart enough to pick that reward). 9 | * And remember, the PIE Cookbook is being built out in the open on Github. You can monitor progress there and review the living outline here: https://github.com/piepdx/pie-cookbook/blob/master/notes/outline.md 10 | 11 | Have a good weekend! 12 | 13 | Hope that helps, 14 | Rick -------------------------------------------------------------------------------- /notes/pie/kickstarter/kickstarter-pie-cookbook-update-32.md: -------------------------------------------------------------------------------- 1 | # Your votes are in. And the topic we'll be starting with is… 2 | 3 | Thanks so much, again, to all of our amazing backers for supporting this project. And for taking the time to participate in our little voting experiment. 4 | 5 | We've managed to tally all of the votes from the campaign and wanted to take a few moments to share the results. 6 | 7 | ## PIE Cookbook topics: Where to begin? 8 | 9 | One of the areas we asked you to help us consider was where the heck we should start this whole PIE Cookbook thing. What's most confusing? Where do you need help? What's perplexing? 10 | 11 | Admittedly, there's a ton to think about when you're considering building an accelerator. And we have a wealth of topics we're looking forward to covering throughout the course of this process. But we really wanted some guidance on where to start. And we were hopeful that giving you the chance to vote would help us focus on the things that were most important to you. 12 | 13 | You didn't disappoint. 14 | 15 | While a few of the topics were neck and neck, here's how we finally netted out. And the order in which we'll be attacking topics is… 16 | 17 | 1. Community (Identification, development, management) 18 | 2. PIE (History, experiments, mistakes, lessons learned, happy accidents) 19 | 2. Funding (Covering the costs of operating an accelerator) 20 | 3. Startups (Recruiting, selecting, on boarding, managing) 21 | 3. Logistics (Day-to-day activities, running a coworking space/accelerator) 22 | 4. Mentors (Recruiting, selecting, on boarding, managing) 23 | 6. Partnerships (Recruiting, managing) 24 | 7. Space (Square footage, infrastructure, furniture) 25 | 26 | ## PIE Cookbook Slack: Keeping the conversation going 27 | 28 | We have been running a private instance of the PIE Cookbook Slack for a while now, but we were curious as to whether it would be even more useful as a public Slack channel. 29 | 30 | Well, backers have spoken. 31 | 32 | Nearly 95% of the votes cast recommended that we open up the PIE Cookbook Slack to the broader community. So that's exactly what we'll be doing. 33 | 34 | If you're a Kickstarter backer and haven't yet responded to your Slack invite, please do that at your earliest convenience. We'd like to make sure that you have access to a special private channel for our backers before we open up the platform to the public. 35 | 36 | ## PIE Cookbook roadshow 37 | We're just going to chalk this one up as a failed experiment. 38 | 39 | We asked folks to cast votes for which town we should visit as part of the PIE Cookbook roadshow, continuing on a theme we started during the course of the Kickstarter campaign: [any town that got more than 66 votes would be a candidate for a visit from the PIE team](https://www.kickstarter.com/projects/turoczy/pie-cookbook-an-open-source-guide-for-startup-acce/posts/1529377). 40 | 41 | In the long run, this voting reflected (or fell short) of [Kickstarter's community metrics on the campaign](https://www.kickstarter.com/projects/turoczy/pie-cookbook-an-open-source-guide-for-startup-acce/community). So we're just going with that. 42 | 43 | See you soon, Eugene, Oregon! 44 | 45 | ## Next steps 46 | In case you missed it, [we've outlined a proposed process for moving forward with this project](https://medium.com/portland-incubator-experiment/kickstarter-pie-cookbook-update-31-2acf760d014c#.2z41ccpw3 "Proposing a process for building the PIE Cookbook in public"). And we're already underway composing content around the topic of "community." 47 | 48 | As always, you can participate by following along on [Github](https://github.com/piepdx/pie-cookbook/) or by joining us on Slack. 49 | 50 | Just as important, we're hard at work producing your awesome backer rewards. So that you can be appropriately ensconced in PIE gear throughout this whole thing. 51 | 52 | Thanks again for your help. More soon. Stay tuned! 53 | 54 | Take care, 55 | Rick 56 | -------------------------------------------------------------------------------- /notes/pie/pie-lead-in.md: -------------------------------------------------------------------------------- 1 | The PIE accelerator, unbeknownst to us, started in 1995, 15 years before PIE officially became an accelerator. 2 | 3 | It doesn't have to take that long for your community. But it did for ours. 4 | 5 | This isn't a guide. Or a regimen. This isn't the answer. This is simply how PIE became an accelerator. There is no right timespan for this. For some communities, it happens more quickly and organically. For others, it takes a long, long, long time. 6 | 7 | I would argue that, in many ways, we're not done. And an accelerator might not be the final answer. And we're still working toward even becoming something truly valuable and sustainable. 8 | 9 | So with that in mind… 10 | -------------------------------------------------------------------------------- /notes/pie/sidebar-fresh-pie.md: -------------------------------------------------------------------------------- 1 | # Fresh PIE 2 | 3 | ![PIE's first pie – – sweet, delicious, local Marionberry. Mmmmm. Damn fine PIE. (pie-pie-gleeson.jpg)](/source/images/pie-pie-gleeson.jpg) 4 | 5 | Pie is delicious. And you get out what you put in. To a Pie, that is. 6 | 7 | Bear with me. 8 | 9 | And I believe if you put fun interesting driven people with varied backgrounds, skills and interests into an enclosed location, unexpected things will happen. So we are doing an experiment in the un-rented retail space inside the W+K building in Portland. 10 | 11 | Portland Incubator Experiment, or PIE for short. It's called an experiment, because we have no clue how this thing will net out. 12 | 13 | It started with conversations years ago, chance and intentional encounters and a lot of “wow, wouldn’t it be cool if…” rap sessions with people I care about and respect, inside and outside W+K. 14 | 15 | And now it’s happening. And I don’t think anyone involved can really believe it did. 16 | 17 | But we’re pretty psyched. 18 | 19 | So why hasn’t W+K made a lot of noise about it? That’s my fault. Believe it or not, I’d rather talk about what comes out of the space than what MIGHT come out of the space. I am sick of bombastic claims of the “new better different” bilge that agencies crap out regularly. 20 | 21 | Show me, I say. Don’t talk — demonstrate. 22 | 23 | For another thing, it’s not owned by W+K – PIE is a collaborative that everyone inside will participate in. Hopefully it will foster interconnections between previously disparate groups and corresponding quantum leaps in thinking. At very least, it may generate some delicious slices of pie. Like the marionberry one we had today. 24 | 25 | And the folks in the space are kicking ass on a shoestring – everything is recycled and easy to break down. Our partners bring their own mobile devices and computers. What you do see, if you walk or stop by, we built cheap in under 30 days. 26 | 27 | So no, there hasn’t been an official press release, and no I haven’t dropped hints in my twitter stream or blog. Because until people were inside, there wasn’t anything but a neat idea. Most importantly, the folks behind this and I have also been VERY concerned that people in the space retain their intellectual property. 28 | 29 | So I’ve been working with lawyers and management and the folks inside to ensure that no-one loses what they have by participating. 30 | 31 | And I’ve always wanted this to be about the people inside and what they do. Sure, W+K is involved – I work for them, after all – and yes, I’ve been spearheading it from our side. But it’s our work that will speak for us, one way or the other. 32 | 33 | What’s in it for W+K? 34 | 35 | The chance to learn. An opportunity to help our clients make leaps. The chance to make participatory digital culture. And if something really blows up big, we’ll all be happy. 36 | 37 | But even if it doesn’t, that’s ok, too. 38 | 39 | Because this is about learning. About failing forward fast with people who understand that in digital culture, you innovate or die. 40 | 41 | We have hopes, but no preconceptions. 42 | 43 | And who the heck doesn't love a good PIE? 44 | 45 | [“Fresh PIE” Renny Gleeson (August 10, 2009)](http://www.rennygleeson.com/fresh-pie/) 46 | 47 | 48 | -------------------------------------------------------------------------------- /notes/pie/sidebar-getting-even-more-creative.md: -------------------------------------------------------------------------------- 1 | getting-even-more-creative.md 2 | 3 | We thought there was something there. And potential for Portland. 4 | 5 | Hold that thought. 6 | 7 | Along about the same time, Renny Gleeson over at W+K was pitching a similar idea to the folks at Wieden. He was dreaming of something that would connect W+K with the Portland tech community. Something that would help W+K stay in touch with the latest tech developments and would help the Portland tech community thrive. 8 | 9 | And W+K just so happened to have a retail space in its building—sitting empty—that could serve as the perfect location for this sort of thing. 10 | 11 | And that led to one of those serendipitous Portland moments when James Keller—who had worked with Renny before leaving W+K to form Small Society—suggested Renny bounce his idea off of some the tech types in town. 12 | 13 | I guess everyone else was busy. Because he decided to chat with me. 14 | 15 | As he laid out the idea and my eyes got wider and wider, we happened upon what can only be categorized as a Reese’s “you got your creative chocolate in my startup peanut butter” moment. 16 | 17 | “[Getting even more creative: Wieden+Kennedy launches Portland Incubator Experiment](http://siliconflorist.com/2009/08/05/creative-wieden-kennedy-wk-launches-portland-incubator-experiment-pie/)” Silicon Florist (August 5, 2009) -------------------------------------------------------------------------------- /notes/pie/staffing.md: -------------------------------------------------------------------------------- 1 | # Staffing considerations 2 | 3 | Beyond job description, it’s important that your management team is a healthy balance of professionalism and personalism. It really doesn’t matter who on the team possesses which traits. There needs to be the combined capability of creating vulnerabilities so you can surface problems, someone who can determine what true needs are, someone who can be conversational and interpersonal, someone who is a good connector, someone who can be a hard ass. 4 | 5 | The right team is a healthy version of good cop, bad cop. They can and should be comfortable switching in and out of these roles but it’s important to find a balance that compliments one another. If everyone in the management team is a carbon copy of one another regarding than your accelerator is only going to work for one sort of person. The fact of the matter is, your accelerator is going to be made up of a bunch of different folks. You’re likelier to succeed in having an impact on them if you have a team that is adaptable and can work in different ways. 6 | 7 | The MD + PM should each have their own weekly check-ins with companies participating in the program, and meet to compare notes. Ideally with different communication styles and the added benefit of hearing problems differently, the PM + MD will have a greater perspective on any needs or issues their companies are having. -------------------------------------------------------------------------------- /notes/pie/standups/20160404.md: -------------------------------------------------------------------------------- 1 | # Stand up for April 4, 2016 2 | 3 | *We will hold regular standups (currently monthly) for this project in the PIE Cookbook Slack channel.* 4 | 5 | Given that this was the first stand up, there wasn't a ton to cover. We're just kicking off the project. 6 | 7 | A complete archive of the discussion can be found at http://piecookbook.slackarchive.io/ama/-/1459456556/1459792018/1459789270000042/ (in reverse chronological order) 8 | 9 | ## High level 10 | 11 | - This week, we’ll be focused on Kickstarter backer surveys, which topics we attack first, and supporting infrastructure (like Slack and Github). 12 | - Be advised that Kickstarter backers have "votes" to cast as to what topics are covered first. These votes will be cast through backer surveys. 13 | - We're also brainstorming content for the PIE Cookbook in https://github.com/piepdx/pie-cookbook/blob/master/notes/outline.md 14 | - Use Github issues to provide feedback on direction https://github.com/piepdx/pie-cookbook/issues?utf8=%E2%9C%93&q=is%3Aissue+ 15 | 16 | 17 | ## Questions and answers 18 | 19 | ### So as of now what is the ultimate vision…. pie cookbook website? 20 | 21 | We see the PIE Cookbook as the beta version of this documentation. Our hope is that the open source project will help all of us generate a much broader view than simply "what PIE did." Ideally, this will result in an “Accelerator Cookbook” that includes many perspectives and ideas for applying the accelerator concept. 22 | 23 | But we had to start somewhere. So we started with what we know :) 24 | 25 | And this content may live as other content besides just web. Maybe video? Maybe curriculum? Maybe certification? Who knows? We don't. But we're hoping this project reveals better ways to digest and use this information. If that's not web-based, we're totally fine with that. 26 | 27 | We’re super curious about how applicable our learnings are, on a topic by topic basis. Would this only work at PIE? Only in Portland? Only if you’re not in the Bay Area? Only in the US? Only in tech? Or is it an example of something that is applicable anywhere? 28 | 29 | ### Is the information you’re looking to give solely based around accelerators? 30 | 31 | We’re going to start with accelerators. But also provide details on how other people have used the model to do other interesting things. We see the “accelerator” concept as an educational structure that has a variety of applications beyond helping early stage startups. 32 | 33 | **I’m just trying to see if it could potentially be used by municipalities to help foster technology in the community** 34 | 35 | Absolutely! Our work with Portland government ([Startup PDX Challenge](http://www.pdc.us/startuppdxchallenge.aspx)) and Oregon government ([Oregon Story Board](http://www.oregonstoryboard.org/)) should be informative in that regard. 36 | 37 | ### So not just accelerating startups…then what else would this be accelerating? 38 | 39 | It could be used for employees [like Daimler has done](https://medium.com/portland-incubator-experiment/no-interest-in-building-a-startup-accelerator-like-pie-good-f31ecbd14e05#.9eguaarw8). Could be for brainstorming. 40 | 41 | **So an internal type of accelerator as well? I wish I had another word to use but I see what you mean.** 42 | 43 | We think the construct has a ton of applications. 44 | 45 | ### The best way requet things to be included is by Github issues reports, correct? 46 | 47 | Yes please! That way, everyone can see them, whether they are part of the Slack channel or not. 48 | 49 | ### Will there be tasks that can be 'outsourced' to the community? 50 | 51 | As the project has more there there, we’ll definitely be looking for that kind of help. For now, PIE has a lot of content to churn out :) 52 | 53 | ### Best way to just follow github channel? 54 | 55 | Yep ;) 56 | 57 | -------------------------------------------------------------------------------- /notes/space/README.md: -------------------------------------------------------------------------------- 1 | # README.md 2 | We'll use this section to capture notes as we're brainstorming about a certain topic — and potentially other spots throughout the development of the documentation. 3 | 4 | It's just one big parking lot. 5 | 6 | To prevent any confusion with versioning, any content from this section that has already moved downstream to the document, itself, will be captured in the /archive directory under each topic. 7 | 8 | NOTE: This may result in different iterations of the same concept appearing in multiple files over time. We will normalize this as the content moves downstream into the final documentation. 9 | -------------------------------------------------------------------------------- /notes/space/space-minimal-valuable.md: -------------------------------------------------------------------------------- 1 | 2 | # Create a Minimally Valuable Space 3 | 4 | We've noticed a tendency in the industry to deck out your coworking or shared workspace with the latest and greatest. Swanky furniture. Gaming equipment. Tons of outlets. Sit/stand desks. Comfy office chairs. 5 | 6 | Yes, people ooh and ah when they see the space. Yes, it makes it easy to defend the prices you're charging them for space. And yes, it provides a certain sense of pride for the folks running the space. 7 | 8 | But, to be honest, more often than not, those are false positives. They don't really make for a great community space. 9 | 10 | Don't feel guilty. PIE fell for this trap too. Our initial build out was set design to be the quintessential startup workspace. Complete with closet door and sawhorse desks. 11 | 12 | It didn't work. 13 | 14 | What we've learned over the years is that the space must be viable and functional. Aside from that, it should never be comfortable. It should never be easy. The space should be just difficult enough. Without being frustrating. 15 | 16 | It's not that we couldn't make the space more comfortable. It's that it shouldn't be more comfortable. The space, like building a startup, should be difficult. And awkward. It should always cause friction. And discomfort. 17 | 18 | Your only requirements are a solid wifi connection, access to power, a surface for a laptop, and a chair. That's it. Beyond that, you provide less than is needed. 19 | 20 | Think less office space, more coffeeshop or bar. 21 | 22 | You should have too many people in the space. It should be noisy. You should have too few conference rooms. People should be eavesdropping whether they want to or not. You should have passible coffee and, if it fits your culture, beer. And most of all, everyone should be in one another's way. 23 | 24 | ![There are no forks](/source/images/2015-03-13-13.55.06.jpg) 25 | 26 | Why put the startups through additional stress and turmoil? Because your objective is not to coddle startups. If you want to coddle them, then start an incubator. Protect them with warmth and comfort. Shield them from the outside world. Create a utopian existence for them. That's what an incubator should do. 27 | 28 | Your job as an accelerator, however, is to get them moving further faster than they would on their own. Your job is to get them to grow up and out. Your job is to create a microcosm. A biome of startup life. They same way it exists in the real world. But with a few safety nets strewn here and there. 29 | 30 | And then you need to poke the startups so that, from time to time, they tumble into those safety nets. 31 | 32 | If you provide a space that is too comfortable and too accommodating then the startups will stay there. Forever. And that isn't what you want. You want churn. You want growth. You want backfill. And activity. And hustle. 33 | 34 | Yes, they're often amazing people to be around. But you need to get them out of the space. And you need to encourage them to move out. And they need to want to do that. That needs to be a motivating factor. An unspoken rule. 35 | 36 | > We are inviting you into our space because we want you to leave. 37 | 38 | Like being embarrassed to bring your friends over to your parents house because their idea of decor is decades out of date. Your accelerator is — both literally and figuratively — their parents' basement. And it should be just as awkward as that arrangement. 39 | 40 | There are also fringe benefits to this sort of interior design. You, as an accelerator staff remain scrappy. You feel less comfortable. You don't have it easy, either. And that's just how it should be. 41 | 42 | ![PIE's kitchen "table"](/source/images/pie-kitchen-table.jpg) 43 | 44 | Potential investors walking into the space shouldn't see opulence. They should see a situation that they want to help your startups escape. The space should inspire the thought that "We need to get you out of here." 45 | 46 | ## IKEA is your friend 47 | 48 | Don't make furnishings a major line item 49 | -------------------------------------------------------------------------------- /notes/startups/README.md: -------------------------------------------------------------------------------- 1 | # README.md 2 | We'll use this section to capture notes as we're brainstorming about a certain topic — and potentially other spots throughout the development of the documentation. 3 | 4 | It's just one big parking lot. 5 | 6 | To prevent any confusion with versioning, any content from this section that has already moved downstream to the document, itself, will be captured in the /archive directory under each topic. 7 | 8 | NOTE: This may result in different iterations of the same concept appearing in multiple files over time. We will normalize this as the content moves downstream into the final documentation. 9 | -------------------------------------------------------------------------------- /notes/startups/startups-educating.md: -------------------------------------------------------------------------------- 1 | # Educating startups 2 | 3 | Startups will only internalize information when they are prepared to hear it. To put it another way, you could put the foremost expert in situation X in front of one of your startups. If the founder is currently dealing with situation Y, believes the company has already dealt with situation X, or is naive that situation X is something that even occurs, then pairing those two is a mistake. 4 | 5 | Startups only pay attention to the situation in which they find themselves at that very moment. It’s like a full kitchen at the height of dinner rush. Make sure nothing is burning. Taste the food before it goes out. Make sure customers are happy. It does absolutely no good to discuss flavor profiles with the chef when he or she is busy breaking down the protein to get it on the heat. 6 | 7 | Putting mentors in front of startups that are not ready to listen is a recipe for complete failure. The founder will not hear a thing. The mentor will be frustrated and potentially feel as if his or her time has been wasted. 8 | -------------------------------------------------------------------------------- /source/documents/1776-Innovation-that-Matters-2016.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/documents/1776-Innovation-that-Matters-2016.pdf -------------------------------------------------------------------------------- /source/documents/HOW-TO-SET-UP-A-SUCCESSFUL-UNIVERSITY-START-UP-INCUBATOR-RK2.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/documents/HOW-TO-SET-UP-A-SUCCESSFUL-UNIVERSITY-START-UP-INCUBATOR-RK2.pdf -------------------------------------------------------------------------------- /source/documents/ICIC_JPMC_Incubators_post.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/documents/ICIC_JPMC_Incubators_post.pdf -------------------------------------------------------------------------------- /source/documents/Mentor Protege 20140609.docx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/documents/Mentor Protege 20140609.docx -------------------------------------------------------------------------------- /source/documents/pie-Demo-Day-Run-of-Show.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/documents/pie-Demo-Day-Run-of-Show.xlsx -------------------------------------------------------------------------------- /source/documents/pie-offer-letter.doc: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/documents/pie-offer-letter.doc -------------------------------------------------------------------------------- /source/documents/pie-statement-of-capitalization.doc: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/documents/pie-statement-of-capitalization.doc -------------------------------------------------------------------------------- /source/documents/rfpOregonInc.docx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/documents/rfpOregonInc.docx -------------------------------------------------------------------------------- /source/images/2009-07-01 14.20.24.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2009-07-01 14.20.24.jpg -------------------------------------------------------------------------------- /source/images/2009-07-01 14.20.29.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2009-07-01 14.20.29.jpg -------------------------------------------------------------------------------- /source/images/2009-07-01 14.20.34.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2009-07-01 14.20.34.jpg -------------------------------------------------------------------------------- /source/images/2009-07-01 14.20.38.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2009-07-01 14.20.38.jpg -------------------------------------------------------------------------------- /source/images/2009-09-11 13.45.53.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2009-09-11 13.45.53.jpg -------------------------------------------------------------------------------- /source/images/2009-10-07 19.15.38.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2009-10-07 19.15.38.jpg -------------------------------------------------------------------------------- /source/images/2009-10-29 17.13.54.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2009-10-29 17.13.54.jpg -------------------------------------------------------------------------------- /source/images/2010-04-05 12.20.22.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2010-04-05 12.20.22.jpg -------------------------------------------------------------------------------- /source/images/2011-03-05 20.31.38.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2011-03-05 20.31.38.jpg -------------------------------------------------------------------------------- /source/images/2011-03-08 09.30.51.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2011-03-08 09.30.51.jpg -------------------------------------------------------------------------------- /source/images/2011-08-12 13.25.01 HDR.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2011-08-12 13.25.01 HDR.jpg -------------------------------------------------------------------------------- /source/images/2011-08-19 10.48.05 HDR.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2011-08-19 10.48.05 HDR.jpg -------------------------------------------------------------------------------- /source/images/2011-08-25 09.47.23.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2011-08-25 09.47.23.jpg -------------------------------------------------------------------------------- /source/images/2011-08-25 09.55.10.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2011-08-25 09.55.10.jpg -------------------------------------------------------------------------------- /source/images/2011-09-07 23.27.14.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2011-09-07 23.27.14.jpg -------------------------------------------------------------------------------- /source/images/2011-09-09 08.15.32.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2011-09-09 08.15.32.jpg -------------------------------------------------------------------------------- /source/images/2011-09-15 12.25.36.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2011-09-15 12.25.36.jpg -------------------------------------------------------------------------------- /source/images/2011-09-15 20.40.13.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2011-09-15 20.40.13.jpg -------------------------------------------------------------------------------- /source/images/2011-09-20 14.01.56.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2011-09-20 14.01.56.jpg -------------------------------------------------------------------------------- /source/images/2011-09-22 10.51.52.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2011-09-22 10.51.52.jpg -------------------------------------------------------------------------------- /source/images/2011-10-27 18.16.36.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2011-10-27 18.16.36.jpg -------------------------------------------------------------------------------- /source/images/2011-11-14 20.32.36.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2011-11-14 20.32.36.png -------------------------------------------------------------------------------- /source/images/2012-01-22 19.38.58.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2012-01-22 19.38.58.jpg -------------------------------------------------------------------------------- /source/images/2012-04-27 19.29.38.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2012-04-27 19.29.38.jpg -------------------------------------------------------------------------------- /source/images/2012-05-21 17.10.02.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2012-05-21 17.10.02.jpg -------------------------------------------------------------------------------- /source/images/2012-05-23 12.15.06.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2012-05-23 12.15.06.jpg -------------------------------------------------------------------------------- /source/images/2012-06-04 10.59.47.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2012-06-04 10.59.47.jpg -------------------------------------------------------------------------------- /source/images/2012-06-12 20.13.26.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2012-06-12 20.13.26.jpg -------------------------------------------------------------------------------- /source/images/2012-07-16 19.51.14.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2012-07-16 19.51.14.jpg -------------------------------------------------------------------------------- /source/images/2012-07-17 12.50.12.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2012-07-17 12.50.12.jpg -------------------------------------------------------------------------------- /source/images/2012-10-05 10.02.29.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2012-10-05 10.02.29.jpg -------------------------------------------------------------------------------- /source/images/2012-12-15 09.34.28.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2012-12-15 09.34.28.jpg -------------------------------------------------------------------------------- /source/images/2013-10-02 15.51.46-2.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2013-10-02 15.51.46-2.jpg -------------------------------------------------------------------------------- /source/images/2013-10-09 09.33.27-2.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2013-10-09 09.33.27-2.jpg -------------------------------------------------------------------------------- /source/images/2013-10-10 14.15.25-2.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2013-10-10 14.15.25-2.jpg -------------------------------------------------------------------------------- /source/images/2014-06-21 13.30.43.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2014-06-21 13.30.43.jpg -------------------------------------------------------------------------------- /source/images/2014-10-24 22.51.34-1.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2014-10-24 22.51.34-1.jpg -------------------------------------------------------------------------------- /source/images/2015-03-01 12.20.18.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2015-03-01 12.20.18.jpg -------------------------------------------------------------------------------- /source/images/2015-03-12 11.52.18.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2015-03-12 11.52.18.jpg -------------------------------------------------------------------------------- /source/images/2015-03-13 15.53.50.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2015-03-13 15.53.50.jpg -------------------------------------------------------------------------------- /source/images/2015-03-13-13.55.06.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2015-03-13-13.55.06.jpg -------------------------------------------------------------------------------- /source/images/2015-03-14 12.10.41.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2015-03-14 12.10.41.jpg -------------------------------------------------------------------------------- /source/images/2015-03-14 13.06.04.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2015-03-14 13.06.04.jpg -------------------------------------------------------------------------------- /source/images/2015-03-14 13.46.57.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2015-03-14 13.46.57.jpg -------------------------------------------------------------------------------- /source/images/2016-04-16 12.28.42-2.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/2016-04-16 12.28.42-2.jpg -------------------------------------------------------------------------------- /source/images/6105242576_fb52ed9c20_b.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/6105242576_fb52ed9c20_b.jpg -------------------------------------------------------------------------------- /source/images/OSB_010.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/OSB_010.jpg -------------------------------------------------------------------------------- /source/images/PIE-CENTRL-interior-2015.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/PIE-CENTRL-interior-2015.jpg -------------------------------------------------------------------------------- /source/images/PIE-Logo.zip: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/PIE-Logo.zip -------------------------------------------------------------------------------- /source/images/PIE-Nike-open-data-hack.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/PIE-Nike-open-data-hack.jpg -------------------------------------------------------------------------------- /source/images/PIE-Renny_Gleeson-cofounder.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/PIE-Renny_Gleeson-cofounder.jpg -------------------------------------------------------------------------------- /source/images/PIE-sketch-2009.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/PIE-sketch-2009.jpg -------------------------------------------------------------------------------- /source/images/all-the-feels.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/all-the-feels.jpg -------------------------------------------------------------------------------- /source/images/appthwack-founders-lab-1000.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/appthwack-founders-lab-1000.png -------------------------------------------------------------------------------- /source/images/flowchart-community-engagement.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/flowchart-community-engagement.jpg -------------------------------------------------------------------------------- /source/images/logo-portland-modern-manufacturing-collective.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/logo-portland-modern-manufacturing-collective.pdf -------------------------------------------------------------------------------- /source/images/osb-demo-day-2015.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/osb-demo-day-2015.jpg -------------------------------------------------------------------------------- /source/images/photo-repositories.md: -------------------------------------------------------------------------------- 1 | # Photo repositories 2 | Ugh. Please do a better job of documenting your accelerator than we have. 3 | 4 | * PIE Demo Day 2012 (Blueberry) https://www.flickr.com/photos/ahockley/albums/72157631824573700 5 | * PIE Demo Day 2013 (Coconut Creme) https://www.flickr.com/photos/ahockley/albums/72157636856907286 6 | * PIE Demo Day 2014 (Derby) https://www.flickr.com/photos/ahockley/albums/72157649086934251 7 | * Flickr search for PIE Demo Day https://www.flickr.com/search/?text=pie%20demo%20day -------------------------------------------------------------------------------- /source/images/pie-active-cropped.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/pie-active-cropped.jpg -------------------------------------------------------------------------------- /source/images/pie-alum-column.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/pie-alum-column.jpeg -------------------------------------------------------------------------------- /source/images/pie-clearing-out-cropped.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/pie-clearing-out-cropped.png -------------------------------------------------------------------------------- /source/images/pie-countdown-clock.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/pie-countdown-clock.jpg -------------------------------------------------------------------------------- /source/images/pie-demo-day-2013-bw.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/pie-demo-day-2013-bw.jpg -------------------------------------------------------------------------------- /source/images/pie-gowalla_400x400.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/pie-gowalla_400x400.png -------------------------------------------------------------------------------- /source/images/pie-highback-leather-chairs.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/pie-highback-leather-chairs.jpg -------------------------------------------------------------------------------- /source/images/pie-ikea-melltorp-table-white.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/pie-ikea-melltorp-table-white.JPG -------------------------------------------------------------------------------- /source/images/pie-kickstarter-hat-socks.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/pie-kickstarter-hat-socks.jpg -------------------------------------------------------------------------------- /source/images/pie-kitchen-table.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/pie-kitchen-table.jpg -------------------------------------------------------------------------------- /source/images/pie-light-switches-xolotl.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/pie-light-switches-xolotl.jpg -------------------------------------------------------------------------------- /source/images/pie-pie-gleeson.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/pie-pie-gleeson.jpg -------------------------------------------------------------------------------- /source/images/pieAcceleratorEmotionalRollerCoaster.001.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/pieAcceleratorEmotionalRollerCoaster.001.png -------------------------------------------------------------------------------- /source/images/pieAcceleratorEmotionalRollerCoasterMonth01Detail.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/pieAcceleratorEmotionalRollerCoasterMonth01Detail.png -------------------------------------------------------------------------------- /source/images/pieAcceleratorEmotionalRollerCoasterMonth02Detail.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/pieAcceleratorEmotionalRollerCoasterMonth02Detail.png -------------------------------------------------------------------------------- /source/images/pieAcceleratorEmotionalRollerCoasterMonth03Detail.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/pieAcceleratorEmotionalRollerCoasterMonth03Detail.png -------------------------------------------------------------------------------- /source/images/pieAcceleratorEmotionalRollerCoasterPreAccelerator-Detail.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/pieAcceleratorEmotionalRollerCoasterPreAccelerator-Detail.png -------------------------------------------------------------------------------- /source/images/pieAcceleratorEmotionalRollerCoasterPreAccelerator.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/pieAcceleratorEmotionalRollerCoasterPreAccelerator.png -------------------------------------------------------------------------------- /source/images/pieActiveSpace.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/pieActiveSpace.jpg -------------------------------------------------------------------------------- /source/images/pieEmptySpace.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/pieEmptySpace.jpg -------------------------------------------------------------------------------- /source/images/pieFrontDoor.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/pieFrontDoor.jpg -------------------------------------------------------------------------------- /source/images/pieKirstenRick.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/pieKirstenRick.jpg -------------------------------------------------------------------------------- /source/images/slideshow-full-00 copy.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/slideshow-full-00 copy.png -------------------------------------------------------------------------------- /source/images/slideshow-full-00.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/slideshow-full-00.png -------------------------------------------------------------------------------- /source/images/slideshow-full-01.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/slideshow-full-01.png -------------------------------------------------------------------------------- /source/images/slideshow-full-02.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/slideshow-full-02.png -------------------------------------------------------------------------------- /source/images/slideshow-full-03.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/slideshow-full-03.png -------------------------------------------------------------------------------- /source/images/slideshow-long-mentors-00.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/slideshow-long-mentors-00.png -------------------------------------------------------------------------------- /source/images/slideshow-long-space-01.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/slideshow-long-space-01.png -------------------------------------------------------------------------------- /source/images/slideshow-long-space-02.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/slideshow-long-space-02.png -------------------------------------------------------------------------------- /source/images/slideshow-long-space-03.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/slideshow-long-space-03.png -------------------------------------------------------------------------------- /source/images/slideshow-long-space-04.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/slideshow-long-space-04.png -------------------------------------------------------------------------------- /source/images/slideshow-long-startups-00.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/slideshow-long-startups-00.png -------------------------------------------------------------------------------- /source/images/supportland-demo-day-pie.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/supportland-demo-day-pie.jpg -------------------------------------------------------------------------------- /source/images/way-is-shut.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/images/way-is-shut.gif -------------------------------------------------------------------------------- /source/presentations/osbMeeting2015.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/piepdx/pie-cookbook/c3c1e5e514ddbc2b227acd6ffa23621f72f215f7/source/presentations/osbMeeting2015.pdf -------------------------------------------------------------------------------- /source/reference.md: -------------------------------------------------------------------------------- 1 | # Reference 2 | 3 | Providing a parking lot to capture resources that may inform the content of the PIE Cookbook. 4 | 5 | ## Overall 6 | 7 | - http://www.startuprev.com/ 8 | - http://paulgraham.com/articles.html 9 | - http://firstround.com/review/ 10 | - http://archive.learntoduck.net/ 11 | - http://blog.samaltman.com/ 12 | 13 | 14 | ## Accelerators 15 | 16 | - https://www.quora.com/What-are-the-challenges-of-running-a-startup-accelerator 17 | - https://medium.com/startups-venture-capital/improving-startup-accelerators-ae89673d4bbf#.cyuam4hwx 18 | - http://www.ianhathaway.org/blog/2016/3/1/startup-accelerators 19 | - http://www.boardofinnovation.com/2015/10/01/a-checklist-for-designing-your-own-innovation-accelerator/ 20 | - http://archive.learntoduck.net/techstars/why-an-accelerator/ 21 | - https://medium.com/@shockwaveinnov/is-a-startup-accelerator-right-for-you-f3ed3d61fecd#.bxraqt84b 22 | - https://c.ymcdn.com/sites/ande.site-ym.com/resource/resmgr/GALI/GALI_Report_032816.pdf 23 | - https://www.techinasia.com/talk/90-articles-applying-500-startups-accelerator 24 | - http://hackaday.com/2016/04/18/how-to-know-when-an-accelerator-is-not-right-for-your-startup/ 25 | 26 | ## Startup communities 27 | 28 | - “A city has to tolerate strangeness to be a home for startups, because startups are so strange. And you can't choose to allow just the forms of strangeness that will turn into big startups, because they're all intermingled. You have to tolerate all strangeness.” http://paulgraham.com/pgh.html 29 | - https://medium.com/@crystalrose/how-to-make-a-startup-communicorn-7c8a517490d8#.nha0ag4f7 (via James Leaverton) 30 | - http://www.geekwire.com/2016/12-things-seattle-can-teach-others-jobs-economic-development-building-better-city/ 31 | 32 | ## Mentors 33 | 34 | - http://davidgcohen.com/2011/08/28/the-mentor-manifesto/ 35 | 36 | ## Investors 37 | 38 | - https://medium.com/@schlaf/a-bunch-of-vcs-went-on-a-retreat-here-s-what-happened-145ede63eb12#.d4fscdu7l 39 | 40 | ## Startup metrics 41 | 42 | - http://a16z.com/2015/08/21/16-metrics/ 43 | - https://chartmogul.attach.io/NkqgtF8H 44 | - http://rahimtula.com/2015/08/01/fundraise-like-a-pro-using-this-internal-saas-metrics-playbook-2/ 45 | -------------------------------------------------------------------------------- /source/videos/video-repositories.md: -------------------------------------------------------------------------------- 1 | # Video repositories 2 | 3 | * PIE Demo Day 2012 (Apple) 4 | * Athletepath https://www.youtube.com/watch?v=iTYJNoR0SHk 5 | * DailyPath https://www.youtube.com/watch?v=HWrRfY-807o 6 | * MoPix https://www.youtube.com/watch?v=vH8j2K6znLQ 7 | * Revisu https://www.youtube.com/watch?v=swzr1fEWCcI 8 | * Spotsi https://www.youtube.com/watch?v=x2d3QEhju6I 9 | * VendScreen https://www.youtube.com/watch?v=CY9q8cQTqz0 10 | * PIE Demo Day 2012 (Blueberry) 11 | * AppThwack https://www.youtube.com/watch?v=HjqAqiW6hXs 12 | * Code Scouts https://www.youtube.com/watch?v=GHUwNUdFIDE 13 | * KS12 https://www.youtube.com/watch?v=e_t6bexU32Q 14 | * Little Bird https://www.youtube.com/watch?v=Bay2_--aQmw 15 | * Lytics https://www.youtube.com/watch?v=ywEM9rle7i0 16 | * Stublisher https://www.youtube.com/watch?v=-U7eJRAZ6a8 17 | * KS12 Early Stage 18 | * Trailer https://vimeo.com/54531470 19 | * Feature https://vimeo.com/53687541 20 | * Interviews 21 | * Andy Baio https://vimeo.com/50458351 22 | * Amber Case https://vimeo.com/50405411 23 | * David Embree https://vimeo.com/50385334 24 | * Brad Feld https://vimeo.com/51099767 25 | * Renny Gleeson https://vimeo.com/50452837 26 | * John Jay https://vimeo.com/50417946 27 | * Robin Jones https://vimeo.com/50385668 28 | * Michael Richardson https://vimeo.com/51158028 29 | * Barb Stark https://vimeo.com/50384970 30 | * Dave Yewman https://vimeo.com/50497400 31 | * PIE Demo Day 2013 (Coconut Creme) 32 | * Cloneless https://www.youtube.com/watch?v=ky27o3PTGiU 33 | * Fleck https://www.youtube.com/watch?v=xXCCEiKB39k 34 | * Orchestrate https://www.youtube.com/watch?v=6YHXaDopgMs 35 | * Smart Mocha https://www.youtube.com/watch?v=fHMpWX9asXY 36 | * Stand In https://www.youtube.com/watch?v=0GeScs3sa4o 37 | * Switchboard https://www.youtube.com/watch?v=fzCppmYIvSI 38 | * Teak https://www.youtube.com/watch?v=TIxYigzHzoo 39 | * PIE Demo Day 2014 (Derby) 40 | * Droplr https://www.youtube.com/watch?v=dqjnEgSRCC4 41 | * Krumplr https://www.youtube.com/watch?v=Ch0qv1JQcjk 42 | * Nutmeg https://www.youtube.com/watch?v=erC8h8nzegw 43 | * Outdoor Project https://www.youtube.com/watch?v=x1_yiowXHUs 44 | * Read the Docs https://www.youtube.com/watch?v=U6ueKExLzSY 45 | * ShopTender https://www.youtube.com/watch?v=wgOG0MxmyDg 46 | * Supportland https://www.youtube.com/watch?v=yGRHmAi3aSA 47 | * World State https://www.youtube.com/watch?v=9ugFy0_iioY 48 | * Experiments https://www.youtube.com/watch?v=eCySGB6y8zc --------------------------------------------------------------------------------