<?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 Ryan Riggin on Medium]]></title>
        <description><![CDATA[Stories by Ryan Riggin on Medium]]></description>
        <link>https://medium.com/@ryanriggin?source=rss-bc2457e819c7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*WCqm3lmXwHf4kmoA.jpg</url>
            <title>Stories by Ryan Riggin on Medium</title>
            <link>https://medium.com/@ryanriggin?source=rss-bc2457e819c7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 03:08:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ryanriggin/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[System of Beliefs]]></title>
            <link>https://medium.com/@ryanriggin/system-of-beliefs-b8172d3ac2a6?source=rss-bc2457e819c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/b8172d3ac2a6</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[habits]]></category>
            <dc:creator><![CDATA[Ryan Riggin]]></dc:creator>
            <pubDate>Tue, 06 Nov 2018 15:15:16 GMT</pubDate>
            <atom:updated>2018-11-06T15:18:32.002Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nc7Ne-23MOiChB-QJo_Kxw.jpeg" /></figure><p>In one of his recent emails <a href="https://medium.com/u/f644ebba8f33">noah kagan</a> recommended this book called <a href="https://jamesclear.com/atomic-habits">Atomic Habits</a> by <a href="https://medium.com/u/528e9a6004d8">James Clear</a></p><p>In the book, the author talks about three levels of change.</p><ul><li>Outcome Based (goals)</li><li>Process Based (systems)</li><li>Identity Based (beliefs)</li></ul><p>For the last few years I’ve written my goals on a big whiteboard. Things like:</p><ul><li>build a 7 figure revenue agency</li><li>spend more time with my family</li><li>build or acquire a SaaS product or E-commerce business</li><li>ride 4000 miles on the bike</li><li>run a half marathon</li><li>20% growth in investment portfolio</li><li>read 15 books</li><li>build an email list of 100,000 subscribers</li><li>write a book</li><li>do a podcast</li><li>learn to play the electric guitar</li></ul><p>The list goes on.</p><p>Some I’ve achieved.</p><p>Some I’m close.</p><p>Some are not even on the radar.</p><p>What I’m realizing while reading this book is that all of these things are Outcomes.</p><p>I need to shift that thinking, and get focused on <em>Process Based Habits</em>. The Process that will lead me to those outcomes.</p><p><strong>Process</strong></p><p>Things like:</p><ul><li>write 500 words every day before 8am</li><li>read for 1 hour before bed instead of watching TV</li><li>ride 25 miles a day on the bike</li><li>spend at least a hour a day with my family device free</li></ul><p>Behind every outcome will be a process.</p><p>Behind every process is someone who <em>identifies</em> themselves as a person who can execute that process.</p><p><strong>Identity</strong></p><p>Athletes exercise daily</p><p>Business Operators focus meticulously on their daily business metrics</p><p>Writers write every day</p><p>Fathers spend device-free time with their family daily</p><p>Readers read daily instead of watching TV.</p><p>Creators create things. Not consume them.</p><p>In order to build a process I need to think about my identity. I need to build what the author calls a “System of Beliefs” about who I am and what what I’m capable of. Not until then will I be able to build a process to achieve the outcomes.</p><p>I should be thinking:</p><ul><li>I am a successful agency operator</li><li>I am a father</li><li>I am a cyclist</li><li>I am a guitar player</li><li>I am a reader</li><li>I am a writer</li><li>I am a creator</li><li>I am an investor</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8172d3ac2a6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What should I optimize for?]]></title>
            <link>https://medium.com/@ryanriggin/what-should-i-optimize-for-71b7833e98c?source=rss-bc2457e819c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/71b7833e98c</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[mixpanel]]></category>
            <category><![CDATA[event-tracking]]></category>
            <category><![CDATA[growth-hacking]]></category>
            <dc:creator><![CDATA[Ryan Riggin]]></dc:creator>
            <pubDate>Thu, 01 Nov 2018 20:10:25 GMT</pubDate>
            <atom:updated>2018-11-01T20:19:37.786Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lwrUstqWZzcaXjb6d-2tNQ.png" /></figure><p>Engagement?</p><p>Retention?</p><p>Clicks?</p><p>Pageviews?</p><p>Conversions?</p><p>Leads?</p><p>I don’t think any of these words mean anything. If I’m trying to grow a product I’m optimizing for ‘events.’ Everything is an event. I want my users / customers to accomplish events.</p><p>At the top of the funnel, in the audience development stage (independent of the business model)..I want to see these events happening.</p><p>‘Like My Page’</p><p>‘Watch a Video’</p><p>’Share a Video’</p><p>‘Comment on a post’</p><p>All of the following could be categorized as ‘engagement.’ The problem is ‘engagement’ isn’t a specific marketing goal. If you can get users to successfully complete these events, then you may have an audience. But not a business model.</p><p>To get to a a business model you need to go further down the event funnel.</p><h3><strong>Example:</strong></h3><p><strong>E-Commerce:</strong></p><p>If I’m an e-commerce brand. I want my users to complete the following events.</p><ul><li>View my site</li><li>View a product</li><li>Sign up for my email list</li><li>View the size chart</li><li>Add a product to cart</li><li>Initiate a Checkout</li><li>Purchase</li><li>Purchase</li><li>Purchase</li><li>Purchase</li></ul><p><strong>SaaS — FREE TRIAL:</strong></p><p>If I’m a SaaS Free Trial product. I want my users to complete these events:</p><ul><li>View my site</li><li>Start a trial</li><li>Get Billed</li><li>Get Billed Again</li><li>Get Billed Again</li><li>Get Billed Again</li></ul><p>I want my users to NOT complete these events.</p><ul><li>Cancel Account.</li></ul><p><strong>SaaS — Freemium:</strong></p><p>This one is tricky. The events you want to optimize for I think are:</p><ul><li>Visit Website</li><li>Sign Up</li><li>DoSomething (this is different for every freemium product. but you want users to accomplish some event that makes them see the value of your product)</li></ul><p>It could be</p><ul><li>dropbox (upload a file)</li><li>record a podcast (anchor)</li><li>create a note (evernote)</li><li>upload a photo (instagram)</li><li>watch a video (youtube)</li><li>get a ride (uber)</li></ul><p>This is where ‘retention’ comes in. If your product depends on users doing some behavior over an over again until they realize value, then you want to focus on retention. But, ‘retention’ isn’t really a thing on its own. Retention is a user doing some ‘event’ over and over again.</p><p>see this talk from Evernote CEO on how they optimized for ’created notes,’ focuses on getting people to do that a lot, and how they stacked user cohorts with that one objective. <a href="https://vimeo.com/11932184">https://vimeo.com/11932184</a></p><p>Once you have users accomplishing ‘events’ that show them value repeatedly (retention)….</p><p>Then get them to:</p><ul><li>Upgrade to a paid account</li><li>Get Billed</li><li>Get Billed Again</li><li>Get Billed Again</li><li>Get Billed Again</li></ul><p>Then it gets really fun. Once you have users doing these events. Then, you can incentivize them from within your product to:</p><ul><li>invite a friend</li><li>share referral codes</li><li>add users to their account</li></ul><p>And other growth events.</p><p>In summary:</p><p>When you’re trying to grow a product. Figure out your model and think about your marketing optimization terms of ‘events.’</p><p>Then test the hell out of your Ads and UX to optimize for whatever those events are.</p><p>How do I track it all?</p><p>Mixpanel: &gt;&gt;&gt; www.mixpanel.com</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71b7833e98c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learning to Communicate as a Remote First Digital Agency.]]></title>
            <link>https://medium.com/@ryanriggin/learning-to-communicate-as-a-remote-first-digital-agency-c7bd4d2b5c7c?source=rss-bc2457e819c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/c7bd4d2b5c7c</guid>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[digital-agency]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[communication]]></category>
            <dc:creator><![CDATA[Ryan Riggin]]></dc:creator>
            <pubDate>Mon, 08 Oct 2018 18:06:00 GMT</pubDate>
            <atom:updated>2020-06-18T00:18:29.675Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y3hSDA3E8ezUkeHDdZiWtQ.jpeg" /><figcaption>image credit: Norman Rockwell</figcaption></figure><p>We’re a digital agency. Our core business model is performing services for our clients. We do that in two main ways.</p><ol><li>Fixed Bid Projects</li><li>Ongoing Retainer Engagements</li></ol><p>The types of work we do include:</p><ul><li>Website &amp; App Development</li><li>User Experience Planning</li><li>Architecting &amp; Building Analytics Infrastructure</li><li>Running Marketing Experiments &amp; Conversion Optimization Programs</li><li>Managing Paid Media Campaigns</li><li>Inbound Marketing Strategy &amp; Execution</li><li>Content Creation &amp; Social Media Management</li><li>Sales &amp; Marketing Automation</li></ul><p>The clients we serve most likely fall into one of the following business models:</p><p>B2C Ecommerce</p><p>B2B Sales</p><p>B2B/B2C SAAS</p><p>As you can imagine this breadth in scope can be a challenge when it comes to building a communication system that works for everything. Like anything, it’s a work in progress. And, we are experimenting with it as we go.</p><p>We’ve recently made a temporary decision to go fully remote and experiment with how that works.</p><p>Here is a hit list of the tools our team uses to communicate, along with some of the nuances and unwritten rules we have in place to make them more efficient.</p><h3><strong>Asana for Project Management:</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0uQGiZQFgaLpxk4eSghoPQ.png" /></figure><p>Every client we work with starts with a fresh Workspace in Asana. Within that workspace we break things into projects. Some projects use board view, and some use list view. In another article we’ll share some of our templates and go into more detail. If used correctly, Asana provides a great high level view of what’s happening; along with a clean way to break projects into subtasks. It also provides a very simple way to send messages from within a task (or as in board view we refer to them as cards)</p><p>Generally speaking if something is related to a specific project it should go in an Asana card. A few things should happen when you force all project specific communication through Asana:</p><ul><li>You force yourself to think deliberately about the work that you’re doing. Is what I’m doing right now related to a specific project, deliverable, or project we’re trying to solve? Who really needs to see this? When do I need a response?</li><li>It keeps project collaboration out of email. Email is horrible for managing projects. Everyone is using a different email client. People have their own email workflows that work well for them. But tools like Asana (and others Basecamp, Monday, Trello) are designed around team workflow.</li><li>It slows you down. Yes, I said that. It slows you down and forces you to think. If you revert to chat as the default for communicating project details, (yes, it’s quicker)…you run the risk of running fast in no particular direction.</li><li>You can see your progress. Tracking ‘progress’ on a given project is much easier to do in a project collaboration tool like asana. Tasks get checked off as complete. Cards move from left to right. From ‘currently working’ to ‘done.’ You can see who is working on what. If things aren’t moving then you have a problem.</li></ul><p>We’ve adapted our communication as our team has grown and our client base has evolved. As a result we’ve learned some things and run into some bumps in the road along the way. I think it’s safe to say that we have underused Asana and it’s capabilities for group project collaboration. Mostly as a result of my failure to communicate how we should be using it (both internally and with clients), and following that process. Something we need to get better at for sure.</p><h3><strong>Slack for Group Chat:</strong></h3><p>Slack is now our office. We’re just kicking off our remote experiment and without a physical location, Slack is now the ‘office.’ As a result I’ve been thinking deeply about how we use it. What have we learned? What can we do better?</p><p>A 30,000 foot view of how we use slack now:</p><p>We have one main room called ‘office’:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VJOgeYv3aHPBt3G6ELB02A.png" /></figure><p>Everyone on our team is a member of this channel. This is the virtual water cooler. A place where were can quickly reach the whole team to share milestones, small updates, wins, interesting articles, jokes/memes, sports bets, whatever. In the absence of physical location where everyone goes every morning this is the way we fill that void. This room is more about culture than execution. Generally speaking we don’t put project related items in here.</p><p><em>Then, we have a few internal team specific rooms:</em></p><p>#devops: This is for all of our designers/developers and project managers to keep everyone in the loop about development related items.</p><p>#bizdev: This is a channel where we track all of our internal agency biz dev &amp; marketing activity.</p><p>Finally, we have a channel for each one of our clients. All of the project stakeholders at our clients have access to our team via slack. This is something we debated about at the beginning. We went ahead and tried it and have stuck with it. It hasn’t been without its challenges, but for the most part we think the good outweighs the bad.</p><p><em>Some things we’ve learned about this setup:</em></p><p>When you make the decision to open up a communication channel like Asana or Slack to your clients, you have to take the good with the bad. The good is that this decision for us has removed a huge barrier to getting things done. Both ways. We have direct access to decision makers and client side team members to get things we need to push projects along. The bad is that the lines are very blurry around who should be communicating directly with who, where and when. There have been a few scenarios where we (both us and the client) will fall into a pattern of communicating sometimes critical project details through one-to-one slack messages. One-to-one messaging is fine, but it can cause a lot of problems if not managed properly. This is something we need to get better at.</p><p>We struggle a bit with over communication. Or maybe “over integration” is the right word. For most of our projects we have all of the Asana activity getting piped into that project’s corresponding slack channel. This can be pretty handy because it provides a consistent feed with what’s happening on a given project right in the slack channel. However, the tendency for people to just remove Asana from the equation and communicate directly within slack is almost irresistible. Also, if you’re not careful about managing which notifications from Asana come in and which don’t, things can get lost. Recently, a couple of our clients have told us sometimes they “don’t know where to put things.” “Does this go in Asana or Slack?” “Should I just email this to you guys?” “Is this something we need to put in the backlog?” “Should we wait until the next meeting to discuss this?” These are all fair questions. If the client is confused about the process of where to communicate project details we need to do a better job of managing that flow.</p><p>The tendency to default to chat is like a drug. If you get used to instant responses you’ll get hooked. Instant response feels great at first. When you’re the initiator of the conversation you get the immediate gratification of having whatever it is that you’re working on becoming a priority for the person you’re pinging. You begin to depend on it. You expect it. You get that endorphin rush. It’s a fine line. If your team lets this become the norm not the exception…you can do a lot of damage. It’s like that glass of scotch after work. It tastes so good. Helps you unwind. But if having a glass of scotch is the only way you can unwind; over time you’ll kill a lot of brain cells. Chat is no different. In moderation. At the right times.</p><h4><strong>Chat can be very useful for:</strong></h4><p><em>Pairing up:</em></p><p>Chat can be very useful for pairing up for real time collaboration on a specific deliverable. When a small group of people are directly focused on solving a multi faceted problem, using chat to quickly share screenshots, quick screencasts or feedback can be incredibly helpful. We use it a lot in this capacity. For testing the final leg of an implementation, working out bugs, collaborating over UX concepts. etc.</p><p><em>Building a team environment with your clients:</em></p><p>For the most part our clients feel like we are part of their team. Maybe not a part of their in house team, but there is a feeling that we’re working with them towards a measurable objective, vs a tug of war that can happen in a lot of client/vendor relationships. I think having an open chat room with them helps this. Having a place where you can drop a relevant article, or share a story that might impact the client work you’re doing for them…open group chat with clients is great for that.</p><p><em>Emergencies:</em></p><p>I use this term carefully. Few things are really emergencies. But, there are times when shit goes haywire and you need to get someone’s attention immediately. When you need something right away, your best bet is probably the phone. But if you can’t get them on the phone pinging someone on chat to get their attention typically works. Be careful though. If everything is a priority, nothing is.</p><h3><strong>Email for Big Things.</strong></h3><p>When it comes to getting projects done, email is the devil. Seriously. Over the past 15 years or so, ‘emailing’ has become synonymous with ‘working.’ We need to stop the madness. How many times have you heard someone say, “I’ll be on email working.” OR, “If you need me I’ll be on email.” Email is not work. And just because someone is ‘emailing’ doesn’t mean they’re working or getting things done.</p><p>I think we’ve become obsessed with inbox zero. I think we’ve slowly buried ourselves into a culture of deflection. People are trained to get things off their plate. As a result, they sacrifice quality thought and productive collaboration for quick replies to make sure clients or co-workers thing they’re ‘working hard.’ Nonsense. A culture where it’s expected to insta-reply to an email thread is a dangerous one. It can divide team members, create a false sense of competition, make people think that a quick reply is better than one that is well thought out.</p><p>As an organization I think we’re pretty good as it relates to email. We’ve gone a little overboard with slack, which probably contributes to that. However, email can be really useful for communicating things like:</p><ul><li>Big organizational ideas, thoughts, proposals for large changes in process or operations.</li><li>Large product feature requests</li><li>Things were you don’t need an immediate reply. Where you’d rather the recipient digest what you’re emailing.</li></ul><h3><strong>Zoom for Video Conferencing:</strong></h3><p>When text just won’t get it done and you need that face to face collaboration, we use Zoom for video conferencing. The video conference is a huge part of our culture, but we need to continue to get better at it.</p><p>We use video conferences and screen shares for:</p><ul><li>Client meetings</li><li>Collaboration on Mockups &amp; Designs</li><li>Troubleshooting Bugs or Issues</li></ul><p>Things we need to do more of now that we’re remote first:</p><ul><li>Video team lunches or happy hours</li><li>Interviewing new team members</li><li>Knowledge sharing sessions</li></ul><h3><strong>The Phone:</strong></h3><p>Calls: Sometimes the old fashioned pick up the phone and call someone works the best. Especially if you’re on the road, in the car or on the move you can get a lot done with a quick call.</p><p>Texts: Just don’t do it. I mean I guess if you’re running late for a meeting, letting someone know where you’re at for happy hour, or if a bunch of us are at a trade show and have a group text to keep in touch. I’d keep text out of the project communication lineup. 🙂</p><h4><strong>Other Thoughts:</strong></h4><p><em>Killing the addiction to ASAP:</em></p><p>The other day I saw a tweet from Jason Fried of Basecamp. He comments that they were thinking about implementing a ‘sleep-on-it’ feature in Basecamp, where the software would require 24 hours before people can comment. He was talking about basecamp and not email, but I thought that was interesting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wkzxU4tA_ecwk5dnfzrzRA.png" /></figure><p>How does your team communicate with remote team members? Are you working with a digital agency? What communication and collaboration tools do you use to work with them?</p><p>I’d love to hear your feedback.</p><p>If you found this article useful I’d be humbled if you recommended it or hit me with a few claps. Follow me here or @rriggin on twitter as we continue this journey. Thanks.</p><p>R-</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7bd4d2b5c7c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Experimenting with a Remote First team at our Digital Agency]]></title>
            <link>https://medium.com/@ryanriggin/experimenting-with-a-remote-first-team-at-our-digital-agency-9cae63338c8c?source=rss-bc2457e819c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/9cae63338c8c</guid>
            <category><![CDATA[digital-agency]]></category>
            <category><![CDATA[remote-working]]></category>
            <dc:creator><![CDATA[Ryan Riggin]]></dc:creator>
            <pubDate>Thu, 04 Oct 2018 13:42:44 GMT</pubDate>
            <atom:updated>2018-10-04T13:50:24.971Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rgcVKn9UJ7lHNtuvqM0kXQ.jpeg" /></figure><p>I run a digital consultancy. We are a small but scrappy team of doers. Our clients are e-commerce brands, B2B sales teams and startups building products. We help our clients with all aspects of digital including UX/Design, Development, Audience Growth, Systems Integration, and Ad Campaign Optimization. I’ve tried for 5 years to follow the advice of all of the gurus and condense that down to a 5 word elevator pitch, choose a niche like (we do conversion optimization for e-commerce brands) or (we do marketing for lawyers) and scale this consultancy into a rocket ship ride of growth. I’m coming to realize some things:</p><ol><li>This consultancy is a lifestyle business. Not a startup. It exists to serve our clients, our team members (employees &amp; contractors), and my own personal lifestyle needs as the owner.</li><li>What we do and how we do it is more important than niching down our service offering so we can build a scalable repeatable sales process so the agency can double revenue every year.</li><li>Growth doesn’t have to happen fast. Slow steady growth is ok.</li><li>At the end of the day, we help our clients identify business and technology problems. Then we staff on demand teams to work WITH them to help implement solutions.</li></ol><p>All of that said, one of our core values as a team is experimentation. We have invested a lot energy in developing a process for experimentation and optimization. Specifically as it relates to ad campaign optimization, marketing automation, and conversion rate optimization. Recently we’ve been having an internal discussion about how we work, and we have decided to run some tests on our process. We’ve spent the last 3 years working out of co-working spaces. And we will likely continue to do so in some capacity. But we’ve made the decision to make Remote a core part of our culture. It sounds funny to even say that because it already was. Now we’re simply being explicit about it.</p><p>We’re in between offices right now. We are exploring a couple of opportunities for office space long term but none of them are readily available today. So the timing worked out pretty well to do this. Here is a summary:</p><p>We are going to spend the next 90 days experimenting with what we’re calling a ‘REMOTE FIRST’ organization. The key here is the word ‘FIRST’. We’re going to optimize our process &amp; team culture so that they exist independent of any one physical location. This will leave us the option if and when we do decide to get another ‘Office,’ that our culture and our processes will exist independently.</p><p>Where we’ve been:</p><p>Our core team consists of around 11 people. 3 of which are full time. The balance is a core group of freelancers/contractors. 3 of us are in one office in downtown Kansas City. That office is around a 30 minute commute for the three of us who work there every day.</p><p>The rest of our team is made up of remote contractors from around the globe.</p><p>1 in the KC suburbs</p><p>1 in Alabama</p><p>1 in Florida</p><p>1 in Georgia</p><p>2 in Pakistan</p><p>1 in India</p><p>1 in California</p><p>1 in the Philippines</p><p>As you can see, Remote is already a big part of who we are.</p><p>Challenges we’ve faced with this setup.</p><ul><li>There is a virtual wall between the three of us in the office and the rest of the group. The 3 of us in the office developed our own culture where the rest of our team wasn’t able to participate. Lunch, happy hours, sports betting, morning coffee, the usual. Over time those small things drive a wedge between the ‘locals’ and the ‘remotes.’</li><li>Having this office was expensive. For the amount of physical space we had we were paying way to much in rent. (It wasn’t a complete waste of money, there were some really positive intangibles that came with having this office that maybe I’ll cover another time.)</li><li>In a given week, our 3 person team kills 15 hours a week commuting. That is purely drive time. This doesn’t account for the disturbance of shifting from one mental space to another after the drive. 15 hours a week of waste is conservative.</li></ul><p>What has been great about having a downtown KC office?</p><ul><li>It gives our clients a sense of who they’re working with and makes them feel like they’re working with a real company. In fairness, I’ve never heard one of our clients say that. This is purely my own head trash.</li><li>We had a killer set up for inviting clients in for meetings. (Conference rooms, rooftop deck, etc).</li><li>I love being in downtown KC. It’s the best kept secret in the country. There is an energy to being in a downtown office that I think we’ll miss.</li></ul><p>What we’re doing now:</p><p>We’re going to run the whole team remotely for the next 90 days. I will maintain a small office space where I live in Lee’s Summit, MO, a suburb of Kansas City. I can’t work from home so I need a place to go. Likely what we’ll do in the long term is find a way to provide co-working opportunities for remote employees who wish to participate.</p><p>What tools we’re going to use:</p><ul><li>Slack is now the office.</li><li>We’ll continue to use Asana for project execution</li><li>Zoom will be our go to for group video calls and collaboration.</li></ul><p>What do we hope to learn? What do we think will happen as a result of this experiment?</p><ul><li>I hope this forces us to focus on all of our key processes. (How we do project delivery, how we manage clients, how we market ourselves.)</li><li>I hope it forces us to be deliberate about how we collaborate as a group.</li><li>I hope it forces us to slow down and refine how we use Slack (chat).</li><li>I hope that documenting our learnings forces us to write and produce content about our process, the awesome client work that we’re doing, and how we get things done.</li><li>I hope that our team members use the time they gain back to enjoy their families more</li><li>I hope the time saved from commuting allows for team members to focus on their health, both mental and physical. (writing, running, cycling, whatever floats your boat)</li></ul><p>What concerns me about this move?</p><ul><li>I’m concerned that our clients will see it as a negative. Like anything, this is something we’re going to have to manage and make sure they see the value.</li><li>I’m concerned that it will be difficult to engage with the Business/Tech community without a presence in the city.</li><li>I’m concerned that we’ll lose some of the impromptu whiteboard brainstorm sessions ( we’ll be focusing specifically on how to make up for this in a remote environment )</li></ul><p>Follow up posts:</p><ul><li>Integrating freelancers/contractors into your remote team</li><li>How we use slack/chat</li><li>How we manage impromptu whiteboard collaboration sessions remotely</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9cae63338c8c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Conversion Optimization Starts with Customer Service?]]></title>
            <link>https://medium.com/@ryanriggin/conversion-optimization-starts-with-customer-service-conversion-optimization-blog-283e1db0e311?source=rss-bc2457e819c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/283e1db0e311</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[customer-service]]></category>
            <dc:creator><![CDATA[Ryan Riggin]]></dc:creator>
            <pubDate>Tue, 25 Apr 2017 00:06:00 GMT</pubDate>
            <atom:updated>2017-04-25T00:07:48.492Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*_VnUlp4vSJlrc6Q5331NyA.jpeg" /></figure><p>Everyone involved with your marketing optimization team should spend at least a week in customer service. Seriously. You think I’m crazy right? Why would you pay an agency to come into your company to do customer service? Not only should your agency spend some time working in customer service but everyone on your marketing team should.</p><p><strong>HERE’S A LITTLE STORY</strong></p><p>A few years back, I heard an interview from Kayak Founder and serial entrepreneur Paul English. In the interview he talks about how he hung an annoying red phone in the area where the Kayak software engineers worked.</p><p>While talking about how his team handled customer service he said:</p><blockquote>The engineers and I handle customer support. When I tell people that, they look at me like I’m smoking crack. They say, “Why would you pay an engineer $150,000 to answer phones when you could pay someone in Arizona $8 an hour?” If you make the engineers answer e-mails and phone calls from the customers, the second or third time they get the same question, they’ll actually stop what they’re doing and fix the code. Then we don’t have those questions anymore.</blockquote><blockquote>About a year ago, I bought a red telephone with a really loud ringer for the office. Whenever a customer calls the help number on our website, that phone rings. The engineers initially complained about it. They said, “That’s so friggin’ annoying!” And I’d say, “There’s a really simple solution: Answer the friggin’ phone and do whatever it takes to make that customer happy. Then hang up, unplug the phone, walk it down to the other end of the office, and plug it in down there.”</blockquote><blockquote>When the phone rings, I literally jump over the desks just so I can get to the phone before anyone else. I love talking to customers, even angry ones. I learn a lot from them about how to make the site easier to use. When the call’s over, I’ll say, “If you have any follow-up questions, my name is Paul English; I’m the co-founder of the company.” I’ll give out my personal cell-phone number. Only one out of 20 people might actually call, but they’re blown away when I do that.<em><br> -Paul English</em></blockquote><p><strong>“I LITERALLY JUMP OVER THE DESKS”</strong><br> “I literally jump over the desks just so I can get to the phone before anyone else. I love talking to customers, even angry ones,” he says.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*Lplp4Zw7nr5HhA2xB4FepA.jpeg" /></figure><p>This is a picture of Paul himself answering the red phone. Credit to the team at GrooveHQ for the image and a very nice blog post about how to establish a culture of customer service within your team.If you’re looking for an easy to use help desk tool I would check them out.</p><p>This is insane right?? I’ll admit. When I first heard it I thought he was crazy. Then I started to buy in. I could hear my boss at the time, and how he would’ve reacted if I’d told him I was going to do that. “That just won’t scale. It’s not efficient,” he’d say. We’ll that’s bullshit.</p><p>Here’s the thing:</p><p><strong>THE TWO BEST WAYS TO LEARN ABOUT HOW A BUSINESS WORKS ARE:</strong><br> You ready??</p><ul><li>Digging through Search Query Data in Google Adwords (we’ll talk about this in another post)</li><li>Talking to customers</li></ul><p><strong>THAT SOUNDS SO SIMPLE RIGHT? TALKING TO CUSTOMERS?</strong><br> But people that wear suits don’t want to do it. More importantly, they’re so obsessed with operational efficiency that they don’t see the value. At first glance you might think its crazy to put your most expensive employees on the front lines dealing with customers. What they’re missing is the learnings you absorb from talking to customers. It is gold.</p><ul><li>Feeling the customer’s pain.</li><li>Hearing the agony in their voice when they can’t figure something out.</li><li>Understanding why they’re pissed off.</li><li>Listening to them tell you EXACTLY what they want.</li><li>All of the customer research, surveys and analytics data in the world can’t give you what you’ll get by spending a few minutes talking to the customer.</li></ul><p>I learned this first hand in my last business and it was gold. For real. My previous business was an online gold buying site. We had a simple model, but we took a different approach to customer service than most of the businesses in that space at the time. Most of the sites in that world were paying ridiculously low rates compared to spot value, and were taking advantage of uneducated customers. We zigged when they zagged. We posted our pricing. We were transparent about our payouts. We offered no risk appraisals. I remember when we started I used to sit on my laptop while watching baseball games at night and man our customer support live chat. It was incredible.</p><p>We grew this business based on learning what the customer wanted, then optimizing our ads, website, conversion path, follow up strategies, and customer service infrastructure to fit. It worked.</p><p><strong>FAST FORWARD TO TODAY</strong></p><p>I’m running an optimization firm that performs these marketing &amp; conversion optimization services for clients in all types of verticals. Why would we do it any differently? When we first engage with a client, we conduct an optimization audit. This audit is a full scale analysis of your customer groups, your website and the data that you have. After that we dig in and spend time working with your customer service team. This can come in the form of live chat, shadowing a customer service rep, manning an email account, or putting on a headset and working in a call center. Whatever it takes. We’re going to engage at a level that no other agency will.</p><p><strong>SO, WHAT HAPPENS WHEN WE DO THIS?</strong></p><p>A lot.</p><ul><li>We figure out what IS working: Companies waste a lot of time fixing what isn’t broken just because some manager doesn’t like the font on some landing page, or the subject line of an email. When you listen to your customers you find out really quick what they don’t like, and what’s working just fine. We’ll quickly bucket the opportunities for large ‘needle moving’ optimizations and push aside any of the frivolous stuff that doesn’t really need fixing.</li><li>We hear the most common frustrations: All of the bad stuff rises to the top. Typically within a few hours of being on the phone you can pinpoint the customer’s most common pain points. After a week you can build a nice list of the ones you hear the most and begin to prioritize them.</li><li>We build a prioritized roadmap for Testing: Yep, you guessed it. Now we start planning. Based on the feedback we’re hearing from customers and the data we see in your analytics we start to organize a roadmap of the tests &amp; optimizations that we can make to you conversion process.</li><li>We put ourself on the same level as you (the client): When we roll up our sleeves and spend time working customer service with you, we immediately become part of your team. No longer are we a third party. Well technically we are, but you get the point. We’re in this with you.</li></ul><p><strong>WHAT ELSE?</strong><br> What other benefits could you see from having your marketing agency spend time in customer service? Are you doing this already in your company? We would love to know!</p><p>Shoot us a <a href="https://twitter.com/measuremedia">tweet</a> and tell us what’s up, or <a href="http://measuremedia.com/#contact">schedule an optimization audit </a>.</p><p><strong>Ryan Riggin</strong></p><p>Ryan is a marketing guy who likes to get his hands dirty with technology and data. Outside of that you can find him out riding a bike somewhere.</p><p><em>Originally published at </em><a href="http://measuremedia.com/blog/conversion-rate-optimization/marketing-optimization-starts-with-customer-service/"><em>measuremedia.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=283e1db0e311" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>