B2B site redesign process

  • Started
  • Last post
  • 22 Responses
  • flashbender0

    If anyone is interested, this is the outline that I cam up with.

    Thanks to all for your input.

    // Discovery Stage
    identify key stake holders
    identify/catalog all existing online properties
    determine scope of project - what all will be included in the redesign (shop, countries, draft review ... )
    select agency/ies

    // Research Phase
    Hold stake holder interviews to determine primary and secondary business objectives *both group and regional
    -- Customer Research
    shared traits of high value customers
    how the site is currently used
    how customers would like to use the site
    learnings from earlier tests and limited redesigns (forms, quality, training)
    !!!! important: create a full and rounded view of how people are using ALL existing properties to be effected by the redesign

    // Customer Profiling
    Create specific customer personas and journeys to identify customer needs
    Compare Customer needs/journey to business needs
    Refine customer journey to ensure that business needs are also met
    !!!! The final customer journey document will serve as the roadmap for the rest of the process.

    // Audits
    Technical Audit - is episerver the correct platform? What tech will be needed based on the previous step - IP recognition, password protected areas...?
    Content Audit - review ALL content currently online - what should be reused, what should be binned?
    SEO Audit - what terms are working for what pages? This will play an important role in both the IA and the content creation

    // Site Structure Development
    IA creation - based on customer journeys
    Create sitemap based on IA
    Create content for all web pages - creating new or reusing existing as necessary
    Create Wireframes
    Create Rapid Prototypes
    Test Rapid Prototypes
    Refine and finalise wireframes based on testing feedback.

    // Design
    Consult with the brand people to determine tone/attitude and look/feel of the website
    Identify key pages/template types and create mockups to define visual style and tone
    Create templates based on brand and testing feedback
    Accessibility testing of templates
    User testing of templates
    Finalize template design
    Populate templates with content

    // Limited Release Trial
    Release new site to UK - run trial for 1 month
    Analyze learning from limited test, apply changes to templates and design
    While the UK test is running, identify key countries

    // launch
    Roll out new site globally

    // continuous improvement
    test and tune

    • I've bookmarked this entire thread.rodzilla
    • that's great!
      vaxorcist has been really helpful
      flashbender
  • zarkonite0

    Needs Assessment
    Personas & Userflows
    Rapid Design Labs
    Site Outline
    Concept
    Technology Plan
    Sitemap & Wireframes
    Content Plan
    Technology Selection & Setup
    Design
    Content Development
    Technology Implementation
    Content Population
    QA/Testing
    Refinement
    Launch

    $$

  • flashbender0

    The auto fill search boxes is a great idea. I will definitely have that on the list of things to explore.

    Granger is similar to the shop portion of the site for BSI (shop.bsigroup.com). This too will be folded into the redesign. If you can pass my email to your friend or just ask him what some of the major pitfalls they faced. That would be handy. If not, that's cool too.

    • Grainger's autofill search box is one of the best I've seen for a site that big....vaxorcist
  • vaxorcist0

    1. auto-fill search boxes can help a LOT, but may hit a database hard... talk to IT about caching search results.... and put in a checkbox to allow people to turn that feature off, some hate it...

    2. extended footers can contain TONS of links without wrecking design

    3. drop-down top menubar items that show whole bunch of links (like granger's PRODUCTS button.. this can work for repeat users well, but test it on an iPhone)

  • vaxorcist0

    Granger did a redesign.... I know somebody who works there....

    http://www.grainger.com/Grainger…

  • flashbender0

    vaxorcist - you are a good dude. And I am going to steal your last line and use that in the proposal.

    And you are spot on - the biggest part of this is going to be actual user testing and we will be working with a dedicated testing agency to do that. Because yeah, people say one thing, but do another - this is made even more complicated by the sheer number of main user types the site has.

    What I'm doing in the mean time is a series of tests based on the current site templates to be used in framing the research plan.

    The biggest assumption that has been made is that it will be a positive to go from the current system of 'hey, we sell things what do you want?' to an approach that says 'Oh, hi! You have a problem? We have solutions, come and explore with us'

    The first test is designed to prove or disprove that.

    Adding to the difficulty of this is that when the content strategy is set getting the marketers to generate the necessary customer based/ benefits focused messaging is going to be an absolute nightmare.

    Thanks a lot for your insight, it is most appreciated.

    • you might allow more than one path to find things... only one = some people miss it..vaxorcist
  • vaxorcist0

    flashbender.... I'm scared about all this customer and business analysis... we took that approach on a project some time ago, it seemed great, lots of meetings, lots of analysis, everyone felt great till the build actually started and ... uh... we found out users had vastly different ways of actually using our stuff than we had planned... even different than what they told us in all those focus groups....

    we had it all ass-backwards....

    we were building an app-like site, possibly a bit different, but there really, really, needed to be a better approach.... and somebody hired a developer from CA who beat us around a bit and knocked some sense into it all, he was hugely into the "fail early and often" approach, show a bunch of somewhat-working testable prototypes to actual users, learn fast what doesn't work, give them tasks, not just asking for feedback, watch more than listen.... videotape them while they try things....

    Our original and bad approach was to think people wanted all sorts of stuff they could specify and tinker with, we ended up with a much more simple system, with a restaurant-menu-like list + a search box.... nobody liked 3 or 4 tier navigation in our experience....

    Good luck, and remember the "Mythical Man Month" ... a software engineering book, arguing that project managers may fool themselves into thinking they can hire more people to make a deadline, but late projects are usually made even later by hiring more people because productive people have to explain everything to everyone new instead of working on stuff,... and invisible disagreements are the main reason it's late...

    Large projects like this are often like a woman having a baby, it takes 9 months, you cannot simply hire 9 women for 1 month to get a baby...

    • note that management needed some convincing to prototype, at first it seemed a waste of time to them....vaxorcist
    • only after we'd had a "beta test" application that irritated actual users were we allowed to test and rethink...vaxorcist
  • vaxorcist0

    I'd consider making a few rapid prototypes in various cheap or free wordpress templates, each one trying a certain approach, then testing these with the HUGE CAVEAT that people know "this is only a test, had this been a real website...."

    why???? Because people's spoken ideas about websites and their actual use are almost completely different in our testing experience.... I did a lot of this, but it was years ago...

  • Irafis0
  • flashbender0

    Hey! Look at that! Some actual useful responses! QBN still has the power to surprise.

    The redesign's main goal is to change from a website designed by committee by the business for the business to something that actually speaks to the user/potential customer. Shocking idea. I know.

    The two biggest concerns that I have are:
    - keeping SEO rank through the redesign so vaxorcist your comments are most appreciated.

    - figuring out how the best way to present the site areas. Right now it is broken down by: country > Business stream > sector > subject. The prevailing theory right now is to present by theme or topic then country then business stream. We'll do a shit load of customer and business needs analysis to figure out just what the right way to handle this is.

    planning/research/analysis is going to take probabally double the actual build time.

    Oh how times have changed.

    If anyone has any links to process docs, I'll be your friend if you post them.

  • vaxorcist0

    SEO things to know....

    1. is there ANY way at all you can keep a lot of URLS the same? a bunch of 404's can torpedo your google juice....this can be a big challenge, as it may force you to re-create the mess you currently have... NOTE: check inbound links on google, then make a list of them, read Matt Cutts too...

    http://googlewebmastercentral.bl…
    http://googlewebmastercentral.bl…

    2. if you do keep some content, try as hard as possible to not duplicate the same content on multiple pages/urls, as this will cause google to think you're a content-farm-spamdexing site...

    3. make sure people know that copy pasted from powerpoint is bad for SEO because it's usually incomplete sentances and not rich enough for google to take seriously, or get inbound links...

    4. make sure people know that copy pasted from print brochures is also bad for SEO, because it's usually wordy and not nearly as keyword rich as content written for the web, with concise sentances.

  • vaxorcist0

    Most imporantly, think of this as NOT about the company/companies, but about WHAT THE TARGET MARKET NEEDS in order to become better customers according to your BUSINESS OBJECTIVES....

    Ask people who matter what will they consider a success, what will they consider a problem and what will they consider a disaster? Get them to write these things down, with clear concise agreements. Use this to determine little questions rather than continually bugging them for details, they will be less micro-manager-esque once they trust that you get their goals.... and once you establish your knowledge of a target market, you can use this as ammunition to stop random tangents and ego-oriented shit taking over ....

    Ask some this OR that questions, establish really clear priorities not just a bunch of "this and that and this other thing" bullshit... once clear priorities are set, architecture almost takes care of itself...

    also make sure you have a clear idea of exactly who has to approve what... often a redesign is a time when people who felt left out last time are gunning for influence....

    Make a list of low hanging fruit and hit a few very quick so you get some reputation...

    • and of course, make damn sure you know WHY they're doing the redesign?!?vaxorcist
  • cannonball19780

    I had to do this before. took forever and was boring as fuck. i reccommend holding a gun to your temple at night to feel alive.

  • Gordy220

    Good luck with that - we ended up rolling out a lighter version for launch and are looking at that kind of thing coming up.

  • flashbender0

    Timescales are up in the air - basically now trying to figure that out. The actual build time should not be too long, but the planning and figuring out the IA are going to be quite long. The IA and the actual structure of the site - segmenting by business theme, industry sector, country... that is going to be the especially trick bit

    We use Episerver for CMS

    • Sorry, dumb question: What's IA? Would it be Information Architecture?oktalk
    • yep. The 'behind the scenes' organisation of the site
      flashbender
  • Gordy220

    I had to do this recently and it was horrendous.

    What's your timescales? What CMS are you using?

  • flashbender0

    and my minneapolis friends who never post

  • flashbender0

    and lvl_13

  • flashbender0

    and spooky

  • flashbender0

    and nairn/detritus