The document discusses redesigning design processes to focus on design as a service. It advocates for an approach where design is a continuous conversation driven by experiments and feedback from users. Key aspects include enabling others to design through shared understanding and automated processes, designing for learning by exploring uncertainty through experiments, and connecting users and teams through robust feedback loops. The goal is for organizations to serve open communities by making design a widespread ability rather than a phase in the process.
11. 11
_ A process nerd!
_ Variegated professional background.
_ Previously: ThoughtWorks, Edenspiekermann
_ Helped people working in automotive, retail,
large online marketplaces, high-growing start-
ups and public sector.
Matteo Cavucci
@matteomced
12. 12
design as a service
design
infrastructure
Product Team
Production
Environment
Users
co-creation of value driven by experiments
Strategy
feedback feedback
high-level
intents
“design enablers”
feedback
13. stand up if you
develop products
through experiments.
23. designOps
23
A cultural shift in the practice of design and a
related set of practices that allows people
across an organisation to continuously
improve the design of products without
compromising on quality, service coherency,
or team autonomy.
24. designOps
ENABLE OTHERS TO DESIGN
Minimise the effort required by designers - and non
designers - to produce high quality design artefacts.
DESIGN FOR LEARNING
Explore uncertainty through rapid experimentation
and a strategy based on optionality.
CONNECT USERS AND TEAMS
Allow users to guide the ideation process through
robust feedback loops after the product is launched.
33. Design
generation
Weak design are eliminated or combined.
Strong design are further developed.
Further narrowing
and integration
Experiment B
Experiment A
34. The agility of your
product depend on the
agility of your
infrastructure.
40. _ build a shared understanding of the
whole product.
_ avoid detailed specifications.
_ communicate as much high-level intent
is needed to create a stable version.
_ free people to make decisions
aligned with the intent.
_ design the developer experience.
_ automate the design process
as more as possibile.
49. _ We created a feedback form at the end
of the funnel.
_ we printed out all the messages every day, and
we put them on a wall.
_ The whole team read them after the morning
stand-up meeting.
_ We sorted the messages by topic.
_ We tracked how many times a specific topic
appeared and we measured the trend.
51. 51
design as a service
design
infrastructure
Product Team
Production
Environment
Users
co-creation of value driven by experiments
Strategy
feedback feedback
high-level
intents
“design enablers”
feedback
55. Thank you
Matteo Cavucci
Tel Aviv, 06 May 2018 Matteo Cavucci | +49 1514 1298316 | matteo@mced.it
Do you want to know more?
matteo@mced.it
@matteomced