<center><img src="hcd_images/board-meeting.png" style="width: 50%; max-width: 200px;"></center>
You pull up a chair at the large roundtable next to one of the new hires, Taylor. You have already been impressed by some of their observations and the comments they’ve made in meetings. You hope that you’ll get to work together on this project.
Blair, your supervisor, starts chatting to the team about the recent influx of complaints regarding lack of communication with the general public. They continue, “Luckily, this gives an opportunity to make some improvements. There has been some funding provided for a new project!”
You are told that the team has done some initial research and have decided that they want to create an app to allow for posting of information, to receive questions and complaints from the public. “Our team has been tasked with developing this app. Jamie, I’d like you to lead this project since you have experience in this area.”
You have done some similar projects in the past and you’re excited about the opportunity to lead the project. You get a thumbs-up from Alex across the table and a smile from Taylor who is sitting next to you. “Happy to take the lead, Blair, but it’s going to be a team effort. I’ll hold some time in our calendars so we can start working!”, you tell the team.
“Great,” says Blair, “I can share more specifics later, but we are aiming for about three months and a budget of roughly $10,000 to get this project done.”
You head back to your desk and start to jot down your ideas at the project. You start to think about what your first step will be.
---
You worked on a similar project in your hometown and you know that there is software out there that can work for this project. [[You choose an existing software to start working with.->Choose a Software]]
Thanks to the project from your hometown, you know that there are other cities that have similar apps and websites, so you decide to ask Alex and Taylor to help you by[[ looking at existing apps for inspiration.->Look at Existing Apps for Inspiration]]
You want to get the ball rolling on this project, you have the timeline & budget already, you should start the process of looking for a partner to build with, so you decide to [[write an RFP. ->Write an RFP]]
You have some ideas for features that could be useful on this app. But, you realize that you probably need some more information, so you decide your first step is to [[do a landscape analysis with your team. ->Do a Landscape Analysis]]
(if: $ProblemFocused_Flag is false) [
(set: $Overconfidence_flag to true)
]
<center><img src="hcd_images/choice.png" style="width: 50%; max-width: 200px;"></center>
(set: $purchase_software to true)
You know that there are existing options available for this project. You even used a similar app in your hometown. You review a couple of your options for the specific software that you plan to use.
You ask a few colleagues on your team to try out the software and give their approval.
---
You decide to:
[[Purchase the software->Purchase Software]] since a couple of your colleagues gave their approval.
[[You check the software ->Check Software Configuration Ability]] for compatibility and the ability be modified to meet your needs.
You buy enough licenses to perform a [[beta test with your users. -> Beta Test]](if: $ProblemFocused_Flag is false) [
(set: $Overconfidence_flag to true)
]
<center><img src="hcd_images/request-for-proposal.png" style="width: 50%; max-width: 200px;"></center>
You head to your desk and write up an RFP. You want to get this project moving and you know that this is the first step.
You share your RFP draft with a colleague so that they can double check you have all the correct requirements. They give it a quick glance and say that it's good to go. You decide that it is time to find a partner to build with so you [[hire a developer.->Hire a Vendor]]
<center><img src="hcd_images/test.png" style="width: 50%; max-width: 200px;"></center>
You remember that there was a similar communication app back in your hometown that people used to tell the local government about potholes and transportation issues. You know that these apps exist out there, so you decide to ask Taylor and Alex if they have heard of anything similar.
Taylor mentions that they know of an app that "//allows citizens to chat to their local representatives. They also have polls so you can 'vote' on the issues that are most important to you//."
You take a look at some of the suggested apps and compile a list including the key features of each.
---
You decide to:
[[Share the apps you found with your colleagues ->Share the Apps with Colleagues]] to see what they prefer.
[[Select the app you ->Select the App for the Community]] think is going to fit the needs of the community.
(set: $ProblemFocused_Flag to true)
(set: $CommunityFocused_Score to $CommunityFocused_Score +1)
<center><img src="hcd_images/corkboard.png" style="width: 50%; max-width: 200px;"></center>
You ask Taylor, Alex, Mel and Sam to join you as you start your landscape analysis. You know that this is going to be a team effort and this group brings a variety of perspectives to the table.
“//Did you raid the supply closet?//” Mel jokes as they note the sticky notes, markers and chart paper scattered across the conference room table.
“//I firmly believe the best ideas were first written on sticky notes,//” you joke back as your team members take their seats. You explain that you want to start out by thinking through the problem you are trying to solve with this app.
Your team spends some time individually thinking about the issue from the perspective of different citizens in North Olania.
Your team has a lively discussion about what some of the major problems and issues are. Taylor is passionate about two-way communication, “//It is just as important that we hear from them - we need a way to connect.//” Mel agrees and adds, “//we need to make sure that we are being providing useful information and resources.//"
As a team you decide that transparent, two-way communication is going to be the focus of the app you develop. As a team, you vote on what you should do next.
---
The team decides to:
[[Identify your target audience.->Identify your Target Audience]]
[[Select the app that you think will meet the needs of your community. ->Select the App for the Community]]
(set: $CommunityFocused_Score to $CommunityFocused_Score + 1)
<center><img src="hcd_images/application.png" style="width: 50%; max-width: 200px;"></center>
You select a design of an app that you'd like to 'mimic' for your own app. You do a bit more digging into the app that you think best fits the needs of the community. You are able to come up with a list of features that you want to ensure that your community app will have so you can communicate effectively.
Now that you have selected the app that you think is the most similar to what your community will need.
---
You decide to:
Start writing your [[ RFP to hire a developer.->Write an RFP]]
Look for and [[choose a software->Choose a Software]] that is 'out of the box'.
(set: $groupthink_flag to true)
(set: $ProblemFocused_Flag to true)
<center><img src="hcd_images/colleague.png" style="width: 50%; max-width: 200px;"></center>
Thanks to Taylor and Alex's suggestions, you were able to look into a few apps that you think might fit the needs of the community.
You have narrowed it down to a couple of options and highlighted the main features that you think will be most important. You gather your whole team together to share your options.
Your team spends a few minutes discussing which app they prefer, but more importantly which features are necessary. Thankfully, the team seems to come to a consensus on which app is going to be the best fit, so you [[schedule a brainstorming session ->Brainstorm with Team]] to create a design based on that app.
<center><img src="hcd_images/group-idea.png" style="width: 50%; max-width: 200px;"></center>
This is your favorite part of these projects: brainstorming!
You made a trip to the supply closet and have lots of sticky notes, markers, and the old rolling whiteboard in the conference room.
Your team spends some time reviewing the existing app and list of features, and then starts to come up with ideas for how you can modify it slightly to meet the needs of your community.
Now that you have more ideas about how you want your apps to be designed, your team has to decide on the next step.
---
Your team decides to:
Build out a second round of design documents to get[[ feedback on that design. -> Second Round of Design with Feedback]]
[[Write up an RFP ->Write an RFP]] so that you can hire a developer or partner to build with.
[[Choose a software->Choose a Software]] that already exists and only requires small modifications. (set: $hire_vendor to true)
<center><img src="hcd_images/search.png" style="width: 50%; max-width: 200px;"></center>
You posted a listing on a freelancer website and thanks to some help from your colleague Sam who conducted interviews, you found a developer that seems like a good fit for this app project. You have hired them and shared your requirements document and information about the app that you want to build.
They are excited to get started on the project and ask you a few clarifying questions about the purpose and features of your app. They ask you for some information about who this is for.
---
You tell the developer to:
[[Design for the general population.->Design for General Population]]
(if: $informed_design is true)[[Use the demographic information you collected.->Provide demographic information to Vendor]]
<center><img src="hcd_images/population.png" style="width: 50%; max-width: 200px;"></center>
The designer says that they have some existing information about the general population in North Olania and they will work on the app with that population in mind.
After about a week they send you their final version of the app. You are excited to take a look at the finished product.
---
[[Look at the developer's design. ->App Developer Shows you Design]]
You are back at your desk. What do you do?
---
You decide to:
* [[Choose an Existing Software->Choose a Software]]
* [[Write an RFP->Write an RFP]]
* [[Look at Existing Apps for Inspiration->Look at Existing Apps for Inspiration]]
* [[Do a Landscape Analysis->Do a Landscape Analysis]]<center><img src="hcd_images/paper.png" style="width: 50%; max-width: 200px;"></center>
You have collected some demographic information about your target audience and share it with the partner who is working on your app.
They take a look at the information and say that they have a couple of ideas and changes to some icons that they will make based on who this app is targeted towards.
After about a week they send you their final version of the app. You are excited to take a look at the finished product.
---
[[Look at the developer's design.->App Developer Shows you Design]]
<center><img src="hcd_images/check.png" style="width: 50%; max-width: 200px;"></center>
(if: $groupthink_flag is false and $Overconfidence_flag is false)[<h2>''Congratulations!''</h2>]
###You completed the project and launched your app.
Let's take a look at how well you included Human Centered Design principles in your app design.
Here is how you scored:
(if: $groupthink_flag is true) [[You may have done some traditional design steps and sought feedback from your team. But a critical purpose of Human Centered Design is to'' understand the problem and get the feedback from your end users''. While you may have created a good product, there is a chance that it did not meet the needs of your intended users. (colour: red)[Try the exercise again], and try to get your end users more involved in the design process.]
] (if: $Overconfidence_flag is true) [
[Wow, you completed this project really quickly! While completing a project ahead of time is exciting, a critical purpose of Human Centered Design is to ''understand the problem and get the feedback from your end users''. This takes time. You didn't do enough of that, and instead you went straight into developing a solution. Without fully understanding the problem being addressed, or your intended users, it is unlikely that your app would be successful. (colour: red)[Try the exercise again], and try to get your end users more involved in the design process.]
]
(if: $CommunityFocused_Score >= 4)
[You scored (colour: green)[''Excellent''] on ''User Focus''! You decided to engage your users through the design and development of your app. One of the core principles of Human Centered Design is to understand and engage your users; you did this successfully. Congratulations! <br>](else-if: $CommunityFocused_Score >=2 and $CommunityFocused_Score < 4 )[You scored (colour: orange)[''Fair''] on ''User Focus''. You made some decisions throughout your design process that considered your users, but missed some opportunities.Remember that one of the core principles of Human Centered Design is to understand and engage your users in the process. ](else: )[Unfortunately, you scored (colour: red)[''Poor''] on ''User Focus''. The choices that you made during your app design and launch didn't consider your users. Remember, one of the core principles of Human Centered Design is to understand and engage your users in the process. Feel free to try this exercise again. <br>]
(if: $TestingIteration_Score >= 2)[You scored (colour: green)[''Excellent''] on ''User Testing''. You decided to take the opportunities to test your app with your intended users. This is a good application of Human Centered Design principles. Congratulations! <br>](else-if: $TestingIteration_Score >=1 and $TestingIteration_Score <2)[You scored (colour: orange)[''Fair''] on ''User Testing''. You did some testing, but missed other opportunities to engage your users in the testing of your app before you launched it. Remember that a core principle of Human Centered Design is considering and including your users at multiple stages of the design process. ](else: )[Uh oh! You scored (colour: red)[''Poor''] on ''User Testing''. You forgot to do user testing before launching your app. Both Human Centered Design and Traditional Design principles encourage testing before launching a product. Feel free to try the exercise again to see where you can include testing with your users in the process. <br>]
(if: $purchase_software is true)
[<br>''You chose to purchase existing software'' in this case. Good thinking! Using existing software is often faster, cheaper and better supported than building something from scratch. But whatever you choose needs to meet all the critical requirements and be secure, reliable, etc. Be sure to check any 'out-of-the-box' software for basic compatibility and ensure it will meet the needs of your intended users. ]
(if: $CompatibilityCheck_Flag is true)
[<br>(colour: green)[''You checked your software for some basic compatibility''] before going further with purchasing or rolling it out to your users. This is smart! It is important to make sure that the software you are purchasing will meet the needs of your users. ]
(if: $hire_vendor is true)
[<br>''You hired a vendor'' to create something custom for your needs. You must have determined that existing software was not going to meet the needs of your users. Very observant! Keep in mind this will often increase the time, cost, and maintenance efforts compared to an existing out-of-the-box software.]
(if: $Communication_Flag is true)
[<br>You spent some time with your team working on a (colour: green)[''communications strategy''] for the rollout of your app. Well done! While it is important to build something with your users in mind, it is equally important to ensure that your users hear about it. Involving your users in the design process is one step towards ensuring they are aware of (and decide to use!) the tool that you build.]
<center><img src="hcd_images/ui.png" style="width: 50%; max-width: 200px;"></center>
You have been sent the final design for the app. You share it with your colleagues and everyone is excited with how this project has come together.
There is room in the budget and within your timeline for one more task. As a team you discuss what the best use of the remaining funds and time might be.
---
As a team you decide to:
[[ Hire a designer to improve the front end. -> Hire a Designer]]
[[Ask the developer to test it with a pool of beta testers. -> Beta Test]]
<center><img src="hcd_images/testing.png" style="width: 50%; max-width: 200px;"></center>
Having worked on a couple of projects like this one before, you knew that a beta test was likely to bring a couple of bugs to light. Thankfully, the developer was already able to find a solution.
They received some feedback from the testers that the local representative contact list could use some upgrading and potentially use geo-location for incident reporting. They are able to add a map that highlights where the incidents have been reported.
You give the go ahead to [[make that change -> Make changes based on beta test feedback]] and a few other small, design tweaks that were suggested by the testers.
(set: $CommunityFocused_Score to $CommunityFocused_Score +1)
(set: $TestingIteration_Score to $TestingIteration_Score +1)
<center><img src="hcd_images/testing-1.png" style="width: 50%; max-width: 200px;"></center>
You present the app to your team. Everyone is happy with how it turned out! You look forward to wrapping up this project.
---
You [[do a final review and get ready for launch! ->Final Review]]
<center><img src="hcd_images/graphic-designer.png" style="width: 50%; max-width: 200px;"></center>
You hire a designer and share the current app design with them.
You ask them to update the design using your organization's branding. They are able to make the changes that you want and are even able to weave in some design nods to North Olania.
You are really happy with the design changes that have been made and are excited to see this app in the hands of the people!
---
[[Do a final review of your app.->Final Review]]
<center><img src="hcd_images/review.png" style="width: 50%; max-width: 200px;"></center>
You’ve done a final review of the app and shared it with your colleagues. The team is ready to launch (thankfully!).
You check in on budget and timeline and agree that now is the time to release your app to the world. One of your colleagues, Alex, asks about how you will get the word out about the app. You know that you’ve built a great tool, you just need people to use it.
---
So you decide to:
[[Create a communications plan->Analytics]] to help spread the word about your app.
[[Go with your gut->Report Card]] and launch the app. People will find it on their own.
<center><img src="hcd_images/testing-1.png" style="width: 50%; max-width: 200px;"></center>
You took some time in the last couple of days to draft out all the design ideas and features into a document that you circulated to the team via email.
Back in the conference room, you decide to go around the room and have each person give you their red lights and green lights. Red lights are things that they think should be removed from the design (or stopped), and the green lights are things that they think should continue to be included in the design. You also have a parking lot of ideas that you don't think fit this project, but that you might be able to incorporate into other programs or projects in the future.
---
You decide to:
[[Incorporate their feedback into the designs-> Incorporate Feedback]]
[[Write an RFP->Write an RFP]]<center><img src="hcd_images/good-feedback.png" style="width: 50%; max-width: 200px;"></center>
Now that you have incorporated that feedback into your plan for the design and written up your requirements document, you have to decide on the next step.
---
You decide to:
[[Hire a developer->Write an RFP]] to build or customize your app.
[[Choose an existing software->Choose a Software]] that you can modify.
(set: $CompatibilityCheck_Flag to true)
<center><img src="hcd_images/rpa.png" style="width: 50%; max-width: 200px;"></center>
You make sure the software you choose is suitable for your users. You note that it is possible to make some modifications and look into if it is available in multiple languages. Luckily it is!
---
Now that you know this is the software you will use, you decide to:
You get some trial license and [[perform a beta test-> Beta Test]]
[[Purchase the software->Purchase Software]].
<center><img src="hcd_images/online-shopping.png" style="width: 50%; max-width: 200px;"></center>
You have chosen the software that you plan to use. You do a check to ensure that it will meet all of your requirements. You ask your supervisor, Blair, for final confirmation that you have everything that you need. They agree and remind you of the steps for finalizing the purchase.
You purchase the software and all the licenses you need. Now that you have everything you are ready to move onto the [[final review. ->Final Review]]
(set: $CommunityFocused_Score to $CommunityFocused_Score +1)
<center><img src="hcd_images/target.png" style="width: 50%; max-width: 200px;"></center>
It’s been a couple of days since you last gathered as a team to work on this project. The team has come back together to think more deeply about the target audience for this project.
You pull out the chart paper from the previous meeting where you identified who would be likely users of this app. Your list includes: college students, parents, government workers, elected representatives, and public service employees.
You lead a discussion about who would be most likely to use the app and who at this point are not likely to engage, but who might be convinced to engage if they had the right tools (like your app!).
The team decides that the target audience is going to be college-aged women. You are happy with the progress that the team has made so far. You know that there is still a lot of work to be done and you are aware that developing the app is going to take a significant amount of time.
---
Now that you have identified the target audience, you ask the team to pair up so that they can:
Dig deeper into the target audience and [[create user personas.->Create User Personas]]
[[Start Looking at existing apps for inspiration.->Look at Existing Apps for Inspiration]]
(set: $CommunityFocused_Score to $CommunityFocused_Score +1)
<center><img src="hcd_images/buyer.png" style="width: 50%; max-width: 200px;"></center>
It has been about a week since you asked Taylor & Sam and Alex & Mel to spend some time thinking through user personas. Not surprisingly, everyone has been busy with other tasks. So you ask them to refresh your memory by giving you a quick rundown of how they came up with their user personas.
You are really excited about the personas your team has created. As a group you look at all of the personas and continue to push each other to give further details about their personas and to challenge assumptions that are being made about the personas. You take a look back at your original target audience list and are satisfied that these seem to be aligned with your original ideas.
---
Now that your team has a clear picture of who this app is intended for, you decide to:
Conduct some research [[by surveying people within your target audience.->User Surveys]]
[[Start Looking at existing apps ->Look at Existing Apps for Inspiration]] that target the same audience for inspiration. (set: $CommunityFocused_Score to $CommunityFocused_Score +1)
<center><img src="hcd_images/surveyor.png" style="width: 50%; max-width: 200px;"></center>
You know that Alex has experience conducting user research, so you ask them to help you create a user survey to get more information from your target audience. They create the survey and suggest that you send it out as part of the community newsletter.
You know that the newsletter will probably only reach people who are already getting communication from the government, so you decide to also send Taylor and Mel out to the local college campus to ask people passing by if they are willing to share their ideas and answer a few survey questions.
After collecting data you take a look at the information that has been collected. People shared their experiences interacting with the government, how they get their information about programs that support women in politics, how they find out about hate crimes related to women and women in politics, and other issues that are important to them.
Now that you have some data from your target audience, you schedule a [[brainstorming session with the team. ->Informed Design]]
<center><img src="hcd_images/brainstorm.png" style="width: 50%; max-width: 200px;"></center>
This is your favorite part of these kinds of projects: brainstorming! You have shared the results of the surveys with the team via email and tell them to keep that information in mind as you brainstorm.
You decide to have the team engage in one of your favorite brainstorming activities: Crazy 8s! You encourage them not to judge their ideas, we are brainstorming after all. “//Just get your ideas down on paper, we can refine them later.//” you remind as you start the timer.
After everyone has shared their ideas about what should be included in the app to meet the needs of the audience. You hand out small stickers and say that it’s time to vote on the ideas. “//Dotmocracy!//” exclaims Mel, “//we used this in college!//”. You laugh at that name for the voting system but agree that it fits.
You read out the ideas for features on the app that received the most votes. As a team you debate the most popular ideas and come up with a list of ‘must-haves’ on your app. They are:
1. Citizens can report issues or incidents
2. Updates and information regarding current and upcoming programs
3. Community Surveys, polls, and ways to gather feedback
4. Listings of local representatives with their contact info
(set: $informed_design to true)
---
Now that you have a list of a few key features for your app, you decide to:
[[Bring your Ideas to your users for feedback.->Bring Your Ideas to your Users]]
[[Build a prototype.->Build a Prototype]]
(set: $TestingIteration_Score to $TestingIteration_Score +1)
<center><img src="hcd_images/customer-feedback.png" style="width: 50%; max-width: 200px;"></center>
It takes additional time, but you know how important it is to seek feedback from your users so you bring your list of features and ideas for the app back to your target audience to see their reactions.
You were able to add this as an agenda item at tomorrow’s town hall meeting. Taylor offers to head to the college campus to get some initial reactions.
Taylor had a couple of great conversations on campus. They tell you, “//A few people brought up the fact that there is an increasing number of immigrants in North Olania. I had more than one person say that we should offer the app in multiple languages.//” You agree that having multiple languages is an important feature saying, “//we could be missing out on communicating with a growing section of the public. We will definitely make sure that multiple languages are supported on the app//”. You know that there are similar apps out there that offer communication in multiple languages.
Now that you have some more information from your users, and an approaching deadline, you decide it’s time to [[build a prototype. ->Build a Prototype]]
<center><img src="hcd_images/prototype.png" style="width: 50%; max-width: 200px;"></center>
Your colleagues Mel & Sam have been pulled away onto another project, so you ask Taylor and Alex to join you in quickly building a prototype for the communication app. You know that you need to move the project along to meet your deadline, so you decide to not spend too much time on the prototype.
You decide to each draw a user interface using paper and markers. The three of you share your prototypes with each other and identify which features you think should be part of the prototype. Taylor offers to combine all of the ideas into one prototype and create a digital copy of the design so that you can share it to get some more feedback.
---
You decide to:
[[Share the prototype with your colleagues.->Share Prototype with Colleagues]]
[[Share the prototype with your users.->Share Prototype with Users]]
<center><img src="hcd_images/colleague.png" style="width: 50%; max-width: 200px;"></center>
You share your prototype with the rest of your colleagues. They are excited to see that this project is coming along.
Mel has a few ideas regarding the interface; they have a lot of experience in UX design so you make sure to take notes on their suggestions.
The idea of a chat feature comes up with your colleagues. You aren't sure if this is going to be feasible with this project, but you agree that you'll look into it.
Now that you have gathered some feedback from your colleagues, you write up a requirements document.
---
You are ready to see this project come to life so you:
[[Hire a partner->Hire a Vendor]] to build or customize an app.
[[Choose an existing software.->Choose a Software]] (set: $CommunityFocused_Score to $CommunityFocused_Score +1)
<center><img src="hcd_images/feedback.png" style="width: 50%; max-width: 200px;"></center>
You know that you need to share your ideas with your target audience. Thankfully, you are able to connect with your audience by working with a Women in Politics group at the local college. You share your idea for the app and the features that you think it should include.
You get some good suggestions on how the interface could be changed to be more user friendly. More than one person suggests having a chat feature so that citizens’ can get quick responses would likely be appreciated. You agree that a chat feature could be helpful, but you do have questions about how feasible it is. You promise to look into the feasibility of adding this to your design plan.
At this stage, you decide that you are ready to build a requirements document.
Now that you have sought some feedback from your users and have built out a requirements document, you are ready to see this project come alive.
---
You decide to:
[[Find a partner to build or customize your app with.->Hire a Vendor]]
[[Choose an existing software for your app.->Choose a Software]] (set: $Communication_Flag to true)
<center><img src="hcd_images/social-marketing.png" style="width: 50%; max-width: 200px;"></center>
Your team knows that marketing and user buy-in are important and you want to make sure you have a plan to encourage people to start using the app. Thankfully, most of your team has experience in communications and are able to create a solid plan for the roll out of your app.
Now that you have a plan in place, you are ready to [[launch your app! ->Report Card]]
{
<!-- $CommunityFocused_Score measures how focused the app developer is on the end user, as opposed to their own ideas, their internal team members, or anyone else who isn't an end user-->
(set: $CommunityFocused_Score to 0)
<!-- $TestingIteration_score is how much the developer leverages user-focused testing and making changes to the product based on that testing. -->
(set: $TestingIteration_Score to 0)
<!-- $informed_design is a flag that the user gets if they do all the HCD design steps. Now they have the data required to make/purchase better apps in the build phase -->
(set: $informed_design to false)
<!-- $purchase_software determines if a user purchased an off-the-shelf software -->
(set: $purchase_software to false)
<!-- $hire_vendor determines if a user hired a vendor -->
(set: $hire_vendor to false)
<!--$groupthink_flag is a flag that is true if the user gets stuck in the cycle of just discussing this internally and then moving on to the build phase-->
(set: $groupthink_flag to false)
<!--$CompatibilityCheck_Flag is a flag that is true if the user does some basic sanity checks on the software before purchasing or rolling it out to users. -->
(set: $CompatibilityCheck_Flag to false)
<!--$Communication_Flag is a flag that is true if the plans a communication strategy for the rollout of their app.-->
(set: $Communication_Flag to false)
<!--$Overconfidence_Flag is a flag that indicates if you went straight ahead to developing a solution without doing much of a design processs-->
(set: $Overconfidence_flag to false)
<!--ProblemFocused checks to see if the user spent any time at all focusing on the problem before moving on to a solution-->
(set: $ProblemFocused_Flag to false)
}
<center><img src="hcd_images/coffee-break.png" style="width: 50%; max-width: 200px;"></center>
You, Jamie, and your coworker, Alex, are chatting while standing in line at the coffee cart near your office. You both work for a civil society group in North Olania. After the recent election, your Women in Politics group is starting some new projects to continue promoting gender equality in politics.
You comment to Alex that you are looking forward to hearing about the new project at your team meeting this morning. “I heard that there have been a couple of complaints filed recently, apparently there was another incident reported by a female politician.”
“I’ve heard from a few people that they’re frustrated, they say they don’t have a way to properly report or track these kinds of issues,” says Alex. They go on to tell you that they heard from your supervisor, Blair, that the team is going to be starting a project that increases the transparency between your organization, the general public, and hopefully the local government as well.
You agree that more transparent communication is probably a step in the right direction. You grab your coffee and head to the office for your team meeting.
---
[[Go to your team meeting ->Start]]
(enchant:?passage,
(align:"=><=") +
(font:"sans-serif") +
(colour: #202124) +
(text-size: .7) +
(background:transparent)
)
(append:?sidebar)[(icon-fullscreen:)(icon-restart:)]#Welcome!
You are about to walk through a story where you play the role of a ''project lead'', tasked with building a transparency and communication app. As you design this app, be careful to follow the principles of ''Human Centered Design'', namely ''engaging with your users'' during the design process and ''testing with end users'' to get accurate feedback.
At the end, you'll get a ''report card'' with feedback on how well you did or did not follow the principles of Human Centered Design. You are welcome to try this story as many times as you like to explore the different paths you can take.
## Navigation
Generally, you navigate by clicking the blue links.
You can also use the navigation icons in the left panel:
<table style="width: 100%;">
<tr>
<td>
<tw-expression ><tw-icon data-raw="">⛶</tw-icon></tw-expression> <br></br>Enter/Exit Fullscreen
</td>
<td>
<tw-icon data-raw="">⟲</tw-icon><br></br> Restart the Story
</td>
<td>
<tw-icon >↶</tw-icon><br></br>Go back one passage
</td>
<td>
<tw-icon >↷</tw-icon><br></br>Go forward one passage
</td>
</tr>
</table>
## Begin
###[[Let's go!->Context]]