Chapter 8 Summary Iterate (March 31, 2020)
(I read the final two chapters of the class textbook over spring break. For all intent and purpose, I will add these dot my journal sometime during the respected weeks that the teacher assigns the material)
Chapter Eight is all about the the last of the four stages of UX: the design (and development) , which is all about the details of your product’s design. It is a continuous cycle of design and development that will eventually see the product get finalized and eventually launched. This process is continuous, starting at the highest level with your design problem; then drilling into the details as you work from your prototype, turning it into a developed solution.
I was surprised to learn that even though this is the last stage, one is always following a process of elimination and simplification.
Beta testing is also explored. It helps someone to fine-tune the design, correct any last-minute development and system issues, and gather feedback on a working model of your entire product, allowing you to tweak the details. These groups engage with your product over a lengthy period of time to help you refine your design and technically test your product. It also helps you to identify features that are a hit and those that aren’t without the emotion that might occur with team members or product owners.
The chapter also details UX documentation, which collates a range of best practices for interface design into a reference document. This can also be applied for digital products. Another aspect explored are interaction guides which highly visual documents that describe the design in sufficient detail for another expert to understand and implement.
The final thing the chapter talks about are pre-launch assumptions. These are several factors to consider before a product is launched. These include:
Intrinsic value - try to quickly ascertain what users appear to value about your product.
Possible hurdles - what is limiting uptake or use of different aspects of your product?
Survival of the fittest - are you managing to hold your own against competitors, and offer value beyond them long enough to differentiate your product and thwart attempts at being copied?
Habitual users - what will make customers fall in love with your product, or even become addicted habitual users of it?
Scalability and growth Are there enough people out there who will find value in your product, so that the audience pool will grow over time? Viability of your product Can you leverage the growth of your product’s popularity enough to turn it into a viable and sustainable revenue stream?
It also asks the user to follow it once it’s put out in the public sphere, as a way of measuring it to see what works and what doesn’t (which could always be put towards a later updated version.
Those are all my notes on the assigned reading. Now to apply those to both my projects: the class will present their group project when our Zoom school class resumes next week
I was surprised to learn that even though this is the last stage, one is always following a process of elimination and simplification.
Beta testing is also explored. It helps someone to fine-tune the design, correct any last-minute development and system issues, and gather feedback on a working model of your entire product, allowing you to tweak the details. These groups engage with your product over a lengthy period of time to help you refine your design and technically test your product. It also helps you to identify features that are a hit and those that aren’t without the emotion that might occur with team members or product owners.
The chapter also details UX documentation, which collates a range of best practices for interface design into a reference document. This can also be applied for digital products. Another aspect explored are interaction guides which highly visual documents that describe the design in sufficient detail for another expert to understand and implement.
The final thing the chapter talks about are pre-launch assumptions. These are several factors to consider before a product is launched. These include:
Intrinsic value - try to quickly ascertain what users appear to value about your product.
Possible hurdles - what is limiting uptake or use of different aspects of your product?
Survival of the fittest - are you managing to hold your own against competitors, and offer value beyond them long enough to differentiate your product and thwart attempts at being copied?
Habitual users - what will make customers fall in love with your product, or even become addicted habitual users of it?
Scalability and growth Are there enough people out there who will find value in your product, so that the audience pool will grow over time? Viability of your product Can you leverage the growth of your product’s popularity enough to turn it into a viable and sustainable revenue stream?
It also asks the user to follow it once it’s put out in the public sphere, as a way of measuring it to see what works and what doesn’t (which could always be put towards a later updated version.
Those are all my notes on the assigned reading. Now to apply those to both my projects: the class will present their group project when our Zoom school class resumes next week
Comments
Post a Comment