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 pros

Destination Sites Reuters Business Briefing Dow Jones Interactive Factiva Integration Factiva Developer Server Software Factiva Links RBB Select Factiva Publisher

CONSTRUCTION JUSTIFICATIONDEFINITION ARCHITECTURE DESIGN TESTINGLAUNCH SUCCESS REVIEW FACTIVA Product Development Process PRODUCT RE-EVALUATION IDEA GENERATION 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 Integration Factiva Publisher

User Interface Default View Sneak Peak Factiva 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

Factiva Developer Objects

Back An Example of DJIs Content Objects at work

Info Pro as Product Developer Definition of results User needs Working with vendors Justification Implementation Evaluation