311 Data Product Planning Monthly Agenda 2025

[ryanfchase]

Overview

This issue tracks meeting agendas for the monthly Product Planning meeting for 311 Data in 2025

Agenda Quick-links

Agenda Template

## YYYY-MM-DD - 311 Data Product Planning
_[Back to Top](#)_

### AGENDA
_Timezones listed as Pacific Time._

- [ ] 7:00PM _5 min_ - Check-in & announcements
- [ ] 7:05PM _30 min_ - agenda_item_1
- [ ] 7:35PM _5 min_ - agenda_item_2
- [ ] 7:55PM _15 min_ - Q/A + Discussion

### Topic requests/questions:

### Notes:

### Action Items:

### Resources/Instructions


---
### Attendees (PMs + Leads):

- [ ] Ryan
- [ ] Cotton
- [ ] Bonnie

[ryanfchase]

• Previous agenda available here: 311 Data Product Planning Monthly Agenda #1528

[ryanfchase]

2024-02-05- 311 Data Product Planning

Back to Top

AGENDA

Timezones listed as Pacific Time.

• 7:00PM 5 min - Check-in & announcements
• 7:05PM 30 min - agenda_item_1
• 7:35PM 5 min - agenda_item_2
• 7:55PM 15 min - Q/A + Discussion

Topic requests/questions:

1. Users have a hard time knowing if an area is within an NC boundary:

• Referenced by Research insights
  • '24 Aug Action Steps Spreadsheet
  • '24 Aug Usability Test Presentation
• Addressed by a couple of similar issues
  • UXD - Clarify regions that are not part of LA city on Map #1305
  • Bug Report: Map Contains Areas With Data But Can't Be Selected #1861
  • DEV - Darken parts of the map that you can't interact with #1585
• My commentary:
  • No NC selected, start with darkened map: UXD - Clarify regions that are not part of LA city on Map #1305 (comment)
  • We can incorporate park boundaries and style them so they don't overlap with NC boundaries: UXD - Clarify regions that are not part of LA city on Map #1305 (comment)
  • I observe that when an NC is selected, we make EVERYTHING outside the selected NC the same shade of blue, only distinguishable on-hover IF that area is a NC

Reupload of 1305 darkened map comment

When an NC is selected, the surrounding area is all blue

everything-turned-blue.mp4

Re-upload of "unselectable areas" in bug report ticket

2. 2025 Dataset is live

If they have not been addressed, I will start listing tickets here whose priority has been significantly lowered now that we don't need to communicate to users about a lack of data.

Resources

• MyLA311 Service Request Data 2025

3. How Are We Display Data At Launch?

• I need us all to acknowledge that we are moving forward with Blank Map as pre-launch
  • Bonnie has urged us several times to prioritize this, since users with limited bandwidth are unable to use the application
  • Blank map is a launching point for us to utilize smaller and more surgical API requests
• WHEN is the data going be loaded? How much?
  • Once all filter criteria is filled out? Does that include filtering by NC? Currently, selecting an NC results in a map fly, which would not suggest to the user that they are in the middle of filling out the Search and Filters modal "form"
• If we are requiring ALL filters to be active, how do our multi-select filters work?
  • Picking multiple SR category types may yield a much larger data payload, mainly Bulky Items and Illegal Dumping
  • Are we still going to allow SR Status "ALL"? Status "CLOSED" tends to be smaller for recent dates, and significantly larger for older dates.
• Will we be caching data?
  • updates to our in-memory database allow us to store non-contiguous data-points for all available years.
  • Should we keep it for faster load times on-load? Or toss the data so that the browser remains nimble?

Related Tickets and Comments

• Epic: Prevent Map Crashing and Reduce Page Load Time #1890
• UXD: Blank Map On Page Load #1848 (comment)
• UXD - Design System Updates: Request Type Icons #1629 (comment)

4. Reminders on Board Workflow*

• Questions column (SUMMARIZED HERE)
  • Only move tickets here when they are blocked until they receive input from PMs or another lead
  • You MUST utilize the correct Ready For label in order to signal a lead for input. That lead MUST remove the Ready For label after they provide an answer. Not sure if the conversation is resolved? Apply the Ready For label for the lead who asked the original question.
  • Per discussion with design lead...
    • Designers should mostly leave their tickets as "In-Progress" while they are continuing to iterate and receive feedback
    • When tickets are ready for dev handoff, please move to "Questions" with ready for dev lead. Dev lead will close the ticket when dev ticket has been produced
• I'm noticing more conversation between leads. This is appreciated, but extended conversations are making it difficult to scan through tickets. My recommendations:
  • Ensure ALL outstanding questions are concisely listed as the bottom-most comment in a list
  • Consider moving more general questions to our Questions ticket: Get Your Team Questions Answered Here #1878
  • Use the Emergent Requests tickets to create proposals and invite discussion for product or other teams: Emergent Request Issue Template
  • Consider adding the question to an upcoming meeting. All are welcome to add to the Thursday PM meeting agenda to function as ad-hoc lead meetings

Notes:

Action Items:

Resources/Instructions

---

Attendees (PMs + Leads):

• Ryan
• Cotton
• Tracy
• Joy
• Audreen
• Peter

[traycn]

Requesting to add the topic of Kanban board statuses to the agenda.

Question:
When are tickets meant to go into the following statuses: Questions and In-Review.

-Please provide a description, ticket requirements, and labels that would generally be shown in each status. Thanks!

[ryanfchase]

Going to make an ER and add it to agenda:

• Emergent Request: Consider making pins clickable
  • Update styling of service request details modal 1870 #1906 (review)
  • DEV - Update styling of the Service Request details modal #1870 (comment)

[ryanfchase]

Another item for the agenda...

• todo item: Epic of Epics: Pre-Launch and Post-Launch Assessment #1862 (comment)
• Related:
  • Nov '23 Bonnie list: 311 Data Weekly PM Meeting Agenda  #1546 (comment)
  • Epic of Epics tx: Make 2 Epics for Pre-Launch Issues (For Bonnie) #1619