<?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 Claire Suellentrop on Medium]]></title>
        <description><![CDATA[Stories by Claire Suellentrop on Medium]]></description>
        <link>https://medium.com/@ClaireSuellentrop?source=rss-6583492c4ed2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ymFPwO72CZLkd_bwhQO9yA.jpeg</url>
            <title>Stories by Claire Suellentrop on Medium</title>
            <link>https://medium.com/@ClaireSuellentrop?source=rss-6583492c4ed2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 12:26:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ClaireSuellentrop/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[The JTBD Research Process We Used To Build Our MVP for Userlist.io]]></title>
            <link>https://medium.com/the-job-to-be-done/the-jtbd-research-process-we-used-to-build-our-mvp-for-userlist-io-e300025ab487?source=rss-6583492c4ed2------2</link>
            <guid isPermaLink="false">https://medium.com/p/e300025ab487</guid>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[jobs-to-be-done]]></category>
            <category><![CDATA[finding-jobs-to-be-done]]></category>
            <category><![CDATA[jtbd]]></category>
            <dc:creator><![CDATA[Claire Suellentrop]]></dc:creator>
            <pubDate>Fri, 27 Apr 2018 13:25:57 GMT</pubDate>
            <atom:updated>2018-10-02T14:30:29.646Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*dnHiyuadBCBfjLwb.png" /></figure><p>When <a href="https://twitter.com/uibreakfast">Jane Portman</a>, <a href="https://twitter.com/benediktdeicke">Benedikt Deicke</a> and I <a href="http://userlist.io/why-another-tool-for-saas-founders/?utm_source=jtbd-info&amp;utm_medium=organic&amp;utm_campaign=organic-promo">decided to join forces</a> on Userlist.io, none of us wanted to start a company based on our personal experiences alone.</p><p>We’d each strongly felt the pains of trying to observe users’ behavior within a SaaS product, and communicate with those users at scale based on their individual behaviors. And we were excited at the prospect of building a <strong>combined user admin panel + communication tool</strong> to solve those pain points for other founders.</p><p>But we <em>weren’t</em> interested in joining the thousands of founders before us who’ve launched a product to scratch their own itch… and no one else’s.</p><p>So before Jane designed a single piece of our UI, and before Benedikt wrote a single line of code, I went into research mode to understand whether other self-funded founders experience the problems Jane and Benedikt faced when building their previous product.</p><p><strong>Here’s the 4-step process I used to gather the data, distill the important insights, and turn our findings into an MVP:</strong></p><ol><li>Define our ideal customer</li><li>Conduct interviews to understand existing struggles</li><li>Organize interview transcripts to find insights</li><li>Build, test, learn</li></ol><p><em>This article </em><a href="https://userlist.io/customer-research-process?utm_source=jtbd-info&amp;utm_medium=organic&amp;utm_campaign=organic-promo"><em>originally appeared</em></a><em> on Userlist.io.</em></p><h3>Step 1. Define our ideal customers</h3><p>Defining your <em>ideal</em> customer means getting much more specific than saying you serve “SMBs” or “founders.” If you’re B2B, what company model does your ideal customer own or work in? What industry or niche? How mature is their business? Is it profitable? Well-funded? Lean? Rapidly expanding? What challenges do they face in doing their work well (or better)?</p><p>For us, defining our ideal customer was relatively easy, since Jane and Benedikt are already active members of the community they wanted to serve — and I have several friends who fit the mold, as well.</p><p>We knew we wanted to focus on founders of small-to-medium SaaS companies:</p><ul><li>…who are self-funded;</li><li>…who are running their company completely solo;</li><li>…or whose teams are small, and probably wearing many hats</li></ul><p>My goal was to get at least 20 phone calls booked with folks who fit these criteria, and to conduct at least 10–15 actual calls. Booking at least 20 would help account for people who had technical difficulties, or had to cancel last minute.</p><p>While it would’ve been lovely to speak with 50 or even 100 ideal customers at this stage, our goal was to get just enough information to work with — those key details that would help us release an MVP, after which we could iterate and improve.</p><p>To my great appreciation, Jane and Benedikt sourced the majority of interviewees — mostly through their personal networks, Slack groups, and Twitter (a huge benefit of building a product for an audience you already know and interact with).</p><p>I set up a Calendly event called “Userlist.io Call,” shared that link with Jane and Benedikt, and watched as the calls rolled into my calendar. All in all, I ended up with 16 calls booked, and 12 actually held (after accounting for cancellations). Not bad!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IQgy39vsky_4UdKe.png" /><figcaption>My calendar, full of research calls for Userlist.io.</figcaption></figure><h3>Step 2. Conduct interviews to identify existing struggles</h3><p>With 16 calls on the calendar, it was time to assemble some interview questions.</p><p><strong>What’s important: the questions I chose for these interviews were slightly different than the questions I’d use when speaking with paying customers of an existing product.</strong></p><p>The goal of these interviews <em>wasn’t</em> to decide on specific features to build, or even to get feedback on our idea. Instead, the goal was simply to understand:</p><ol><li>What pains exist in our ideal customer’s day</li><li>What causes those pains</li><li>How those pains are currently solved… (or if they are solved at all)</li></ol><p>Gaining this understanding would pull us out of the weeds of the problem we’d identified from our experience, and help us see more clearly whether it was the right problem to pursue, or whether a much bigger problem existed that was worth tackling.</p><p>This approach was, of course, based on Jobs To Be Done.</p><p>Since Userlist.io is a combined user admin panel + communication tool (for observing user behavior, then communicating at scale based on that behavior), I needed to understand:</p><ul><li>How do our ideal customers currently organize, observe, and leverage their users’ behavioral data?</li><li>How do they communicate with users at scale, based on users’ behavior?</li><li>Are their existing solutions perfectly fine? Or…</li><li>Did we indeed have an opportunity to solve a pain point?</li></ul><p>So I had to take each interviewee back in time, to the moments they made decisions about how they would accomplish these tasks.</p><p>Apart from confirming that interviewees met our ideal customer criteria (self-funded, running their company solo, or working with a very small team), we did very little pre-qualifying. <strong>Our goal was to hear from founders at many different stages of company growth: problem-solution fit, product-market fit, growth, and scale.</strong></p><p>At the end of the process, our interviewees all fell into one of those first three stages: problem-solution fit, product-market fit, or growth. So…how were these founders observing their users’ behavior, and communicating with those users?</p><p>For the most part, the founders I spoke with were custom-building a user admin panel, which (of course) didn’t integrate with any communication tool directly. So to communicate with their users at scale, those founders had the following options available…</p><ul><li>Push user data from their product into a service like Drip or Intercom</li><li>Send custom emails with something like Postmark or Sendgrid</li><li>Manually keep track of new user signups, trial endings, etc., and send batch-send emails through their personal address every morning or evening (which sounds terrible)</li></ul><p>Let’s say I was on a call with someone using a custom-built user admin panel plus Intercom.</p><p><strong>Here are some of the research questions I’d ask:</strong></p><ul><li>“Let’s go back to the point in time when you were working on your product, and you chose Intercom. Tell me about that.”</li><li>“Did you consider any other solutions? Which ones?”</li><li>“Okay, so you considered MailChimp and Drip. What happened that made you decide <em>not</em> to use MailChimp or Drip?”</li><li>“What happened that eventually made you say, ‘Okay, Intercom is going to work for us’?”</li><li>“Now that you’re in Intercom, what is working well? What are the pros?”</li><li>“What’s still really painful at this point?”</li><li>“Are there new problems that have popped up, or are there some problems that you thought Intercom was going to solve that it never actually solved for you? What are those?”</li></ul><p><strong><em>** By the way: </em></strong>Want the entire list of questions I used to run these customer interviews? <a href="https://www.getdrip.com/forms/690487994/submissions/new"><strong>Get all my interview questions + a spreadsheet template to organize your data.</strong></a><strong> **</strong></p><p>Essentially, I was trying to create <em>a mental timeline</em> of our ideal customers’ decision-making process:</p><ul><li>What events or situations led up to the problem we want to solve?</li><li>How do people decide to solve that problem right now?</li><li>What’s still not working about existing solutions?</li></ul><p>Based on interviewees’ emotional reactions to their current ways of observing and communicating with users, it was clear we were on to <em>something</em>.</p><p><strong>Here are just a few of the ways founders described the problems with their existing solutions:</strong></p><blockquote>“The problem with every custom built system is that every time you need to tweak something, you’re too lazy to go actually code something to make a change. You have no time for that.”</blockquote><blockquote>“When you start out as a bootstrapped founder…at least, when I did…I didn’t know how to get enough user data to understand how people were really using the product, and what features I still needed to build to get to product-market fit. There’s this concept of a ‘minimum path to awesome,’ but how do you figure out what that path is, when you’re in the really early days and you don’t have very many customers?”</blockquote><blockquote>“For my last product, all my emails were custom and they’d go through Mandrill. I definitely don’t want to do that for this new product, because it’s not efficient to code emails, and there’s no way to keep track of them or see how they performs.”</blockquote><blockquote>“What I love about Intercom is the user dashboard. It’s like an admin panel, and one thing that’s painful about having your own product is that you need to have that admin panel. But Intercom’s dashboard is too limited. Intercom is a generalist, so all their different features are just…okay. They’re not really strong in any one category.”</blockquote><p>I recorded every call, which allowed me to give each interviewee my full attention, and then uploaded each recording to Rev.com. In 24 hours or less, I’d have the transcript back — and with 12 calls complete, I was ready to settle in for a month of deep data review.</p><h3>Step 3. Organize raw transcripts into meaningful data</h3><p>Based on the conversations held with these 12 founders (plus one <a href="https://soundcloud.com/user-539369312/asasw1">audio rant</a> Amy Hoy recorded and published, which happened to be extremely timely and relevant to us), we could’ve started building our MVP with 25 different features. Different people needed different things, at all different levels of urgency.</p><p>So, how did we figure out what mattered most?</p><p>By distilling dozens of pages of qualitative data into… a very unsexy spreadsheet. Below are the three questions I used to organize our data.</p><h4>Question 1. Are enough people motivated to solve this pain? Or is there a stronger pain somewhere else?</h4><p>The first step was to make a list of all the various pain points interviewees had shared during calls. My goal was to identify which pain points interviewees were <em>most often </em>motivated to solve, and which pain points could be excluded as edge cases.</p><p>Here are just a few motivations our ideal customers felt, color coded by which came up most frequently during interviews (dark red = came up most often, dark blue = came up least often):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/0*K9z71z5rQr3w0mIJ.png" /><figcaption>A few motivations our ideal customers felt, color coded by which came up most frequently during interviews (dark red = came up most often, dark blue = came up least often)</figcaption></figure><p>As you can see, many interviewees wanted to improve how well they guided users through their product — which validated that the pain point Jane, Benedikt and I are trying to solve is real, and commonly felt by our ideal customers.</p><p>While the blue problems are no less legitimate (or important to a successful business) than the dark red, relatively few founders in our sample size were as concerned about the blue problems as they were about the red.</p><p>With validation that the pain point we’re trying to solve — <em>“I want to nudge users to use the product in a way that makes them successful”</em> — is real and widely-felt, we could safely narrow our focus to just this pain point, and ignore the others for now.</p><p>Now, I was ready to figure out:</p><ul><li>What events / situations most often trigger this pain?</li><li>What’s the “better life” founders envision for themselves as they try various solutions?</li></ul><h4>Question 2. What common events or situations trigger this pain point?</h4><p>Next, we needed to figure out which events or situations were occurring in founders’ workflows, that most frequently <em>cause</em> this pain point to arise. This would help us understand what events along a founder’s journey would most likely trigger that founder to seek out (and adopt) a new solution.</p><p>Remember: during my interviews with founders, I was trying to create a mental timeline of each founder’s decision-process. So I reviewed the transcripts in which our chosen pain point came up frequently, and looked for patterns in those founders’ stories.</p><p><strong>Some of the common situations that pushed founders to worry about properly communicating with their users:</strong></p><ul><li>Trying to quickly ship an MVP, and reserving all possible time/energy for building core product features (as opposed to spending time on “extracurricular” marketing and communication)</li><li>Trying to implement an analytics tool to understand user behavior, but getting overwhelmed by the process, not knowing what to measure, or having insufficient data to understand which user behaviors lead to subscriptions vs. which lead to churn</li><li>Wanting to switch from time-triggered customer communication to event-triggered communication</li><li>Wanting to send product updates, but only to a certain segment of users (those who would care the most)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kcE1iUadv0vWncvj.png" /><figcaption>Red: situations that cause founders pain (“struggling moments”). Orange: motivating factors pushing founders to seek a new solution. Green: desired outcome, and existing solutions for achieving that outcome.</figcaption></figure><p><strong>Some key learnings we took away from this:</strong></p><ol><li>If we get our product on founders’ radar while they’re still in ideation phase, before they’ve begun building their product, we could save people TONS of time/effort — which many of them are currently spending building admin panels by hand</li><li>If we provide foundational analytics about user behavior, founders may never need to bother with bulky analytics tools designed for much larger, mature companies. On the other hand, if they’re already a power-user of a tool like KISSmetrics or Mixpanel, they may not be a fit for Userlist.io.</li><li>Even founders who de-prioritize user communication in the early days of their product (e.g. in favor of concierge onboarding) will eventually want to optimize the messages they send to users. If we can help a founder publish their first basic time-based onboarding email, then collect user data in the background for a while, that founder will have everything they need to send super-effective event-based emails down the road.</li></ol><p><strong>This was helpful not just for early product development, but from a marketing and overall business perspective, as well.</strong></p><p>For example, we know we’ll need to make founders aware of Userlist.io extremely early on in their product-building journey — otherwise, we could miss the boat, and they’ll become too comfortable with a homegrown user admin panel + other email solution… and both of these require lots of effort to migrate away from.</p><p>With these learnings in mind, we were ready to examine the existing solutions founders use in these situations.</p><p><em>**Sidenote. Some of the founders I interviewed expressed </em><strong><em>no</em></strong><em> pain points related to building their own user admin panel, and actually preferred to build as much as possible by hand — including emails, analytics tools, etc. We chose to exclude data from interviews with these founders, intentionally creating a sampling bias.</em></p><p><em>While we recognize some founders may never see the value of a done-for-you tool, we believe — based on the quantity of founders who </em><strong><em>did</em></strong><em> want to avoid hand-coding everything — that a healthy percentage will!</em></p><h4>Question 3. What existing solutions do we not want to compete with?</h4><p>We know the customer communication space is a large one, and believe many competitive solutions can co-exist. However, we wanted to avoid going up directly against the clearly incumbent products that it would be most difficult to pull users away from.</p><p>That meant analyzing the feature sets of solutions founders currently use, figuring out what founders love and hate about those solutions, and being <em>extremely</em> selective about which features our MVP would include.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/869/0*VJPMFLiv3oWJr3PX.jpg" /><figcaption>Frustrations our ideal customers feel with custom-coding emails to users.</figcaption></figure><p>Ultimately, we decided <em>not</em> to focus on…</p><ul><li><em>Pre-signup marketing communications.</em> With umpteen email marketing tools already available, we’re not interested in building yet another way for people to capture leads outside of their products, and nurture those leads into trials.However, many founders currently force pre-signup marketing tools (e.g., Mailchimp, Drip) into their users’ post-signup experience, with much frustration — and we’re very interested in solving that problem.</li><li><em>Robust analytics.</em> There’s no way we can (or want to) compete with powerful analytic tools like KISSmetrics, Mixpanel, or FullStory. Our ultimate goal is to create a tool that sends relevant messages well, so our analytics features will most likely be “necessary and sufficient” to provide quality event triggers.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/869/0*or9LOiimsPZs-dZT.jpg" /><figcaption>Frustrations our ideal customers feel with existing analytics tools.</figcaption></figure><p><strong><em>** By the way: </em></strong>Want a copy of this spreadsheet I used to sort our customer data? <a href="https://www.getdrip.com/forms/690487994/submissions/new"><strong>Get all my interview questions + this spreadsheet template above to organize your data.</strong></a><strong> **</strong></p><h3>Step 4. Build, test &amp; learn</h3><p>We’re extremely close to launching our MVP, and we can’t wait to invite folks in. Feedback from our first users will help us validate — or rethink — whether Userlist.io has the right mix of core features to truly deliver value.</p><p>Even at this early stage, though, we’re hopeful that our focus on founders’ most common situations, struggles, and motivations leads to a product that makes self-funding a SaaS company 10x easier.</p><h3>Get your free research templates</h3><p>Want a copy of the interview questions &amp; spreadsheet template I used for Userlist.io’s customer research? <a href="https://www.getdrip.com/forms/690487994/submissions/new"><strong>Get both here.</strong></a></p><p><a href="https://twitter.com/clairesuellen"><em>Claire Suellentrop</em></a><em> is the co-founder + head of marketing at </em><a href="http://userlist.io/"><em>Userlist.io</em></a><em>, alongside Jane Portman and Benedikt Deicke. Previously, consulted on customer insights and marketing for Wistia, MeetEdgar, Death to the Stock Photo, and many other fun SaaS companies.</em></p><p><em>Before jumping into the world of consulting and co-founding, Claire was Director of Marketing and #2 employee at Calendly.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e300025ab487" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-job-to-be-done/the-jtbd-research-process-we-used-to-build-our-mvp-for-userlist-io-e300025ab487">The JTBD Research Process We Used To Build Our MVP for Userlist.io</a> was originally published in <a href="https://medium.com/the-job-to-be-done">Jobs to be Done</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Gain Influence as a Marketer at a Tech Company]]></title>
            <link>https://medium.com/forgetthefunnel/how-to-gain-influence-as-a-marketer-at-a-tech-company-a0f8a66dc6ad?source=rss-6583492c4ed2------2</link>
            <guid isPermaLink="false">https://medium.com/p/a0f8a66dc6ad</guid>
            <category><![CDATA[saas-marketing]]></category>
            <category><![CDATA[marketers]]></category>
            <category><![CDATA[professional-development]]></category>
            <category><![CDATA[mentorship]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Claire Suellentrop]]></dc:creator>
            <pubDate>Thu, 15 Mar 2018 10:31:01 GMT</pubDate>
            <atom:updated>2018-03-15T10:56:21.273Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This article was co-authored by </em><a href="https://twitter.com/ClaireSuellen"><em>Claire Suellentrop</em></a><em> and </em><a href="https://twitter.com/ggiiaa"><em>Georgiana Laudi</em></a><em>. It originally appeared on the </em><a href="http://news.codecademy.com/marketer-at-tech-company/"><em>Codecademy Blog</em></a><em>.</em></p><p>It’s no secret: being a “non-technical” team member at a tech company is tough. You may struggle to establish good rapport with your Head of Product, your projects may be treated with less urgency than the dev team’s, or you may feel like you’re constantly working under a microscope.</p><p>As the first marketers hired at two tech companies ourselves, we’ve experienced each of these challenges in our own careers. The good news, though? Things <em>can</em> improve from here. You <em>do</em> have the power to build trust with your technical coworkers, shed that “non-technical” label, and gain influence in your role as a marketing leader.</p><p>After years of building relationships with technical teams, figuring out executives’ priorities, making the case for marketing projects, and negotiating resources &amp; budget, we’ve learned some of the most surefire ways marketers at tech companies can build trust with their technical co-workers.</p><p><strong>What follows is the advice we wish <em>we’d</em> had during our early days in tech</strong>: a collection of tactics to help you demonstrate your value, prove you’re thinking strategically, and ultimately, get better results at work.</p><p>If you need help mastering these tactics, <strong>we run a </strong><a href="https://forgetthefunnel.com/workshops/?utm_source=medium&amp;utm_medium=blog-post&amp;utm_campaign=influence"><strong>free, weekly series of workshops</strong></a><strong> to help marketers at tech companies level up and be more effective at work.</strong> We’d love to see you at the next one!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WYxxdhGfXL0sFkZVAlh3NA.png" /></figure><h3>Shift your mindset from “employee” to “essential”</h3><p>As a marketing leader, your very first step toward gaining influence is to remember that <strong>marketing is integral to the success of any tech company</strong>. If you’re the owner of marketing within your organization (Director, Manager, Lead, etc), know that you’re <em>much</em> more than just a cog in the wheel.</p><p>Long gone are the days of marketing being the <a href="http://chiefmartec.com/2012/11/moving-marketing-beyond-the-arts-and-crafts-department-interview/">“arts and crafts” department</a>; <strong>your real goal is to generate revenue</strong> — and revenue is the lifeblood of the company!</p><p>Keep this top of mind, and instead of waiting passively for your CEO or your manager to hand you an assignment, get proactive. Start thinking about what marketing can do to make a positive impact on key company metrics like leads generated, prospects qualified, or new customers acquired (more on company metrics in a bit).</p><p>Once you start to see your role as essential to the success of the business, your tasks become purposeful (or culled, if you realize your projects aren’t contributing to revenue). This shows other department leaders that you’re thinking about the big picture.</p><h3>Earn your CEO’s trust</h3><p>Your CEO can be your biggest champion — or your biggest blocker. As the person ultimately responsible for representing the company, the CEO of any tech company ultimately owns marketing. When your CEO trusts that you’re thinking strategically and acting with the best interest of the business in mind, she’s more likely to champion your ideas, remove roadblocks, and vouch for you when other team members struggle to see the value of your projects.</p><p>So, how do you gain your CEO’s trust? How do you establish yourself as an equal with folks at the executive level?</p><p>Ultimately, trust comes down to a little truth that we all know as marketers already: humans care about themselves and their own struggles more than anything else. So, <strong>if you can understand your boss’s struggles , you can run your department in a way that’s <em>relevant</em> to your boss.</strong></p><p>How do you learn what your boss cares about? Ask! At your next 1:1 meeting, try getting (just a bit) personal before or after you’ve shared your regular updates, and ask how your boss is doing.</p><p>A great question to start with is “What’s going well right now, and what are you most worried about these days?” They probably won’t pour their heart out right away, especially if you haven’t already established a pattern of discussing personal wins and worries. But gradually, your boss is likely to open up, giving you more visibility into their work — empowering you to plan marketing projects that impact the things your CEO cares about.</p><p>And <strong>once you begin to understand what issues your CEO cares about, you can begin to identify the <em>business metrics</em> most related to her priorities.</strong></p><p>For example, if your CEO’s primary concern right now is getting enough customers in the door every month, the related metric would be <em>Net New MRR </em>(MRR = monthly recurring revenue). On the other hand, if your CEO’s biggest worry is that key customers aren’t sticking around very long, the related metrics would be <em>retention rate</em> and <em>churn rate.</em> (Need help getting familiar with common tech company metrics? We recommend <a href="http://www.forentrepreneurs.com/saas-metrics-2/">David Skok’s SaaS Metrics Guide</a> or <a href="https://chartmogul.com/resources/saas-metrics-cheat-sheet/">ChartMogul’s SaaS Metrics Cheatsheet</a>.)</p><p>With an understanding of which metrics matter most to the business, you can begin identifying areas where marketing can make a direct impact on those metrics.</p><h3>Get (at least a little) technical</h3><p>To some degree, <em>all</em> online marketers are technical marketers; after all, you’re creating demand for a technical product, and the key to good marketing is deeply understanding <em>what</em> it is you’re marketing in the first place.</p><p>With that said, being successful doesn’t necessarily mean knowing the complex ins and outs of your product’s code. It just means being able to speak the basic language of your engineers.</p><p>For this reason, we recommend getting familiar with foundational aspects of development that will save you time in the long run — like deciphering HTML, or learning SQL so you can dive into customer data by yourself (instead of having to wait around for an engineer to help you).</p><p><strong>Understanding analytics is also crucial to gaining influence as a marketer.</strong> In a recent Forget The Funnel workshop called “<a href="https://forgetthefunnel.com/create-saas-content-that-wont-kill-you/?utm_source=medium&amp;utm_medium=blog-post&amp;utm_campaign=influence">How to Create Content That Won’t Kill You</a>,” Codecademy’s Content Strategist Ashley Hockney shared this golden piece of advice:</p><p><em>“</em><strong><em>The data-driven get paid.</em></strong><em> If you can analyze your content week over week, track your Google Analytics, track your growth via Twitter, track which of your inbound channels is generating the most leads, and — even better — which is generating the most product signups, you have numbers to back up your decisions.”</em></p><h3>Hold regular one-on-ones with department heads</h3><p>As a marketing lead,<strong> it’s part of your job to keep up with the current needs and projects of other departments</strong> — and the best way to do this is by holding regular weekly (or at least biweekly) 1:1 meetings with fellow department leaders.</p><p>Holding 1:1’s helps you better understand what your technical, sales, and support teams are working on right now, or struggling with lately. And having that context gives you the opportunity to plan marketing projects that help support other departments’ efforts, or relieve their struggles — which positions you as a thoughtful, empathetic colleague, and the marketing department as a valuable asset to the company.</p><p>Of course, no one appreciates meetings that feel like time-wasters — so to ensure you and your colleagues each get value, keep the purpose of your 1:1s straightforward:</p><ul><li>Update each other on important things that’ve happened since you last met</li><li>Review important things launching or starting in the next two weeks</li><li>Schedule quick times in the coming days to connect with other project stakeholders, to address issues / remove roadblocks where needed</li></ul><p>As John Doherty (CEO, Credo) <a href="https://www.getcredo.com/cmo-ways-communication-open-nonmarketing-teams/">says</a>: “don’t think about this meeting as a time to build rapport with others at your same level. You should be doing that at after-work happy hours, lunches, or other times. <strong>This meeting is all about business.</strong>”</p><h3>Tie every project to business value</h3><p>When you tie marketing projects to the goals of your business, you prove to the technical team and C-suite that marketing is a revenue-generating department. For this reason, <strong>connecting your projects to relevant business metrics should be an ongoing habit</strong> when communicating with teams across the company.</p><p><strong>One of the best tools you can use to demonstrate any project’s value is a</strong> <strong>marketing brief:</strong> in other words, a short description of your project, an estimate of the time and resources required to execute on it, and the results (numbers!) you expect it to produce.</p><p><strong>Writing a marketing brief to pitch a project can make all the difference between acceptance or rejection</strong>, between getting buy-in or getting skeptical side-eyes.</p><p>When preparing a brief, you want to accomplish four critical points:</p><ul><li>Explain the purpose / strategy behind the project — why <em>this</em> project? Why now?</li><li>Outline the measurements that will determine success</li><li>Identify the target audience, and the expected outcomes</li><li>Establish clear goals, timelines, and responsible parties</li></ul><p>Need a marketing brief template to help you get started? <a href="https://docs.google.com/document/u/1/d/1oPGF4mZmvgZYKTHUuHAhmWhFwDvny2VuiqzfIOaq2Es/edit?usp=sharing">You can make a copy of ours here</a>.</p><h3>Know your customers better than anyone</h3><p>Conducting customer research can make a <em>huge</em> difference in your work. Customer surveys, website analytics, product usage, customer and user interviews, and target market interviews — <strong>all of these help you become the internal expert on your customer</strong>. This not only makes you a stronger marketer who can plan and launch more relevant campaigns; <strong>it also makes you an indispensable resource to the other departments</strong> — all of which <em>need</em> that valuable customer data, but don’t have the bandwidth to collect it themselves.</p><p>If conducting customer research is a completely new topic for you, <a href="https://forgetthefunnel.com/mvp-saas-value-propositions/?utm_source=medium&amp;utm_medium=blog-post&amp;utm_campaign=influence">this workshop</a> will show you one quick way to get started. But <em>collecting</em> the data is just step one; <em>sharing</em> what you’ve gathered with your technical team is the extra step that sets you apart as an indispensable resource.</p><p>After you’ve done the work, the chances of your colleagues taking the time to sort through a big, messy pile of data are pretty low. So <strong>package up what you’ve learned, and present your findings over a short lunch-and-learn to make them digestible for other people on the team</strong>. This is the step that will elevate you from secret encyclopedia, to resident customer expert whose input is valued in strategic meetings.</p><h3>Get familiar with the product roadmap</h3><p>From minor bug fixes to major new features, <strong>understanding what product updates your dev team has planned is essential context</strong> when building your marketing strategy.</p><p>Whenever we say this, though, we add “don’t laugh!” to the end — because for some marketers, gaining access to the dev team’s product roadmap can feel like a huge first battle.</p><p>Marketers who <em>do</em> have visibility into the product roadmap <em>still</em> often wind up frustrated, as deadlines and launch dates constantly shift, seemingly without warning (another bonus of regular 1:1s with your Head of Product: avoiding these unpleasant plot twists).</p><p>However, even <strong>getting a loose delivery timeline from your CTO will spare you from having to throw together a campaign last-minute</strong> — or worse, spending three months developing a big project, then having to scrap it entirely when you find out a drastic product update will render your work irrelevant.</p><h3>There’s hope (and help!)</h3><p>Sometimes, it can feel like marketing at a tech company is a never-ending battle to learn more — or of constantly trying to catch up. The reality is that it’s probably a mix of both, but you can gain more influence and make a bigger impact by building trust with your c-suite and technical coworkers. <strong>That means tying your work to business value, getting (at least a little) technical yourself, and nurturing ongoing communication with other departments.</strong></p><p>If you need help mastering these tactics, we run a free, <a href="https://forgetthefunnel.com/workshops/?utm_source=medium&amp;utm_medium=blog-post&amp;utm_campaign=influence">weekly series of workshops for marketers</a> at tech companies. Our goal is to help you get out of the weeds, think strategically, and be more effective at work.</p><p>We’d love to see you at our next workshop. And, when you <a href="https://forgetthefunnel.com/workshops/?utm_source=medium&amp;utm_medium=blog-post&amp;utm_campaign=influence">reserve your spot</a>, <strong>we’ll send you all the recordings from our first season</strong> (18 workshops total!) right away, no waiting.</p><p><a href="https://twitter.com/ClaireSuellen"><em>Claire Suellentrop</em></a><em> and </em><a href="https://twitter.com/ggiiaa"><em>Georgiana Laudi</em></a><em> address the unique struggles of SaaS marketers, based on their firsthand experience building brands (pretty much from scratch) as the Director of Marketing at Calendly and VP of Marketing at Unbounce.</em></p><p><a href="https://forgetthefunnel.com/workshops/?utm_source=medium&amp;utm_medium=blog-post&amp;utm_campaign=influence"><strong><em>Forget The Funnel</em></strong></a><em> is a series of free weekly workshops for SaaS marketers, on topics like gaining C-Suite trust, thinking strategically, and getting buy-in when pitching new marketing experiments.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a0f8a66dc6ad" width="1" height="1" alt=""><hr><p><a href="https://medium.com/forgetthefunnel/how-to-gain-influence-as-a-marketer-at-a-tech-company-a0f8a66dc6ad">How to Gain Influence as a Marketer at a Tech Company</a> was originally published in <a href="https://medium.com/forgetthefunnel">Forget The Funnel</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>