How Customers Develop Factiva Products

Ann Lee

Special Libraries Association

June 13, 2000

Customer as Product Developer

Incorporating customer input into the design process

How our customers have implemented creative solutions

A new career for info pro’s

DestinationSites

Reuters Business Briefing

Dow Jones Interactiv

e

FactivaIntegration

Factiva Developer

ServerSoftware

Factiva Links

RBB Select

Factiva Publisher

CONSTRUCTION

JUSTIFICATION DEFINITIONARCHITECTURE

DESIGN

TESTING LAUNCHSUCCESS REVIEW

FACTIVAProduct Development Process

PRODUCTRE-EVALUATION

IDEAGENERATION

Methods of Work

How Do We Collect Customer Input?

Individual research interviews globally

Field observations of users

Usability testing of new product concepts

Continuous loop

How we choose participants

Various professional roles

Users of different products

All vertical markets represented

Geographically diverse

Monitoring the Market

Evaluations of current products globally

Forecasts

web access

industry trends

business climate -- flatter orgs, e.g.

What is important to users?

Speed/response time/performance

Post-processing of results

User administration

Company searching should be easy

What is important to users?

One product that works for all levels

Clear, simple labels for global audience

Allow for customization

Integrate content

different types of sources

internal and external

Factiva IntegrationFactiva Publisher

User InterfaceDefault

View

Sneak PeakFactiva

Publisher

Back

Info Pro as Product Developer

Greater choice of products

Component-based purchases

Customized for their environment

Opportunity: not limited to out-of-the-box

Back

Back

Factiva DeveloperObjects

Back

An Example of DJI’s Content

Objects at work

Info Pro as Product Developer

Definition of results

User needs

Working with vendors

Justification

Implementation

Evaluation