Browse Prior Art Database

Process to Validate Client Experience Attributes for Hardware and Operating System Development

IP.com Disclosure Number: IPCOM000241175D
Publication Date: 2015-Apr-01
Document File: 2 page(s) / 99K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a process to improve client experience with hardware and operating system products based upon three pillars of validations: Breadth of Validation, Iterative Validation, and Customer Relationship.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 2

Process to Validate Client Experience Attributes for Hardware and Operating System Development

Client experience is a key competitive factor for Sciences, Technology, and Globalization (STG). Organizations seek methods to improve client experience with current systems and solutions we deliver to in the marketplace, minimize the risk of client experience issues at product introduction, and address client experience earlier in the development cycle, when it is more cost-effective and less disruptive to the clients.

The following definitions are used in this article:


Client Experience : describes the fit between the customer's needs and expectations, as measured from the actual experience with the given products and processes. The requirement is to meet or exceed these needs and expectations.


Validation : denotes the process of exposing products and processes to customers, or to people who can think like customers, in order to assess this fit


Client Experience Validation Process (CEV Process) : denotes a linear process of goal setting, validation planning, validation execution, and validation assessment

The novel process builds upon three important pillars of validations to validate and assess client experience, and then use it to improve future products. The three pillars are: Breadth of Validation, Iterative Validation, and Customer Relationship. The novel process outlines methods to include validation in those three pillars, a method to assess the validation, and a method to determine at what points in the development cycle to perform these methods.

This Client Experience Validation (CEV) process uses following three definitions:


Breadth of Validation : Every intersection of the client and the product should be validated. This is relative to the functions available in the release, but extends beyond the traditional Value Proposition proof points. This includes, but is not limited to, marketing of the value, technical sales planning material, product ordering, service, support, installation, updates, migrations, functional/runtime aspects, Remote Access Services (RAS), manageability, fit into information technology (IT) environment (e.g., hardware, software, applications, and management), quality, and all human skill touch points.


Iterative Validation : Starting with the earliest development phases, Client Experience Validation should happen during each phase. This includes iterative validation that occurs throughout the development process. Multiple validations on the same process should occur from design through general assembly, function, or client touch point; the final validation of any...