TDM: Design Lead Tasks

[thetanmancan]

Overview

Create a weekly list of action items that the design leads need to address.

Details

Problem: Design leads have a list of action items siloed in their own personal documents. This leads to:

• Inefficient coordination of work tasks between leads and others on the design team because time must be taken to communicate the tasks either via Slack or Zoom meetings
• Tasks getting lost when a lead is unavailable or leaves the project because others on the design team don't have access to the lead's documentation
• The rest of the TDM team not understanding the type or quantity of work that design leads do because they have no way to track it

Solution: Use a GitHub issue to create a weekly list of tasks that the design leads need to address. This leads to:

• Better coordination efforts between design team members
• Others on the team being able to cover a task when a lead can't complete it
• Transparency to the wider TDM team

Not all tasks will be able to be completed within the span of a week. Incomplete tasks will be copied over to the next week.

Tasks can be organized into a general pool, which then can be pulled into a specific lead's section based on their availability.

Template

## [Friday Date – Thursday Date]

### Task Pool
- [ ] 

### Tristan


### Marlena

[thetanmancan]

2025-02-28 – 2025-03-06

Task Pool

• Convert the tasks listed in this comment/issue into individual issues.
• Wikis
  • Create an EPIC parent issue for Update Design Wiki Page: Documentation #1310 to track all wiki updates.
    • Hide Bonnie's comment in Update Design Wiki Page: Documentation #1310 once this has been resolved.
  • Finish writing the UX Lead Protocols wiki.
  • Create a wiki that explains how to onboard and offboard team members.
  • Create a wiki for what designers need to have done by Monday night.
    • Include progress update template.
  • Create a wiki for what designers need to have done on Wednesday night.
    • They need to take notes on feedback and post that feedback in a comment on their issue. They need a template for that.
    • Move their issue from Visual Review or Questions/Clarifications over to In Progress or Done.
  • Create a wiki that explains how to decide which issue to work on.
  • General project questions with answers that would be helpful to other team members should be asked in Get your Team Questions Answered here #1938, issue-specific questions should be asked in the comments of an issue, and any other questions should be asked via Slack or during a meeting.
    • In Get your Team Questions Answered here #1938, one question should be asked per comment so that they can be individually referenced in response comments and can be closed as resolved. Also, each question should be numbered.
  • In the Open an Issue wiki and probably in the action items section of the design issue template, include an action item for designers to add a slide to the Staging Deck for their newly-written issue.
  • Designers need to include the related handoff issue number at the bottom of the design issue description once they close it.
  • Make a “how to use devtools” resource for our site audits.
  • Add a page for how to write a bug.
  • Add a page about how to edit an issue template.
  • Add information from Get your Team Questions Answered here #1938 that is wiki-relevant.
  • Add that any comment within an issue that is no longer relevant should be closed as resolved.
  • Everything should be documented by an assignee in the GitHub. A brain dump to accommodate for the bus factor. All necessary information should be included that would allow someone else to jump in, know what’s going on with the issue, and then continue working on it.
  • Pull requests need to be associated with an issue.
• Make a design issue template. Include action items from the Design: Open an Issue and Design: Close an Issue wikis.
• Make a handoff issue template. Ask dev if they approve of the handoff issue template.
  • Ask John and developers if they can please make reference to the Figma files so that the specifications of the mockups are accurately implemented rather than guessing off of screenshots.
• Draft language for Submit Snapshot page popovers and non content #2010
  • Determine if Design messages for empty Submit Snapshot tables #2009 and Design popovers for the Submit Snapshot tables #2019 are enough to accomodate all the changes described in Draft language for Submit Snapshot page popovers and non content #2010. If not, write new issues.
  • Does Bonnie's comment in Design popovers for the Submit Snapshot tables #2019 apply to Design messages for empty Submit Snapshot tables #2009 too?
  • We will make a new issue to have clicking on the link to the snapshot go to page 5 regardless of ownership. Find out from John if he wrote this.
  • Only people who own the snapshot can see the prior pages (1-4)
• Make sure changes made to Design: Create Style Guide Presentation (Radio Buttons/Checkboxes) #1839 are used to update the Figma design system.
• Create new issue to answer these questions related to Design Snapshot Admin and Audit Log pages #1953:
  • Will the submitter be able to see the updates of their application data, or is that information only viewable to admins?
  • Will the submitter be notified of a change in their application’s status?
  • Does any of the information from the Snapshot Admin page need to be reflected on the Submit Snapshot or My Projects or Save Summary pages for the submitter?
• New issue: Write instructions on how to change people’s permissions as a security admin. These instructions will be added to the Admin Guide.
• Add Angela Liao’s question to Get your Team Questions Answered here #1938: What do the project statuses mean, namely “project,” “draft,” and “snapshot”?
• Create two issues that create dependencies for Add Submit button to Final summary, Page 5 of the Calculation Wizard. #1656
  • One for the “You have not reached the target points” modal, which should be informational and included as part of Implement changes to INFORMATION modals to match style guide #1986
  • One that’s for a design update of the button styling on Page 5.
