Tag Archives: Product Development

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 html"}]' tabindex='0' role='link'>User Experience and html"}]' tabindex='0' role='link'>Information Architecture process. It is therefore an important aspect of communicating the product offering to the html"}]' tabindex='0' role='link'>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 …

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 , html"}]' tabindex='0' role='link'>A/B testing and focus groups that will then, in turn, be analyzed along with KPI)" href="http://jumpstartcto.com/defining-your-startup-key-performance-indicator-kpi/">your Key Performance Indicators (KPI’s).

html"}]' tabindex='0' role='link'>Minimum Viable Product" width="600" height="100" class="lazy lazy-hidden alignnone size-full wp-image-833" srcset="" data-srcset="https://d2haskyseezqzi.cloudfront.net/wp-content/uploads/2013/02/gather_requirements600x100.jpg 600w, https://d2haskyseezqzi.cloudfront.net/wp-content/uploads/2013/02/gather_requirements600x100-300x50.jpg 300w" sizes="(max-width: 600px) 100vw, 600px"/>

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 …

How to Develop Your Idea into a Product

The html"}]' tabindex='0' role='link'>Minimal Viable Product

Building your idea into a product requires a process that involves several different modes of expertise and knowledge. Above all, one must have a plan or methodology to follow so that the outcome will meet one’s expectations and more importantly your plan will address what your proposed html"}]' tabindex='0' role='link'>target audience needs.

First and foremost to your plan is the need to focus your idea. This is done by doing comprehensive research and identifying potential competitors, in order to understand what the proposed value of your offering is in comparison to other players within your niche market. Often it may be more difficult to be first player in your market than being in a position among several other players. Despite the fact that being first gives you the advantage, it also means your market is not yet defined and you need to educate your customers in advance on how to use your product.

Read More …