CWS-CARES Public Library

As part of the holistic design process, Core Constituents have been participating in prototype demonstrations and giving feedback to improve the user experience. During Prototype Demonstrations, Core constituents review prototypes, or pre-build designs of CWS-CARES, that represent system functionality. Then they provide early feedback on user experience, navigation, and screen actions before the designs go into development. ​

These demonstrations typically begin with contextual information or a scenario, and then presenters show how a user would navigate through the system. The facilitators also allow time for feedback, and participants can ask to revisit items or ask questions. Occasionally, the discussion uncovers differences in procedures or preferences among counties.​ Core Constituents can enter their feedback in Microsoft Teams using a form or ask questions during the demonstrations (the team tracks these items as well).​

What are prototypes?​

• Prototypes are designs of CWS-CARES built in Salesforce to represent system functionality, where the presenter can showcase the screens during the demonstration. ​

• Prototypes illustrate the user experience, navigation, and screen actions viewers can expect to see in CWS-CARES. ​

• Prototypes give Core Constituents an opportunity to provide early feedback on user experience, navigation, and screen actions before the screens go into development. 

Will the prototype demonstrations be recorded so that folks can revisit the content later? ​

Yes, the sessions will be recorded and shared via the Microsoft Teams Channel. Recordings will be available for 3 business days. ​

Is the Microsoft Teams Channel feedback form the only avenue to provide feedback? ​

During the prototype sessions, feedback that is given live and in the chat is captured by our team which is then added to the feedback log. Outside of this, the feedback log in the Microsoft Teams Channel is the only avenue to provide feedback. Core Constituents will have additional opportunities to provide feedback in future project phases, including build demonstrations, user feedback, and Extended User Scenario Testing (EUST).​

Will Core Constituents have access to the feedback log and the decisions/categorizations made about feedback?​

Yes, Core Constituents will be able to see not only the feedback provided and the decisions made regarding it, but also a list of feedback and decisions that other participants have provided as well. ​

Are we expected to submit feedback through the form if we've already given it verbally during the live demonstration?​

The PaaS SI Team will ensure any verbal and chat-entered feedback provided during the call will also be recorded and documented in the feedback log. Participants are also welcome to use the feedback form provided during the session to provide comprehensive feedback during the demonstration.​

How long will I have to provide feedback after the prototype demonstration?​

The feedback form in the Microsoft Teams Channel will be open for 3 business days after the ​demonstration. ​

Can I show the recorded demonstration to others in my county, gather their feedback, and provide it to you via the feedback form on the Microsoft Teams Channel?​

We encourage you to invite others in your county to attend and participate in the demonstrations. However, the feedback form will be open for 3 days after the session to gather any offline feedback county users want to share. We request that Core Constituents gather and consolidate all additional feedback and enter it into the feedback form on the Microsoft Teams Channel.​

My county has been designated as a Core Constituent for a Service Area I'm not very familiar with. Will there be opportunities for me to be included as a Core Constituent in other Service Areas that I have more experience with? ​

Counties have been designated to serve as Core Constituents for different Service Areas by recommendation from the County Welfare Director’s Association (CWDA). Up to this point in the CWS-CARES Project, we've used those Service Area designations to solicit input from Core Constituents. What Core Constituents will see moving forward in holistic design is a greater emphasis on getting input across Service Areas. For example, all Core Constituents are invited to provide feedback on the upcoming prototype demonstrations. It's not limited to just Core Constituents designated to those Service Areas. We encourage Core Constituents to forward these sessions to colleagues at their organizations with additional expertise.