3 ms·
In my experience even things which are explicitly prototypes can be dangerous, as it can appear to be in the short term interest of the business to take a proto
by jrs95 8y ago
In my experience even things which are explicitly prototypes can be dangerous, as it can appear to be in the short term interest of the business to take a prototype and modify it as little as possible to get it shipped. I've seen this result in massive headaches and thousands of wasted man hours, and for what? Shipping an "MVP" that can't be effectively iterated on 2 weeks sooner? The worst case of this I saw, the technical aspects of this were bad enough that it was (in my opinion) what caused the product to fail.
- sethammons 8y agoIf you go the prototype route, it is critical that management knows that it is an exploration and no running code will result from it - just knowledge. I am a super big fan of prototypes in my domain. They take under a week usually. We use them to crack the hardest nuts on an upcoming project and usually learn something(s) very valuable that guide the design of the v1 product/solution. Usually these are the learnings we would not have gotten to until mid-way or more in a real project, but we can prototype it, preventing all the potential rework.