How OASIS+ compares to Legacy OASIS

[vickimcfadden]

• As a buyer, I need to understand the key differences between legacy OASIS and OASIS+, so that I can plan my acquisition strategy accordingly.

• As a prospective supplier, I need to understand the key differences between legacy OASIS and OASIS+, so that I can determine if OASIS+ supports my business strategy and I can prepare my offer (when OASIS+ reopens) accordingly.

• Content

• Design

Status

• [x] Content created
• [x] Content reviewed by SD
• [x] Content reviewed by SME
• [x] Design finalized
• [x] Content finalized
• [x] Page developed

[vickimcfadden]

@ekidenda @PowderD do y'all want to populate the user story here? The format is linked in the card, as a [some type of user], i need [to understand / do something], so that [I have some outcome]!

[vickimcfadden]

Decisions:

• Have content in table top-aligned.
• Left-align content in all the table headers.

[mark-meyer]

@klohman This is ready for your eyes: https://federalist-76c8d2ee-2655-47f7-8fa4-63811842d0a5.sites.pages.cloud.gov/preview/gsa/oasis-plus/mmeyer/about-oasis-compares/about/oasis-plus-comparison/

[klohman]

@mark-meyer One content change (and @rosamundtgov I updated in the content doc); we want to make the header row "OASIS legacy" instead of just "OASIS"

Other than that it's ready from my side.

[mark-meyer]

Hi @ekidenda — this is merged in now and ready for review: https://federalist-76c8d2ee-2655-47f7-8fa4-63811842d0a5.sites.pages.cloud.gov/site/gsa/oasis-plus/about/oasis-plus-comparison/

[ekidenda]

@mark-meyer and @rosamundtgov - Noticed the reference to 'family of contracts' applied to OASIS rather than OASIS+ as consistent with language in other parts of the webpage. I suggested a minor revision of the first sentence accordingly on the content doc. Thanks.

[rosamundtgov]

Updated in the copy doc and in Github

@mark-meyer: https://github.com/GSA/oasis-plus/pull/181

[vickimcfadden]

@ekidenda ready for your review

[ekidenda]

This page generally looks good, but when reading it, seems as though the section under the header: "OASIS+ will continues to:" represents 'similarities' between the contracts. In reading further, the table presents both similarities and differences in a random manner and it is confusing / difficult to follow. Perhaps one option could be to organize the content in two buckets one being 'similarities' and the other 'differences' will make it clear and easier to consume.

[rosamundtgov]

@ekidenda We have this as an item for post-MVP. Let us know if the priority has changed.

[ekidenda]

@rosamundtgov the comparison matrix seems like information new entrants (awarded contractors and customers) will find useful. If the page is confusing, do we want to launch it as-is and potentially cause confusion?

I reviewed everything in the ready for PSHC Q&A and provided feedback. My understanding is if the page isn't done, move it back. If done, move it forward. Let me know if I might have missed something...? thanks.

[rosamundtgov]

@ekidenda Your process re: moving the items backwards or forwards is correct. I'll meet with the team about this and let you know when we have an update.

[vickimcfadden]

For MVP, maybe we launch the page as-is, and then post-MVP we can work on a redesign? For now, let's stick to content changes.

[vickimcfadden]

Moving this to done. We'll address design / content changes in a new card in post-MVP