<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Olark on Medium]]></title>
        <description><![CDATA[Stories by Olark on Medium]]></description>
        <link>https://medium.com/@olark?source=rss-f218a12fa80f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*AXqW3zjZ5URKRR9JfSDptg.png</url>
            <title>Stories by Olark on Medium</title>
            <link>https://medium.com/@olark?source=rss-f218a12fa80f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 02:42:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@olark/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Toward Accessible AI Chatbots: Olark’s Annual Report for GAAD (Year 3!)]]></title>
            <link>https://olark.medium.com/toward-accessible-ai-chatbots-olarks-annual-report-for-gaad-year-3-b1afcdc0dec0?source=rss-f218a12fa80f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1afcdc0dec0</guid>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Olark]]></dc:creator>
            <pubDate>Mon, 13 May 2024 15:02:19 GMT</pubDate>
            <atom:updated>2024-05-13T15:02:19.075Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Global Accessibility Awareness Day (GAAD) is this Thursday, May 16! </strong>Did you know that this event kicked off <a href="https://accessibility.day/about/">based on a single blog post written by web developer Joe Devon — and a subsequent tweet seen by accessibility professional Jennison Asuncion</a> — 13 years ago? The fact that GAAD is bigger and better than ever is a testament to the power of the a11y community, of which we’re proud to be a part.</p><p>It’s a reminder of the power of a few individuals to start — and grow — important movements like this one by persisting for years. And with the humble blog post, no less! (Bloggers, take note?)</p><p>At Olark, GAAD is a special day. Inclusiveness is at the heart of our mission. We believe every person deserves access to the essential digital tools that make up our world. Speaking of persistence… it’s been seven years since we <a href="https://olark.com/speak/olarks-a11y-journey-how-our-people-and-our-values-pushed-us-to-build-better-products-for-all">first identified accessibility as a priority</a> for Olark chat, and three years since we started <a href="https://olark.com/speak/olarks-a11y-journey-how-our-people-and-our-values-pushed-us-to-build-better-products-for-all">publicizing our accessibility commitments</a>. It feels good to be on this path!</p><p>This year AI also made huge waves in our industry. We are responding with an accessible-first mindset and are super proud of our team.</p><h3>Let’s see how far we’ve come…</h3><p>During the first few years of our accessibility journey, we were laying the foundation. We established best practices with our engineering and product teams, got familiar with terms, put together training. <strong>This year, it feels like accessibility is baked into our processes. </strong>Instead of developing everything from scratch, we’re in a groove, taking the next steps we know we need to take.</p><p>The last year has been a whirlwind. We launched an accessible signup process for Olark, attended multiple accessibility events, and even brought in the producer of the film <a href="https://surpassingsightmovie.com/">Surpassing Sight</a> — a documentary about two blind cyclists — for a discussion of his film with our team at our offsite in Austin, Texas.</p><p>Sometimes it’s hard to see just how far we’ve come until we sit down and reflect on the progress we’ve made. <strong>Many micro-actions add up to a web of impact.</strong></p><p>We hope sharing what we’ve been doing and learning will support you on your accessibility journey too. <strong>Below, check out our scores on last year’s accessibility commitments and our new commitments (plus some lessons learned!).</strong></p><p>Let’s get this party started!</p><h3>Our 2023 Commitments: How did they go?</h3><p>Last year, we set eight accessibility goals (our most ambitious number yet!). Here’s how we’re scoring our performance and what we did to meet each goal.</p><p>Rating scale:</p><ul><li>GREEN: We did what we set out to do and maybe even did more than we’d planned.</li><li>YELLOW: We made meaningful progress, but we have a ways to go.</li><li>RED: We aren’t satisfied with the progress.</li></ul><p>__</p><p>Commitment #1: <strong>Offer an end-to-end accessible experience for everyone. All Olark users, new and existing, have access to this experience: GREEN, AND IN PROGRESS</strong></p><p>ORIGINAL 2023 GOAL: <em>Olark is accessible for chatting both on the customer and agent-side, and most agent-side functionality is also accessible. But there is still the last mile: account settings, reporting, and some dashboard screens are not yet accessible. For example, you can’t yet change the color of your chat box using a screen reader. We’re excited to make Olark accessible in its entirety with this goal.</em></p><p>Our chatbox was already accessible in many ways. But as mentioned in our original goal, we’ve been hard at work over the last year addressing that last mile: building an end-to-end, fully accessible experience. One highlight is a brand-spanking-new accessible agent console, with some new settings, account management features like login, and improved password management. We’ve also swapped in the new accessible login flow, even for classic users! In-app notifications now stay on the page longer and have more options to dismiss or not. As well, the chat box theme can be changed with a screen reader now. <a href="https://changelog.olark.com/">You can check out detailed updates in our changelog</a>.</p><p>Based on user feedback, we made numerous smaller upgrades, relating to text legibility, dark mode, Zoom compatibility with increased text size, and more. We say this is green and still in progress because we haven’t rolled the new version out to every existing customer yet. But soon!</p><p>Commitment #2: <strong>Monitor what’s coming for WCAG 2.2 and externally share our journey engaging with the changes: YELLOW, ALMOST GREEN</strong></p><p>ORIGINAL 2023 GOAL: <em>The World Wide Web Consortium (W3C) releases regular updates to its WCAG accessibility standards, sometimes as a draft before formally approving. We’re keeping an eye on how the next version impacts our chatbox. Our aim is to keep ahead of the curve and plan for addressing the next standard. With all that we’ve learned (and keep learning) we think we’ll be in great shape.</em></p><p>We’ve been looking ahead to what will eventually become the new standard in accessibility. Our accessibility engineer, Lee, has been monitoring what’s coming for the next version, <a href="https://www.w3.org/TR/WCAG22/">WCAG 2.2</a>. (She also got <a href="https://olark.com/speak/olarks-q3-2023-accessibility-progress-report">certified as a Web Accessibility Specialist</a> by the International Association of Accessibility Professionals… congrats, Lee!) Our first plan is to audit the target sizes of buttons and links and modify if any are too small. This commitment is yellow because we haven’t shared our journey externally yet.</p><p>Commitment #3: <strong>Report accessibility issues quarterly in a public way: SOLID GREEN</strong></p><p>ORIGINAL 2023 GOAL: <em>We started this goal in 2021, and we’re recording it again because we’re going to keep doing it. We plan to make the reporting easier to find as well.</em></p><p>Every quarter, our teammates Lee and Rhi have highlighted accessibility issues that we’ve run into and what we’ve done to tackle them. You can find our ongoing Accessibility Progress Reports <a href="https://olark.com/speak">on the Olark blog here</a>, with some smaller updates in the <a href="https://changelog.olark.com/">changelog</a>. We’re excited that these reports are now easy to locate, all in one place!</p><p>Commitment #4: <strong>Evaluate all internal tools used across the Olark team to determine what’s accessible and what’s not. Audit these tools and provide a roadmap for change based on what we find: GREEN, ONGOING</strong></p><p>ORIGINAL 2023 GOAL: <em>Putting on our Olark-as-employer hat, we have company-wide tools that we use in our work (plus some departmentally-specific tools). For this commitment, we’ll be assessing the tools everyone uses, so we understand which have accessibility issues. This way, we can seek replacements in our stack and/or if there are transition issues, be upfront with our hires who use assistive tech.</em></p><p>We put together a spreadsheet with our evaluations of all the internal tools we use at Olark and the accessibility policies that go with them. These include everything from communications and project management tools to accounting and operations. The goal was to make sure we knew where our teamwide tooling stood when it came to accessibility initiatives and access.</p><p>This has certainly been a journey — we now know that we have a handful of tools that aren’t as accessible as we’d like.</p><p>We expect this to be a dynamic and ongoing process that we’ll continue to monitor. The roadmap we created reinforces that we will regularly audit our tooling, will reassess tool usage based on the needs of new hires, and will always center accessibility first when it comes to adding new tooling. (As part of an earlier — and ongoing — goal, we ask for accessibility policies for every new tool or software we are considering.) Given this audit, we’re now on the lookout for more accessible tooling for specific parts of our business, including design and operations.</p><p>As we grow in this, we’d love to eventually collaborate with other startups and bootstrapped companies on a list of favorite internal tools. If you’re interested to know what we found or would like to recommend a tool that your organization uses internally, feel free to contact Mandy at support[at]olark.com.</p><p>Commitment #5: <strong>Ship a new website that supports getting &gt;75% of pages to WCAG compliance, and write a post summarizing our learning from the process: ALMOST GREEN</strong></p><p>ORIGINAL 2023 GOAL: <em>Big project: we’re rebuilding our website from the ground up to address accessibility foundationally! In the past, we’ve relied more on spot fixes, and they helped a lot. Now we want to take things to the next level.</em></p><p>We gathered internal needs for tooling from Marketing, Support, and Engineering and vetted several web platforms for our new website. Our priorities were the right mix of ease-of-use for all technical abilities internally and ease of development for accessible visitor-facing pages. In the end, we selected Webflow, which allows us to create WCAG-compliant pages any time. We crossed the line to over 75% WCAG compliance for sure!</p><p>Each page is redesigned/reformatted with accessibility best practices and usability in mind as it’s migrated and then tested for ease of use with assistive tech, along with visual readability, by internal and external partners. We’re still very much in the middle of the process of migrating our site pages, but are making steady progress. This post is a great opportunity to share what we’ve learned too.</p><p><strong>Here are a few of our takeaways:</strong></p><ul><li>The web platform we landed on, Webflow, has some great built-in tools for checking contrast, ensuring all images have proper alt-text, and checking page structure before publishing.</li><li>We made an initial roadmap to determine which pages needed migration first. Our best practice of looking at the volume of traffic (make the most-used pages accessible to the most users first) and function of the pages was a great prioritization filter.</li><li>We determined that porting our Help Center pages and content very early on would make a huge accessibility impact, both internally (on team members being able to update and publish content) and externally (on adherence to WCAG guidelines and a11y-friendly layouts).</li></ul><p>Commitment #6: <strong>Onboard 10 new customers that have customer-facing staff using assistive tech on their teams: RED</strong></p><p>ORIGINAL 2023 GOAL: <em>With each new customer, we’ve learned more about (and we think, improved!) accessibility across our company, not only for our product, but also our processes. For example, when we started with one of our pilot customers, our sales team rethought demos for a blind and low-vision audience. Our customer service team learned how to describe functionality differently. We’d like to keep increasing the diversity of our customer base to include as many disability experiences as possible, so we can be prepared to truly serve everyone.</em></p><p>This goal was more challenging than expected, and our score wasn’t for lack of trying! We reached out within our networks (<a href="https://www.linkedin.com/posts/bencongleton_a11y-accessibility-activity-7159301383391748096-vp8x">like in this LinkedIn post, which crowdsourced a lot of great resources</a>). So far, we’ve onboarded two companies with customer-facing staff who use assistive technology, so we still have a ways to go to reach our target ten. We put in effort and we’ll keep putting in effort. This work will be ongoing: look for it in our 2024 commitments!</p><p>Commitment #7: <strong>Craft an internal playbook for our team on how to accommodate people with disabilities in sales and customer service. Bonus if time: publish this guide externally: RED</strong></p><p>ORIGINAL 2023 GOAL: <em>Our previous goal will synergize with this one. The more we learn about our customers, the more real-world insights we can contribute to this playbook, which will be a source of training for our team — both veterans and new hires — to interact more helpfully with our disabled customers. We hope to do this well enough to share publicly for the benefit of other companies!</em></p><p>Each year since the start of our commitments, we have made one more commitment than the last. We’re just really excited about making progress in accessibility! However, we did load our plate fairly high this time. We had to prioritize where to direct resources for our small team and decided to focus core efforts on the new website and internal tools audit. This project was back-burnered.</p><p>We could have put together something quickly, but we thought the spirit of this goal was to compile a really thoughtful playbook that could be shared externally. To do it well would take more learning and time. We still see the value of this goal, and will potentially revisit it in the future.</p><p>Commitment #8: <strong>Write an ongoing blog about our journey and communicate about choices we’ve made about accessibility on each of our teams: GREEN</strong></p><p>ORIGINAL 2023 GOAL: <em>Sometimes, we can work in a silo, learning things without capturing them for others. We aim to participate in the conversation with this blog and share useful company lessons we learn along the way, in the hopes that we can make this path a little easier for someone else.</em></p><p>We’ve been posting steadily about accessibility feature updates and requests <a href="https://olark.com/speak">on our blog here</a>!</p><p><em>Note on our overall scoring: </em>Olark uses <a href="https://rework.withgoogle.com/guides/set-goals-with-okrs/steps/introduction/">OKRs</a> (which stands for Objectives and Key Results) as our company goal-setting framework. In this framework, if you get a 75%, say, that means it was a good, sufficiently aspirational goal. You didn’t set a goal that was too easy or too hard. In several cases above, we hit 75% or 85% of our target, which means we’re proud of where we landed.</p><h3>Other notable accessibility highlights:</h3><p>Not everything we did was quantified in our commitments. We wanted to celebrate other wins here, like growth in our accessibility network and other assorted cool things:</p><ul><li>We <a href="https://olark.com/speak/olarks-q3-2023-accessibility-progress-report">added automated accessibility testing</a> into our development workflow! Automation is a big advancement in how we do testing. It ensures that what we’re doing follows industry standards and doesn’t regress in the future. The tests also run on every commit we make to our code base, so we can be confident in all the changes we make.</li><li>Early investments in accessibility over the last couple of years helped us work with New York University (NYU) during their new accessibility-forward procurement process.</li><li>A neat turn of events led our CEO Ben to bring the producer of the documentary Surpassing Sight to Olark’s offsite retreat in Austin, Texas. Ben saw a <a href="https://lighthouse-sf.org/2023/01/09/first-look-behind-the-documentary-surpassing-sight-coming-to-a-private-lighthouse-screening/">screening at the LightHouse San Francisco</a> and loved the film, both an action sports movie and a relatable piece about the challenges of folks with disabilities finding employment opportunities. A key social goal of the film is to help build awareness that disabled folks are capable of success both in business and in endurance sports. After connecting with several members of the film team after the screening, he contacted the producer about screening the film at our retreat. The producer had friends in Austin so he came out, presented his film, and did a Q&amp;A with our team afterwards. It was an inspiring experience for us and a great reminder of why we do this work!</li><li>Attending the <a href="https://olark.com/speak/olarks-q3-2023-accessibility-progress-report">CSUN Assistive Technology Conference</a> as a returning speaker and exhibitor gave our CEO, Ben, a new perspective on the growth of the community and also the strength of the core group of folks who attend CSUN every year. This was one of the first times he attended CSUN and ran out of time to see all the folks he knew, and ended up scheduling multiple follow-ups for post-CSUN.</li><li>Within the above CSUN community, there has been a lot of interest in accessible chatbots. This bodes well for the investments we want to make to build more accessible AI and chat solutions. Unlike previous years, there was a lot more interest from potential customers and partners, which has led to many opportunities to work closer with the accessibility community.</li><li>Relationships and demonstrated progress developed over years have opened doors, and continue to open doors, as folks learn that not only are we talking about progress over perfection, we are making progress.</li></ul><h3>Our 2024 Commitments: Where are we headed?</h3><p>This year is about deepening the gains we’ve made, like enhancing our new website, onboarding customers, and continuing to share our journey, while making more strides toward accessible AI chatbots. Here are our new commitments:</p><ol><li><strong>Do a deep dive on making AI chatbots accessible and share our findings on our blog. </strong>We want to tap into the opportunities at the intersection of AI chatbots and accessibility. So we’re committing to researching the requirements for this development, getting feedback from the community, and publicizing what we find.</li><li><strong>Invite an audit for the latest version of Olark. </strong>Back in 2019, we partnered with <a href="https://allyant.com/">Allyant</a> (formerly Accessible360) to conduct an external audit of our chatbox. With their thorough feedback, we made changes to conform to WCAG and Section 508 standards. It’s a good time to revisit this practice, getting a professional perspective to make sure we’re as accessible as we can be!</li><li><strong>Write an ongoing blog about our journey and communicate about choices we’ve made about accessibility on each of our teams. Report accessibility issues quarterly in a public way. </strong>Tracking and sharing our accessibility progress and reporting have been fruitful endeavors, ones that we want to keep on doing. These updates serve as a useful, regular reminder to us that we’re making progress. It can be easy to get stuck in the grind and miss that!</li><li><strong>Two Olarkers give public talks about accessibility. </strong>Speaking at events has been a rewarding way for us to improve our accessibility messages, connect with the community, and hear important perspectives. For this goal, we’d like to extend our accessibility presentations to conferences that don’t specifically target accessibility and reach a broader audience.</li><li><strong>Onboard 10 customers with customer facing roles who rely on accessibility. Get direct feedback on our accessibility from 5 paying end users who rely on assistive technology and benefit from Olark. </strong>This is an extension of our goal from last year. Every new customer teaches us more, improving our product and processes and diversifying our base. We want to keep finding customers we can support and listening deeply to their needs.</li><li><strong>Add automated testing on our new website. </strong>We want to make sure our ongoing development is the most accessible it can be. Automating our tests will help us do that faster and more efficiently.</li></ol><h3>Reflections and takeaways</h3><p>After years of doing this work, we’re still constantly learning and growing. If you’re getting started or on the path of your own accessibility journey, here are just a few principles we recommend:</p><p><strong>Progress over perfection. </strong>We’ve said it before, but it bears repeating. When we first started thinking about making accessibility a core part of our mission at Olark, we worried about not knowing what to do, messing things up, excluding people accidentally. Then we met accessibility consultant Meryl Evans, a deaf individual who sometimes wears a t-shirt that reads: “Progress over perfection.” Her motto gave us permission to fail, and ultimately, to get started. None of us are perfect anyway! We’ll improve as we go. And we’ll do so much more toward accessibility if we’re not afraid of making mistakes. This is so important to remember at every step of the journey.</p><p><strong>Seek feedback from the experts. </strong>You don’t have to go it alone. There are so many friendly and helpful folks you can talk to about improving accessibility at your company. Here are some of the methods we’ve done over the years: reach out to friends and their networks with questions, hire professionals in accessibility, ask for feedback from our employees with disabilities, and assemble diverse panels of our customers who use assistive technology. You’ll be so much better at serving the needs of your customers with disabilities if you talk to them.</p><p><strong>Hire people with disabilities.</strong> This was advice we received from the head of disability inclusion at Google, Chris Patnoe, for the best method to make our organization and our product more accessible. We already had folks on our team with disabilities at that time. If you are a diverse and inclusive company that is mid-sized or larger, the odds are good that you do too (a little over <a href="https://www.pewresearch.org/short-reads/2023/07/24/8-facts-about-americans-with-disabilities/">1 in 8 Americans in the working population have disabilities</a>). When you help teammates resolve accessibility issues related to the work environment, you’ll improve your standards internally. As well, teammates with disabilities can bring much needed perspectives to your product.</p><p>Also, in recent news, the U.S. Department of Justice <a href="https://www.ada.gov/notices/2024/03/08/web-rule/">issued a final rule to update regulations for Title II of the Americans with Disabilities Act (ADA)</a>. This rule applies to state and local government organizations, ie. public organizations. It requires (in most cases) that their web content and mobile apps comply with <a href="https://www.w3.org/TR/WCAG21/#background-on-wcag-2">WCAG 2.1, version AA</a> accessibility standards within 2–3 years. Clarifying how the ADA applies online for these organizations is a huge milestone that moves us all towards a more accessible web — our hope is that this update will lead to more public organizations getting the resources they need to be fully accessible.</p><h3>Have a wonderful GAAD and don’t be a stranger!</h3><p>This year, we’re celebrating wins in our formal commitments, like our end-to-end accessible chatbox and new website on a more accessibility-first platform. We’re also excited and grateful for the growth of our a11y community, our baked-in processes within the company, and the many rewarding experiences we’ve had along the way.</p><p>We’re looking forward to spreading the word about accessibility at conferences, exploring the potential of accessible AI chatbots, continuing to post quarterly updates about our progress, and serving more customers who rely on assistive technology.</p><p>If you read this far, thank you. We hope you learned something valuable to take with you on your own accessibility journey. Happy GAAD and come see us again soon!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1afcdc0dec0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Olark’s Accessibility Journey: Annual Report for GAAD + the Messy Middle]]></title>
            <link>https://olark.medium.com/olarks-accessibility-journey-annual-report-for-gaad-the-messy-middle-9f19de5fa73d?source=rss-f218a12fa80f------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f19de5fa73d</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[inclusion]]></category>
            <dc:creator><![CDATA[Olark]]></dc:creator>
            <pubDate>Tue, 16 May 2023 19:42:56 GMT</pubDate>
            <atom:updated>2023-05-16T22:25:09.675Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Global Accessibility Awareness Day (GAAD) is this week!</strong> As part of this important celebration, we’re sharing our yearly progress and lessons in accessibility. This is a blogging tradition we started <a href="https://olark.medium.com/olarks-a11y-journey-how-our-people-and-our-values-pushed-us-to-build-better-products-for-all-a01f51a6d7e4">in 2021 (plus a deep dive on how we got started)</a> and we continued the practice <a href="https://olark.medium.com/today-marks-an-exciting-date-on-the-calendar-global-accessibility-awareness-day-gaad-180199166951">last year</a>. Come along with us as we reflect!</p><p>If you’re reading this, we probably don’t have to tell you how crucial digital accessibility is or why it matters (<a href="https://digitalaccess.missouri.edu/why-accessibility/">but here’s a quick rundown, just in case</a>). It’s a key value to Olark to be inclusive. That means designing our communication tools to make life easier for <em>everyone</em>.</p><p>We now find ourselves smack in the middle of this accessibility-by-design journey. Beginnings are often flashy and exciting, while the middle — as any storyteller can tell you — risks being more of a “muddle.” If you’ve been on the a11y train awhile too, we’re guessing you can relate.</p><p>The clear path we charted seems both more messy and sometimes more mundane, as we take the daily steps to meet our vision. We have to stay compassionate with ourselves: sometimes we’re raising the bar quite a bit, doing everything we did before and much, much more. The middle is the period where the most change and growth happens. It’s the heart of the story. Persistence is the name of the game here, along with lots of juicy lessons and fun!</p><p><strong>Next, we’ll share details about how we did in our 2022 goals and what we’re aiming for this year. </strong>The last year saw us getting further traction in our agent-side accessibility, enriching our feedback from customers, and adding supportive internal processes.</p><p>We hope that following us in this annual ritual will give you ideas and inspiration of your own. So let’s go!</p><h3>Our 2022 Commitments: How did things go?</h3><p>Last year, we set seven accessibility goals. Here’s how we’re scoring our performance and what we did to meet each goal.</p><p>Rating scale:</p><ul><li>GREEN: We did what we set out to do and maybe even did more than we’d planned.</li><li>YELLOW: We made meaningful progress, but we have a ways to go.</li><li>RED: We aren’t satisfied with the progress.</li></ul><p>__</p><p>Commitment #1: <strong>Evaluate our new agent chat experience &amp; establish our WCAG baseline: REALLY, REALLY GREEN</strong></p><p>ORIGINAL 2022 GOAL: <em>In addition to getting feedback from testers with disabilities and customers with accessibility expertise, we’ll hire a third-party auditor to help us understand where this product stands relative to WCAG guidelines. This information will inform our go-to-market plans and our product roadmap in 2023.</em></p><p>We went all in on this goal and then some. Not only did we decide where we wanted to land on WCAG, but we also met an ambitious internal goal quickly by reaching a new standard (WCAG 2.1 AA) with the help of usability and accessibility feedback from <a href="https://makeitfable.com/">Fable</a>, third-party certification by our accredited auditor <a href="https://allyant.com/">Allyant</a>, and pilot programs with customers who have assistive technology users in customer-facing roles (more on this in the next commitment). Decisions we made early in our design process because of our accessibility commitment — like the choice to build on <a href="https://mui.com/">MUI</a>, one of the most accessible component libraries — helped lay the groundwork for fast progress. We hit this target a month ahead of schedule, in time for the 2023 <a href="https://www.csun.edu/cod/conference/sessions/">CSUN conference</a>.</p><p>It’s worth noting that the agent chat experience was more challenging to make accessible than the customer-facing chat box. It features more information, more notifications, and more functionality. Now, both staff with disabilities and customers have the same level of chat access. We set a high bar for ourselves and weren’t even sure if we could hit it. Overall, we are proud to say that we met this goal 200%.</p><p>Commitment #2: <strong>Collaborate directly with chat agents who rely on assistive technology: GREEN</strong></p><p>ORIGINAL 2022 GOAL: <em>We aim to make an agent chat app that is more than WCAG-compliant and </em>nice to use<em> for disabled customer support reps in their work environment. To achieve this, we need to partner with people who chat or perform related customer messaging tasks as part of their daily work. Frankly, this is hard to do because there are not a lot of accessible options on the market for customer support reps who use AT, but this is also why it’s so important that we build one and make it great.</em></p><p>We are actively collecting feedback from users with disabilities testing our chat experience and implementing their recommendations. For example, <a href="https://clusiv.io/">Clusiv</a>, an eLearning platform built for the blind community to learn key skills for employment, has shared feedback to improve the accessibility and experience of the Olark chat tools, to help ensure the best usability for users who are blind or visually impaired.</p><p>Our pilot customer, <a href="https://www.atguys.com/store/">A. T. Guys</a>, has a web storefront of products, services, and training for blind and low vision users. Their team has blind and low vision staff, so they are able to share the experience on both the agent and customer sides. We also have a pilot participant that has been providing invaluable feedback on how Olark works for their constituents and staff with spinal cord injuries and paralysis. It’s been both meaningful and valuable to us to work with these customers. The more we get real-world responses, the more we can make our chat not simply accessibility-compliant, but <em>good</em> and hopefully a pleasure to use. We’re excited at our progress with this goal and our partnership with our customers.</p><p>Commitment #3: <strong>Make the ASL Zoom integration available to other customers who want it: YELLOW</strong></p><p>ORIGINAL 2022 GOAL: <em>We’re so excited to launch this innovative feature with our partner. Our goal is to enable this functionality for others who need a similar integration.</em></p><p>We put in significant effort on this integration and worked through how we would build the feature. However, other aspects didn’t go as planned. Along the way, through no fault of anyone’s, we no longer had the partnership to drive this feature forward. One lesson we learned: accessibility alone does not mean your chat solution will have all the functionality a business needs. And a strong business use case makes it more likely that your feature will be supported to the finish line. In good news, we got about 60% of the way to shipping this feature and are still open to exploring its completion, if it is of interest to an engaged customer willing to provide feedback.</p><p>Commitment #4: <strong>Publish best practices for accessible chatbots: RED</strong></p><p>ORIGINAL 2022 GOAL: <em>We have strong opinions about chatbots. One of those opinions is that they can be a blessing </em>or a curse<em> for accessibility. This year we’ll share what we’ve learned about how to build chatbots that are helpful to people with disabilities, and we’ll give Olark customers guidance and feedback on how they can find a happy medium between automation and accessibility.</em></p><p>Two big things stalled us on this goal: our immediate aims for the CSUN conference and the disruptive force that is ChatGPT. We mainly channeled our resources into our first big, ambitious goal of the WCAG standard by CSUN time, and we started research into how ongoing changes in AI change the picture. Early last year MITRE (a nonprofit which manages federally funded research and development centers) shared their best practices around accessible chatbots. While their coverage of the material is fairly exhaustive, we know we still have thoughts to add. Overall, we haven’t done this yet and are rethinking what type of best practices would be most useful for the community, especially given AI.</p><p>Commitment #5: <strong>Put every Olarker through role-specific accessibility training: GREEN</strong></p><p>ORIGINAL 2022 GOAL: <em>Accessibility is everyone’s job. This year we will ensure everyone at Olark knows how to do their job in a way that supports disabled people. Each team will set its timeline and curriculum for training, but our Accessibility Working Group will provide oversight and resources. We’ll also lean on our new HR manager to ensure all new hires receive role-specific training within their first 100 days at Olark.</em></p><p>Our goal here was to make sure that everyone understood how their individual role impacted accessibility for our customers. Each team decided on what level of training would be sufficient for all full-time employees in its department, and everyone is on a timeline to be done with training in the near future. We have also added onboarding-specific training for new Olarkers.</p><p>Commitment #6: <strong>Report the status of all accessibility issues quarterly: GREEN</strong></p><p>ORIGINAL 2022 GOAL: <em>To quote our friends at Pope Tech, “there’s no point hiding your accessibility issues because people who have disabilities already know what they are”. We agree. We also think that it’s a lot to ask of people who’ve found our bugs to report them. We can save them the trouble by publishing the summary of our accessibility tickets.</em></p><p>Since the last GAAD, we’ve <a href="https://changelog.olark.com/">published an accessibility status report</a> quarterly for people to see.</p><p>Commitment #7: <strong>Speak at (or host) another GAAD event in 2023: GREEN</strong></p><p>ORIGINAL 2022 GOAL: <em>We had a lot of fun presenting at CSUN, in part because it showed us how far we have to go to make our presentations, demos, and meetings accessible. We are committed to attending GAAD annually — we have already learned so much and it’s helpful for time-boxing our goals.</em></p><p>We’d call this goal achieved in spirit, if not exactly in letter. Multiple Olarkers are participating in an A11y camp this year. And our marketing director, Kelly, is now on the board of the GAAD Foundation, and has been contributing to advancing its goals. For example, she worked on an initiative called the <a href="https://gaad.foundation/what-we-do/speakers-fund">GAAD Speakers Fund</a> — which helps everyday tech professionals with disabilities cover expenses to speak at an in-person event — and is helping with the GAAD day-of launch.</p><p><em>Note on our overall scoring: </em>Olark uses <a href="https://rework.withgoogle.com/guides/set-goals-with-okrs/steps/introduction/">OKRs</a> (which stands for Objectives and Key Results) as our company goal-setting framework. We don’t get into the nitty-gritty of our scoring above. However, we wanted to mention that in this framework, if you get a 75%, say, that means it was a good, sufficiently aspirational goal. You didn’t set a goal that was too easy or too hard. In several cases above, we hit 75% or 85% of our target, which means we’re proud of where we landed.</p><h3>Other neat accessibility accomplishments in 2022:</h3><p>Along the way, we made other valuable contributions that we didn’t quantify in our accessibility commitments above.</p><ul><li>We have multiple motivated technologists on our team working on accessibility. This year, we also <strong>hired a dedicated accessibility engineer</strong> (hi, Lee!) who could focus on key efforts. She’ll think about engineering problems through the lens of accessibility first, and — while she’ll still work on projects outside of accessibility as well — her unique background will help us level up accessibility in all of our projects.</li><li>Our team worked hard to participate in the <strong>CSUN</strong> <strong>Assistive Technology Conference</strong> this year, and <strong>our CEO, Ben, gave a talk highlighting the importance of workplace accessibility</strong>. It was exciting to meet so many in the assistive tech community and share some of our ideas for greater employee access.</li><li>Keeping the motto “nothing about us without us” in mind, we <strong>onboarded people who have lived experience with a variety of disabilities</strong> into our marketing team, to give <strong>feedback on marketing materials</strong> before they go out.</li><li>In an effort to make all of our content more inclusive, we <strong>wrote inclusive language and alt-text guidelines into our brand style guide</strong>.</li><li>This year, we <strong>maintained the Accessibility Working Group we started last year</strong> to keep us accountable to our goals. This group contains roughly five passionate Olarkers who collaborate periodically on Slack.</li></ul><h3>Our 2023 Commitments: Where are we headed?</h3><p>This year is about deepening the gains we’ve made and going more “global” in our external and internal accessibility. Here are our <em>new</em> commitments.</p><ol><li><strong>Offer an end-to-end accessible experience for everyone. All Olark users, new and existing, have access to this experience. </strong>Olark is accessible for chatting both on the customer and agent-side, and most agent-side functionality is also accessible. But there is still the last mile: account settings, reporting, and some dashboard screens are not yet accessible. For example, you can’t yet change the color of your chat box using a screen reader. We’re excited to make Olark accessible in its entirety with this goal.</li><li><strong>Monitor what’s coming for WCAG 2.2 and externally share our journey engaging with the changes. </strong>The <a href="https://www.w3.org/">World Wide Web Consortium (W3C)</a> releases regular updates to its WCAG accessibility standards, sometimes as a draft before formally approving. We’re keeping an eye on how the next version impacts our chatbox. Our aim is to keep ahead of the curve and plan for addressing the next standard. With all that we’ve learned (and keep learning) we think we’ll be in great shape.</li><li><strong>Report accessibility issues quarterly in a public way. </strong>We <a href="https://changelog.olark.com/">started this goal</a> in 2021, and we’re recording it again because we’re going to keep doing it. We plan to make the reporting easier to find as well.</li><li><strong>Evaluate all internal tools used across the Olark team to determine what’s accessible and what’s not. Audit these tools and provide a roadmap for change based on what we find. </strong>Putting on our Olark-as-employer hat, we have company-wide tools that we use in our work (plus some departmentally-specific tools).<strong> </strong>For this commitment, we’ll be assessing the tools everyone uses, so we understand which have accessibility issues. This way, we can seek replacements in our stack and/or if there are transition issues, be upfront with our hires who use assistive tech.</li><li><strong>Ship a new website that supports getting &gt;75% of pages to WCAG compliance, and write a post summarizing our learning from the process. </strong>Big project: we’re rebuilding our website from the ground up to address accessibility foundationally! In the past, we’ve relied more on spot fixes, and they helped a lot. Now we want to take things to the next level.</li><li><strong>Onboard 10 new customers that have customer-facing staff using assistive tech on their teams. </strong>With each new customer, we’ve learned more about (and we think, improved!) accessibility across our company, not only for our product, but also our processes. For example, when we started with one of our pilot customers, our sales team rethought demos for a blind and low-vision audience. Our customer service team learned how to describe functionality differently. We’d like to keep increasing the diversity of our customer base to include as many disability experiences as possible, so we can be prepared to truly serve everyone.</li><li><strong>Craft an internal playbook for our team on how to accommodate people with disabilities in sales and customer service. Bonus if time: publish this guide externally. </strong>Our previous goal will synergize with this one. The more we learn about our customers, the more real-world insights we can contribute to this playbook, which will be a source of training for our team — both veterans and new hires — to interact more helpfully with our disabled customers.<strong> </strong>We hope to do this well enough to share publicly for the benefit of other companies!</li><li><strong>Write an ongoing blog about our journey and communicate about choices we’ve made about accessibility on each of our teams. </strong>Sometimes, we can work in a silo, learning things without capturing them for others. We aim to participate in the conversation with this blog and share useful company lessons we learn along the way, in the hopes that we can make this path a little easier for someone else.</li></ol><h3>Reflections: what we’ve learned lately</h3><p>This year in his <a href="https://docs.google.com/presentation/d/1FXHKDdfI4BGpjjLBywPYAdrsehI-l14IA25WtzYkDPE/edit#slide=id.g1df2a9e2b1c_4_6">talk at CSUN</a>, our CEO Ben summarized some valuable lessons we’ve learned. Here are just a few of the highlights:</p><p><strong>Workplace accessibility matters. </strong>One key theme on our minds is the importance of doing our part to address the employment gap for people with disabilities. Sadly (as you may know), staff-facing tech is often not accessible, even today. The best way we know to chip away at that gap is by making our employee-facing chat technology the most accessible it can be. We’re also bringing on amazing disabled team members to help us advance these efforts.</p><p><strong>There is a </strong><a href="https://en.wikipedia.org/wiki/Maslow%27s_hierarchy_of_needs"><strong>Maslow’s hierarchy</strong></a><strong> of becoming more accessible.</strong> At the base of this pyramid is compliance, which often means an audit. (We’ve moved up this pyramid ourselves, by the way! And sometimes you can move down again for a while.) The next step up is usability, where you can start to work with testers. Up from there, you have integration. In our case, this is where we added real customers with core needs around accessibility. And finally, at the tip of the pyramid, you can experience the joy and fun of solving problems!</p><figure><img alt="A pyramid with four layers. Starting from the bottom: 1) Compliance, 2) Usability, 3) Integration, and 4) Fun!" src="https://cdn-images-1.medium.com/max/1000/1*0UUdlMMc64r7CKCMCyPU4Q.png" /></figure><p><strong>Motivation over obligation. </strong>We’ve learned that people — both staff and customers — who are motivated trump people who are obligated to work in accessibility. That means we’re especially excited to work with customers who aren’t just checking a compliance box, but who are also motivated to support the larger goals and values of inclusion.</p><h3>Next steps in Olark’s accessibility</h3><p>From WCAG 2.1AA to meaningful customer input, we’re proud of the progress we’ve made this year. And of course, the journey is never done. We look forward to putting the final accessibility touches on our agent-side experience, making our website more accessible, sharing our lessons internally and externally, and listening to the needs of a wider set of customers using assistive technology. We’re continuing to embrace progress over perfection. Thank you for reading. It’s been super valuable for us to hold ourselves publicly accountable to these goals and we hope you got some useful takeaways for your own efforts.</p><p>Have a wonderful GAAD and we’ll see you next time on the same bat channel!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f19de5fa73d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Today marks an exciting date on the calendar — Global Accessibility Awareness Day (GAAD)!]]></title>
            <link>https://olark.medium.com/today-marks-an-exciting-date-on-the-calendar-global-accessibility-awareness-day-gaad-180199166951?source=rss-f218a12fa80f------2</link>
            <guid isPermaLink="false">https://medium.com/p/180199166951</guid>
            <dc:creator><![CDATA[Olark]]></dc:creator>
            <pubDate>Thu, 19 May 2022 17:02:28 GMT</pubDate>
            <atom:updated>2022-05-19T17:02:28.451Z</atom:updated>
            <content:encoded><![CDATA[<h3>Olark’s Accessibility Journey: Annual Report from GAAD</h3><p><strong>Today marks an exciting date on the calendar — Global Accessibility Awareness Day (GAAD)!</strong> Each year, technologists join a11ys and activists in the disability community to educate people about how to make digital experiences that are friendly to people with disabilities and anyone using assistive technology.</p><p>Olark believes that digital accessibility is a civil rights issue. More than one billion people worldwide have some form of disability, and every one of them deserves good usability. As people who make chat tools for the web, we understand that if we want to design and build for everyone, we must acknowledge the consequences of our choices. We can either make life easier or more difficult for people.</p><p>2021 was the first GAAD we participated in as a company and ended up being transformational for Olark. Getting involved with the a11y community inspired us to think holistically about accessibility, and to realize <em>our</em> role in the big picture of inclusion and universal design.</p><p>Last year we published a set of commitments on how Olark would improve accessibility as an organization. Accessibility remains a key priority for us, and we’ve made some huge strides towards our goals. But, our work is not complete. Today we’re here to hold ourselves accountable to our 2021 commitments, share some of our biggest takeaways from the past year, and set our agenda for our accessibility journey in 2022.</p><p><strong>Our 2021 Commitments: How did we do?</strong></p><p>Last year we outlined six accessibility goals. For each, we’ve scored our performance below and shared what we did to meet each goal.</p><p>Here’s our rating scale:</p><ul><li>GREEN: We did what we set out to do and in some cases, did more than we’d planned.</li><li>YELLOW: We made meaningful progress, but we have a long way to go.</li><li>RED: We’re disappointed in the outcome.</li></ul><p><strong>— —</strong></p><p><strong>Commitment #1: Expand accessibility beyond the chatbox: YELLOW</strong></p><p><strong><em>ORIGINAL 2021 GOAL: </em></strong><em>Our digital accessibility footprint extends beyond our software and website. We’ve identified gaps in our email marketing and content publishing workflows and will be updating our brand style guide to provide a more contrast-friendly color palette and better adherence to semantic HTML guidelines.</em></p><p>On the content side, we made numerous fixes on our website, but not enough to meet the Service-Level Agreement (SLA) we set as a team. We also updated our brand style guide to require high color contrast and we now screen for accessibility issues before publishing new content. So, our new content is accessible, but the bulk of our website still needs work.</p><p>In early 2021, we updated our chatbox to adhere to a WCAG 2.0 AA rating, however, we knew the app our customers used to respond to incoming chats was unusable on a screen reader. This app was also quite old and built on legacy systems, so we opted to create a new one from scratch. Our Product team has since redesigned the app with accessibility in mind and is building a newer version. We have a few customers beta testing this app but we are months away from having it ready for public release.</p><p><strong>Commitment #2: Prioritize accessibility in our customer feedback: GREEN</strong></p><p><strong><em>ORIGINAL 2021 GOAL: </em></strong><em>In 2021, we launched a customer advisory board to help guide our product development going forward. We’ve added requirements to our recruitment of that board to make sure we’re getting engaged feedback from organizations who have very high requirements for accessibility (in both public institutions and commercial settings).</em></p><p>We’ve continued to engage with leaders in Accessibility offices at major higher education institutions, including University of California at Berkeley. We’re also excited about our work with Gallaudet University, the only university in the world where students can live and learn in both English and ASL (American Sign Language). Gallaudet asked us to build a feature for their chatbox that would allow Deaf students to express themselves in the language where they’re most comfortable communicating. So, we built in the option to either type text or sign over a video chat extension.</p><p><strong>Commitment #3: Diversify our pool of beta testers with disabilities: GREEN<br><em>ORIGINAL 2021 GOAL: </em></strong><em>We’d already succeeded in getting product feedback from people who use assistive technology, but this year we’ve set goals to ensure we’re testing our products across a broader range of adaptive technology platforms and gathering accessibility feedback earlier in our design process.</em></p><p>In addition to working with Gallaudet, we’ve engaged Fable to help us source usability feedback from testers who rely on assistive technology. This will help us get accessibility input earlier in our development cycle from a more diverse group who use a variety of assistive technologies. We plan to supplement our initiatives in 2022.</p><p><strong>Commitment #4: Speak at a GAAD 2022 event: GREEN</strong></p><p><strong><em>ORIGINAL 2021 GOAL: </em></strong><em>This time next year, we’ll share our accessibility progress in a live event setting.</em></p><p>Earlier this year, we exhibited at CSUN’s Assistive Technology Conference in Anaheim with five Olarkers in tow. We enjoyed watching our CEO, Ben Congleton, present how his mistakes as a leader slowed our progress and how we overcame them to translate our passion for inclusion into specific accessibility policies. Ben’s also kicking off A11yBay’s GAAD programming this year withan adapted version of this talk, which you can attend virtually <a href="https://www.meetup.com/a11ybay/events/285753429/">here</a> if you’re interested.</p><p><strong>Commitment #5: Establish and maintain an accessibility SLA for Olark.com: GREEN</strong></p><p><strong><em>ORIGINAL 2021 GOAL: </em></strong><em>We’ve been consistently chipping away at updating the outdated content pages on our website, but in 2021 we’ll be formalizing this in our quarterly OKRs so we know that these issues will get prioritized and resourced by the entire company.</em></p><p>We recently established accessibility SLAs across each team in the company. In addition to reporting our performance against these SLAs, each team has set OKRs that advance Olark’s accessibility quarterly. To be candid, we haven’t met all of our SLAs every quarter. However, having the goals pushed us to make progress and have hard conversations around how we must resource teams to satisfy these commitments.</p><p><strong>Commitment #6: Require an accessibility review before adopting user-facing 3rd-party tools: GREEN</strong></p><p><strong><em>ORIGINAL 2021 GOAL: </em></strong><em>We were motivated to improve our accessibility by a customer who drew a line in the sand and wouldn’t sign a contract until we addressed some accessibility issues they’d identified. This year, we’re going to follow that example and require an accessibility evaluation of any company-wide 3rd-party software tools before they’re rolled out to the entire company.</em></p><p>Of all the goals on this list, this one was the easiest to meet but also quite powerful. Asking other companies about their accessibility policy before purchasing has helped us use our buying power in the market to push for better accessibility for both our employees and their other customers. It’s been satisfying to see how just asking a few questions can start a conversation.</p><p><strong>Other cool accessibility accomplishments in 2021:</strong></p><p>Throughout the year we learned a lot about how we could socialize our accessibility knowledge and support individuals as they came up with their own ideas. Of all the things we accomplished, our leadership team is most excited to see how many gains have come from Olarkers improving something because they wanted to vs. being told to.</p><ul><li>We hadn’t set any commitments around improving our accessibility as an employer, but we realized we needed to. So, we <strong>hired an HR Manager</strong> to help us revamp all of our internal and candidate-facing processes.</li><li>We learned it’s way more energizing to build relationships in the accessibility community than read web standards documentation. So, several Olarkers attended their first a11y event. Members of every team went to <strong>CSUN</strong> this year<strong>, </strong>our CEO participated in a workshop with<strong> EduCause, </strong>and our Chief of Staff just came back from<strong> AccessU</strong> with <em>many ideas</em><strong><em>.</em></strong></li><li>To foster cross-functional learning and collaboration, we also <strong>formed an Accessibility Working Group</strong>. This move allows us to set goals, unblock accessibility initiatives across teams, and keep track of complex projects To help with developing an accessible agent console, many of the engineers on this product team have begun working toward International Association of Accessibility Professionals — Web Accessibility Specialist Certification ( IAAP WAS).</li><li>This month our Support team audited our Help Center for accessibility and have begun <strong>rewriting documentation and tutorials using plain language</strong> to make our self-serve content easier to read and understand.</li></ul><p><strong>Our 2022 Commitments: Where are we headed?</strong></p><p>This year is all about building momentum and applying what we’ve learned. We’ll make progress with the basics by expanding audits and updating existing content. To level up, we’ll be formalizing accessibility education company-wide and contributing to the conversation about how chat helps (or hurts) accessibility.</p><p>Between now and GAAD 2023, we’ll continue to invest in meeting and maintaining our accessibility SLAs across the company. Here are the <em>new</em> <em>commitments</em> of where we’ll improve.</p><ol><li><strong>Evaluate our new agent chat experience &amp; establish our WCAG baseline.</strong>. In addition to getting feedback from testers with disabilities and customers with accessibility expertise, we’ll hire a 3rd-party auditor to help us understand where this product stands relative to WCAG guidelines. This information will inform our go-to-market plans and our product roadmap in 2023.</li><li><strong>Collaborate directly with chat agents who rely on assistive technology.</strong>We aim to make an agent chat app that is more than WCAG-compliant <em>and</em> <em>nice to use</em> for disabled customer support reps in their work environment. To achieve this, we need to partner with people who chat or perform related customer messaging tasks as part of their daily work. Frankly, this is hard to do because there are not a lot of accessible options on the market for customer support reps who use AT, but this is also why it’s so important that we build one and make it great. If you have any suggestions of people or organizations we should reach out to, or other advice around how to build this kind of usability panel, please reach out to <a href="/service/mailto:benc@olark.com">benc@olark.com</a>.</li><li><strong>Make the ASL Zoom integration available to other customers who want it. </strong>We’re so excited to launch this innovative feature with Gallaudet. Our goal is to enable this functionality for others who share Gallaudet’s vision for bilingual English/ASL chat.</li><li><strong>Publish best practices for accessible chatbots.</strong> We have strong opinions about chatbots. One of those opinions is that they can be a blessing <em>or a curse</em> for accessibility. This year we’ll share what we’ve learned about how to build chatbots that are helpful to people with disabilities, and we’ll give Olark customers guidance and feedback on how they can find a happy medium between automation and accessibility.</li><li><strong>Put every Olarker through role-specific accessibility training</strong>. Accessibility is everyone’s job. This year we will ensure everyone at Olark knows how to do their job in a way that supports disabled people. Each team will set its timeline and curriculum for training, but our Accessibility Working Group will provide oversight and resources. We’ll also lean on our new HR manager to ensure all new hires receive role-specific training within their first 100 days at Olark.</li><li><strong>Report the status of all accessibility issues quarterly. </strong>To quote our friends at Pope Tech, “there’s no point hiding your accessibility issues because people who have disabilities already know what they are”. We agree. We also think that it’s a lot to ask of people who’ve found our bugs to report them. We can save them the trouble by publishing the summary of our accessibility tickets.</li><li><strong>Speak at (or host) another GAAD event in 2023</strong>. We had a lot of fun presenting at CSUN, in part because it showed us how far we have to go to make our presentations, demos, and meetings accessible. We are committed to attending GAAD annually — we have already learned so much and it’s helpful for time-boxing our goals.</li></ol><p><strong>One year later: How has Olark changed since GAAD 2021?</strong></p><p>It’s been an amazing 365 days at Olark, and our accessibility work has reinvigorated our company culture. This time last year, we had no idea how we’d meet some of the commitments we outlined, but we found a way because we don’t like to fail, especially not in public.</p><p>Using GAAD as an occasion to align our team around specific, realistic, and diverse goals helped us turn our passion into progress. It’s been rewarding for us to see teammates set their own goals and find satisfaction in knowing that their work aligned with their values.</p><p>Working on these goals and engaging with the a11y community has helped us realize our company values and feel connected to the people who can benefit most from what we do. After digging in with accessibility, we’re not that interested in being a chat software company — we’re inspired to be the most accessible and inclusive customer communication platform on the market.</p><p>Our experience with GAAD led us to make a huge decision last fall. We registered Olark as a Public Benefit Corporation (PBC) and <strong>wrote our commitment to accessibility into our company charter</strong>. Now, we have even higher stakes for this work, along with another external party to hold us to our mission. We plan to double down on this in 2022 by becoming a B-Corporation that’s evaluated on how well we contribute to social goals and inclusion in the workplace. To us, these designations are an extension of how we can push ourselves to be more accessible as a matter of <em>practice and purpose.</em></p><p>More than anything, GAAD helped us make an important mental shift: accessibility is a journey, not a destination. To us, that means:</p><ul><li><strong>We focus on culture over compliance. </strong>Conforming to WCAG standards is useful because it offers a good starting point and makes it easy for customers to know if we meet the minimum requirements of accessibility. But emphasizing compliance and 3rd-party certification is a way to build “good enough” digital experiences and then give up in favor of other priorities. Investing in culture is the only way to make online experiences GREAT.</li><li><strong>We focus on progress over perfection. </strong>We are flawed; if you scan our website for accessibility issues, you will find them. We have a lot of work to do, but we’ve found that it’s easier to do this work if we celebrate how we’ve improved and discuss momentum. We’ve also seen there aren’t many small businesses willing or able to talk openly about their accessibility failures. But we’ve gained more by being vulnerable, accepting critical feedback, and rewarding curiosity over expertise.</li><li><strong>We reward curiosity over expertise.</strong> To quote Mike Shebanek, the PM who built VoiceOver and made iPhones accessible to blind and low-vision users, “it’s better to have a lot of people who know a little bit about accessibility than it is to have a few people who know everything about it”. This belief has informed how we’ve organized this work as a small team. Many industry leaders have experts on staff whose sole focus is accessibility. That sounds nice, but it’s not really an option in a company as small as Olark. We’ve seen it’s easier to guarantee that every project has a focus on accessibility if you invest in keeping people curious and motivated to learn what they don’t know.</li><li><strong>We accept that we’ll never be done. </strong>Olark prefers to talk about “becoming accessible” instead of “being accessible” because only one of those is a durable goal in practice. The web is constantly changing, and so are the ways people adapt to get their needs met, even as an environment disables them. Once we realized that we’d never be finished, we started getting more done because it’s easier to commit to resources if you know you’ll need them forever.</li><li><strong>We remember that designing for the few rewards the many.</strong> If you’ve made it this far, you probably already know that there’s no usability without accessibility. We’ve found that it helps to imagine how building the features that are required for people with disabilities ends up benefiting people who don’t. Some people use captions on Netflix because they can’t hear the dialog. Other people use captions on Netflix because the baby is finally asleep in the next room, so they must turn down the volume on their favorite show. Were it not for the needs of the Deaf community, captioned video may not have been created to benefit everyone else. Focusing on accessibility is a reliable path to innovation, and it’s a lot more fun to build something for the few people who need it now than it is to try to imagine what the world wants next.</li></ul><p><strong>Wrapping up — next steps in Olark’s accessibility quest</strong></p><p>From building an accessible agent chat app to leveling up our website content, we’ve made positive steps forward in our accessibility journey. But we recognize this is just the beginning. To see significant changes in our products and content, we’ll need to continue optimizing our culture and technology to build an ecosystem in which accessibility (and usability) can thrive. We aren’t deterred, in fact, we’re ready for the challenge and will remain focused on progress over perfection through. We hope you’ll join us for the next stop on our journey.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=180199166951" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Olark’s Accessibility Journey: how our people and our values pushed us to build better products for…]]></title>
            <link>https://olark.medium.com/olarks-a11y-journey-how-our-people-and-our-values-pushed-us-to-build-better-products-for-all-a01f51a6d7e4?source=rss-f218a12fa80f------2</link>
            <guid isPermaLink="false">https://medium.com/p/a01f51a6d7e4</guid>
            <category><![CDATA[advocacy]]></category>
            <category><![CDATA[core-values]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[inclusive-design]]></category>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[Olark]]></dc:creator>
            <pubDate>Thu, 20 May 2021 02:03:10 GMT</pubDate>
            <atom:updated>2021-05-20T03:14:42.449Z</atom:updated>
            <content:encoded><![CDATA[<h3>Olark’s Accessibility Journey: how our people and our values pushed us to build better products for all</h3><p><strong>May 20th is Global Accessibility Awareness Day (</strong><a href="https://globalaccessibilityawarenessday.org/"><strong>GAAD</strong></a><strong>)! </strong>To celebrate, we are sharing Olark’s story: how we went from finding a couple of accessibility issues in our bug tracker to developing a <a href="http://www.olark.com/help/accessibility">WCAG 2.0 AA compliant chatbox</a> and fostering a team committed to doing more to make Olark accessible (with a lot of work ahead of us).</p><p>Every one of us has a role to play to make the web more accessible, and with 1 in 4 adults in the US (<a href="https://www.cdc.gov/ncbddd/disabilityandhealth/infographic-disability-impacts-all.html">CDC</a>) and over 1 billion people worldwide (<a href="https://www.who.int/en/news-room/fact-sheets/detail/disability-and-health">WHO</a>) living with a disability, we all are needed.</p><p>Whether you are an accessibility pro, an advocate, or just starting your journey, we hope you can learn from the road we’ve traveled so far.</p><p>And if you are inspired and want to get started yourself, <a href="https://www.olark.com/global-accessibility-awareness-day"><strong>join us and our partners in taking a pledge to make the web more accessible in 2021</strong></a>.</p><h3>What exactly is digital accessibility?</h3><p>It sounds obvious, but the simplest possible way of looking at accessibility is <em>access</em>. Is the front door to your technology locked to someone with visual, hearing, cognitive, or fine motor impairments? Or is it open? And once someone gets in, can they easily and independently accomplish their goals?</p><p><strong>Right now, about 98% of websites have software-detectable accessibility issues</strong>, making them non-compliant with best practices (<a href="https://globalaccessibilityawarenessday.org/">WebAIM</a>). And even compliance with WCAG (<a href="https://www.w3.org/TR/WCAG21/">Web Accessibility Content Guidelines</a>) does not mean your technology is easy to use by someone with disabilities.</p><p><strong>Good digital accessibility means supporting the following user stories (and then some):</strong></p><ol><li>As someone who has color vision trouble distinguishing shades of red and blue, I can identify and navigate your website’s links without relying on hue.</li><li>As someone who uses the keyboard to navigate web pages, I can quickly navigate a chatbox without getting stuck in a <a href="https://www.nomensa.com/blog/what-are-keyboard-traps">keyboard trap</a>.</li><li>As someone who is hard-of-hearing, I can tell that I have a new chat message through immediate visual cues so I don’t have to rely on sound for notifications.</li><li>As someone with a cognitive difference, I find your interface simple to use and free of unnecessary distractions.</li><li>As someone who relies on a screen reader, I can quickly navigate and understand your content without a purely visible layout.</li></ol><p>The <a href="https://www.w3.org/WAI/standards-guidelines/wcag/">Web Accessibility Content Guidelines</a> (WCAG) help all of us have a shared understanding of where to start, but they are by no means a finish line for building great usable products.</p><h3>How did we get started on this journey?</h3><h4>Part I: Building a customer-centric, inclusive organization</h4><p>Olark started over 12 years ago as an easy way for companies to be able to chat with their customers through a chatbox. Very early on, we realized that chat was a great game-changer, both for those who were not comfortable talking on the phone and for those for whom text communication was necessary.</p><p>The deaf community has been one of the huge benefactors of our society’s shift towards written communication, and positive feedback from this community gave us momentum in the early days.</p><p>We codified our human-centered <a href="https://www.olark.com/values">values</a> early on, clarifying the importance of <strong>#practicing empathy</strong>, and <strong># speaking</strong> your mind — we apply these values both internally in the culture we build — but also in the tool we build for our customers. Deeply rooted in our beliefs was that Olark as technology should <strong>#help </strong>everyone communicate better and that it was our shared responsibility to <strong>#make it happen</strong>. In the early days, this meant simplifying chat to its core and making easy-to-understand and highly usable interfaces, but over time this definition has grown.</p><p>Prior to 2017, as customers reported accessibility issues, they were entered into a bug tracker, prioritized, and completed, similar to any other bug. We addressed small one-off issues but did not do any big accessibility pushes or attempt to change our big-picture development process to be more accessibility-aware.</p><h4>Part II: A passion project becomes the catalyst</h4><p>The real push to improve started in 2017. Two factors contributed to a shift towards a more holistic approach to accessibility. One, we had a customer who was passionate about the need for our product to be more accessible. Two, one of our previous engineers (hi Madalyn!) sparked an internal initiative to make accessibility a focus in engineering. Along with evangelizing the need for accessibility-friendly development practices and work processes, she led the team in adding:</p><ul><li>screen-reader-friendly <a href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA">ARIA attributes</a>, ensuring our chatbox was tab- and keyboard-focus friendly</li><li>more accessible forms and icons</li><li>automated accessibility tests (to our development workflows)</li><li>a high-contrast color mode for our agent console</li></ul><p>These changes led to a greater awareness of the importance of accessibility within Olark, which really kick-started our journey to where we are today.</p><h3>Three big catalysts got us moving. Remember, you can be any of these.</h3><blockquote>An internal champion. Thanks, Madalyn.</blockquote><blockquote>A passionate customer who we listened to.</blockquote><blockquote>A culture that made it easy for an internal champion to take something and run with it.</blockquote><p>Following the push in 2017, we started seeing more business from accessibility-minded organizations: from non-profits to government to higher education. The accessibility tickets would come in, and get triaged and addressed similar to pre-2017. But with a strong base to draw from, we started becoming more organically known as an organization that deeply cared about accessibility.</p><h4>Part III: Getting serious</h4><p>In 2019, accessibility became a product-led initiative with the resources to do necessary user research to understand accessibility as a holistic challenge. Due to our Head of Product Julie’s leadership, we were able to think more critically about accessibility, and have the discussions needed to make it a priority at the management level.</p><p><strong>The following elements played a role in getting serious:</strong></p><ul><li>Our human-first culture and values made it easy to create bottom-up and top-down buy-in.</li><li>A small number of vocal customers encouraged us to improve and do better.</li><li>A management-level champion took ownership over accessibility and used her privilege to push for inclusive design.</li></ul><p>With accessibility as a priority, the end of 2019 and 2020 was a whirlwind of progress. We defined our goal as full WCAG 2.0 AA compliance for our new chatbox to be released in 2020. We started our journey towards compliance by bringing in outside expertise.</p><p>We had customers who had worked with <a href="https://accessible360.com/">Accessible360</a> (A360) in the past, and they came highly recommended as an agency that knew how to work with engineering teams and was well-respected within the accessibility community. We went from proposal to a full audit of our chatbox in a matter of weeks. (<a href="https://blog.olark.com/live-chat-accessibility-audit">See a blog post about our A360 audit here</a>!)</p><p>In addition to prioritizing issues discovered by Accessible360, we also took a holistic look at our accessibility backlog and made it clear to our entire team that accessibility issues were to be routed directly to our team working on accessibility and prioritized immediately rather than processed as part of our normal engineering backlog.</p><p>This initiative culminated in:</p><ul><li>A complete <a href="https://www.olark.com/help/chatbox_update/">visual update of our chatbox</a> optimized for screen readers</li><li>Notably: enabled screen readers to read incoming messages, fixed labeling, and semantic markups</li><li>A new accessibility forward design and development process.</li><li>Identifying top opportunities for us to improve the accessibility of our marketing site.</li><li>Setting new standards for our chat agent console, customer experience, content, bug reporting, and more!</li></ul><p><strong>In January of 2021, we received a Letter of Compliance from A360, asserting that our chatbox meets WCAG 2.0 AA requirements!</strong></p><p>With a more accessible chatbox, we’ve opened ourselves up to great partners like <a href="https://dac.berkeley.edu/home">UC Berkeley’s Center for Disability Access &amp; Compliance</a>, as well as many forward-thinking customers who provide us with constant feedback on how we can do better.</p><h3>Our accessibility takeaways so far:</h3><ul><li><strong>Accessibility is good for business. </strong>We’ve grown as a direct result of being able to better serve and sell to a wider range of customers in forward-thinking, inclusive companies, as well as regulated environments like higher education and government.</li><li><strong>Don’t underestimate the value of a small nudge. </strong>A couple of persistent customers, an inclusive culture, and an internal champion helped us move towards becoming accessible. As a buyer of software or an employee at a company, you have a lot of power to drive change.</li><li><strong>Setting specific accessibility goals is powerful. WCAG compliance is a great start. </strong>WCAG 2.0 AA compliance was a powerful target to build towards and helped us level up our approach.</li><li><strong>Accessibility is a team effort… but needs a clear owner</strong>. Marketing, sales, customer service, product, design, engineering, people ops, and executive departments all have a role to play, but make sure you have one clear owner for accessibility in your organization.</li><li><strong>Accessibility is a continuous process. </strong>We’ve created an internal checklist for design and development to refer to as they work, we’re investigating plug-ins and extensions for our tools that help us make more accessible design decisions, and we have a list of resources for help tackling tricky problems and leveling up internal knowledge.</li><li><strong>Start accessibility early in the development process. </strong>Each time we moved accessibility earlier in the development process, it accelerated our progress, made our impact much quicker, and lowered our costs. There is a larger moment to <a href="https://blog.tenon.io/core-features-for-a-true-shift-left-web-accessibility-testing-tool/#:~:text=Shifting%20left%20allows%20for%20early,becoming%20embroiled%20in%20ADA%20litigation.">shift accessibility earlier in the development process</a>, and we believe in it.</li><li><strong>We have a lot to do and a lot to learn. </strong>We are just getting started. Olark’s accessibility is incomplete, we have a lot of work to do, and we hope you will join us on this journey.</li></ul><h3>Where we go from here</h3><p>Accessibility isn’t a destination, it’s an ongoing process to meet and maintain a high standard of usability for all. We’re happy to have come so far over the last year, but what we’ve done isn’t as important as what we’re doing to improve.</p><h4>What we’re committed to doing before GAAD 2022:</h4><ol><li><strong>Expand accessibility beyond the chatbox: </strong>Our digital accessibility footprint extends beyond our software and our website. We’ve identified some gaps in our email marketing and content publishing workflows and will be updating our brand style guide to provide a more contrast-friendly color palette and better adherence to semantic HTML guidelines.</li><li><strong>Prioritize accessibility in our customer feedback: </strong>This year we’ve launched Olark’s BrainTrust as a customer advisory board to help guide our product development going forward. We’ve added requirements to our recruitment of that board to make sure we’re getting engaged feedback from organizations who have very high requirements for accessibility (in both public institutions and commercial settings).</li><li><strong>Diversify our pool of beta testers with disabilities: </strong>We’d already succeeded in getting product feedback from people with disabilities, but this year we’ve set goals to ensure we’re testing our products across a broader range of adaptive technology platforms and gathering accessibility feedback earlier in our design process.</li><li><strong>Speak at a GAAD 2022 event: </strong>This time next year, we’ll share our accessibility progress in a live event setting.</li><li><strong>Establish and maintain an accessibility SLA for Olark.com: </strong>We’ve been consistently chipping away at updating the outdated content pages on our website, but in 2021 we’ll be formalizing this in our quarterly OKRs so we know that these issues will get prioritized and resourced by the entire company.</li><li><strong>Require an accessibility review prior to adopting user-facing 3rd-party tools: </strong>We were motivated into improving our accessibility by a customer who drew a line in the sand and wouldn’t sign a contract until we addressed some accessibility issues they’d identified. This year, we’re going to follow that example and require an accessibility evaluation of any company-wide 3rd-party software tools before they’re rolled out to the entire company.</li></ol><p>We look forward to writing the next chapter and expanding accessibility across our marketing site, help center, and chat agent experience.</p><p>Remember Global Accessibility Awareness Day is May 20th, <a href="https://www.olark.com/global-accessibility-awareness-day"><strong>join us and our partners in taking a pledge to make the web more accessible in 2021</strong></a>.</p><p><em>A huge thanks to Mandy, Kerry, Rhi, Kelly, and others for reading and writing drafts of this post, and all of the Olarkers (past and present) who have worked to make Olark more accessible and open: Alicia, Melanie, Nick, Rhi, Julie, Joe, Ben, Matt, Hector, Miranda, Kelly, Madalyn, Lithia, Sarah; our freelancers Chris, Coco and Kerry; and our partners at GAAD and Accessible 360. Your dedication and passion for inclusion makes us better every day.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a01f51a6d7e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From 0 to 10: Making the “right” decisions]]></title>
            <link>https://olark.medium.com/from-0-to-10-making-the-right-decisions-6442af671326?source=rss-f218a12fa80f------2</link>
            <guid isPermaLink="false">https://medium.com/p/6442af671326</guid>
            <category><![CDATA[small-business]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Olark]]></dc:creator>
            <pubDate>Wed, 11 Dec 2019 18:06:55 GMT</pubDate>
            <atom:updated>2019-12-11T21:29:51.664Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/75/1*Cc9rTnK1MxUC6tl5LBYGZg.png" /><figcaption>By Ben Congleton, Chief Executive Olarker</figcaption></figure><p><em>This post is the fourth in our 10 year anniversary series. Want to catch up? Read the </em><a href="https://medium.com/@Olark/from-0-to-10-how-we-built-an-unconventional-silicon-valley-startup-10f6694665b9?source=---------4------------------"><em>series intro</em></a><em>, </em><a href="https://medium.com/@Olark/from-0-to-10-starting-a-business-by-solving-our-own-problems-bfc71c429f95?source=---------3------------------"><em>Olark’s origin story</em></a><em>, and </em><a href="https://medium.com/@Olark/from-0-to-10-our-bumpy-but-worth-it-road-to-a-co-created-culture-fc62d3cf1dd4"><em>our road to a co-created culture</em></a><em>.</em></p><p>A few years after graduating from YCombinator, Olark walked away from what could potentially have been a very lucrative acquisition offer.</p><p>We were in the midst of partnership discussions with a larger tech firm. In one late-stage meeting, the conversation about our technical capabilities turned into a presentation on their product vision, and I realized that our potential partners were actually interested in buying Olark.</p><p>I reacted instinctively. I told them I wasn’t selling.</p><p>As soon as the words were out of my mouth, I felt the tension rise in the room. The other company’s representatives were a little taken aback, of course, but my co-founders were truly alarmed. We hadn’t discussed the possibility of an acquisition offer, and others on our founding team were (justifiably) excited and wanted to hear them out.</p><p>I knew that many founders in my position would jump at an opportunity like this one. But I also believed strongly in Olark’s future as an independent company; I loved the <a href="https://medium.com/@Olark/from-0-to-10-our-bumpy-but-worth-it-road-to-a-co-created-culture-fc62d3cf1dd4">culture</a> we were building, and I felt like our product and vision were just starting to gain momentum. I knew that if we were acquired at our small size, we’d simply be absorbed, and our unique little spark would fade out in a corporate blaze.</p><blockquote>I knew that many founders would jump at an opportunity like this one. But I also believed strongly in Olark’s future as an independent company; I loved the culture we were building, and I felt like our product and vision were just starting to gain momentum.</blockquote><p>I walked back to our office in the dark, feeling vaguely sick to my stomach. I fielded questions and listened to my team’s frustrated objections, and ultimately sent a conciliatory email that left the door open, ever so slightly, for further discussion. I knew I’d made my decision, though. Olark wouldn’t pursue acquisition in 2013 (or since, for that matter).</p><p>Over the weeks, months, and years that followed, plenty of people would second-guess that choice. And the fallout certainly wasn’t all good. Ultimately, two of our four original co-founders decided to move on from Olark, in part (though not entirely) due to disagreements around the acquisition decision. Our would-be acquirer ultimately became a competitor. And, of course, we walked away from what might have been a fairly sizable chunk of cash.</p><p>Despite all that, though, I’ve never doubted that I made the right call. I started Olark to create freedom, and I wanted to build an organization where I’d be excited to be either CEO or the next hire. Some of the things I said in that meeting were impulsive, but they were voiced from a place of uncompromising alignment with Olark’s values, and with my own.</p><p>The “right” call isn’t always what everyone else thinks. More often, it’s the decision that moves you one step closer to your vision of the world and the work you want to do in it — even if you can’t see the entire path that follows.</p><blockquote>The “right” call moves you one step closer to your vision of the world and the work you want to do in it.</blockquote><p>Because Olark remained independent, we’ve been able to evolve in the ways that matter most to our team. Some of these have been things we expected and planned for, and some have happened organically. In particular:</p><ul><li><strong>We went full remote.</strong> Remote work was one of our potential acquirer’s major concerns, and it almost certainly would have gone away if we’d been bought. As an independent company, we were able to go all-in on learning to hire, onboard, manage, and build culture remotely. The option to bring in the best person for every role, regardless of where they live, has been an enormous competitive advantage — and has given me the opportunity to work with amazing Olarkers from around the world.</li><li><strong>We demonstrated that small companies can have a big social impact. </strong>Our remote, 35-person team made national news for our stances on <a href="https://www.inc.com/business-insider/madalyn-parker-ben-congleton-olark-live-chat-lesson-leadership.html">mental health</a> and <a href="https://www.nbcnews.com/nightly-news/some-companies-encouraging-employees-disconnect-during-vacation-n732116">unplugged vacation</a>. We’ve set an example by starting conversations and living our <a href="https://www.olark.com/values">values</a>, and our stories have touched people and companies around the world.</li><li><strong>We emphasized </strong><a href="https://www.olark.com/values"><strong>#Chill</strong></a><strong>.</strong> Olark has never been a “typical” 60-hour-a-week tech startup. Bootstrapping and staying independent meant that we needed everyone to be energized for the long term — and that meant creating space for flexible work, parental leave, unplugged paid vacations, breather weeks between quarters, and laid-back time together as a team. We’ve figured out how to work sustainably, which is something far too many companies never learn.</li></ul><blockquote>We’ve figured out how to work sustainably, which is something far too many companies never learn.</blockquote><ul><li><strong>We developed talent internally.</strong> The decision to build a unique and independent company was also a decision to build a leadership team that understood our product, culture, and vision. Prioritizing Olark-specific knowledge and alignment has meant that the people who fit our leadership profile may not have decades of corporate experience or degrees from top universities — what they often do have is a history of creating impact at Olark, often starting as individual contributors and developing skills in multiple areas until they’re ready to head up a team or take ownership of a product area. This focus on internal growth has helped us hire and retain talented people who would likely have hit a ceiling at many bigger companies.</li><li><strong>We failed a lot. And we learned a lot.</strong> In declining acquisition, we reserved the right to make our own decisions by our own values. More often than not, we chose something that didn’t work at all. That’s humbling. But it’s also how we’ve gained perspective and grown. I’m still often wrong, but I have developed greater confidence as a leader; I know I can make informed choices and cope with failure when it happens.</li><li><strong>We built Olark to last</strong>. Olark now serves over 11,000 businesses, and we’ve created an organization and a culture that can continue even when both founders are <a href="https://www.wsj.com/articles/the-bosses-who-walk-the-walk-on-paternity-leave-11558949400">out on parental leave</a> at the same time, while weathering ups and downs as we continue to innovate. That doesn’t happen overnight — it really has taken a decade, and the opportunity to build something that lasts a decade doesn’t come along very often.</li></ul><p>So — what if? What if we’d sold Olark, taken the money, and re-invested it in our next big idea? What if we’d risen to leadership positions in a larger corporation with more social influence? Those other possible outcomes would not have been bad, or wrong. I’m not sharing this story to say that you should never sell your company — I’m saying that you should align your decisions with your values first and foremost. If you can do that, even when people question you, you’ll have few regrets.</p><blockquote>I’m not sharing this story to say that you should never sell your company — I’m saying that you should align your decisions with your values first and foremost.</blockquote><p>I’ll never know where we’d be today if we’d been acquired. But I know Olark is a company I’m excited to lead for another decade or two — and also that it’s a company that Olarkers are excited to work for. I have a balanced life, great customers, and a happy team, and I think that means that even if there was no one “right thing to do”, I at least did do right by my teammates, customers, and our shared values.</p><p>Now, I’ll open it up to you. What decisions are you facing in your business? How do you weigh the pros and cons, and how do you gut-check possible directions against your values? Let’s talk about the “what if’s?” and unanswered questions. Uncertainty, after all, is only human.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6442af671326" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why you (yes, you, the CEO) should be talking directly to customers]]></title>
            <link>https://olark.medium.com/why-you-yes-you-the-ceo-should-be-talking-directly-to-customers-93cd24ac3472?source=rss-f218a12fa80f------2</link>
            <guid isPermaLink="false">https://medium.com/p/93cd24ac3472</guid>
            <category><![CDATA[customer-feedback]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[small-business]]></category>
            <category><![CDATA[ceo]]></category>
            <category><![CDATA[customer-engagement]]></category>
            <dc:creator><![CDATA[Olark]]></dc:creator>
            <pubDate>Thu, 07 Nov 2019 19:05:32 GMT</pubDate>
            <atom:updated>2019-11-11T18:21:31.198Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/75/1*YiH2q8C1w8EpnbzzzhNxYw.png" /><figcaption><em>By Ben Congleton, Chief Executive Olarker</em></figcaption></figure><p>In 2013, four years after co-founding <a href="https://www.olark.com/">Olark</a>, I was waiting for some friends to order at a Starbucks in Mumbai when a woman approached me and commented on my Virginia Tech t-shirt. I was jet-lagged, but energized — being in a new place always gives me energy — and eager to connect with people. So, even though I was just barely finding my footing after only 8 hours in a city that couldn’t have been more different from Palo Alto, I struck up a conversation.</p><p>Talk about a small world. The woman, it turned out, was Aditi Avasthi, founder and CEO of <a href="https://www.embibe.com/">embibe</a> — an early Olark customer, and now one of the most successful e-learning companies in India. Our conversation ultimately led to an impromptu tour of Mumbai, including a post-Starbucks jet-lagged presentation at her company’s headquarters. Aditi and I talked at length about the challenge of building trust with students as she disrupted test prep for national exams in India; seeing her office, and meeting the passionate individuals who made up her small team, gave me so much more context about her business than I could ever have hoped to pull from a spreadsheet or graph. I was so focused on in the conversation that I arrived back at the hotel with only an hour to spare before the wedding I had flown to India to attend — my wife had started to think I might have been kidnapped.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*1Q5pUGmaqBkc4z1gEQh7WA.png" /><figcaption>At the embibe offices in Mumbai</figcaption></figure><p>Businesses exist to serve their customers — but whether you’re the CEO, middle management, or an individual contributor, it’s all too easy to get caught up in the operations and forget about the very real people who are buying and using your product. To avoid that, I’ve tried to spend as much time as possible talking with Olark customers over live chat, on the phone, and in person. These conversations keep me grounded in the realities of our customers’ day-to-day, and they also fuel my creativity as I think about how Olark can contribute to our customers’ goals for the future.</p><p>Over the last two years, though, I found myself focusing more on building Olark’s internal organization, and less on the customer-facing side of the business. Many of the challenges we were facing as a company were more internal than external, and in the wider context of life (including becoming a new dad — my wife and I made the transition from 0 to 2 kids in just over two years!) I had to be somewhat selective about where I put my energy.</p><p>This spring, though, I returned from parental leave with a mission. I wanted to step back into the role of customer champion and re-ignite our focus on customers. Specifically, I wanted to go beyond providing amazing customer service (which our Customer Service team <a href="https://blog.olark.com/olark-live-chat-a-gold-stevie-award-winner">definitely has covered</a>) to build a sense of connection with and passion for the people who we serve with our product. It was a big vision, but it actually boiled down to a simple process — talk to our customers, listen to their stories, and share their perspectives both within and outside of our organization.</p><p>So, I started inviting customers to chat. I hopped on the phone with a director of global customer service who had slipped in a hotel bathroom and was working from home while she healed. I talked to a VP of marketing who’d stopped working weekends so he could spend more time with his 17-year-old son. I took a verbal tour of a family-owned envelope factory, helped one customer optimize their automation rules, and learned that another cares deeply about response times because their business is built on turning prototypes around quickly. And in a very fun meta-discussion, I listened while a longtime friend and potential customer told me about the process of talking with more than 300 of <em>his</em> customers before launching their most recent app.</p><p>In case you stop reading here, I want you to know that <strong>these deep, open-ended, and occasionally rambling conversations have been one of the best things I’ve done as Olark’s CEO. </strong>My calls varied in length from 15 to 90 minutes, but every single one was filled with insights and context that I can use to motivate our team, drive product decisions, and keep myself energized and excited for the future.</p><p>If you’re leading a business, you should be setting aside time to talk to customers and understand their challenges — and not just in a narrow user research or customer service context. And if you’re not sure where to start…well, hang in there through a few more paragraphs, and I’ll tell you what worked (and didn’t) for me.</p><h3>Recruiting customers</h3><p>Conversations, of course, are two-sided — so once I set my sights on talking to customers, I had to find customers who were open to talking to me.</p><p>I started with a list of goals. I knew that I wanted to:</p><ol><li>Talk with customers across different industries (e-commerce, hospitality, education, legal services, etc.)</li><li>Talk with customers of a variety of sizes (sole proprietor to large company, one chat agent to several dozen or more)</li><li>Go deep to understand how live chat fit into the bigger picture of the customer’s business — this meant that I needed customers to commit to at least a 20-minute call.</li></ol><p>Then, I created an initial list of customers to reach out to. That list included:</p><ul><li>Our 500 largest customers</li><li>Our 500 smallest customers</li><li>Accounts recommended to me by our customer service team (essentially, anyone who they thought would appreciate a phone call, for any reason)</li><li>A selection of customers who responded to our new account welcome email with a personal note or support question</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/502/1*WmNeC2-vmAHqoEnLKoKbuw.png" /><figcaption><em>I used google sheets to track my outreach and progress against my goals for the project.</em></figcaption></figure><p>Armed with this (sizable) list, I tried a few approaches to reach out and recruit customers. The first was an old-school <strong>“do stuff that doesn’t scale” approach</strong> — I combed through customer websites, explored LinkedIn, hand-picked individual contacts, and wrote personalized emails explaining my goals and inviting them to set up a call. My first attempt completely failed to get a response:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/502/1*GiqCRQNDwwEr63lGSr1pOQ.png" /><figcaption><em>One of my first emails, which elicited radio silence.</em></figcaption></figure><p>I iterated on the email and tried again. I knew I couldn’t keep up the super-personal approach indefinitely, but taking more time with the first few recruits helped me hone in on an email style that resonated and earned responses.</p><p>The third iteration of my email finally led to a few great calls—however, I had realized by this time that even when I spent hours scrutinizing LinkedIn and our customer database, I was still mostly guessing at who to contact. So I stopped presuming that I could parse out every customer’s org chart, and started simply emailing multiple people at each company and <strong>asking for an introduction to the right person</strong>. This process was much more efficient, and with less time spent finding the right contact I was able to focus my energies on listening closely to our customers, sharing feedback with the team, and finding interesting customers to reach out to. I also began experimenting with subject lines and template copy that could be reused, with minor tweaks, across customers.</p><p>Eventually, I landed on a <strong>generalized email </strong>that captured most of what I’d found myself writing in each personalized message. At the scale I was emailing customers (tens at a time, not thousands) it appeared that the subject line did make a big impact, so I quickly adapted the subject line for each email before sending it off. Once I got into a rhythm, <strong>I found that I could send about 50–60 of these semi-personalized emails in about an hour</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/502/1*_pM4YJtFEC-bVEkbF6_Iqw.png" /><figcaption><em>This is the email template that I’m using now; I tailor it slightly to each customer.</em></figcaption></figure><p><em>Note: If you want to email all of your customers at once, </em><a href="https://www.groovehq.com/blog/customer-development"><em>here’s a great example email template from Groove</em></a><em>. I’m keeping my messaging a little more customized for now, but I could see myself trying an approach like Alex’s in the future!</em></p><p>I’m still using this approach, and have seen about a 20–30% response rate (on a per-business basis), which I’m extremely happy with — especially given that one member of our marketing team, who I’ll allow to remain anonymous, bet me I’d never see response rates in the double digits. I still think there’s room for improvement, though. I’d like to block out time in my calendar and allow customers to self-schedule calls, for example, although I do wonder if a list of appointment slots will feel less personal. I’m continuing to experiment, and by the end of the year, I want to have a system in place where I can reliably talk to 2–4 customers a week without a lot of coordination.</p><h3>Asking the right questions</h3><p>At Olark, we have a great team of designers and PMs who regularly run user studies and product-focused interviews. I wanted my customer conversations to have a different focus. I was interested in improving my customer intuition, building a library of customer stories to motivate our team, gaining a more complete view of the people using our product and the challenges they face in their roles, and building long-term relationships.</p><p>I also wanted to have genuine, free-flowing conversations. So I went into the first few calls with a list of questions, but didn’t try too hard to keep things “on track” — if my first question sent us off on an hour-long tangent, that was fine, so long as I was learning and connecting with the customer. I noted the questions that elicited interesting responses, and iterated from there. At this point, I have a loose script that looks something like the following, although I still ad-lib quite a bit:</p><ul><li><strong>Intro</strong>: I start the conversation by thanking the customer for their time and explaining that I’m here to listen and learn about their role, the challenges they’re facing, and how Olark helps or hinders them in overcoming those challenges. I intentionally try to set a personal tone — as we move through the standard “How are you?” small talk, I mention things happening in my family (e.g., I’ve been single-parenting my daughter while my wife is on the east coast helping her mom recover from a bike accident). Setting a personal tone and opening up beyond the standard “good, and you?” call and response helps build trust and makes for much more genuine conversations.</li><li><strong>Tell me about your role at [company]</strong>. This question helps me get a sense of how live chat fits into the company’s strategy and management structure. Usually, it also elicits information about the interviewee’s day-to-day routine and the skills and resources (e.g., IT support) that they do or don’t have access to.</li><li><strong>What are your goals for the quarter/year (or longer-term)? How do <em>you</em> know you had a good quarter? What performance indicators do you track and report? </strong>I want to understand what success looks like for this person and their team, so I can gauge how much we’re actually helping them and where we could provide better tools or information.</li><li><strong>What are your biggest challenges right now?</strong> When I ask this question, I emphasize that I’m looking for insight into their biggest challenges <em>overall</em>, not just with respect to Olark (I assure them we’ll talk about Olark’s shortcomings later!). Are they juggling a lot of competing priorities? Wearing many different hats? Struggling to get access to the human, technical, or strategic resources they need?</li><li><strong>What are your biggest challenges with Olark?</strong> If the interviewee’s challenges with Olark are related to their biggest challenges overall, I know we have an immediate opportunity to help them. Sometimes this means relaying feedback to our product team and advocating for a new feature, but it can also mean teaching the customer a few tricks while I have them on the call. For example, I’ve been able to solve problems for some customers just by walking them through a creative use of <a href="https://www.olark.com/api">our API</a>.</li><li><strong>What do you like about Olark?</strong> I’ll admit this is mostly a feel-good question, but whenever I get an unusual or unexpected answer, I’m reminded of the tremendous diversity in our customer base. People use Olark in all kinds of different ways, and features that we consider “nice to have” can be critical to a customer’s workflows.</li><li>(for newer customers) <strong>How did you hear about us?</strong> When possible, I love hearing about the journey a customer took to find Olark, and this is also useful information for our Marketing team.</li></ul><p>The questions above are solid conversation-starters, but they’re just that — starters. <strong>If a customer’s answer feels incomplete, or piques your curiosity, follow up</strong>. I’ve learned much, much more from followup questions that I have from my basic script — why one customer prefers us to a competitor, why another switched live chat providers after an internal reorg, how vacations and parental leave affected another’s workload and ability to take advantage of our software. I’ve also followed up via email, and asked customers to share artifacts (such as flow charts and spreadsheets) that have helped me better contextualize their feedback. Artifacts are invaluable for showing our team how Olark fits into a customer’s larger workflow.</p><h3>Sharing insights</h3><p>One of my goals for this project was to share what I learned from each interview with our entire team, ideally in a way that would generate excitement around customer stories. My first attempt at this was to simply post a link to my interview notes in Slack. That completely flopped — no one clicked the link, of course, because everyone’s busy, and I hadn’t done much to make it sound interesting.</p><p>After watching a couple of lonely links fade into the Slack archive, I realized I needed a better hook. I started writing up a short summary of each interview — almost like a teaser for the detailed notes — which I shared in our main Slack channel. I also created a new channel, <em>#customers</em>, where I shared the full notes doc and invited questions and comments from the team. Finally, I tried to share summaries and notes on Fridays, which tend to be more social and less “heads down” for most Olarkers.</p><p>So far, the elevator pitch has worked. I’ve seen engagement in Slack from across all of our major departments (engineering, product, marketing, CS, and HR), and have heard customer insights reflected back in meetings and presentations; a group of Olarkers even put together a “customer scavenger hunt” project at our annual company retreat, with no prompting from me. In short, after holding about 30 customers calls and sharing around 20 summaries with the team, I’m seeing a big impact on the company — and on my own energy and engagement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/502/1*b6bhDb18jMapQew8XqwlOA.png" /><figcaption><em>Posts like these had much higher engagement than just linking notes to a channel.</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/502/1*1-gXKNc57NUlFnjzOXrM7Q.png" /><figcaption><em>Olarkers joining in these discussions included everyone from frontline support to backend DevOps.</em></figcaption></figure><h3>What’s next?</h3><p>I definitely have some product recommendations to make based on these interviews. But for me, the most important lesson has been that <strong>deep customer conversations are indispensable</strong>. These open-ended discussions yield insights and inspiration that you just can’t get anywhere else. My plan for the next few months is to continue a steady cadence of customer calls, refine my process, and set up opportunities for others at Olark to talk with customers, too.</p><p>In conclusion — I’d like to challenge you to pick up the phone and call one of your customers. Get to know them, ask about their work, and brainstorm solutions to their problems. Even if you go in with no script, no plan, and no goals aside from listening and learning, I guarantee you won’t regret it. Share summaries of your calls with your team — it can be incredibly motivating for them to understand the stories of the people your business is helping every day. And if you can’t think of a customer you’d like to talk to offhand, or if you find yourself digging to find 5 customer examples for a presentation, just start reaching out — you’ll be surprised by the impact it will have on you and your organization.</p><p><em>PS — If you have a tip, question, or comment related to customer conversations (or if you’re an Olark customer who’d like to schedule a chat!), I’d love to hear from you. Find me on Twitter </em><a href="https://twitter.com/jaminben"><em>@jaminben</em></a><em>, or reach out on </em><a href="https://www.linkedin.com/in/bencongleton/"><em>LinkedIn</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=93cd24ac3472" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Starting remote employees on the right foot]]></title>
            <link>https://olark.medium.com/starting-remote-employees-on-the-right-foot-d810126e2225?source=rss-f218a12fa80f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d810126e2225</guid>
            <category><![CDATA[human-resources]]></category>
            <category><![CDATA[onboarding]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[remote-work]]></category>
            <dc:creator><![CDATA[Olark]]></dc:creator>
            <pubDate>Thu, 03 Oct 2019 21:07:53 GMT</pubDate>
            <atom:updated>2019-10-03T21:07:53.367Z</atom:updated>
            <content:encoded><![CDATA[<figure><a href="https://www.olark.com/about"><img alt="" src="https://cdn-images-1.medium.com/max/80/1*aFl0gofbOcW-LK_CKVwQXw.png" /></a><figcaption>By Mandy Smith, Director of PeopleOps, <a href="https://medium.com/u/f218a12fa80f">Olark</a></figcaption></figure><p>I’ll never forget the second day of my first remote job. The first day was the usual — signing all the things, attending all the things, logging into all the things. But when the second day arrived, I had no idea what to do.</p><p>I was used to an office job and a structured 9–6 schedule. I’d drive to work, check in with my manager and team, and make a visit (or six) to the communal coffeepot. I’d have lunch around noon, usually with a few folks on my team, and then I’d huddle in a windowless office for the rest of the day. My time was accounted for, everything was in person, and I never second-guessed the routine.</p><p>Now, I was sitting at my kitchen table, feeling more unsure than I had since the first day of my very first paying job. Weird thoughts crept in — <em>Do I need to tell someone if I’m going for a walk? Should I ask permission before I take a break to make breakfast? If I hear the ding of the washing machine informing me, hey, it’s time to put your clothes in the dryer — is that cool? And why am I being so paranoid, anyway?</em></p><p>I eventually settled in, and in retrospect, I can laugh at my second-day freakout. But I also feel for my slightly-younger self — and for my employer at the time. The shift from an in-house job to remote work is quite frankly, pretty weird, and onboarding a new remote employee requires a different, not-always-obvious approach. There’s a lot of room for mistakes, misunderstandings, and existential crises.</p><blockquote>The shift from an in-house job to remote work is quite frankly, pretty weird, and onboarding a new remote employee requires a different, not-always-obvious approach.</blockquote><h3><strong>Rethinking remote onboarding</strong></h3><p>For someone new to remote work, the first few weeks are going to be a bit of a culture shock. Even a seasoned remote employee will probably stumble around a little as they’re learning new tools, etc. So, when I started thinking about Olark’s onboarding process, my challenge was (and is) to address any awkwardness and uncertainty head-on, assure everyone that those feelings are normal, and ease new hires into the remote routine in a fun, human way.</p><p>My first piece of advice for any onboarding lead is simply to <em>overcommunicate</em>. Communication is important in an office environment, too, but it’s absolutely critical when you’re remote, and even more so if the employee you’re onboarding is new to remote work. Start by checking in with the new hire daily, and keep talking on a regular schedule for at least the first month. Set up recurring calls. Ping them in Slack (or whatever chat tool you use) just to say hi. If you feel like you’re bugging them a little <em>too</em> much, you’re doing it right.</p><blockquote>Start by checking in with the new hire daily, and keep talking on a regular schedule for at least the first month. If you feel like you’re bugging them a little <em>too</em> much, you’re doing it right.</blockquote><p>Over the course of a new hire’s first few weeks, I make a point to ask the following questions, repeatedly, through various channels (video calls, Slack messages, structured surveys, etc.):</p><p><strong>How are you doing?</strong> Simple — and very effective for flagging small problems before they get bigger. The only problem with this question is that it tends to elicit a vague response. If the new hire is “doing pretty good” for days on end, try being more specific: <em>How are you feeling about your schedule? Your workload? Are you happy with your home office setup or coworking space? How did your meeting with [employee] go?</em></p><p><strong>Have you had lunch?</strong> Or breakfast? Did you get out for a walk this morning? You can tweak these questions, of course; the point is to reinforce that yes, their schedule is flexible, and no, they don’t need permission to eat, take the dog out, etc. If their responses amount to “I walked to the mailbox and ate a cracker”, remind them that work (including the overwhelming number of things they’re learning and absorbing in their first few weeks) will always be there, and that you want them to establish a sustainable rhythm for the long term.</p><p><strong>How can we make this onboarding process better? </strong>Once the new hire has a week or two under their belt, start asking for their feedback. What’s been easy, helpful, or otherwise positive? Where have they gotten stuck? Show them that you want to keep improving, and get them engaged in brainstorming and making changes — this openness goes a long way toward smoothing over any bumps they’ve encountered, not to mention toward eliminating those bumps for your next hire.</p><p>In addition to overcommunicating (and then overcommunicating some more), there are a few best practices that I’ve integrated into Olark’s onboarding process over the past three years. Some of them might seem obvious, while others are less intuitive, but they’ve all made our onboarding much smoother:</p><p><strong>If you work remotely, onboard remotely</strong>. When I started working at Olark, our hiring and onboarding processes still included some in-person time. But that ultimately felt disingenuous; if we were really going to commit to being a fully remote company, we needed to be able to hire and onboard remotely, too. And, practically speaking, onboarding in person just wasn’t that effective. The new hire got into a short-term rhythm of in-person interactions, and then needed just as much adjustment time to establish a remote routine once their onboarding period ended.</p><p>So, as with our <a href="https://medium.com/@Olark/dos-and-donts-for-building-a-remote-team-lessons-from-a-hiring-manager-f55d61ec8849">hiring process</a>, we took onboarding from in-person to remote — and I’d encourage other remote teams to do the same. Getting a new hire familiar with your company’s day-to-day operations is a big part of onboarding, and you can’t accomplish that if you onboard in an environment that’s significantly different from the one they’ll actually be working in.</p><blockquote>Getting a new hire familiar with your company’s day-to-day operations is a big part of onboarding, and you can’t accomplish that if you onboard in an environment that’s significantly different from the one they’ll actually be working in.</blockquote><p><strong>Create an onboarding plan</strong>. What meetings does the new hire need to attend? Who do they need to talk to, both within and outside of their direct team? What fun activities can they get involved with? What information should they review?</p><p>Write up a list of action items for at least their first two weeks. Then, go ahead and schedule a week’s worth of meetings and heads-down time on their calendar, so they can focus on ramping up without worrying about how to fit everything in.</p><figure><a href="https://hello.olark.com/hubfs/Blog_Images/2019/onboarding_infographic.jpg"><img alt="6 steps to successfully onboard remote employees" src="https://cdn-images-1.medium.com/max/1024/1*T5S3wyI-EQsHUmorXdN9HA.jpeg" /></a><figcaption>A simple six-step process for successful remote onboarding. <a href="https://hello.olark.com/hubfs/Blog_Images/2019/onboarding_infographic.jpg">Download a high-resolution version of this graphic</a>.</figcaption></figure><p><strong>Designate a point person</strong>. Think of the point person as playing a similar role to a friendly neighbor or officemate in an in-person workplace. They’re there to make sure the new hire feels welcome and supported; they don’t need to have all the answers, but they do need to provide context, suggest resources, and steer the new hire in the right direction on everything from vacation policies to backend bugs. They also need to be available just to chat, especially if the new hire is frustrated, confused, or otherwise in need of a good ear.</p><p>It usually makes sense for the point person to be someone from the new hire’s immediate team, but you can appoint anyone who knows the ropes, as long as they’re excited about welcoming a new addition to the company.</p><p><strong>Introduce new hires publicly</strong>. Here’s a personal story for you. I had just landed a super exciting freelancing gig, and the timing was perfect — the team was about to hold their annual summit, which meant I’d have a great opportunity to dive in, meet everyone, and start planning the year ahead. On the first day of the summit, my manager kicked things off by introducing all the new hires…except me.</p><p>Granted, I was dialing in, and the rest of the team was meeting in person. But they’d hired me to work remotely, and they knew I was on the phone. I was left wondering how folks outside my immediate team would even know that I existed. Was I going to have to introduce myself to everyone individually? I vowed then and there that I’d never allow a new hire to feel that feeling.</p><p>I like to use as many channels as possible to introduce new hires (again, overcommunication), including a company-wide email announcement, messages in our company-wide Slack channel, and live intros on as many video calls as possible. I also create a dedicated “welcome” channel in Slack for each new hire, where other team members can introduce themselves and answer questions.</p><p><strong>Spend time on tools</strong>. Most remote team rely heavily on technology to communicate — and if a new hire isn’t comfortable with your instant messaging, videoconferencing, or project management software, they’re going to have a hard time asking for help. That means that demoing tools and answering questions should be one of your very first onboarding action items.</p><p>Even if the hire has experience with Slack, Zoom, Trello, etc., take ten minutes to check that their accounts are set up correctly. You should also familiarize new hires with any tool-related norms that might be specific to your company. For example, should they set their Slack status to “away” when they go to lunch? Should they mute their audio on group video calls, and is it okay to turn off video if they’re having a bad hair day?</p><blockquote>Familiarize new hires with your company’s specific tool-related norms. Should they set their Slack status to “away” when they go to lunch? Is it okay to turn off video on calls if they’re having a bad hair day?</blockquote><p><strong>Introduce culture early</strong>. Given everything else a new hire has to absorb, explaining your company’s history and values might not seem urgent. But I’ve found that a high-level orientation in the first week or two is incredibly valuable — especially if an employee is new to remote work and anxious about building connections to their teammates.</p><p>One thing I love about our founders is their unwavering dedication to our <a href="https://medium.com/@Olark/from-0-to-10-our-bumpy-but-worth-it-road-to-a-co-created-culture-fc62d3cf1dd4?source=your_stories_page---------------------------">co-created culture</a>. As such, they play an important part in our onboarding process — specifically, they give new hires a deep dive into why they built Olark, what they value in business, how our culture has evolved, etc. They are dedicated to making sure the new hire feels welcomed, and they’re able to provide some historical context for our <a href="https://www.olark.com/values">values</a> and processes. Win win.</p><p>New Olarkers almost always come away from those conversations motivated, excited to contribute, and grounded in a clear understanding of why we built Olark and where we want to take the company from here.</p><p>One final note: if you’re onboarding remote employees, make sure you’re putting yourself in their shoes. You’ve been a new employee before, and possibly even a new remote employee. What resources were most useful? What do you wish you’d known or done earlier? Ask yourself how you can provide those things for new hires at your company — maybe there are recorded presentations they can watch, Slack channels they should join, or opportunities to share something they’re passionate about with the wider team.</p><p>Experiment, overcommunicate, and iterate from there. And let me know what you learn — because even after dozens of remote hires, I’m still tweaking my process, too! You can share your tips and questions in a comment on this post, or reach out to me through Olark’s <a href="https://www.facebook.com/olarklivechat/">Facebook</a>, <a href="https://twitter.com/olark">Twitter</a>, or <a href="https://www.linkedin.com/company/olark">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d810126e2225" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From 0 to 10: Our bumpy (but worth it!) road to a co-created culture]]></title>
            <link>https://olark.medium.com/from-0-to-10-our-bumpy-but-worth-it-road-to-a-co-created-culture-fc62d3cf1dd4?source=rss-f218a12fa80f------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc62d3cf1dd4</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[small-business]]></category>
            <category><![CDATA[founder-stories]]></category>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[company-values]]></category>
            <dc:creator><![CDATA[Olark]]></dc:creator>
            <pubDate>Wed, 28 Aug 2019 20:38:19 GMT</pubDate>
            <atom:updated>2019-08-29T03:26:41.262Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This post is the third in our 10 year anniversary series. Want to catch up? Read the </em><a href="https://medium.com/@Olark/from-0-to-10-how-we-built-an-unconventional-silicon-valley-startup-10f6694665b9?source=---------4------------------"><em>series intro</em></a><em> and </em><a href="https://medium.com/@Olark/from-0-to-10-starting-a-business-by-solving-our-own-problems-bfc71c429f95?source=---------3------------------"><em>Olark’s origin story</em></a><em>.</em></p><h3>Early days: “Who used my toothbrush?!”</h3><p>When Olark joined YCombinator in the fall of 2009, our original co-founders moved in together in Mountain View, California. We were four co-founders, one spouse, and two cats, sharing a soulless three-bedroom townhouse. The dining room served as our fourth “bedroom” and the “door” (a curtain) was certainly not respected by either of the cats.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wips14QKrPGEZBXk8aWn5A.png" /><figcaption>The original Olark house — not exactly ideal working conditions.</figcaption></figure><p>Today, of course, we attach some sentimental value to that old townhouse. But as you might imagine, it wasn’t especially easy at the time. We had a variety of expectations and communication styles. Our clashes included everything from product strategy to housekeeping standards.</p><p>Having a central purpose — building a company we wanted to work at — gave us the foundation we needed to survive the crucible and birth this early version of our team culture. So we talked, we argued, and we gradually established norms and processes that helped us navigate everything from new product features, to financial discussions, to dish duty. We moved to a bigger house with natural light and greenery. We sampled different project management tools. We shopped together at Costco, loading up on produce and falafel balls — we even bought a giant case of ramen that may or may not have followed us through at least a few moves. And we established a communal social life that gathered all different groups of friends together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*vM5kRwiwAAOQU013GT88wQ.png" /><figcaption>Bonding over homemade bread, which was a big part of our early co-founder culture.</figcaption></figure><p>As a tight-knit group of founders, we’d collaborated — or been forced to collaborate, in large part by physical proximity — to create the culture we wanted. And we had expected that collaboration around culture to continue organically as the company grew. But as we grew, we became a more diverse team, made up of people who didn’t always see eye to eye. Some of us were driven by creating order, while others thrived on chaos; some had years of corporate experience, while for others, Olark was a first “real” job.</p><blockquote>As a tight-knit group of founders, we’d collaborated — or been forced to collaborate, in large part by physical proximity — to create the culture we wanted. And we had expected that collaboration around culture to continue organically as the company grew.</blockquote><p>This diversity was powerful, but it came with ambiguity around cultural expectations and what it meant to be an Olarker. With each addition to the team, we had cheerfully absorbed new working patterns and communication styles, telling ourselves that our culture was only getting better — but around the 10-employee mark, we started seeing tensions that couldn’t be resolved through simple compromise. For the first time, we felt ourselves drifting away from some of the values we really cared about.</p><h3>Growing pains: Team retreat, or Modern Family?</h3><p>In 2012, we held our first in-person company retreat. We felt that bringing the whole team together would fix a lot of things — that we’d quickly move past those underlying tensions, build deeper relationships, and plot a path forward.</p><p>Boy, were we in for a wakeup call.</p><p>Colleagues who we’d convinced ourselves were “getting along fine” griped, fought, and walked out of meetings. People talked over and past each other and clung tightly to their own perspectives and desires. To our shock, we realized we were back where we’d started as roommates — edgy, upset, and more than a little confused — but now we had 12 people not only “living” in the same small company, but also literally trapped together in a big house for a week.</p><h3>Hitting reset: Everyone gets an oar in the culture boat</h3><p>Since we clearly weren’t going to get any work done, much less enjoy socializing, until we’d addressed the elephants in the room, we scrapped our plans for the retreat and shifted the focus to cultural alignment. We had no desire to dictate culture to our employees (and we didn’t have much confidence in that approach, anyway). We’d hired smart, compassionate, creative people, and we wanted them to play an equal role. We just had to make sure they understood that expectation, knew how to contribute, and were recognized and rewarded for their efforts.</p><blockquote>We had no desire to dictate culture to our employees (and we didn’t have much confidence in that approach, anyway). We’d hired smart, compassionate, creative people, and we wanted them to play an equal role.</blockquote><p>First, we gathered the team and took advantage of the face-to-face time to create the first version of our <a href="https://www.olark.com/values">company values</a>. Everyone contributed to what became an incredibly fun brainstorm, scribbling ideas across hundreds of post-it notes and dozens of whiteboards. We distilled all the input, talked through lingering concerns, and checked with every single Olarker to make sure they felt confident signing off on the final draft.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/332/1*oHW8T71B-HVjbvYA1_UFqw.png" /><figcaption><em>Creating our values — still one of the best brainstorms I’ve ever been part of.</em></figcaption></figure><p>A few weeks later, we used a similar collaborative process to draft our first mission statement. We started kicking off our weekly all-hands meetings by thanking teammates who’d exemplified our newly-articulated values, and over time, we also updated our <a href="https://medium.com/@OlarkLiveChat/dos-and-donts-for-building-a-remote-team-lessons-from-a-hiring-manager-f55d61ec8849?source=post_stats_page---------------------------">hiring process</a> to ensure that we spoke in depth with each candidate about our cultural foundations.</p><p>And, well — the team took it from there. Articulating our mission and values set a precedent of co-creation and co-ownership that has bolstered so many culture initiatives over the years.</p><p>I still think about culture constantly, and give little nudges now and then, but Olarkers have stepped up to apply our values to everything they do, from making tough product and business decisions to establishing a huge variety of cultural traditions that I could never have dreamed up on my own.</p><h3>Moments that shaped our culture: Gnomes, karmies, and more…</h3><p>A few years after that first retreat, one of our backend engineers — a brilliant and somewhat imposing guy who wrote server code all day — came to us with an idea. He wanted to start a secret society of Olarkers who would send little snail mail gifts to their colleagues for birthdays, work anniversaries, family events, and “just because”.</p><p>The initiative, which we dubbed the “Olark Gnomes”, launched with our enthusiastic blessing. One of the trickiest elements of remote culture is celebration — there are no donuts in the breakroom or birthday cakes at team sync. The Gnomes gave us a means of celebrating and surprising one another remotely. And although that particular engineer has since moved on to new adventures, his legacy lives on in the dozens of little anonymous packages that Olarkers receive each year.</p><blockquote>One of the trickiest elements of remote culture is celebration — there are no donuts in the breakroom or birthday cakes at team sync. The Gnomes gave us a means of celebrating and surprising one another remotely.</blockquote><p>The Gnomes are just one example of the ways that our employees have stepped up to shape Olark’s culture. Here’s another — in a similar fashion, one of our early engineers took it upon himself to build a Slackbot extension that gives “karma”. If you were to join an Olark <a href="https://slack.com/">Slack</a> channel, you’d see a lot of this:</p><ul><li><em>@betts++ @rhi++ so much #help</em></li><li><em>@matt++ #make ing my slides look :100:</em></li><li><em>@mandy++ reminding me to #chill</em></li></ul><p>What’s up with the “++”? It’s a little <a href="https://api.slack.com/bot-users">Slackbot</a> magic built by another of our early engineers. For every “++” after your name, our Slackbot (affectionately nicknamed Olarkami) issues you a karma point and posts your total karma tally. We give karma all the time — to recognize teammates who are living our values, to compliment a funny gif or photo, or whenever we feel like someone deserves a shoutout. Because so much of our communication takes place in Slack, giving and receiving karma is a daily habit for all of us — which makes it an amazing culture-building tool.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/1*Fp3P9FK0ctRcl8oYev6UUA.png" /><figcaption>A double-whammy culture moment — Gnomes getting karma!</figcaption></figure><p>We have Karmie Awards, too — at our annual retreat, we host a goofy awards ceremony to highlight the little things our teammates have done to contribute to our culture. We’ve given awards for Cutest Pet Photo, Worst Dad Joke, Best Custom Emoji, Funniest Out-of-Context Quote, etc., rotating the awards committee each year so that everyone has a chance to recognize something that helped them or made them smile.</p><p>On the less-whimsical side, employees have also taken the lead on proactively creating our <a href="https://blog.olark.com/what-is-the-olark-parental-leave-plan">parental leave policy</a> (before any Olarker had children!), programming <a href="https://blog.olark.com/what-is-the-olark-retreat">retreat activities</a>, kicking off open conversations around topics like <a href="https://medium.com/@Olark/its-2017-and-mental-health-is-still-an-issue-in-the-workplace-61efbef092f">mental health in the workplace</a>, and much, much more. Today, almost all of our employees say our culture is one of their favorite things about Olark. With everyone working on our culture, we’ve been able to build a culture that works for everyone.</p><p>That first retreat was rocky, no question, but we’re grateful for the fact that it forced us to take a hard look at culture early on, and creating our Core Values that week established a precedent for co-creation and co-ownership that’s still with us a decade later. Our culture makes work easier and more fun — but even more important, our values and mission help us make hard business and product decisions, and earn buy-in from our team and customers when those decisions are controversial. As a small business in a fast-moving industry, we feel incredibly lucky to have that solid foundation.</p><blockquote>That first retreat was rocky, no question, but we’re grateful for the fact that it forced us to take a hard look at culture early on, and creating our Core Values that week established a precedent for co-creation and co-ownership that still a decade later.</blockquote><h3>What we learned (hindsight is 20/20!)</h3><p>So — if we could rewind the clock 10 years, what would we tell our younger selves about stewarding culture in a small business? A few things:</p><ul><li><strong>Dig underneath conflict</strong> — Approach tensions with an open and curious mind; this argument may be exactly what you need to identify some of the things you and your teammates value most deeply.</li><li><strong>Get it in writing. </strong>When the core pieces of your culture are explicitly written out, it’s not only an incredibly helpful resource for your team when things feel like they’re “drifting”, but also gives future job candidates an explicit thing to opt into.</li><li><strong>Get everyone involved</strong>. Culture impacts your entire team. Everyone (including every new hire!) has both a right and responsibility to shape it in a way that works for them and shares something meaningful with their teammates.</li><li><strong>Culture is hard — but it’s worth the work.</strong> A great culture will help you work better and faster together, hire more amazing people, and generally have more fun building your business.</li></ul><p>If you’re facing a cultural challenge right now, or have advice for other small business owners and founders who might be looking to invest time and energy in their company cultures, we’d love to hear your perspective! Leave a comment on this post, or reach out on Twitter (<a href="https://twitter.com/jaminben">@jaminben</a> and <a href="https://twitter.com/mjpizz">@mjpizz</a>) or LinkedIn (<a href="https://www.linkedin.com/in/bencongleton/">Ben</a> and <a href="https://www.linkedin.com/in/mjpizz/">Matt</a>), to join the conversation.</p><p><em>Share this post on </em><a href="https://www.facebook.com/sharer/sharer.php?u=https%3A//medium.com/%40Olark/from-0-to-10-our-bumpy-but-worth-it-road-to-a-co-created-culture-fc62d3cf1dd4"><em>Facebook</em></a><em>, </em><a href="https://twitter.com/intent/tweet?text=%23CompanyCulture%20takes%20everyone%20(especially%20in%20a%20%23SmallBusiness%20or%20%23RemoteTeam!),%20and%20it%20doesn&#39;t%20happen%20by%20accident.%20%40Olark%20has%20a%20great%20story%3A%20https%3A//medium.com/%40Olark/from-0-to-10-our-bumpy-but-worth-it-road-to-a-co-created-culture-fc62d3cf1dd4"><em>Twitter</em></a><em>, or </em><a href="https://www.linkedin.com/shareArticle?mini=true&amp;url=https%3A//medium.com/%40Olark/from-0-to-10-our-bumpy-but-worth-it-road-to-a-co-created-culture-fc62d3cf1dd4&amp;title=From%200%20to%2010%3A%20Our%20bumpy%20(but%20worth%20it!)%20road%20to%20a%20co-created%20culture&amp;summary=%23CompanyCulture%20takes%20everyone%20(especially%20in%20a%20%23SmallBusiness%20or%20%23RemoteTeam!),%20and%20it%20doesn&#39;t%20happen%20by%20accident.%20%40Olark%20has%20a%20great%20story!&amp;source="><em>LinkedIn</em></a><em>!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc62d3cf1dd4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dos and don’ts for building a remote team: Lessons from a hiring manager]]></title>
            <link>https://olark.medium.com/dos-and-donts-for-building-a-remote-team-lessons-from-a-hiring-manager-f55d61ec8849?source=rss-f218a12fa80f------2</link>
            <guid isPermaLink="false">https://medium.com/p/f55d61ec8849</guid>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[small-business]]></category>
            <category><![CDATA[human-resources]]></category>
            <category><![CDATA[people-operations]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Olark]]></dc:creator>
            <pubDate>Wed, 14 Aug 2019 22:36:05 GMT</pubDate>
            <atom:updated>2019-08-14T22:36:05.164Z</atom:updated>
            <content:encoded><![CDATA[<figure><a href="https://www.olark.com/about"><img alt="" src="https://cdn-images-1.medium.com/max/80/1*aFl0gofbOcW-LK_CKVwQXw.png" /></a><figcaption>By Mandy Smith, Director of PeopleOps, <a href="https://medium.com/u/f218a12fa80f">Olark</a></figcaption></figure><p>Most of us have had at least one bad hiring experience — a recruiter who got too aggressive (or, conversely, ghosted), an interviewer who showed up unprepared, or even an unpleasant post-hire moment when we realized the job wasn’t what we’d been led to believe. But as someone who’s been part of this process for more than a decade, I’m still shocked by some of my friends’ and colleagues’ hiring horror stories. Who are these people, I wonder, who are so blasé about hiring? Do they not understand the stakes?</p><blockquote>As someone who’s been part of this process for more than a decade, I’m still shocked by some of my friends’ and colleagues’ hiring horror stories.</blockquote><p>For a job candidate, the hiring process is the first impression of a company’s values, ways of working, and approach to supporting and caring for employees. For a company, it’s a means (often the only means, beyond scanning a resumé) of learning about a candidate’s personality, professional style, and strengths and weaknesses with respect to a role. It culminates in both company and candidate making a huge investment of time, money (the <a href="https://www.shrm.org/about-shrm/press-room/press-releases/pages/human-capital-benchmarking-report.aspx">cost of hiring and onboarding a new employee</a> is about $4,000), energy, and trust.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X-m8Rq4jv-FQGOdSd8Ekkw.jpeg" /><figcaption>My goal is to make prospective employees feel welcome, respected, and excited about working with us.</figcaption></figure><p>“Finding qualified employees” is one of the <a href="https://www.forbes.com/sites/jimblasingame/2017/01/21/top-10-things-that-keep-small-business-owners-up-at-night/#767c1abe2826">top ten concerns for today’s small business owners</a>. At a small company like <a href="https://www.olark.com/about">Olark</a>, a new hire might be one of just 4 or 5 people on a functional team, and they’ll interact almost daily with everyone who works here. The right person can lift the entire company up, and a bad fit can bring everyone down. That profound impact is part of what makes hiring my favorite part of being Olark’s Director of People Operations — and it’s also the reason I take hiring very, very seriously.</p><blockquote>The right person can lift the entire company up, and a bad fit can bring everyone down.</blockquote><p>Hiring at Olark is challenging and high-stakes not only because we’re small, but also because we’re remote. When I applied for my role back in 2015, the process took several months and culminated in an in-person interview. It was a great experience; I made genuine connections with everyone I met, and was inspired by the team’s energy and enthusiasm. After I started, however, I began thinking about how we could make hiring even better — and the in-person component nagged at me. I understood why a face-to-face meeting felt important, but it was also costly and time-consuming, and didn’t mimic the way the new hire would be working with us on a daily basis. So I took a deep breath, and scrapped it.</p><p>We’ve been hiring and onboarding new employees 100% remotely for several years now. It’s not always easy, but it has taught me a lot about what’s truly important, especially when bringing new members into a small, close-knit team. As we’ve refined our system, I’ve compiled a list of dos and don’ts that I hope will help all small companies — remote-first, remote-friendly, remote-curious, or happily co-located — develop more effective hiring processes. There’s a lot here, but my tips really boil down to building a process that’s genuine, transparent, and respectful of every candidate’s time and talents.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*tsIb5m5BnH64t3bBk0NbBw.png" /></figure><p><strong>Do: Keep it real</strong></p><p>During my first phone interview with Mark (now one of Olark’s senior backend engineers), my doorbell rang. Surprise — the dryer I’d ordered had arrived early. Mark and I were having a great chat, and I didn’t want to cut it off, but now I had a large appliance sitting on my porch. So I just got real with him: “This is weird, but I need to get this dryer installed. Is it okay if I call you back in 5 minutes?” We both laughed about it, and after the dryer was installed (unsuccessfully, but that’s a story for another day), we hopped back on the phone and finished our interview.</p><p>Mark was hired a few weeks later, and the dryer incident is still one of my favorite interviewing memories. It was a great reminder of the fact that life happens — and when you work remotely, life can happen unexpectedly, at your front door, smack in the middle of the workday. If a candidate gets a glimpse of your real life during the interview process — or if you get a glimpse of theirs — it’s really only a good thing. Take it in stride and work around it as you would with any friend or colleague.</p><p><strong>Do: Provide a “day in the life” experience</strong></p><p>The problem with most interview settings is that they’re, well…fake. Most people can practice their way into nailing an interview, and hiring managers can know interview questions front to back. But are you getting actual data on how well the applicant can do the job? Or are you both just doing the interview tango?</p><p>The only way to really know if someone can do what you need them to do, with the team they’ll actually be working with, is to put them in the real situation. This has become a non-negotiable step in our interview process. Final-round candidates at Olark complete a full-day “work-along”, during which they meet with teammates, dive into a project, present their work, and answer questions.</p><blockquote>Are you getting actual data on how well the applicant can do the job? Or are you both just doing the interview tango?</blockquote><p>The work-along has never failed us. By the end of the day, it’s 100% clear if an applicant is the right fit. The applicant also knows exactly what they’re signing up for — they’ve had a taste, they’ve seen the inner workings, and they know how our workflows operate. It’s truly a win/win.</p><p>Make sure you involve folks from other departments in the work-along, too. In a small company, collaboration across teams is the day-to-day norm; for example, a new Customer Service team member will be working with engineers, marketers, product analysts, and designers, so members of those teams should have an opportunity to meet candidates and weigh in. I often have Olarkers from different departments conduct non-technical interviews, meet with candidates informally, or to sit in on presentations. Diverse involvement gives us a wide range of perspectives on each candidate — and it gives candidates a much clearer picture of what it’s really like to work here.</p><p><strong>Don’t: Be too rigid</strong></p><p>Plan your interviews carefully, but don’t try to stick to a script. As long as you get the baseline data you need, there is absolutely nothing wrong with going off on a tangent or allowing a candidate to elaborate on something they’re passionate about. If you’re too focused on keeping an interview “on track”, you won’t learn anything about what it’s like to have a normal conversation with the candidate — the kind of conversation they’ll be having with you and your teammates every day if they’re hired.</p><p>Of course, to have a normal conversation, you need to make sure you’ve put the candidate at ease. Almost everyone gets at least a little nervous in an interview, but I’ve found that kicking things off with a simple “let’s keep this informal — I want to get to know you” goes a long way toward bringing out the real human.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*lvdY50kivpzHRab1YqxA-A.png" /></figure><p><strong>Do: Discuss salary right away</strong></p><p>I get a lot of raised eyebrows when I say this, but I firmly believe you should set salary expectations in the first interview. We all care about money — it’s a part of life. As a small company, Olark has a fixed budget for each new hire, and sharing that information upfront helps us ensure that we’re not wasting anyone’s time. We’d rather lose a great candidate on the first call than go through a month-long interview process only to learn that we can’t possibly pay them what they’re expecting.</p><blockquote>We all care about money — it’s a part of life. Sharing salary information upfront helps us ensure that we’re not wasting anyone’s time.</blockquote><p>Setting salary expectations up front also helps us keep salaries equitable, since we make it clear that we’re not open to negotiating big changes. My role as an HR and hiring manager includes compensation research, inclusion, and benefits planning — which means that knowing our salaries are fair compared to the market, that we prioritize gender equality, and that we’re up front about all of these factors is enormously important to me.</p><p><strong>Do: Be upfront about the interview process and expectations</strong></p><p>Although we no longer require an in-person interview, hiring at Olark is an involved process, and it can be a little intense at times. The last thing I want is for a candidate to be surprised by how long things are taking or what’s being asked of them, so I explain the process in the first interview, and give estimates for the time required of the candidate at each step as well as for our overall timeline for making a hire. That way, the candidate goes in clear-eyed and has a chance to let me know about any potential conflicts (upcoming vacations, etc.) — and they can bow out with no hard feelings if they’re uncomfortable with our timeline or process for any reason.</p><p><strong>Do: Talk about the challenges</strong></p><p>No job is 100% rainbows and sunshine. If it were easy, or you had it all figured out, you wouldn’t be hiring someone new to take it on. When candidates ask about the tough, ambiguous, or tedious parts of a role, or about the department’s or company’s general struggles and weaknesses, be completely honest. If they’re a good fit, they’ll see those challenges as opportunities.</p><p>For example, everyone at Olark periodically chips in on tasks outside their core areas of expertise. We’re very upfront about those “all hands on deck” moments in our interview process, and we learn a lot from candidates’ reactions. Someone who sees pinch-hitting as a downside of the job probably isn’t the best fit for us. On the other hand, many candidates are excited about learning and contributing in different areas, and those are the folks we want to move on to the next stage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*kVpTFtQYYBuNpdDNhHXoqA.png" /></figure><p><strong>Do: Take time to review applications thoroughly</strong></p><p>Olark receives hundreds of applications for every position we post. Apart from the fact that we’re awesome (yes, I’m biased), being remote significantly expands our applicant pool.</p><p>What happens with that stack of applications? Well, I read them. And I don’t just mean “I scan them quickly for keywords.” I spend the ten minutes it takes to digest each candidate’s information, and to think critically about whether they’re a potential fit. I also read and consider their answers to the application questions — open-ended questions related to the specific role and our core values are a key part of our application, and allow me to gauge a candidate’s interest, knowledge, and written communication abilities before deciding whether to move them to a phone screen.</p><p>For some roles, reading applications takes a full week of my time. But it’s worth it, because the most important qualities we’re looking for — creativity, empathy, ability to adapt and learn — can’t be captured in a six-word headline. Some of our top employees come from non-traditional backgrounds, and probably would have been dismissed in a traditional “filtering” process.</p><blockquote>The most important qualities we’re looking for — creativity, empathy, ability to adapt and learn — can’t be captured in a six-word headline.</blockquote><p>If you’re hiring for a very specific, static skill set, you might be able to get away with just scanning resumes. But very few small companies are in that position. If you want someone who can grow with your business and contribute in a variety of ways, you owe your candidates (and yourself) the time it takes to read every word.</p><p><strong>Do: Pay for any project-based or lengthy activity</strong></p><p>For most positions, we ask applicants to complete two lengthy activities (2–3 hours or more) into the interview process. We pay $100-$250 per activity, because we want candidates to know we respect and value their time. A homework assignment might eat into an evening or weekend that an applicant would otherwise have spent with family; a full-day work-along will probably require them to take a vacation day, find a babysitter, etc. It’s important to us that prospective employees know we don’t take those things lightly, and that if they do join our team, we’ll respect their lives and commitments outside of work.</p><p><strong>Don’t: Waste someone’s time</strong></p><p>Don’t string people along. If a candidate clearly isn’t a good fit, tell them right away so they can move on and pursue other opportunities. It’s no fun letting someone down, but it’s much, much easier if you do it quickly and cleanly, before they’ve invested too much time in your process.</p><p>Similarly, don’t disappear from the process. If you say you’re going to get back to a candidate within a certain period of time, do it. If it’s been more than two weeks since you’ve updated them, update them. Ghosting after a first date is bad — ghosting after a first interview is literally the worst, and sets an especially bad precedent in a remote setting, where everyone is highly reliant on consistent, predictable communication. We’re all busy, but even a one-line email is better than radio silence.</p><p><em>And finally…</em></p><p><strong>Do: Share your experiences</strong></p><p>We just covered a ton of ground — but really, these dos and don’ts only scratch the surface of what it takes to build a great team. If you have tips of insights that might benefit other small businesses (remote or otherwise), let us know! You can comment on this post or drop us a line on <a href="https://www.facebook.com/olarklivechat/">Facebook</a>, <a href="https://twitter.com/olark">Twitter</a>, or <a href="https://www.linkedin.com/company/olark">LinkedIn</a>. We’d love to learn more about what works for you.</p><p><em>Olark builds human-centered software that helps businesses listen, learn, and improve; learn more at </em><a href="https://www.olark.com/"><em>www.olark.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f55d61ec8849" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From 0 to 10: Starting a business by solving our own problems]]></title>
            <link>https://olark.medium.com/from-0-to-10-starting-a-business-by-solving-our-own-problems-bfc71c429f95?source=rss-f218a12fa80f------2</link>
            <guid isPermaLink="false">https://medium.com/p/bfc71c429f95</guid>
            <category><![CDATA[small-business]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[founder-stories]]></category>
            <dc:creator><![CDATA[Olark]]></dc:creator>
            <pubDate>Wed, 07 Aug 2019 17:06:30 GMT</pubDate>
            <atom:updated>2019-08-07T17:12:34.526Z</atom:updated>
            <content:encoded><![CDATA[<p><em>By Ben Congleton</em></p><p><em>This post is the second in our “From 0 to 10” anniversary series. </em><a href="https://medium.com/@OlarkLiveChat/from-0-to-10-how-we-built-an-unconventional-silicon-valley-startup-10f6694665b9"><em>You can read the series introduction here</em></a><em>.</em></p><p>As we celebrate Olark’s 10-year anniversary this month, I’ve found myself retelling our origin story more and more frequently. I live in the heart of Silicon Valley, where the dominant business narrative is one of fly-and-die startups, so any story about a bootstrapped company with 10 years of stable history attracts a bit of attention. People naturally want to know how we got started, and where the idea for a simple, user-friendly live chat app came from.</p><p>The answer to the second question is that Olark grew out of a problem I had in my own small business — which, as it turns out, is a pretty good place to look for ideas.</p><h3>Our story</h3><p>In the 1990s, I ran a web hosting company with a few friends. We were all high school students, and given that we were in class for most of the business day, customer service was a challenge; none of us had the bandwidth to answer phone calls. Most of our internal communication was via tools like AIM, ICQ, and IRC (the predecessors to Facebook Messenger, Slack, and Google Chat), so we started looking for a similar product that would allow us to chat with our customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*U5zIDXisbY49IoYo3YyLYQ.png" /><figcaption>Original AIM, ICQ, and IRC icons. Graphic design has come a long way since the ‘90s!</figcaption></figure><p>Live chat existed in the ’90s, but almost all of the available tools were aimed at (and priced for) much bigger companies. There was only one real option for small to medium businesses, which we used to great effect; in fact, our responsiveness helped us grow the business to an impressive — for high school students — $150K+ in annual revenue. But after a few years, that tool was acquired by an enterprise software company, and the price increased.</p><p>Fast forward to 2006. I was working on my PhD at the University of Michigan and kicking around ideas for products to build on the side. In one of my School of Information seminars, we’d talked about <a href="https://shoshanazuboff.com/">Shoshana Zuboff’</a>s work on disintermediation — the idea that the Internet will support a larger marketplace in which producers sell directly to buyers, without relying on middlemen. I found myself wondering how producers and buyers would communicate in such a market. What about live chat? Had anything changed in that market since the 1990s?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/280/1*Lt7bYbUIIrBfX80-MxCQwA.png" /><figcaption>Grad school! This is me on my 23rd birthday — a little less wisdom, and a little more hair…</figcaption></figure><p>As it turned out, the answer was no. Enterprise live chat solutions were alive and well, but despite the explosion of small and medium Internet-based businesses, no one had built a live chat product aimed at small teams.</p><p>I knew that if I founded another small company, I would want a chat product to be part of our daily operations. I couldn’t find an existing solution — which I saw as an opportunity to build one. That led to the first version of Olark, our acceptance into YCombinator, and the <a href="https://techcrunch.com/2009/08/19/olark-is-a-dead-simple-chat-widget-for-site-owners/">launch of our first paid product</a> in 2009. We used Olark to support Olark customers from day one, and our continuous dogfooding has helped us uncover more problems, create solutions, and build a version of live chat that’s specifically optimized (as well as priced) for small, nimble teams.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oWYxG5pR8AVHTYMCg6Mv_Q.png" /><figcaption>Throwback to 2009…the very first version of the Olark website.</figcaption></figure><h3>What we learned</h3><p>Many entrepreneurs are drawn to “big” external problems, and there’s good work to be done there, too. But if you’re itching to develop a new product, my advice is to start by reflecting on your own problems — regardless of how big or small they might seem — and taking time to think deeply about solutions. You’ll know exactly what success looks like, and you’ll work with greater empathy, creativity, and drive. In the best case, you’ll uncover an unsolved problem that many people are facing. At worst, you’ll make your own life and business better by finding or adapting an existing solution that works.</p><blockquote>Many entrepreneurs are drawn to “big” external problems, and there’s good work to be done there, too. But if you’re itching to develop a new product, my advice is to start by reflecting on your own problems — regardless of how big or small they might seem — and taking time to think deeply about solutions.</blockquote><p>In our case, it turned out that many small businesses had challenges communicating with their customers, and our simple solution became the foundation for a successful, sustainable business. But even if Olark had never developed into anything other than an internal tool, the process of creating the product would have helped us reflect, grow, and work a little more effectively. Working on your own problems will always move you forward.</p><p>Speaking of which — we’d love to hear about the problems you’re facing in your business. Are you dealing with a challenge that might inspire your team (or someone else’s) to innovate and create something new? If you’ve recently overcome a problem, could other small businesses benefit from your solution? Leave a comment on this post, or reach out on Twitter (<a href="https://twitter.com/jaminben">@jaminben</a> and <a href="https://twitter.com/mjpizz">@mjpizz</a>) or LinkedIn (<a href="https://www.linkedin.com/in/bencongleton/">Ben</a> and <a href="https://www.linkedin.com/in/mjpizz/">Matt</a>), to share your ideas and start a conversation.</p><p><em>Stay tuned — in our next post, we’ll talk about sharing toiletries, creating company values, and other essential steps to building a thriving small business culture.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfc71c429f95" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>