CCH Feature Prioritization High Priority Hitlist Research
This is a starting point to gather the potential most desirable features of the CCH.
Starting sources are internal staff experience and recollections from interactions with customers.
Customer validation will be forthcoming.
Related pages: Current Product Feature Prioritization
Does exist things they can’t live without
Feature | Benefit | Benefit Customer Confirmation | Risks | Comments |
---|---|---|---|---|
AD Lists |
|
|
|
|
Builds |
|
|
|
|
Compare |
|
|
|
|
API Integration with GRC partners |
|
|
|
|
Attestation Portal |
|
|
| JH: why is this important? what is evidence customers using it?
|
The benefit customer confirmation numbers are current as of 9/30/23
Doesn’t Exist
Feature | Risks | Benefit |
---|---|---|
See Citations tied to Common Controls | Could expose tenious mapping/older mapping practice or highlight weaknesses in the mapping. | Would allow customers to see the nuance of each Citation, i.e. are there specific time frames, etc. |
See only associated Common Controls in a List in the CCH | If we didn’t keep control parentage, could lose some context. | Would allow customers to to view pertinent information quicker. |
Better AD Search Capabilities | N/A | Would allow customers to find the products they need quicker and more reliably, which could increase customer onboarding and retention. |
New Version Notification | If the mapping team is slow to map new versions, this could highlight a weakness in our internal processes. | Would provide customers the latest and greatest information about ADs. |
Clear indication of AD versions in UI | If the mapping team is slow to map new versions, this could highlight a weakness in our internal processes. | Would provide customers and mapping team clarity on AD history. For customers easier to find the AD version they care about. |