Write copy explaining "brief overview" question on Wins form

[cwvivianlin]

Overview

Based on the Wins submission research findings, users are confused about what is expected in the "brief overview" question on p.4 of the Win submission form. Users would like word count suggestions, and additional guidelines on what we want them to write.

Action Items

• Review research presentation: https://docs.google.com/presentation/d/1RU80s0ep8azGb7V3IUQ3N-8dDmzQH7oV1nn8q_peTUY/edit#slide=id.p

User quote:
“Not sure what this one is exactly asking for, a brief overview of what? I think that would be better if they gives me more specific guideline.”

• Review analysis board: https://drive.google.com/drive/u/0/folders/1DQMLMmorazeKM3b1W-eZQZAV0GcIbRF2

• Write a short copy that would provide guidance on what is expected in the “brief overview” question (p.4 of form). Include word count. Since there is already a long checklist of potential wins to celebrate, the explanation could be along the lines of "tell us more about the Win you selected, etc." The copy would be placed in the description right under the question:

Resources/Instructions

Wins submission research Wiki: https://github.com/hackforla/website/wiki/Wins-submission-process-research

Is there a dependency?

Yes

If Yes, please explain

Development to include the new copy.

[github-actions]

Hi @cwvivianlin.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:
Size, Role, Feature

NOTE: Please ignore the adding proper labels comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards.
To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Milestone" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels