Juan Herrera
Google Developer Expert in Angular & Web Technologies
Development-Driven Design
UXPA Austria
Why we are doing this?
Cross-team Collaboration
π©βπ¨π©βπ»
Problem
π Rewards
π§ Beliefs
What is assumed?
What is encouraged?
+
CULTURE
πΊ
πββοΈ
π§ BELIEFS
The Project
The Team
The Individuals
"We must meet the deadline"
"We must deliver high-quality software"
"We need to reduce the amount of meetings"
"We need to sync more often"
"Bob is the scrum master"
(Spectrum of beliefs)
"Bob is the product owner"
(Common understandings)
π REWARDS
(Incentives)
Acknolwedgement
Acknowledgement
Encouragement
Reminders
Examples
Constantly
By your team lead
During retros
By the seniors
What can YOU do about it?
Components'Nature
βοΈ
1. Technical Spec
Minutes
π Scope - Creativity π
Uncertainty
(design timeline)
Too early
Refactoring
Too late
ONE-TIME COMMUNICATION
CONSTANT COMMUNICATION
Minutes
π Less back and forthΒ π
2. Handout Protocols
Customization Limits
π§
Depends On The Developer
π
"It's not possible" can be replaced with
an estimation
Is it possible?
How long would that take YOU? π
3. Estimation over feasability
π Trade-offs π
4. Proof of Concept
Hours
π Feasibility π
Palette Definition
π¨
π Consistency π
5. Be frugal with colors
Style Guide
π
Palette
Layout
Typographies
Iconography
States
π§ RWD π§
6.Β Β ππ» Consistency
ππ» RulesΒ Β Β
π Better Style Guide π
Why we are doing this?
1. Technical Spec
Minutes
π Scope - Creativity π
Minutes
π Quick QuestionsΒ π
2. Handout Protocol
3. Estimation over feasability
4. Proof of Concept
Hours
π Feasability π
5. Be frugal with colors
π Uniformity π
π Better Style Guide π
6.Β Β ππ» Consistency
ππ» RulesΒ Β Β
7. Cultural Challenges
π Rewards
π§ Beliefs
What is assumed?
What is encouraged?
+
CULTURE
πΊ
πββοΈ
THANK YOU
Juan Herrera | @jdjuan
ππ»
By Juan Herrera