By @ronbronson

It’s not going to happen. Whether you have a team of 20 or an army of one, you’re simply not going to undertake a project like this by yourself. Still, the process can be daunting if you don’t know where to turn or even where to begin.

Lots of places will logically start with finding a firm to partner with (if you’re a solo) or perhaps you’re the person charged with implementing an already existing solution. Either way, the process isn’t always just about the nooks and crannies of the design and development of your site’s edifice, but the content contained therein.

If you’ve ever undertaken a project of this magnitude, you understand the variables involved. The first time you do it, it can be very daunting. There’s no manual for the beast of a higher ed website redesign, and it’s an easy thing to feel like you’re alone on an island, relying heavily on the advice of external partners who may or may not understand the needs of your institution or how different redesigning a school site is compared to a business or something else.

There are just a few things to think if you’re in the midst of process, beginning to think about and don’t (necessarily) know where to start.

1. Establish a team early

You remember how I said you can’t do it alone, right? The most critical part of the project is making sure you’re surrounded with people who can help you navigate the mine field of all the things. The danger with assembling a team is making sure the core team that’s responsible for content, development and the nuts and bolts of actually getting the site launched is nimble. Whether there’s a larger committee of stakeholders or not, is really dependent on the way your school works. I’ve worked on redesigns with thirty people in a room trying to figure things out and some where it was just three people making all of the key decisions. There’s no perfect way to do it.

2. Ask for help if you need it

It’s a marathon, not a speed walk. You should talk to the various stakeholders in your environment when you’re trying to “do it all yourself,” because not everyone understands the unique challenges of trying to pull off a redesign with 1/32nd of the resources that your more well-heeled (or well-staffed) peers might be accustomed to. Now it doesn’t always mean you get what you want (or that anyone cares. “You signed up for this…”) but there are often instances where things can be done to make things go more smoothly. But if no one knows there’s a possible problem, it’s hard to craft solutions.

3. Plan for tomorrow, not just today

The process is often really focused on building solutions that work for the people in the current jobs at that time. It’s important to make sure the process isn’t person-dependent. So many times, I see redesign projects that adopt their technology or CMS based solely on the limitations of the incumbent. That’s practical, but it’s important to explore what possibilities can balance those needs with a scalable solutions that can last beyond the person. My rule of thumb in situations with limited tech-friendly staff is implementing solutions that don’t require overt day-to-day technical assistance if there’s no web person in-house.

There are all sorts of other things that really are dependent on the needs of the institution. Have you completed a redesign as a solo? What would you add to this list? What ideas should people keep in mind as they embark on this quest? Share with us at @higheredsolo on Twitter or in the comments.