Write copy for 311 Data Story

[bberhane]

Overview

We need to write up a script detailing the 311 Data story so we can feature it on the About page, where past and prospective stakeholders can understand what led up to relaunch.

Action Items

• [x] Identify/research the Google Drive to find documents that can give us a grasp of the history of the project
• [x] Create an outline
  • [x] invited reps to in-person sessions (we can use pictures of whiteboards in gdrive),
  • [ ] talk about nature of neighborhood involvement changed to zoom mtgs
  • [x] talk about 311-Data site wasn't as accessible and prompted us to do user research
  • [x] talk about need to make data and code accessible as free datavis wrappers around public datasets
• [ ] Gather blurbs from team leads
  • [ ] dev can speak on making data/code more accessible
  • [ ] Design can comment on improvements to accessibility
  • [ ] Research can talk about what we've been learning about from usability tests
• [x] Write up script
• [ ] Get Bonnie's stamp of approval
• [ ] Hand off to UX/UI Design to develop visuals

Resources/Instructions

• Draft 311 Data Story Google Doc
• Story of 311 Drive Folder
• Interview notes

[ryanfchase]

@bberhane shall we add as sub-action items the points outlined by Bonnie in THAT PM meeting comment? (edited to turn the second part into action-items/sub action-items)

E.g.

• [ ] Create an outline
  • [ ] invited reps to in-person sessions (we can use pictures of whiteboards in gdrive),
  • [ ] talk about nature of neighborhood involvement changed to zoom mtgs
  • [ ] talk about 311-Data site wasn't as accessible and prompted us to do user research
  • [ ] talk about need to make data and code accessible as free datavis wrappers around public datasets

I can imagine that we'd need to reach out to members of other teams for more info on some of these... So perhaps we should add these action items too:

• [ ] Gather notes from team leads
  • [ ] dev can speak on making data/code more accessible
  • [ ] Design can comment on improvements to accessibility
  • [ ] Research can talk about what we've been learning about from usability tests

[ryanfchase]

Updated action items after reviewing it as a team in PM meeting

[ExperimentsInHonesty]

@bberhane Uploaded both recordings 311 Data History Interview - this recording is to be kept confidential, only the timeline is required, and it has to be approved by bonnie

[ExperimentsInHonesty]

• @bberhane I mentioned we made a tool that was a csv download. Here is a one-pager about the project. There might be a more current version of that document https://github.com/hackforla/311-data/issues/576, so poke around in the drive for it.

[bberhane]

@ExperimentsInHonesty Interviews have been removed from the drive and thank you for the One-Pager! I'll rummage through the drive for any updated versions.

[bberhane]

@ExperimentsInHonesty It looks like you uploaded part 1 in the part 2 folder. Can you upload part 2?

[bberhane]

Here's an initial draft of the story: 311 Data Story Draft

It has yet to incorporate the note about neighborhood involvement, and will ask Bonnie for part 2 during PM meeting

[ryanfchase]

Hi @bberhane,

IIRC we are waiting on Bonnie to make time with us to close this out. Let us know if this is the case, otherwise provide the usual update info:

• updated ETA
• progress from the last week (if applicable)
• availability for communications during the week

TY!

[bberhane]

Awaiting Bonnie's review

[ExperimentsInHonesty]

We have to figure out where this goes in the history and how we want to represent it. I also have pictures from the event.

As part of the process that we did with the NCs to determine what they wanted, we had an in person Design Thinking workshop. Out of it came a variety of items they were interested in. At one point we had sticky notes, which we transferred to a GitHub board with cards and now that GitHub is no longer supporting cards, we have moved the info to a spreadsheet Project Board Cards: 311-data: 20200414 - NC Workshop Board.

What the 20200414 - NC Workshop Board looked like prior to migration

[bberhane]

@Joy-Truex, @ryanfchase, @rrhea22, @brianmonroetherapy If you guys and your teams could jot down a few bullet points speaking to the design updates and successes from this past year about the website, that would be greatly appreciated.

[bberhane]

Spreadsheet is from post-first version, remind Bonnie to upload images and data from the event that happened

[ryanfchase]

I've created this document to track each team's blurbs: 311 Data: Highlights and Wins of 2024

[ryanfchase]

Some notes from Bonnie

• Dev section is too technical, but we should keep it in case it belongs in a different document/report
• Need timeline, Bonnie to confirm timeline is correct (w/ John Ritchey)
• Need to add Headings (so that table of contents works)
• Need to add a "Why Zero Cost"
  • talk about challenge of scalability and sustainability of nonprofit
  • we need a transitional section on why we need zero cost
  • nonprofit lacks institutional funding/support, but we have lots of labor power
  • dont want project to be a burden on organization -- typically an org will spend lots of money each month on a project, only for it to "lose steam" and then become a drain on resources. so its better to start with sustainability in mind, rather than going heavy on costly infrastructure

