CHUBB User Experience (UX) Deliverables

The below list contains a key deliverables throughout the User Experience process.

Stage 1
Narrative Reports  

Review Business (Stakeholder) Requirements

A stakeholder meeting is a strategic way to do all of the following from a business perspective:

  • Gain an initial understanding of your users and their needs
  • Find out about any existing customer research
  • Understand your business objectives
  • Learn about the proposed strategy and plans for the new application
  • Ensure that all factors related to use of the system are identified before design starts
  • Brings together all the people relevant to the development, to create a common vision
User Research  

Target Audience Document

Blackwell will provide a document to help Chubb's team identify each the needs or each person who will be using the system. The goal is to identify key users groups and discover the following:

  • What the site needs to do so they achieve your business goals
  • Their goals, needs, behavior, attitudes and motivations
  • What kind of functionality they'd realistically use
  • Exactly how they go about completing key tasks on the website



  1. Create Template
  2. Deliver to Chubb
  3. Chubb will interview users
  4. Chubb will populate document
  5. Blackwell's User experience designer will review document

Create Wireframes

A wireframe is a skeletal (black and white) rendering of every click-through possibility on your site - a text-only "action," "decision" or "experience" model. Its purpose is to maintain the flow of your specific logical and business functions by identifying all the entry and exit points your users will experience on every page of your site. The goal is to ensure your needs and the needs of your visitors will be met effectively in the resulting application.


  1. Create wireframes for first 4 sections identified in project plan (view wireframe example)
    1. General Bond Processing
    2. New Bond Processing
    3. Bond Renewal Wireframes
    4. Cancellation and Changes
  2. Review with development team
  3. Revise
  4. Test with users (at least 3-5 users)
    Usability testing involves watching actual users use your application. The results of the analysis are a huge eye-opener and their implementation often leads to a greatly improved understanding of your customers' needs and thus more user satisfaction
    1. Pre Test Planning
    2. Recruit Users
    3. Conduct Usability Test
    4. Post-test Analysis
  5. Revise
  6. Finalize
Stage 2
visual design  

Visual Design

The overall visual and aesthetic design of the user interface. This is created after the wireframes have been completed and after the creative brief has been reviewed.


  1. Visual Design Meetings - Review Creative Brief (view sample create brief)
  2. Create Design for 1 page which will server as the model for all other pages (view landing page example)
  3. Review #1 with client (2 major revisions included)
  4. Revise
  5. Review #2 with client
  6. Revise
  7. Signoff

HTML Prototyping

  1. Code approved visual Design into HTML/CSS
    1. Adhere to Web Standards
    2. Add each unique page to an online catalog (Style Guide)
    3. Utilize, update, and maintain Style Guide
  2. Migrate existing approved wireframes into Storyboards (HTML/CSS static prototype)
    1. Create an HTML example for each unique looking page (these pages are listed and categorized and in a shared site which will become a Style Guide)
    2. Update and maintain the Style Guide
Stage 3
Narrative Reports  

Continue to Review Requirements

  1. Review Stakeholder Requirements
  2. Review Target Audience Document

Create Wireframes

Create wireframes for all of the other sections of the application.


  1. Homepage
    1. Create
    2. Review & Revise
    3. Sign-off
  2. TX Dividend
    1. Create
    2. Review & Revise
    3. Sign-off
  3. Surety Express
    1. Create
    2. Review & Revise
    3. Sign-off
  4. Power of Attorney
    1. Create
    2. Review & Revise
    3. Sign-off
  5. Fronting Desk
    1. Create
    2. Review & Revise
    3. Sign-off
Style Guides  

Style Guide

This will be an on-line catalog which defines a set of standards for identity, design, and writing to promote clarity and consistency for all applications. This will increase the consistency between screens, reduce the development time, and enhance usability.