Challenge Summary
Welcome to "FAST - Government Agency Digital Identity Agency User Wireframes". In this challenge, we are looking for you to help plan a great user experience for a new digital identity management tool. We recently ran a wireframe challenge through Topcoder (see the previous challenge here) to establish the IA for the "citizen-user" view for this tool and we have a great starting point for the page layout, information architecture, and navigation for the citizen-user view of this site. The purpose of this challenge is to create the "Agency-user" view. Read below for more information!
During this one round challenge format, we would like for you to take the provided design problem, explore the user experience, and design wireframes which highlight user navigation, experience, and information flow across the digital identity tool targetted to Agency User.
Challenge Timeline and Rolling Checkpoint (One Round Challenge Format)
- Challenge Starts: 12/08/2016 00:00 PM EDT
- Rolling Checkpoint Ends: 12/09/2016 16:00 PM EDT
- Challenge Ends: 12/13/2016 06:00 AM EDT
We are offering an award to the top 3 wireframe designs! Plus 5 $75 Checkpoint prizes!
1) $1300
2) $650
3) $250
Rolling Checkpoint $75 each for 5 selected submissions. Please submit your initial wireframes solution before "12/09/2016 16:00 PM EDT".
Background Overview
Government programs require proof of identity and other attributes when citizens apply, register, or sign up for programs and services. This information is necessary to
(1) prove that people are who they say they are; and
(2) that they meet eligibility requirements for certain programs.
Agencies, however, often find it difficult to verify the accuracy of citizen's information (especially when it is not provided in-person). This can lead to processing delays that make it difficult for Agency programs to provide services/benefits on a timely basis. This verification process is even more difficult via digital channels. These difficulties are due to several issues:
- No standard approach to identity verification in the digital world. Currently, there is no authoritative digital identity (like a driver's license in the physical world) that multiple agencies or relying parties can accept with absolute certainty.
- Citizen-driven benefits fraud. Agencies and their respective programs can become victims of benefits fraud – scenarios in which citizens misrepresent themselves to gain access to additional benefits or services – and as a result incur additional costs and/or delays.
- Information security risk. Some agencies are hesitant to move certain processes to digital channels, where they perceived it to be more difficult to safeguard citizen data and effectively ensure their privacy.
- Inertia and legacy physical processes. Some agencies are still "stuck" completing manual, paper-based transactions and interacting with their constituents through physical means, and have yet to adopt the business processes and/or system to support a more virtual, electronic interaction.
Because of these difficulties, Agencies either overcompensate with burdensome requirements (e.g. collect too much information) or avoid digital channels altogether and collect requirements via intrusive or inconvenient procedures (e.g. in person appointments or physical forms). The intent of this solution is to help Agencies spend fewer resources (e.g. time, money, personnel) on identity verification and more time fulfilling their mandate.
The following quotes represent the basic desire across government agencies for a central identity verification solution in the digital world:
"The government should have one, cross-Agency identity verification system that we can all use. Each Agency should not have its own process." – Agency employee
"We should have a universal system. Our Agency does not want to be in the business of authentication. We want to spend more time doing our job." – Agency employee
Challenge Goals
To address these difficulties, this solution aims to create a single platform for identity verification for agencies. This solution is intended to improve digital interactions between Citizens and Agencies by allowing Citizen users to proactively assemble and manage their digital identities while also reducing the identity verification burden on organizations.
While the Citizen user-facing wireframes have already been built (see challenge attachment), this Agency user-facing wireframe strives to address Agency pain points with a single, dynamic platform that will allow them to set transaction requirements, intake verified applications for their benefits/services, and then take action on those applications with certainty (see challenge goal diagram.jpg).
The goal of this wireframe challenge is to take first steps toward development of the information architecture and user navigation for Agency users. We want to deliver a great user experience that is simple, intuitive, and very easy for different Agency users to understand and adopt.
Target User
This challenge will focus on target users who are:
- Government employees responsible for setting application requirements, receiving forms and applications, verifying their contents, and making a decision about whether to provide benefits or services
- Predominantly 18 and older (average age 45), male and female
User Needs:
- Facilitate a relationship with the Citizen user
-- "We're obligated, as the government, to provide avenues for folks who need to ask for additional help." – Agency employee
- Increased process efficiency
-- "Citizens could do all their registrations online, but many choose to fax in their forms. I am trying to move us away from that system – we have employees that have to walk to the fax machine every 20 minutes." – Agency employee
- Modern, advanced look and feel
-- "We are still in the paper world. We're working through the electronic version process, but it is going to be difficult to get rid of paper." – Agency employee
- Real-time, more accurate information flows
-- "Name changes are really difficult. Even the number of characters in a name can stymie a system. Multiple-hyphen last names are difficult" – Agency employee
-- "Information is constantly changing. If citizens get married, if they move, etc. things change and their status changes – which informs the adjudication around certain benefits. Agencies have to constantly verify and keep up with those changes, which is difficult." – Agency employee
- Clean, intuitive design
Core functionality:
- Agency user should be able to choose which of their agency's programs (e.g. Passport Services, Visa Services) and corresponding benefit/services applications (e.g. New Passport Application, Passport Renewal Application) are present on the Citizen-user interface.
- Agency user is notified when a Citizen user has submitted an application for one of these services / benefits
- Agency user can view submitted applications in the order in which they were received in an "inbox-like" screen/view
- Agency user can either review the application on the screen, download it, or print it for additional processing off line
- Agency user can open the application within the Portal for review, make a decision based on its contents, and communicate to user whether application has been approved, denied or more information is required
- Agency user can share important information with the user, such as upcoming deadlines or expiration dates (e.g. deadline for Passport renewal, travel alerts, etc.)
- For each application, Agency user can set the following requirements:
-- Eligibility: Define the attributes required from citizens in order for the Agency to verify identity and adjudicate services accordingly. For example, in the case of a Passport application, requirements may include name, address, birth date, proof of citizenship, SSN, etc.
-- Product/Service Specifications: Define specifications and/or functions that a user could choose from and would be available as a choice on the Citizen-user interface. For example, in the case of a passport application, users would need to specify if they desire a 28-page or 56-page booklet, expedited shipping options, or a leather-bound cover in which to house the passport.
- Agency user can view a summary of submitted applications, including:
-- How many are currently in the inbox?
-- How many have been submitted over the last day, week, year (e.g. line graph over time)?
-- How many deserve immediate attention based on how long they have been sitting in the "inbox" and desired processing/response times?
Existing Artifacts
Wireframes - we recently ran a wireframe challenge through Topcoder and have a great starting point for the page layout, information architecture, and navigation for the "Citizen-user" view of this site. Please refer to the attached Citizen-user wireframe to understand the Citizen process.
We now need to create the "Agency-user" view, and we are asking each IA to essentially pick up where the Citizen-user facing wireframes left off. Essentially we want to design the agency user screens and experience which is basically the next step of the process after a citizen elects to submit information to apply for a product/service and that information is transferred to the agency for review and approvals.
The two wireframes (e.g. citizen user & agency user) should show opposite sides of the same transaction – e.g., you should be able to follow the Passport application transaction as it moves from the Citizen wireframes to the Agency-user wireframes:
- The Citizen-user wireframes (see attached screen 6. "Application Status") show the creation of a verified identity credential, which is then used to populate and submit an application for a benefit/service provided by a specific Agency program (e.g. passport renewal in the wireframes)
- The Agency-user wireframes should show how that application is received via an inbox-like screen as soon as the application is submitted by the citizen (see attached screen 6. "Application Status" – once a user submits this the application enters phase 2 which is "Credential Approval" – at this point the process hands off to the agency user).
-- Once opened in the inbox application - the Agency user should be able to see all of the information the Citizen user entered to complete the application
Suggested Screens for Agency User
For this wireframe challenge, it is important to note that we would like you to think through which pages are necessary and how to layout the above functionality. We would like to see your suggestions for a clear information architecture and beautiful user experience. Below are a list of suggested screens for the Digital Identity Agency-user experience. Please note that these are merely suggestions – if you can think of ways to lay out the above functions and features to improve the user experience, please do. If you need to combine or alter suggested screens, please do.
1. Login Process vs. Home Screen vs. Dashboard
- When an Agency user logs in, he / she is aiming to accomplish one of the following tasks:
-- Manage Programs / Applications through the platform
-- Review and Approve or Deny Applications from Citizens
-- Push alerts / notifications out to the citizen-end users
- Based on your understanding of the above core functionality, the citizen end-user screens, and these three major tasks – how can you design the log-in process so that a user is quickly able to accomplish his / her task?
-- Is a user presented with options as to his / her goal that facilitate navigation?
-- Is there a homepage or a dashboard for the tool and if so what information is on it?
-- How else might you make this platform very easy to understand, navigate, and accomplish these tasks?
2. Programs/Applications Management Screen
- A program (e.g. Passport Services) is designed to deliver specific benefits/services (e.g. Passport) to Citizens. One Agency may have multiple programs. An application is the method through which Citizens submit information pulled from their digital identity thread to request access to a program's products or services (e.g. New Passport Application). One program may have multiple applications for the different benefits/services provided.
- Screen should allow the Agency user to add, edit, or remove programs that fall within an Agency's jurisdiction (e.g. if the Agency is responsible for supporting international travel, some of the programs the Agency user could add, edit, or, remove would be "Passport Services" or "Visa Services")
-- If the Agency user is adding a new program, he could be asked to include:
---- The title of that program
---- A description of what that program does and the benefits/services it provides to Citizens
-- Upon creation of a program, the Agency user could be prompted to add an Application for that Program
- Screen should allow the Agency user to add, edit, or remove applications that fall within a program's jurisdiction (e.g. if the program is Passport Services, some of the applications the Agency user can add, edit, or remove would be "New Passport Application" or "Passport Renewal")
-- If the Agency user is adding a new application, he could be asked to include:
---- The name of the application (e.g. Passport Renewal)
---- The official government document used to apply (e.g. a current application form)
------ If the Agency user uploads an official document, the Portal would set requirements for the application from that document
------ If the Agency user does not wish to upload an official document, they can manually select required data fields at this point
---- The expiration date of the product/service (e.g. one year, five years, for life)
---- The program responsible for reviewing the application (e.g. dropdown list of programs for whom this Agency user is authorized to create applications)
3. Digital Application "Inbox"
- Screen should allow the Agency user to review submitted citizen-user Application information
-- Screen should communicate metadata about the Applications submitted by citizens for respective services such as data fields submitted, name of the applicant, time submitted, etc.
-- Screen should have a search functionality
---- Agency user should be able to "pin" applications for further review
-- Screen should make clear if there are new incoming Applications and feature a summary of applications currently in the "inbox"
---- How many are currently in the inbox?
---- How many have been submitted over the last day, week, year (e.g. line graph over time)?
---- How many deserve immediate attention based on how long they have been sitting in the "inbox"?
---- Summary could feature a "pie chart" that illustrates applications by how long they have gone unaddressed (breakdown is notional)
- 1 – 3 days old applications are green
- 3 – 7 days old applications are yellow
- 7 days+ old applications are red
-- Screen should be able to mark applications that have been expedited by the citizen user and therefore should receive attention first
-- For each application, the screen should communicate options for the Agency user to address it including:
---- "Download", "Print", "Confirm or Deny Application"
4. Adjudication ("Confirm or Deny Application") Screen
- Once the Agency employee clicks on the "Confirm or Deny Application" option, then the employee is brought to a screen that allows for the adjudication (i.e. yes/no decision) of the application
- This screen should communicate high-level details of the applicant's information with the ability to click to view more detailed information
- At the bottom or top of the screen, there should be three buttons that communicate adjudication options for the application
-- Button one: "Yes" – application is accepted
-- Button two: "No" – application is rejected
-- Button three: "More information is required" – application is sent back to citizen user with explanation of what additional information is needed
5. Communications Management
- Screen should allow the Agency user to add, edit, or remove communications
-- Agency user can choose to create either notifications or alerts
---- A notification is an automated prompt to the citizen user based on business rules (e.g. expiration notification to go out to citizen user 6 months before expiration date)
---- An alert is a program-wide communication written to convey program news and changes (e.g. all Passport owners may no longer wear glasses in their Passport pictures)
---- Manual pushes of information to an individual applicant
6. Other screens up to your discretion!
- As mentioned above we are looking for wireframes that create an intuitive and seamless user experience. Outside of the suggested screens above - are there any other functions or features that you would recommend? Consider how an Agency user might want to review applications as they come in.
- Additionally, these screens are merely suggestions. If you can think of a better way to lay this out – please do!
Things to consider for intended user:
- Why is he/she opening this web application in the first place? What is he/she looking to do?
- What is the "first experience" when opening the application? What is the primary goal of the application and experience?
- What are the priority actions or items a user needs to interact with?
Desired Brand Attributes:
- Should be clean & intuitive (must not add complexity or confusion)
- Should be concise with clear calls to action
- Should be efficient – it should be clear to the employees that this tool is designed to make their lives easier and more streamlined
Design Inspiration:
- Simplicity: The website should display various levels of priority for different applications; include a search box to sort through email; and provide the option to categorize applications (e.g. Google Inbox)
- User-Centricity/Personalization: The site should be personalized for those visitors that have logged in and feel like it is catering to a visitor’s specific needs (ex: GrubHub, Netflix)
- Consistency: Each screen should contain a similar design and maintain a high level of consistency throughout the process
- Efficiency: The interface should allow the Agency user to complete the task in the most efficient way possible. What is the user trying to achieve? What functions does it need to have? How can you design an interface that lets the Agency user accomplish what he wants and needs to do?
Attached Documentation:
- Citizen-user wireframes
- Challenge Goal diagram
Target Devices:
- Desktop (1280px)
****Please note**** The final solution will be a fully responsive web application. Please consider this as you design your desktop layouts so that these designs are scalable for other device sizes.
Wireframe Expectations:
- Produce HTML click through wireframes that can be used to demonstrate all mentioned functionalities as required in each round.
- The website must be very easy to use and intuitive. Keep that in mind when designing your solution.
- You MUST cover all screens mentioned in required sections below, if any requirement is missing in final submission the client will not look at it, so make a checklist for the required screens to make sure you designed all of them.
- Please show us your proposal as a movie or series of wireframes that communicate the user’s intended interaction with your proposed solution.
- You MUST use wireframes note pane in every single page you design to explain what items are addressed in that page from the documentation, what things you added/changed/removed, use it to make your idea clearer and help the client to give you constructive feedback.
Learn Axure:
New to Axure? Here are some quick tutorials to help you get started.
http://www.axure.com/learn
Judging Criteria
- User Experience of application.
- Completeness and accuracy of the wireframe as defined in the spec requirements.
- How well your wireframes provide a consistent user flow.
Submission & Source Files
Preview Image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
Generated HTML files with all the requested contest requirements stated above.
Source Files
Wireframes should be built in Axure. The resulting files should have generated HTML files. Also, all the content must be listed and the pages are linked together to show page flow.
Final Fixes
As part of the Final Fix phase, you may be asked to remove, update, or change some features of the wireframe.
During this one round challenge format, we would like for you to take the provided design problem, explore the user experience, and design wireframes which highlight user navigation, experience, and information flow across the digital identity tool targetted to Agency User.
Challenge Timeline and Rolling Checkpoint (One Round Challenge Format)
- Challenge Starts: 12/08/2016 00:00 PM EDT
- Rolling Checkpoint Ends: 12/09/2016 16:00 PM EDT
- Challenge Ends: 12/13/2016 06:00 AM EDT
We are offering an award to the top 3 wireframe designs! Plus 5 $75 Checkpoint prizes!
1) $1300
2) $650
3) $250
Rolling Checkpoint $75 each for 5 selected submissions. Please submit your initial wireframes solution before "12/09/2016 16:00 PM EDT".
Background Overview
Government programs require proof of identity and other attributes when citizens apply, register, or sign up for programs and services. This information is necessary to
(1) prove that people are who they say they are; and
(2) that they meet eligibility requirements for certain programs.
Agencies, however, often find it difficult to verify the accuracy of citizen's information (especially when it is not provided in-person). This can lead to processing delays that make it difficult for Agency programs to provide services/benefits on a timely basis. This verification process is even more difficult via digital channels. These difficulties are due to several issues:
- No standard approach to identity verification in the digital world. Currently, there is no authoritative digital identity (like a driver's license in the physical world) that multiple agencies or relying parties can accept with absolute certainty.
- Citizen-driven benefits fraud. Agencies and their respective programs can become victims of benefits fraud – scenarios in which citizens misrepresent themselves to gain access to additional benefits or services – and as a result incur additional costs and/or delays.
- Information security risk. Some agencies are hesitant to move certain processes to digital channels, where they perceived it to be more difficult to safeguard citizen data and effectively ensure their privacy.
- Inertia and legacy physical processes. Some agencies are still "stuck" completing manual, paper-based transactions and interacting with their constituents through physical means, and have yet to adopt the business processes and/or system to support a more virtual, electronic interaction.
Because of these difficulties, Agencies either overcompensate with burdensome requirements (e.g. collect too much information) or avoid digital channels altogether and collect requirements via intrusive or inconvenient procedures (e.g. in person appointments or physical forms). The intent of this solution is to help Agencies spend fewer resources (e.g. time, money, personnel) on identity verification and more time fulfilling their mandate.
The following quotes represent the basic desire across government agencies for a central identity verification solution in the digital world:
"The government should have one, cross-Agency identity verification system that we can all use. Each Agency should not have its own process." – Agency employee
"We should have a universal system. Our Agency does not want to be in the business of authentication. We want to spend more time doing our job." – Agency employee
Challenge Goals
To address these difficulties, this solution aims to create a single platform for identity verification for agencies. This solution is intended to improve digital interactions between Citizens and Agencies by allowing Citizen users to proactively assemble and manage their digital identities while also reducing the identity verification burden on organizations.
While the Citizen user-facing wireframes have already been built (see challenge attachment), this Agency user-facing wireframe strives to address Agency pain points with a single, dynamic platform that will allow them to set transaction requirements, intake verified applications for their benefits/services, and then take action on those applications with certainty (see challenge goal diagram.jpg).
The goal of this wireframe challenge is to take first steps toward development of the information architecture and user navigation for Agency users. We want to deliver a great user experience that is simple, intuitive, and very easy for different Agency users to understand and adopt.
Target User
This challenge will focus on target users who are:
- Government employees responsible for setting application requirements, receiving forms and applications, verifying their contents, and making a decision about whether to provide benefits or services
- Predominantly 18 and older (average age 45), male and female
User Needs:
- Facilitate a relationship with the Citizen user
-- "We're obligated, as the government, to provide avenues for folks who need to ask for additional help." – Agency employee
- Increased process efficiency
-- "Citizens could do all their registrations online, but many choose to fax in their forms. I am trying to move us away from that system – we have employees that have to walk to the fax machine every 20 minutes." – Agency employee
- Modern, advanced look and feel
-- "We are still in the paper world. We're working through the electronic version process, but it is going to be difficult to get rid of paper." – Agency employee
- Real-time, more accurate information flows
-- "Name changes are really difficult. Even the number of characters in a name can stymie a system. Multiple-hyphen last names are difficult" – Agency employee
-- "Information is constantly changing. If citizens get married, if they move, etc. things change and their status changes – which informs the adjudication around certain benefits. Agencies have to constantly verify and keep up with those changes, which is difficult." – Agency employee
- Clean, intuitive design
Core functionality:
- Agency user should be able to choose which of their agency's programs (e.g. Passport Services, Visa Services) and corresponding benefit/services applications (e.g. New Passport Application, Passport Renewal Application) are present on the Citizen-user interface.
- Agency user is notified when a Citizen user has submitted an application for one of these services / benefits
- Agency user can view submitted applications in the order in which they were received in an "inbox-like" screen/view
- Agency user can either review the application on the screen, download it, or print it for additional processing off line
- Agency user can open the application within the Portal for review, make a decision based on its contents, and communicate to user whether application has been approved, denied or more information is required
- Agency user can share important information with the user, such as upcoming deadlines or expiration dates (e.g. deadline for Passport renewal, travel alerts, etc.)
- For each application, Agency user can set the following requirements:
-- Eligibility: Define the attributes required from citizens in order for the Agency to verify identity and adjudicate services accordingly. For example, in the case of a Passport application, requirements may include name, address, birth date, proof of citizenship, SSN, etc.
-- Product/Service Specifications: Define specifications and/or functions that a user could choose from and would be available as a choice on the Citizen-user interface. For example, in the case of a passport application, users would need to specify if they desire a 28-page or 56-page booklet, expedited shipping options, or a leather-bound cover in which to house the passport.
- Agency user can view a summary of submitted applications, including:
-- How many are currently in the inbox?
-- How many have been submitted over the last day, week, year (e.g. line graph over time)?
-- How many deserve immediate attention based on how long they have been sitting in the "inbox" and desired processing/response times?
Existing Artifacts
Wireframes - we recently ran a wireframe challenge through Topcoder and have a great starting point for the page layout, information architecture, and navigation for the "Citizen-user" view of this site. Please refer to the attached Citizen-user wireframe to understand the Citizen process.
We now need to create the "Agency-user" view, and we are asking each IA to essentially pick up where the Citizen-user facing wireframes left off. Essentially we want to design the agency user screens and experience which is basically the next step of the process after a citizen elects to submit information to apply for a product/service and that information is transferred to the agency for review and approvals.
The two wireframes (e.g. citizen user & agency user) should show opposite sides of the same transaction – e.g., you should be able to follow the Passport application transaction as it moves from the Citizen wireframes to the Agency-user wireframes:
- The Citizen-user wireframes (see attached screen 6. "Application Status") show the creation of a verified identity credential, which is then used to populate and submit an application for a benefit/service provided by a specific Agency program (e.g. passport renewal in the wireframes)
- The Agency-user wireframes should show how that application is received via an inbox-like screen as soon as the application is submitted by the citizen (see attached screen 6. "Application Status" – once a user submits this the application enters phase 2 which is "Credential Approval" – at this point the process hands off to the agency user).
-- Once opened in the inbox application - the Agency user should be able to see all of the information the Citizen user entered to complete the application
Suggested Screens for Agency User
For this wireframe challenge, it is important to note that we would like you to think through which pages are necessary and how to layout the above functionality. We would like to see your suggestions for a clear information architecture and beautiful user experience. Below are a list of suggested screens for the Digital Identity Agency-user experience. Please note that these are merely suggestions – if you can think of ways to lay out the above functions and features to improve the user experience, please do. If you need to combine or alter suggested screens, please do.
1. Login Process vs. Home Screen vs. Dashboard
- When an Agency user logs in, he / she is aiming to accomplish one of the following tasks:
-- Manage Programs / Applications through the platform
-- Review and Approve or Deny Applications from Citizens
-- Push alerts / notifications out to the citizen-end users
- Based on your understanding of the above core functionality, the citizen end-user screens, and these three major tasks – how can you design the log-in process so that a user is quickly able to accomplish his / her task?
-- Is a user presented with options as to his / her goal that facilitate navigation?
-- Is there a homepage or a dashboard for the tool and if so what information is on it?
-- How else might you make this platform very easy to understand, navigate, and accomplish these tasks?
2. Programs/Applications Management Screen
- A program (e.g. Passport Services) is designed to deliver specific benefits/services (e.g. Passport) to Citizens. One Agency may have multiple programs. An application is the method through which Citizens submit information pulled from their digital identity thread to request access to a program's products or services (e.g. New Passport Application). One program may have multiple applications for the different benefits/services provided.
- Screen should allow the Agency user to add, edit, or remove programs that fall within an Agency's jurisdiction (e.g. if the Agency is responsible for supporting international travel, some of the programs the Agency user could add, edit, or, remove would be "Passport Services" or "Visa Services")
-- If the Agency user is adding a new program, he could be asked to include:
---- The title of that program
---- A description of what that program does and the benefits/services it provides to Citizens
-- Upon creation of a program, the Agency user could be prompted to add an Application for that Program
- Screen should allow the Agency user to add, edit, or remove applications that fall within a program's jurisdiction (e.g. if the program is Passport Services, some of the applications the Agency user can add, edit, or remove would be "New Passport Application" or "Passport Renewal")
-- If the Agency user is adding a new application, he could be asked to include:
---- The name of the application (e.g. Passport Renewal)
---- The official government document used to apply (e.g. a current application form)
------ If the Agency user uploads an official document, the Portal would set requirements for the application from that document
------ If the Agency user does not wish to upload an official document, they can manually select required data fields at this point
---- The expiration date of the product/service (e.g. one year, five years, for life)
---- The program responsible for reviewing the application (e.g. dropdown list of programs for whom this Agency user is authorized to create applications)
3. Digital Application "Inbox"
- Screen should allow the Agency user to review submitted citizen-user Application information
-- Screen should communicate metadata about the Applications submitted by citizens for respective services such as data fields submitted, name of the applicant, time submitted, etc.
-- Screen should have a search functionality
---- Agency user should be able to "pin" applications for further review
-- Screen should make clear if there are new incoming Applications and feature a summary of applications currently in the "inbox"
---- How many are currently in the inbox?
---- How many have been submitted over the last day, week, year (e.g. line graph over time)?
---- How many deserve immediate attention based on how long they have been sitting in the "inbox"?
---- Summary could feature a "pie chart" that illustrates applications by how long they have gone unaddressed (breakdown is notional)
- 1 – 3 days old applications are green
- 3 – 7 days old applications are yellow
- 7 days+ old applications are red
-- Screen should be able to mark applications that have been expedited by the citizen user and therefore should receive attention first
-- For each application, the screen should communicate options for the Agency user to address it including:
---- "Download", "Print", "Confirm or Deny Application"
4. Adjudication ("Confirm or Deny Application") Screen
- Once the Agency employee clicks on the "Confirm or Deny Application" option, then the employee is brought to a screen that allows for the adjudication (i.e. yes/no decision) of the application
- This screen should communicate high-level details of the applicant's information with the ability to click to view more detailed information
- At the bottom or top of the screen, there should be three buttons that communicate adjudication options for the application
-- Button one: "Yes" – application is accepted
-- Button two: "No" – application is rejected
-- Button three: "More information is required" – application is sent back to citizen user with explanation of what additional information is needed
5. Communications Management
- Screen should allow the Agency user to add, edit, or remove communications
-- Agency user can choose to create either notifications or alerts
---- A notification is an automated prompt to the citizen user based on business rules (e.g. expiration notification to go out to citizen user 6 months before expiration date)
---- An alert is a program-wide communication written to convey program news and changes (e.g. all Passport owners may no longer wear glasses in their Passport pictures)
---- Manual pushes of information to an individual applicant
6. Other screens up to your discretion!
- As mentioned above we are looking for wireframes that create an intuitive and seamless user experience. Outside of the suggested screens above - are there any other functions or features that you would recommend? Consider how an Agency user might want to review applications as they come in.
- Additionally, these screens are merely suggestions. If you can think of a better way to lay this out – please do!
Things to consider for intended user:
- Why is he/she opening this web application in the first place? What is he/she looking to do?
- What is the "first experience" when opening the application? What is the primary goal of the application and experience?
- What are the priority actions or items a user needs to interact with?
Desired Brand Attributes:
- Should be clean & intuitive (must not add complexity or confusion)
- Should be concise with clear calls to action
- Should be efficient – it should be clear to the employees that this tool is designed to make their lives easier and more streamlined
Design Inspiration:
- Simplicity: The website should display various levels of priority for different applications; include a search box to sort through email; and provide the option to categorize applications (e.g. Google Inbox)
- User-Centricity/Personalization: The site should be personalized for those visitors that have logged in and feel like it is catering to a visitor’s specific needs (ex: GrubHub, Netflix)
- Consistency: Each screen should contain a similar design and maintain a high level of consistency throughout the process
- Efficiency: The interface should allow the Agency user to complete the task in the most efficient way possible. What is the user trying to achieve? What functions does it need to have? How can you design an interface that lets the Agency user accomplish what he wants and needs to do?
Attached Documentation:
- Citizen-user wireframes
- Challenge Goal diagram
Target Devices:
- Desktop (1280px)
****Please note**** The final solution will be a fully responsive web application. Please consider this as you design your desktop layouts so that these designs are scalable for other device sizes.
Wireframe Expectations:
- Produce HTML click through wireframes that can be used to demonstrate all mentioned functionalities as required in each round.
- The website must be very easy to use and intuitive. Keep that in mind when designing your solution.
- You MUST cover all screens mentioned in required sections below, if any requirement is missing in final submission the client will not look at it, so make a checklist for the required screens to make sure you designed all of them.
- Please show us your proposal as a movie or series of wireframes that communicate the user’s intended interaction with your proposed solution.
- You MUST use wireframes note pane in every single page you design to explain what items are addressed in that page from the documentation, what things you added/changed/removed, use it to make your idea clearer and help the client to give you constructive feedback.
Learn Axure:
New to Axure? Here are some quick tutorials to help you get started.
http://www.axure.com/learn
Judging Criteria
- User Experience of application.
- Completeness and accuracy of the wireframe as defined in the spec requirements.
- How well your wireframes provide a consistent user flow.
Submission & Source Files
Preview Image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
Generated HTML files with all the requested contest requirements stated above.
Source Files
Wireframes should be built in Axure. The resulting files should have generated HTML files. Also, all the content must be listed and the pages are linked together to show page flow.
Final Fixes
As part of the Final Fix phase, you may be asked to remove, update, or change some features of the wireframe.
Please read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. It is important that you monitor any updates provided by the client or Studio Admins in the forums. Please post any questions you might have for the client in the forums.