As of today, my time at Automattic has come to a close, so I picked out my favorite photos from trips I took between 2010 and 2016.
My father’s a guy who builds rockets. And I don’t mean that he builds the model rockets you see at the park that get blown onto neighbor’s roofs by a slight wind, I mean that he builds the giant Atlas V rockets that launch actual shit into actual outer space.
So when I was kid, there were key points I can remember when we’d all head down to the pizza place closest to my dad’s plant to watch his and his coworkers’ work launch satellites into space. It’s a unique experience to witness your father witnessing his own work do something so mind blowing.
So while my father builds the rockets that launch satellites into space, I manage to do some (much less complicated, and much less tension-inducing) building and launching of my own: I work for the company that builds WordPress.com, the platform I’m blogging on right now, and we just launched some pretty cool stuff that we’ve been working on for quite a while.
So, is your website a satellite being shot into orbit? Not quite, but it wouldn’t be far off to think of WordPress.com as an Atlas V rocket to get your site on the web, anyway. 🙂
In September 2005, I was 26 years old. A decade ago.
I called Scott Upton on the phone and asked if he was happy at his job and if they were hiring. A week later I’d had my interviews, handed in my resignation for a second time at Spiremedia and began a new chapter in my career: I was about to spend 4 years at a company in Boulder called Wall Street on Demand.
Wall Street on Demand specialized in taking hundreds of live-streaming stock market data feeds and turning them into beautiful interfaces for making financial decisions. We designed and built investment research interfaces for everyone from the E-Trade home investor managing their retirement account to the Merrill Lynch institutional investor trading hundreds of millions of dollars at a time.
These were not small local clients whose deadlines could slip when the process didn’t go according to plan, with business plans I’d seen a hundred times before. These were clients like investment banks and cable TV news networks who demanded financial visualization expertise from our staff on a daily basis.
If I put a percentage instead of a dollar amount in a table cell showing Earnings Per Share, it would be called out long before my work made it to the client’s inbox. The amount of training to be done with new hires was incredibly high before we were allowed to run our own projects without a CD at the helm, something as a Senior Designer I was expected to do fairly soon.
Competition is not the best way to get ahead
We had posters on the walls extolling the virtues of collaboration. The design team at Wall Street was not competitive: as a team of teams, we had a lot of design leadership and structure facilitating our collaboration at every level. The structure looked like this:
Before my tenure was up, we’d add a couple new titles, Associate Creative Director and Junior Designer. It was a unique system that had the added benefit of Chris, the company Creative Director, essentially working at the C-level with James, the CEO and Catherine, the COO: all three of them were related.
This was more or less a design-focused, family-run business with Goldman Sachs as the Board of Directors.
Chris had domain expertise in interaction design and financial design. He’d been educated at Johns Hopkins for creative writing and this education gave him a passion for concise, effective communication. He’d later go on to do post-grad work at UCLA for data visualization and he was a god-damned whirlwind to work with. It was exhausting to try and keep up.
This was by far the most design-led organization of which I’ve ever been a part. There was a truly talented design brain with actual power in the executive suite who demanded at the highest level that our own organization be true to a specific design philosophy.
There was a lot to learn. There was new, insane shit showing up in front of my eyes every day. Page designs containing ideas more complicated than I had ever imagined myself designing were casually discussed over cubicle walls, all around me. It felt like being in college again – except everyone was obsessed with the stock market for some reason.
I’d had a similar feeling before in my life: junior high school with my friends, coding Pascal and BASIC. I’d had it at Spire when I was 20 years old, coding Flash animations for websites whose domain names cost 10 times my salary. It was the feeling of being a little fish in a big pond, and it was good for me. “I will never know everything there is to know here” was something I thought to myself on a daily basis. I engaged in learning without fear, and applied that knowledge immediately.
The design staff carved out many physically-communal design spaces. We started out having our design meetings in a room labeled Aspen, named after the trees that swayed right outside its window. When we leased more space across the street, Chris oversaw the entire design and construction of the new office, building it specifically for designers and developers to collaborate.
We had two rooms separated by a substantial but removable accordion wall made entirely out of whiteboard. These rooms were named after Charles and Ray Eames and were reconfigurable as we needed.
We’d gather every Friday morning, bright and early. Coffee in hand, we’d file into whichever space we were using at the time and we would nerd out as designers together. We’d discuss three things:
We all sat near each other in the office. We went on design- and art-oriented outings together, and we created a culture that really worked to get beautifully-finished work out the door.
The funny thing about all of this collaboration was that I resisted it at first. We had a global Creative Director running the entire Design & Development division and I had Kent, a Creative Director, directly managing my work. I’d never had this many bosses before. During the first few months, I was a little unhappy about how much direct contact I was having with Kent. It was the first time in a while where I was working directly beneath someone who checked in on my progress multiple times a day. He’d show up right behind me at my desk and pull up a chair:
Whatcha up to, Kev?
was his usual phrasing.
Fuck you, Kent.
was the usual response in my head. I didn’t say it. I’d stop reading the NY Times article that was probably on my screen, tab back over to Photoshop, and show him my work.
He’s ask me questions that would make me frustrated, because of course I wasn’t done with it yet. He’d ask me something I hadn’t gotten to or he’d challenge me on basic things like color usage:
Why’d you use yellow here? It’s not in the palette.
I’m designing the warning panel you assigned me. I chose a yellow with similar attributes to the family of colors already on the page, so it works to add it.
and he’d go
to which I would again in my head reply
Fuck you, Kent.
This didn’t last long, and I’m giving Kent a hard time about it. We got past it and I moved on to learn an incredible amount of data visualization and general financial knowledge directly from him.
The moment of truth was when work started getting really hard. I was driving home to Denver every night in a daze, feeling like I wasn’t keeping up. Kent’s own design work was taking up more and more of his time, and yet I was not owning much about my designs or my clients. Even though he didn’t change my work much any more, it all seemed to hinge on his opinion, and so I felt powerless. The day he shocked me out of my daze was when he sent me a heart-pounding email. It said simply:
I need to you to engage now.
I had no idea what this meant. I went to Chris and asked him what on earth I was supposed to do with this. Chris told me:
If you ask me, it sounds like he’s saying it’s time for you to jump in. If you don’t know what that means, then it’s up to you to decide.”
I was afraid at first. I was the only designer on a project for the very first time here, and I knew I didn’t know very much yet. All of the experienced designers were working on the cool stuff like stock charts for BusinessWeek and CNN. I was designing UIs for people to get email alerts. I wanted the big-name work, but was terrified when I was given something serious to handle on my own.
I decided it was time to start using my design skills to actually get design accomplished. I started drawing diagrams of how I understood the system I was designing to work. I took these diagrams to the client and then to my company’s developers and we iterated on them until they made sense and everyone agreed. Then I started wireframing in HTML. We had clickable prototypes with no CSS before we had a design language, which followed on quickly. I scheduled meetings with people downstairs I’d never met but with whom I needed to create relationships because my client was requesting a brand-new way of handling incoming data feeds, which needed to be written from scratch. I worked closely with the client to determine their systemic and visual requirements. At the very end, some crucial final understanding of the client’s needs came from Kent’s involvement in days-long meetings.
By the time it launched, I’d written the final production HTML and had handed it to our developers who plugged in the data calls and re-arranged things to work with our nascent pre-ajax technology.
In the end, what got us ahead and to a good place was that the whole team came together and collaborated, not that I could do the design work perfectly in a silo on my own, which was what I thought my role as a designer had been up to this point.
At the end of that project I had a sense of pride I’d never felt before. Many teams worked together, and I learned to lean on my team lead at crucial moments, pushing through a UI I knew was up to speed with what the rest of the design staff was producing.
I just described an intense project, and it was the first of many to come. Over the next 4 years, I’d learn that some resistance from the first-floor engineering teams was something of a common theme. As we grew and grew quicker and quicker, more inexperienced project managers were being hired to manage more and more work.
By 2009, people like me who’d been at the company a while and had shown leadership promise were moved into new positions. On the design team, this new position was called Associate Creative Director. It was our job to essentially work closely with our CD and start adapting their responsibilities into our workflow, namely managing the relationship alongside the Account Director and selling the client on new work at every turn.
This was new! And challenging! And I didn’t take much to it.
What I could do: execute high-quality UI and UX work on a weekly basis, in a novel and compelling way, driving the less-experienced designers on my team to do the same. As Associate Creative Director I really tried to know everything there was to know, just like it looked like the other CDs were doing when I started, and I began to lust after the wrong thing: prestige.
I started forgetting to collaborate. I’d react strongly in internal meetings where I felt developers didn’t care as much as I did about turning out a great product. I’d push clients toward what I thought the correct solution was, without really listening to what they were trying to accomplish. I’d bully other designers into trying to learn to code, despite their protestations that they just never really understood it. “Every designer should learn to code!” I’d say, dismissing their views entirely.
And so I burned myself the hell out. I burned everyone around me out on working with me. It’s true that when I left this job, my clients called emergency meetings in Boulder to plan the roadmap for how they were going to continue working with Wall Street in my absence, but I was fending off internal talk from above that I wasn’t quite working out in this position. What I needed though was something I couldn’t find at this company anymore: I needed to be a little fish again.
I needed to learn to collaborate with other designers again, without the ego attached as I rose the ranks and earned respect. I didn’t know it yet, but what I needed was to go work at Automattic, something I’d have the chance to do sooner than I’d know.
As a 5-year employee of Automattic, I have the option of taking a 2-3 month sabbatical. I opted for the shorter duration as I felt it was a good amount of time to get some artwork created and some studying done on being a stronger leader in my design community, so that I could come back to work strong. I felt like a 3-month break would have been too much time to get lazy and bored, making for a bad re-entry to work.
Before my break would start though, I’d have an inspiring last bit of work to do in Denmark with the Automattic Design Team (the half that wanted to travel to Copenhagen, that is. The other half went to Atlanta).
During a jetlag-fueled haze, I quickly wrapped up the badges and schedule designs for WordCamp Denver. My first official week off included spending some good time with my kids, the longest time I’ve had with them since their mom and I separated in mid-2014. I also spent time that week designing the slides for my WordCamp Denver talk “Full-Stack Web Design: A Case Study in Interactive Prototyping”
Between Copenhagen and WordCamp Denver, my girlfriend Beth and I got to see the premiere of a movie that we’d been extras in over a year ago called Something Along the Lines of Dating:
Since I’ve now got an amazing apartment, I finally took the time to decorate it how I like:
One of the main reasons for this sabbatical was art. I spent some time getting back in touch with my art school education by doing some drawing and painting: skills I don’t use in my every-day professional work, done with tools I’ve allowed myself to become unfamiliar with. Time to change all that.
I’d long had a blog series in draft form saved away that I wanted to flesh out and spend more time getting right before I published. This series turned into the Why I’m a Designer series on this blog that I started posting early into my break. I have 4 more parts planned, but I have some studying to do first.
Part 2 of this series is titled View Source and it’s a concept I’ve decided to flesh out even further by writing an Almost Famous-type film loosely-based on a fictionalized account of my first real job in the early days of the web. I was inspired by attending the premiere of the film I’d briefly appeared in; it seemed possible for me to actually make something worth watching. The rough writing I’ve gotten done is a baby step in that direction. I’ve been watching films by my favorite directors trying to study their work.
Since writing isn’t a strong suit of mine, I decided to mostly tackle the View Source film through its music. I first created a Spotify playlist of the music we used to listen to in the office at the time, music that lived inside of a 300-disc CD changer that also powered what people calling the office heard when they were on hold. I augmented this list with music I was personally listening to a lot at my first job.
The second part of this approach was to record an original motion picture soundtrack influenced by music made in the 1998 – 2001 range.
I also wrote these songs I’m not sure what else to do with:
I was very glad to spend some extended time with my kiddos this summer.
I got to see my friends and Denver’s Best Cover/Tribute act (according to voters in The Westword) The Gin Doctors a couple of times this summer, which is always an incredible time:
I found reasons to use these images:
I got to go to a couple nights of The Denver Post’s UMS event held on South Broadway. Highlight of the event for me was an epic performance by Denver’s own Slim Cessna’s Auto Club:
I got to go a wedding in Vail:
In general, there’s nowhere else in the world I’d rather spend two months re-energizing and getting back to my creative roots than Denver.
Then something funny happened that we weren’t expecting, but sort of hoping for: the web became a tool everyone used, all the time, for a ton of reasons.
New users were arriving online every day, and new services were popping up in droves to give them fun stuff to do there. Years after Wall Street left the “dot-coms” to die in the gutter, the former employees of these companies built new tools, with new ideas about what a web interface could accomplish.
Web users adapted and started to actually love the products they used online. Flickr, Twitter, Tumblr, Del.icio.us: we all have memories of what was new about these things when they first appeared that delighted us.
The web was a super-fun place to be, both as a user and designer.
I spent the intervening years doing the following:
I can honestly say that during those 9-10 years, my work was used by millions of people, and that by 2010 my work reached that many people daily. I learned a lot during this time about how people use web applications, how they share content on the web, and how they talk to one another with the tools we build. I learned what my medium was being used for (fun fact: in 2002 I owned the domain “automaticmedium.com”) above and beyond what I was personally using it for. And all this time, I blogged.
I used a system built in PHP3 my friend Tai and I paid $500 for and then I ported that blog to a custom system I wrote in PHP 4 which I then wrote a custom importer for in 2007 that pulled it all into WordPress. Blogging was and is important to how I work.
While designing and building the tools my clients asked me for, I was simultaneously either plugging away at a new CSS idea on my blog, or trying out a new language to build a web app. My craft and I grew up at the same time and I tried to stay involved in it above and beyond my client work for two simple reasons:
These two concepts seem diametrically opposed: Ego and Empathy. I contend that to design a web application that people want to use on a daily basis you need both the ego to say:
“I can make something people will want to use that’s better than what exists”
and the empathy to listen to what your users actually say when you launch it. Additionally, your empathy for what you’d want on the screen you’re designing goes a long way toward making something your users may want to use.
How do you build this empathy? One of the ways besides maintaining a web app by yourself is to be a die-hard trier-and-user of any and all web apps. Really use them for really real things. See what making boards on Pinterest is all about. Follow art blogs on Tumblr and check it every day. Try Snapchat and get confused and close the app forever. Stuff like that.
You can start to understand what else the rest of the world is doing with their digital devices on a daily basis; you can see where your app fits into your users’ lives, not just how your users’ lives fit into your engagement cycle.
Empathize with what your users do on a daily basis with your tool by doing the same things with it and by doing the other things they do on a daily basis on the web, too. Pay fucking attention to what works and what doesn’t and why. You can start to synthesize this information with the designer’s ego telling you that you actually can produce a better product. What can result is remarkable: an app that people love using.
That’s always been my goal for my work on the web: to make something that people love having in their lives, something that feels like humans made it for other humans. They’ll come back over and over and give you their money for things you’re building that they want to use. You won’t have to beg for money from people who want to pay you for what you make.
Up next, part 5: Designer-Driven Design
Boysetsfire, After the Eulogy:
No Justice, No Peace.
Written, signed off
In the obituary: “What happened to us?”
Where’s your anger?
Where’s your fucking rage?
Watered down, senses lost.
Denial and self-gratified.
A tradition passed down to our blood-stained hands.
Give in, give up.
Give in, give up.
Contented to strive for new worthless slogans.
We miss our potential for action and substance.
Contended to lie in our boring vomit,
Suggesting arrangements, while others are dying.
Stand up. Fight back.
Stand up. Fight back.
How many starving millions have to die on our front doorsteps?
How many dying millions have to crawl to our front doorsteps?
Written, signed off in the obituary: “What happened to us?”
Where’s your anger? Where’s your fucking rage? Watered down senses lost.
Where’s your anger?
Where’s your fucking rage?
Content and corrupted,
Contrite and disgusting.
Dig a hole,
It’s all over.
Forget the words and good intentions,
Unless we rise.
Unless we rise.
Tear it down.
Last time, I mentioned that we had 2-3 designers simultaneously pitching ideas to clients. What I omitted then but would like to clarify now is that each designer determined for themselves absolutely everything they pitched:
What this meant was that often a client would see different versions of all of the above in the same meeting. They couldn’t focus purely on the competing designs’ visual directions because they’d also be picking a navigation structure and maybe even a logo at the same time.
This was a pretty terrible process. Factor in that Project Managers also didn’t exist and unsurprisingly lots of confusion resulted all around. Designers would pitch competing and usually slightly misinterpreted ideas the client floated in earlier discussions. We’d catch a glimpse of the other designer’s work and decide to incorporate some of their concepts, creating a miasma of ideas presented all at once, similarly sourced but slightly tweaked.
Then Jen showed up.
The subject of the all-employee email read
“Has anyone seen the office cell phone?”
These were incredibly rare devices and when our new office manager Jen Mylo (née Wells) needed to find it, there was something about her wording that immediately made me envision our plastic brick of a cell phone sitting on a bar stool, smoking a cigarette, talking shit about the employees that lugged it around the city. It cracked me up.
I immediately replied-all and said “I saw it a bar last night; it doesn’t want to see you.” My intention was to be funny and set a new employee at ease, that we had fun at this company. What actually happened was that she thought I hated her, which I learned a few days later when we were both part of a small group tasked with picking out a new office pinball machine.
I think I was the only one with a car at the time so I offered to drive. It was on this formative drive to Lakewood when I learned:
I’m incredibly lucky that we cleared up the misunderstanding that day, chose a sweet new pinball machine for the office, and made friends for life (so far).
When she spoke to Spiremedia co-workers about her life and work experiences, she was quick to mention her time on a dude ranch in Arizona, as an activist for Greenpeace, as the supervisor of a food co-op and many, many others. What she’d purposely be quiet about, and left off her resume entirely, was her time working on the web as an Information Architect. She was at the moment living and working in Denver along with her boyfriend, and wasn’t sure if she was staying long, so doing serious web work here wasn’t really on her list of priorities. “I really don’t want them to know I know how to do this” she’d quietly mention.
Of course “they” did find out about this unexpected IA on staff and quickly put her to work on our clients. By this time we had a team of 8-10 designers pitching sometimes totally off-the-wall ideas to clients and generally running the asylum. There was one incident where I went on vacation and left another designer in charge of my client work, only to return to a totally functionally-altered concept. Jen changed all that.
With the addition of Jen to our design team (as well as three experienced project managers: a lot changed for us at once), the process started to resemble something sane:
Clients no longer had competing, complete design philosophies to pick from all at once: each visual design was now proposed with the same labels, the same content, and the same architecture as the others in the meeting, and it had all been already determined. By working with Jen first, client expectations were set for what to get from the visual design staff and our expectations were set for what the client actually needed.
She enabled success on both ends of the spectrum by advocating for the users to the client early in the process, and then she’d pivot and advocate for the client and users to the designers when we came in later.
I now had two mentors helping me establish two keystones of my design philosophy:
I’ve plotted just about my entire career path between these two ideological pillars of how to build for the web. I’ll explain in Part 4 what I’ve done in the last 15 years with this foundation.
As I stood in the cramped first-floor hall of the 300 building at the Art Institute of Colorado, my heavy bag of supplies dug painfully into my shoulder. I was with a friend and we were looking for jobs on the board, a task I undertook when I found myself in each of the three buildings we had on campus in Capitol Hill for the first time that week. As soon as we walked up, one posting in particular jumped out at me and I forgot all about the huge bag on my shoulder. It said in stark Franklin Gothic Condensed type:
SPIREMEDIA IS HIRING A RECEPTIONIST
which I’m sure doesn’t sound to you like that big of a deal, but to me it was like that paper was etched in gold. I’d been doing web design hourly for a small shop owned by a man who – in a daze of inspired light and beauty – named his company The Internet Design Firm. During my first week at this job I AltaVista’d (we didn’t Google back then) “Denver web design companies” to see what was happening in town, and to find work that could inspire me in times of need.
Spiremedia was an agency I found during this search whose portfolio suddenly redefined for me what a web site could look like, what the web could be. I had already spent a lot of time on their site, poring over the portfolio looking at the decisions the designers made on each piece, trying to determine what I could learn from them.
“What about this work is applicable to my own? What can I discard? What can I change about what I take, to make it my own, my clients’ own? How did they code that?”
It wasn’t just their client work, either: their own site was an excellent example of the thinking that went into everything they designed. I never dreamed I’d actually end up working there. I was a student who had done a total of 10 months of contract work in the industry, not one of the professionals these people clearly were hiring. I’d click “view source” in my browser, copy out some of their clever HTML code, and learn from their ideas.
And so but here was this flyer stapled to the wall, telling me they were hiring a receptionist. The privilege of my education leapfrogged me past wanting to apply for the job for which they were actually hiring, so my email’s subject line said “I don’t want to be your receptionist” and the body included a link to my portfolio telling them I’d admired their work for a while, and that I wasn’t a very good receptionist but I was wondering if they were hiring designers. I couldn’t have been happier when the reply came that they wanted an interview, but I had no idea what to expect.
What I found when I showed up was incredibly disorienting: the building was out past Lower Downtown (the newly-named LoDo), on a street no one I knew had heard of. When I pulled my car into the dirt expanse in front of the building, I suddenly recognized it: this was the terrifying part of town where we parked our cars back in high school to go to St. Mark’s Coffee House. The concrete and abandoned 5-floor building at the edge of the dirt lot wasn’t so intimidating during the day, it seemed. What on earth was I going to find inside the warehouse across the street?
I couldn’t have guessed that it was going to be about 5,000 square feet of exactly what I’d been looking for since junior high, but this was not an office that my work experience had prepared me for. There was no sterile drywall bound by drop-ceilings and cheap carpet. There were no medical-grade waiting room chairs or neckties. No one was freaking out about the dogs wandering around and no one appeared to be over 30. Everyone wanted to be there.
A video created by Scott Upton with an original iBook and external video camera
Thick, wooden warehouse columns broke up the space into distinct areas. Existing long before many floors of offices had been built around them, they stood like stoic Redwoods throughout the office, ancient and real. I marveled at how many people must have done how many kinds of work in this building near these columns, and noticed this group of people covered them and the exposed brick in artwork and ethernet cables. The waiting area for clients was made up of a duo of (also wooden) old-timey school chairs which faced pinball and Asteroids machines. The music was loud and the person interviewing me had about 1,000 toys on his desk in the only private office I could see.
I was home again.
Spiremedia often worked in a traditional design agency model: 2-3 designers were assigned to each new project and tasked with designing something totally different from their counterparts. The client would choose a design (or they’d make the worst of all possible decisions and combine two of them), and the designers whose work wasn’t picked would go on to new projects. The selected designer would work with the client to design each page, using whatever tools necessary, and hand it over to development to build. This was and continues to be a super common way to do web design, but the end result is that you’d usually get your designs built not quite right by the developer.
Part of doing web design was (and continues to be) understanding what the medium is capable of. If we designed something crazy or just not-quite-possible, we’d get an approximation of our designs live on the web and this was a thing I’d get sort of sad about. I wanted my pages to look and work how I designed them, dammit.
I alluded in Part 1 to a tendency of entirely visually-focused graphic designers to make fun of the web in 1999. At the risk of sounding incredibly “get off my lawn” about it, here’s an incomplete list of things we didn’t have as web designers when I started out:
Without a clear mode of operation to follow, we got to make things up. We tried to figure out what this new “web interface” idea should really look and feel like, given the limitations of the browser. We couldn’t do the UI heavy lifting you had on the desktop, and the whole idea of pages broke the application metaphor anyway.
We improvised and we changed course quickly because that was and continues to be the benefit of designing for our platform:
My first two clients were businesses commonly referred to as dot-coms to denote their internet-only status. My official title was Production Artist and my job was loosely defined as helping designers put their work on the web. My first two projects ended up being simply design projects that I used code to produce, which has impacted my entire career to-date.
Why.com (forever embedded in my brain by its clever logo leveraging a question mark for the dot: Why?com) was assigned to me at the same time. This was a search engine that included a social aspect: other users were able to rank, rate, and recommend search results for given terms. Apple launched a service called iReview not long after, effectively killing the company. Two things stand out during my time working on why.com: it was the first time anyone in our office had heard of Google, which powered our search results (we thought it was a weird choice), and it was this project that provided me with my first business trip.
I didn’t realize it at the time but Scott Upton, my lead on the aforementioned projects, was also the designer whose work I’d most admired in the company’s portfolio from afar. I still haven’t had a creative director quite like him for three reasons:
For the first 6 months of my professional career, code and design were one and the same. There wasn’t a developer alive who’d touch Flash at that time and having our hands in the code of a site, no matter the language, gave us a control over the end-result that no amount of wire-framing or Photoshop mockups could give us. The client would usually see screenshots of our work, but that work’s production had a web-native methodology baked into it; we knew the screens we designed could be executed in code because we were already doing it.
Some common stressful situations that could have ruined your day circa 1999:
“There’s a typo on the final production graphics that millions of people are looking at right now.”
“Users hate the new placement of the button for the feature we shipped last week. No one can figure out where to find it and they’re throwing bricks through our windows.”
“The colors aren’t right. The red is too purple.”
“No one is clicking the BUY NOW button!”