We worked with the some of the vendors on D2D and have a LONG list of lessons learned on outreach/customer service we'd be happy to share. Please hit me up.
With respect to a Veteran Verification use case, we'd actually recommend minimizing (not cutting off) interaction with a vendors after upfront outreach. That is, little outreach after requirements are set and VA dev begins.
One of the lessons learned from the D2D experience is that 3rd parties don't have the bandwidth to interact with VA while kinks in authorization, access management, testing, and documentation get worked out.
One approach to outreach would be to go to market with a functioning Veterans Verification API, to include authorization process, documentation, SDK if deemed necessary, test harness, etc. If you can show them it works out of the box (maybe through a reference implementation), then it will be easier to get them to commit their own dev dollars.
JCQuin
commented
6 years ago
Hiya,
Thanks for posting. Good stuff!
We worked with the some of the vendors on D2D and have a LONG list of lessons learned on outreach/customer service we'd be happy to share. Please hit me up.
With respect to a Veteran Verification use case, we'd actually recommend minimizing (not cutting off) interaction with a vendors after upfront outreach. That is, little outreach after requirements are set and VA dev begins.
One of the lessons learned from the D2D experience is that 3rd parties don't have the bandwidth to interact with VA while kinks in authorization, access management, testing, and documentation get worked out.
One approach to outreach would be to go to market with a functioning Veterans Verification API, to include authorization process, documentation, SDK if deemed necessary, test harness, etc. If you can show them it works out of the box (maybe through a reference implementation), then it will be easier to get them to commit their own dev dollars.
Hope this helps!
Thanks, R/S Joe.