You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PM reviews invoice, request more info from contractor, accepts invoice, access dashboard, receive communication/notification
Finance 1 reviews invoice, request more info from PM, accepts invoice, access dashboard, receive communication/notification
There are a good amount of folks available morning and afternoon CEST time zone, including our senior accountant/finance 1 user.
If this is feasible for you, could you please send me a template email with the parameters? I will then email my coworkers to initiate a meeting request for you, and cc you on the email.
Let me know your proposed methodology. One focus group with many PMs, one separate session for finance. Or 1:1 sessions with 2-3 PM individually. length of each session. I could also create accounts for staff to access the test instance if needed.
The text was updated successfully, but these errors were encountered:
Internal docs here: https://www.notion.so/simplysecure/Usability-Testing-April-May-2022-53bd40d8e22f42438d125fe6bc0d43dc
Original email here:
Example workflows for usability review:
PM reviews invoice, request more info from contractor, accepts invoice, access dashboard, receive communication/notification
Finance 1 reviews invoice, request more info from PM, accepts invoice, access dashboard, receive communication/notification
There are a good amount of folks available morning and afternoon CEST time zone, including our senior accountant/finance 1 user.
If this is feasible for you, could you please send me a template email with the parameters? I will then email my coworkers to initiate a meeting request for you, and cc you on the email.
Let me know your proposed methodology. One focus group with many PMs, one separate session for finance. Or 1:1 sessions with 2-3 PM individually. length of each session. I could also create accounts for staff to access the test instance if needed.
The text was updated successfully, but these errors were encountered: