Everything But Visual Design

#designProcess  

As our product has matured, our team has expanded, and our marketing site’s information has evolved, we’ve discovered a need to holistically re-approach our public facing marketing site. So I’ve recently been doing some initial design thinking around what we’re internally calling “Marketing Site 2.0”.

This realization started as a discussion amongst two or three of us internally. That discussion evolved into a formal meeting where we tossed ideas around the room, sketched them out on a white board, and took notes. Those notes were jotted down as guidelines for further guidance in developing the hazy idea of “Marketing Site 2.0” (it is worth noting that all of this happened over the course of a few weeks, in and out of other more pressing meetings and projects).

Once we had a loose rubric to follow you might think I jumped right into the visual design of the new site, but I didn’t. Don’t get me wrong, I wanted to because that’s the exciting part. But experience has taught me that putting any work into high fidelity visuals this early would prove an inefficient use of time. The next hurdle was getting buy-in from stakeholders in the marketing site, which meant basically every major head in the company.

As a design team we had a common, unspoken, un-written-down understanding amongst ourselves as to why this “redesign” was necessary. But we realized we needed to formalize our argument to get buy-in from other stakeholders in the company. Simply saying, “the marketing site needs a redesign” wouldn’t cut it. So I started to think about what this “redesign” would entail by sketching out some of our ideas as they related to the site’s information architecture, user flows, etc.

Picture of sketches

After we had a basic conception of what the new site could be, we put together a slide show with our arguments (backed by the data which impelled us to even begin this project) along with some low-fidelty wireframes I had created to help tell a story as to why we’re doing what we’re doing, how we plan on executing it, and how it will benefit all stakeholders involved, including current and future customers.

Screenshot of mock in Sketch

Why am I saying all this? Because this seems to be, most often, the real “design process”. You have ideas and intuitively you know the reasons as to why they have promise. But if you can’t vocalize those arguments and convince others as to their potential, you’ll likely never get anywhere. So before you jump into your design application of choice to create the next best thing, you’re likely going to have to convince others why you should be jumping into your design application of choice to create the next best thing.

Oh, and if you’re interested, our formalized arguments, data, and mocks helped convince those involved that what we were doing was indeed a good idea. Now we just have many more meetings, sketches, notes, arguments, and low-fidelity mocks to go before I can jump into my design application of choice. That is going to be the easy part.