<?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 Josh Botterman on Medium]]></title>
        <description><![CDATA[Stories by Josh Botterman on Medium]]></description>
        <link>https://medium.com/@joshbotterman?source=rss-1d6add3d2303------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*dQqfp-0H0jSY3TdW.</url>
            <title>Stories by Josh Botterman on Medium</title>
            <link>https://medium.com/@joshbotterman?source=rss-1d6add3d2303------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 03:23:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@joshbotterman/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[Building a One-Stop-Shop for IT Support Technicians]]></title>
            <link>https://medium.com/@joshbotterman/building-a-one-stop-shop-for-it-support-technicians-885f496550fc?source=rss-1d6add3d2303------2</link>
            <guid isPermaLink="false">https://medium.com/p/885f496550fc</guid>
            <category><![CDATA[it]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[dashboard]]></category>
            <dc:creator><![CDATA[Josh Botterman]]></dc:creator>
            <pubDate>Fri, 30 Aug 2019 01:37:05 GMT</pubDate>
            <atom:updated>2019-08-30T01:37:05.832Z</atom:updated>
            <content:encoded><![CDATA[<h3>Building a One-Stop Shop for IT Support Technicians</h3><h4>…and making it pretty</h4><p>Part of the brilliance (and challenge) of working at a rapidly scaling startup like Cruise is watching old problems fade away and new ones appear without much notice. More employees mean more brainpower — and labor hours — to knock out those projects that were once tabled for “when we’re a bigger company”.</p><p>Often though, auxiliary teams like IT, Facilities, etc. struggle to keep up with the crazy growth. All of a sudden the <em>“user:technician</em> <em>ratio”</em> explodes and support queues spiral out of control.</p><p>As a designer with hands-on IT experience, I know this problem very well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z5HOsC71pAfUPqNe7N7cnQ.png" /></figure><h3>The Ask</h3><p>After careful study of our workflows and queues we found that by-the-numbers Cruise IT (we) should have been performing at a higher clip. However, we were not accurately tracking the amount of “walk-up” traffic to our physical help desks. In fact, we were not recording any of these face-to-face interactions. This in-person help is key to the success of our customers and our reputation within the company. And yet, its omission from our recording practices was distorting our assessment of performance. In other words, a lack of data was causing a huge oversight in our key metrics and results. By building out Service-Level Agreements (SLAs) and other benchmarks based exclusively on web ingest we were significantly misrepresenting our impact and shortchanging our effort.</p><p>So, the path to alleviating the pressure of never-ending support queues and tough-to-meet SLAs became clear: <strong>find a way to easily and accurately document walk-up traffic at IT help desks.</strong></p><p>To best solve our documentation problem we had to gain a better understanding of why walk-up traffic was passing us by. Luckily, both my partner in this project — my brother and full-stack developer Zach — and I had plenty of hands-on research into the inner workings of an IT help desk. The answer was simple: the necessary process to file a ticket on behalf of a customer was just flat out too clunky. This was especially true given the speed at which we were working through a customer’s request and moving on to the next in line.</p><p>To better illustrate this, here’s an example of a typical help desk interaction:</p><ol><li><em>Customer — 1 of 6 in line — approaches the help desk requesting a pair of headphones.</em></li><li><em>The Support Specialist walks to the inventory room where she grabs the headphones. She then asks for the customer’s name.</em></li><li><em>The Support Specialist, on her laptop, navigates to our asset management platform where she looks up the customer to assign the headphones and mark them as deployed.</em></li><li><em>The customer receives the headphones and walks away, happy with their help desk experience.</em></li><li><em>Customer 2 of 6 steps up and the process starts all over again.</em></li></ol><p>Now, to the untrained eye this seems like a complete, successful service interaction. And<em> — </em>to be fair<em> — </em>in almost every way it is. Below the surface though, lies the crux of our issue. No data! Without a ticket to live on, there’s nothing to say customers were being helped.</p><p>Of course it’s easy to say “why doesn’t the Support Specialist make a ticket quickly before moving on?”. A valid question, no doubt. But if we were to take a look at the same interaction, this time with the Support Specialist doing everything by the book<em> — </em>including creating a ticket<em> — </em>it wouldn’t be the same breezy experience for the customer (or specialist), thus holding up the line. Here is that version:</p><ol><li><em>Customer — 1 of 6 in line — approaches the help desk requesting a pair of headphones.</em></li><li><em>The Support Specialist walks to the inventory room where she grabs the headphones. She then asks for the customer’s name.</em></li><li><em>The Support Specialist, on her laptop now, opens a new window and authenticates for access to our HR/People platform. She types the customer’s name into the HR/People platform to confirm their name’s spelling and validate the customer’s status as a full-time employee.</em></li><li><em>The Support Specialist then navigates to our asset management platform where she looks up the customer to assign the headphones and mark them as deployed.</em></li><li><em>The Support Specialist next begins the ticket creation process. She opens yet another tab or window to access our project management and ticket recording platform. If she is already signed in she will choose to “create” a new issue. At this point she is brought to a form with several required fields including “summary”, “reporter”, etc. She fills out these fields as quickly as possible and submits the ticket.</em></li><li><em>The Support Specialist then navigates to the ticket queue where she will find her recent submission. She opens the ticket, assigns it to herself, comments something to the effect of “headphones assigned to user”, and marks the ticket “resolved”.</em></li><li><em>The customer receives the headphones and walks away, hopefully happy with their help desk experience.</em></li><li><em>Customer 2 of 6 steps up and the process starts all over again.</em></li></ol><p>As you can see, the process isn’t so simple when you follow all the rules. Besides the obvious increase in time-to-resolution, the constant opening, closing, navigating, and authenticating for our many software platforms can be an incredibly frustrating experience. By the seventh time, signing in to view a customer’s ticket history can be rage-inducing. Taking a closer look at common interactions like the one I laid out not only validates the core “ask” of the product, but actually informs the way to go about solving the problem. Thus, in order to (1)<strong> easily and accurately document walk-up traffic </strong>we needed to a build a tool that would (2) <strong>aggregate the many resources needed to deliver exceptional service</strong>.</p><h3>The Process</h3><p>With a clear understanding of what our tool needed to accomplish, Zach and I set out to create our aptly named <em>Pitstop</em>. Seeing as Zach had already spun up a basic prototype, we had a foundation to build upon. Initially, the layout was a bit funky so my first contribution was laying a blueprint, of sorts, for the content to come. For our first iteration, we knew we needed to build in the following components:</p><ul><li><em>Ticket Submission Form</em></li><li><em>Search Bar</em></li><li><em>User Information Side Bar</em></li><li><em>Open Users Side Bar</em></li><li><em>Existing Tickets and Assets Carousels</em></li><li><em>Technician Sign In/Avatar</em></li></ul><p>Drawing inspiration from existing productivity software like GSuite, Monday, and Slack, these elements started to take their places. We knew creating a ticket was our top priority, and therefore ticket submission took center stage in the interface. Everything else came second and subsequently filled out the periphery.</p><p>Seen below, our <em>Alpha</em> version accomplishes much of what we set out to do:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yklmBLagovpHSoTwbHh1AQ.png" /><figcaption>Alpha Version, User Page</figcaption></figure><p>From here on out, most of my work came in the form of stylistic changes. For instance, I toned down the existing tickets’ color, fine tuned the search bar height, and altered the open user bar’s appearance. An exception to aesthetic decisions though, was the inclusion of the user’s Okta groups to the user information side bar. Okta, Cruise’s SSO of choice, provides us a way to manage users’ access to a host of different protocols and applications. Often times an IT service request requires adding, removing, or otherwise altering a user’s Okta access. Therefore, adding existing groups in a highly legible format contributes greatly to streamlining the Support Specialist’s job.</p><p>In a later version (seen below) you can see the Okta group update — among others:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6PAzoFeQjDycq93J6m-MBQ.png" /></figure><h3>Shipping It</h3><p>With all of our initial “must-haves” being met, Zach and I were feeling confident about getting <em>Pitstop</em> out there. While he worked on some backend integrations I shored up some design details and provided mockups for edge cases — like a “no users found” page.</p><p>Through initial demos we realized that the existing ticket form, while appropriately prominent, was encroaching on other important page elements. Though it made sense for the form to remain front and center, there was no reason to have the ticket “description” box expanded at all times. Luckily, Zach was able to make my suggested changes, and we were left with an expandable submission field. This allows the Support Specialist to immediately see existing tickets and assets without having to scroll down.</p><p>Another small addition was in the form of some Pitstop-specific branding. Seeing as though my background is in brand design, I naturally looked to give our platform a visual identity. The result, a simple checkered flag — recognizable in small formats like a browser tab’s favicon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EbXhbiY_hZQV7dPjYSKqfw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WUgyx-LNi2cg1mDV30Yekw.png" /><figcaption>Non-Expanded and Expanded “Description” Boxes</figcaption></figure><p>With Pitstop’s <em>Beta </em>all<em> </em>but completed, and my final responsibility being the design of what was essentially an error page, I figured it couldn’t hurt to add a splash of our team’s personality. After all, this <em>is </em>a tool built for the IT team, by the IT team. Directly in front of my desk stood a white board filled with various sketches of cartoon characters — none of which carried the esteem of the very popular <em>business fish</em>. Drawn by our Lead, the business fish and his biz-casual attire was often a topic of conversation. Thus, it was a no-brainer to have him deliver the message “no users open”. Of course, once I had drawn the fish in vector graphics, as opposed to expo marker, I couldn’t help but switch up his outfits for a bit of flavor. Now, every time you reach the “no users found” page you’re greeted by a randomly-chosen and ridiculously-dressed fish. A crucial detail if you ask me.</p><p>Here they are in all their glory:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tBxPEsMgZBHFFvWwLHUsvA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*72vHGHGPAS6LIt0CWs6gyw.png" /><figcaption>‘Business Fish’ et al.</figcaption></figure><h3>Wrap-Up</h3><p>Now that Pitstop has been sent off to the Site Reliability and Integration Engineers to bring it into the Cruise ecosystem of internal tools, my job is (temporarily) finished. With much to be proud of — and even more learned — I’ve been able to reflect on the project. First, and most simply, Pitstop gave me the chance to re-familiarize myself with Sketch. Most of my recent work had been in visual design, so jumping back in to product design and its requisite tools was undoubtedly beneficial.</p><p>Second, Pitstop offered me the opportunity to get hands-on in designing a <em>real</em> product with <em>real </em>parameters. A big challenge in creating one’s own design projects out of thin air is that the limitations and deadlines are never quite as firm as when work is asked of you. Charles Eames once defined design as “…<em>a plan for arranging elements to accomplish a particular purpose</em>”. I found the Pitstop project to provide me with a very clear, particular purpose.</p><p>Last, Pitstop was once again a way for me to use my particular skill set and experience to engage with an otherwise unrelated team within an organization. It is empowering to know that Pitstop will have lasting effects on the productivity of my peers at Cruise.</p><p><em>Special thanks to Zach for building the thing and the Cruise IT team for giving us the platform to build…well, this platform.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=885f496550fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design a Brand, Build a Community]]></title>
            <link>https://medium.com/@joshbotterman/design-a-brand-build-a-community-7a7aeba4d18b?source=rss-1d6add3d2303------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a7aeba4d18b</guid>
            <category><![CDATA[design-for-diversity]]></category>
            <category><![CDATA[blacklivesmatter]]></category>
            <category><![CDATA[brand-design]]></category>
            <category><![CDATA[cruise-automation]]></category>
            <dc:creator><![CDATA[Josh Botterman]]></dc:creator>
            <pubDate>Thu, 09 May 2019 01:05:34 GMT</pubDate>
            <atom:updated>2019-08-07T22:08:18.107Z</atom:updated>
            <content:encoded><![CDATA[<h4>How a logo can bring a diverse group — and company — together.</h4><h3><strong>Inspiration</strong></h3><blockquote>1. COAD should feel like a second “home” for its members and allies <br>2. COAD should honor the diversity of experience of its members</blockquote><p><em>Cruisers of the African Diaspora </em>is an employee resource group wherein members and allies celebrate the vibrance of their heritage. When one of COAD’s leaders approached me to design their logo, I was beyond honored. What followed were a series of focused conversations between members of COAD and me.</p><p>For the first time, I had the privilege to design for a community other than my own. Further, this group’s sole purpose is to support black and brown professionals in <em>Tech</em> — an overwhelmingly white and Asian male dominated field. To say the least, I wanted to do my coworkers justice and bring their vision to life.</p><p>My partner-in-crime and liaison Sadé explained that, above all else, COAD should feel like a second “home”, while honoring the diversity of experience of its members. We agreed that <em>pattern-work</em> would capture the essence of the various cultures associated with the African Diaspora, and I began to do my research. Fortunately, I stumbled across Loïs Mailou Jones’ <em>Street Vendors </em>and was immediately inspired.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3h1ngnYlZCaofGG-OGZOnw.jpeg" /><figcaption>“Street Vendors”, Loïs Mailou Jones, 1978</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zPsgFjgK1PxTFnPeWMwS4w.png" /><figcaption>Gathering inspiration from patterns and African Diasporic art</figcaption></figure><h3>Product</h3><p>After countless design reviews and iterations the final wordmark, symbol “C”, and Cruise car let color and pattern rise above all. Stripping away, piece by piece, I was eventually left with a single pattern taken loosely from Jones’ painting. The pattern is directional and architectural, conveying movement and power (both qualities that Sadé and the rest of the team emphasized). Within the “O”, the outline of continental Africa serves as constant reminder of COAD’s shared history.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LXqPNTIGgl5gRwM7qoQQiw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YSuJFAYnd8DW6HV5faYE2g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*gsQqVeCnL4miYTl0sbxBFg@2x.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2B-V42LUXK7tI_w_70jhPg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OwASnix_xGiZrg39cSWbmQ.png" /></figure><h3>Aftermath</h3><p>Once printed, COAD “swag” has spread quickly across Cruise offices.</p><p>Shortly after the brand unveiling, COAD organized an incredible Black History Month program celebrating “Hidden Figures”. Speakers including former NASA Administrator Major General Charles Bolden left us with unforgettable stories and inspiration. Major General Bolden and I are shown holding the BHM poster I designed.</p><p>The word quickly got out and I have since been asked by LGBTQruise, Families@Cruise, and Vets@Cruise for help developing the visual identities of their communities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ewYkxKg4w6glCznQ4c1yKg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YZ7BKKSRZUaCG-HZxLocpQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7IT6NjXAk_zviGmEhqEV5A.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a7aeba4d18b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>