[cottonchristopher]

Hi @bberhane, Please leave a comment with the following items:

• updated ETA:
• progress from the last week (if applicable):
• availability for communications during the week:

Thank you so much

[ryanfchase]

I am posting this here so we can provide a link to the draft and/or the wiki:

Screenshot of the old dashboard

[Joy-Truex]

@bberhane @ryanfchase should I start an outline for the about page and we can insert the finalized copy as it comes in? Do we have a general idea for the outline?

[ryanfchase]

I've moved this to In Review, I will be following up with Bonnie on 1/8/25. @Joy-Truex I will ask to see if we can start drafting up UXUI tickets.

[ryanfchase]

@bberhane @ryanfchase should I start an outline for the about page and we can insert the finalized copy as it comes in? Do we have a general idea for the outline?

FYI Bonnie has asked we wait until all the content is provided in the draft. All that's left to do is add my findings from the old PM's email account (completed last weekend), and Bonnie will review our last iteration on Monday!

[ryanfchase]

Todo for this evening:

• [ ] review: https://github.com/hackforla/311-data/issues/1898
• [ ] come up with a new draft for Bonnie to review, Monday Feb 3, @ 3pm

[ryanfchase]

Updates from last week

• [X] completed review of ALL tickets since the beginning of the repo
  • I am using this to verify the approximate time the 311 Data team hit their various milestones throughout the year. I have access to info like:
    • when did Design start working on V2 accessibility?
    • when did Engineering add certain features? Which v1 features became feature requirements?
    • when did Product begin reaching out to DONE, when were certain workshops scheduled?
• [ ] We had a look at Bonnie's emails that pertained to conversations in 2019
  • [ ] ⚠ this section is WIP, i'd like to provide a summary of those additions ⚠

My objectives for this week:

• [ ] Begin compiling notes into a document (or tab): 311 Data Timeline, we'll focus on getting the facts and events first, then we can focus on tackling the Content (see: recruiting new UX Content Writer)
  • The Timeline should come from the following sources
    • PM Lead Gmail correspondence (between 2019 and 2020)
    • Bonnie's Gmail correspondence (between 2019 and 2020)
    • Summary of entire 311 Data tickets (from 2019 to present)
    • Research Roadmaps and Research Plans (from ~2020 to present)
    • Other documents available in the drive

[ryanfchase]

ETA: 2025-02-12 Blockers: none

[cottonchristopher]

404. That’s an error. The requested URL was not found on this server. That’s all we know. (for the following link: Story of 311 Drive Folder )

[ryanfchase]

Moving this back to prioritized backlog to work on higher priority tickets -- however the work completed by PMs on this ticket is should go on the Timeline page for Story of 311

• https://github.com/hackforla/311-data/issues/1845
  • List for consideration, PM accomplishment tickets: https://github.com/hackforla/311-data/issues/1845#issuecomment-2629148027

[ExperimentsInHonesty]

Meeting Prep

During the meeting:

Use the stakeholder register for the 311 project.

And the document: XXXXXX (don't include anything that is already covered)

Use the start date minus a month 2019-06-05 to search bonnie@hackforla emails for relevant 311 timeline information.

• 2019
• 2020
• 2021
• 2022

If you find any email addresses missing from the 311 spreadsheet, add them to the spreadsheet.

[ryanfchase]

Link to markdown file with merged timeline (first draft... i may try to refine this and take the best version)

• https://drive.google.com/file/d/1n4JAoGhWZehy_aUQfcKdW48HW-ZBULBx/view?usp=drive_link

[ryanfchase]

We converted that markdown into a google docs so the team could edit

• https://docs.google.com/document/d/1xYkW1T4F5b55YQnRJSlMXC-rwvP3u8RGbBlA9GlebXg/edit?tab=t.0

[cottonchristopher]

Hello, I was reviewing the stakeholder register: stakeholder Register- 311 Data Project

• new columns list: Invited to 8/20 (2025) and Attended 8/20 (2025). Is this correct or should this be from year 2020? or some other year?

update from Ryan:

• we determined it should be 8/20/2020
• closing as resolved

[danagfleming]

Hey @ryanfchase! Checking in on progress re: 1Password Vault creation. Have some time to get to work on this whenever the vault is set up. Thanks :-)