<?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[Animoto - Medium]]></title>
        <description><![CDATA[Animoto is the easiest way to create pro-quality videos — without the hassle of complex software or the expense of an agency budget. Get started free. - Medium]]></description>
        <link>https://medium.com/animoto-blog?source=rss----75cf85816582---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Animoto - Medium</title>
            <link>https://medium.com/animoto-blog?source=rss----75cf85816582---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 00:14:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/animoto-blog" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Growing With Our Company Virtues]]></title>
            <link>https://medium.com/animoto-blog/growing-with-our-company-virtues-317dd1f48806?source=rss----75cf85816582---4</link>
            <guid isPermaLink="false">https://medium.com/p/317dd1f48806</guid>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[values]]></category>
            <category><![CDATA[team]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Brad Jefferson]]></dc:creator>
            <pubDate>Wed, 25 Aug 2021 19:28:06 GMT</pubDate>
            <atom:updated>2021-08-25T19:28:06.611Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zmxQ3qN5c-OUOSW13XrZPQ.png" /></figure><p>Here at Animoto, we are a team that rallies together through good times and bad. It’s easy to celebrate the victories and wins during good times — and we’re very good at that. But, more importantly, we are great at lifting each other up when things aren’t going so well and the victories and wins don’t come so easily. We’ve been at this for fifteen years and have seen these cycles many times. It’s my belief that companies that stand the test of time are those that are intentional about investing in their people and their culture.</p><p>How exactly do you do that?</p><p>In my experience, companies with a successful culture are:</p><ul><li>readily responsive to feedback,</li><li>agile in the face of change,</li><li>and excited about growing through setbacks.</li></ul><p>For our company, revisiting our core values, or what we now refer to as <a href="https://medium.com/animoto-blog/making-the-leap-from-company-values-to-company-virtues-1b9deede2bac">our virtues</a>, is about making sure we do all three — and do them well.</p><h3>How it all started</h3><p>When we founded Animoto as a group of four friends, our culture was already built-in at the core of our business. Back in 2006, our company was founded on deep friendship, perfect trust and accountability, and of course — a lot of fun. We were able to scale this as the basis for our culture for the first several years.</p><p>When we grew to around forty employees, however, we ran into some natural challenges. So, the executive team put together our very first set of company values, seen below. These values are still up on the Animoto HQ wall, as a relic and reminder of where we started.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/0*ejRh_40zIzHwWTLL" /></figure><p>Although those values were a good stepping stone, the team soon outgrew them. Eventually, they looked to us like helpful <em>principles</em> and <em>promises</em> but they certainly didn’t feel unique to Animoto. So, in 2016, we went back to the drawing board. This time, we asked the whole Animoto team one simple question: <em>Who are we when we are at our best?</em></p><p>We didn’t ask for the executive team’s take on our aspiration values, and we didn’t ask “Who do we think we should be?”, or “Who do we want to be in the future?”. We wanted to know how our team <em>as a whole</em> saw ourselves in our ideal state.</p><h3>How our values evolved with our team</h3><p>The responses we received were inspiring, to say the least. Even better, they had three common themes: humility, a problem-solving attitude, and passion/creativity/fun. We then tasked a small creative team within Animoto to take these themes and mold them into the values that reflected our culture. Here’s what they came up with:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vtfSKmvJFgxw1A2V" /></figure><p>These new values weren’t just memorable and distinct. They helped us make meaning of aspirations that were unique to our team. They helped us feel united and gave us a north star to strive towards.</p><h3>How our team grew together — and what it meant for our company values</h3><p>In 2019, we made a subtle but important change: we went <a href="https://medium.com/animoto-blog/making-the-leap-from-company-values-to-company-virtues-1b9deede2bac">from “company values” to “company virtues”</a>. Inspired by Ben Horowitz’s book, <a href="https://www.amazon.com/What-You-Do-Who-Are/dp/0062871331">What You Do Is Who You Are</a>, he credits the Japanese samurai culture with saying, “Virtues are what you do, whereas values are merely what you believe.” That hit me really hard. The reality is that Humbletude, Betterfication, and Oomphosity have become what we do at Animoto — they are our code of conduct. These three traits are deeper than just our values. They’re our virtues that we live each and every day at work.</p><p>This year, we decided to take it even further. In the spirit of betterfication, and to ensure that our virtues are a growing reflection of our team, we took a deep, humbling look at the definitions of our company virtues. Here’s how we explain our three company virtues today.</p><h4>Humble•tude</h4><p>Previously, we saw humbletude as a combination of humility and attitude. Since then, we’ve realized that being humble and having an attitude can be polar opposites of each other. So, we thought through this with the team and shifted this value from “attitude” to “aptitude”. Why? Because we are confident in our abilities but believe we can <em>always</em> learn from each other.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XldAckLDzi2cWM9Z" /></figure><h4>Better•fication</h4><p>In the past, we thought betterfication was strictly about our team at Animoto, our brand, or our business. Last year, we learned that our platform affords us an opportunity to betterfy much more. We believe that making the world a better place begins with each of us pushing for and becoming the change we want to see. At Animoto, we’re crazy enough to believe that we can change the world with this outlook.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Gdcskj_ONH5qvXVp" /></figure><h4>Oompho•sity</h4><p>We believe our diversity of thought, experience, background, gender, race, sexual orientation, and ability makes Animoto stronger and puts us in the best position to fulfill our company vision. We are proud to bring our full selves and unique talents to work every day. When we look at ourselves in the mirror at this stage in our journey, we know that our strength comes from our diversity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*G0rXP9wjc9769VIq" /></figure><p>Everything we do at Animoto is stronger when we bring together as much diversity as possible. That’s why we work towards this daily.</p><h3>Have you considered your company virtues?</h3><p>What makes up your company’s values (or virtues)? Have you and your team thought through who you are at your best? Do you live by what you believe? If you had to come up with a list of virtues for your team, what would they be? If you’ve already come up with that list, can everyone in your company recite them? Better yet, does everyone live by them? Drop a comment below and let me know!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=317dd1f48806" width="1" height="1" alt=""><hr><p><a href="https://medium.com/animoto-blog/growing-with-our-company-virtues-317dd1f48806">Growing With Our Company Virtues</a> was originally published in <a href="https://medium.com/animoto-blog">Animoto</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pivoting to Weekly User Testing: A Blueprint for Success]]></title>
            <link>https://medium.com/animoto-blog/pivoting-to-weekly-user-testing-a-blueprint-for-success-aec571703d37?source=rss----75cf85816582---4</link>
            <guid isPermaLink="false">https://medium.com/p/aec571703d37</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Mike Montano]]></dc:creator>
            <pubDate>Mon, 08 Feb 2021 16:54:21 GMT</pubDate>
            <atom:updated>2021-02-05T22:25:04.663Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tumN9jc--WepdPI9aiTSjQ.jpeg" /><figcaption>Illustration by Kaylee Reynolds</figcaption></figure><p>In graduate school, my advisor gave me one of the most important pieces of research wisdom. After a hiccup during one of our studies, she shrugged and said “The course of science never runneth smooth.” It’s a phrase that has stuck with me throughout my career and I mentally repeat it to myself anytime there is an error in a prototype, or I flub a question during an interview. As researchers, we always strive to be perfect, rigorous, and repeatable, but sometimes you’ve just got to find a way forward to best get research to meet the needs of the team. This was a situation I recently experienced as I worked to pivot the research process from its previous form to a rapid, weekly testing cadence. Oh, and I am the only researcher currently on board.</p><p>My name is Mike Montaño and I work at Animoto, a video creation tool that small business owners and consumers can use to easily create videos to market themselves, and their products or content on social media. I’ve been at Animoto for nearly four years, and have been the lead UX researcher for nearly the past two and a half. I have a master’s degree in experimental cognitive psychology from Auburn University and have worked in the UX field for almost eight years.</p><p>While at Animoto I had fallen into a comfortable routine of running in-person moderated usability tests on a two-week (possibly three-week depending on the constraints and research question) cadence from kickoff to readout while also juggling other requests, consults, and smaller projects. However, in October of 2019 Animoto as a company and the design team specifically realized that there was a new chance to move the product forward as a whole.</p><p>The design team identified an opportunity to fully redesign the core experience and user interface of the Animoto product. This would be a chance to drive the user experience and provide functionality that would empower users to be able to make more eye-catching videos at a significantly faster pace, optimized for various platforms and aspect ratios. It was a huge project that would require Engineering, Product Management, and Design to all crank harder than ever before, in concert with one another to get the product launched into beta by the second quarter. With so many new designs and interactions available to users a new approach to rapid research and testing was going to need to quickly kick into gear. Let me tell you what we did, what went well, and what we sacrificed to run effective weekly testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BaY49odZ3WMA3IIV_I3Mkw.png" /><figcaption>Illustration by Kaylee Reynolds</figcaption></figure><h3>What Did We Do?</h3><p>After taking some time to work closely with the designers to define the best approach to the testing structure, we were able to settle on a plan that would allow for rapid iterative testing as a result of fast recruiting and group synthesis. Recruiting would begin on Thursday and was accomplished through a subscription with UserInterviews.com. The new recruit would begin and then continue for 24–48 hours while potential participants were filtered onto the dashboard by the service. On Monday, I would meet with the team to sync on the testing needs for the week. If there were early prototypes or general sketches we could walk through them at this point so I could begin thinking about what the moderator’s guide might look like and start working on an outline.</p><p>I would then log back into UserInterviews.com to approve qualified participants from the pool of surfaced options. Four slots were opened throughout the day on Wednesday and approved participants had the ability to self select into whichever time slot worked best for their schedule. New potential participants were always being added to the pool after the first 24 hours so I would frequently return to the dashboard to approve new participants in the hopes of filling all four of the time slots before Wednesday.</p><p>By Tuesday, the designers had finalized their designs of the prototypes that were to be tested on Wednesday. So, we would meet again to step through the process and sync on all the questions they hoped to have answered during the session. At that point, I would flesh out the draft of the moderator guide with the new information from the prototypes and questions from the designers and send the guide out to the group for any feedback and comments. Ideally, the time slots would be filled by this point so I would send out the calendar invites for the sessions to the team so they would be able to listen in. I’d send out reminder emails to all the participants with troubleshooting instructions and my contact information so they could reach out if they encountered any difficulties logging into the remote sessions.</p><p>On Wednesday morning, I would send out a blank document that would be used for notes and ask for volunteers to take notes. For each session, there would be at least three people on the Google hangout: myself, the participant, and one designer to take notes during the session. I would refer to the designer as a research colleague at the outset of the session to avoid biasing the participant to only give positive feedback to the creator of the designs. Additionally, all sessions were recorded using Quicktime with the participant’s consent. Each session lasted one hour and were scheduled such that there was a thirty minute gap between each to allow for potential spillover due to late arrivals, technical difficulties, etcetera.</p><p>After the sessions were completed the entire team would meet to debrief. This group consisted of the product managers, product designers, engineers, and myself. A note taker would be designated at the beginning of the meeting and I would step through the prototype with the team and call out key findings and consistent feedback from the participants at each turn. After my initial readout, I would open the floor to other team members to see if they had other feedback about what I had called out or additional findings that they had seen during the sessions so we could discuss them as a group. At the end of the debrief the team would discuss next steps and how to take action based on the results of the sessions and would begin to work on new iterations to cover next Monday. On Thursday, I would spin up another round of recruiting on UserInterviews.com and the process would begin again.</p><h3>What Went Well?</h3><p>There were three main techniques and approaches that allowed this weekly testing cadence to work for the team: supercharged recruiting, over-communication between product design and UXR, and a streamlined moderator guide scripting process.</p><h4>Recruiting</h4><p>This entire section will inevitably sound like a paid advertisement from UserInterviews.com, but I promise I am in no way being compensated for it. Most researchers dread recruiting because it can be an arduous and frustrating process while simultaneously being wildly time consuming. When the team was in the early stages of planning weekly testing, I made it clear that a weekly cadence would only be possible if we were able to find a way to significantly reduce recruiting time and be assured that the reduced time would be replicable each week. After some investigation and trial runs with different approaches I brought UserInterviews.com back to the team. Luckily, at Animoto research is highly valued so I did not have to argue particularly hard to get buy-in from the team and executive level stakeholders. After crunching the numbers, it was clear that we would be recruiting and running enough sessions that signing up for an unlimited monthly membership with targeted recruiting based on the participant’s job, since we were after a specific participant type, would make the most sense. The consistency, both in speed of participants being surfaced to the dashboard and in the caliber of participants who took part in the sessions was incredible. Without such a powerful pipeline of reliable participants this weekly testing plan likely never would have gotten off the ground.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wnKka4ATi96rbXQ_kuKm4A.png" /><figcaption>Illustration by Kaylee Reynolds</figcaption></figure><h4>Over-communication</h4><p>One of the most important parts of working with teammates is learning how to communicate effectively. While it was always important to stay in touch when working in the office together, the need to communicate clearly and frequently ended up becoming even more important once we were all physically apart from one another during the pandemic. There were certain weeks when the prototype was being finalized in the hours before the test was set to run and times when the moderators guide was being tweaked right before the first session was set to begin. Stressful situations like that can often lead to mistakes and miscommunication so the team really made sure to focus on over communicating throughout the week and especially during the lead-up to the first session kicking off. Using shared tools like Slack and Google Docs, we were able to very clearly see the status of various deliverables and inform one another when new content was ready to be reviewed by the team. Working together to streamline communication while also being flexible in this newly remote world we were existing in allowed us to get into a rhythm and hum like a well-oiled machine.</p><h4>Scripting</h4><p>This was an area where the weekly testing really provided me an opportunity to grow and develop as a researcher. In previous testing situations I have preferred to focus on getting all of the details perfect before sharing out a moderators guide for review with team members. I certainly know that no first-draft is ever the final draft but I often would let perfectionism get the better of me and spend too long tweaking everything to get it just right. With the shorter deadlines in place, I needed to move beyond this habit and work more effectively within the reduced time frame. This meant ceding some of the control to, as mentioned above, communicate earlier and often. Functionally, this required sharing the moderator guides out for feedback at earlier stages than I was used to. This ended up being a boon for the research and for my development as a researcher because I was able to learn to let go a little bit and not focus on attaining perfection with a first draft, and also allow for more time for the team to provide feedback about the guide itself by providing it earlier. I now find myself to be less tight-fisted with the first draft than I used to be coming into weekly testing.</p><h3>What Did We Sacrifice</h3><p>In order to get into the weekly testing cycle, we had to make some sacrifices. There were three main areas that the team came together and decided on in order to reach our weekly testing goals: the number of participants in each round, dedicated analysis time, and our shared cortisol levels.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hp739AHDHCtNduVGDdJnAA.png" /><figcaption>Illustration by Kaylee Reynolds</figcaption></figure><h4>Number of Participants</h4><p>With our schedule set up the way it was, there was only one day allotted for the actual testing process. Given that there was only one researcher and only so many hours in the day we decided to use only 4 participants in each test as opposed to the industry standard of five. Now, I can almost hear people already complaining that they’ve run more than five participants in a day and I certainly understand — I’ve done it myself. However, given that we were going to be doing this for an undetermined length of time we wanted to make testing as sustainable as possible and capping the participants at four was one step we took to meet that end. Looking at the <a href="https://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/">famous Nielsen Norman graph</a> you can clearly see that four participants are still providing a wealth of information and data. We further justified this sacrifice with the understanding that we would be running significantly more tests on given parts of the designs. Why do researchers not test with ten participants instead of five? Because the ROI on time invested is better served by doing two tests of five. We decided to lower our participants to four but then do significantly more iterative tests thereby uncovering the same insights over time that would have been identified with one test with five.</p><h4>Time for Analysis</h4><p>Given that the point of the weekly testing was to provide frequent data to the designer who could then take those insights and iterate on the previous designs there was simply not time for an extended data analysis period. A full day of affinity mapping was a day less for the designers to be working on new ideas. In order to keep the process as streamlined as possible, a debrief meeting was scheduled for the end of the day after the last session ended. During that meeting, one person would volunteer to be a notetaker and UXR would step through the prototype and the moderator guide and call out the main takeaways where the majority of participants had issues throughout the test. After identifying the primary key insights, the floor was opened to the rest of the team who had been observing all of the sessions as well. This was an opportunity for everyone else to add in any other insights that may not have been included in the original rundown or areas where there had been differing impressions. This allowed the team to get on the same page about what the main takeaways and key insights were and identify next steps for the next iterations on the designs. It was a very collaborative and open space that allowed for the team to effectively highlight and prioritize the key findings and ended up being an illustrative showcase for the collaboration between product design, product management, and UXR.</p><h4>Cortisol levels</h4><p>The title of this section is a bit of a joke but if you can’t tell based on how I’ve outlined what our process looked like, allow me to be clear: doing testing at this cadence can be (and was at times) incredibly stressful. You need to be able to recruit participants for a test that will cover a prototype you haven’t seen yet, create a moderator’s guide based on incomplete designs, deal with some degree of uncertainty coming right up to the day of the test, run a marathon of testing in one day, analyze and summarize the key insights at the end of the day and then turn around and begin the process again the next day. In order to try to fight the impending stress it is incredibly important to plan effectively and find a process that works well for you. Finding a rhythm that works well and is sustainable will help you be able to continue working at this clip. Finally, assembling a team that communicates openly and often throughout the week will absolutely make this process significantly less bumpy. Remember what my advisor said: “The course of science never runneth smooth.” Be open to making mistakes, but more importantly take action to learn from the mistakes you make along the way. Finally, hold on and get ready for an exciting ride if your team decides that there is a need to start weekly testing and you’re the sole researcher at your company.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aec571703d37" width="1" height="1" alt=""><hr><p><a href="https://medium.com/animoto-blog/pivoting-to-weekly-user-testing-a-blueprint-for-success-aec571703d37">Pivoting to Weekly User Testing: A Blueprint for Success</a> was originally published in <a href="https://medium.com/animoto-blog">Animoto</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Inspiration to Migration: 7 Steps to Launch a Product Redesign]]></title>
            <link>https://medium.com/animoto-blog/inspiration-to-migration-7-steps-to-launch-a-product-redesign-86572d72ae00?source=rss----75cf85816582---4</link>
            <guid isPermaLink="false">https://medium.com/p/86572d72ae00</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Brian Rhee]]></dc:creator>
            <pubDate>Wed, 11 Nov 2020 21:30:08 GMT</pubDate>
            <atom:updated>2020-11-23T16:10:18.854Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Inn6DAF5myCHl3iArPc-wA.jpeg" /><figcaption>Illustration by Danielle Vogl</figcaption></figure><p>In the Fall of 2019, Animoto set out on a mission to reimagine and rebuild our web video creation product from the ground up. It was the most ambitious project we’ve ever taken on in my tenure here (which is now eight years!). We started with a design workshop to envision the future of Animoto, set in the near-term future of 2022. Then, we set an ultra-aggressive MVP ship date of Mother’s Day 2020.</p><p>And as of Fall of 2020, we’ve fully migrated 100% of our users to our new web product, Animoto 3! Although this isn’t my first time shipping a new product, the opportunity to build something from the ground up doesn’t come everyday. Most often, designers with in-house tech roles have the mission to incrementally improve experiences over time. But every few years, the moment arrives where it’s better to start fresh with a clean slate.</p><p>If you find yourself in one of these moments, here are 7 steps to follow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9Red_3SGQ1bt4gbFU2k1qQ.jpeg" /><figcaption>Before and after our redesign. Illustration by Danielle Vogl.</figcaption></figure><h3>Step 1: Before you start, build organizational support</h3><p>Although the design process began Fall of 2019, Design leadership began advocating for the need to redesign our web product in January 2019. We had just completed a workshop to explore a new project start experience across web and mobile, and started shifting our focus to the video creation experience itself.</p><p>In this phase, it’s important to:</p><ul><li><strong>Foster relationships with Product Management and Engineering.</strong> It’s important to build support with your partners, and to learn the challenges they face as well. With these conversations, you’ll then be able to better articulate the need and identify the right time to pull the trigger.</li><li><strong>Clearly articulated the need.</strong> At Animoto, we found that we had outgrown our existing product architecture from and it had become almost nightmare-ish for designers and engineers to add value and improve the product experience.</li><li><strong>Choose your timing wisely.</strong> Design workshops and product redesigns are highly disruptive activities. Set yourself up for success by identifying the right time for a vision workshop, and the right time in your product lifecycle for a rebuild.</li></ul><h3>Step 2: Define a long term vision</h3><p>Because this was a large product redesign, we conducted a workshop to set a vision for our future. We set a timeframe for that future to be 2 years. It was just far enough to help us let go of our current constraints, but also close enough that we felt confident in knowing that the marketplace opportunity would not dramatically change.</p><p>While conducting this workshop, your goals should be to:</p><ul><li><strong>Deep dive into context building.</strong> The goal here is to develop a more holistic understanding of the problems your customers are facing. We worked with all of our customer facing teams to pool together the learnings of the last 5 years into a single Miro board.</li><li><strong>Be inclusive and transparent in your process.</strong> To successfully execute your vision, it’s critical that everybody in your company feels ownership in the vision. How might you set up ideation workshops to include key members across your organization? Are there checkpoints to incorporate feedback from your executive team along the way?</li><li><strong>Plan for multiple cycles of customer feedback loops.</strong> As you generate ideas, various themes will emerge. It’s absolutely imperative that you understand which ideas resonate most with your target customers. Validate that your concepts and proposed features genuinely excite your target customer.</li></ul><h3>Step 3: Develop your execution strategy</h3><p>After building organizational support and generating real excitement with your 2 year vision, we were ready to develop an execution strategy to achieve the first step: Setting a new foundation for the future by rebuilding our core video creation experience. This new foundation would set the stage for Animoto to accelerate into our 2 year vision.</p><p>At this stage, there will be a number of decisions you’ll have to make:</p><ul><li>What is your MVP feature set? What existing features are must have? Which features can you deprecate? What new features can you bring in to help ensure a successful launch?</li><li>Will your design system set you up for success? Before we started, we reimagined our design system by developing a new visual language built with design tokens.</li><li>Are there any changes you need to make to your tech stack?</li><li>Are there any critical milestones you’ll need to hit?</li><li>Do you need to reorganize your Product Org to support this mission? If you’re a small to mid-sized company, consider staffing the majority of your product org towards this effort.</li></ul><h3>Step 4: Run a user test every week</h3><p>While the design workshop gave us confidence in the direction we were going, we now needed to bring our ideas up into high fidelity while acknowledging the constraints of our execution strategy. This meant more design iterations, more user testing, and building broad swaths of our application, section by section.</p><p>To drive this process, we set up a cadence to test our designs with users every week. Most weeks looked like this:</p><ul><li><strong>Monday:</strong> Sprint planning and design exploration</li><li><strong>Tuesday:</strong> Design exploration</li><li><strong>Wednesday:</strong> Critique with product design team + prepping for user testing</li><li><strong>Thursday:</strong> In-person user testing+debrief</li><li><strong>Friday:</strong> Iterating based on learnings</li></ul><h3>Step 5: Ship fast, but roll out slow</h3><p>As we rebuilt our application and brought the pieces together, we became very excited to get an end-to-end experience in front of users. However, we knew the first few iterations wouldn’t be ready for primetime, so we set up three phases of roll out:</p><ul><li><strong>Closed Beta</strong> — As soon as it was possible to render a video, we invited a small group of highly engaged users to a Closed Beta. We asked them to make at least one video, then interviewed each user to understand what was successful and where we needed to iterate.</li><li><strong>Open Beta</strong> — In our next stage, we invited a large group of existing users to opt-in to an Open Beta program. We controlled the group size, but using the new product was completely optional. We measured the frequency of opt-outs and also conducted qualitative research.</li><li><strong>Controlled Rollout Test</strong> — Finally, we reached a phase where we felt confident releasing to New Users, to measure how successful users were in making videos, as well as measuring how well we were converting these users to paying subscribers.</li></ul><h3>Step 6: Expect to monetize poorly at first</h3><p>Reaching our first controlled rollout test felt like a huge achievement! We hit our target ship date of Mother’s Day and had virtual drinks with one another. But what we didn’t know at the time, was that this was only Halftime.</p><p>Our first roll-out test was a test against our existing web product, which, for all it’s faults and grievances, was a product with years of optimizations built in. While we were worried about improving the fundamental video creation experience, we under-invested into a number of areas, including:</p><ul><li>New user onboarding</li><li>Upsells and monetization paths</li><li>Ongoing product education</li></ul><p>Be prepared, your first release will monetize poorly! How you react and respond to this adversary will be critical. We took a step back to run a learn cycle and looked through a number of lens:</p><ul><li>When looking at your data, are there any glaring gaps in product usage?</li><li>Using tools such as Full Story, where are users getting tripped up in the experience?</li><li>Comparing the experiences of your new product and old, what is different?</li><li>If you have segmentation data, can you dive into specific audience types and your most common user flows to pinpoint specific areas of pain?</li></ul><h3>Step 7: Migrate existing users with care</h3><p>As we reached our success criteria with New Users and minimized our Opt-out rates in Open Beta, we moved towards migrating our entire user base to Animoto 3. For us, we did not want to carry the legacy cost of supporting 2 versions of the same product. We ran our users through 3 phases of migration:</p><ul><li><strong>Opt-in Migration</strong> — At first, we allowed our entire user base to opt-in on their own accord. They were invited to try our new product, and could jump back between Animoto 2 and Animoto 3 at will.</li><li><strong>Opt-out Migration</strong> — After several weeks, we started the next phase of migration. Upon sign in, we notified users that they will now be using Animoto 3 from here on out. However, we allowed users to opt-out of Animoto 3 by contacting our Customer Success team.</li><li><strong>Full Migration</strong> — After several weeks of low opt-out rates, we made the decision to end access to Animoto 2.</li></ul><h3>Congrats!</h3><p>If you’ve done this successfully, you’ll now have a completely redesigned and rebuilt a product that is a better experience for your customers, and built on a foundation that will help you and your team deliver your vision at lightning speed.</p><p>Have you gone through this process? What lessons have you learned? Please let me know in the comments!</p><p><em>We’re hiring! </em><a href="https://animoto.com/about?utm_source=medium&amp;utm_medium=social&amp;utm_campaign=medium_social-distance&amp;utm_content=medium"><em>Click here</em></a><em> to check out our open roles. Want to learn more about Animoto? </em><a href="https://animoto.com/?utm_source=medium&amp;utm_medium=social&amp;utm_campaign=medium_social-distance&amp;utm_content=medium"><em>Sign up for a free account</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=86572d72ae00" width="1" height="1" alt=""><hr><p><a href="https://medium.com/animoto-blog/inspiration-to-migration-7-steps-to-launch-a-product-redesign-86572d72ae00">Inspiration to Migration: 7 Steps to Launch a Product Redesign</a> was originally published in <a href="https://medium.com/animoto-blog">Animoto</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Social Distancer’s Guide to Working from Home]]></title>
            <link>https://medium.com/animoto-blog/the-social-distancers-guide-to-working-from-home-95aebcf444e5?source=rss----75cf85816582---4</link>
            <guid isPermaLink="false">https://medium.com/p/95aebcf444e5</guid>
            <category><![CDATA[work-from-home]]></category>
            <category><![CDATA[social-distance]]></category>
            <category><![CDATA[tech-companies]]></category>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[remote-working]]></category>
            <dc:creator><![CDATA[Teague LaBrosse]]></dc:creator>
            <pubDate>Mon, 11 May 2020 21:49:00 GMT</pubDate>
            <atom:updated>2020-05-20T17:34:25.964Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_Y23my4y-g_-FoLzis9arQ.png" /></figure><p>To quote one of my favorite books, <em>The Hitchhiker’s Guide to the Galaxy</em>, “DON’T PANIC!” This has been my personal mantra since the start of social distancing. As the People and Facilities Coordinator at Animoto, it has been an interesting transition for me not to be around our people or in our facilities. Fortunately, with the help of my team and our wonderful executives, we’ve managed to keep our company culture alive as we’ve adapted to this new normal.</p><h3>Creating a Space to Work</h3><p>On the first Monday of working from home, our CEO, Brad Jefferson, took the virtual stage at our first entirely remote all-hands meeting. He announced that each employee would receive a $100 stipend to improve our work from home setups.</p><p>Brad also created the #wfhbetterfied Slack channel, so everyone could share their new setups and purchases. Since then, my co-workers have been showing off their new standing desks and monitors, their beautifully decorated work spaces, and of course, the furry little critters that live with them. It’s helped lighten the mood and bring home (literally) how fortunate we are that our company is in position to make such a seamless transition to fully remote work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*l8_AOHSr1seqd2oe" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FFRekaw81ITRISkt" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Z34jwcHzXEs1VY-Q" /></figure><h3>The Struggle is Real</h3><p>Wait a second…$100? No commute? No pants? Working from home sounds nice. And it’s true! But it doesn’t come without its challenges, too. First and foremost: getting out of bed. It’s amazing how much of a motivator catching the train or trying to beat rush hour traffic can be. No longer having that to kick start your morning is hard!</p><p>Our marketing team is a great example of how to get into work mode. They’ve taken to wishing each other good morning when they sign on each day. Then they all join in a 9:45 a.m. video chat, where they share their priorities for the day.</p><p>See that wasn’t too bad, we’ve done it! The rest should be easy! But the challenges don’t stop there. Add a kid or three to the mix, and oh, buddy, it’s a whole new game. Talking with my co-worker, André, about how he and his wife are adapting, he said, “We’re outnumbered! The kids are stir-crazy from being quarantined, so they are extra spicy and hard to manage.” At the other end of the spectrum is another co-worker, Ali, who said, “I have to say, I’m glad they’re older. Most of the time I can leave them alone,” He went on to say, “For me, it’s a few more interruptions, and I have to make them lunch sometimes. They’re probably less work than a dog.” And hey, perception is reality, right?</p><p>If you’re more like André than Ali, try teaching the kids a new game to keep them busy. Some of our parents have done memory games and puzzles for little ones or even chess for the older ones. If all else fails, some snacks and a good book will keep them busy for a while.</p><h3>Keeping the Culture Alive!</h3><p>With this universal craziness and the unique struggles of each employee, I think now more than ever is the time to make sure our company’s culture is not only alive, but thriving. A prime example of this is our long-standing “Welcome Buddy” tradition. Usually this means a current employee takes our most recent new hire out for a nice cup of coffee or tea on their first day before they even make it to the office. We adapted this to a stay-at-home cup of joe, done over a Google Hangout with a few current employees to keep things light and fun. We had to make this adjustment quickly, since we had three new hires starting the first three weeks of our office closure.</p><p>We’ve also started new Slack channels like #healthimoto, which sends out daily reminders to eat and stretch. We still have our 15-minute random one-on-one meetings, but these now take place on our living room couches rather than our office couches. The People Team ordered pre-made snack boxes, with individually wrapped snacks, to be sent out to our employees in the mail as a gift to the company. Our Vice President of People, Jennie Lee, compiled a mental health email, with links to resources for employees to take advantage of. I also put together a Wellness Guide full of fun and relaxing quarantine-friendly activities.</p><p>But most importantly (to me at least), we’ve even found a way to keep everyone’s favorite tradition alive in this time: “Other Demos”. Every other Friday, the aforementioned Ali and assisting team members delight and surprise us all with funny videos, silly games, and unique viewpoints. Our first virtual Other Demos was just that: a virtual version of the Animoto office Ali had created himself. The next time around, he went for a prerecorded news report, with me as his delightfully clumsy co-anchor. Needless to say, Other Demos is the best way to end the week and an even better way to stay joyful.</p><h3>Don’t Panic!</h3><p>Now, I don’t think I made an ultimate guide to the universe and everything, but I do hope this helped ease your mind about the transition to a work from home situation. Working from home can be a sedative to any company’s culture when team members feel isolated from each other. But there are ways to encourage and foster solidarity — even while working from home. Being creative in how you communicate with each other (and having fun with it) can make all the difference. So keep your chin up, stay safe, and hop on Zoom to have a nice chat with a colleague. So long, and thanks for all the fish!</p><h3>Tips for Social Distancing as a Tech Company</h3><p>Here’s the TL;DR for tips from the Animoto People Team.</p><ul><li>Provide a work-from-home stipend to improve employees at-home setups. And let them show off their new work spaces.</li><li>Host a low-stakes morning meeting, just to check in and help team members get into the workflow.</li><li>Keep the kids busy! Challenge them with strategic and memory-based games.</li><li>Create virtual versions of your current traditions.</li><li>Send employees helpful links and articles. The more centralized your list of resources, the better.</li><li>Have fun! Make silly videos, play games. Keep things light for your employees, and they’ll appreciate you brightening up their at-home workday.</li></ul><p><em>We’re hiring! </em><a href="https://animoto.com/careers?utm_campaign=medium_social-distance&amp;utm_content=about-us&amp;utm_medium=social&amp;utm_source=medium"><em>Click here</em></a><em> to check out our open roles. Want to learn more about Animoto? </em><a href="https://animoto.com/?utm_source=medium&amp;utm_medium=social&amp;utm_campaign=medium_social-distance&amp;utm_content=home-page"><em>Sign up for a free account</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=95aebcf444e5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/animoto-blog/the-social-distancers-guide-to-working-from-home-95aebcf444e5">The Social Distancer’s Guide to Working from Home</a> was originally published in <a href="https://medium.com/animoto-blog">Animoto</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making the Leap from Company Values to Company Virtues]]></title>
            <link>https://medium.com/animoto-blog/making-the-leap-from-company-values-to-company-virtues-1b9deede2bac?source=rss----75cf85816582---4</link>
            <guid isPermaLink="false">https://medium.com/p/1b9deede2bac</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[company-values]]></category>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[ceo]]></category>
            <category><![CDATA[team-building]]></category>
            <dc:creator><![CDATA[Brad Jefferson]]></dc:creator>
            <pubDate>Tue, 03 Mar 2020 15:10:26 GMT</pubDate>
            <atom:updated>2020-03-03T21:23:55.142Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ha9awTXpfGddJTRdRMRF1w.png" /></figure><p>Here at Animoto, we believe that strong values are an integral part of company culture. For over a decade, we’ve used company values to bring our team together.</p><p>In 2017, we decided to <a href="https://medium.com/animoto-blog/when-and-how-to-update-your-company-values-6d8fc6bb771f">refresh our values</a> to better reflect our growing team. And now, in 2020, we’ve decided to take it to the next level and start referring to our values as <strong>“virtues.”</strong> In this article, I’ll share some background and explain why we’re taking this leap.</p><h3>Betterfication, Humbletude, and Oomphosity</h3><p>Before I get into why I decided to make the leap from values to virtues, I thought I’d share a little background on what our virtues are — Betterfication, Humbletude, and Oomphosity — and how we came up with them.</p><p>As I mentioned, back in 2017 we introduced our current Animoto values. Before that, our values had been a list of aspirational phrases on a poster — things like “Transparency on all levels” and “Measure, Learn, Improve.”</p><p>The executive team decided it was time for a refresh after reading Patrick Lencioni’s book, <a href="https://www.amazon.com/Advantage-Organizational-Health-Everything-Business/dp/0470941529/ref=sr_1_2?keywords=the+advantage&amp;qid=1582134047&amp;s=books&amp;sr=1-2">The Advantage</a>. In The Advantage, Lencioni talks about the difference between “core values” and “aspirational values.” He explains this difference in a <a href="https://hbr.org/2002/07/make-your-values-mean-something">Harvard Business Review article</a>:</p><p>“<em>Core values</em> are the deeply ingrained principles that guide all of a company’s actions; they serve as its cultural cornerstones… They are the source of a company’s distinctiveness and must be maintained at all costs.</p><p>“<em>Aspirational values </em>are those that a company needs to succeed in the future but currently lacks. A company may need to develop a new value to support a new strategy, for example, or to meet the requirements of a changing market or industry.”</p><p>As an executive team, we realized that our old values were simply an aspirational list of traits on the wall. We wanted our values to truly represent the culture at Animoto. So we brought together the Animoto Management Team for a values brainstorm.</p><p>Each manager was asked to think about the best qualities of specific people on their teams and write them down on sticky notes — humility, creativity, problem solving attitude, etc. Once all the sticky notes were written, we reviewed them all and looked for themes. Then, we molded those themes into values that are unique to Animoto:</p><h3>Betterfication</h3><p>Betterfication refers to a can-do attitude that’s always searching for solutions, not problems. How can we make things better? How can we improve a process? How can we deliver more value to our customers? As a team, we’re constantly striving to “betterfy” — a word you hear quite frequently in meetings and around our office!</p><h3>Humbletude</h3><p>Humbletude refers to our blend of humility and confidence. We take pride in the quality of our work and are confident in our talents — but we’re not jerks about it! Animoto is made up of a team of immensely talented people, but talent and skill are only part of the equation. We’re not precious about our ideas, we’re open to feedback, and we’re constantly learning from each other.</p><h3>Oomphosity</h3><p>Last but not least, oomphosity refers to our commitment to living life with that extra gear. When hiring, we don’t look for a certain type of person, and we don’t try to mold people into a certain type. Rather, we embrace differences and genuinely value and celebrate individuals. It’s the collection of diverse talents, personalities, and qualities that make the Animoto culture and product so unique.</p><h3>Values vs. Virtues</h3><p>The move from <em>aspirational values</em> to <em>core values </em>has been a game changer. For the last three years, the Animoto team has been living these new core values. Betterfication, Humbletude, and Oomphosity have become ingrained in everything we do, including our hiring process.</p><p>But something had been weighing on me. Betterfication, Humbletude, and Oomphosity have become such a strong part of our culture that the word values feels too generic. Then, I read Ben Horowitz’s new book, <a href="https://www.amazon.com/What-You-Do-Who-Are/dp/0062871331">What You Do Is Who You Are</a>, and it clicked.</p><p>In his book, he talks a lot about culture, values, and virtues. He credits the Japanese samurai culture with saying, <strong>“Virtues are what you do, whereas values are merely what you believe.”</strong></p><p>That hit me really hard. The reality is that Humbletude, Betterfication, and Oomphosity have become <em>what we do</em> at Animoto — they are our code of conduct. These three traits are deeper than just our values. They’re our virtues that we live each and every day at work.</p><h3>The leap to virtues</h3><p>In December, at our company’s all hands event in NYC, I shared my intention to start referring to our values as virtues. There’s a deep rationale for <em>why</em> the change makes perfect sense: we don’t just believe in Humbletude, Betterfication, and Oomphosity — we actually live by them. They are our virtues.</p><p>I acknowledged that saying they are our virtues instead of our values goes against convention, so it might feel a little uncomfortable and unfamiliar. It will likely feel a little weird, a little strange — <em>dare I say, a little oomphtastic! ;)</em></p><p>And when we talk about our “virtues” outside the walls of Animoto, it may require a deeper conversation and more explanation about what we mean. But that’s good! That’s exactly why I think this is an important change. I want us to each internalize exactly what our company virtues mean to us. We don’t just believe in the ideas of Humbletude, Betterfication, and Oomphosity; we choose to actively live by them here at Animoto. Referring to them as virtues helps cement their importance in our minds.</p><h3>What are your company’s virtues?</h3><p>In conclusion, I challenge you to think about your company values. Are they just a list of words on the wall? Are they aspirational traits or does your team actually live by them? If you had to come up with a list of virtues for your team, what would they be? Drop a comment below and let me know!</p><p><em>We’re hiring! </em><a href="https://animo.to/38lD99j"><em>Click here</em></a><em> to check out our open roles.</em></p><p><em>Want to learn more about Animoto? </em><a href="https://animo.to/2PIxTWO"><em>Sign up for a free account</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b9deede2bac" width="1" height="1" alt=""><hr><p><a href="https://medium.com/animoto-blog/making-the-leap-from-company-values-to-company-virtues-1b9deede2bac">Making the Leap from Company Values to Company Virtues</a> was originally published in <a href="https://medium.com/animoto-blog">Animoto</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Life as a new hire at Animoto]]></title>
            <link>https://medium.com/animoto-blog/life-as-a-new-hire-at-animoto-b175a959f1a5?source=rss----75cf85816582---4</link>
            <guid isPermaLink="false">https://medium.com/p/b175a959f1a5</guid>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[human-resources]]></category>
            <category><![CDATA[people-management]]></category>
            <category><![CDATA[onboarding]]></category>
            <dc:creator><![CDATA[Kevin Jan]]></dc:creator>
            <pubDate>Mon, 30 Sep 2019 19:27:20 GMT</pubDate>
            <atom:updated>2021-04-02T18:37:25.157Z</atom:updated>
            <content:encoded><![CDATA[<h3>Life as a New Hire at Animoto</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ezbcoR6gCFgDl8aNycr9Cw.png" /></figure><p>Six months ago, I found myself at a crossroads in my career. I had spent two and a half years at a recruiting startup connecting millions of users with jobs they love. Over time, my role expanded from building and executing our email program to managing multiple channels. While I grew both personally and professionally, I missed being hands-on. I was eager to pivot back to my original passion: email marketing.</p><p>Simultaneously, Animoto was looking to backfill an email role for a team member who was transitioning from marketing to engineering. When the VP of People reached out to me, the timing could not have been better. It seemed everything was falling into place.</p><h3><strong>The Interview Process</strong></h3><p>After an initial phone screening with the hiring manager, I was invited to Animoto HQ for in-person interviews. If all went well, the final step would be a <a href="https://medium.com/animoto-blog/the-final-interview-93eea8ce5ab4">30-minute call with CEO Brad Jefferson</a>.</p><p>During my time onsite, I met with five team members across marketing and engineering, and completed two exercises specific to my role. While it may sound like an intense process, it wasn’t. I left feeling energized, with several important takeaways:</p><ul><li>Animoto’s strategic vision</li><li>Animoto’s product roadmap</li><li>Animoto’s customer and their unique needs</li></ul><p>During the conversations, I was able to learn more about each employee on a personal level and realized many shared similar career paths. The entire process took about three weeks, and before I knew it, I was getting ready for my first day at work.</p><h3><strong>Onboarding</strong></h3><p>Before I started, I was introduced to the People Team at Animoto. They were there to help make the transition as smooth as possible and to answer any questions I had. They set me up with an Animoto Professional account (one of the perks of joining the team) and paired me with a “welcome buddy.” It was the first time I had an onboarding process which began before my first day, and it helped calm my new-hire nerves.</p><h3><strong>Animoto Intro Video</strong></h3><p>One of the first things I did as a new hire at Animoto was create <a href="https://animoto.com/play/ZtdruQjx9oT0j5hcnHk0LQ">my introduction video</a>. It’s a fun tradition and rite of passage for anyone joining the team. These 60-second videos show off who you are as a person. It’s also a great way to familiarize yourself with the product and experience how our customers use Animoto. Each video is shown during our weekly Monday Morning Meeting, better known as MMM. If you want to win over the team, including pets is the way to go!</p><h3><strong>Coffee with a Team Member</strong></h3><p>Before the start of my first day, the People Team coordinated a coffee for me and a colleague who has been with the company for 3+ years. He shared his experience at Animoto, the history of the company, and how the product has grown. During our conversation, we chatted about hobbies, and he let me know of people to reach out to who shared similar interests. It was impressive to see how well he knew everyone at the company.</p><h3><strong>My First 30 Days</strong></h3><p>My manager put together a detailed onboarding document with everything I needed to know. It included how our team was structured, who I should meet, who I would be working closely with, meetings I should attend, and the processes in place. My first two weeks were primarily focused on getting up to speed on our tools and getting to know everyone. It was refreshing to see how aligned everyone at the company was, and how they could all speak to past performances, what worked well, what hasn’t, and the potential they saw for email.</p><h3><strong>Conclusion</strong></h3><p>Overall, my experience as a new Animoto hire has exceeded expectations. As I write this, it’s hard to believe that I’ve been with the company for over six months, and I couldn’t be more excited for the future.</p><p><em>We’re hiring! </em><a href="https://animo.to/2nQBG9A"><em>Click here</em></a><em> to check out our open roles.</em></p><p><em>Want to learn more about Animoto? </em><a href="http://bit.ly/2RkqQVj"><em>Get started for free</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b175a959f1a5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/animoto-blog/life-as-a-new-hire-at-animoto-b175a959f1a5">Life as a new hire at Animoto</a> was originally published in <a href="https://medium.com/animoto-blog">Animoto</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Final Interview]]></title>
            <link>https://medium.com/animoto-blog/the-final-interview-93eea8ce5ab4?source=rss----75cf85816582---4</link>
            <guid isPermaLink="false">https://medium.com/p/93eea8ce5ab4</guid>
            <category><![CDATA[ceo-skills]]></category>
            <category><![CDATA[company-values]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[interviewing]]></category>
            <dc:creator><![CDATA[Brad Jefferson]]></dc:creator>
            <pubDate>Tue, 10 Sep 2019 21:14:59 GMT</pubDate>
            <atom:updated>2021-04-02T18:37:44.200Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*48eGKych_zWbzoQkoFAhSA.jpeg" /></figure><p>Before you’re hired at Animoto, you talk to our People Team. Then you talk to the hiring manager. If those conversations go well you come into the office and you talk to them again, along with other members of the team you’d be joining. If all of <em>those</em> conversations go well, too, then you talk to me.</p><h3>Why I interview candidates</h3><p>Why do I, the CEO, interview all potential new hires? There are two main reasons that I’ll dive into in this post, but the simple answer is that it’s about company culture. If you’ve made it to that point in the interview process, I know you’re good at what you do. I’ve read your resume, I’ve jotted down a few notes.</p><p>Your experience and skills are, of course, crucial to success here, but one of my responsibilities is making sure that every new person who joins the company can thrive in the environment we’ve built.</p><p>We want people who are qualified not just to participate in what we have here, but to build upon it and help propel us forward. Without further ado, here’s the “why” behind my interviews.</p><h3>Our culture is set by our employees</h3><p>Company culture can be a tricky thing to nail down. Between our executive team, longtime employees, new hires, interns, and everyone in between, there are a ton of moving pieces, each with a role to play. That said, culture can’t stem from just any one person.</p><p>Culture isn’t just about how you interact with your coworkers, or breaking out the ping pong table after work, or happy hours or trivia nights or any single activity. Culture is the environment that you walk into every day. It’s how you understand what’s expected of you. It’s how you think about how to deliver on that expectation. We’re working to create an environment where people can do the best work of their lives, and culture can make the whole greater than the sum of its (very talented) parts.</p><p>Ultimately, we’re looking for people who are a ‘values fit’ with our team. Here are Animoto’s company values that we hold dear:</p><ul><li><strong>Humbletude</strong>: The balance of the humility needed to hear and respect other people’s ideas and the confidence necessary to advocate for your own</li><li><strong>Betterfication</strong>: A hunger for solutions, not problems</li><li><strong>Oomphosity</strong>: A passion for life, with interests both inside and outside of work, and the ability to bring that passion to work everyday</li></ul><p>When I conduct my interview, I want to find out more about what motivates you, both professionally and personally. Are you naturally curious? What are the things that you can’t stop talking about? Do you have a fixed mindset or a growth mindset? Are you more of a consumer, or a creator? And, ultimately, do you embody the values that we hold dear as a company?</p><h3>Accountability and openness</h3><p>It’s not lost on me that, at first glance, an interview with the CEO sounds a little intimidating. But truly, that’s not the point. When you join a new company, there are a million things to get adjusted to. New coworkers, new manager, new workflows, a new place you go to work every day.</p><p>With our conversation, we cross one adjustment off that list. If you work here, we’re going to be working together. From day one, I’m a point of contact for you, and someone you should feel confident coming to.</p><p>Our conversation should establish a line of communication that bridges the gap between your interview process and your time at Animoto, which I do my best to continue nurturing in a few different ways.</p><ul><li>First, I hold welcome breakfasts outside the office with all new hires shortly after they start with us.</li><li>Second, I host a monthly Q&amp;A session (formerly Ask Brad Anything, now Bradical Candor) where all Animoto employees can submit questions anonymously for me to answer. There are always silly questions; there are always serious questions, but every single one is a chance for the team to make their feelings known, and for me to get better as a CEO. I actually have a whole post about these Q&amp;As so if you’re curious about the details behind why we do it (and how to conduct them if you’re in a position to do so) you can <a href="https://medium.com/animoto-blog/the-ceo-in-the-hot-seat-why-i-recommend-getting-grilled-by-your-employees-and-the-best-way-to-do-ed32b5c81f13">check that out here</a>.</li><li>Third, I do my best to make myself available whenever possible. I’m based in San Francisco, but make frequent trips into New York to work out of our main office. While I’m there, I host lunches in our conference rooms where all are welcome to come chat with me, and in general I try to keep time on my calendar for 1:1 conversations with anyone who needs the time.</li></ul><p>It’s incredibly important to me that everyone at Animoto feels comfortable coming to me with any questions, suggestions, or concerns that they may have. We have a ton of incredibly smart, talented people at Animoto, and I don’t believe that walling myself off from their points of view is the best way to take advantage of all they have to offer.</p><p>All of this is to say that while part of the goal of my final interview is to establish whether candidates will make strong cultural additions to our team, it is just as much about setting the tone around openness and accountability that we maintain at Animoto. I’m getting to know you during our talk, but I expect you to be just as curious about me, and that first conversation establishes a connection that I want you to take full advantage of here.</p><h3>Final Thoughts</h3><p>As the CEO of Animoto, the buck stops with me. I like having a connection with every single person we hire at Animoto and I like that I can respond to any final questions that our candidates may have. I like to talk about our company vision, mission, and our future, to make sure candidates understand who Animoto is today and where we’re going. I want to make sure that’s motivating to people who join Animoto. Any edge that I can bring with a little extra insight to excite potential team members is a fully worthwhile endeavor.</p><p>We go after the top talent in our space. Since there will always be a competitive market for the individuals we seek to hire at Animoto, every step of the recruiting and interview process is a chance to set Animoto apart. We think about all aspects of the recruiting and interviewing journey at Animoto and our final CEO interview is an easy step that frequently sets Animoto apart from other companies and offers.</p><p>To be honest, I sometimes find myself wondering why more CEOs don’t conduct candidate interviews. When it comes down to it, at a company of our size, I’m called upon only a handful of times a month, and it is a <strong>very </strong>good use of my time. It’s a small investment in building relationships with each and every Animoto employee from day one, and it’s one that I’m thrilled to make. Further, if you’re interviewing with Animoto and receive an offer, you should have the confidence that everyone at Animoto believes you’ll be successful here, from your future peers, to your future manager, and to me, the CEO.</p><p><em>We’re hiring! </em><a href="http://bit.ly/36gRToN"><em>Click here</em></a><em> to check out our open roles.</em></p><p><em>Want to learn more about Animoto? </em><a href="http://bit.ly/2RkqQVj"><em>Get started for free</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=93eea8ce5ab4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/animoto-blog/the-final-interview-93eea8ce5ab4">The Final Interview</a> was originally published in <a href="https://medium.com/animoto-blog">Animoto</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 big lessons on organizational design maturity]]></title>
            <link>https://medium.com/animoto-blog/3-big-lessons-on-organizational-design-maturity-461a6d73a7b5?source=rss----75cf85816582---4</link>
            <guid isPermaLink="false">https://medium.com/p/461a6d73a7b5</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[organizational-structures]]></category>
            <dc:creator><![CDATA[Kristen Connor]]></dc:creator>
            <pubDate>Thu, 15 Aug 2019 19:26:51 GMT</pubDate>
            <atom:updated>2021-04-02T18:36:17.179Z</atom:updated>
            <content:encoded><![CDATA[<h3>3 Big Lessons on Organizational Design Maturity</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XTPtWuNgt7Q07p7kLXQgJA.png" /><figcaption>Illustration by Ryan Stec</figcaption></figure><p>On June 13, 2019, Animoto hosted a roundtable discussion about <em>organizational design maturity</em>. This term was introduced in a 2018 InVision report called “<a href="https://www.invisionapp.com/design-better/design-maturity-model/">The New Design Frontier</a>”, and it refers to how thoroughly a company has committed to industry-recognized design practices, where design thinking is integrated and valued at the highest levels of the organization.</p><p>This article provides a quick summary of the report, a recap of the event, and 3 big lessons that emerged from our discussion.</p><h3>Report summary</h3><p>If you haven’t read it yet, <em>you should</em>. I’ve spent years of my design career advocating for companies to invest in strong design practices — and this is one of the most effective and well structured arguments I’ve encountered.</p><p>InVision generated the report from a survey of designers in 2,200+ organizations to explore how companies can create better business outcomes with design. It states that “<em>companies with high design maturity see cost savings, revenue gains, and brand and market position improvements as a result of their design efforts</em>.”</p><p>This finding remained true regardless of industry, location, and company size. Yet, of the organizations surveyed, “<em>just 5% are empowering design for the greatest benefits, and 41% have significant room to grow</em>”.</p><p>The report identified 5 levels of design maturity. At level 1, design is reduced to the way things look. Progressing up the ladder, design is increasingly viewed as the approach by which we can deliver value and delight our users. This culminates at level 5, where design becomes equivalent to strategy — great customer experience is critical to achieve great business results.</p><p>This framework provides an easy reference point for companies to evaluate their current state, and think about how they might advance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YEnwzFk35X36dDUHXfKv5Q.png" /></figure><h3>Event overview</h3><p>The purpose of the event was to discuss organizational design maturity among designers from a diverse group of companies, and understand how the concepts apply within various industries, company sizes, and design orgs.</p><p>I moderated the discussion — I’m Kristen Connor, Head of Design at Animoto. Attendees included product and user experience (UX) designers from top New York companies, such as:</p><ul><li>Animoto</li><li>Designation (now WeWork)</li><li>Dropbox</li><li>Equinox</li><li>Perch</li><li>Warner Bros. Digital Labs</li><li>ZocDoc</li></ul><p>We broke the discussion into 3 major sections, each with a handful of sub-questions:</p><ul><li>Do the five levels resonate with your experience working in design orgs?</li><li>What design organizations do you admire for their design maturity?</li><li>Have you been a part of an org that has raised its design maturity?</li></ul><h3>3 big lessons</h3><p>Our discussion was really engaging and fun, and I learned a lot. I’m grateful to the designers who spent a rainy morning in June with us at Animoto, lending their insights and experiences.</p><p>After letting it all sink in, I came away with 3 big lessons I think could be valuable to other design organizations.</p><h4>1. The levels aren’t precise, but offer a valuable yardstick</h4><p>It’s common for companies to exhibit characteristics of multiple levels within the framework.</p><p>For example, at a level-1 org (where design is viewed as what happens on screens) — the team may start to advance its design maturity by introducing such practices as collaborative design sessions with stakeholders (which is a trait of level 2), or even start to document some guidelines (typical of level 3).</p><p>A level-3 company (which has a well established, documented design system), might be stretching into some level-4 behaviors (e.g., establishing strong testing methods). And it also might be lagging behind in some areas, like having a lack of structure in capturing stakeholder input (which is common to level 2).</p><p>Even the most advanced companies represented at our roundtable (levels 4 and 5) indicated there are pockets of level 1 thinking in their companies. Designers must provide constant education about the value of design maturity.</p><p><strong>How to apply this lesson</strong></p><p>While identifying an exact “score” isn’t realistic or particularly useful, the levels can serve as a yardstick that everyone can understand. Use the yardstick to assess current-state design maturity. Discuss the practices identified at each level to identify strengths and areas of improvement in your org. You can also use this yardstick to chart a path to greater design maturity by identifying initiatives that will help achieve higher levels.</p><h4>2. Executive support is required to achieve level 5</h4><p>Consistent with the Invision report, our participants agreed that organizations with level-5 design maturity are extremely rare. But such companies do exist, and level 5 is attainable <em>IF</em> (big <em>IF</em>) executive leadership not only understands design as strategy, but actively expects all employees to play a role in delivering a great customer experience.</p><p>We discussed companies we admire for their emphasis on design and customer experience — for example, Apple, Amazon, and Zappos. In each of these companies, the founders (Steve Jobs, Jeff Bezos, and Tony Hsieh respectively), were/are ardent evangelists for great customer experience.</p><p>Here are a few quotes:</p><ul><li><em>“You’ve got to start with customer experience and work backward to the technology.”</em><br>- Steve Jobs</li><li><em>“If there’s one reason we have done better than our peers…, it is because we have focused like a laser on customer experience.”</em><br>- Jeff Bezos</li><li><em>“We decided a long time ago that we didn’t want our brand to be just about shoes… we wanted our brand to be about the very best customer experience.”</em><br>- Tony Hsieh</li></ul><p>At our roundtable discussion, one of our participants was representing a well known, publicly traded, level-5 company. When we discussed how the organization reached the highest level of design maturity, this participant noted the founders had studied design as part of their computer science education, and actively expected strong design thinking.</p><p>This raised a question: If a company didn’t start out with customer experience at its core, is it even possible to achieve level 5? I believe the answer is yes — if executive leadership grows to embrace the value of design thinking, and works to change the culture. Over time, leadership must set increasing expectations that everyone in the company should play a role in creating a great customer experience.</p><p>Here’s one last quote, from Animoto’s co-founder and CEO, Brad Jefferson:</p><ul><li><em>“User experience isn’t only a design-team thing, it’s an every-team thing.”</em><br>- Brad Jefferson</li></ul><p><strong>How to apply this lesson</strong></p><p>If you work for a company whose founders and/or executive leaders fully embrace design as strategy, you’re in great shape. Share the organizational design maturity framework with them. Seek their help in charting a path to reach (or maintain) level 5. They will likely be willing to sponsor initiatives that seek to achieve the business benefits that come along with level-5 maturity.</p><p>If you work for a company whose founders and/or executive leaders are not yet on board, it’s time to roll up your sleeves and get to work. Focus on making the case to your exec team for investing in organizational design maturity. (More on how to make the case in lesson 3.) Persistence and resilience will be required, but the effort is worthwhile, as executive support is a key to achieving level 5.</p><h4>3. The business case is critical</h4><p>To earn the support of executive leaders (and other colleagues), it’s critical to make a results-focused, measurable business case for investing in design maturity. That’s part of what makes “<a href="https://www.invisionapp.com/design-better/design-maturity-model/">The New Design Frontier</a>” so effective. As noted, the study found that “<em>companies with high design maturity see cost savings, revenue gains, and brand and market position improvements as a result of their design efforts</em>.” It breaks this down in the Analysis section of the report.</p><p>Other studies support this finding. For example, McKinsey tracked the design practices of 300 public companies over a five-year period. The results were published in an October 2018 article called “<a href="https://www.mckinsey.com/business-functions/mckinsey-design/our-insights/the-business-value-of-design">The business value of design</a>”.</p><p>The report states:</p><ul><li><em>There is a strong correlation between strong design practices and superior business performance.</em></li><li><em>Business performance of companies with the strongest design practices (top quartile) was disproportionately greater than the other three quartiles.</em></li><li><em>The results held true across companies producing physical goods, digital products, services, or some combination of these.</em></li></ul><p>These studies from reputable sources can be effective tools to make the business case for design maturity. They are even more effective when combined with internal practices to measure and communicate the impact of design within your organization.</p><p><strong>How to apply this lesson</strong></p><p>Every company’s culture is different. Some companies adopt new ideas by way of reading and discussing outside, reputable sources of information. Other companies are more practically oriented, and prefer to rely on results produced by real projects within their organizations.</p><p>Most often it’s a combination of both tactics that drives new ways of thinking. To start to make the case for the business value of design, why not share reports like the “<a href="https://www.invisionapp.com/design-better/design-maturity-model/">The New Design Frontier</a>” and “<a href="https://www.mckinsey.com/business-functions/mckinsey-design/our-insights/the-business-value-of-design">The business value of design</a>” with company leaders? Invite them to have lunch, and discuss the articles. Talk about how the concepts apply to your organization.</p><p>Meanwhile, start implementing practices within the design team at your company that can lead to a greater understanding of design’s impact on business results. Here are a few examples, ranging from simple to complex — make sure designers present work at end-of-sprint demos; whenever designers communicate to stakeholders, connect the dots between design decisions and success metrics; implement a structured framework for assessing the impact of new features on the user experience; and when establishing KRs/KPIs (or whatever tool your company uses), include measurements of the impact on customer experience.</p><h3>Let’s continue the discussion</h3><p>We are so thankful to the designers from Designation (now WeWork), Dropbox, Equinox, Perch, Warner Bros. Digital Labs, and ZocDoc for joining us at the roundtable discussion about organizational design maturity.</p><p>I took away many new ideas about how we can continue to improve our design maturity at Animoto, where we make tools for small business owners to create professional marketing videos that stand out on social media. The InVision framework has been a great tool in guiding our internal discussions and I’m excited to get to work on some of these new ideas.</p><p>I’d love to know how other designers are making progress within their own organizations. Are there are reference articles, books, or other materials that are helping you raise the profile of design in your company? Have you had any great successes that can help other design orgs improve? Let me know. I’d love to hear from you.</p><p><em>We’re hiring! </em><a href="https://animo.to/30qNhvf"><em>Click here </em></a><em>to check out our open roles.</em></p><p><em>Want to learn more about Animoto? </em><a href="https://animo.to/2u9wX5Q"><em>Get started for free</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=461a6d73a7b5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/animoto-blog/3-big-lessons-on-organizational-design-maturity-461a6d73a7b5">3 big lessons on organizational design maturity</a> was originally published in <a href="https://medium.com/animoto-blog">Animoto</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tips for Creating a Nimble Customer Operations Team]]></title>
            <link>https://medium.com/animoto-blog/tips-for-creating-a-nimble-customer-operations-team-6d04e6af8432?source=rss----75cf85816582---4</link>
            <guid isPermaLink="false">https://medium.com/p/6d04e6af8432</guid>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[customer-obsession]]></category>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[customer-engagement]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Brittany Bishop]]></dc:creator>
            <pubDate>Wed, 10 Jul 2019 19:45:58 GMT</pubDate>
            <atom:updated>2021-04-02T18:35:46.320Z</atom:updated>
            <content:encoded><![CDATA[<h3>How We Stay Nimble as a Customer Operations Team</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0WskyebPOAbDXe5U1OseWQ.png" /></figure><p>At Animoto, we’re always working towards the next improvement to our product. With multiple product teams all working on releases and tests for our web and mobile app, there is a lot that can change on Animoto.com from day to day. Our Customer Operations team is on the front-lines with our customers, so making sure we are equipped to help our customers and prepared for anything is a must.</p><p>In this article, I’ll dive into what Customer Operations means at Animoto. Plus, I’ll share some of the ways our team works with the rest of the teams at Animoto to stay nimble and help our customers find success with our product.</p><h3>What is Customer Operations?</h3><p>Customer facing teams can take all forms and shapes within a company. At Animoto, the heart of Customer Operations is rooted in supporting people. While other teams at Animoto use communications with customers to align with the company’s needs (e.g. user research for better product decisions) the Customer Operations team is aligned with the customer’s needs and acts as the human representation of the company at operational moments when the customer interacts with us.</p><p>Rather than three separate teams with individual goals, we’ve joined the forces of sales, support, and success together to create a super-powered operations team whose goals align around the entire customer journey. While other teams in the company are zoomed in on improving a specific piece of the product or a customer experience, the Customer Operations team has a holistic view of our customers and understands what success looks like for them.</p><p>A healthy mixture of knowledge-sharing and flexibility are the secret sauce to keeping the team prepared and providing stellar support.</p><h3>Knowledge Sharing</h3><p>To make sure that we’re getting information to and from the Customer Operations team at the right times, we prioritize in-person and virtual touchpoints to connect and collaborate.</p><h4>Go where the knowledge is</h4><p>To maximize the use of our in-person interactions and to make sure we’re never creating unnecessary calendar clutter, we look for established meetings where information is already flowing and then add in a representative from the Customer Operations team. This approach has been especially fruitful with our product teams that already have multiple review meetings to discuss learnings and roadmaps.</p><p>By adding a member of the Customer Operations team to sprint review meetings and product stakeholder meetings, we’ve created longer lead times for the team to prepare for upcoming changes and cleaner opportunities for questions and feedback.</p><h4>Write it down</h4><p>The Customer Operations team has a healthy mix of preferred learning styles, but one thing we all agree on is that having documentation can save us valuable time when we are addressing customer concerns or troubleshooting something. Luckily, the whole Animoto team loves documentation as much as we do!</p><p>What makes this knowledge sharing option so appealing for us is that our preferred documentation platforms all have collaboration tools built right in. When sharing documents, we set time limits for open comments, but allow conversation to build naturally during that time. This transparency not only gives us a document to come back to for questions in the future, but also lets us understand what important conversations were happening when the document was created, long after the team has moved on to something new.</p><h4>Organize it</h4><p>The one downfall to all those collaborative documents is that they can be difficult to wade through when we are looking for a very specific piece of information. To combat that, our Customer Operations team has built an online documentation hub that groups key documents based on our own areas of expertise together for easy finding. Once a quarter we review all of those documents to make sure we aren’t hanging onto incorrect documentation that could cause confusion later. We also call out knowledge gaps in our hub so that team members can be assigned to track down or create the missing documentation.</p><h3>Flexibility</h3><p>Thanks to all the knowledge sharing we do across the company and within the team, we are able to anticipate what we <em>think</em> will happen when something goes live or how we <em>think</em> our customers will respond to something. Even so, we often have to wait and see what our customers will actually do or say, so we focus on preparing for what we can predict and leave room for flexibility for the things we can’t.</p><h4>The art of staying unattached</h4><p>When we know a significant change is coming we start by gathering any documentation that currently exists. If there isn’t any documentation, we create it! The majority of our preparation documents include tidbits of knowledge and content from various team members. In most situations, compilation documents can cause headaches, but for the Customer Operations team the more information we can gather the better. The closer we get to a launch the more organized our documentation gets, but we never consider our documentation totally complete.</p><p>We also gather the team and write starter responses to questions we predict we will receive when we know a release will drive customer inquiries. Most of the time we pour energy into crafting just the right responses to our customers, but when we are writing up starter responses we push ourselves to not get attached.</p><p>Having a draft to work off makes sure we aren’t starting from scratch for every new customer response, but also gives us the breathing room to send a response that matches the customers needs in the future.</p><h4>Pause when needed</h4><p>As they say, preparation is only half of the battle. No matter how much information we’ve gathered or how much knowledge has been shared there is always a possibility something unexpected will be waiting for us when we start working with customers after a release. If we discover that we do not have the proper tools or knowledge to support our customers at any point in time, we aren’t afraid to call a timeout.</p><p>When customer inquiries are pouring in, taking the time to talk face to face might feel like losing valuable time, but what we’ve discovered is that taking the time to meet and get on the same page as a team ensures we are all delivering consistent support for our customers.</p><p>During these timeouts, we focus on what we can change, not what we can’t. That often leaves us with a short, impactful to-do list that allows us to divide any work or research that is necessary for our success and gets us back to focusing on our customers quickly.</p><h4>Must love adventure</h4><p>Our hiring process also plays a huge role in ensuring the Customer Operations team is set up for success in moments when things are changing quickly. We’ve hired to make sure we have a room full of folks that not only know how to define success, identify the challenges, and troubleshoot for solutions but also feel a little thrill when a new challenge pops up.</p><p>We define that as a love of adventure and we’ve got a special set of interview questions that help us suss out just how adventurous a candidate is. The goal is to find a new hire that is excited about coming to work each day, at least in part because they don’t know what might be waiting in their inbox.</p><h3>In Conclusion</h3><p>While the rest of our team has their eyes on the future, we rely on our Customer Operations team to know about and guide our customers through the things they are experiencing right now. To ensure that our team can deliver on the success we all want our customers to have, we all put in the work to make sure we are sharing knowledge with the Customer Operations team early and then giving them the space to stay nimble when it matters most.</p><p><em>Sound good to you? Join our team, </em><a href="https://animo.to/2O9K2U7"><em>we’re hiring</em></a><em>!</em></p><p><em>Want to learn more about Animoto? </em><a href="https://animo.to/2Gog36d"><em>Get started for free</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d04e6af8432" width="1" height="1" alt=""><hr><p><a href="https://medium.com/animoto-blog/tips-for-creating-a-nimble-customer-operations-team-6d04e6af8432">Tips for Creating a Nimble Customer Operations Team</a> was originally published in <a href="https://medium.com/animoto-blog">Animoto</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Animoto uses data to create a culture of customer-focused decision making]]></title>
            <link>https://medium.com/animoto-blog/how-animoto-uses-data-to-create-a-culture-of-customer-focused-decision-making-5572652dbe15?source=rss----75cf85816582---4</link>
            <guid isPermaLink="false">https://medium.com/p/5572652dbe15</guid>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[data-analytics]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[customer-engagement]]></category>
            <category><![CDATA[business-analytics]]></category>
            <dc:creator><![CDATA[Analytics @ Animoto]]></dc:creator>
            <pubDate>Thu, 02 May 2019 19:44:33 GMT</pubDate>
            <atom:updated>2021-04-02T18:35:13.927Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YTkpjAc6pN6pRl5Mqa0ttw.png" /><figcaption>The Animoto Analytics team — Alex Beskin (left) and Jason Bellinger (right)</figcaption></figure><p>At Animoto, we strongly believe in a data-driven culture. Since our main goal as a business is to make it as easy as possible for our customers to create professional videos, we try to focus on customer-centric data to inform much of our decision making. The path for growing our business goes through improving the customer experience, engaging users, and making the process of creating videos as easy as possible. To do this, we have to look at data from a myriad of different angles. In this post, we will outline some of the strategies we use.</p><h3><strong>Keeping everyone in the company informed as to how our customers are using the product</strong></h3><p>Transparency is a big part of how we operate at Animoto. From the data side of things, this means keeping everyone up-to-date on how we are trending in important metrics and KPIs like sales, lifetime value (LTV), churn, new subscriptions, and monthly active users (MAU). But most importantly, we keep everyone in the loop as to how our customers are actually interacting with the product.</p><p>How are users interacting with certain features within the product? And how do these features result in the number of videos they create? We have dashboards and reports showing this type of data — and everyone at Animoto has access to them. We look at every possible metric that we feel might benefit our users — from how much time it takes to finalize their very first video to how many assets they add and what template they use. We strongly feel that every metric, every customer generated event, and every interaction the user has with the product is important to understand. Knowing our customer’s product usage behavior helps our product team to come up with ideas for future improvements to the product.</p><h3><strong>‘Data-Gatekeeper’ to ‘Data-Enabler’</strong></h3><p>Curiosity among Animoto team members and accessibility of data was the main reason why Animoto was one of the early adopters of Looker, a reporting and business intelligence (BI) tool. To support our growing, customer-focused team, the Analytics team morphed from a ‘data-gatekeeper’ to a ‘data-enabler.’ Inspiring curiosity allows our marketing team, designers, developers, and product owners to not only start asking questions, but also have fun diving into the data.</p><p>One of the initial challenges for the analytics team when enabling access to the data was overcoming the fear that the data would be misused or misinterpreted. And that business owners would draw “wrong conclusions”’ from the data that would lead to questionable decisions. To overcome this fear, the analytics team heavily invested in training and coaching business owners by creating a special “data onboarding program” for new employees. While there is always the inherent risk that data can be misinterpreted, the benefit of data democratization outweighs the risk.</p><h3><strong>Analyzing the Customer Journey</strong></h3><p>Many companies rely on click-stream data to see how their users are interacting with the various features of their product or website. And Animoto is no different. We utilize our event tracking data to help us understand the journey that our users take from hitting our website for the first time, to creating their very first video, and beyond. By looking at all these data points, we can identify trends that show which features or behaviors are highly correlated to a user being successful — which in our case means creating stunning marketing videos. Once we identify these trends and behavioral patterns, we can better tailor the experience to benefit our users. In some cases, understanding the customer journey can help us identify big opportunities for improvement, but most of the time we’re using it to find small incremental enhancements to our product or user flow.</p><h3><strong>A culture of testing</strong></h3><p>While jumping into the deep end can be thrilling…it’s not the best strategy in a business context. We have a lot of ideas swirling around in our heads about how to make the customer experience better (some better than others). And the most effective way to determine whether these ideas are winners or not is to test them out…and to look at the hard data that results from them.</p><p>In 2016, we introduced a new product for creating marketing videos. Before we launched, we tested every detail of it to see how customers reacted. And we used those results to inform the direction that we took with the product. We make it a priority to test nearly every change we implement, however small — from the color of button to the layout of a landing page. Doing so allows us to make changes that benefit both the customer <em>and</em> the business — a win-win!</p><h3><strong>Quality of data over quantity of data</strong></h3><p>Not all data is created equal. Many companies collect data simply for the sake of collecting data. We used to be the same way. But this doesn’t necessarily lead to better insights or better decision making. We were gathering millions of rows of data each day and only using a fraction of it to inform decisions. The key to reducing this “data bloat” is to decide which metrics are the most beneficial to the overall business, and ultimately, the customer. Is knowing something like how many pages a user viewed before signing up informative? If so, track it. But if something is not so important, like how many seconds a user was on a particular page for example, then don’t waste any time or resources looking at it. Narrowing down the amount of data you look at makes decision making that much easier.</p><h3><strong>Listen to our customers</strong></h3><p>Even though Animoto as a company is heavily reliant upon data and metrics, the last piece of the puzzle is a tried and true method — actually listening to our customers! We have fantastic customers who are incredibly passionate about our product and creating videos, and they have insightful feedback and ideas about our product because they are the ones constantly using it. If there is a feature improvement that they think is a good idea, we give it heavy consideration (and then we test it). It is important to not lose sight of the ultimate goal of your company — to serve your customers. If we solely focused on quantitative data points to make our decisions, we would be doing a disservice to our customers and missing out on qualitative data that we wouldn’t be able to get anywhere else.</p><p>As Animoto moves forward and grows as a company, we are always on the lookout for more ways to improve the experience for our customers and strengthen our business. Data plays an integral role in both of these objectives and is the foundation of much of our decision making. By empowering everyone in the company to have direct access to this data, we can be absolutely sure that we are moving in the right direction as a collective group.</p><p><em>We’re hiring! </em><a href="https://animo.to/2RjYriq"><em>Click here</em></a><em> to check out our open roles.</em></p><p><em>Want to learn more about Animoto? </em><a href="https://animo.to/2Gog36d"><em>Get started for free</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5572652dbe15" width="1" height="1" alt=""><hr><p><a href="https://medium.com/animoto-blog/how-animoto-uses-data-to-create-a-culture-of-customer-focused-decision-making-5572652dbe15">How Animoto uses data to create a culture of customer-focused decision making</a> was originally published in <a href="https://medium.com/animoto-blog">Animoto</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>