Tag Archives: Minimal Viable Product

Creating your Application Taxonomy

Taxonomies systems for naming and organizing things into groups that share similar characteristics. Initially emerging from Biology and Library Sciences, we increasingly tend to use Taxonomies for describing the outcome structure of buildings, or for labeling the navigation system of a given application.

Creating a product’s set of taxonomies is part of the User Experience and Information Architecture process. It is therefore an important aspect of communicating the product offering to the target audience in a way that will help them understand the product’s functionality, while at the same time, minimizing the amount of time they spend in order to get their bearings and find what options they need to control within the product


Read More …

User Testing Made Easy

In this article I share a recent experience of a user testing session that was conducted. I believe that this experience shows how much easier things become when user testing is performed. Not only does it yield data about your Minimum Viable Product, it is also important to meet regularly with real users to gather user requirements during the initial stages of the development of your product – before it is offered to the market – for these reasons.
Users can test your invention before it heads to the marketplace. Sometimes multiple rounds of testing is required in order for your target audience to understand your offering. Meeting with a sample of potential users provides an opportunity to collect data on user requirements for future releases of versions of your product.
Read More …

Cross Platform Applications and Responsive Design

This article discusses one of the more important trends in current application design and development, cross platform application, which impacts your product’s ability to reach different types of audiences that use various devices. When developing your Minimal Viable Product (Minimum Viable Product), cross platform application support immediately becomes a big challenge to the problem of reaching your target audience.

How to implement cross platform application in products with built-in responsive design features.

Read More …

The Continuing Process of Gathering & Analyzing Users Requirements

Gathering User Requirements involves a process that uses several different methods and sources to find and collect data. This can be comprised of information from interviews, questionnaires , A/B testing and focus groups that will then, in turn, be analyzed along with your Key Performance Indicators (KPI’s).

A common mistake people make is that they tend to treat themselves as one of the users. Like a horses with blinders, we often myopically base what we think the requirements list is, solely on one’s own selfish needs and not on the real and objective needs of the users. The correct way is to first adhere to the process of gathering User Requirements before deciding on what you think those requirements ought to be.

Read More …

Defining your Startup Key Performance Indicator (KPI)

KPI’s and the Human Body

It is easy to understand what a Key Performance Indicator is by way of metaphor, because what the term KPI stands for, comes from our interactions with the human body. The most common KPI that is monitored in Western society is found by studying a person’s health condition, specifically by taking the body’s internal temperature. This is one of the most important indicators that can instantly tell us if someone may be sick or not. A gradual change in temperature or a quick fluctuation can indicate that the human body is recovering or fighting infection. There are several other indicators but only few of them are as important as the body temperature.  Body temperature therefore defines by metaphor what is known as the Key Performance Indicator.  In the study of Chinese medicine, there are other important KPIs which are measured to determine the human body’s condition. Demographically, the KPI is determined by a wide range of considerations, from the standards of measurement for the conditions of the prospective study, and from the background of the subject to the setting of the testing environment. These are all factors that contribute to determining the meaning of the KPIs we observe.

Read More …

How to Gather and Prioritize User Requirements and Functionality for a Minimal Viable Product?

In a previous post we established a working definition of the Minimal Viable Product (Minimum Viable Product) and argued that it is more a process within one’s product development strategy that is supported in different  scenarios, than it is a definition of a goal in itself.

In this post is meant to extend the discussion of development processes that determine the Minimum Viable Product into areas of what functionality to include, as well as what to exclude, when designing your product’s offering.

Read More …

What is a Minimal Viable Product (MVP)?

The term ‘minimal viable product’ is a common buzzword these days in the realm of business start-ups and early stage ventures by product managers and developers who are trying to perfect their product offering.  The Minimal Viable Product (Minimum Viable Product) is actually better defined as a process and not necessarily as a product goal in itself.

A Definition of the Minimal Viable Product (Minimum Viable Product)

The basic definition for the Minimum Viable Product includes those features that allow the product to be deployed within the defined target audience.

Read More …

How can a CTO help me test my product?

Do you know where to begin testing your product?

Usability evaluation of software products and web applications is a growing trend in venture and is proving to be an important need when one is concerned with saving money. It ensures that the product is easy to use and that users have a positive experience. When one is steering a lean start-up through new waters, a usability evaluation can often be an invaluable tool that will saves both time and money.

Read More …