From bdf1d4f4c3709bd9252e03bc2ab4fdc454fd9357 Mon Sep 17 00:00:00 2001 From: Dovid Kopel Date: Mon, 28 May 2018 15:18:13 -0400 Subject: [PATCH] Update 01.md --- _plays/01.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/_plays/01.md b/_plays/01.md index 29833811..a7de3956 100644 --- a/_plays/01.md +++ b/_plays/01.md @@ -1,9 +1,11 @@ --- play_number: 1 -title: Understand what people need +title: Understand what the service consumers need --- -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. ### Checklist 1. Early in the project, spend time with current and prospective users of the service @@ -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? +- What are the concurrency needs of the service? +- What is the uptime needs and how far should being cautious of single point of failure go?