Product Optimization

Is it more important to build the right product, or to build the product right? We would answer YES. Building a product that does what you intend it to do is important (the product built right), but no more important than building a product that really fulfills customer requirements (the right product).

It is recognized by international standards, as well as practical designers, that both usability and fulfillment of user needs are key considerations in the determination of software quality. The ability to satisfy user requirements is a key measurement in our definition of quality. We also include usability in our quality metric. We have built a process for designing products that considers a continuum of requirement vs. usability trade-offs and enables us to work with you to optimize your efforts towards your target.

All this constitutes a baseline. The fact is that software systems - whether built to address the needs of an enterprise, or the opportunities of the market - offer diverse feature sets, and tend to be used by multiple classes of people. Those needs, or requirements, vary depending on a range of dimensions having to do with their backgrounds, abilities, roles and objectives. As a result it's usually impossible to say that a product fulfills requirements without also identifying for who, and for what.

To address this complexity, we have built systems to perform segmentation of the target user communities, and to identify which sets of product requirements apply to each community. Depending on how deep you want us to go, we can use our systems to optimize your product or service to particular segments, or user communities, peforming specific classes of tasks.