以下黑色字体内容来自Luke Wroblewski,紫色字体部分来自Zoe观察和建议：

    Issue Business approach How to collaborate Design approach
    Problem solving approach Definitive. Relies on equations for “proof” <-
    Deliver best efforts that can satisfy designer selves first before team sharing    		 Iterative. Relies on a “build to think” process dependent on trial and error.
    ->
    accept pootential iterations and do the analysis again each iteration
    validation through what customer say: often a combinatioon of qualitative(focus groups) and quantitative(surveys) research <-
    keep intense communication with customers and talk to them to understand more, not just observe behaviors but also understand business motivations and task restrictions    		 what customers do: often direct observation and usability testing
    ->
    understand “what people say” doesn’t equal to “what people actually need”. Analyze further based on given theory.
    informed by market analysis and aggregate consumer behavior <-
    careful validation of assumption    		 direct consumer observation and abductive reasoning(what might be)反向推导
    ->
    deeper motivation analysis
    completed completion oof strategy phase marks the start of product development phase <-
    set reasonable deadlines for each iteration, and map achievement into specifical goals/measurements    		 never: continually evolving with customers
    ->
    small waterfalls amongest big agile cycle
    focused on an understanding of the results of customer activities an understanding of customer activitiies.
    tools used too communicate strategic vision spreadsheets and powerpoint decks <-
    understand how spreadsheets works and organized content in the form of standard ppt for better dissemination    		 prototypes, files, and scenarios
    ->
    more intuitive data visualization
    described through words(often open to interpretation) <-
    stronger verbal explanation and presenation    		 pictoriial representations and direct experiences with prototypes
    ->
    listen more before talk
    team members veritcal expertise and individual responsibilities “T-shaped” expertise: a principle vertical skill and a horizontal set of secondard skills. Collaborative (team) responsibilitiies.
    work patterns permanent jobs, on-going tasks, and fixed hours tempooary projects with assoociated tasks and flexible hours


    reward structure

    corporate recognition based on the bottom line    		 <-
    engage more actively and scale designer’s influence, eg collate best efforts to educate other team members

    peer recognitioin based on the quality of solutions.