What would happen if we would bring design, front end, back end etc. all together? How could we improve the user-flows by thinking of alternative, non-happy flows? What would happen to the performance and therefore the user-experience when back end is already involved before the finalised wireframes are handed over?!
That's all nice and dandy. But we do need to deal with some concerns like:
- Knowledge gap: How can the different disciplines with their specialty understand each other and come to conclusions?
- Shared responsibilities: Where do start and where do they end?
- Efficiency: What would it do to the efficiency of the team when they get different tasks?
In this talk we’ll try to address and hopefully take away those concerns and focus on the benefits it will bring, working in a hybride team.
4. @de_gijt@nerdculture.de ∙ Co-creating with UX and Software
- Simon Sinek
“ People don’t buy what you do,
they buy WHY you do it.
And what you do simply proves what you believe.”
12. Co-creating with UX and Software
Team structures
Operations teams
Process teams
Feature teams
Project teams
Permanent.
Focused on the IT ecosystem.
Permanent.
Focused on a specific business process.
Permanent.
Focused on a specific function / service.
Temporary.
Focused on a single or group of releases.
13. Co-creating with UX and Software
“We don’t understand each other. We have di
ff
erent vocabularies”
“We are already in too many meetings”
“So now I will be responsible of making the design?”
“I tune out when they start talking about their part of the process”
“I don’t get paid to do this work”
“I can’t guarantee the quality of my work when I need to deliver 100 things at the same time”
“We have roles for a reason right?
Does everybody need to own the same skill set?”
23. Co-creating with UX and Software
Explore
Event storming
Command
Triggers
Event Resources
Condition
Order
process
was
started
Order
was
submitted
Start order
process
from
basket
Submit
the entire
order
Customer
Time
Condition
Aggregate
24. Co-creating with UX and Software
Explore
Command
Triggers
Event Resources
Condition
Aggregate
Event storming
38. Co-creating with UX and Software
Key take aways
What do we want you to take away from our presentation today?
Look at your team and team structure from the why.
Talented individuals != a successful team.
Incorporate design into your development cycle.
Responsibility of the end product lies with the team.
Responsibility for speci
fi
c steps in the cycle belong to a discipline.
Trust your team members.
Find a language / tool that both design + development understand.
Give proper attention to the OPS cycle.
39. Co-creating with UX and Software
Tips + resources
• Start with Why, How Great Leaders Inspire Everyone to Take Action - Simon Sinek
• https://www.nngroup.com/articles/design-thinking/
• https://freshservice.com/it-team
• https://sequencediagram.org/instructions.html
• https://www.tutorialspoint.com/uml/index.htm
• https://www.boldare.com/blog/event-storming-guide/#event-storming-basics-how-
does-it-work?-event-storming-guide
• https://geek
fl
are.com/about-uml-diagram-and-tools/
40. Thanks for your attention!
Slidedeck:
Co-creating with UX and Software
