Your friends at Viget present Advance, a Strategy & Marketing Blog

What #TheDress reminded me about web design

As the dust settles on #TheDress debate and the naysayers start to see that the dress is obviously blue and black, I've realized that there is an underlying lesson to be learned from this internet sensation:

People see things differently based on their circumstances.


This is an important reminder. As professionals in the web design world, it's something we need to constantly keep in mind. Whether it's due to screen brightness, environmental lighting, time of day, or some other external factor, there's inevitably going to be a number of considerations to take into account when designing for the web.

Sifting through the hundreds of articles on #TheDress, you'll find that some postulate that it might be your emotional state that's causing you to see blue and black vs. white and gold. Could this be the real reason? I can't answer that, but what I do know is that it's yet another factor to take into consideration.

The Next Rocky Mountain Digital Project Manager Presentation: Atomic20

On Thursday, February 26, Rocky Mountain Digital Project Managers will get together for another great presentation from local digital leaders.

This month, we’re back in Boulder and are excited to have Atomic20 as our host. By coming to the event, you’ll get a chance to see their space and hear more about their process! Atomic20 is a marketing agency and shared creative workspace dedicated to free agents and curating teams who solve design challenges. How Atomic20 fields teams is different than many agencies and it will be interesting to dive into the details with them.

Atomic20 will also be providing pizza and beverages!

Using GitHub on Multidisciplinary Teams

We use GitHub for file versioning and code reviews on almost every project here at Viget. With less frequency, we use GitHub Issues to assign tasks and address bugs. With even less frequency, we use Milestones and Wikis for setting deadlines and documenting projects, respectively. In most cases, we lean heavily on GitHub’s primary offering while ignoring the power of its myriad other features.

What if we used more of GitHub’s features? What if we involved more members of a project team outside of developers? What would that look like?

I’ve got a couple of ideas. Now, I haven’t been able to put all of these ideas into practice, so they may or may not be feasible. In this post, I’ll trade out some of these ideas, attempting to wring even more value out of an already indisposable tool.

An Uncomfortable Missing Part of the Accessibility Discussion

We're making an internal push at Viget, led by Jeremy Fields, to better incorporate accessibility into more of our projects. But when we talk about accessibility internally, it often feels like the conversation ends up in an awkward place.

I had the same awkward feeling when reading Anne Gibson's "Reframing Accessibility for the Web" article on A List Apart and other recent articles about accessibility. They feel awkward because they largely avoid an important but obvious piece of the discussion. 

It's an uncomfortable missing piece, to be sure. But unless we address this uncomfortable truth head-on, I don't think the accessibility argument will ultimately succeed.

Project Managers’ Other Work, Part 1: Introducing Definition and Documentation

This post is part of a series about the heretofore-unarticulated areas of digital project managers' work that make up a large portion of the job. Read other posts in the series: A Different Way of Thinking About Digital Project Managers' Work.

Do these scenarios sound familiar?

  • You're regrouping with the team after a kickoff meeting, or a few weeks into a project just before development is set to begin. The discussion goes around in circles, and finally a developer says, "I just don't know what we're supposed to be building."
  • A developer is ready to start implementing a ticket but has to stop and ask you, "Wait, how is this supposed to work?"
  • The team is discussing a view in the site you're building. The UX designer keeps talking about a landing page, but the developer is talking about a product index. You can't tell if they're referring to the same thing. Meantime, the wireframe file for that view is titled "product-landing-page" and you can't find a correspondingly named design comp (turns out the PSD is named "products").

If so, you've encountered common deficiencies in two of the key areas of project managers' connective-tissue work: definition and documentation.