<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Angela Tran Kingyens on Medium]]></title>
        <description><![CDATA[Stories by Angela Tran Kingyens on Medium]]></description>
        <link>https://medium.com/@ATKingyens?source=rss-1d6ecf706047------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*DDfYAMTqY1nZPEc1.jpeg</url>
            <title>Stories by Angela Tran Kingyens on Medium</title>
            <link>https://medium.com/@ATKingyens?source=rss-1d6ecf706047------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 09:42:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ATKingyens/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Entrepreneurial ecosystems: Reflections on Toronto and Silicon Valley]]></title>
            <link>https://medium.com/versiononevc/entrepreneurial-ecosystems-reflections-on-toronto-and-silicon-valley-987c8c613335?source=rss-1d6ecf706047------2</link>
            <guid isPermaLink="false">https://medium.com/p/987c8c613335</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[startup-ecosystem]]></category>
            <category><![CDATA[harmony]]></category>
            <category><![CDATA[diversity]]></category>
            <dc:creator><![CDATA[Angela Tran Kingyens]]></dc:creator>
            <pubDate>Wed, 31 May 2017 18:58:22 GMT</pubDate>
            <atom:updated>2017-06-02T16:07:36.160Z</atom:updated>
            <content:encoded><![CDATA[<p>On May 26th, I attended the <a href="https://www.c2montreal.com/">C2 conference</a> in Montreal, joining my good friend Harley Finkelstein (Shopify), along with Magaly Charbonneau (Password Box), Wesley Chan (Felicis) and Eric Boyko (Stingray) on a panel. The theme was: “Entrepreneurial ecosystem: it takes a village to build a startup”.</p><p>Harley asked about my experiences growing up in Toronto and moving to Silicon Valley, specifically what my thoughts are on the differences between the two communities.</p><p>It’s an interesting question and one that I’m asked quite often. In fact, I touched upon the subject in a reflection I wrote last year on “<a href="http://versionone.vc/thoughts-outside-sf/#ixzz4iPOul2cg">Building startups and collective ambition outside Silicon Valley</a>”. When discussing regional and cultural differences, it’s hard to not overgeneralize, but here’s what I shared during the panel.</p><p><strong>Culture, harmony and outliers</strong></p><p>Canadians tend to be harmonious and neutral. We apologize for everything. We aren’t extreme and aim to get along. This is quite different from the US where things seem more polarized. While living in Silicon Valley (which has a more capitalistic culture), I’ve had the privilege to meet some the smartest, most brilliant, most ambitious, and generous people. But there’s also a huge disparity in wealth, education, etc. There are countless people on the other end of the spectrum who have not had the same opportunities, feel disenfranchised and are a stark contrast to the American Dream.</p><p>So what do these culture differences mean for entrepreneurship when winners are usually outliers? It doesn’t pay to be average or play it safe.</p><p>I believe that there are opportunities for both ecosystems to improve, albeit in very different ways. For Canadians, we need to be bold and think on a bigger stage. For SV, we need to think about how we can build and use technology to democratize knowledge, improve access to healthcare for all, and create a fairer distribution of wealth.</p><p><strong>Culture and diversity</strong></p><p>For Toronto (and most of Canada), diversity is our nation’s identity and pride. It is the quality that unites us. It is a great strength that introduces us to different perspectives and experiences, while teaching us tolerance and inclusion. On the other hand, SV is quite homogenous when it comes to diversity of thought (i.e. there’s a lot of “groupthink” with everyone being in tech). As a result, here, diversity is a way that individuals can stand out from the crowd.</p><p>For an analogy on how the two nations embrace diversity: just think about their birthdays. The differences are quite clear: Canada Day celebrates confederation, and July 4th celebrates Independence Day.</p><p>What are the implications for entrepreneurship? We already know that diverse companies and teams perform better and the recent events have put tremendous pressure on Silicon Valley (and all of us, for that matter) to be more aware and purposeful around the cause. On the flip side, Canadians should be more aggressive in embracing this advantage to gain some ground!</p><p>As you can see, these are very general observations made during a panel discussion. I’m deeply entrenched in both ecosystems. It’s not my place to say that one is better than the other, especially when I truly love both. But by appreciating the differences, we can learn and grow each ecosystem to cultivate more success for all.</p><p><em>Originally published at </em><a href="http://versionone.vc/toronto-sv/"><em>versionone.vc</em></a><em> on May 31, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=987c8c613335" width="1" height="1" alt=""><hr><p><a href="https://medium.com/versiononevc/entrepreneurial-ecosystems-reflections-on-toronto-and-silicon-valley-987c8c613335">Entrepreneurial ecosystems: Reflections on Toronto and Silicon Valley</a> was originally published in <a href="https://medium.com/versiononevc">VersionOneVC</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s our NPS as investors?]]></title>
            <link>https://medium.com/versiononevc/whats-our-nps-as-investors-da3b26c404c?source=rss-1d6ecf706047------2</link>
            <guid isPermaLink="false">https://medium.com/p/da3b26c404c</guid>
            <category><![CDATA[nps]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[midas-list]]></category>
            <category><![CDATA[investors]]></category>
            <dc:creator><![CDATA[Angela Tran Kingyens]]></dc:creator>
            <pubDate>Thu, 11 May 2017 16:56:33 GMT</pubDate>
            <atom:updated>2017-06-02T16:09:15.371Z</atom:updated>
            <content:encoded><![CDATA[<p>A few weeks ago, Forbes released their annual <a href="https://www.forbes.com/midas/list/#tab:overall">Midas List of Top Tech Investors</a>, recognizing those investors who have backed unicorns and seen strong returns for their funds. For these investors, their success is partly due to the fact that they are good pickers and can see opportunities like Uber and Airbnb. But there’s more to it than that. Great investors are at the right place at the right time by being thought leaders and generally solid and helpful individuals.</p><p>This idea is a strong inspiration for me, as Boris and I are continually striving to be better investors and people.</p><p>Over a year ago, we started sending a post-pitch survey to founders to get their anonymous feedback on how we can be better investors. We send this survey to any founder we’ve interacted with — not just those we end up investing in. As a small firm, we only make six to eight investments a year, meaning we have to pass on many opportunities — but we still respect these founders and try to help in other ways where we can.</p><p>The core question in the survey is <strong><em>How likely is it that you would recommend Version One to a friend or colleague?</em></strong> If you’re an entrepreneur, you’re more than familiar with this kind of question and the Net Promoter Score (NPS). Just as companies do with their customers, it is imperative that we understand what our NPS is with <em>our</em> customers: founders.</p><p>When we breakdown our NPS by information we get from other survey questions, it is no surprise that it is better when 1) we are quicker in our decision-making process; 2) we clearly communicate our thesis; and 3) we provide helpful feedback.</p><p>We’re going to shed some light on these three aspects of the survey and share what we’ve learned about ourselves as entrepreneurs, as well as some best practices and areas where we continue to improve.</p><p><strong>1)</strong> <strong>How did you find the efficiency of our process? How responsive were we?</strong></p><p>Our average turnaround time to get back to an entrepreneur is 2–3 days. It’s about a week if we dig deeper into an opportunity. We’re lucky that we have a small partnership that allows for fast decision making. And while we can’t always be as quick as we’d like, we always do get back to a founder. We know that a founder’s time is more precious than our own.</p><p>Not surprisingly, we’ve learned that what contributes to a higher NPS is if we both spend time with an entrepreneur — probably because s/he finds that we are able to be more thorough in due diligence. However, given our schedules and size of the firm, this is not always practical. So at the very least, we try our best to hear/see every pitch from a fresh lens. We once got feedback that we had too many preconceived notions and never gave a founder a fair chance — we took that feedback to heart!</p><p>Internally, we discuss every deal that we see and make sure that we talk about both sides of the decision: why the company is not a fit for us, as well as what we like about it and what the possibilities could be if it were a fit.</p><p><strong>2)</strong> <strong>Were we clear in our communication about our investment thesis?</strong></p><p>There is a lot of debate among VCs about whether it is important to have an investment thesis. On one hand, some believe that being thesis-driven can make one less opportunistic and there’s a greater chance of missing something new. On the flip side, having a thesis on the fund level provides a north star to align to. We’ve found that an investment thesis helps us focus our time. More critically, it enables us to effectively communicate our beliefs and who we are to our LPs and entrepreneurs.</p><p>Based on our survey data, the strongest contributor to positive NPS is our ability to communicate <a href="http://versionone.vc/our-refocused-investment-thesis/">our thesis</a>: we like to invest in businesses with potentially large network effects built around people and/or data.</p><p><strong>3)</strong> <strong>Did we provide helpful feedback on your business?</strong></p><p>Survey results show that our NPS is highest when we provide good feedback. This is arguably the hardest thing to do because it sucks to say “no” and we can’t say “yes” to everything. As investors, it’s also hard to have an expert opinion or strong conviction, having spent far less time on a category or space than the founder who has most likely dedicated years of his/her life to the matter.</p><p>One great tip that an entrepreneur gave us is that VCs should give feedback in three parts: 1) what we like about the opportunity; 2) what we don’t necessarily believe in about the deal and 3) what we’re not sure about (and will do more research on).</p><p>VC is a long-term game but there are certainly ways in which we can improve ourselves in the short-term. There are also so many other facets to being a great VC than the initial founder interactions. For instance, in those cases where we have the privilege of joining your journey, we strive to be the first people you come to. But for now, I decided to start with the top of the funnel because none of the above is tied to an investor’s experience, but to his/her operating and investment philosophy.</p><p><em>Originally published at </em><a href="http://versionone.vc/whats-nps-investors/"><em>versionone.vc</em></a><em> on May 11, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da3b26c404c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/versiononevc/whats-our-nps-as-investors-da3b26c404c">What’s our NPS as investors?</a> was originally published in <a href="https://medium.com/versiononevc">VersionOneVC</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bringing Transparency to Startup Data: Our Data Repository Project]]></title>
            <link>https://medium.com/versiononevc/bringing-transparency-to-startup-data-our-data-repository-project-318706246290?source=rss-1d6ecf706047------2</link>
            <guid isPermaLink="false">https://medium.com/p/318706246290</guid>
            <category><![CDATA[data-transparency]]></category>
            <category><![CDATA[data-startup]]></category>
            <dc:creator><![CDATA[Angela Tran Kingyens]]></dc:creator>
            <pubDate>Wed, 29 Mar 2017 13:00:13 GMT</pubDate>
            <atom:updated>2017-06-02T16:13:21.901Z</atom:updated>
            <content:encoded><![CDATA[<p>Two months ago, I first introduced my vision to <a href="http://versionone.vc/next-chapter-vc/">create a startup data repository</a>. Since then, I’ve chatted with many of you who share the desire to democratize access to information on startups and bring transparency to what’s been a traditionally private ecosystem.</p><p>I’ve been blown away by the response and appreciate every like, share, tweet, retweet, email, call, and coffee meeting. I’m thrilled that I underestimated the level of interest in this topic.</p><p>I also underestimated how ambitious this goal truly is. Through all these conversations, I’ve come to realize that not everyone has the same needs and expectations for startup data. Some of you want high-level KPI data (i.e. how “fast” is a fast-growing marketplace in terms of GMV). Others are looking for baseline information on operational expenses (i.e. what is a “reasonable” cost for square foot of office space in SF).</p><p>Today, I am seeking to define the scope of this project and would love your feedback.</p><p><strong>Vision</strong>: A centralized hub of startup data</p><p><strong>Mission</strong>: To provide answers to those questions that founders/operators frequently ask their investors and peers, and to replace anecdotes with data-supported answers.</p><p><strong>Strategy</strong>: To crowdsource data, KPIs and benchmarks on anything from operations to sales to hiring.</p><p><strong>What data is available today?</strong></p><p>If we examine the current landscape of startup data, we can categorize it into two types: 1) financial statements and financing information; and 2) general/operations information (basically anything that’s not financial). And, we find privately held and publicly available information within each of these two categories.</p><p>The following figure breaks these categories into four quadrants: privately held financial, publicly available financial, privately held general and publicly available general.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*tA7F2hblMLchSz3ggVgDiQ.jpeg" /></figure><p><strong>1: Privately held financial</strong></p><ul><li>Founders and startups use SaaS (i.e. eShares, HockeyStick) in order to communicate their financial information to investors. In these cases, data is standardized to the SaaS’ requirements, but remains silo’ed within an organization. It’s worth noting that SaaS companies could probably do something interesting with all their data in aggregate.</li><li>Some VCs have data and engineering teams manually wrangle non-standard financial statements and KPIs from their portfolio and pitches and create an internal repository for their own use. This data stays silo’ed (and rightfully so, given how expensive and resource-intensive this task is)</li></ul><p><strong>2: Privately held operational</strong></p><ul><li>Some companies collect operational data as a part or side benefit of their main business. Examples are Hired, Comparably, Glassdoor and Stack Overflow for salaries and compensation. Some of these companies do share their aggregate findings, but never their raw data. This information is typically quite vertical — and even within a vertical, data isn’t standardized so there’s no way to reliably compare two data sets.</li></ul><p><strong>3: Publicly available financial</strong></p><ul><li>Companies (like <a href="https://mattermark.com/">Mattermark</a>, a V1 company) scrape the Internet, taking raw (and free) public information from social media, SEC filings and press releases and then repackaging that information into a usable database that typically requires a fee to access. Typical use cases are business development, sales, and investing.</li></ul><p><strong>4: Publicly available operational</strong></p><p><strong>The opportunity, what’s next and getting involved</strong></p><p>After evaluating the current landscape, it’s clear that the lowest hanging fruit is in collecting general/operational data (#4). Ideally, we’d love for the repository to also shed light on financial statements and financing rounds — and perhaps in time we’ll be able to do so as we build trust and can demonstrate the value.</p><p>But for now, we’ll begin by crowdsourcing information through a series of anonymous surveys.</p><p>Are there any topics you’d like to learn more about? What questions do you have around operating costs? Are you curious about best practices in data science? What are the areas where you need more data to complement the anecdotes from founders and investors? Please leave your thoughts in the comments below.</p><p>There is so much more that we can do, so feel free to ping me with your feedback and suggestions for this project in general. And, if you’re interested in helping with this project, we’d very much appreciate it (we are a small team of two, after all!).</p><p>Until then… stay tuned for the first survey soon!</p><p><em>Originally published at </em><a href="http://versionone.vc/startup-data-project/"><em>versionone.vc</em></a><em> on March 29, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=318706246290" width="1" height="1" alt=""><hr><p><a href="https://medium.com/versiononevc/bringing-transparency-to-startup-data-our-data-repository-project-318706246290">Bringing Transparency to Startup Data: Our Data Repository Project</a> was originally published in <a href="https://medium.com/versiononevc">VersionOneVC</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Do you need data engineering before data science?]]></title>
            <link>https://medium.com/versiononevc/do-you-need-data-engineering-before-data-science-7e199f8137c5?source=rss-1d6ecf706047------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e199f8137c5</guid>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[data-engineering]]></category>
            <dc:creator><![CDATA[Angela Tran Kingyens]]></dc:creator>
            <pubDate>Thu, 23 Mar 2017 15:40:15 GMT</pubDate>
            <atom:updated>2017-06-02T16:21:02.637Z</atom:updated>
            <content:encoded><![CDATA[<p>Last week, I shared some lessons learned from a <a href="http://versionone.vc/domino-data-takeaways/">Domino Data Science Pop-up</a> that I attended a month ago. There were some very important discussions surrounding the world of data science today. One thread explored the differences between data science and data engineering.</p><p>I’ll admit that I was completely unaware of the engineering behind data science when we first launched <a href="http://insightdatascience.com/">Insight Data Science</a> back in 2012. And I don’t believe that I was alone. We data scientists were too enamoured with the idea of having the <a href="https://hbr.org/2012/10/data-scientist-the-sexiest-job-of-the-21st-century">sexiest job of the 21st century</a>.</p><p>However, quietly under our radar, data engineering (our “slightly younger sibling”) was emerging, stretching its wings, and undergoing its own evolution. You can read <a href="https://medium.freecodecamp.com/the-rise-of-the-data-engineer-91be18f1e603#.m8bdjrwg3">about this from Maxime Beauchemin</a>, data engineer at Airbnb).</p><p>So, what is the difference between a data scientist and data engineer? Companies often overlap these positions but understanding the distinction is essential to building your team and hiring the right resources.</p><p>Since Insight added a <a href="https://blog.insightdatascience.com/data-science-vs-data-engineering-62da7678adaa#.nvbhw9yqc">Data Engineering Program</a> in recent years, we can compare it to the Data Science program to shed some light on these two important roles.</p><p><strong>Data Science</strong></p><p>The key responsibilities for a data scientist are:</p><ul><li>Asking the right questions on any given dataset</li><li>Being able to answer those questions — either through statistical analysis, machine learning, and/or data mining</li><li>Clearly and effectively communicating any results to interested parties (either verbally or in writing)</li></ul><p>Data scientists have a PhD because “it demonstrates that s/he has spent roughly 5 intense years in graduate training to either ask the right questions about data, performing data analysis, create statistical or mathematical models, and present results.”</p><p><strong>Data Engineering</strong></p><p>A good data engineer:</p><ul><li>Gathers data, stores it, does batch/real-time processing on it, and serves it via an API to a data scientist (some companies may call this data infrastructure or data architecture)</li><li>Has extensive knowledge on databases and best engineering practices</li></ul><p>Data engineers should have very strong software engineering skills. They need to be able to quickly learn to use any of the big data tools on the market, as well as be able to improve the available tools if needed.</p><p>With all that said, the easy way to look at the two roles: <em>data engineers enable data scientists to do their jobs more effectively.</em></p><p>So, for those of you looking to build out your data science team: before you hire your first data scientist, ask yourself, will he or she have the infrastructure to be successful? It just might be that you need to hire a data engineer first.</p><p><em>Originally published at </em><a href="http://versionone.vc/need-data-engineering-data-science/"><em>versionone.vc</em></a><em> on March 23, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e199f8137c5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/versiononevc/do-you-need-data-engineering-before-data-science-7e199f8137c5">Do you need data engineering before data science?</a> was originally published in <a href="https://medium.com/versiononevc">VersionOneVC</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Takeaways from the Domino Data Science Pop-up: Defining a data scientist]]></title>
            <link>https://medium.com/versiononevc/takeaways-from-the-domino-data-science-pop-up-defining-a-data-scientist-6dc085c929fe?source=rss-1d6ecf706047------2</link>
            <guid isPermaLink="false">https://medium.com/p/6dc085c929fe</guid>
            <category><![CDATA[data-science]]></category>
            <dc:creator><![CDATA[Angela Tran Kingyens]]></dc:creator>
            <pubDate>Wed, 15 Mar 2017 15:36:53 GMT</pubDate>
            <atom:updated>2017-06-02T16:24:17.076Z</atom:updated>
            <content:encoded><![CDATA[<p>Three weeks ago, I had the pleasure of attending the <a href="https://popup.dominodatalab.com/">Domino Data Science Pop-up</a>, which was one of the best days of talks on data science that I have attended. You can check out <a href="https://dominodatalab.wistia.com/projects/h34yaov6t8">recordings of the talks</a> as well as copies of the presentations <a href="https://www.slideshare.net/dominodatalab">on SlideShare</a>.</p><p>I won’t dive into all the nitty-gritty discussions on math and statistics, but I do want to share some insightful discussions surrounding the definition and role of data scientists in today’s startups.</p><p><strong>What’s a data scientist? It’s what we do, not who we are</strong></p><p>It’s always tricky to define trendy terms — and that’s certainly true about data science. Whipple Neely, Director of Data Science at EA, gave us a better way to define a data scientist: <em>it isn’t who we are but rather what we do.</em></p><p>This distinction is important for several reasons. First, it helps us better understand why and when we need data scientists (and what we can expect of them). And two, it sheds light on what we should be looking for when recruiting for data science. In the past, I have shared some insight on recruiting and <a href="http://versionone.vc/hiring-data-scientists/">hiring data scientists</a> from my time at Insight Data Science.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*7GAlMoAjHiH-8DDorQxIGA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*afqVXp_R1qM3uieWTt4UGg.jpeg" /><figcaption><a href="https://www.slideshare.net/dominodatalab/data-scientists-are-analysts-are-also-software-engineers"><em>Data Scientists Are Analysts are Also Software Engineers</em></a><em>, William Whipple Neely</em></figcaption></figure><p>It turns out that a data scientist is both analyst and software engineer (and everything in between) as Neely’s presentation was aptly titled “Data Scientists Are Analysts Are Also Software Engineers.” Building models is the least important part of the job. Data science isn’t just about optimization, but also <em>communication</em>. Taking a black box approach to data science makes it harder to explain the insights — and the findings can come off as less believable, especially when your company’s core business isn’t machine learning.</p><p><strong>Finding that data scientist unicorn</strong></p><p>How do we go about finding these elusive people who are technical builders with deep mathematical knowledge, who are both product and sales-driven, and who think like a CEO with an understanding of internal and external stakeholders?</p><p>As Kimberly Shenk, Director of Data Science Solutions at Domino Data Labs, explained: “It’s hard ‘to do all and be all things’.” Therefore, she suggests the following strategy when hiring and developing the team:</p><ul><li>First, think about which area people on your team naturally gravitate to: are they sales pitchers (i.e. good at convincing people in the organization about what work brings value), problem interpreters (good at deciphering what the problem really is), mini-strategists / CEOs (good at prioritizing what will drive the business forward), data engineering socialites (good at mobilizing others to implement your work)?</li><li>Then, start by hiring individuals who are strong in a few of these categories and continue to build out their expertise, while developing other skills over time (if they are so interested and inclined). It’s all about “divide and conquer,” so make sure you don’t hire the same kind of individuals who all have the same subset of skills. Every addition to the team should be synergistic.</li></ul><p>You might be wondering if it is better to hire someone who is stronger technically or business-wise? It really depends on your needs and company, as you can certainly learn technical/math skills just like you can pick up business skills. Ultimately, the consensus of the crowd was that good intuition (specifically a scientific thinking process) is important. And, curiosity is the most critical attribute that can’t be taught.</p><p>On a side note, I would love to talk to anyone who has a “curriculum” or process for fostering and cultivating data science talent? Ping me and we can compare notes.</p><p><strong>Where does data science fit in an organization?</strong></p><p>Another great discussion focused on how to structure a data science team within your company. Is a centralized or decentralized approach better? To summarize the two:</p><ul><li><strong>Centralized</strong>: individuals are on a data science team, working with product teams on a per-project basis (almost like “consultants”)</li><li><strong>Decentralized</strong>: individuals are on different product/engineering teams</li></ul><p>As with anything, there’s always a tradeoff. A centralized approach creates distance between team and product, while a decentralized approach creates a risk of redundant work.</p><p>The consensus from the group is that most companies start with data science embedded with the product team, as there’s a natural fit there. Then, as the organization grows, it needs to find ways to implement a hub-and-spoke model. For more thoughts on this, you can read my friend Clare Corthell’s <a href="https://medium.com/@clarecorthell/where-successful-data-scientists-sit-815a49319b79#.8teunpx3t">blog post</a>.</p><p><strong>Best practices in data science and engineering</strong></p><p>Last month, I wrote about my mission to create a <a href="http://versionone.vc/next-chapter-vc/">crowdsourced repository</a> for startup data — stay tuned for more on this next week.</p><p>One of the key questions I want to answer is: what are the best practices when it comes to data science and engineering. Ironically, many of the decisions made on infrastructure and analysis are made through anecdotes, i.e. asking other data scientists and engineers questions like “what do you use?” and “do you build your own tools?”.</p><p>Of course, it’s not enough to consider each database, computing platform, etc. separately because everything is intertwined (as an example, just look at data at Atlassian!).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*xYGTfwrk7A-RvlIRwbdLuw.png" /></figure><p>But if it is possible for us to bring some data forward on the data pipeline to complement qualitative anecdotes we get from friends, I have no doubt that that would be valuable. So if you’re interested in working on this with me, please ping me and stay tuned!</p><p><em>Originally published at </em><a href="http://versionone.vc/domino-data-takeaways/"><em>versionone.vc</em></a><em> on March 15, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6dc085c929fe" width="1" height="1" alt=""><hr><p><a href="https://medium.com/versiononevc/takeaways-from-the-domino-data-science-pop-up-defining-a-data-scientist-6dc085c929fe">Takeaways from the Domino Data Science Pop-up: Defining a data scientist</a> was originally published in <a href="https://medium.com/versiononevc">VersionOneVC</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“Understanding Social Platforms,” now summarized in a presentation deck]]></title>
            <link>https://medium.com/versiononevc/understanding-social-platforms-now-summarized-in-a-presentation-deck-5b5aad5378c7?source=rss-1d6ecf706047------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b5aad5378c7</guid>
            <category><![CDATA[social-network]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[network-effect]]></category>
            <category><![CDATA[social-platforms]]></category>
            <dc:creator><![CDATA[Angela Tran Kingyens]]></dc:creator>
            <pubDate>Wed, 22 Feb 2017 14:00:30 GMT</pubDate>
            <atom:updated>2017-06-02T16:26:32.101Z</atom:updated>
            <content:encoded><![CDATA[<p>Two months ago, we published our second eBook, <a href="http://versionone.vc/social-handbook/">Understanding Social Platforms</a>. In it, we discuss the dynamics of each social platform type: messaging, private networks, public networks, enterprise networks, and communities. We also cover important topics for social platform businesses like metrics, exits, valuations, and our outlook for future opportunities in social.</p><p>Today, we are happy to announce that this eBook is now available in slide deck form for a faster read or quick refresher for the over 2,500 of you who have already picked this up!</p><p>You can download the slide deck <a href="https://www.slideshare.net/AngelaTranKingyens/understanding-social-platforms-by-version-one-ventures">here</a>. And if you’re interested in the full version of the book, it’s available as a <a href="http://versionone.vc/wp-content/uploads/2016/12/Understanding-Social-Platforms-Dec2016.pdf">PDF</a> or <a href="https://www.dropbox.com/s/ce3ipr135mnuhhj/Understanding%20Social%20Platforms-Dec-2016.epub?dl=0">ePub</a>.</p><p><em>Originally published at </em><a href="http://versionone.vc/social-platforms-deck/"><em>versionone.vc</em></a><em> on February 22, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b5aad5378c7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/versiononevc/understanding-social-platforms-now-summarized-in-a-presentation-deck-5b5aad5378c7">“Understanding Social Platforms,” now summarized in a presentation deck</a> was originally published in <a href="https://medium.com/versiononevc">VersionOneVC</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My next chapter of VC: More data!]]></title>
            <link>https://medium.com/versiononevc/my-next-chapter-of-vc-more-data-b941810f5bcc?source=rss-1d6ecf706047------2</link>
            <guid isPermaLink="false">https://medium.com/p/b941810f5bcc</guid>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[network-effect]]></category>
            <category><![CDATA[venture-capital]]></category>
            <dc:creator><![CDATA[Angela Tran Kingyens]]></dc:creator>
            <pubDate>Tue, 07 Feb 2017 16:57:22 GMT</pubDate>
            <atom:updated>2017-02-07T17:13:31.378Z</atom:updated>
            <content:encoded><![CDATA[<p>On the heels of being named principal last week, I am humbled by <a href="http://versionone.vc/congratulations-angela-tran-kingyens-newest-principal/">Boris’s announcement</a> and thrilled to begin leading deals for Version One. While many of you have already worked with me directly or read my thoughts on this blog over the years, I want to take the opportunity to share my vision: what I’m working on, where I can be the most helpful, and where I’d like to go from here.</p><p>Those of you who already know me understand that I’m quite data-driven. My love for data isn’t too surprising given my background and in my “next chapter” of VC, I plan to double down on data projects, including:</p><p><strong>Building a stronger community around data science and learning</strong></p><p>Through my work with <a href="http://insightdatascience.com/">Insight</a>, I’ve been fortunate to connect with incredible data scientists and data-driven entrepreneurs. I’m looking forward to cultivating stronger relationships with data experts and thought leaders who can help Version One and our portfolio companies with building products, hiring, and more. Stay tuned for most posts on these topics in the coming year.</p><p>I’m also passionate about leadership development and am excited about connecting with those who are working on building and promoting a culture of learning, leadership, and inclusivity.</p><p><strong>Creating a repository for startup data</strong></p><p>Companies collect so much data but it’s usually silo’ed. By compiling and leveraging this data, we can help founders better understand the dynamics of their business to grow and scale accordingly. In addition, data can help us as investors better evaluate investment opportunities. This is particularly important in early stages when evaluations are certainly much less objective.</p><p>Over the years, we have blogged about ways that startups can structure their data — such as our metrics templates for <a href="http://versionone.vc/marketplace-kpi/">marketplaces</a> and <a href="http://versionone.vc/social-platforms-metrics-1/">social platforms</a>. These are good starting points, but the data is still silo’ed so comparisons and benchmarking across companies are still done intuitively. We’ve also shared <a href="http://versionone.vc/marketplace-fundraising/">frameworks and benchmarks</a>, but these have been more anecdotal than backed by data.</p><p>It may be an incredibly ambitious goal, but I’d like to centralize data to become the go-to fund for advice on KPIs and benchmarks on anything from operations to sales and hiring. Of course, we don’t have the same scale as large VCs where whole teams are tasked with building out these platforms. However, I’m looking forward to crowdsourcing some of the work and collaborating with others to shed more light on startup data.</p><p><strong>Pushing my own knowledge on AI/ML</strong></p><p>From my work in my PhD, I’ve built a solid foundation when it comes to statistics and data mining. However, it’s been some time since I’ve needed to exercise my technical brain for complex machine learning and AI. I’m hoping to carve out some time in the day to code/hack so I can make an even bigger impact.</p><p>Stay tuned for updates on our blog and <a href="https://twitter.com/ATKingyens">follow me on Twitter</a> for my plans on how this will all come to fruition!</p><p>Generally speaking, when it comes to investment themes, we at Version One are quite agnostic and instead are <a href="http://versionone.vc/our-refocused-investment-thesis/">thesis-driven around network effects</a>. As such, I’ve personally spent a lot of time on <a href="http://versionone.vc/marketplace-handbook/">marketplaces</a>,<a href="http://versionone.vc/social-handbook/"> social platforms</a> (i.e. messaging, networks, communities) and <a href="http://versionone.vc/healthcare-update/">healthcare</a>. I’m still excited about these categories, but as I <a href="http://versionone.vc/2016-review/">recently wrote</a>, we’re learning more about <a href="http://versionone.vc/cryptocurrencys-second-act-rise-ethereum-whats-store-2017/">Blockchain</a>, genomics, and other emerging technologies (AR, VR, robotics, etc.).</p><p>On a personal note, I am passionate about the democratization of knowledge, increased accessibility to healthcare, distribution of our wealth, and inclusion of the diverse. I am the daughter of a refugee (of Canada) and now an immigrant of the US. My family and I are forever grateful for the openness and generosity of others as we wouldn’t be where we are today without them. Given the current state of affairs which challenge everyone’s basic rights, it seems that investing in companies with these same values is more critical than ever.</p><p>If any of the above resonates with you, whether it’s on data, network effects, democratization, etc., please reach out to me. It doesn’t matter if you’re an entrepreneur, engineer, growth hacker, data scientist, student, professor or fellow investor… I’d love to learn from and work with you.</p><p>Finally and most importantly, thanks to our entire community — investor friends, entrepreneurs, our founders and LPs — who reached out with congratulatory wishes and continue to bring out the best in me. And of course, a special shout out to Boris for this incredible opportunity to build Version One together.</p><p>-ange 🙂</p><p><em>Originally published at </em><a href="http://versionone.vc/next-chapter-vc/"><em>versionone.vc</em></a><em> on February 7, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b941810f5bcc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/versiononevc/my-next-chapter-of-vc-more-data-b941810f5bcc">My next chapter of VC: More data!</a> was originally published in <a href="https://medium.com/versiononevc">VersionOneVC</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Revisiting the Engagement Pyramid]]></title>
            <link>https://medium.com/versiononevc/revisiting-the-engagement-pyramid-e7d562cdbbe0?source=rss-1d6ecf706047------2</link>
            <guid isPermaLink="false">https://medium.com/p/e7d562cdbbe0</guid>
            <category><![CDATA[engagement]]></category>
            <category><![CDATA[metrics]]></category>
            <category><![CDATA[social-network]]></category>
            <dc:creator><![CDATA[Angela Tran Kingyens]]></dc:creator>
            <pubDate>Tue, 24 Jan 2017 14:00:20 GMT</pubDate>
            <atom:updated>2017-02-07T17:11:55.576Z</atom:updated>
            <content:encoded><![CDATA[<p>Back in 2014, I blogged about building a <a href="http://versionone.vc/engagement-pyramid/">user engagement pyramid</a> for social platforms, inspired by Fred Wilson’s <a href="http://avc.com/2011/06/dont-forget-your-logged-out-users/">100/10/1 rule</a>.</p><p>The premise of that post was simple: since user-generated content is king, the top of the pyramid (aka the most engaged users) are those who post status updates, photos and links. And, these creators are inspired when they are recognized for their contributions via shares, comments, and favourites. As such, the user engagement pyramid should look something like below and the goal of social networks is to move users up the pyramid.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/277/1*9tTtKXaEFGH-sOYNjtFh3Q.jpeg" /></figure><p>In that original post, I offered two non-mathematical steps for creating an engagement pyramid:</p><ol><li>At the top, place the activity that you determine to be a sign of someone who is most engaged with your product (this is usually the factor that drives your most important metrics).</li><li>Next, rank the activities in decreasing order based on level of friction (from hardest to easiest).</li></ol><p>A few months ago, one of our founders reflected on this advice, “Conceptually, this is all good but is there a ‘scientific’ method of building this hierarchy of engagement?” As a lover of all things data, these comments inspired me to revisit the post and see if I could add a more solid mathematical framework to the pyramid.</p><p>Upon further reflection, I think the first point about placing your most engaged activity up top is still valid. However, for point 2, I think that friction (as measured by how hard/easy an activity is) may not be the most important factor for determining engagement. Here’s why:</p><p><strong>Individual vs. Systematic Engagement</strong></p><p>Let’s consider the following: is the user who logs on everyday and simply lurks more or less engaged than the user who only logs in once that month but posts content?</p><p>On a purely DAU/MAU basis, the former is more engaged than the latter. However, there is a difference between the individual’s engagement and “systematic” engagement (how the individual’s actions influence all other actions of the platform). The pyramid above represents the latter because posting content, in theory, will attract more people to the platform than just lurking or liking. In other words, posting has higher systematic engagement than logging in.</p><p>It’s a nuanced distinction, but important to understand.</p><p><strong>Can we create an index for engagement?</strong></p><p>If we revisit point #1, there’s some low-hanging fruit to help us figure out individual engagement:</p><ul><li>Of those users with the highest DAU/MAU, what are actions are they doing?</li><li>On the flip side, of those users who post or comment frequently, what is their DAU/MAU?</li></ul><p>These two exercises should inform what the systematic engagement pyramid looks like. Most likely, you already have a strong intuition of what action should be on top and this exercise is just a matter of testing your hypothesis.</p><p>Here’s an example. Let’s say you believe that posting an image engages the most users. How do you test this to be true? You’ll need to take a step back and define the influence or reach of a given action.</p><p>In this case, the engagement “index” of an image can be computed as:</p><p><strong><em># of likes + # of comments + # of shares + # of views</em></strong></p><p>Likewise, the engagement index of a comment is:</p><p><strong><em># likes + # of views</em></strong></p><p>Simply put, think of the pyramid as ranking the potential reach of all users. Every step down the pyramid has a smaller reach. Based on the above, the reach of an image is greater than the reach of a comment. You can assign value to every possible user action (posting a status update, sharing a link, etc.) and then rank the actions according to total potential value.</p><p>Keep in mind, that your index will be more complex, as I made a lot of assumptions on linearity for simplicity’s sake.</p><p><strong>Key takeaways</strong></p><p>What can we take away from all this? First, systematic and individual engagement are two different things: systematic engagement is a function of all individual engagement combined. It’s important to understand this distinction when building your engagement pyramid. Second, for as much as we try to quantify engagement, this process is still very much more art than science.</p><p>And please, keep the comments coming. Each discussion further refines the model and helps us all.</p><p><em>Originally published at </em><a href="http://versionone.vc/engagement-v2/"><em>versionone.vc</em></a><em> on January 24, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7d562cdbbe0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/versiononevc/revisiting-the-engagement-pyramid-e7d562cdbbe0">Revisiting the Engagement Pyramid</a> was originally published in <a href="https://medium.com/versiononevc">VersionOneVC</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Year in Review: 2016]]></title>
            <link>https://medium.com/versiononevc/a-year-in-review-2016-740a62d91177?source=rss-1d6ecf706047------2</link>
            <guid isPermaLink="false">https://medium.com/p/740a62d91177</guid>
            <category><![CDATA[year-in-review]]></category>
            <category><![CDATA[2016]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[venture-capital]]></category>
            <dc:creator><![CDATA[Angela Tran Kingyens]]></dc:creator>
            <pubDate>Wed, 14 Dec 2016 14:00:22 GMT</pubDate>
            <atom:updated>2016-12-14T15:07:57.584Z</atom:updated>
            <content:encoded><![CDATA[<p>This has been an important year for us as a firm, as well as the market in general. We couldn’t begin any recap of 2016 without focusing on the bubble we hear so much about. The industry entered the year bracing for an apocalypse. Every announcement — whether it was a funding round, exit or layoffs — was analyzed within the context that the tech bubble has definitely burst or that we’re still in the bubble.</p><p>So, what really happened in 2016? There was a significant pull-back of the public markets in Q1. As <a href="http://tomtunguz.com/forward-multiples-mid-2016/">Tomasz Tunguz of Redpoint</a> showed, in February 2016, public SaaS companies had fallen <a href="http://tomtunguz.com/depression-in-saas/">57% from their highs</a>. Yet while they were trading at 3.3x forward revenue in February 2016 (the low), they appreciated by 6% each month for the following six months. As Tomasz points out, these public companies are now trading at 4.7x forward, which is relatively comparable to the median of 5.2x for the last two years.</p><p>In other words, any correction in public valuations happened quickly and has now stabilized.</p><p>But what kind of impact has this had on the private markets? The fundraising environment is certainly tougher for later rounds. From Series A and onwards, fundraising takes longer and valuations are typically below the expectations and benchmarks of 2015. At the same time, seed money is still abundant due to the proliferation of micro VC over the past few years. This can set up a perfect storm if early-stage companies don’t manage their expectations and reality properly.</p><p>Mattermark (a portfolio company) looked at the <a href="https://mattermark.com/startup-graduation-rate-surprisingly-low/">matriculation rates for a class of startups</a>. They started with a simple question: if 100 startups raise a Seed round, how many of those will go on to raise a Series A, and then a Series B?</p><p>Mattermark found that, on average, around 31 of the initial startups raised a Series A. From there, the number of startups that raise a Series B halves and continues to halve in a stepwise function through Series F and beyond. It’s a pretty steep drop-off rate.</p><p>The challenge here is that founders — having an easy time raising their seed rounds and maybe Series A — can be lulled into thinking that each subsequent round will be just as easy. Likewise, early-stage investors may not appreciate just how much follow-on support their portfolio companies will need.</p><p><strong>2016 for Version One companies</strong></p><p>So, how have Version One portfolio companies done in this environment?</p><ul><li>Collectively, our companies raised over $100M in 2016</li><li>We welcomed five new companies to our portfolio: <a href="https://www.abstractapp.com/">Abstract</a>, <a href="http://www.asktrim.com/">Trim</a>, and three yet-to-be-announced</li><li>Across Funds I and II, eight companies raised follow-on funding. The ones we announced publicly are: <a href="https://goshippo.com/">Shippo</a> (Series A), <a href="https://mattermark.com/">Mattermark</a> (Series B), <a href="https://outreach.io/">Outreach</a> (Series B).</li><li>In total, we now have 28 active companies with the highest concentration of companies in the SF/Bay Area (11) and Toronto/Kitchener-Waterloo (7).</li></ul><p><strong>Looking ahead to 2017</strong></p><p>We expect that the financing scene in 2017 will look very similar to 2016. Of course, upcoming IPOs like Snapchat will bring some added excitement to the industry.</p><p>We also believe that we’ll get more clarity on what the next platform will be. Every 10–15 years, a major cycle reshapes the computing landscape: PC (1981), Internet (1994), Mobile (2007). If historical trends continue, we should now be at the cusp of the next big thing. Chris Dixon for example believes that we’re in the <a href="https://medium.com/software-is-eating-the-world/what-s-next-in-computing-e54b870b80cc#.tx4m0212m">early stage of <em>multiple</em> new eras</a>, fueled by advancements in deep learning and different platforms (autos, wearables, drones, IoT, and AR/VR).</p><p>If we look beyond the cyclical nature of computing platforms, we can see that technological innovation comes in waves — with a surge of technological development followed by quieter periods of adaptation. First, there was the Industrial Revolution, followed by the Age of Steam and Railways; Steel &amp; Heavy Engineering; Oil, Autos &amp; Mass Production; and now the Information and Communications Technology Revolution.</p><p>In his post <a href="http://reactionwheel.net/2015/10/the-deployment-age.html">“The Deployment Age,”</a> Jerry Neumann discusses our current stage within this historical context, providing a great synopsis of Carlota Perez’ theories surrounding the path that each technological revolution takes, including the social, economic, and institutional ramifications.</p><p>In short, Perez believes that we are currently in the deployment period for web and mobile. In this phase, companies move from creating entirely new markets to expanding and consolidating their existing markets. They make their products cheaper and easier to use in order to appeal to more customers. And, funding moves entirely to production capital, with little to no focus on next-wave technologies.</p><p>As investors, we need to be future-looking…whether we’re looking for the next new computing platform or looking for new ways to expand the existing market. As such, we are excited about:</p><ul><li>Cryptocurrencies (blockchain/Ethereum)</li><li>VR/AR</li><li>Genomics</li><li>Robotics</li><li>Quantum Computing</li><li>And more</li></ul><p>In the coming year, we’ll be spending significant time on these themes, likely focused on the application layer. It’s important to note that we’re looking for startups leveraging <a href="http://versionone.vc/our-refocused-investment-thesis/">network effects</a> in these new themes, because they are platform-agnostic after all.</p><p>We still love <a href="http://versionone.vc/marketplace-handbook/">marketplaces</a>, <a href="http://versionone.vc/social-handbook/">social platforms</a>, and <a href="http://versionone.vc/favorite-investment-themes-right-now-ai-machine-learning/">applications of AI/ML</a>, but starting January, we’ll begin writing more about these new themes with the hope of stirring up new dialogue about emerging technology. If you’re enthusiastic about these themes as an entrepreneur, investor, or operator, please reach out!</p><p><strong>But until then…</strong></p><p>… we thank our LPs, colleagues, partners, portfolio companies, friends, and followers, for their continued support this year. We are fortunate to love what we do because of the people who make it worthwhile.</p><p>Our best wishes to you and yours for a happy holiday season and here’s to an awesome 2017!</p><p>– Angela &amp; Boris 🙂</p><p><em>Originally published at </em><a href="http://versionone.vc/2016-review/"><em>versionone.vc</em></a><em> on December 14, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=740a62d91177" width="1" height="1" alt=""><hr><p><a href="https://medium.com/versiononevc/a-year-in-review-2016-740a62d91177">A Year in Review: 2016</a> was originally published in <a href="https://medium.com/versiononevc">VersionOneVC</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Announcing our second eBook: Understanding Social Platforms]]></title>
            <link>https://medium.com/versiononevc/announcing-our-second-ebook-understanding-social-platforms-607751799488?source=rss-1d6ecf706047------2</link>
            <guid isPermaLink="false">https://medium.com/p/607751799488</guid>
            <category><![CDATA[social-network]]></category>
            <category><![CDATA[social-platforms]]></category>
            <category><![CDATA[community]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[messaging]]></category>
            <dc:creator><![CDATA[Angela Tran Kingyens]]></dc:creator>
            <pubDate>Wed, 07 Dec 2016 14:00:34 GMT</pubDate>
            <atom:updated>2016-12-14T15:06:52.092Z</atom:updated>
            <content:encoded><![CDATA[<p>If you have been following our blog or firm, you know how much we love network effects. <a href="http://versionone.vc/our-refocused-investment-thesis/">Our investment thesis is centered around network effects</a>, and our portfolio is full of network effects startups ranging from marketplaces to social platforms, SaaS and applications of AI and machine learning.</p><p>It has been a little over a year since we published our first handbook, <a href="http://versionone.vc/marketplace-handbook/">A Guide to Marketplaces</a>. And now, we’re pleased to announce that we have just produced our second eBook, “<a href="http://versionone.vc/wp-content/uploads/2016/12/Understanding-Social-Platforms-Dec2016.pdf">Understanding Social Platforms</a>.”</p><p>Why social? As individuals, we use social platforms on a daily basis. As investors, we love the underlying business models, including the daily use case, virality, and network effects. Humans have an innate need to interact with others. As a result, there will always be room for companies to dream up new ways to help us connect, share, learn, and participate.</p><p>Version One, as well as Boris as an angel, have invested in social platforms like Abstract, Edmodo, Figure 1, Shift Messenger, Wattpad, among others.</p><p>Over the past year, as we have been refining our investment thesis, we realized that not much has been written about social platform businesses. This is most likely because social platforms like Twitter, WhatsApp, and Figure 1 are quite diverse: it’s hard to draw conclusions that apply across them all.</p><p>To that end, we are sharing the insights we have gained from investing in, and watching, social platform businesses. In this book, we walk through the dynamics of each platform type: messaging, private networks, public networks, enterprise networks, and communities. There are chapters on metrics, exits, valuations, as well as our outlook for future opportunities in social.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wOnz0SgR7Zi-ckU3ZUOcHA.png" /></figure><p><strong>Download the </strong><a href="http://versionone.vc/wp-content/uploads/2016/12/Understanding-Social-Platforms-Dec2016.pdf"><strong>PDF</strong></a><strong> or </strong><a href="https://www.dropbox.com/s/ce3ipr135mnuhhj/Understanding%20Social%20Platforms-Dec-2016.epub?dl=0"><strong>ePub</strong></a><strong> version of the handbook and refer to it as you need it.</strong></p><p>Lastly, we’d love to hear if you find the content useful. What should we expand on? Did we leave anything out? Please leave a comment below or reach out to us directly.</p><p><em>Originally published at </em><a href="http://versionone.vc/social-handbook/"><em>versionone.vc</em></a><em> on December 7, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=607751799488" width="1" height="1" alt=""><hr><p><a href="https://medium.com/versiononevc/announcing-our-second-ebook-understanding-social-platforms-607751799488">Announcing our second eBook: Understanding Social Platforms</a> was originally published in <a href="https://medium.com/versiononevc">VersionOneVC</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>