2. @hp Prototype Page # July 2001 Design prototypes @hp Design and Communication Tools: Proof of Concepts, Prototypes and Demos: Definitions and Purpose

3. @hp Prototype July 2001 Design prototypes Page 3 Four @hp Communication and Design Tools Proof of Concept HTML Release Prototype HTML Visioning Prototype Promotional Demo A design tool used to validate and communicate the design and flow of the upcoming release of the @hp Enterprise Portal. A tool created to prove the technology and functionality A marketing and communication tool to effectively and easily communicate upcoming enhancements of the @hp Enterprise Portal. Provide a tool to help validate and communicate the 12-month vision of the @hp Enterprise Portal.

4. @hp Prototype July 2001 Design prototypes Page 4 The Ideal Approach HTML Prototype HTML Prototype Epicentric Proof of Concept Epicentric Proof of Concept Visioning Prototype Visioning Prototype Promotional Demo Promotional Demo Step One: Create HTML Prototype based the current requirements from @hp and TEE, Marketing, Mgmt, etc. Step Two: Use to test TEE and usability. Update design based on feedback. Validate Design Step Three: Provide HTML to prototype Development Team to create POC. Also provide to Customer Advocacy to create Promotional Demo And Visioning Prototype,and on-going usability testing. Step Four: Repeat process for subsequent releases The following approach could be used as part of the @ hp release planning process:

5. @hp Prototype July 2001 Design prototypes Page 5 Where are these tools developed and used in the lifecycle? Investigate Design Develop MTP Production Visioning Demo (12 mo. ahead) Proof of Concept HTML Prototype Promotional Demo

6. @hp Prototype July 2001 Design prototypes Page 6 HTML Release Prototype LC Stages: Investigation and Design Objective Scope Usage Owner A design tool used to validate and communicate the design and flow of the upcoming release or MTP change of the @hp Enterprise Portal. Include all design components of R3, including look and feel, navigation/taxonomy and Epicentric module integration Include some simulated functionality and content Static and Portable (I.e. HTML); easy to update Tool for validating design requirements of upcoming release Leveraged by development team for POC Usability testing, communications, training Customer Advocacy CPE: (Ben Hutchins) Info Source(s) Audience Business, Functions, TEE, Marketing & Research, Management Requirements Communications, @hp Management, Tee, Training

7. @hp Prototype July 2001 Design prototypes Page 7 Proof of Concept LC Stage: Development Objective Scope Usage Owner Provide a tool that will assist developers during the design/development of R3; prove Epicentric functionality Build a site that demonstrates new R3 functionality, incorporating some of the new “look & feel” Prove Epicentric capabilities Build in actual development environment Ongoing proof-of-concept tool for @hp Enterprise Development team Usability testing @hp Enterprise Development Team Info Source(s) Audience HTML Prototype @hp Enterprise Development Team

8. @hp Prototype July 2001 Design prototypes Page 8 Promotional Demo LC Stages: MTP and Production Objective Scope Usage Owner A marketing and communication tool to effectively and easily communicate upcoming enhancements of the @hp Enterprise Portal (R3). Demonstrate the look and feel of R3 with some simulated functionality. Include animation and audio enhancements to highlight new site features. Static and Portable (I.e. HTML) Currently the demo is in Flash and takes only a few minutes to go through the entire demo. Communications and Marketing tool to promote upcoming release Customer Advocacy (Rachel Watkins) Info Source(s) Audience HTML Prototype, Marketing Team. End-Users, Customers, B2E Marketing

9. @hp Prototype July 2001 Design prototypes Page 9 HTML Visioning Prototype Objective Scope Usage Owner Provide a tool to help validate and communicate the 12-month vision of the @hp Enterprise Portal. Mirrors the R3 Portable Prototype Includes potential design and functional enhancements collected from businesses across hp “wish list” Includes some simulated functionality and content Static and Portable (I.e. HTML) Validate potential design/features of upcoming releases Help set direction for future @hp portal release planning Provide a single, consistent vision for evolving the portal Customer Advocacy Management (Janet Beyers) Info Source(s) Audience Technology, @hp Mgmt., Business Plan and Direction EC, Management, B2E Marketing

10. @hp Prototype July 2001 Design prototypes Page 10 Side By Side Comparison Owner: Development team requires a functional model to base further design/development efforts of the @hp portal. Sits in development environment and incorporates true functionality @hp Development ( Chris claborne) Proof-of-Concept Key Distinction: Why it’s necessary? Estimated Shelf-Life: Customer advocacy requires a portable prototype of the upcoming @hp portal release for usability testing, release planning, and communication. Portable; static HTML format Reflects actual design/layout of R3. Contains some simulated functionality CA: Design (Ben Hutchins) @hp Communications requires a marketing presentation to communicate new features/functionality of @hp portal Multimedia application (I.e.Flash demo, video) Focused on marketing new features of @hp portal CA: Communications (Rachel Watkins) Customer advocacy requires a portable prototype to help define future features/functionality of the @hp portal Portable; static HTML format Focused on the future vision of the portal (12-18 months) CA: Mgmt (Janet Beyers) HTML Release Prototype Promotional Demo HTML Visioning Prototype Until the end of the development lifecycle Until next Portable Prototype release. 3 months (associated with major changes to portal, not releases) Created during release planning cycles 12-18 month vision Each Initiative is Required All four prototypes/demos have separate objectives and specifications. Each should have its own strategy and associated processes.

11. @hp Prototype July 2001 Design prototypes Page 11 Recommendations All Initiatives are Required All four prototypes/demos have separate objectives and specifications. Define Strategy/Processes In the future, we need to have a standard approach to release planning activities and understand how these prototyping tools will be used. Identify Ownership A group and individual within hp should be assigned to own each of these initiatives in the on-going process

12. @hp Prototype July 2001 Design prototypes Page 12 Recommendations HTMLVisioning Prototype HTML Release Prototype Proof of Concept Promotional Demo Owner @hp Enterprise Development Chris Claborne Customer Advocacy Communications Rachel Watkins Development Customer Advocacy Communications Rachel Watkins @hp Enterprise Development Chris Claborne/ Stellcom @hp Enterprise Development Chris Claborne Customer Advocacy (Janet Beyers/PwC) Customer Advocacy Design and Tools (Ben Hutchins) Strategy/Process Func. Requirements Customer Advocacy Design and Tools (Ben Hutchins/PwC) @hp Enterprise Development Chris Claborne @hp Enterprise Development Chris Claborne Customer Advocacy Communications Rachel Watkins Customer Advocacy Communications Rachel Watkins @hp Enterprise Development Chris Claborne/Stellcom Customer Advocacy (Janet Beyers/PwC) Customer Advocacy (Janet Beyers/PwC) Customer Advocacy (Janet Beyers)