Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update 01.md #221

Open
wants to merge 1 commit into
base: gh-pages
Choose a base branch
from
Open

Update 01.md #221

wants to merge 1 commit into from

Conversation

dovidkopel
Copy link

No description provided.

Copy link

@robbiethegeek-usds robbiethegeek-usds left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a few comments.

@@ -1,9 +1,11 @@
---
play_number: 1
title: Understand what people need
title: Understand what the service consumers need

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

@charwo
Copy link
Contributor

charwo commented Feb 9, 2020

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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants