Meeting minutes
<Daniel> Date: February 9, 2021
<Daniel> https://
Scribe/eoncins
Designer modules outline -- overall structure and contents
Daniel: First outline for structure and contents for the next curricula. We are about to publish the developer modules. Next module is for designers
… before getting to specifics I would like to gather things people are missing.
David: Module titles are very developer oriented. Module 2 talks about mark-up.
… it seems to me we want to make it more designers oriented. Also there is a missing use of colours...
Carlos: I felt almost exactly like David. Too developer oriented. I don't think a designer will recognise this topics as they are described. Learning outcomes present the same problem...
… All modules are focused on the outcome of the design process. No modules present an approach to make sure to test involving users.
Shadi: Do you have examples on thinks to consider in the design process?
<sloandr> +1 to Carlos on the benefits of covering the design process, in addition to design output
Carlos: In the design process you need to make sure to involve users also to gather a requirements listing. This allow higher fidelity prototypes...
… it should not be just to select which widget you are trying to use.
Carlos: I would call this UX design. Starting with personas.
Carlos: These modules look like they are at the end of the line and I think this needs to start earlier.
Daniel: We might want to approach not only the personas but also user requirements.
Daniel: I do acknowledge the use of colours also addressing visual design.
Shadi: User research needs to be reflected.
Gerhard: What could be done is participatory design. If the designers are aware of user involvement it is important.
… Sometimes the problem in involving people is the budget.
Sarah: I agree with everybody. We have an opportunity to flag best practices. I will be planting seeds for people coming the first time.
Daniel: I am hearing the need to work on a structure less developed centred and also stress the need of involving user and address visual design.
less developer-centric.
David: I really like the start. I think is really important for designers to make sure they identify their responsabilities but in some cases they will not be responsible for their implementation.
Sign-posting designer and developer shared responsibilities
Daniel: We have quite a developer-centric approach (editor's bias). I will try to make sure to correct this...
… designers need to recognise a mark-up even if it is not part of their responsibility, also accessibility roles and names.
Roberto: I was going through the language and actually the person responsible for providing requirements are accessibility engineers...
… the designer is not the person dealing with html.
… accessibility is like a translator in the way we do it.
Daniel: I guess that even if there is an accessibility engineer this could also fall in the design aspects. We could approach both roles.
Shadi: Two thoughts I think we have a broad spectrum we have visual designers, UX designers, so we have to be careful on how to approach and communicate the modules.
… visual designers might need issues more related to colours while UX researchers will need other issues...
… there also a slight differentiation between knowing how and knowing why. So we need to be careful with the wording that it is not too technical.
… so we need to a) consider the different audiences and b) how we communicate the information.
Daniel: I agree that we have to use a proper wording and get clear. I will try to work on these aspects.
David: Encouraging annotation in a non technical is very important. Make clear that designers understand the language used in the curriculum.
Daniel: Any further comments or suggestions?
Covering visual design and UX design
Daniel: Linked to what Shadi was suggesting before on how to communicate. In this curricula a sequential approach might not work as in the developer curricula...
… would people be in favour of approaching the curricula based on the different designer roles we have been discussing?
David: I would favour this approach. Plus one for subcategories.
+1
Howard: I just wanted to plus one...
<CarlosD> +1
Howard: which topics in the UX will you take into consideration?
Daniel: The first would be to introduce user design and researcher related to disabilities, make sure also to cover personas and maybe gathering requirements through surveys.
Daniel: The third roles would be: visual designer (colour/spacing and how elements are identified), UX Design (technical aspects) and the third will be UX researcher
Carlos: Now is clear.
<CarlosD> +1 to David's suggestion
David: For me the first group would be visual design, second group interaction design and third group UX research.
<RPerez> Where in that structure would we address anotations for developers for things such as text equivalents?
Daniel: First visual design more related to visuals, second interaction design more related to developers and third UX design or research more related to gathering requirements and making sure peoples with disabilities are involved
Roberto: Where in that structure would we address anotations for developers for things such as text equivalents?
Daniel: I think that this would follow under interaction design, as they will be dealing with these aspects.
Roberto: Maybe also cross mention between the different roles could be made.
+1 to the third roles proposed
FYIs
Daniel: Developers modules survey was closed yesterday and a new survey has been opened about the overview page of the whole curricula...
… I encourage everybody to complete the survey.
… I will be sending a reminder later on this week.
<shadi> https://
I hope to have an updated outline so we can start work on the module titles of the different roles that we mentioned today.
<RPerez> Thanks everyone for the nice introductions and for welcoming me.