Read on Twitter
1/ A thread on product #design leadership within non-tech organisations.
When a design team within a complex organisation becomes more mature (e.g. team scales, increasing amount of products, ...) there are a lot of challenges:
When a design team within a complex organisation becomes more mature (e.g. team scales, increasing amount of products, ...) there are a lot of challenges:
2/ Setting the standard design process:
A larger team means that people have different ways of solving problems. Trying to align and streamline the methods used can improve the communication outside the design team greatly.
A larger team means that people have different ways of solving problems. Trying to align and streamline the methods used can improve the communication outside the design team greatly.
3/ Debriefing user research to stakeholders outside of design:
Great user research has a lot of insights which go beyond #UX. When design isn't greatly positioned within an organisation, it can be rough getting insights to others and seeing that they are acted on.
Great user research has a lot of insights which go beyond #UX. When design isn't greatly positioned within an organisation, it can be rough getting insights to others and seeing that they are acted on.
4/ Maturing the design system:
Getting a design system which is up-to-date, in which processes are in place (e.g. to change key components) are tricky as the org becomes larger.
Getting a design system which is up-to-date, in which processes are in place (e.g. to change key components) are tricky as the org becomes larger.
5/ Making the design system matter beyond the design team:
In large orgs, it's often not just a design team who contributes to the creation of UI. Developers or external partners (agencies, freelancers, ...) need to be in the loop.
In large orgs, it's often not just a design team who contributes to the creation of UI. Developers or external partners (agencies, freelancers, ...) need to be in the loop.
6/ Handling accessibility:
WCAG and co are tricky beasts. As much as it's a design implementation problem, it's equally a process problem. You don't want to fix accessibility after - you want to handle it while working on features/products.
WCAG and co are tricky beasts. As much as it's a design implementation problem, it's equally a process problem. You don't want to fix accessibility after - you want to handle it while working on features/products.
7/ Taking documentation seriously:
This remains a tricky one. What is the right level of documentation? How do you make sure that people effectively do document their work?
This remains a tricky one. What is the right level of documentation? How do you make sure that people effectively do document their work?
