Update 01.md #221
Open
Update 01.md #221
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| @@ -1,9 +1,11 @@ | |||
| --- | |||
| play_number: 1 | |||
| title: Understand what people need | |||
| title: Understand what the service consumers need | |||
There was a problem hiding this comment.
Maybe end-users? Since this is generalized to digital projects.
| We must begin digital projects by exploring and pinpointing the needs of the people who will use the service, and the ways the service will fit into their lives. Whether the users are members of the public or government employees, policy makers must include real people in their design process from the beginning. The needs of people — not constraints of government structures or silos — should inform technical and design decisions. We need to continually test the products we build with real people to keep us honest about what is important. | ||
| We must begin digital projects by exploring and pinpointing the needs of the consumers who will use the service, and the ways the service will fit into their lives. Whether the users are members of the public or government employees, policy makers must include real people in their design process from the beginning. The needs of people — not constraints of government structures or silos — should inform technical and design decisions. We need to continually test the products we build with real people to keep us honest about what is important. | ||
|
|
||
| Services are no longer limited to people. Many services will be consumed or utilized by another service or non-human. |
There was a problem hiding this comment.
Digital projects users are not limited to only individuals, many will be utilized or consumed by other projects or services.
| @@ -23,3 +25,6 @@ We must begin digital projects by exploring and pinpointing the needs of the peo | |||
| - What were the key findings? | |||
| - How were the findings documented? Where can future team members access the documentation? | |||
| - How often are you testing with real people? | |||
| - What is the range of concurrent API calls during a given time period? | |||
There was a problem hiding this comment.
I think that:
What is the range of concurrent API calls during a given time period?
is covered by:
- What are the concurrency needs of the service?
if we rewrite as - What are the concurrency needs of the digital project?
|
I am in favor of leaving the “people” terminology. Even in cases where a service is built to be consumed by a different system, the way to learn about what the service should do is to talk with people, such as the developers of the consuming product, or the people who use that product. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.