Guideline Creation for PSI writing standards

### Overview
We need to create standardized guidelines for product managers on how to write PSI (Problem, Solution, Impact) statements for projects.

### Action Items
- [ ] Create a standardized guideline for product managers on how to write PSI statements
- [ ] Verify the creation of PSI for the following active projects:
- [ ] Civic Tech Jobs
- [ ] Design Systems
- [ ] Expunge Assist
- [ ] Food Oasis
- [ ] Guides Team
- [ ] Home Unite US
- [ ] TDM Calculator
- [ ] VRMS
- [ ] Website

### Resources/Instructions
Example PSI from 311 data

Problem: The city produces a data set from all the 311 tickets placed. This data is useful if you are a data scientist, but for citizens without this training it has little value.

Solution: We partnered with the Los Angeles Department of Neighborhood Empowerment and LA Neighborhood Councils to co-create and iterate analysis and tools (see 311-Data.org) to provide neighborhoods with actionable information at the local level through real time visualizations and comparison tools.

Impact: Neighborhood Councils are able to use visualizations to demonstrate and discuss the city service levels with constituents and determine where to send mailings to target information to those parts of their community not availing themselves of specific city services.

Taken from [here](https://raw.githubusercontent.com/hackforla/website/gh-pages/_projects/311-data.md)