<?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 Brian Balfour on Medium]]></title>
        <description><![CDATA[Stories by Brian Balfour on Medium]]></description>
        <link>https://medium.com/@bbalfour?source=rss-cae0f48dccf6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*OC5x5K22R-jZTVR-M-LDjg.png</url>
            <title>Stories by Brian Balfour on Medium</title>
            <link>https://medium.com/@bbalfour?source=rss-cae0f48dccf6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 24 Jun 2026 16:11:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bbalfour/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[6 Mistakes Growth Candidates Make in the Interview Process]]></title>
            <link>https://medium.com/reforge/6-mistakes-growth-candidates-make-in-the-interview-process-3a77b05bd306?source=rss-cae0f48dccf6------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a77b05bd306</guid>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[growth-strategy]]></category>
            <category><![CDATA[interview-questions]]></category>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[growth-hacking]]></category>
            <dc:creator><![CDATA[Brian Balfour]]></dc:creator>
            <pubDate>Tue, 26 Sep 2017 00:00:00 GMT</pubDate>
            <atom:updated>2017-09-28T16:36:03.326Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>This post comes with a customizable Growth Interview Prep Template. </em></strong><a href="https://brianbalfour.com/growth-interview-prep-worksheet-subscribe"><strong><em>Get the Template here.</em></strong></a></p><p>You walk into your growth interview after hours of preparation. You’ve perfected your 2 minute pitch, polished your work stories, and maybe even done some case prep. You’re ready to showcase your achievements and you have an answer ready for any question they throw at you.</p><p>But there’s one big problem you’ve overlooked — the interview isn’t actually about you.</p><p>Most candidates approach the interview process as a way to showcase themselves and their accomplishments. But, the best growth candidates orient the process around the company and its strategy.</p><p>After years of interviewing hundreds of people applying for various growth roles, I’ve seen candidates make the same 6 mistakes over and over again. They all tie back to this one core error — thinking the interview is about you.</p><p>In this post, I’ll outline the six most common ways those mistakes play out — and look at the mental models that can help you avoid falling into the most common trap that trips up even the strongest growth candidates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/613/1*tEAt4zhzTjpd0Bhwk2qW9Q.png" /></figure><p><a href="https://brianbalfour.com/growth-interview-prep-worksheet-subscribe"><strong><em>Subscribe to get access to the interactive Growth Interview Prep Worksheet.</em></strong></a></p><h3><strong>1. You forget to identify what growth means to the company.</strong></h3><p>Growth means something different at every company. At one company, it may be another name for marketing. At another company, it may be a hybrid of marketing and product, while at another company it may mean expansion into new markets.</p><p>Whatever the case, it’s your job to find out what it means at the company where you’re interviewing, and frame your answers through that lens. The key here is to do the research beforehand, and then ask the right questions early in the screening process, prior to the main interview.</p><p>Below are a few select things you can research and questions you can ask to give you insight into what growth means at a specific company.</p><p><strong>Research the following topics:</strong></p><ol><li>Search LinkedIn to identify the leaders on the team you would be joining and look at their backgrounds:</li></ol><ul><li>What functions were they in previously?</li><li>What types of companies did they work at previously?</li><li>How long have they been in a leadership role at this company?</li></ul><p>2. Google those growth leaders to see if you can find any blogs, podcasts or other content that gives you insight into their approach to growth.</p><p>3. Google the company to see if you can find any press that outlines how it’s grown.</p><p><strong>Ask the following questions:</strong></p><ol><li>What part of the organization is the growth team part of? Is it its own team or part of marketing or product?</li><li>What metrics does the growth team own?</li><li>What are a few examples of growth focused experiments or campaigns your team has run previously?</li><li>How has the company grown thus far? What are your key channels?</li></ol><p>The risk if you don’t ask these questions early and frame your answers accordingly is that the interviewers may misunderstand what you bring to the table.</p><p>For instance, if you’re interviewing at a company that views growth simply as marketing, and you start talking about a bunch of product initiatives, it won’t resonate. To get the job offer, you need to adapt your ideas, language, and answers to how the company views growth.</p><p>You can also use this information to evaluate whether the company is the fit you’re looking for.</p><p><a href="https://brianbalfour.com/growth-interview-prep-worksheet-subscribe"><strong><em>Get the interactive Growth Interview Prep Template that goes with this post.</em></strong></a></p><h3><strong>2. You overlook the cultural principles of the growth team.</strong></h3><p>Every team operates by certain set of <a href="https://brianbalfour.com/growth-machine/principles-process-team-tactics">principles</a> that shapes the culture and drives how it makes decisions. Testing for culture fit is integrated into almost every growth interview, and lack of fit is often used by interviewers as a “veto card.”</p><p>Occasionally, those cultural principles are explicitly stated, but more often they are implicitly understood by the team. If you scroll to the bottom of my <a href="https://brianbalfour.com/growth-team">Work with Me</a> page, you can see that I outline the principles that govern my team at <a href="http://reforge.com">Reforge</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*vF0mYvQaiieNApQi916Tfw.png" /></figure><p>Many candidates don’t realize how important it is to tease out the cultural principles unique to the target company and frame their answers in terms of those principles. Demonstrating that you embody the cultural principles during the interviews lets the interviewers feel confident that you share their values and will fit culturally.</p><p>The risk of failing to identify the key principles early, is that even if you embody them, it may not come through in an obvious way during the interviews. In this case, the interviewers may wrongly assume you don’t fit with the team.</p><p>Below are a few select things you can research and questions you can ask to suss out these principles.</p><p><strong>Research the following topics:</strong></p><ol><li>Check out the company’s career page on their site — does it outline details on cultural principles?</li><li>Read the job description carefully. Are the team’s principles baked into the description of the company, team, and role?</li></ol><p><strong>Ask the following questions:</strong></p><ol><li>What are the key characteristics of the strongest members on the team?</li><li>What’s the difference between a good candidate and a great candidate for this role?</li><li>What are the core operating principles of the growth team? How are they used in the decision making process? Can you give any examples?</li></ol><h3>3. You misunderstand the purpose of “Walk me through your resume.”</h3><p>I’ve had many candidates walk me through their resumes word-for-word, listing off their previous companies and roles, without providing deeper insight than what I read on their resume. When interviewers say, “Walk me through your background,” they’re not actually looking for a verbal recap of your resume. They’re trying to get at two things:</p><p>1. What <strong>specifically </strong>did you contribute at previous companies?</p><p>2. Why did you make the decisions you made?</p><p><em>What </em><strong><em>specifically</em></strong><em> did you contribute at previous companies?</em></p><p>Rather than saying “I was on the retention team,” tell me what you did and how you drove results that led to growth. Ideally, you summarize this information on your resume, and then use this prompt to further shape the narrative around how you made an impact. Interviewers are more interested in your contributions than your role.</p><p><em>Why did you make the decisions you made?</em></p><p>Interviewers also want insight into why you made the decisions you did. We want to know how and why you chose those projects, joined that company, and took on that role. Many candidates realize it’s critical to share what they did and the impact of those efforts, but fail to understand that “the why” is what leaves a lasting impression.</p><p>“The why” offers insight into what it would be like to work with you. It reveals your personal motivations, which are usually found in why you chose to work on certain projects, and how you allocate your time.</p><p>For example, if you’re an engineer and explain that you were excited to work on a certain experiment because you thought it would deliver meaningful conversion improvements, the interviewer may infer you are motivated by growing the business. In contrast, if you instead explained that you were excited to work on the experiment because it was a big challenge, the interviewer may assume that you value solving hard engineering problems above all else, and would be dissatisfied in a growth engineer role.</p><p>When I ask candidates why they chose to work on specific projects, a common but terrible response is, “It was decided by management.” This kind of answer not only makes the candidate appear to be an order taker, it also misses the opportunity to showcase the candidate as a strategic thinker.</p><p>Instead, flip this response on its head, transform it into an opportunity to demonstrate critical thinking, and show that you had ideas about how to improve the strategy.</p><p>Say, “My manager told me to do [explain the project]. This is why I think it was chosen [explain the reasoning]. If the decision had been in my hands, I may have chosen [insert other initiative] and here’s why [explain your reasoning and why you think this other project should have been higher priority and would have had a higher impact].”</p><p><strong>Below are examples of the types of questions you want to answer in your “walk me through your resume”discussion.</strong></p><ol><li>What results did you drive in each role?</li><li>How and why did you choose each company?</li><li>What factors helped you determine that a company was a good fit?</li><li>How and why did you choose each role?</li><li>How did each role progress your career towards your longer term goals?</li></ol><h3>4. You fail to think about the target audience.</h3><p>Considering the qualitative and quantitative perspectives together <a href="https://brianbalfour.com/essays/growth-insights">drive insights for growth</a>. When you’re interviewing for a growth role, approach questions from both a qualitative and quantitative perspective to demonstrate that you know how to use both to make strategic and tactical decisions.</p><p>One of the biggest mistakes I see growth candidates make is coming into the interview without a solid hypothesis of who the target customer is. I want to see that a candidate roots their ideas in critical thought about who the product serves, rather than blindly coming up with initiatives.</p><p>Prior to your first interview, research the company and develop a point of view on who the target audience is, what their needs are, and why they use the product.</p><p>Test your customer hypotheses and showcase your critical thinking during the interview process by saying something like, “Before I answer that question, I’d like to make sure I understand the target audience. Here is my current hypothesis given the preliminary research I’ve done, but I’m wondering if you can tell me more?”</p><p>After the interviewer shares their point of view, weave their insights into your answers to show that you listened and adapted your hypothesis to reflect new input. Doing this will demonstrate that you take the user’s perspective into account when framing growth problems, opportunities, and hypotheses. It will also have three other positive benefits — it shows:</p><ol><li>You “do your homework” and take initiative</li><li>You’re not afraid to develop a point of view</li><li>You’re <a href="https://brianbalfour.com/essays/embrace-constant-change">adaptable</a> and you listen to feedback — you ask questions and refine your POV based on new input</li></ol><p>Below are things to research and questions to ask to understand the qualitative aspects of the target audience.</p><p><strong>Research the following topics:</strong></p><p><strong>1. Analyze the company’s website (especially the home page and pricing page) and/or presence in the App Store</strong> — what can you learn about how they define the target audience from the messaging, imagery, and pricing?</p><p><strong>2. Read reviews on Yelp</strong>, in the app store and any other review site. Who are those people? Why do they love or hate the product? What motivates them to feel the way they feel?</p><p><strong>3. Scan their social media presence</strong> — what are people saying about them on Facebook, Twitter, Instagram, LinkedIn, etc.? Who are those people? Why do they love or hate the product? What motivates them to feel the way they feel?</p><p><strong>Ask the following questions:</strong></p><ol><li>How does your customer describe the pain point or problem that your product solves?</li><li>What are the top 3 reasons your customers use your product?</li><li>Can you walk me through the persona for your target customer? What are their demographics, psychographics, and needs, and what channels do they spend the most time in?</li></ol><h3>5. You don’t focus on the data.</h3><p>On the flip side, I’ve interviewed many candidates who make the mistake of relying purely on “gut feel,” rather than consulting behavioral user data to guide their decision making process. As I interview, I look for candidates who use data to pressure test and validate their growth ideas that may have originated from instinct.</p><p>There are a few ways that you can demonstrate data-orientation during the hiring process:</p><p><strong>1. Include quantitative outcomes in your resume. </strong>For instance, if a bullet point on your resume highlights a project you worked on related to retention, make sure to include something like, “Launched [insert initiative], increasing retention by x%.”</p><p><strong>2. As you’re walking through experiences in your work history with interviewers, speak to the quantitative impact your work had for each project you worked on.</strong></p><p><strong>3. When answering case exercises, explain how you would use the given data and ask for any data that seems important but hasn’t been shared.</strong> Even if the interviewer doesn’t give you the data, asking for specific baseline metrics not only demonstrates data orientation, but also shows you know which metrics are important.</p><p><strong>4. Ask questions about the company’s metrics throughout the interview process. </strong>For instance, if you’re interviewing at a startup and you want to assess its level of Product-Market fit, you could ask what the retention curves looks like. Again, asking this question, and other data-related questions, will show that you know which metrics matter.</p><p>Intuition is important, but ultimately growth leaders are looking to hire practitioners who balance qualitative and quantitative inputs to keep themselves honest, on track, and <a href="https://brianbalfour.com/essays/how-to-setup-a-growth-team-for-maximum-impact">working on the highest impact initiatives</a>.</p><p>To get insight into the quantitative user data, here are a few examples of questions you can ask throughout the interview process.</p><p><strong>Ask the following questions:</strong></p><ol><li>What does retention for the product look like?</li><li>What is the CAC and LTV?</li><li>What do the top of funnel and conversion metrics look like for the product?</li></ol><p>When candidates don’t factor in both the qualitative and quantitative data, they end up becoming reactionary, which leads us to the next mistake…</p><h3>6. You jump to an answer too quickly in case exercises.</h3><p>It’s becoming more popular for companies to ask case questions during growth interviews. These types of on-the-spot exercises can be nerve wracking for even the most experienced candidates.</p><p>The biggest mistake I’ve watched candidates make over and over, is jumping to an answer immediately upon being presented with an exercise-based question. For instance, when given a question asking where they would focus in a specific channel or on a certain initiative, many candidates jump right into ideas they have to optimize x or y.</p><p>But that’s the wrong approach. Candidates often miss the point of these types of exercises, randomly grab for immediate answers, and then dig into those answers when questioned. These exercises are less about giving the right answer, and more about demonstrating how you approach problems, evaluate and prioritize options, and make decisions. Think back to 6th grade math — it’s the demonstration of your work that matters most, not your answer to the question.</p><p>In case questions like this, you want to make sure you take a step back first and start by focusing on higher level strategy, not tactics. Start by asking the interviewer questions to understand the goals, audience, metrics and any other information that would help you identify the strategy.</p><p>Once you have that baseline information, breakdown the desired goal or output into its inputs, and walk through how you would identify and prioritize different initiatives in which you could invest. Questions like this are great opportunities to get on the whiteboard and map out your strategy, goals, inputs and approach to show your process, rather than just tell.</p><p>By walking the interviewer through your approach, rather than immediately jumping to an answer, you demonstrate that you have a repeatable process for approaching growth problems. More importantly, you demonstrate that if you had the role full time, and access to all information, that you’d have a high likelihood of identifying winning strategies and tactics.</p><p>Here are a few types of questions you can ask during a case exercise to help you focus at the strategic level first. Since case questions vary quite a bit, tailor the questions you ask to the information that is explicitly given in the case.</p><p><strong>Possible Questions:</strong></p><ol><li>What is the goal or desired outcome of the initiative, experiment, or campaign?</li><li>Who is the target customer or audience?</li><li>What is the baseline for [insert key metric]? And where do we want to take it?</li><li>What resources do we have at our disposal?</li></ol><h3>Research + Hypotheses + Smart Questions + Critical Thinking = A Winning Interview Strategy</h3><p>Ultimately, whenever you’re interviewing for a growth role, you’re being tested for skills, experience and fit, but most importantly, the interviewers are assessing your critical thinking.</p><p>One of the best ways to demonstrate your critical thinking about the company and its market in the interview, is to do as much of it as you can beforehand. Do your research, ask the key questions early in the process, come up with your hypotheses, and then translate your answers and stories into the language spoken by the company and its people.</p><p><a href="https://brianbalfour.com/growth-interview-prep-worksheet-subscribe">Subscribe to get access to the interactive Growth Interview Prep Worksheet.</a></p><p><em>Originally published at </em><a href="https://brianbalfour.com/essays/6-mistakes-growth-interview"><em>brianbalfour.com</em></a><em> on September 26, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a77b05bd306" width="1" height="1" alt=""><hr><p><a href="https://medium.com/reforge/6-mistakes-growth-candidates-make-in-the-interview-process-3a77b05bd306">6 Mistakes Growth Candidates Make in the Interview Process</a> was originally published in <a href="https://medium.com/reforge">Reforge</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How You Battle the “Data Wheel of Death” in Growth]]></title>
            <link>https://medium.com/read-think/how-you-battle-the-data-wheel-of-death-in-growth-dc75e7317692?source=rss-cae0f48dccf6------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc75e7317692</guid>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Brian Balfour]]></dc:creator>
            <pubDate>Tue, 04 Apr 2017 00:00:00 GMT</pubDate>
            <atom:updated>2017-07-06T23:26:41.143Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WkEhya4IkPi3lPtIvXU2rg.jpeg" /></figure><p>This is the Data Wheel of Death:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*qOjSQipyodorZQJakKteJw.jpeg" /></figure><p>If the above looks familiar, you’re not alone. I estimate that greater than ⅔ of data efforts at companies fail.</p><p>This is trouble because data plays a key horizontal role in the growth process and mindset. <strong>Without good data, it’s not possible to run a legitimate experimentation cycle.</strong></p><p>Today, I’ll take a look at 4 reasons why well-meaning data efforts fail so often, and what you can do about it.</p><h3>#1: Project Mindset vs Process Mindset</h3><p>Most companies that want to get more serious about data approach it as a project. Something with a definitive start and a definitive end.</p><blockquote>When you think about data as a project, you get the Data Wheel of Death.</blockquote><p>The project wraps up, but at some point someone finds a piece of data that doesn’t look quite right. As a result, they don’t trust it and then they stop using the data. Because no one is using the data, the data isn’t maintained — which leads to more distrust.</p><p>In the above scenario, treating data like a project is at fault. In reality, data is an ongoing, never-ending project, similar to building a product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*EeES9qzphSKIyOETnmJtKg.jpeg" /></figure><p>Your data needs to be refined and updated via an ongoing process for a few reasons:</p><p><strong>1.Your product will change.<em> </em></strong>Features will change on an ongoing basis. As your product evolves feature by feature, your data also needs to keep pace or it will become irrelevant / flawed, people will lose trust, and the Data Wheel of Death will continue.</p><p><strong>2.Your understanding of the business will change. </strong>Data should lead you to insight that might lead you to prioritize some things and de-prioritize others.</p><p>Andrew Chen likes to say, “Your data and KPI’s should be a reflection of your strategy.” Your strategy will change over time and what you track and analyze needs to evolve along with what it.</p><p><strong>3. New answers expose new questions. </strong>As you gain fresh insight from your data, it opens the door to new questions. As you have new questions, you need to update your instrumentation and analysis. Saying the process is “done” is saying you understand every thing there is to know about your users, product, and channels.</p><p><strong>4. Shit breaks. </strong>It’s that simple.</p><p><strong>5. Data is never done. </strong>People spend more time on analyzing what tool to use than they do instrumenting and updating their data. The project mindset is what’s behind this, and is tied to a mindset of “I have to get this right the first time.” The problem — there is no perfect tool and you end up in analysis paralysis.</p><p>If you view data as an ongoing process — there’s no defined finish — it’s easier to jump in knowing that you’re bound to iterate as new needs emerge.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F3364e9%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2F3364e9%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/cc48a905796627aa20c894847aa3b04c/href">https://medium.com/media/cc48a905796627aa20c894847aa3b04c/href</a></iframe><h4><strong>What to do instead</strong></h4><p>Instead of a one-and-done, project-based approach to data, you should assign dedicated resources for both data collection and analysis.</p><p>In the earliest stages, this might be part of a couple of engineers’ or PMs’ time, but no matter how many or how few the number of hours it is, it needs to be seen as critical part of their role.</p><p>In later stages as the company grows, you will most likely need a dedicated team to maintain the data process — both building and maintaining the data infrastructure, and promoting data usage.</p><blockquote>It’s important to keep in mind that getting a data process off the ground isn’t just about instrumentation. Your other job is to build trust with the consumers of your data within the organization.</blockquote><p>You must spend time verifying data in at least some of the reports and working with the greater team around you to make sure they both understand and trust what they’re seeing. <strong>If they don’t trust it, they won’t use it.</strong></p><h3>Issue #2: Misalignment of Incentives</h3><p>Even if you treat data as a process vs a project, that doesn’t necessarily translate into success. There are companies that spend endless time on the infrastructure, tooling, and instrumentation but then miss something extremely important.</p><blockquote>Getting an organization to use data requires behavior change among the individuals.</blockquote><p><strong>Changing behavior is extremely difficult.</strong> There is typically one culprit behind the lack of change: a misalignment of incentives and rewards.</p><p>Teams and individuals will ultimately do what they are <a href="http://www.coelevate.com/essays/how-to-setup-a-growth-team-for-maximum-impact">rewarded for</a>. So if you want to change behavior, you have to make sure that the behavior is part of what they are rewarded for. There are multiple types of rewards:</p><ul><li>Financial Rewards (bonuses/raises/equity)</li><li>Progression Rewards (promotions)</li><li>Authoritative Recognition (good job from boss/superior, etc)</li><li>Peer Recognition (“good job” from peers, etc)</li></ul><p>When you look around your team, how often are you delivering one of those rewards related to the use of data?</p><h4><strong>Here’s the problem</strong></h4><p>If the use of data is not rewarded, then the work that it takes to instrument and analyze data will be seen as friction to doing what is rewarded, or what’s perceived as a “good job” within the company.</p><p>If the use of data is rewarded, then the work it takes to incorporate data will be seen as an ally to doing a good job.</p><p>Then ask yourself a second question: How big / often is that reward in relation to other things you reward for?</p><p>How big/often the use of data is rewarded compared to other rewards signal importance/priority. Managers need to be careful how they weight different factors as part of rewards.</p><h4><strong>What to do instead</strong></h4><p><strong>1. Every team needs a KPI. </strong>Every team needs a KPI as part of their measure of success. Having a KPI for each team aligns the use of data to their work vs positioning data as a friction point. Just setting the KPI isn’t enough, though. These 3 things need to happen:</p><ul><li>The team needs have a sense of ownership over the KPI.</li><li>If they don’t feel like they own it, they will view it as someone else’s problem.</li><li>Every single person on the team needs to understand the KPI and have easy access to viewing it.</li></ul><p>Often times only the PM or a couple people on the team will truly understand it.</p><p>The KPI needs to be part of the four types of rewards, but not the only thing the team is rewarded for.</p><p>There are other important factors for product teams like shipping velocity, product quality, etc. Like most things, it is a balance.</p><p><strong>2.Design systems for each type of reward. </strong>Go through each of the four reward types and design systems to reward for the use of data. What do I mean by systems?</p><p>Here’s a quick example around a system for Authoritative Recognition Reward: the best managers I know have checklists they use to prep for every 1:1. An item on the checklist might be “Did this person display the use of data in their work?”</p><p>If yes, make sure to give recognition for it. It is too easy to forget these types of things unless you have specific prompts.</p><p><strong>3.Communicate the rewards clearly. </strong>Don’t assume that team members know how they get promotions, bonuses, praise. You need to put it in writing, make it explicit, and reinforce. You have to over communicate in order for it to get through.</p><p>When you promote someone, don’t just announce “Congrats to Jane Smith on her promotion to Sr. Product Manager.” Back the announcement up with examples of the type of work and behavior that the person has displayed which led to the promotion.</p><h3>Issue #3: Data Team Becomes the Bottleneck</h3><p>If you solve process vs project and incentives and data starts to become valuable in the company it creates a couple of new problems.</p><p>The first is that the data team can end up becoming a bottleneck. This stems from a the data team taking an “ownership” mindset to the data, i.e. “We own the data.”</p><p>But ownership thinking leaves out one important point: <strong>Every team has a “customer.”</strong></p><p>The data team’s customers are the other people using the data internally: data analysts, product managers, engineers, marketers, etc.</p><p>In service to these internal customers, the data team needs to act like any other product team:</p><ul><li>They need to define their customer segments</li><li>They need to understand customer needs</li><li>They need to deliver the most compelling solution</li><li>And they have to iterate!</li></ul><p>In other words, their output must be able to enable other teams’ output, rather than them being the exclusive owners.</p><h3>Issue #4: Brilliant Answers, Useless Questions</h3><p>There’s a second issue that arises once data has become valuable and recognized, and that’s when people start noodling on data for data’s sake. Whether it’s because they find the data process intellectually fascinating, or just to seem smart, productive, etc. in the end, it’s data masturbation :)</p><p>Data for data’s sake is an alluring trap, but only creates “brilliant answers to useless questions,” as <a href="https://www.linkedin.com/in/kenrudin/">Ken Rudin</a>, Head of User Growth &amp; Analytics at Google and former Head of Analytics at Facebook, says.</p><p>Rudin reminds us that even though it’s alluring to increase knowledge, insight alone isn’t enough — results and impact are the true goal of analytics. To that end, data teams should make sure they’re asking the right questions, not just coming up with more and more answers.</p><p>Rudin has two suggestions for how to create a data process that actually serves business needs:</p><p><strong>1.Hire analysts that are business savvy, not only academic about data or its tools. </strong>When you interview candidates, don’t focus on just “How do we calculate this metric?” Ask them “In this business scenario, what metrics do you think would be important?”</p><p><strong>2.Make data everyone’s thing. </strong>Rudin’s team at Facebook ran a two week “Data Camp” for not just the data team but for everyone at the company. It gives the wider organization a common language to frame questions that data can answer. <em>(Some great additional talks by Ken on data and impact </em><a href="https://www.youtube.com/watch?v=-FnlygE2sSo"><em>here</em></a><em> and </em><a href="http://productsthatcount.com/blog/facebook-analytics-vp-on-big-data-bigger-impact/"><em>here</em></a><em>.)</em></p><p>A solid data process will be informed by asking good questions that result in a real business impact. Rudin also makes a great point that data teams must be accountable for not just “actionable insights” but the fact that those necessary actions get taken.</p><blockquote>As data provides answers and actions, it helps shape better and better questions.</blockquote><p>As data’s answers translate to impact, people will be incentivized to maintain and even improve data systems, leading to more data capacity, and stronger answers to better questions.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fbaf3c9%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2Fbaf3c9%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/770f7a65b7c654ee54b52d898eba941b/href">https://medium.com/media/770f7a65b7c654ee54b52d898eba941b/href</a></iframe><h4>Learned something? Say “thanks” by clicking the 💚.</h4><p><em>This article was originally published at </em><a href="http://www.coelevate.com/essays/growth-data-mistakes"><em>www.coelevate.com</em></a><em> on April 4, 2017.</em></p><p><strong>Keep reading about this topic…</strong></p><p><a href="https://thinkgrowth.org/the-startup-founders-guide-to-analytics-1d2176f20ac1">The Startup Founder’s Guide to Analytics</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc75e7317692" width="1" height="1" alt=""><hr><p><a href="https://medium.com/read-think/how-you-battle-the-data-wheel-of-death-in-growth-dc75e7317692">How You Battle the “Data Wheel of Death” in Growth</a> was originally published in <a href="https://medium.com/read-think">ThinkGrowth.org</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[7 Things I Wish I Knew When I Started My Career]]></title>
            <link>https://medium.com/buffer-stories/7-things-i-wish-i-knew-when-i-started-my-career-c69be5d55d54?source=rss-cae0f48dccf6------2</link>
            <guid isPermaLink="false">https://medium.com/p/c69be5d55d54</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Brian Balfour]]></dc:creator>
            <pubDate>Wed, 12 Oct 2016 00:00:00 GMT</pubDate>
            <atom:updated>2017-07-06T23:11:57.244Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U6ZqU_U8fYXxsPranVtDUA.jpeg" /></figure><p>In marketing/growth there is a big industry problem. An addiction to Hacktics - the tips, tricks, hacks, tools, and secrets that promise to solve all growth problems.</p><p>As a result, marketers now get the majority of their “learning” through this prescription based hack-tic content which isn’t helping create the next crop of great marketers. As a result, I recently <a href="http://www.coelevate.com/essays/learn-growth-marketing">wrote about what growth professionals should focus on instead</a>. In the process, I realized that these principles apply to many professionals.</p><p>Most real world work involves a problem that doesn’t have an answer yet, and the biggest growth opportunities are in uncharted territories. More specifically, you don’t figure out the answer by just plugging in the answers that have worked for others in the past. Instead, the biggest upside lies in solving problems that likely didn’t exist before.</p><p>As we emphasize continuously in <a href="http://reforge.com">Reforge</a>, becoming an elite professional has nothing to do with the specific hammer in your toolkit and everything to do with mastering the emerging skills, frameworks, and thought processes that enable you to solve new problems, repeatedly.</p><p>So that begs the question, how do you do this?</p><h3>1. Generalist or Specialist?</h3><p>I’ve commonly been asked the question, “Should I be a generalist or a specialist?”</p><p>It is such a popular question that it was asked on Inbound. I hate to say it, but 100% of people who took the poll got it wrong. Partly because the question presents two false choices.</p><p>Some of the commenters started to get it right by saying that you should “<a href="http://www.coelevate.com/essays/customer-acquisition">Shape yourself like a T.</a>” But what does that actually mean?</p><ol><li>Master The Fundamentals</li><li>Go Deep</li></ol><p>Lets dive into each of those individually…</p><h4>Mastering The Fundamentals</h4><p>In his book <a href="https://www.amazon.com/5-Elements-Effective-Thinking/dp/0691156662">The 5 Elements of Effective Thinking</a>, author Edward Burger tells a story about internationally acclaimed composer and trumpet player Tony Plog teaching a group of students:</p><blockquote><em>“During the class, each student played a portion of his or her selected virtuosic piece. They played wonderfully. Tony then gave very easy warm-up exercise that any beginning trumpet player might be given. They played the handful of simple notes, which sounded childish compared to the dramatically fast, high notes from the earlier, more sophisticated pieces.</em></blockquote><blockquote><em>After they played the simple phrase, Tony, for the first time during the lesson, picked up the trumpet. He played that same phrase, but when he played it, it was not childish. It was exquisite. Each note was a rich, delightful sound. The students’ attempts did not come close — the contrast was astounding.”</em></blockquote><p>The point of the story is that the difference between the master and student happened <strong><em>at the level of fundamentals</em></strong>.</p><p>The fundamentals are the foundation that everything else builds upon. Another analogy would be in sports. What separates someone like Lebron James from average professional basketball player (physical advantages aside) are not his abilities to dunk or complete alley oops. Lebron simply knows how to dribble, pass, and shoot a jump shot, better. The fundamentals.</p><p>The fundamentals help you solve the variety of growth problems you will face in your specific situation. The better you are that fundamentals, the harder the problems you will be able to solve. The fundamentals for growth are not Search, Facebook Ads, Content, etc. It also has nothing to do with a set of tools.</p><p><strong>The fundamentals for growth are:</strong></p><ol><li><strong>Data Analysis</strong> — Understanding the meaning of data to identify, understand, and pinpoint solutions.</li><li><strong>Quantitative Modeling</strong> — Translating your historical data into a forward looking model to simulate the future which helps you understand better what you should be doing today.</li><li><strong>User Psychology</strong> — The data doesn’t matter unless you know how to influence the numbers in an authentic way. That comes down to understanding the psychology of your audience, problem, and solution to figure out what your users respond to.</li><li><strong>Storytelling</strong> — You can be the best at quant modeling, analyzing data, and understanding the psychology, but to be a great growth professional you need to know how to bring those things to life in a way that is compelling and interesting to your target audience. This is storytelling.</li></ol><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F9e52a1%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2F9e52a1%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/655cb3dfddd624e18f6546a11f065607/href">https://medium.com/media/655cb3dfddd624e18f6546a11f065607/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vVynJlRge_tvf81SaeKBqg.jpeg" /></figure><p>Everything else like Copywriting, CRO, Facebook Ads, etc build off the foundation of these four things.</p><p>Don’t underestimate how much time you need to be spending on the fundamentals. Reading Cialdini’s “<a href="https://www.amazon.com/Influence-Psychology-Persuasion-Robert-Cialdini/dp/006124189X">Influence</a>” doesn’t mean you know User Psychology. Your learning on the fundamentals never ends. It is continual process of mastery.</p><h4>Go Deep</h4><p>Every time I’ve hired for a role I inevitably get a swarm of applications with a couple years of experience that say they “know” CRO, Facebook Ads, Content Marketing some other combination of 5 + things. The applicants claim they are generalists, and they’re proud of it. Sounds great on paper, but as soon as I dig in I typically find they are ok at a lot of things, but amazing at nothing.</p><p><strong><em>Being “ok” at a variety of things, is far less valuable then been amazing at one.</em></strong></p><p>Why is that?</p><p>Anyone can learn the surface layer of a subject. But going deep requires you to solve problems where the answer isn’t in some hacktics blog post. You never experience this as a generalist. The best way to get better at solving problems, is by solving more problems so in the process you actually build the skills that will enable you to go deep on something else.</p><p>When I hire, I will take someone who has become amazing at one thing over a generalist any day of the week because if they got great at one thing, the probability of them becoming great at another are a lot better.</p><p>When I’ve given the “go deep” advice to those early in their careers I’ve found that it feels daunting to them. Common responses I get are:</p><blockquote><em>“What if I don’t like it?” <br>“I might not want to pin my career on that one area.” <br>“I don’t want to be stuck there.”<br>“I better be really sure.”</em></blockquote><p>Two responses to this…</p><p>One, the only way to find out the answers to those questions is through action. You aren’t going to think your way to those answers. You need to dive in and spend enough time on it to give yourself an opportunity to fight through a hard problem.</p><p>Two, this isn’t a 10 year commitment. If you really focus you can go deep on something in a year or two. If you end up not liking that area, it’s not a waste.</p><p>The process of going deep on one thing is itself a skill that makes it easier to go deep on another.</p><h3>2. Choosing What You Work On</h3><p>A large input into how you learn are the projects you work on in your organization. That means you should choose projects wisely. How do you make decisions of what projects to work on in the organization?</p><p>Some people choose projects based on if they were the easiest, the most fun, the most creative, the most technically difficult, etc.</p><p><a href="http://www.coelevate.com/growth-machine/maximize-learning">If you want to optimize for learning</a> and career trajectory, you’ll need to take a different approach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*moWlIzMr-EYj2-FlOcbk5g.jpeg" /></figure><p>While most people will position themselves in one of the three blue quadrants, you want to position yourself in the green quadrant — getting into the projects that have high organizational impact and are unpopular to everyone else. Why?</p><p><a href="http://www.coelevate.com/essays/learning-and-impact-over-ideas-and-activity">Having high org impact</a> should be self-explanatory. Projects are unpopular because they are typically hard and messy. But, by taking those projects on you do a few things:</p><ol><li><a href="http://www.coelevate.com/essays/learning-and-impact-over-ideas-and-activity">You learn a lot</a> simply because the more challenging a project is the more you tend to learn.</li><li>Messy projects require a deeper level of understanding to untangle whatever the mess is. You instantly become an expert on something that is high impact in the org.</li><li>You put yourself at the center in focus. These types of projects tend to have high visibility in an organization. You are seen as a leader/savior because you are tackling something no one else wanted to touch. Everyone wants these types of people on their team.</li></ol><p>The combination of those two things leads to faster trajectory. If you successfully solve one hard problem, people will come to you with more. Opportunities will start flowing to you rather than you having to seek them out.</p><h3>3. Keep One Foot in the Known</h3><p>My first job out of college was as a Product Manager at ZoomInfo. By all measures I was a terrible employee when I started.</p><p>I entered into a situation where 90%+ of what I was suppose to work on were things I knew nothing about and as a result I struggled to make progress on anything. My manager at the time quickly recognized this, and we had a long honest conversation about what I was comfortable with and what I wasn’t. From there, he helped reshape the project so that a larger percent was based on things I knew and was comfortable with while make sure a chunk was still new to me. That was a turning point for me. After that, I not only learned much faster but delivered much better results.</p><p>If you want to maximize learning you need a foot in the known and a foot in the unknown. Whatever you are working on, a certain percentage of the work are things you already know, and a certain percentage are things you don’t know and have never worked on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*55T-rEPByUnEFuEaCIASJA.jpeg" /></figure><p>You don’t want to be too far in the known. When everything is known you aren’t continually learning and over a long period of time <a href="http://www.coelevate.com/essays/growth-is-never-done">you become obsolete as the industry moves around you</a>. The challenge is that it’s easy to fall too far into the known because it feels easy, comfortable, and efficient or you start to get bored which leads to unhappiness.</p><p>Being too far in the unknown also has its problems. It is easy to get overwhelmed and not know where to start, making it impossible to make progress.</p><p>I often hear that you should jump into something with both feet if you want to learn. But studies have shown that the <a href="http://journal.frontiersin.org/article/10.3389/fnbeh.2013.00139/full">most effective learners learn by relating the new with the known</a>.</p><p>In reality there is no perfect 50/50. What you want to shoot for is the range in the middle. Sometimes you might be 70% in the known, and 30% in the unknown. Sometimes the reverse. Your goal is to recognize the signs when you are one of the ends of the spectrum and figure out a way to work yourself back to the middle.</p><h3>4. Accomplishments Over Credentials</h3><p>I went to the University of Michigan for my undergraduate degree. While I enjoyed my college days I look back now and realize that it was an extremely unfulfilling experience.</p><p>Part of why it was so unfulfilling was that I made sure half of my classes were easy to make sure my GPA was high. I thought the GPA and degree credential were super important. I realize now how stupid that was, yet the dominant thinking today hasn’t changed: the Credential is what matters.</p><p>Our education system burns a hole in our head from childhood until we graduate college that it is all about the credentials (the grade, the degree, etc). Pre-internet the credential was one of the more efficient ways to signal that you know something about a certain topic. This thinking is out of date for two big reasons:</p><ol><li>As Google itself has discovered, credentials have little to no correlation to being successful in a role and a highly productive professional. The company that was famous for hiring exclusively from the “Ivy Plus” has now removed it from their screening criteria.</li><li>The internet makes our actual work more transparent, easier for us to display, and easier for others to check out. There’s Github for developers, Medium, Slideshare (and other sites) for business people, Dribbble for designers, and so on.</li></ol><p>It is no longer about credentials. It is about creating good work and then finding a way to show it off (see Build A Platform section). Yet, instead of showing off work on LinkedIn I see professionals adding lists of certificates and credentials.</p><p>However, as an employer, I could care less that you took a course and passed some test. I want to see if you can actually apply it. Focus on accomplishments, not credentials.</p><h3>5. Build a Platform</h3><p>Each year for the past 7 years I’ve taken a couple days in December to reflect on the past year. One of the questions I ask myself is “What are the 20% of activities that led to 80% of value creation?” There is only one thing that has been on that list all 7 years. Writing on my blog.</p><p>Funny thing is that I don’t even write that often, yet it is still on the list every year. Every professional opportunity that I’ve had has come from my blog. I got my first job at ZoomInfo because my hiring manager read my blog. I got my first round of VC funding for Viximo because the VC’s knew me through my blog. I met the VC’s of Boundless through my blog. A huge reason I got hired at HubSpot was because of my blog. The only reason I’m in a position to start Reforge is once again because of my blog.</p><p>I’m not saying you must write a blog, but you should invest in building a platform for yourself <strong><em>that you own</em></strong>.</p><p>The platform could be a blog, speaking gigs, videos, images etc. Your platform gives you an opportunity to show off your hard work, creations, and thoughts (which is very different from showing off credentials).</p><p>By doing this, a few things happen:</p><ol><li><strong>Opportunities Flow To You</strong>. When you distribute your hard work, people take notice and the opportunities flow to you.</li><li><strong>You Create Leverage</strong>. Because opportunities flow to you, you end up gaining leverage. It is a much stronger position to be in the seat of being sold to versus being the one that is selling.</li><li><strong>You Build a Personal Brand</strong>. It is no secret that companies with strong brands hold a number of powerful advantages in their market. The same holds true when thinking about your personal brand.</li></ol><p>Everyone isn’t a great writer, but that doesn’t mean you can’t build a platform. The medium that fits you could be video, podcasts, visual portfolio site, presentations, speaking, or something else. The tools are out there to make any of these mediums easy (and it is getting easier) so you don’t really have any excuses.</p><h3>6. Get A Coach</h3><p>You’ve probably heard the a advice to get a coach 100 times, yet, so few do it.</p><p>The truth is, finding a great coach is incredibly difficult. It is something that you have to search for and work at for a long time. But when you find the right person, the relationship can last for years.</p><p>More important you need to understand what the value of a coach is. The biggest misconception is that you need a coach in order to do good work.</p><p>It’s actually the opposite — you do good work first, which gives you the opportunity to find a good coach.</p><p>I use the term coach vs mentor (or something else) on purpose. Any professional sports player’s coach can’t dribble the ball for them and make in game decisions. That is up to the player.</p><p>Similarly, a business or career coach doesn’t make decisions for you or provide the answers. Instead you want to find a coach that helps facilitate a better answer than one you would get to on your own.</p><p>That guidance takes two forms:</p><ol><li><strong>Unbiased Opinion</strong>. Everyone around you (family, friends, employees, co-founders, investors) have their own personal biases pulling you in different directions because they all have a personal stake in the outcome in some way shape or form. The value of a coach is someone who can offer an unbiased perspective because they don’t have a stake in the outcome.</li><li><strong>The Right Questions</strong>. Great questions lead to great answers. A great coach will ask you questions that you wouldn’t ask yourself. In the process helping you look at a problem in a different way or reveal some information you wouldn’t have otherwise.</li></ol><h3>7. Proactive vs Reactive</h3><p>If you do the above things, you will likely have a lot of opportunities that flow your way. This creates a new issue:<br>Reacting to things that come your way rather than being proactive about what you want.</p><p>Being reactive almost always creates sub-optimal outcomes. It is hard to say no or evaluate opportunities in an unbiased way if you don’t have some pre-set criteria or filter.</p><p>Being proactive rather than reactive is my usual advice, but as I’ve watched others try to put this into action I’ve noticed a couple of common issues. The proactive mindset forces you to ask yourself about what you really want. Understanding the answer to that question seems easy on the surface, but for many is actually pretty difficult.</p><p>The answer is simpler than we think. Like the other important problems / questions, “What do I really want?” is something you can’t think or theorize your way out of. You need to act.</p><p>So here’s my revised advice:</p><p>Rather than feeling like you need to think your way to a confident answer, <a href="http://www.coelevate.com/essays/growth-process-first-tactics-second">treat it like experiments</a>.</p><p>It breaks down into these steps:</p><ol><li>Think your way to a set of prioritized hypotheses of what you want</li><li>Design the experiment</li><li>Run the experiment</li><li>Analyze its results</li></ol><p>If the results are positive, keep going. If the results are bad, then stop and feed those learnings back into your next set of hypotheses in a series of iterations.</p><p>As we emphasize in <a href="http://reforge.com">Reforge</a> and on our own growth teams and players, learning growth marketing is also learning problem solving. The best “rules” aren’t shortcuts but a long term investment in integrating the principles of mastery into your career.</p><p>If you are interested in more content like this, check out my personal blog <a href="http://coelevate.com">Coelevate.com</a>.</p><p><strong>P.S. This is actually my first Medium post! I could use some ❤’s!</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fbaf3c9%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2Fbaf3c9%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/770f7a65b7c654ee54b52d898eba941b/href">https://medium.com/media/770f7a65b7c654ee54b52d898eba941b/href</a></iframe><p><em>Originally published at </em><a href="http://www.coelevate.com/essays/learn-growth-marketing"><em>www.coelevate.com</em></a><em> on October 12, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c69be5d55d54" width="1" height="1" alt=""><hr><p><a href="https://medium.com/buffer-stories/7-things-i-wish-i-knew-when-i-started-my-career-c69be5d55d54">7 Things I Wish I Knew When I Started My Career</a> was originally published in <a href="https://medium.com/buffer-stories">Buffer Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>