mirror of
https://github.com/cisagov/manage.get.gov.git
synced 2025-07-24 03:30:50 +02:00
Update product_strategy.md (#140)
* Update product_strategy.md * Update product_strategy.md Sounds good - I updated the problem statement a little to reflect the CISA side of it. I added CISA and the note about the ability to "secure" a domain. * Update product_strategy.md @h-m-f-t split them - not in love with this framing, but wanted to get some of your thoughts!
This commit is contained in:
parent
36148cf6d7
commit
a31e385727
1 changed files with 6 additions and 8 deletions
|
@ -2,7 +2,9 @@
|
|||
Purpose: Clarify our focus for developing a new .gov TLD system and align it to the needs of its users, CISA's mission and standards, and the vision for the .gov program.
|
||||
|
||||
## Product Vision
|
||||
_TBD - once we synthesize initial research and align as a product team_
|
||||
|
||||
CISA intends to create a modern, user-centered, responsive web application to enable .gov registrants to manage their domain’s registration lifecycle, DNS settings, and useful supporting services. The registrar should be the central .gov hub for CISA, supporting registrant management and tracking technical performance indicators for the TLD. For CISA and registrants, the registrar should help generate insights into the security of an organization’s internet-accessible systems.
|
||||
|
||||
|
||||
## Primary, Secondary, Tertiary Users
|
||||
### Primary:
|
||||
|
@ -12,7 +14,9 @@ _TBD - once we synthesize initial research and align as a product team_
|
|||
|
||||
|
||||
## Problem Statements
|
||||
_TBD - once we synthesize initial research and prioritize areas of need_
|
||||
U.S.-based government organizations and publicly controlled entities lack a clear, usable, and efficient way to apply, register, and a .gov domain and related infrastructure in order to build public trust of their website and communications.
|
||||
|
||||
CISA lacks a scalable, efficient, and secure method of managing the outreach and operations of .gov TLD program in order to facilitate government agencies building public trust of their website and communications.
|
||||
|
||||
## Short-term Success for .gov
|
||||
* A production-ready, modern .gov registrar that can replace the current system with improved user experience and operational efficiency
|
||||
|
@ -25,12 +29,6 @@ _TBD - once we synthesize initial research and prioritize areas of need_
|
|||
* Develop services to support “the security, privacy, reliability, accessibility, and speed of registered .gov internet domains” (DOTGOV ACT)
|
||||
* Sustainable long-term skills and capacity to scale up the program
|
||||
|
||||
## Problems .gov system needs to solve (now)
|
||||
_TBD - once we synthesize initial research and align as a product team_
|
||||
|
||||
## Problems .gov system doesn’t need to solve (next or later)
|
||||
_TBD - once we synthesize initial research and align as a product team_
|
||||
|
||||
## Risks
|
||||
_To be prioritized and posted_
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue