How can prototyping help you explore new technologies?

MVP, simple. Hacer productos minimos viables que vayan testeando tecnologias y plataformas, pero por sobre todo audiencias. El mercado será quien nos diga si nuestro desarrollo les gusta o no

This is a big step that often demands a fair amount of cross-team collaboration. Extend yourself grace as you enter this exciting step. Start with a high-level understanding of the technical feasibility and limitations. Refine the understanding as you improve metrics, write requirements, and collect prototype feedback. Remember that there are several frameworks for quantitatively and qualitatively describing technical feasibility and limitations. For example, the pebble, rock, and boulder is a popular option that can be used successfully in different industries and with different products.

Prototyping is often where "the rubber meets the road". Once you can see and interact with something in the way you've envisioned it, you quickly find out what is intuitive, what works and what doesn't. It also gives you a relatively "low stakes" entry into what the completed outcome would look like, where you can pressure test it with internal and external stakeholders.

Users are often the best "inventors/innovators". They often modify a product or use it in a way not originally thought of. Thus, prototype testing with users can lead to new extensions or modifications with increased value.

Observing un-influenced users as they interact with a prototype is one of the most enlightening things you can do when launching a new feature or creating something with a new look and feel. These observations can often surprise you and point to weaknesses that you may not have been aware of. Getting feedback from others is also the fastest way to get a diverse set of observations, and all the different ways that humans may think and interact with your application. This can provide vital insights that can flow into all areas of your application.

Prototypes are one of my go-to tools when reviewing the approach to solutions with internal stakeholders. This is an effective way to gauge whether the proposal will solve the right problems and whether there may be byproducts of the "solution" that are problematic. I've found that we often go through multiple iterations of a prototype before we land on the "right" one that solves the problems in an intuitive and graceful way without introducing unnecessary complexity or other problems.