Challenge Summary
Welcome to GE - Risk Assessment Tool Wireframe Challenge!
We are please to bring another GE project to the community. The Risk Assessment Tool will help our customer to manage and control possible risks that happen around the business. The application is very simple, we require your skills and imagination to represent data the best way possible.
You’ll be creating a brand new wireframes solution - with Axure - that covers the requirements of the application, translating them into an easy-to-understand workflow.
Best of luck!
- 1. Login
- 2. Dashboard
Add notes explaining your solution.
- 1. Login
- 2. Dashboard
Add notes explaining your solution.
The goal of this challenge is to create clickable wireframes that fulfills the requirements of the GE Risk Assessment application. It’s a simple application, however, a key point to consider is HOW YOU REPRESENT DATA. It’s quite important to be easily digestible at first sight, well thought and well organized. The information displayed helps to predict where the next miss might happen.
About GE Risks Assessment Tool
This application is being built with the intention of creating a conversation about risks a business can face and the controls in place to manage those risks. This app will allow users to collaborate on how likely a risk is to occur, by assigning it a position on a scatterplot. Other users can propose moving that risk to a different position on a scatterplot along with comments on why they think it should be elsewhere.
General Requirements
- 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 use cases mentioned in screens requirements and user roles below.
- You MUST use wireframes note pane in every single page you design to explain what cases/items are addressed in that page, what things you added/changed/removed, use it to make your idea clearer and help the client to give you constructive feedback.
Users
1. Corporate User (enters initial data, can edit/delete data - the only user who can perform these mentioned actions).
2. T1 Business User (makes edits to node locations, adds comments, cannot add new nodes).
3. T2 Business User (makes edits to node locations, adds comments, cannot add new nodes). Has an order participation difference in comparison with T1. See more below in the workflow.
4. CRB - Compliance Review Board. Compliance team shares status updates on the state of the program with the leadership teams within their businesses. Essentially, we want to make this meaningful for not only the corporate users but the businesses as well who have to present out data.
User Workflow
1. Corporate users create the intial scatterplots.
2. T1 Users log in and see what corporate created. They move things around with comments.
3. T2 Users log in, and see the combination of data from corporate and T1. They can see if something moved and the comments. They can move again and add comments of their own.
4. Corporate logs back in and can see how things ended up after others have edited and commented.
Screens Requirements
Business Document attached, shows the raw concept of the application.
Data Sample attached, shows some sample data (nodes).
1. Login
- All user groups should be able to login through the same page.
- Handle error and success cases respectively.
2. Dashboard
- The goal of this page is to provide a company wide assessment of control infrastructure to provide inputs to audit, compliance program priorities.
- This is a data-intensive page. Must be treated carefully to represent the meaning in a pleasant and understandable way to the users.
- The main display of this page is formed by Scatter plot graphs. It’s populated with risk areas (see sample) against likelihood to occur.
- Corporate user is the only user who can create risk graphs (scatterplots).
- Each risk graph must handle the following:
-- Title
-- Nodes (dots in the graph). At the same time, nodes handle the following:
--- Title: name to display if expanded (details view).
--- Label: short title to be used in the graph. See the Business Document page #3 (drill-down into details through labels to titles).
--- Position: initially parent nodes are added manually by the user (drag&drop, textboxes, up to you). If adding a child node, user should be warned that the location of the parent will be auto-calculated based on the child nodes.
--- Comments: added to a node or to a movement. If there is a user who moves/changes the position of the node, there must be a tied comment to explain the reason of this change.
--- Key controls
--- Assurance
--- Improvement
--- Priority
--- Action
- The app should handle node hierarchy and auto-positioning: not a data to show per se, a capability. The app must be wise in the way of showing nodes hierarchy. A node can have N amount of node children and ability to drill-down deep to each detail view of node, which is basically another nested scatterplot with more nodes. Once you add a child node underneath a parent, it should then be calculated from those children. If there are five child nodes, the parents position on its chart would be based on the average position of the five child nodes.
- User should be able to tell easily which ones have child data and which do not.
- All user groups move the ‘dots’ based on where they think the next breakdown will occur (input rationale). Also add comments if necessary.
- The app must provide a smart way of notifying users of recent updates, comments or movements in nodes made by other users. HOWEVER, we don’t want a notifications/activity page, panel or section. It has to be smartly introduced in the dashboard, probably marking nodes somehow that have recent activity (specially node movements)? We’re open to suggestions.
- There should be an option to use scatterplot in business CRBs, update. Real-time update to view on control effectiveness.
- User should be able to share results with Policy Owners, CAS, PCRB to define priorities for next year.
Screen Specifications
- Must support desktop view, 1280px width. Height as much as needed.
- The design implementation will support lower viewports (tablet/mobile). It’s not in scope for this challenge, however, it would be helpful to come up with a desktop approach that could be easily taken into lower viewports.
Target User
- Internal users who report and manage operational risks.
- Stakeholders who would view data input by the internal users.
Judging Criteria
- User experience.
- Completeness and accuracy of the areas of functionality and content.
- How well your wireframes provide a consistent user flow and clear information architecture for the application
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
All requested contest requirements/screens as clickable HTML files.
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.
We are please to bring another GE project to the community. The Risk Assessment Tool will help our customer to manage and control possible risks that happen around the business. The application is very simple, we require your skills and imagination to represent data the best way possible.
You’ll be creating a brand new wireframes solution - with Axure - that covers the requirements of the application, translating them into an easy-to-understand workflow.
Best of luck!
Round 1
Submit your wireframe for a Checkpoint feedback.- 1. Login
- 2. Dashboard
Add notes explaining your solution.
Round 2
Submit your final wireframe solution including updates from checkpoint feedback.- 1. Login
- 2. Dashboard
Add notes explaining your solution.
The goal of this challenge is to create clickable wireframes that fulfills the requirements of the GE Risk Assessment application. It’s a simple application, however, a key point to consider is HOW YOU REPRESENT DATA. It’s quite important to be easily digestible at first sight, well thought and well organized. The information displayed helps to predict where the next miss might happen.
About GE Risks Assessment Tool
This application is being built with the intention of creating a conversation about risks a business can face and the controls in place to manage those risks. This app will allow users to collaborate on how likely a risk is to occur, by assigning it a position on a scatterplot. Other users can propose moving that risk to a different position on a scatterplot along with comments on why they think it should be elsewhere.
General Requirements
- 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 use cases mentioned in screens requirements and user roles below.
- You MUST use wireframes note pane in every single page you design to explain what cases/items are addressed in that page, what things you added/changed/removed, use it to make your idea clearer and help the client to give you constructive feedback.
Users
1. Corporate User (enters initial data, can edit/delete data - the only user who can perform these mentioned actions).
2. T1 Business User (makes edits to node locations, adds comments, cannot add new nodes).
3. T2 Business User (makes edits to node locations, adds comments, cannot add new nodes). Has an order participation difference in comparison with T1. See more below in the workflow.
4. CRB - Compliance Review Board. Compliance team shares status updates on the state of the program with the leadership teams within their businesses. Essentially, we want to make this meaningful for not only the corporate users but the businesses as well who have to present out data.
User Workflow
1. Corporate users create the intial scatterplots.
2. T1 Users log in and see what corporate created. They move things around with comments.
3. T2 Users log in, and see the combination of data from corporate and T1. They can see if something moved and the comments. They can move again and add comments of their own.
4. Corporate logs back in and can see how things ended up after others have edited and commented.
Screens Requirements
Business Document attached, shows the raw concept of the application.
Data Sample attached, shows some sample data (nodes).
1. Login
- All user groups should be able to login through the same page.
- Handle error and success cases respectively.
2. Dashboard
- The goal of this page is to provide a company wide assessment of control infrastructure to provide inputs to audit, compliance program priorities.
- This is a data-intensive page. Must be treated carefully to represent the meaning in a pleasant and understandable way to the users.
- The main display of this page is formed by Scatter plot graphs. It’s populated with risk areas (see sample) against likelihood to occur.
- Corporate user is the only user who can create risk graphs (scatterplots).
- Each risk graph must handle the following:
-- Title
-- Nodes (dots in the graph). At the same time, nodes handle the following:
--- Title: name to display if expanded (details view).
--- Label: short title to be used in the graph. See the Business Document page #3 (drill-down into details through labels to titles).
--- Position: initially parent nodes are added manually by the user (drag&drop, textboxes, up to you). If adding a child node, user should be warned that the location of the parent will be auto-calculated based on the child nodes.
--- Comments: added to a node or to a movement. If there is a user who moves/changes the position of the node, there must be a tied comment to explain the reason of this change.
--- Key controls
--- Assurance
--- Improvement
--- Priority
--- Action
- The app should handle node hierarchy and auto-positioning: not a data to show per se, a capability. The app must be wise in the way of showing nodes hierarchy. A node can have N amount of node children and ability to drill-down deep to each detail view of node, which is basically another nested scatterplot with more nodes. Once you add a child node underneath a parent, it should then be calculated from those children. If there are five child nodes, the parents position on its chart would be based on the average position of the five child nodes.
- User should be able to tell easily which ones have child data and which do not.
- All user groups move the ‘dots’ based on where they think the next breakdown will occur (input rationale). Also add comments if necessary.
- The app must provide a smart way of notifying users of recent updates, comments or movements in nodes made by other users. HOWEVER, we don’t want a notifications/activity page, panel or section. It has to be smartly introduced in the dashboard, probably marking nodes somehow that have recent activity (specially node movements)? We’re open to suggestions.
- There should be an option to use scatterplot in business CRBs, update. Real-time update to view on control effectiveness.
- User should be able to share results with Policy Owners, CAS, PCRB to define priorities for next year.
Screen Specifications
- Must support desktop view, 1280px width. Height as much as needed.
- The design implementation will support lower viewports (tablet/mobile). It’s not in scope for this challenge, however, it would be helpful to come up with a desktop approach that could be easily taken into lower viewports.
Target User
- Internal users who report and manage operational risks.
- Stakeholders who would view data input by the internal users.
Judging Criteria
- User experience.
- Completeness and accuracy of the areas of functionality and content.
- How well your wireframes provide a consistent user flow and clear information architecture for the application
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
All requested contest requirements/screens as clickable HTML files.
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.