being team [tradecraft]
Post on 11-Aug-2014
3.404 Views
Preview:
DESCRIPTION
TRANSCRIPT
UX TRACK • BEING TEAM • FEBRUARY 2014
BeingTeam
Roles & Rules for Awesome Collaborative Work
UX TRACK • BEING TEAM • FEBRUARY 2014
Envision+Implement
UX TRACK • BEING TEAM • FEBRUARY 2014
we say this...• Silos suck!• Cross-functions rock!• Letʼs collaborate!
UX TRACK • BEING TEAM • FEBRUARY 2014
we do this...but
• Think we know best • Wish “they” would just “work like us”• Call disagreements “politics”
UX TRACK • BEING TEAM • FEBRUARY 2014
we end up...so
• Cranky• Underused• Combative
UX TRACK • BEING TEAM • FEBRUARY 2014
focus only on roles for implementation,
When we
miss out on the unique expertise of each type of thinking.
we...
UX TRACK • BEING TEAM • FEBRUARY 2014
BALANCED TEAMProduct Ownership & Roles
*via Tim McCoy & adapted by Janice Fraser (@luxrco)
*
UX TRACK • BEING TEAM • FEBRUARY 2014
Product Owner
Dev
Dev
Dev
Dev
DevDev
Dev}Restof
theWorld
UX TRACK • BEING TEAM • FEBRUARY 2014
UX
& D
esig
nDev & Eng
•
blah blahblah blah
blah blahblah blah
PRODUCT IDEAS
BALANCED TEAM
Biz/PM
UX TRACK • BEING TEAM • FEBRUARY 2014
Design+ Development
+ Product Management
= 1 product teammind
UX TRACK • BEING TEAM • FEBRUARY 2014
DESIGNEmpathizer-in-ChiefDesign Mind
Understand the customer at an expert level.
Translate high-value needs into product.
Hone the craft.
Key Responsibility
Prioritize customer problems.
Translate insights into tangible design ideas.
UX TRACK • BEING TEAM • FEBRUARY 2014
DEVELOPMENT“Raise high the roof”Development Mind
Envision the best possible solutions based on available technology.
Commit to the outcome.
Key Responsibility
Recommend technologies.
Measure outcomes over time.
•
UX TRACK • BEING TEAM • FEBRUARY 2014
PM & BUSINESSScales of JusticeBusiness Mind
Make fast, concrete decisions despite inadequate evidence and conflicting priorities.
Identify the business value in customer needs.
Key Responsibility
Make the tough calls.
Delegate decisions to the appropriate person.
UX TRACK • BEING TEAM • FEBRUARY 2014
UX
& D
esig
nDev & EngBiz/PM
SHARED RESPONSIBILITY
UX TRACK • BEING TEAM • FEBRUARY 2014
UX
& D
esig
nDev & EngBiz/PM
deciding
10%
SHARED RESPONSIBILITY
UX TRACK • BEING TEAM • FEBRUARY 2014
UX
& D
esig
nDev & EngBiz/PM
understanding& envisioning20%
deciding
10%
SHARED RESPONSIBILITY
UX TRACK • BEING TEAM • FEBRUARY 2014
UX
& D
esig
nDev & EngBiz/PM
executing& evaluating
70%
understanding& envisioning20%
deciding
10%
SHARED RESPONSIBILITY
UX TRACK • BEING TEAM • FEBRUARY 2014
Dedicate 20% time to understanding needs & exploring new & emerging solutions.
make the shift...
by doing this.... Connect implementation priorities to specific user needs; measure outcomes with data.
LUXR.CO AUGUST 2013
This way of working is hard.
UX TRACK • BEING TEAM • FEBRUARY 2014
1 true process1. Define the problem you need to solve.2. Define the as evidence of success.3. Sketch many ideas.4. Collaboratively pick the best bet.5. Prototype it in the simplest, fastest, cheapest way you can.6. Test it with real people.7. Iterate it and test it again.8. Release as often as possible. repeat
�
�
UX TRACK • BEING TEAM • FEBRUARY 2014
Kate Rutter@katerutterhttp://intelleto.com
Perspectives based on personal experience.Balanced Team Model pioneered by Tim McCoy (Pivotal Labs) & adapted by Janice Fraser (Luxr.co)
top related