-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As a grantee Pilot user I want to know how to get started in TDP #1691
Comments
Will drive additional dev tix |
@reitermb @stevenino @lfrohlich @ADPennington Please find the mural link and the hackMD pages for review. Happy to walkthrough this as well - we can discuss availability in Wednesday's standup. |
@lilybl1 Just a few comments.
|
left my feedback in hackmds. |
My comments are in hack.md and Mural. Looking really good @lilybl1 ! |
@reitermb @lfrohlich @stevenino Please see below for the comments back and what has been done/completed. @ADPennington I'm working the HackMD feedback next. What are the long term implications? This story is focusing just on the pilot program that is happening in August which is short term. Long term when this scales or after hand-off with OFA, definitely need to setup a OFA affiliated email distribution. The reason we didn't want to send to OFA right now is that according to Alex, that inbox is already pretty full and if grantees reply, that may get lost in the shuffle. Creating a new inbox on the OFA side for long term seems like a launch task item that OFA would coordinate internally. Let's discuss if you had other thoughts here. What happens if they reach out with questions not specific to TDP but data specific? My initial thought is for the short term pilot testing, Miles and I will be manning this inbox and will coordinate with Alex/Lauren if they are questions that we cannot answer. I'm hesitant to add everyone to the distribution because it would be preferred that there's a POC that will be responding each time vs. 5 different people chiming in on an email stream. Thoughts? [Steve] Is the plan to actually send "manual" emails once TDP access is granted? Who will be sending them? From what email address? Will it be confusing if it is different from the introductory email? As we discussed in Backlog, due to the small volume of grantees in pilot testing (~roughly 15ish) we would be starting with manual emails. If we wanted to automate this flow then we would need to prioritize and pick-up story 1336. When we spoke about this during UX Sync it was discussed that Alex or Thomas would then send the email from their own email address. However, if might be cleaner for the short term in pilot to create a spreadsheet of grantees, track who has requested access, granted access and the UX team will manage coordinating with Alex. Then the UX team can send out the email from tdppilot@goraft.tech. This would keep all the email communication cleaner. [Steve] Why does the "Create New LOGIN.GOV account" ask the question of "do you have a LOGIN.GOV account?" since this document is meant to be for people without an account? This was an internal thought bubble – looking to include that in the Knowledge Center potentially This has been removed from the document itself. [Steve] Are there any legal issues with saying "Read and accept the Rules of Use" in step 3 of "Create New LOGIN.GOV account"? It is a required step, but agree we may not need to be so explicit in the statement. Is all of the text in step 5 of "Create New LOGIN.GOV account" actually required? [Miles] Alt text added to HackMD for reference and will need to transfer over to the Knowledge Center page - done [Miles] Welcome Email – add a view lines of content on the pilot program feature set – Done [Lauren] Mural comments – responded and done |
@ADPennington @lfrohlich HackMD comments have been resolved except for 2 items:
|
@ADPennington RE: Existing Login.gov comment -- im pretty sure that someone with an existing account in logingov prod env can use it to log into tdp but we've only been using logingov sandbox env so far which does not recognize existing accounts, so we're asking login.gov support to confirm. -- Did someone get back to you on this? |
login.gov support ticket 442 was created to track our UX-related questions.
cc: @lilybl1 |
from login.gov support :
To be sure, we should test the experience again when we're setup in prod. @lilybl1 |
@ADPennington @lfrohlich Reviewed and updated per discussions. This is moving back into QASP for final review. |
|
|
great. can you add the email address to the
👍🏾 see suggestion above. Also i think there is extra text in here that i think can be dropped since it sounds like a comment as opposed to instructions.
👍🏾 i can approve this ticket once all placeholders in embedded. |
@ADPennington Updated per our post scrum. Please note that we will update the placeholder screenshot with the final version once #1653 is complete. We discussed this would be appropriate for this ticket. |
thanks @lilybl1 👍🏾 this is approved. let's be sure to revisit the placeholder photo before this document is added to the knowledge center. cc: @reitermb @lfrohlich |
Description
Delivers a welcome email for the TDP pilot program. This serves as the first formal step of onboarding–a jumping off point that will prompt the user about what to expect in TDP, how to create an account, and other first steps.
Complements #1653 by delivering getting-started specific content. This content should get a user up and running in TDP, the rest of the onboarding content should take it from there.
AC:
Notes
Things to Consider
Tasks
DD
The text was updated successfully, but these errors were encountered: