311 NYC Noise App
311 NYC Noise App
311 NYC Noise App
Role
Sole Designer
Sole Designer
Tools
Figma, Figma Make
Timeline
1 Week

NYC 311 Noise Reporting is designed to be a simple solution for reporting noise complaints in New York City.
The submission process is frustrating without feedback. The design seeks to address the question of “Is anything even happening?” at each step within the process.
The app is broken down into 2 parts: a place to submit your complaint and a log of your submissions.
The submit part of the app follows the simple framework of What/Where/When/Why/How. It is made of 1. a place to record the noise, 2. a place to locate your sound, and 3. a place to timestamp/describe your sound.
The app is designed to be instrument-like; a simple and satisfying recording device.
The steps to submission are clarified through a progress meter
The list of noise complaint submissions shows the status of received, in progress, or completed.
Each individual noise complaint has a log of the process in progress on the side of 311 internally
The Submission Log part of the app lists your noise complaints and classifies them by status (received, in progress, completed)
NYC 311 Noise Reporting is designed to be a simple solution for reporting noise complaints in New York City.
The submission process is frustrating without feedback. The design seeks to address the question of “Is anything even happening?” at each step within the process.
The app is broken down into 2 parts: a place to submit your complaint and a log of your submissions.
The submit part of the app follows the simple framework of What/Where/When/Why/How. It is made of 1. a place to record the noise, 2. a place to locate your sound, and 3. a place to timestamp/describe your sound.
The app is designed to be instrument-like; a simple and satisfying recording device.
The steps to submission are clarified through a progress meter
The list of noise complaint submissions shows the status of received, in progress, or completed.
Each individual noise complaint has a log of the process in progress on the side of 311 internally
The Submission Log part of the app lists your noise complaints and classifies them by status (received, in progress, completed)
NYC 311 Noise Reporting is designed to be a simple solution for reporting noise complaints in New York City.
The submission process is frustrating without feedback. The design seeks to address the question of “Is anything even happening?” at each step within the process.
The app is broken down into 2 parts: a place to submit your complaint and a log of your submissions.
The submit part of the app follows the simple framework of What/Where/When/Why/How. It is made of 1. a place to record the noise, 2. a place to locate your sound, and 3. a place to timestamp/describe your sound.
The app is designed to be instrument-like; a simple and satisfying recording device.
The steps to submission are clarified through a progress meter
The list of noise complaint submissions shows the status of received, in progress, or completed.
Each individual noise complaint has a log of the process in progress on the side of 311 internally
The Submission Log part of the app lists your noise complaints and classifies them by status (received, in progress, completed)
Background
The problem was presented by the Civic By Design Hackathon for 311 Noise Complaints in New York City
Problem
Submitting noise complaints can feel like a shot in the dark. The user may feel like nothing is happening and ultimately no one is addressing the issue.
Goals
To create an app that provides feedback and information to eliminate the feeling of abandonment and mystery in the 311 submission process. The user should know what is happening.
C. Challenge
How can we relieve the anxiety of the submitting a complaint and help users feel acknowledged and respected in the process?
How can we relieve the anxiety of the submitting a complaint and help users feel acknowledged and respected in the process?
01. Discover
I focused on assessing the competitive landscape for the product and looked at what 311 submissions systems currently exist.
NYC has a 311 complaint system in effect that is fairly simple and straightforward. The organization of it is based on a what, where, when framework which makes it simple enough to understand. However, it doesn't retain a log of submissions or help to show what is happening on the city side.
Various noise logging apps have great systems for recording, plotting the dates, logging, and even generating reports for present to authorities. They have rich visual tools like sound recording interfaces, calendars, and maps.
Dashboards for resolving tickets are a great source of inspiration. Color coding, lists, and filters are a useful framework to draw from.
Competitive Assessment
Various municipalities have implemented 311 systems that incorporate great ideas about logging and submitting complaints. Similarly, noise logging apps have a lot of great features. Dashboards for logging submissions have
01. Discover
I focused on assessing the competitive landscape for the product and looked at what 311 submissions systems currently exist.
NYC has a 311 complaint system in effect that is fairly simple and straightforward. The organization of it is based on a what, where, when framework which makes it simple enough to understand. However, it doesn't retain a log of submissions or help to show what is happening on the city side.
Various noise logging apps have great systems for recording, plotting the dates, logging, and even generating reports for present to authorities. They have rich visual tools like sound recording interfaces, calendars, and maps.
Dashboards for resolving tickets are a great source of inspiration. Color coding, lists, and filters are a useful framework to draw from.
Competitive Assessment
Various municipalities have implemented 311 systems that incorporate great ideas about logging and submitting complaints. Similarly, noise logging apps have a lot of great features. Dashboards for logging submissions have
02. Define
The submission process is frustrating without feedback. The design seeks to address the question of “Is anything even happening?” at each step within the process.
Anxiety is tied with the ambiguity of the process. An input without a response feels like something is broken so transparency, responsiveness, and updates are a defining principle.
02. Define
The submission process is frustrating without feedback. The design seeks to address the question of “Is anything even happening?” at each step within the process.
Anxiety is tied with the ambiguity of the process. An input without a response feels like something is broken so transparency, responsiveness, and updates are a defining principle.
03. Develop
The app is designed to be instrument-like; a simple and satisfying device. Specifically, inspiration comes from sound recording devices.
Anxiety is tied with the ambiguity of the process. An input without a response feels like something is broken so transparency, responsiveness, and updates are a defining principle.
03. Develop
The app is designed to be instrument-like; a simple and satisfying device. Specifically, inspiration comes from sound recording devices.
Anxiety is tied with the ambiguity of the process. An input without a response feels like something is broken so transparency, responsiveness, and updates are a defining principle.
The app is broken down into 2 parts: a place to submit your complaint and a log of your submissions.
The submit part of the app follows the simple framework of What/Where/When/Why/How. It is made of 1. a place to record the noise, 2. a place to locate your sound, and 3. a place to timestamp/describe your sound.
The integration of the progress meter needs to be secondary in presence to the "device" interface. Iterations investigating this idea area shown below:
The app is broken down into 2 parts: a place to submit your complaint and a log of your submissions.
The submit part of the app follows the simple framework of What/Where/When/Why/How. It is made of 1. a place to record the noise, 2. a place to locate your sound, and 3. a place to timestamp/describe your sound.
The integration of the progress meter needs to be secondary in presence to the "device" interface. Iterations investigating this idea area shown below:
04. Deliver
Drawing from successful 311 tools from other municipalities, noise reporting apps, and ticket resolution dashboards serves as a starting point for the design. Ultimately, tuning the design though is focused on clarifying what is happening in the submission process - both in the steps leading up to the submission and after (the submission log).
04. Deliver
Drawing from successful 311 tools from other municipalities, noise reporting apps, and ticket resolution dashboards serves as a starting point for the design. Ultimately, tuning the design though is focused on clarifying what is happening in the submission process - both in the steps leading up to the submission and after (the submission log).
A number of competitive noise complaint apps also had features that could be useful. One such feature is a graphical calendar to help visually plot repeat noise complaints. Another feature is report generation; the ability to output a simple document for legal purposes. This could be another feature to add in the future.
A number of competitive noise complaint apps also had features that could be useful. One such feature is a graphical calendar to help visually plot repeat noise complaints. Another feature is report generation; the ability to output a simple document for legal purposes. This could be another feature to add in the future.




















