Prototype Vs Product

What is the difference between a prototype and a product?

I will try to summarise this based on our experiences and understanding.

When we started building out this product, we did not have access to real data or to real customers. So we did the next next thing.

We stubbed out the data.

We presented the application on NRF, Big Show and received feedback from prospective users.

Prototype#1: No real data and no real customers. Just functionality

We received a real data set form a prospect and started out to develop based on the data set. What we missed out were the real-time scenarios based on the data. We showcased the prototype and received the next set of feedback.

Prototype#2: Real data but not real-time scenarios. Functionality with limited scenarios.

Once we understood the business of the customers and what they do, what they want, we continued building the prototype and now have a product with 2 customers.

Product: A base-lined prototype that handles a basic finite set of scenarios based on the data available and is generic enough to be used by the cross section of users defined for the product.

Comments

My Journey in Inquiry and Advocacy - An experience report

It is recently that I have consciously started practicing Inquiry. Let me explain. I am a consultant who constantly looks at the situation and comes up and implements the solution to progress from there. While I do that, I constantly use Inquiry as a means to progress - one of the key facilitation technique specifically in multiple stakeholder situations.

Principles for developing systems that are anti-fragile

I have been trying to make sense of what anti-fragility means and how do I use that in my day job. As a Business Principal, I tend to work with the abstract but orchestrate a program of work that needs details. This makes my job a little difficult in the terms of designing for more self-preserving systems that preserve the spirit of the abstracted strategy or vision. I came across an article from Daniel Russo on anti-fragility and his attempt at creating a manifesto similar to the manifesto for agile software development. For more reading on Daniel Russo, here is his profile: http://djrusso.github.io More reading from his paper here: https://www.sciencedirect.com/science/article/pii/S1877050916302290 This post is an attempt for me to understand what goes into developing a program that uses every opportunity to strengthen itself and achieve its objective - the vision. I liked the approach of principles for developing systems that are anti-fragile. It i...

User Personas

User Personas are a very good tool for the product owners, business analysts or product managers to be able to co-create with designers. It is predominantly a product of the user research and should not be an amalgamation of demographic data. It is the best way for us to list all scenarios that a persona would take when they want to attain a goal. It is predominantly used to build empathy with user, focus the team and build consensus in a large diverse stakeholder group. The website I referred to is here: https://www.smashingmagazine.com/2014/08/a-closer-look-at-personas-part-1/

Life of a Business Principal in Consulting

Search This Blog