Libérer Télécharger Creative Selection: Inside Apples Design Process During the Golden Age of Steve Jobs – Libérerwebdesing.com
Ply involved the senior leaders were on a weekly basis with engaging in depth with the product during these demosThe nature of these meetings also looked so different from traditional exec meeting topics with discussions around market opportunity competitors resourcing etc They were instead fundamentally about the design and user experience And each leader would play with the product themselves just as a user would to really connect with the product experienceEually important to their process was extreme product dogfooding which they called living on the product They understood that even after making initial product decisions in these demo reviews they needed to continue to experience the product on a daily basis to ensure the experience was actually satisfying And in doing so they would continually come up with feedback from amongst the team who was living on the product and incorporate that feedback into the product Ken shares how each change he made to the keyboard auto correction capabilities would be rolled out to the small team of iPhone software engineers and how the feedback directly from those individuals shaped his future iterations I do regularly see a disconnect in product uality emerge when the product design and engineering teams aren t using their own product on a daily basisAnd finally the teams tasked with owning critical software components were very small empowered teams of individuals Each component would have a DRI a directly responsible individual who was ultimately on the line for producing that component And there was a fundamental belief that small teams did the best work because they were empowered to do so Ken was the DRI for the iPhone keyboard and worked directly and close 1 It d be tempting to have played up the Steve Jobs angle throughout but the author doesn t do that he admits that Jobs wouldn t have been able to pick him out in a small crowd2 There aren t many business related books about the work of an individual contributor which makes it refreshing the activity was the day to day work and output2a This meant he could tell the story of Apple s culture and influences without trying to be the center of the story3 A large part of the story is about a specific problem to solve the iPhone keyboard and how it was overcome but the story was able to zoom out as well and talk about design in general4 There isn t a lot of ego he talks about who helped him mistakes along the way etc This is the real deal written by an insider I was also there during that time This book accurately describes Apple s software engineering during the second Steve Jobs era For hardware engineering read Adam Lashinsky s Inside AppleThe vivid descriptions in the book are better than the analyses I would stress that the principles and practices described by the author were completely unwritten and unnamed as the author says So if ou re trying to be like Apple by reading a book The Fall Of White City (Victorian Chicago Mystery Series Book 1) you re doing it wrong Ifou want to be like Apple ditch the business books and startup blogs do ou think Steve Jobs read those things and really focus on the product There s nothing in the book about MVP Agile Scrum AB testing TDD etc Apple really didn t work like that The key is what the author calls creative selection demoingdogfoodingiteratingconverging the product with tight loops of communication with minimal teams enforced by secrecyOne thing that occurred to me is that the examples given and generally in Apple s history are ones where the product definitions were relatively well formed and concrete up front leaving plenty of room for technical innovation but little room for exploration and business validation Before getting to that concrete vision the Apple way isn t applicable. Risis and collaboration illuminating each with lessons learned over his Apple career He introduces the essential elements of innovationinspiration collaboration craft diligence decisiveness taste and empathyand uses these as a lens through which to understand productive work cultureAn insiders tale of creativity and innovation at Apple Creative Selection shows readers how a small group of people developed an evolutionary design model and how they used this methodology to make groundbreaking and intuitive software which countless millions use every day.
free download Creative Selection: Inside Apples Design Process During the Golden Age of Steve Jobs
Gives concrete examples of how he used all the Cs throughout his illustrious career designing and developing products many of us use every day While I purchased both the Kindle and Audible version of this book I must recommend the Audible version since Kocienda provides his own voice as the reader In addition to his talent as an author he clearly has a talent as a voiceover artist as I feel his voiced account of his story added another important dimension I was excited about diving in this weekend into Creative Selection by Ken Kocienda a new book providing a detailed look inside the design process at Apple And Creative Selection did not disappoint While much has been written about Steve Jobs and Apple I found Creative Selection particularly insightful because it provided a vignette into the development of the first iPhone and in particular one of it s most critical features the keyboard from the perspective of Ken Kocienda the software engineer ultimately responsible for developing it Ken goes through the many challenges and subseuent iterations to address those challenges with building the first keyboard to be presented only on a glass display And in doing so it showcased how Apple s design and development process was different from traditional Silicon Valley companies in subtle et incredibly important waysKen distills the Apple development approach that ultimately made them successful to seven elements inspiration collaboration craft diligence decisiveness taste and empathy And he walks through what each of these elements means to him with detailed stories exemplifying eachBut I wanted to share some personal observations I took away from the book on how Apple built products in such a fundamentally different wayKen describes the process by which they would prepare product demos for their own team and then for various leaders use that demo as the primary avenue for feedback and then continue to iterate to the next demo followed by rounds of demo feedback and so on He calls this process creative selection While at the surface this may sound like a typical product review process that many companies have there was so much that was different about itFirst demos were done early and often even at the prototype stage These were not just reviews at the end of the process to get final approval but instead they were done to show early progress determine viability of the project and make fundamental design decisions The goal was to produce an initial prototype to demo as uickly as possible and then continually refine the prototype through subseuent feedback sessions These demo sessions with senior leaders happened on a weekly basis not months apartAnd in contrast to so many classic reviews where leaders are largely concerned with ensuring projects are on time that there are no unaddressed bottlenecks and that the team is executing on the right strategy leaders at Apple in fact played the role of arbiters of taste Ken defines taste as developing a refined sense of judgment and finding the balance that produces a pleasing and integrated whole And in these reviews leaders would often be making calls on the spot on design decisions for the product Ken retells the story of many reviews with Scott Forstall who was head of iPhone software and Steve Jobs himself who would make critical decisions to remove UI elements to pick amongst a few design directions that the team was presenting and to cancel efforts entirely all based on the context and feedback they got from the presenting team their own first hand experience with the demo and their ultimate sense of taste This feedback was highly respected by the team and didn t feel like classic executive swoop ins because of how dee. Ars he was on the ground floor of the company as a specialist directly responsible for experimenting with novel user interface concepts and writing powerful easy to use software for products including the iPhone the iPad and the Safari web browser His stories explain the symbiotic relationship between software and product development for those who have never dreamed of programming a computer and reveal what it was like to work on the cutting edge of technology at one of the worlds most admired companiesKocienda shares moments of struggle and success
This book appears like a journal recounting the development of some projects at Apple rather than an insightful book about how to best approach product design design processes It relies too much on self indulging memory walk that are often void of true learning Feels like the author wanted to remember the fond MTIV year at Apple developing some of its software leaving us with some very unsurprising unsophisticated learning from how things are actually happening I really enjoyed this book as someone who works in software development and is trying to build products that users love Ken s accounts of Apple s principles and the creative selection process is not just fascinating to read about but can also be applied toour own work I also geeked out over the iterative journey to decide the iPhone autocorrect algorithm or to decide what the size of an icon should beThis book is a window into how Apple built and continues to build incredible products that seamlessly mould into people s lives I highly recommend An insight into the meticulous detail of developing great software while recognising the human element of interactionTyping this on an iPad keyboard brings a tangible link to the material in the book Excellent This is not a book for International Organizations you ifou re looking for dirt or stories on Steve Jobs but is exactly what Laurus you re looking for to get an insight into the processes that resulted in some of the most iconic products Apple produce Primarily the Safari web browser and the iOS keyboard Who would have thought a keyboard design could be so convoluted and so interestingA gripping read Highly recommended for anyone interested in Apple history I pre ordered this book based on some extremely positive reviews but I found it to be something of a disappointment Whatever Mr Kocienda s other skills his prose style is lifeless and flat Given that he is describing one of the most significant technology developments of the last ten or soears his account lacks excitement and oddly passion In describing the work he did at Apple and the way her perceives the company to work he writes as a programmer rather than a story teller Along the way he includes rather jarring links to the work of people like Kant and Darwin and sometimes the value of these references is so limited as to encourage the belief that they have been added to give some artificial weight to the author s own text This faux intellectualism also leads to some incredibly clumsy phrasing For example he talks repeatedly about a refined like response a combination of words the meaning of which is only made less clear by the inclusion of the hyphen As another example he states that The past is a source of the timeless and enduring which sounds excellent right up to the point that Silk and Steel you try to understand what he means Ultimately there are a few interesting insights that the book offers into the way that Apple works but these are rare enough not to redeem it I listened intently to this book from two perspectives as a long time userfan of Apple products and as a leader of a school district s technology department The book was was interesting informative and enjoyable though both lenses personally and professionally Kocienda provides a fascinating view into the process of design at Apple and gives a perspective from the inside rarely told He effectively takes the readerlistener through the idea stages into the design process and to the shipped product all while explaining intricate details and telling interesting stories along the way In education we often tell our students and teachers about the importance of using the 4 Cs creativity collaboration communication and critical thinking to prepare our students for the world Kocienda. WALL STREET JOURNAL BESTSELLER An insiders account of Apples creative process during the goldenears of Steve JobsHundreds of millions of people use Apple products every day; several thousand work on Apples campus in Cupertino California; but only a handful sit at the drawing board Creative Selection recounts the life of one of the few who worked behind the scenes a highly respected software engineer who worked in the final Het Reservaat Van Ward Ruyslinck years of the Steve Jobs erathe Golden Age of Apple Ken Kocienda offers an inside look at Apples creative process For fifteene.
Libérer Télécharger Creative Selection: Inside Apples Design Process During the Golden Age of Steve Jobs – Libérerwebdesing.com
Ken Kocienda was a software engineer and designer at Apple for over fifteen years After graduating from Yale with a degree in history he fixed motorcycles in Arizona worked in the editorial library of a newspaper in New York taught English in Japan and made fine art photographs in all those places Eventually he discovered the internet taught himself computer programming and made his way through a succession of dot com era startups before landing at Apple in 2001 where he worked on the software teams that created the Safari web browser iPhone iPad and Apple Watch Ken lives in San Jose California with his wife