Wells Fargo : Banner Builder
Attempting to take the Advertising production process completely off the hands of the agency, Wells Fargo championed a 'banner builder' application which would allow their sales team to roll their own. This became a component in their greater extranet application.
| Project Year: 2004 | Project Status: Dead | Agency: Grey SF | Relevant Link: |
| Technology: PHP / SQL | Project Duration: 4 months | Employ: FTE | Agency Site |
Facets Include:
1
Business Requirements
A part of GREY's offering to Wells Fargo as a part of a greater agency account, the Marketing Extranet was tailored to their specific needs while retaining a site template.
Stakeholder Interviews
Client representatives were interviewed to assess the needs for the local and regional offices surrounding their creative assest and distribution / approval process.
Heuristic Analysis
Analysis of previous versions of the intranet were integral to making staged improvements each step along the way. Generalized acceptance of one's flaws from a previous development cycle.
Facets Include:
2
Usability Testing
As a part of a continual cycle, provided feedback surrounding the extranet were integral to improving the usability of this product.
Process Flows
Wells Fargo had several 'microsites' which performed specific tasks - each of which needed to integrate with the greater extranet. Site structure diagrams helped plan the inter-dependencies.
Site Structure Diagrams
Wells Fargo had several 'microsites' which performed specific tasks - each of which needed to integrate with the greater extranet. Site structure diagrams helped plan the inter-dependencies.
Facets Include:
3
UX Wireframes
These wireframes helped the client realize the scope and scale of the extranet, as well as assist in customization and development for before release cycle.
Design Comps
The creative look and feel matched the agency's greater efforts, while still translating well to the interactive space. A muted, earth-tone palette still held a high level of contrast for proper legibility.
Cascading Stylesheets
Whenever possible a tableless design solution was found for layout of page content. Separation of presentation layer and front-end code allowed for greater modularity.