Post on 26-Jan-2015
description
@deanmalmgren @DsAtweet
design and data science
2013 december brighttalk
@deanmalmgren @DsAtweet
design and data science
2013 december brighttalk
@deanmalmgren @DsAtweet
design and data science
innovating with data requires a unique approach
2013 december brighttalk
Through 2015, 85% of Fortune 500 organizations will be unable to exploit big data
for competitive advantage.
@deanmalmgren | bit.ly/design-data
no solutions available?
@deanmalmgren | bit.ly/design-data
no solutions available?successful all, companies are really different
@deanmalmgren | bit.ly/design-data
no solutions available?
Innovation does not come from a product,but from a process.
@deanmalmgren | bit.ly/design-data
design: the process of creating
@deanmalmgren | bit.ly/design-data
design: the process of creating
ideo’s human-centered design
@deanmalmgren | bit.ly/design-data
design: the process of creating
ideo’s human-centered design
eric ries’ lean startup
@deanmalmgren | bit.ly/design-data
design: the process of creating
ideo’s human-centered design
eric ries’ lean startup
agile programming
@deanmalmgren | bit.ly/design-data
design: the process of creating
@deanmalmgren | bit.ly/design-data
unique challenges of designing with data
@deanmalmgren | bit.ly/design-data
unique challenges of designing with datastakeholder naiveté
@deanmalmgren | bit.ly/design-data
unique challenges of designing with datared tape
@deanmalmgren | bit.ly/design-data
unique challenges of designing with dataterminology barriers
@deanmalmgren | bit.ly/design-data
unique challenges of designing with dataunknown need
@deanmalmgren | bit.ly/design-data
unique challenges of designing with datastakeholder alignment
@deanmalmgren | bit.ly/design-data
unique challenges of designing with dataanalysis distrust
@deanmalmgren | bit.ly/design-data
unique challenges of designing with data
analysis distruststakeholder alignmentunknown need
terminology barriersred tapestakeholder naiveté
@deanmalmgren | bit.ly/design-data
lessons learned from designing with dataduct tape and popsicle sticks
@deanmalmgren | bit.ly/design-data
lessons learned from designing with dataduct tape and popsicle sticks
@deanmalmgren | bit.ly/design-data
lessons learned from designing with dataduct tape and popsicle sticks
@deanmalmgren | bit.ly/design-data
stakeholder alignmentunknown need
terminology barriersstakeholder naiveté
lessons learned from designing with dataduct tape and popsicle sticks
@deanmalmgren | bit.ly/design-data
lessons learned from designing with datarapid iteration
@deanmalmgren | bit.ly/design-data
lessons learned from designing with datarapid iteration
!P?GLQRMPK
,W�DOO�VWDUWV�ZLWK�DQ�LGHD��7HFKQLFDOO\��D�ORW�LGHDV��VRPH�WKDW�DUH�FRPSHOOLQJ�DQG�PDQ\�WKDW�DUH�IRUJHWWDEOH�
@deanmalmgren | bit.ly/design-data
lessons learned from designing with datarapid iteration
@deanmalmgren | bit.ly/design-data
lessons learned from designing with datarapid iteration
2ICRAFCQ
(YHQ�PRGHVW�GUDZLQJV�KHOS�IOHVK�RXW�LGHDV�WR�PDNH�WKHP�WDQJLEOH�HQRXJK�WR�JHW�IHHGEDFN�IURP�RWKHUV�
@deanmalmgren | bit.ly/design-data
lessons learned from designing with datarapid iteration
@deanmalmgren | bit.ly/design-data
lessons learned from designing with datarapid iteration
@deanmalmgren | bit.ly/design-data
lessons learned from designing with datarapid iteration
@deanmalmgren | bit.ly/design-data
lessons learned from designing with datarapid iteration
,MAISNQ
%XLOGLQJ�GDVKERDUGV�WDNHV�D�ORW�RI�WLPH�%HIRUH�LPSOHPHQWLQJ��PDNH�VXUH�LW�LV�XVHIXO�
@deanmalmgren | bit.ly/design-data
lessons learned from designing with datarapid iteration
@deanmalmgren | bit.ly/design-data
lessons learned from designing with datarapid iteration
@deanmalmgren | bit.ly/design-data
lessons learned from designing with datarapid iteration
@deanmalmgren | bit.ly/design-data
lessons learned from designing with datarapid iteration
#?QF@M?PB
1R�PRUH�WDON\�WDON\��GR�\�GR�\�
@deanmalmgren | bit.ly/design-data
lessons learned from designing with datarapid iteration
@deanmalmgren | bit.ly/design-data
lessons learned from designing with datarapid iteration
@deanmalmgren | bit.ly/design-data
analysis distruststakeholder alignment
terminology barriers
lessons learned from designing with datarapid iteration
@deanmalmgren | bit.ly/design-data
lessons learned from designing with datasimplicity for starters
@deanmalmgren | bit.ly/design-data
lessons learned from designing with datasimplicity for starters
@deanmalmgren | bit.ly/design-data
analysis distrustunknown need
stakeholder naiveté
lessons learned from designing with datasimplicity for starters
@deanmalmgren | bit.ly/design-data
lessons learned from designing with dataexplain it to your grandmother
@deanmalmgren | bit.ly/design-data
analysis distrust
terminology barriersstakeholder naiveté
lessons learned from designing with dataexplain it to your grandmother
@deanmalmgren | bit.ly/design-data
lessons learned from designing with datasurrogate data is better than none
@deanmalmgren | bit.ly/design-data
lessons learned from designing with datasurrogate data is better than none
@deanmalmgren | bit.ly/design-data
analysis distrustunknown need
red tapestakeholder naiveté
lessons learned from designing with datasurrogate data is better than none
@deanmalmgren | bit.ly/design-data
lessons learned from designing with datatransparency
@deanmalmgren | bit.ly/design-data
lessons learned from designing with datatransparency
@deanmalmgren | bit.ly/design-data
analysis distrust
red tape
lessons learned from designing with datatransparency
@deanmalmgren | bit.ly/design-data
http://bit.ly/design-data !
@deanmalmgren dean.malmgren@datascopeanalytics.com
innovating with data requires a unique approach