<?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 In Sik Rhee on Medium]]></title>
        <description><![CDATA[Stories by In Sik Rhee on Medium]]></description>
        <link>https://medium.com/@insikr?source=rss-9fc10170ff0e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*gBmYoo9iubqkF-vD.jpg</url>
            <title>Stories by In Sik Rhee on Medium</title>
            <link>https://medium.com/@insikr?source=rss-9fc10170ff0e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 00:09:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@insikr/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[Building a new product/market category]]></title>
            <link>https://medium.com/vvus/building-a-new-product-market-category-a6ed9f57725a?source=rss-9fc10170ff0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6ed9f57725a</guid>
            <dc:creator><![CDATA[In Sik Rhee]]></dc:creator>
            <pubDate>Thu, 04 Jan 2024 06:31:46 GMT</pubDate>
            <atom:updated>2024-01-04T21:08:47.656Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y5dcSydWj4Zb4MJYOWzJlw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@codyengel?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Cody Engel</a> on <a href="https://unsplash.com/photos/man-standing-on-rock-JdrGnREEMKI?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Unsplash</a></figcaption></figure><h3>Building a new product for a market category that doesn’t exist yet</h3><p>One of the hardest startup journeys — for founders and investors alike — is building an enterprise software company when there’s no clear predefined market. It’s one of the greatest joys when done right, but full of pitfalls along the way. I feel lucky to have been a founder during the infancy of the Internet, when so much innovation was created. Both of my entrepreneurial journeys — Kiva Software and Opsware — ushered in new software categories. As an investor, I’ve had the privilege of backing several successful startups at “day 0” such as Terracotta, Couchbase, and Cloudera. Today, I still find immense satisfaction in backing teams that dare to challenge conventional wisdom and build products that can ultimately create new markets.</p><p>What does it take for founders to break into the enterprise market with a brand-new idea, and how do I evaluate those companies as an investor? I’ll list a few axioms and tactics that I like to follow during the ideation process in these cases below, in no particular order of importance.</p><h3><strong><em>Problem identification is the most important exercise. Minimize hypothesis.</em></strong></h3><p>What is the fundamental problem/challenge of the customer’s organization? Who cares and why? How is the customer addressing the issue today? How does that differ with your solution? What changes and risks are they introducing in order to adopt your solution? What does success look like? What happens if it fails? Why do they need the solution today?</p><p>If you can’t answer any of these questions, your chances at defining a new market are slim. A new company/category/product requires a healthy dose of vision and hypothesis. In consumer tech, it’s impossible to validate market hypotheses. In enterprise tech, it’s relatively straightforward — the hard part is figuring out who to ask.</p><h3><strong><em>Define the customer journey. Don’t build products for a market blindly without customer validation.</em></strong></h3><p>Customers buy products, markets do not. Define the customer precisely: delineate by sub-segments, including Logo/Brand, Department, User, Buyer, Champion. One of the most powerful enterprise software sales methodologies is <a href="https://www.lucidchart.com/blog/close-more-deals-with-meddic-sales-process#:~:text=MEDDIC%20is%20an%20acronym%20that,customer%20into%20your%20sales%20funnel.">MEDDIC</a>. If you embrace nothing else, understand the “Discovery” process of that technique and conduct these sessions before you get in too deep by writing a ton of code.</p><h3><strong><em>You only get one chance to make a first impression.</em></strong></h3><p>The first meeting with any enterprise prospect should be a healthy balance of founders asking a lot of questions to better understand the organization prior to pitching demos. I often tell founders not to discuss their product or launch into demos in the first meeting (unless asked), especially when dealing with a large enterprise. The best founders focus their initial dialogue with a prospect on understanding the customer organization and providing empathy and feedback to specific challenges and problems. Remember, patience is a virtue!</p><h3><strong><em>Explain the problem, not how you solve it.</em></strong></h3><p>A startup’s website should guide the customer journey. The primary job of the website is to let the visitor identify with a pain point or a value you can clearly articulate within a very short attention span (usually less than a minute). Without establishing context for the problem, you’re just marketing to drive-by strangers. I like to look at a founders’ homepage during a first call and ask them “how do you feel about your current website”?</p><h3><strong><em>Simple values create the largest market opportunities. Focus on what you do for your customer, nothing else.</em></strong></h3><p>Coming up with a mission statement is a very powerful exercise for every founder. The best companies can distill their value proposition into a few sentences: “We are the #1 company that does X for Y”. Solving for X and Y sounds trivial, but it can be quite challenging in today’s crowded tech ecosystem. By the same token, a clearly defined and memorable mission statement can help you stand out from the pack.</p><h3><strong><em>Proof by induction is powerful.</em></strong></h3><p>Pick 3 design partners, ideally in different industry categories or sizes of organization. Try to force yourself to build features that appeal to all 3. Many young startups invest too much resources on a single enterprise use case, only to find that it’s very difficult to replicate the results to new customer journeys. I once backed a startup where the founder’s first customer was a 7-figure deal with a major Wall Street bank. This deal ended up nearly killing the company as the product strategy morphed into a customer wish list, undermining the vision.</p><h3><strong><em>Pivoting an idea is easier than pivoting a product, or a sales process.</em></strong></h3><p>As a young engineer, I always valued the difficulty of building the technology above all else. Years later, I learned that fixing broken products or building new features are relatively easy endeavors compared to recasting the market messaging or diagnosing a sales process. Far easier. Founders should take a very comprehensive view of the entire customer journey when ideating a new company, even in the absence of a market.</p><h3><strong><em>Conclusion</em></strong></h3><p>The journey of a founder is a lonely one fraught with fear, uncertainty, and doubt. The best founders build conviction early by efficiently building relationships with early customers who validate their approach to solving a problem they can jointly identify — shared conviction is a powerful motivator. Founders, customers, and investors who can share conviction can create amazing innovation together.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6ed9f57725a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vvus/building-a-new-product-market-category-a6ed9f57725a">Building a new product/market category</a> was originally published in <a href="https://medium.com/vvus">Vertex Ventures US</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Running better board meetings that lead to better outcomes]]></title>
            <link>https://medium.com/vvus/running-better-board-meetings-that-lead-to-better-outcomes-a47f65e23a39?source=rss-9fc10170ff0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/a47f65e23a39</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[board-of-directors]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startupş]]></category>
            <dc:creator><![CDATA[In Sik Rhee]]></dc:creator>
            <pubDate>Mon, 13 Nov 2023 20:40:12 GMT</pubDate>
            <atom:updated>2023-11-13T20:40:12.905Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TGuk22IL8-W5RTJq.jpg" /></figure><p>The past two years have seen quite a correction in the technology markets, putting CEOs under a lot of pressure to perform efficiently.</p><p>Gone are the days when it was easy to raise capital, where a few growth metrics centered around ARR growth were all they needed to justify a healthy premium in their valuations. The industry has seen a lot of RIF (reduction in force, or layoffs), even as many enact stricter cost-cutting measures.</p><p>Under these challenging circumstances, CEOs have had to step up as leaders. Some have risen to the challenge, and we’ve witnessed some truly heroic behavior from CEOs who work tirelessly to navigate these choppy waters.</p><p>On the other hand, we’ve also seen some leaders withdraw and become distant, choosing to try to solve problems on their own rather than engage with what should be their greatest resource — their board of directors. The best and most resilient CEOs we know actively engage the board, enlisting their operational wisdom and domain expertise to constructively find solutions to their problems.</p><p>However, the structure of the board meeting itself is often counterproductive, keeping discussion of the real issues to a minimum. Here’s the quick primer to how a CEO should manage their board, prior to and during their regular meetings.</p><ol><li><strong>Be prepared</strong>. Prepare and send board material at least 24 hours in advance. Operational results, P&amp;L and other necessary governance documents should be distributed to the board ASAP. In turn, the board’s job is to do the reading prior to showing up.</li><li><strong>Be inclusive</strong>. Sometimes, CEOs try to represent the views of their entire C-Suite by “pulling everything together” and presenting it themselves. This isn’t scalable, nor does it give the board confidence that they’re getting the full picture. Instead, have each functional exec give a short presentation at each board session, and have them be present in the room the whole time to answer questions and address concerns as they arise. The board gets the benefit of hearing directly from the source, and the exec gets to know exactly what’s on the board’s mind.</li><li><strong>Be transparent</strong>. The board wants to understand the causes of success as well as setbacks. Burying the bad news or skimming over details on churn causes, lost deals, or missed product deadlines does not help the situation — it makes the board meeting a game of “hide-and-seek” where the board needs to probe and ask questions to get after the truth. This deteriorates the relationship between the CEO and board over time, and trust lost can be impossible to rebuild. Simply present the metrics alongside the plan and provide the relevant rationale. Even if the figures aren’t flattering, the board will appreciate the transparency and get into problem-solving mode faster.</li><li><strong>Provide analysis</strong>, not just results. interpretation of the operating results and a view as to the general momentum of the business is far more interesting and important than just reading out the stats. We want to understand how you want to navigate the choices ahead, and to help you focus and build confidence toward a narrow path. In order to do that well, it’s important to always have a plan you can communicate and present the underlying hypothesis and assumptions that inform the plan.</li><li><strong>Look forward</strong>, not just backward. A good board session should spend at most 50% on results and updates, and a big chunk of time on forward looking initiatives (beyond sales forecasts) and concerns regarding operational choices. Sometimes it’s okay to take the board into a deep dive into a single function’s plan, whether that’s product, marketing, customer success, or something else entirely. Board members can help map your forward looking strategy against their past experiences and offer insightful questions and challenges you may not have considered.</li><li><strong>You don’t work for the board, the board works for you</strong>. Many CEO’s think of a board as some glorified decision-making body. The last thing a good board should be doing is making decisions for a CEO. Our job is to help CEOs make decisions as best and efficiently as possible. CEOs should lean into the knowledge and wisdom a board can provide to build confidence in their own decisions, right or wrong. Outside the board session, engage in regular 1:1s and make sure you’re getting the most out of each board member’s experience and expertise.</li></ol><p>Ultimately, it’s important for founders to think of the board meeting as a critical tool in their belt. Used improperly, it can slow down progress and reduce the company’s chances at success. When wielded with care and intention, however, these meetings can help CEOs streamline decision making and gain confidence to execute through uncertainty.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a47f65e23a39" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vvus/running-better-board-meetings-that-lead-to-better-outcomes-a47f65e23a39">Running better board meetings that lead to better outcomes</a> was originally published in <a href="https://medium.com/vvus">Vertex Ventures US</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is it possible to modernize the data pipeline without hiring a new data team?]]></title>
            <link>https://medium.com/vertexventures/is-it-possible-to-modernize-the-data-pipeline-without-hiring-a-new-data-team-eab03d094e59?source=rss-9fc10170ff0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/eab03d094e59</guid>
            <dc:creator><![CDATA[In Sik Rhee]]></dc:creator>
            <pubDate>Tue, 30 Jun 2020 16:04:25 GMT</pubDate>
            <atom:updated>2020-06-30T18:42:18.237Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P1qO-byLYRDvxb7hMQimqA.jpeg" /></figure><p>In the last 20 years, data processing capabilities have increased at least by 1000x thanks to cheaper storage, cheaper bandwidth, increased compute, and most importantly, advancements in distributed data processing techniques (MPP, Hadoop, Spark). What used to cost millions of dollars in CapEx and OpEx to process a terabyte’s worth of data now costs hundreds of dollars, if that. Despite such modern advances, with data flowing in real time from all aspects of our analog and digital lives, the volumes of data collected and processed by enterprises continued to grow at an even faster exponent, and the old terabyte problem is now a petabyte problem for many enterprises.</p><p>In the past generation, OLTP and OLAP worlds were bridged by ETL and ESB. Multibillion-dollar companies such as Oracle, Teradata, Informatica, Tibco, and MuleSoft emerged as leaders in these fields respectively. Most of their technology innovations occurred during the “terabyte-scale” era. Since then, a new generation of cloud-enabled services began to disrupt these incumbents. Companies such as Cloudera, MongoDB, Snowflake, Databricks, and Confluent began to promote new technologies and best practices to ensure companies could handle “petabyte scale.”</p><p>Many enterprises rushed ahead to build pristine “data lakes” often to discover that they had “data swamps.” Data lakes were more focused on storing vast sums of data infinitely, as opposed to ensuring that the quality and format were correct. As a result, a new class of tools emerged to solve these legacy problems such as data preparation, data catalog, and ETL. Many of these products were based on open source technologies contributed by hyperscale internet companies. They were complex, unstable, and had steep learning curves without adequate documentation or tutorials. Furthermore, they forced enterprises to invest in new talent who could do platform engineering work in order to get data to a useful state. These people were data engineers. They had skills in Java, Scala, distributed clustering, message queues, systems management, and provisioning, in addition to data analysis. Data engineers were difficult to source, and the very best worked in the largest successful internet startups (who paid them far better than most enterprises could afford).</p><p>However, recently we’ve seen the data world start to fully embrace cloud computing. As a result, there is a lot of fantastic growth and momentum in storing, processing, and analyzing data all in the cloud. In such a world, why would I want to spend time cobbling together my own tooling and looking to build a data engineering competency?</p><p>This is when we intersected on our latest investment, <a href="http://upsolver.com/">Upsolver</a>. Upsolver was founded by two data practitioners frustrated by the experience of having to manage a data lake in order to scale their ad-optimization startup. They toiled away at solving systems management problems (scaling, reliability, performance) instead of working with datasets. As a result, they pivoted their company to focus on the data pipeline (ETL) problem and built a sophisticated product that can be used by traditional DBA or SQL analysts to handle modern data pipelines in the cloud.</p><p>Upsolver found early traction and was recently featured as an AWS Advanced Technology Partner. We loved that they were able to easily handle production “petabyte-scale” real-time workloads for their customers, but we were more impressed upon learning that these customers were able to realize the full value by upskilling their existing staff and resources instead of having to hire a new team or outsource implementation to a consulting firm.</p><p>One of our investment theses is that there is a large opportunity in creating heroes out of an underserved class of stakeholders. That’s how companies like VMWare and Splunk got built. In Upsolver, we found a similar pattern in the forgotten DBA who had been left out of the journey to data lakes and the cloud. We are excited to announce our lead in Upsolver’s $13M Series A financing along with our friends at Wing Venture Capital and our close collaborators Jeff Rothschild and Sohaib Abbasi.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eab03d094e59" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vertexventures/is-it-possible-to-modernize-the-data-pipeline-without-hiring-a-new-data-team-eab03d094e59">Is it possible to modernize the data pipeline without hiring a new data team?</a> was originally published in <a href="https://medium.com/vertexventures">Vertex Ventures</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Protecting trade secrets with Data Behavior Analytics]]></title>
            <link>https://medium.com/@insikr/protecting-trade-secrets-with-data-behavior-analytics-c10379471e9a?source=rss-9fc10170ff0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/c10379471e9a</guid>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[venture-capital]]></category>
            <category><![CDATA[data-protection]]></category>
            <category><![CDATA[enterprise-technology]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[In Sik Rhee]]></dc:creator>
            <pubDate>Thu, 05 Dec 2019 17:30:20 GMT</pubDate>
            <atom:updated>2019-12-05T18:12:37.157Z</atom:updated>
            <content:encoded><![CDATA[<p>Increased regulatory scrutiny around sensitive data and the threat of billions in losses from data breaches have applied pressure across industries (from manufacturing, financial services, healthcare, high-tech, governments, municipalities, and more) to better monitor and safeguard sensitive information. Over just the past five years, highly publicized breaches and cases of IP theft at organizations such as Equifax, Marriott, British Airways, Uber/Waymo and others have led to billions of dollars in fines and financial loss — not to mention the enduring impact of tarnished brands. As a result, regulations such as GDPR, CCPA, and others have emerged and begun to impose stringent standards and fines.</p><p>While bad actors are attempting to steal valuable trade secrets by breaking into organizations from the outside, the majority of sensitive data leaks are caused unintentionally by trusted users — often senior executives who forward sensitive information without understanding the potential negative consequences. Today’s enterprise knowledge workers collaborate across many different SaaS applications such as Office 365, Salesforce, Dropbox, Google Suite, Slack, etc. Each application contains silos of data being consumed and shared by its users. Moreover, each vendor works hard to offer easy “one-click share” features to promote organic growth of their service across corporate domains. As a result, enterprises are left with the challenge of understanding what business-critical data lives in which silos, who is responsible for stewarding it, and how to monitor both the activity of the data and movement as it migrates between users and applications. Prior methods of tracking the flow of data were relegated to mainly filtering/blocking E-mail and corporate file servers. However, as information is rapidly disseminated via text messaging, chat apps, social media, etc., it becomes important that the context and heritage of data are always maintained:</p><ul><li>What is the sensitivity of data?</li><li>Who is authorized to access the information? Employees? Contractors? Temporary workers?</li><li>Who can the information be shared with, and under what context?</li><li>How long should users retain the information? What happens when they leave the company?</li></ul><p>We’ve been in search of a solution to this problem for a while, and today are excited to announce our investment in <a href="https://cyberhaven.com/">Cyberhaven</a> — a company that enables enterprises to rapidly visualize and monitor the dissemination of sensitive data. Its product features a powerful search interface that is utilized by security analysts to quickly visualize data movement across users and help remediate potential breach incidents. It establishes the root cause of information leaks, as opposed to merely trying to blindly “block” data from leaving an enterprise. This Data Behavior Analytics (DaBA) technology is non-invasive, real-time, and offers agility without tampering with data assets or disrupting critical processing flows.</p><p>Cyberhaven was founded by PhD students from <a href="https://www.epfl.ch/en/">EPFL</a>, a top 10 global research institute. They studied under George Candea, head of the Dependable Systems Lab, whose research focuses on building trustworthy, safe, and secure computer systems. We initially met Cyberhaven co-founder Vova Kuznetsov in 2016 as he spun out of the academic lab and started the company. Building trustworthy computing and subtle detection systems were complex endeavors requiring years of core R&amp;D, yet we were impressed with each iteration of the technology and the team’s drive. Earlier this year, Cyberhaven unveiled their newly designed product, and we were floored to see how quickly they helped identify, isolate, and monitor critical data and trade secrets for top global enterprises and government agencies. These customer testimonials convinced us that Cyberhaven’s solution has the potential to reinvent a very important category in the infosec market, and prompted us to lead the company’s Series A financing round.</p><p>We are very excited to join Cyberhaven on this journey as the team delivers its Data Behavior Analytics technology to safeguard critical enterprise information for global enterprises.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c10379471e9a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Finding Obi-Wan in Silicon Valley]]></title>
            <link>https://medium.com/@insikr/finding-obi-wan-in-silicon-valley-d8189f0dde5b?source=rss-9fc10170ff0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8189f0dde5b</guid>
            <category><![CDATA[mentorship]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[founders]]></category>
            <dc:creator><![CDATA[In Sik Rhee]]></dc:creator>
            <pubDate>Mon, 12 Aug 2019 22:10:38 GMT</pubDate>
            <atom:updated>2019-08-12T22:10:38.227Z</atom:updated>
            <content:encoded><![CDATA[<p>In Silicon Valley, we are blessed to have 2–3 generations of entrepreneurs who have pioneered ahead and won at a grand scale. These same pioneers who have won their own struggles to build amazing successes choose to invest — not just with money, but with their time — into the next generation of entrepreneurs. They become angels/advisers/mentors and often take time to give advice and connections for the next crop of entrepreneurs — sometimes during the course of a first meeting. The willingness to “pay it forward” is part of what makes our culture special.</p><p><em>Here is a lightly edited Q+A we shared recently with our founders.<br></em> <br><strong>You often speak of the importance on coaching and mentorship within the startup ecosystem, why is that? </strong><br> <br>Being an entrepreneur is a very demanding and often lonely endeavor. A founder needs to constantly make decisions about what product/features to build for audiences and use cases, with very little or no data to validate a need. Many times, the product vision precedes any existential proof of market/demand. Over the course of months and sometimes years, nagging doubts and uncertainties will linger, even after a company and team are formed to rally around the idea/vision. Avoiding failure isn’t the goal. It’s about absorbing lessons quickly and moving forward without losing confidence. It’s emotionally and psychologically draining. Every founder should seek a mentor.</p><p><strong>What are the qualities of a good coach or mentor?</strong></p><p>A great mentor comes with two important qualifications — a positive winning experience, and on-demand availability. A mentor can recollect not just their fabulous wins, but countless setbacks during the journey, and use the vast library of lessons to help entrepreneurs in a 1:1 setting. There are many great books and blogs that can sprinkle anecdotes and generalizations of “how to succeed”. Unfortunately, that’s not enough for a founder. A founder needs someone who can provide real-time feedback to very specific situations of importance as they are happening, and get in-the-moment coaching. Friday evening calls/texts are the norm here.</p><p><strong>Who was an influential mentor in your career? What was a key takeaway you implement to this day?</strong></p><p>During my 2nd startup (Opsware) we were privileged to have wonderful mentors such as <a href="https://en.wikipedia.org/wiki/Michael_Homer">Mike Homer</a>, <a href="https://en.wikipedia.org/wiki/Eric_Hahn">Eric Hahn</a> and <a href="https://en.wikipedia.org/wiki/William_Campbell_(business_executive)">Bill Campbell</a> — their impact was felt by not just what they said to us, but how they made us feel. Despite our constant setbacks and churn and upward/downward/sideways momentum quarter after quarter, we were always inspired to try new things and find new strength and resolve. They encouraged us to always think big and not settle for being #2. At the time, I underappreciated the pep talk — after all, they often didn’t understand the depth of the problems we were trying to solve. But looking back, what I recall is that every meeting started and ended with a big hug — and that made a tremendous impact to our morale and confidence to continue to tread forward. They also helped us focus on what’s most important — recruiting, educating, and retaining the best team around us. <br> <br>As a VC it’s often difficult to have the same level of trusted confidant relationship with founders — however that doesn’t mean we should shy away from the challenge. While we may not start and end every conversation with a hug, it’s great when we can accomplish the camaraderie (and yes it’s great when the occasional hug does happen)<br> <br> Some takeaways:</p><ol><li>Try to match founders with great independent mentors who can eventually become board members</li><li>Focus on building confidence and steering teams toward success, rather than diving into failure mode analysis. “Told you so” is not helpful and downright demoralizing.</li><li>It’s not just what you say that matters, it’s how you make them feel.</li></ol><p><strong>What tips do you have for founders on selecting a mentor? How should they work with them?</strong><br> <br>Look for a winner. Winners make the best coaches. Ideally, former startup founders/execs who have built their own companies to IPO or M&amp;A. Mentors should inspire confidence — and that comes best by speaking with first-hand experience.<br> <br>Try to build a connection based on your journey and mission of the company. Mentors want to share in your excitement — so show it! Their motivations are rarely for financial gain. If they are interested in investing that’s also great, but an investor does not qualify as a mentor — on the contrary, it can actually cause friction and reduce transparency.<br> <br>The goal is to have someone who understands you at a fundamental, behavioral level (how you make decisions, conduct yourself in front of the company, receive/provide feedback and handle stress) — and provide empathy and constructive feedback. This means finding someone you can feel comfortable sharing deep concerns and vulnerabilities with. It’s a serious endeavor on both sides — so it’s important to be deliberate, prepared, and make each interaction count. And be thankful.<br> <br><strong>What tools or resources does Vertex US offer their portfolio companies in the form of coaching and mentorship?</strong><br> <br>At Vertex, we run a series of Breakfast@Vertex seminars for continuous education for founders. This smallish group event is run by domain experts — many of whom would be amazing mentors in their own right — and help educate our founders on various aspects of company building. Some past speakers include:</p><ul><li>Michael Baum, founding CEO of Splunk (and 4 other startups), “How to find product-market fit”</li><li>Maynard Webb, former COO eBay, board member at VISA and Salesforce, “How to manage a board”</li><li>Scott Dietzen, CTO at BEA, President/CTO at Zimbra, CEO at Pure Storage, “Transitioning from a technical leader to CEO”</li><li>James Kim, Managing Partner at Qatalyst partners, “How to manage the M&amp;A process”</li></ul><p>Breakfast@Vertex is a roundtable held in our boardroom (typically 10–15 attendees), so every participant has opportunities to share and trade ideas.</p><p><strong>Closing thoughts</strong></p><p>I believe that the strength and uniqueness of our entrepreneurship ecosystem in Silicon Valley stems from (1) the existence of great companies, talent, and capital; and just as importantly (2) the informal cultural values of knowledge sharing and mentorship that help transfer the know-how of success to the next generation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8189f0dde5b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Announcing Testlio: A partner for agile development teams]]></title>
            <link>https://medium.com/@insikr/announcing-testlio-a-partner-for-agile-development-teams-af9d2b4f8c9b?source=rss-9fc10170ff0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/af9d2b4f8c9b</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[venture-capital]]></category>
            <dc:creator><![CDATA[In Sik Rhee]]></dc:creator>
            <pubDate>Tue, 12 Apr 2016 21:21:59 GMT</pubDate>
            <atom:updated>2016-04-12T21:21:59.513Z</atom:updated>
            <content:encoded><![CDATA[<p>Today I’m pleased to announce our investment in <a href="https://testlio.com/">Testlio</a>, a mobile app testing service tackling the ever-increasing demand for world-class quality assurance. QA has for some time been an underinvested (and always underappreciated) segment of the workforce. Much of it has to do with the adoption of web-enabled technologies and processes, which downplayed the importance of QA. However, with the adoption of native mobile applications and IoT devices, we are seeing renewed demand for this category. As we dug into the investment opportunity in Testlio, the reasons became obvious.</p><h4>Agile vs Mobile</h4><p>Agile development and DevOps are two of the hottest terms in enterprise IT today.</p><p>Unfortunately, they’re also rapidly running into the limitations of the Web-based technology ecosystem that they emerged from. As we move into a more mobile-centric world, particularly one where a wide variety of connected devices surround us (the “Internet of Things”) and every company we interact with has a native app they want us to use, agile and DevOps are unfortunately already dated.</p><p>Agile is optimized for a Web-centric technology environment where you can push updates to your application at a high rate of speed, sometimes many times a day. If there’s a glitch in the Web app, no problem: Just apply a patch as soon as you discover it and everyone will instantly be using the fixed version.</p><p>Not so with mobile apps or IoT devices. If you push an update to your app and discover belatedly that it has a critical security flaw or another problem, your options are much more limited. You may have to wait several weeks for a company in Cupertino to approve your update, if it’s an iOS app. And even once the new version of the app is out there, it will take time for every current user to upgrade. It could be weeks or months before the flawed version is no longer a significant presence in the wild.</p><p>I recently had a discussion with a top global bank. Over half of their online transactions take place via their mobile app, which has over 30 million users. So it’s a mission-critical component of their customer strategy.</p><p>This bank, which used to do a handful of updates to their software every year, now does five or six major releases in any given month. Getting each of those releases right is critical — there’s no room for an agile, “we’ll just push an update” mentality. Decisions on major UI components can’t be relegated to A/B testing. If there’s a problem with a mobile app, there’s egg on everyone’s face, including the CEO — the mobile app represents a brand’s direct interface to its consumers.</p><p>The bank is not alone. For every major enterprise with an app — and that’s virtually every major consumer brand — the stakes of pushing a new update are much higher than they ever were in the Web world. In many ways, today’s mobile and IoT developers need to go back to the era of client-server computing to learn some best practices. Clearly mapping out how users will experience an application, and testing it before deployment, have become critical again.</p><h4>A brief history lesson</h4><p>Before the internet, sometime in the late 1980’s, client-server technologies evolved as the personal computing tidal wave ran into the needs of large enterprises to centralize control and management of critical data. PCs were already in the enterprise, with employees often bringing in their own TRS-80s or IBM PCs to work on spreadsheets in Lotus 1–2–3. Computing could no longer be confined to the white-floored, air-conditioned datacenters that housed the old mainframes — but PCs also didn’t offer the power, or the security, needed for advanced corporate work. To make that tradeoff work, the client-server architecture distributed computing power between very capable servers and somewhat less capable clients.</p><p>In this environment, development was characterized by long release cycles (six to 18 months) and extensive testing. When you were shipping software on physical media (floppy discs, and later CD-ROMs) mistakes were expensive and crippling. You had to get it right.</p><p>As we moved into the Web era, we built a new model around extremely thin clients — the web browser. That necessitated the creation of application servers, connecting web pages to databases for dynamic page generation and transactions. Over a period of ten or so years (roughly 1998 to 2008) the dominant enterprise architecture shifted from client-server to three-tier architectures utilizing dynamically interpreted languages such as PHP and Python.</p><p>The browser-centric model enabled an extremely rapid, iterative development methodology, now known as agile. After all, when your application runs on a server and is accessed only through a browser, correcting mistakes is simple: You just push a hot fix and all your users are immediately using the updated application. In that environment, iteration was cheap, so it called for an approach to development that was far nimbler than the client-server era that had gone before, pushing updates to code as frequently as daily, or even many times per day. “Move fast and break things” became the motto of the era.</p><h4>The mobile upheaval</h4><p>With the advent of native mobile applications, we’re moving back to an era of compiled code, through “native” apps that are distributed via app stores.</p><p>But the mobile era is only the tip of the iceberg. We’re also seeing the onslaught of the Internet of Things: Connected devices that surround us, in everything from cars to thermostats to light bulbs. All of these devices will be running code, most of it compiled, much of it mission-critical, and all of it pushed via sporadic releases rather than continuous updates.</p><p>There are currently an estimated<a href="https://gsmaintelligence.com/"> 7.7 billion connected devices in the world</a> — more than there are humans on the planet. Thanks to the growth of IoT, there will be<a href="http://www.gartner.com/newsroom/id/3165317"> almost 21 billion connected “things” online by 2020</a>.</p><p>That means radically slower development cycles than in the Web era, because it’s harder to push updates. In the case of iOS and Android, penetration of new releases into the market can take months due to user behavior. And for IoT, upgrades are dependent on the devices being connected to the network (and power) — and,<a href="http://www.businessinsider.com/nest-thermostat-problem-2014-1"> as Nest has learned</a>, you really don’t want to screw up the upgrade of someone’s thermostat or smoke alarm.</p><p>Yet development cycles cannot afford to go back to the leisurely pace of the client-server era. Consumer and enterprise expectations are much higher, thanks to two decades of life on the Web. Apps need frequent updates to remain competitive, and also to address security vulnerabilities that can emerge with disconcerting frequency. The trick for developers is to find a new balance between rapid development are careful vetting of updates in order to avoid embarrassing and costly mistakes in deployment.</p><h4>Takeaways for the future</h4><p>To survive in this new era, developers need to shift their thinking beyond “agile.” Yes, frequent releases have become the norm and that’s unlikely to change. But developers need to balance the need for speed with a more careful, considered deployment process that takes into account some of what we learned in the client-server era.</p><p>Quality assurance and quality control are necessary investments. Every release needs to go through a structured testing process where its features are tested and validated on a variety of platforms.</p><p>Tools for automating testing are critical. With the vast number of platforms that companies need to manage in the mobile era, manual testing alone will not be able to deliver the results you need. There will always be someone with an older version of Android running an odd device you haven’t heard of. Automated testing tools can help uncover incompatibilities that you might have overlooked.</p><p>Security is a particular concern. Hackers are growing increasingly adept at exploiting whatever vulnerabilities present themselves. Sometimes those vectors are through improperly designed apps, or APIs. Security testing prior to release is just as important, if not more important, than ensuring that an app or IoT device functions as expected.</p><p>As the internet scales from 5 billion to 50 billion connected devices in the next decade, we see fundamental challenges in how processes such as dev/QA/ops evolve. We continue to seek fresh approaches to these age old problems, and are delighted to have partnered with Testlio as a starting point.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af9d2b4f8c9b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>