<?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 Elie Khoury on Medium]]></title>
        <description><![CDATA[Stories by Elie Khoury on Medium]]></description>
        <link>https://medium.com/@eliekhoury?source=rss-810fb05d65f2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*wg8BUR1tebBSCHID.jpeg</url>
            <title>Stories by Elie Khoury on Medium</title>
            <link>https://medium.com/@eliekhoury?source=rss-810fb05d65f2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 07:53:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@eliekhoury/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[Introducing Woopra Data Loader]]></title>
            <link>https://medium.com/woopra/woopra-data-loader-journey-mapping-cfbae7a63710?source=rss-810fb05d65f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/cfbae7a63710</guid>
            <category><![CDATA[journey-maps]]></category>
            <category><![CDATA[customer-analytics]]></category>
            <category><![CDATA[business-intelligence]]></category>
            <category><![CDATA[big-data]]></category>
            <category><![CDATA[user-journey-mapping]]></category>
            <dc:creator><![CDATA[Elie Khoury]]></dc:creator>
            <pubDate>Tue, 19 Nov 2019 20:58:12 GMT</pubDate>
            <atom:updated>2019-11-19T20:58:12.567Z</atom:updated>
            <content:encoded><![CDATA[<p><em>You can now import existing data to Woopra to retroactively map the end-to-end user journey.</em></p><p>Today, we’re excited to introduce a new feature that we’ve been working on for over a year: Data Loader.</p><p>We hear the following scenario over and over: you have existing customer data in SQL databases, data warehouses, Salesforce, and a multitude of other platforms. You want to understand how this data impacts the user journey, but you have no way of leveraging that historical data. This is where Data Loader comes in.</p><p>With Data Loader, customers can now import and convert their <em>existing</em> customer data from various sources into Woopra as actions without involving a developer. This ultimately enables our customers to <em>retroactively</em> map the end-to-end user journey across all channels.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2cHgAJCDX31yB6Y6mdiIFw.png" /></figure><h3>What problems are we solving?</h3><p>Woopra’s initial approach to data collection has been through front-end trackers, such as our <a href="https://docs.woopra.com/reference#getting-started-with-tracking-sdks">Javascript Snippet</a> and its underlying <a href="https://docs.woopra.com/reference#intro-http-tracking">HTTP Tracking API</a>. The primary focus has always been on real-time tracking of user behavior across websites, web applications, and mobile apps.</p><p>Around 2014, we introduced AppConnect to evolve our data collection systems and collect data from third-party service providers such as Zendesk, Stripe, and others using Webhooks, a technique that was commonly used around that time.</p><p>This approach helped our customers collect real-time customer behavioral data across all their channels to create the most comprehensive picture possible of the user experience.</p><p>This may have been the only way to collect large amounts of data at the time (I will get more into this later in this post), but this strategy has multiple limitations.</p><h4>Data Integrity</h4><p>Front-end trackers are limited mainly because the data is pushed by the user from an uncontrolled environment — the browser. While there is no way around that for front-end tracking, some important milestones such as a “<em>user signing up”</em> are being recorded in the company’s database. It may make more sense to collect data right from the source of truth rather than rely on the front-end to notify our servers that the user has signed up.</p><p>Using Webhooks for real-time data collection from service providers can also be unreliable. Webhooks might be skipped at some point for whatever reason and may end up causing problems like broken funnels.</p><h4>Data Retroactivity</h4><p>Most of our customers start using our platform years, if not decades, after they launch their business, so they already have existing data.</p><p>Tracking user behavior is, unfortunately, an afterthought by many companies. By the time they’re ready to start tracking their users, the traditional tracking methods will only track data from that moment forward.</p><p>That creates two significant issues. The first is that customers are limited to new data collected and will never be able to leverage years of data they already have. Second, customers will need to collect data for two to three months to reach an ah-ha moment.</p><h4>Developers Must Get Involved</h4><p>The third issue with traditional data collection methods is that developers have to be involved.</p><p>Developers always have bigger fish to fry, and we often face resistance and delays to getting code snippets installed and configured to track custom actions. Any little improvement or new custom action to be introduced will often have to wait weeks, if not months.</p><p>Our friends at Heap introduced an excellent solution to streamline this process by tracking all possible interactions and move the responsibility of taxonomizing data to the analytics user rather than a developer.</p><p>Since then, my colleagues at Woopra and some customers have suggested to follow that path and implement similar technology. I’ve been hesitant to move forward with this initiative for many reasons, which I won’t get into at length in this post, but mainly because we’re not in the front-end micro-interactions tracking business. It conflicts with our vision to track the end-to-end user journey. I believe that instead of replicating that solution and collecting noise that is irrelevant to the problem we’re trying to solve, we should start looking at the front-end behavioral tracker as a yet-another channel. We should also partner with the best of breed services like Segment and Heap to import just the interactions we need to complete the user journey.</p><p>This leads me to the following point.</p><h3>The Convergence of Business Intelligence and Analytics</h3><p>If you’ve been observing the data space over the past few years, you probably noticed the re-emergence of SQL and relational databases. If you didn’t catch that trend, <a href="https://www.google.com/search?q=everyone+should+learn+SQL">try this Google search</a>. Just a few years ago, the direction was that SQL is dead, and NoSQL is the future. What happened?</p><p>Amazon happened. <a href="https://aws.amazon.com/blogs/aws/amazon-redshift-the-new-aws-data-warehouse/">Amazon introduced RedShift</a>, which redefined what’s possible with relational databases.</p><p>Remember the Big Data buzzword? Companies realized last decade how valuable data is. While it was technically and organizationally challenging to store structured data due to the lack of scalability of structured and relational databases, they resorted to leveraging Data Lakes, which are designed to accept any non-structured data. They then put the weight on Data Scientists to scrape the data to get a few complex questions answered.</p><p>The introduction of a scalable relational database system like Redshift enabled companies to implement a data strategy upfront to collect data in a structured manner. This shift ultimately empowered SQL experts to get questions answered without the need for Data Scientists to write complicated code to parse through unstructured data.</p><p>As a result, a new breed of Business Intelligence cloud services emerged, such as Looker and Periscope Data. Just last year, Alphabet acquired Looker at a $2.6 billion valuation, which is impressive for a relatively new company.</p><p>Business Intelligence became more than just a data visualization tool for executives to assume correlations from line charts generated by siloed data sources. Instead, it was finally possible to bring all customer data together using SQL interfaces and make real data-driven and deterministic correlations, which ultimately drove more confident decisions. In other words, companies can now tie individual user data together and find deterministic correlations instead of having to make risky assumptions by observing two sets of aggregated siloed data.</p><blockquote>Why is this important? It’s important because the customer analytics space and business intelligence space are converging. Those two species of data solutions are now solving the exact problem.</blockquote><p>What happened next? Similarly to how Webhooks trended in 2013, cloud services now realized that their value increases by making their data available in data warehouses. They are offering basic analytics, but that data cannot be tied to data from other sources. A marketing automation service can tell you how many emails were sent on a day to day basis and how many were opened. That’s great, but it will not tell you how that email campaign is affecting your customer engagement and how a particular audience is resonating with campaign X and not Y.</p><p>For that reason, most service providers have launched or are launching the ability to dump their data in some data warehouse. If they don’t, companies like <a href="https://www.stitchdata.com/">Stitch Data</a> are helping their customers do just that.</p><p>Modern data warehouses like Amazon Redshift, Google BigQuery, Snowflake, and others are at war today to be the <em>“final destination”</em> for all company customer data.</p><p>Now, to the problems.</p><h4>Need For Data Experts</h4><p>Using Business Intelligence solutions today requires data experts — or SQL experts to be more specific. It’s true that companies no longer need to hire dozens of data scientists to answer fundamental attribution questions. However, if your team doesn’t know SQL, they’re still running blind and <a href="https://techcrunch.com/2016/06/12/data-breadlines-and-data-brawls/">waiting in the data breadline</a> to validate their efforts and make data-driven decisions.</p><h4>SQL for User Journeys</h4><p>The SQL interface is absolute horsesh*t for attribution analysis. While it can help you narrow down complex multi-dimensional data into one simple two-dimensional tabular report, SQL is not the right solution for generating graphs — and user journeys in particular. It doesn’t mean that you can’t do it, but you will probably have to write a three page SQL query to generate a very basic funnel (e.g., X users did step A, then 50% did step B, then 10% did step C).</p><p>It gets even more complicated when you want to analyze a particular initiative and its attribution to the success or failure of the customer.</p><h4>SQL Is Too Generic</h4><p>While SQL is mighty, it’s too generic for the average decision-maker at companies.</p><blockquote>Suggesting that marketers should learn SQL is like asking Uber drivers to pave the road and build the car from the ground up.</blockquote><p>SQL queries can be used for any type of data, including satellite data, traffic lights, weather conditions, and more. But, when it comes to customer analytics, there are two constants that we are dealing with:</p><ol><li>The structure of the data: Timestamped user actions and unique identifiers</li><li>A finite set of possible questions: Behavioral segmentation, attribution analysis, funnel reports, journey mapping, growth trends, retention and cohorts analysis</li></ol><p>So optimizing for a specific data structure and building a friendly drag &amp; drop user interface that abstracts the complexity (and limitations) of SQL queries is arguably the best way forward to democratize customer analytics.</p><p>Which finally leads us to the initiative we’re launching.</p><h3>Launching Data Loader</h3><p>Our mission at Woopra is democratizing customer data to enable every team member to analyze the effect of their work on the success of the company. A key component to realizing this mission is providing a complete view of the end-to-end user journey.</p><p>With the launch of Data Loader, Woopra customers can now import and convert all their existing customer data from various sources into Woopra as actions without involving a developer. This enables customers to retroactively map the end-to-end user journey across all channels.</p><h4>Here’s How it Works</h4><p>Woopra has full control over the underlying data architecture. Our proprietary database system is optimized for sophisticated queries like behavioral segmentation, journey analysis, and attribution reporting. And as a result, users can get all their customer-related questions answered in seconds, without the need to work with data experts! Which of course is impossible with traditional SQL based systems.</p><p>To make all this possible, every behavioral data point we collect must adhere to the following rules:</p><ul><li><strong>When:</strong> Must have a timestamp — we must know when the user did that particular action</li><li><strong>What:</strong> What is the user doing in this action, and optionally what metadata is associated with this action? (e.g., view page x, create a ticket, use feature X)</li><li><strong>Who:</strong> Must have a unique identifier so we can tie that activity to the right user.</li></ul><p>So if we can take all the data you have and identify these three variables, we can successfully import your existing data, convert it to a behavioral footprint data structure, and keep it in sync.</p><p>Let me give you a typical example. A SaaS company has some database of <em>users</em>, which is their source of truth for authentication and more. That table looks as follows:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d5190ee140b9e41d5f9cb292a67a1a43/href">https://medium.com/media/d5190ee140b9e41d5f9cb292a67a1a43/href</a></iframe><p>In this scenario, we can convert entries in that table into a “<em>Signup</em>” action in Woopra as follows:</p><ul><li><strong>When:</strong> <em>date_created</em></li><li><strong>What:</strong> ‘<em>Signup’</em></li><li><strong>Who: </strong><em>ID (unique), email (unique), first name, last name</em></li></ul><p>This mapping process can be configured by directly connecting your data source to Woopra. Woopra will automatically load the schema (all the tables and columns). Then our customers, in collaboration with our data consultants, can map all these tables into actions and user properties. On top of that, Woopra offers an ID Graph system to handle all the scattered unique identifiers across all the services and databases you’re importing data from.</p><p>Once the initial batch is imported, Woopra can look for changes as fast as every minute, to make sure that your data is continuously in sync.</p><p>One data source at a time and one table at a time, we can build the whole end to end journey overnight without wasting our users’ and their developers’ time. What’s impressive is that many of our customers host all that data in one final destination data warehouse. But even if they don’t, Woopra will connect to your service providers and import existing data the same way by loading schemas as tables and allowing you to join data to match unique identifiers across multiple data sources.</p><p>Even more? We will have a mapping template pre-generated for all the service providers that you chose to load data from. So in most scenarios, loading tickets and payments historically would be as simple as authorizing your helpdesk system and payment gateway.</p><p>Our first release includes connections with leading database technologies:</p><ul><li>Amazon Redshift</li><li>Google BigQuery</li><li>Azure</li><li>Snowflake</li><li>Cassandra</li><li>MySQL</li><li>Postgres</li></ul><p>as well as cloud services such as:</p><ul><li>Salesforce</li><li>Zendesk</li><li>Stripe</li><li>Hubspot</li><li>And more</li></ul><p>We now have the infrastructure to scale our data sources through partners, and we’re open to integrating directly with most data sources upon request.</p><p>We can’t wait to see you use the Data Loader.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cfbae7a63710" width="1" height="1" alt=""><hr><p><a href="https://medium.com/woopra/woopra-data-loader-journey-mapping-cfbae7a63710">Introducing Woopra Data Loader</a> was originally published in <a href="https://medium.com/woopra">Woopra</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Woopra 2019 Q1 Update]]></title>
            <link>https://medium.com/woopra/woopra-2019-q1-update-4a43e23ab296?source=rss-810fb05d65f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a43e23ab296</guid>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[data-analysis]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[analytics]]></category>
            <dc:creator><![CDATA[Elie Khoury]]></dc:creator>
            <pubDate>Wed, 20 Mar 2019 23:49:51 GMT</pubDate>
            <atom:updated>2019-03-27T20:28:43.838Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kQjRIvhaRkc9peTk47PUcg.png" /></figure><p>Today, we’re announcing our 2019 Q1 product update. We refreshed the UI, finalized the <em>Journey report</em> and introduced a few new types of <em>People Metrics</em>.</p><h3>Refreshed UI</h3><p>Fine tuning the UI and pixel perfection is an area we’re always working on. This release introduces over 100 UI fixes and improvements. With so many enhancements, we’ll let the UI speak for itself.</p><h3>New Journey reports are out of beta</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UJ6xiXlKglWLuylEtSjsrw.png" /></figure><p>As some of you know, we’ve been experimenting with a more comprehensive approach to help you analyze your user journey. We quickly realized that we were trying to squeeze too many solutions into a single feature which prompted us to refocus on the core functionality.</p><p>During the beta, we experimented with <em>Footprints</em>; the ability to analyze <em>First </em>and<em> Last touch</em> for a step between two steps. While the last touch option brought some solid attribution insight, we became aware that it may still be limited when you want to analyze the attribution of specific steps on the conversions. We decided to spin off that feature into a new report which we’re calling “Attribution” which will be launched later this year.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LF1fVhOKmcDGDfagfO0t2g.png" /></figure><p>By removing Footprints (first and last touch), we are now able to support the optional flag across both <em>Parallel</em> and <em>Dynamic steps</em> which will give our customers a lot of flexibility designing and visualizing their user journey.</p><p>Although we no longer support footprints, all of your old Journey reports will be automatically migrated to the new interface.</p><h3>Enhanced People Reports</h3><p>We continued to add additional dynamic columns to our People reports and introduced two new column types.</p><h4>Count Distinct</h4><p>This column will allow you to count the unique number of specific actions or visit properties which opens up a new world of possibilities. Now you can count the number of devices used by a user, the number of locations they’re visiting from, or the number of features they used.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/834/1*PZTh_IeJ2nBg08b3YAueew.png" /></figure><h4>Last Touch</h4><p>Introducing Last Touch to our People Metrics helps you study the last occurrence of a specific action. You can now add columns such as Last Purchase Date, Last Feature Used, Last Email Read, Most Recent Login Date and more.</p><p>The Column Editor was also redesigned to make room for other column types we will be introducing in the future.</p><h3>New Woopra Profiles</h3><p>We also completely redesigned the Profile UI to allow for a more responsive experience. The new Woopra profile is designed to be embeddable in your other tools such as CRM and Help Desk systems. So if you’re using <em>Salesforce</em> or <em>Zendesk</em>, you will see the new enhanced and more responsive UI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1ODXsRPwg3uNQMlkbhyj7A.png" /></figure><h4>Profile Search Bar</h4><p>We introduced a Profile Search bar that enables quick date and action filtering to spot important aspects of the user journey.</p><h4>Histogram: Active vs Passive Actions</h4><p>Active and Passive actions have been added to the histogram to clearly differentiate between actions taken by the users (e.g. opening an email) and actions taken on their behalf (e.g. sending them an email).</p><p>We’ll soon provide a customizable iFrame Embed Code that you can use in your backend pages as well.</p><p>This new modular profile design introduces a dashboard system that will make room for <em>Profile Metrics</em>, a new feature that we’re introducing soon.</p><h3>What’s next?</h3><p>Next quarter, we’re introducing a new transformative product and that will be the biggest feature since the introduction of our Integration system (formerly AppConnect). I can promise that this feature will transform how you’ve always thought about and used customer data.</p><p>Stay tuned!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a43e23ab296" width="1" height="1" alt=""><hr><p><a href="https://medium.com/woopra/woopra-2019-q1-update-4a43e23ab296">Woopra 2019 Q1 Update</a> was originally published in <a href="https://medium.com/woopra">Woopra</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What it Means to Have a Product-First Company]]></title>
            <link>https://medium.com/woopra/what-it-means-to-have-a-product-first-company-18c12ef3a114?source=rss-810fb05d65f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/18c12ef3a114</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Elie Khoury]]></dc:creator>
            <pubDate>Tue, 11 Apr 2017 17:48:34 GMT</pubDate>
            <atom:updated>2020-08-11T01:29:16.234Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hKcuiBlWkEQ-Sykotddmgg.jpeg" /></figure><p>Looking at the likes of Stripe, Slack, Evernote or MailChimp, you can begin to understand the meaning of a product-first organization. It’s not a website tagline or value statement, but a culture they’ve embraced that places innovation and user experience above all else.</p><p>I’ve spoken, read and heard from dozens of product founders and was blown away after learning of the creativity and team alignment that can spawn from an inspiring product vision. But, how do you know if you’re a product-first company? Is it inherently in your DNA? Is there a secret recipe that one could follow to get there?</p><p>I’ve found that common denominators tie these companies together. They have similar challenges and team backgrounds. They have moments of triumph and setbacks revealing weakness. Whether you’re developing a disruptive new product or driving a well-established corporation, the product-first mindset is equally applicable.</p><p>My hope is that by continuing to absorb advice from other incredible product companies, while building one of my own, we can all learn from these examples together. So, without further ado, here’s what I’ve learned it means to have a product-first company, both from my trials and observations, and that of others.</p><h3>The Makeup of a Product-First Company</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/589/1*0cfuHC9eOlfrnooS7qZpig.png" /></figure><h4>Product-Minded Leadership Team</h4><p>Product companies are generally dominated by product teams (e.g. engineering, user experience and product experts) and leadership has a background in product rather than business or sales. This is important to distinguish because product founders will have different priorities than a sales founder.</p><p>A sales founder loves the thrill of new customer acquisition, while figuring out how to scale and penetrate markets. He/she will focus on hiring experienced sales and marketing teams first to communicate and sell the value. This works in many cases and fails in others. Take Microsoft’s <a href="http://www.newyorker.com/business/currency/why-steve-ballmer-failed">Steve Ballmer as an example</a> of a major fail, resulting in one of the biggest missed opportunities of the decade!</p><p>In contrast, a product founder loves the thrill of perpetual innovation; look to good ol’ Steve Jobs for an example worth emulating. He built an organization entirely dedicated to delivering the best products! These founders have a strong, clearly communicated vision and focus on hiring people who value the product-first approach, nurturing this as the company scales.</p><p>Ben Horowitz <a href="https://a16z.com/2010/04/28/why-we-prefer-founding-ceos/">wrote a great piece</a> on why they prefer funding companies with founding CEOs at Andreessen Horowitz. In it, he describes:</p><blockquote>Founding CEOs are excellent at finding, but not maximizing, product cycles. Our experience shows — and the data supports — that teaching a founding CEO how to maximize the product cycle is easier than teaching the professional CEO how to find the new product cycle.</blockquote><p>The reason being that innovation is the core competency of any business, and founding CEOs, like Steve, built their company by overcoming doubt and having the courage to push innovative ideas to the forefront. They had to believe in their product, understand the technology required, what code base was needed to make it happen and how to overcome market challenges to bring their idea to life.</p><p>A product-driven leadership team will do the same — leveraging the knowledge at their disposal to identify and maximize new product cycles while keeping innovation alive.</p><h4>Product Engagement Drives Conversions</h4><p>Product-first companies have confidence in what they’ve built and, as a result, in offering a low barrier to entry. Often running a freemium model, they trust that the right people using and experiencing the product will purchase. The focus is long-term over short-term gain and with this, you’ll see things like flexible pricing terms, month-to-month contracts and free trials.</p><p>Look at Dropbox, SendGrid or Asana, for example. These companies optimize for<a href="http://www.business2community.com/product-management/build-sales-accelerating-product-qualified-lead-engine-01696527#q4ie0OFC6XF68omK.97"> PQLs (product-qualified leads)</a> over MQLs (marketing-qualified leads) or SQLs (sales-qualified leads).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/719/1*ixz2Zusqp87uYNt-jrR2sA.png" /></figure><p>In the PQL model, the traditional lead funnel is flipped, starting instead with product adoption. Rather than combing through a massive database of contacts or identifying a select group of prospects, users qualify themselves by product usage and engagement.</p><p>Another great example is <a href="https://thenextweb.com/dd/2016/05/11/github-new-pricing/#.tnw_PUD0QhhO">Github’s recent price reduction</a> for repositories. They adjusted their pricing model to allow individuals to create an unlimited number of non-open source projects with the ability to invite collaborators. Strategies like these promote stickiness and encourage the sharing and collaboration that drive success.</p><p>As Phil Libin, Evernote CEO, said:</p><blockquote>The easiest way to get one million people paying is to get one billion people using!”</blockquote><p>But, getting the traction to reach that one billion users begins with a deep understanding of the product value and bringing users to that “aha!” moment as quickly as possible.</p><p>The outcome is that product-first companies are beloved companies! They have to be. There’s no immediate pressure for users to become customers which automatically builds trust and loyalty. Once users see value, growth is generated by cultivating an experience that turns users into customers and customers into promoters. Leveraging these promoters, product-first companies can scale organically, by offering a taste of the product and “wow-ing” users with the experience.</p><h4>Cross-Company Alignment on Mission</h4><p>Having a product-first company requires a clearly defined, laser-focused mission at the forefront of all decision making. Creative thinking, collaboration and an intense thirst for disruption is welcomed and permeates throughout all levels of the organization.</p><p>While every feature in the roadmap is designed to delight users and create better experiences, leadership teams must make difficult decisions to stay on track. There are times when a customer must be “fired” in exchange for putting the product vision first. This doesn’t mean customer feedback is ignored, but instead, accepted and incorporated into the roadmap <strong>when it aligns</strong> with the mission.</p><p>This is unique, so I’ll say it again. Instead of shaping the product to appeal to the request of a high-paying or demanding customer, product-first companies may have to say “no” if the request doesn’t match their core value proposition or fit into the scope of your existing priorities.</p><p>A friend of mine refers to this scenario as “feature blackmail” and it’s actually a common startup pitfall. There will be cases when a big customer or prospect comes and threatens to not renew, or become a customer, if you don’t develop a specific feature they’re requesting. This is “feature blackmail” and you shouldn’t fall for it.</p><p>It’s never easy to turn down a potential paycheck but ultimately, it all goes back to long-term over short-term gain. Good leadership will focus on building features that map to and complement the vision. They know when to compromise and how to avoid derailing the roadmap if it doesn’t make the product stronger for their primary audience.</p><h3>The Challenges with Product-first</h3><p>In business, product-first isn’t always the winner. It’s prone to mistakes, with plenty of room for error and it’s easy to stumble in the wrong direction. If you have a product-minded leadership team, product engagement driving conversions and cross-company alignment on your mission — you’re well on your way to being a product-first company. But, getting it all right requires incredible execution and nothing less.</p><p>As Slack’s CEO Stewart Butterfield <a href="https://medium.com/@stewart/we-dont-sell-saddles-here-4c59524d650d#.f3zxpnlm5">described in a memo</a> back in 2013:</p><blockquote>Even the best slogans, ads, landing pages, PR campaigns, etc., will fall down if they are not supported by the experience people have when they hit our site, when they sign up for an account, when they first begin using the product and when they start using it day in, day out.</blockquote><p>The advantage being that when it’s done right, there’s an opportunity to scale significantly faster than sales-driven companies, with higher margins and returns — the product will sell itself! You’ll have created a brand worth talking about, with a compelling vision that differentiates your company from the rest. All of this from having the passion and courage to build a product-first company.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18c12ef3a114" width="1" height="1" alt=""><hr><p><a href="https://medium.com/woopra/what-it-means-to-have-a-product-first-company-18c12ef3a114">What it Means to Have a Product-First Company</a> was originally published in <a href="https://medium.com/woopra">Woopra</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>