Don't Make This Mistake

Following on, if you do need to redesign the community interface, inform everyone first. Explain why you need to do it and the benefits of doing it.

Take your community through the entire design process. Show them the same screenshots and templates your designers show you. Listen and respond to their concerns.

Let members participate in the new design. Use some of their suggestions and invite important members to test the community before you launch. Perhaps even let them write the copy for each other?

Comments

[Jodith]

At my real job (i.e. the job that pays me money, not blogging) we are in the process of redesigning the entire corporate intranet. It's going to be a big change, both in look and functionality. We're already planning things out so we can minimally affect the day to day work of our employees. A big part of that is information. Let people know what's happening, when and why.

The other part is doing small incremental changes over time, so there isn't one huge change that is disruptive to everyone. Whether your community is a work community or an internet community, it's important to communicate changes. One of my suggestions, which I find way to few sites do, is to have a Changes page, so folks who haven't looked at the site in a while can see what changes have happened, so they can find that piece of information they need that you moved.

[jenx67]

I am really interested in why you are moving to Vilinius. I've been learning about development in this city through a blog by a Fulbright Scholar. Here is her blog: http://cathyinvilnius.blogspot.com/
She is on my blog roll. I really enjoy her posts. She is a city planner. You may have already discovered her, but if not, enjoy! I left an introduction for you on her blog a well.

[jenx67]

that would be *vilnius* sorry.

[Grant Simmons]

A redesign *should* be a collaboration and driven by users.

More often than not, marketing departments decide a change is a necessity to visually justify their efforts.

The mantra "if it ain't broke don't fix it" is relevant to websites as well as mechanics.

Users and user requests / comments / feedback should drive and justify redesigns, egos or job justifications should not.

2c

[Richard Millington]

Hi Jenx67, thanks for recommending Cathy's blog. I'm trying to find an e-mail address that I can use to contact her.

My girlfriend is Lithuanian and an architect. I live with her in the UK, and she needs to move to back to Vilnius for 6 months to finish her degree. So I figured I'd move back with her.

[newsblaze]

Quite often - in my past experience, - changes were made based on requests from clients and visitors, not by marketing for the sake of change.

I have seen change based on marketing or sales people wanting to have the latest and greatest new idea.

Like you, I prefer to make incremental changes. If you get hate mail, you can more easily roll back.

[Richard Millington]

Thanks for the comment newsblaze. You're absolutely right.

Part of building teh community, I feel, is to fight for the community. That might mean fighting hard against your own associates.

It's a hard but worthwhile part of the job.