Skip to content
This repository has been archived by the owner on Aug 13, 2024. It is now read-only.

Agenda for week of October 18th 2021 #144

Closed
3 tasks done
Hanastevenson opened this issue Oct 12, 2021 · 4 comments
Closed
3 tasks done

Agenda for week of October 18th 2021 #144

Hanastevenson opened this issue Oct 12, 2021 · 4 comments
Assignees
Labels
feature: agenda meeting notes

Comments

@Hanastevenson
Copy link
Member

Hanastevenson commented Oct 12, 2021

Overview

This issue tracks the agenda for the design systems meetings and weekly roll call for projects.

Please check in on the Roll Call Spreadsheet

Action

@BobbyBishopUX
Copy link
Member

My thoughts as of now:
We may have to consider that this project is too big for us to handle. Maybe even too big for Hack for LA. Maybe Code for America is better able to handle it.
We may need to rethink the project and it's name, as Design System seems to prescribe the solution.
I am thinking that we should consider doing task analysis as a research method.
We could also do experiments with parts of a design system if we have enough of a sample size.
We may also want to look into systems thinking and what that would mean for this project.
We should do more research on the organization of Hack for LA. How are teams structured? Size? How does information flow? Who should we interview that is the most knowledgeable about the system of Hack for LA and the individual projects?

@JeannyRen
Copy link
Member

Please see my comment from the perspective of a newbie.

But on the basis what I have learned the past week I resonate with Bobby's thoughts that he just has expressed. Questions that pop up are things like "What does HfLA exactly want", "what are the HfLA's roadblocks? (and why are these roadblocks for them)", "Is a design system a premature solution for the problem faced", "whose idea was it to come up with a design system in the first place (and when and why did this idea came to light)", and lastly "what is people's sentiment towards reorganization of HfLA?". All such questions touch upon the idea that we are likely to have to invest in getting to know the organization at large. (Like Bobby also mentions in his comment.) And we are likely to have to go beyond the teams, since the teams or development goals will differ over time (I guess). If they are just searching for a method to streamline volunteers and procedures, we have to develop a different solution and it is better to know this now.

With that in mind things like expert interviews will help. Observing how tasks are executed is important as well.

Well, these are my first thoughts. Looking forward to tomorrow's meetings.

@Hanastevenson
Copy link
Member Author

@navarroliuanthony @kevinmoutoucarpin Please could you let me know if you have watched this.

@Hanastevenson
Copy link
Member Author

Meeting notes:

Thoughts and learnings will be shared in the Discussion tab. As a team we will discuss how we wish to collate all the resources from each week.

Next week we shall be discussing #183 and #176

@kelenelee kelenelee removed this from the Velocity milestone Apr 23, 2022
@kelenelee kelenelee removed the ⏳ <6 hrs Size: 1 HfLA week or 1 traditional work day label Apr 23, 2022
@github-project-automation github-project-automation bot moved this to ✅ DONE ✅ in DS: Project Board Aug 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature: agenda meeting notes
Projects
No open projects
Status: ✅ DONE ✅
Development

No branches or pull requests

4 participants