(The kick-off of an ongoing series…)
With shrinking endowments, budget cuts and hiring freezes (or worse) fewer institutions are in a position to hire a hot-shot consulting or design firm to tackle all aspects of a far-reaching strategy / ia / design / content / html / cms implementation type of project.
Instead, colleges and universities (at least many of the folks we’re talking to lately) are looking for ways to do more with limited resources, which often means dividing work between internal teams and consultants like us. Partially to shave costs, partially to build internal capacity and partially just because a website redeployment is a lot of fun (really!). Sometimes we’ll do strategy and design and the college project team will handle writing and programming. Or the opposite. Or a completely different division of labor. The idea is to meet the client where they are: relying on their strengths, filling in gaps where additional expertise is needed.
But… in order for this divide / conquer approach to actually work (and to result in an actually great website) everybody needs an understanding of the nature of the work involved. So over the next few months we’re going to explain — in excruciating detail — the steps we run through in a “typical” website redesign (from initial planning to post-launch debrief meetings).
If you’re running your own project and this helps you keep it all straight, excellent. If you’re considering working with mStoner, it’s important to understand exactly how we work so you can determine what makes sense for you to do and what for us to do. No matter what, if you know up front all that’s involved in your big ol’ redesign then you can make some informed decisions about what to tackle on your own and when (if at all) to look for outside expertise.
The outline of our DIY Website Redesign guide looks like this:
And, starting tomorrow we’re running through ‘Groundwork’ (probably an 8‑part series).
Details to follow…