• Take Design: Update Submit Snapshot tables #2004 and Design: Update the table on the Feedback page #2008 out of the icebox after Design System: Consistency between table headers #2013 has been resolved.
• Once Design a "Ready to Submit" modal #2031 is finished, update the Changes to TDM Modals List document with it.
• Make sure John entered an issue for not being logged in but still having the link to the Submit Snapshot page in the navigation bar.
• Need to include the fact that we only allow Material Design 3 icons in our system.
• Propose a new Figma template to make design presentations easier for leads and to understand changes when looking at Figma files in the future. Spreadsheet design.
• Design Snapshot Admin and Audit Log pages #1953
  • Add "Level" column to the right of the Certificate of Occupancy Date column in the description and mockups for Design Snapshot Admin and Audit Log pages #1953.
  • Stakeholders asked that the "Monitoring" column be removed.
  • Will stakeholders provide an update to including language that explains all of the Approval Status values?
  • Add a Download CSV button which downloads the summary of all the snapshots on the Snapshot Admin page.
• Rewrite Bug: Parking Provided / Baseline field displays non-whole numbers #2052 to reflect that the defect should be that only up to seven numerical digits should be allowed in the Parking Provided field.
• Add implied action items from Nami's comment to the list of action items in Design System: Consistency between table headers #2013.
  • Make sure these changes are included in the Figma design system.
• Make a design issue and see if it can get Material Design 3 icons for the radio buttons and checkboxes implemented.
  • Need a handoff issue to handle using Material Design 3 icons and sizes.
  • Make sure both issues differentiate themselves from Design: Create Style Guide Presentation (Radio Buttons/Checkboxes) #1839 and Implement style changes to input controls #2111, which handle coloring rather than specific icon usage.
  • Make sure the design issue mentions that the design system needs to be updated.
• Write an issue asking stakeholders about how payment will be taken care of in the TDM system.
• If it has not already been addressed by an issue created from Site Audit: Check Create Project page 2 for visual design consistency #1955, write an issue addressing the lack of color contrast between text and the background color in the disabled buttons in our design system.
• Enter bugs from TDM: Track Bugs to be Written by the Design Team #2135 as issues.
• Create an issue to standardize the focus state of input fields between browsers.
  • Make sure the issue mentions that the design system and style guide need to be updated
• Write a design issue to create mockups with alternative wording for 'Reset Project' on Page 2 when a user has a saved project.
• Create an issue to review and update modals.
  • Make sure the google doc gets updated
• Review Design different icon sizes on the My Projects page #2054 before closing it.
• New issue: Create a copy of the TDM Modals List.
  • Do an audit of the site and include any modals in the list that are not there.
  • Include only mockups of the updated designs, not what they looked like before.
  • Include steps on how to reproduce that modal on the Dev site.
• New issue: Experiment with naming "Reset Project" to something else if the project has already been saved. We have had several users confused into thinking that it meant it would wipe all the data in the project when in actuality all it does it clear all unsaved data from the project. Therefore, we should change the name of the link/button so that people aren't misled into thinking the functionality is something that it isn't.
• New issue: Can we create a workflow where the Save Project button can work on the first page? Right now, a project can't be saved without including data in the Parking Provided field that is on Page 3. This is because the Parking Provided field partly determines what level the project is. Does the project level need to be determined before saving? What is the minimum amount of data needed before a project can appear on the My Projects page?
• New development issue: Apply a maximum width of 2096 px to all pages other than the My Projects page.
• On the Feedback page, will the copy for the "Would you like your comment to also be delivered to the website team?" field be changed once the regulation is live? If so, what should the copy be changed to? Need to ask this to the product team. We already searched the p-feature: Feedback tag and couldn't find an issue that was written to address this question.

Tristan

• Onboard/offboard
  • Onboard Ancy.
    • Needs to have her acceptance confirmed on 1Password.
    • Make sure she’s had the rest of the process taken care of via Onboard & Offboard: UI/UX #1618.
  • Offboard Serena.
    • Make sure she’s had the rest of the process taken care of via Onboard & Offboard: UI/UX #1618.
• Get your Team Questions Answered here #1938 (comment))
  • Make comments that provide the answers that Bonnie gave to my questions from this meeting.
  • For questions that didn't get answered, set up a meeting with Bonnie.
• Create an issue for the application withdrawal slide on the stakeholder deck.
• Review Design: Page 5/Save Summary with a level 0 project #2112 before removing the Draft label.
• Update Google Calendar to reflect Design's 6:00 PM meeting time on Wednesdays.
• On March 5th, clean up Design: Draft admin FAQ instructions and placement on menu #1726's comments and issue description and reassign it to someone else or place it in the Prioritized Backlog at the top of the list.

Marlena

• Write a design issue to address the fact that some warning modals have a red icon but a green primary button, and that those clashing colors give mixed messages. The design team already brought this up as an issue and so has John.
• Write a design issue to address the following problems with drop shadows for the buttons in our design system:
  • The Google Slides Style Guide Presentation does not make mention of drop shadow color for any of the button states.
  • The Google Slides Style Guide Presentation's hover state drop shadow specifications have an incorrect Y-Offset number.
  • The Google Slides Style Guide Presentation does not list any drop shadow specifications for disabled buttons.
  • In the Figma design system page, the tertiary button's hover state drop shadow color is inconsistent with all other buttons.
• Need a new issue to remove the orange "warning" color from our design system and to do an audit of the dev site to make sure it isn't appearing anywhere.