February 9, 2012 - 11 comments

#siteweek

This week, we're redesigning the happycog.com. Yes, this week: everything will be built from the ground up. New IA, new design, new copy, new code. It's all new, and it's all being done in 5 days. 

It's a lot of work. It's also a lot of fun. We're on day four of a five-day project, and so much has happened. I feel as though I have learned a lot, because I'm seeing the activity on a project that would typically take us six months or more in five work days. I'm siting in a conference room with my amazing coworkers who are designing and building the site, so I have the benefit of hearing and knowing the full spectrum of thoughts going into every detail. For me, that is invaluable. Plus. I've been able to jump in and help out. It's been fun to apply some of my day-to-day PM experience, but  I've also learned a lot about how projects can work, how they should work, and what can always prove to be an issue. Here's a quick breakdown of what I've taken in so far:

Communication...Yeah.
I'm like a broken record. I think all I ever write about is how communications are the most important aspect to a project. It's true, and I found that out within the first two days of this week. Our first day was full of brainstorming. That led right into working. That meant that everyone was eager to do as much as possible. It also meant that people were having conversations without the rest of the group, and that not everyone knew what was happening all the time. So, we had to adjust the way we were working and put a good communication plan into place. We needed regular check-ins and decided on this schedule: 10am, noon, 2pm and 4pm. A quick review of what everyone is working on at the moment, and any issues that needed to be addressed. That's helped us immensely.

Plans Change. Adapt.
Project plans almost never play out the way you expect. They certainly don't on a short, high pressure project, but it's good to have a high level list of things that need to be done and a target day/time. We're working from a list with that kind of detail. I have found that it's best to keep track of who's doing what, when you need things done, and how they're getting done. New tasks will come up and requirements might change, but knowing what can/cannot be done in a week is critical. A high-level list will help in setting or maintaining that expectation.

Document Everything.
We're using Basecamp To Dos and writeboards like bosses. Everything is there; if it isn't, it probably didn't happen. It's nice to know that one-off conversations are turning into "I'll add a To Do for that." Also, I made one whiteboard a status board that lists the goals for the day, our check in times, issues, and a bulleted status list for everyone on the project. We reviewed that list at every check in. It works well to show how much progress is made.

Don't Be Bashful.
Someone in the room has to be listening to what's going on, making sure that there are no conflicting details, or questions unanswered. I have felt that a lot of my job this week has been to resolve issues by asking question about the tasks (and following-up) and making sure conversations are happening.

Have Fun.
Yes, work is serious and you'll be under pressure. But have fun. Honestly, that has been the best part of this week. The crew I work with…they're awesome. And very funny.

So that's it. Tomorrow is launch day. Another day of lessons learned. I'm excited. Also, ready for a celebratory beer with all my buddies.

Published by: brettharned in Uncategorized

Comments

Brad Frost
February 9, 2012 at 10:48 pm

GET BACK TO WORK.

James Collins
February 10, 2012 at 9:02 am

So, in a whippersnapper project like this, which PM traditions did you have to break? Did you write up a brief or work straight from the whiteboard? What were your initial questions/comments to the creative team? Arrrrg, so many questions!! Congrats on the launch!

    brettharned
    February 15, 2012 at 4:18 pm

    Thanks James!

    I can’t lie: there was some pre-work. There was a requirements document (which I did not write) that articulated what must be included in the new site. There was also a document that laid out the goals for the week, in generalities.

    At the same time, our company’s leadership finalized the new brand and worked with the design team to select a mood board design that could be executed during siteweek. So, that definitely got a lot of the design decisions out of the way. There was still a ton of work to be done…but our team is pretty amazing and collaborative.

Crystal
February 10, 2012 at 9:53 am

new website in 5 days…you peeps are crazy! Can’t wait to see how it looks. Thanks for sharing insight into your process. It’s nice to see how you think through a project and then compare that to my own style. Really helpful!

    brettharned
    February 15, 2012 at 4:14 pm

    Thanks, Crystal. I’d love to hear if there are any major differences. I’m always looking to learn.

      Crystal
      February 15, 2012 at 4:37 pm

      The new site looks really great! And I must say, 5 days for a new website (especially since it’s your own company website) has inspired me to inspire my team about what can and can’t be done with tight timelines. I liked the Check-In meetings you mentioned. I think just using the term “check-in” vs meeting or internal review would help the meeting haters on our team. If you don’t mind, I think I’m gonna use that tactic 🙂

Sloan Miller
February 10, 2012 at 10:11 am

Congrats to everyone at Happy Cog for the rapid project execution!!

Brett the war stories and lessons learned from this project must be amazing. I’d love to hear more about some of the team member interactions, how you resolved some of the typically project related issues (so rapidly), and how this project is going to change your approach to future client-based project work.

In my experience internal projects generally take way too long (our site redesign took three times as long as we planned – http://bit.ly/zTG9SE for more details). Congrats again it must have been an unbelievable ride.

    brettharned
    February 15, 2012 at 4:14 pm

    Thanks Sloan! I have to say, working with an awesome team who are willing to bend is half the battle. That doesn’t mean that we didn’t have any issues with communication or even conflict, but it had to work out. We all wanted to make it to Friday night happy hour.

    I’d say that this is a great start for a new site, if you are brave enough to make yourself redesign in one week. But the project won’t end there. We’re planning for some immediate upgrades and additions. But at least the foundation is there and we’re all happy with what we’ve done so far.

Alex Turbett (@alexonbass)
February 12, 2012 at 1:39 pm

Like James, I’m also interested in what you needed to adapt from a typical PM process to one condensed into 5 days, AND one where the client is actually the very people working on the project. Did anything that is typically critical end up lacking (i.e. QA, standard documentation, or other typical process)?

Congrats on the new launch and thanks for the insight from the PM side.

    brettharned
    February 15, 2012 at 4:11 pm

    Hi Alex. Thanks for posting and the kind words.

    We’re going to follow this project up with a much-needed post mortem meeting. That should bring a lot of the issues to the forefront fro correction if we dare to do it again. But yes, there were some things that lacked just due to time. We worked from a requirements document, but that was altered at times. We documented our IA on whiteboards, but things changed in places. We then missed documentation of those changes, and that affected other pieces of the work. This was certainly a departure from our process, but one that might provide some insight on how we can handle things moving forward on new client work.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.