We use cookies to personalize content, to provide social media features and to analyze our traffic. We also share information about your use of our site with our social media, advertising and analytics partners. For information on how to change your cookie settings, please see our Privacy policy. Otherwise, if you agree to our use of cookies, please continue to use our website.

The Top 3 Don'ts on Running a Successful Responsive Design Project

Caitlin Roberts, Account Manager at Merkle, has many enterprise Responsive Design projects under her belt. Through her hands-on experience interacting with clients on a daily basis, she has learned the many do's and don'ts of what to do and what not to do on a Responsive project. With this in mind, she shared with The eTail Blog her "Top 3 Don'ts on Running a Successful Responsive Web Design Project."

As a kid, I used to hold out my hand and shout ‘TIP?’ to my Mom when I did something she asked me to. She always replied: ‘Of course!’

She would then proceed to reach into her pocket, as if she was grabbing me wads of cash, and say, ‘Don’t bet on the race horses!’ with a high five against my eager hand. There was never any cash exchanged, just a tough life lesson I had to learn. This was until one day, I finally realized that sometimes a bit of advice on what not to do, can actually go pretty far. The more I’ve thought about this article and how to approach it, the more I’m brought back to this exchange.

Successful implementations don’t always have to result in a client up-sell, added revenue, or in the case of an 8-year-old, two extra dollars in your pocket. Successful project management in the responsive web design (RWD) world can teach us a lot about what not to do, the “Dont’s” if you will.

1) Don’t assume that everyone in the room knows what responsive web design is.

At my first kickoff for a project, I walked into a room of 20 client stakeholders. They ranged from departments including IT, design and marketing. Only three in the room were involved in the sales process and knew how our technology worked or what RWD was.

As more project kickoffs came my way, I learned how important it was as a PM to provide a background and context on our technology, and what the client had signed up for. This sets expectations and ensures that everyone is on the same page from day one. A little education can go a long way!

To read the full article on The eTail Blog, click here

Join the Discussion