The document discusses how to incorporate Apple-like design principles into products through an agile process called inception. It recommends conducting inception workshops to understand user needs, define personas, map tasks and stories, and create high-level designs in a collaborative and time-boxed manner. The goal is to focus on desirability and get feedback early without large upfront designs, in order to develop products that are simple, useful and delightful for users.
Appkodes Tinder Clone Script with Customisable Solutions.pptx
Incorporate Apple-like Design into Products
1. How do I incorporate Apple like design into my products? Michael Walkden VP Product Delivery Pathfinder Development LLC www.pathf.com April 2, 2011 Product Camp Chicago (c) Copyright 2011 Pathfinder Development LLC. www.pathf.com DEVELOPMENT
6. As computing technology moves toward mobile devices, we’ve seen the 1990s’ growth in processor speed taper off and product development become less about horsepower [and more] about the overall design of the product. ... a healthier view of human intelligence ... ... that it is reactive, responsive, sensitive, nimble. Brian Christian, The Atlantic March 2011
22. send annotations load in plans in pdf format annotate plans with text aggregate annotations arrange plans into projects annotate with photos manage site visits within a project support jpeg as well as pdf plans search for a plan by title search for a plan using meta data access past projects upload files via email upload files via iTunes upload files via a virtual plan room m m m m m m add color to annotations separate documents into pages display PDF table of contents M M M X X 3 weeks 6 weeks 15 weeks
23. Architect in office, preparing for site visit captured site observations and emailed them load pdf plans on iPad for the site go to site launch iPad app find the plan for this particular inspection inspect site create annotations Finish inspection Connect iPad to network Generate annotations summary and send via email find site plans for site review annotations
24.
25. The _____________ helps _____________ to _________________________ (product, feature) (target audience) (receive a benefit) Problem__________________________________________________________________________________________________________________________________________ The Story Solution__________________________________________________________________________________________________________________________________________ Desired Action __________________________________ Picture Caption ________________________________________________ Construction Obs. App architects/contractors carry whole plan libary to site and record and email observations without extra paperwork Architects often bring the wrong drawings to a site inspection and must reenter and can lose notes taken on yellow pads at a site The iPad punch list puts all the plans at the architects fingertips, gets rid of re-entry and insures notes are not lost Architect watches video demo and is offered link to app store touch an object to annotate, DONE button takes you back
26. Business Objectives What does success look like from a business perspective? Users Who are the primary users of this product? User Objectives Why do users want this product? What do they expect from it? Brand Characteristics How do we want customers to perceive the brand? Value Propositions What value does this product offer to the consumer? Key Differentiators What does this product offer that no one else can? Measures of Success How will we know we've been successful? Are there any key performance indicators?
27. Ken Mitchell Responsible for Gig events, responsible for Gig staff, wants to sell out events, likes the service, likes innovators, staff prints thermal tickets (Box Office Manager, The Gig)
35. Inception A short period of hard collaborative work; to better understand project objectives, identify potential users, and define high level functional scope so that size of the project can be roughly estimated and an incremental release strategy can be identified
42. Traditional analysis: Exhaustively evaluate each level before moving on Agile recognizes that: Clarity is an iterative process… The levels interact...
43. Traditional analysis: Exhaustively elaborate each level before moving on Agile process strives to: Do just enough to move down...you can always go back Get to market and realize return on investment
48. Inception HypothesisTest ResultsPersonasUsability TestingUser StoriesClarityCohesiveFocus on getting started There is Only One Team - Just different roles Design + Development + Testing + Project Management + Product Management
49. Agile Delivery Velocity Iterations Continuos Deployment User Stories Testing Lean UXD Wireframes Comp Prototyping User Behavior Analytics Usability Testing Product Focus Customer Development Funnels Sign-ups Analytics Constant Innovation There is Only One Team - Just different roles Design + Development + Testing + Project Management + Product Management Rapid Cycles Focus on desirability of end product