Challenge Summary
Welcome to the "Global Financial Institution - Crisis Management Platform Wireframe Challenge". In this challenge we are looking for responsive wireframes (desktop, tablet and mobile) that help managers at a large global financial institution (FI) to predict, detect, monitor, and react to critical enterprise-related events that may affect the FI.
We are looking for your expertise related to how to best present the information to the user and create a clean UX across desktop and mobile. Good luck and looking forward to your ideas!
Round 1
Your initial wireframes for client review.
Round 2
All requirements as stated in challenge details with client feedback applied.
A large global financial institution that serves individual customers, businesses, and capital markets seeks to gather, analyze, and report on prioritized actions in order to prevent and respond to critical enterprise crises. Crisis events could be things like a cyber attack or a large corporate customer going bankrupt. Basically, we’re talking about events that span across geographies and/or business lines and have the potential to affect the entire enterprise (examples of two such crisis event scenarios are detailed below).
For the purposes of this challenge, we are only focusing on the two crisis events listed below and the outcomes of those events. If you can think of common actions to additional related scenarios, feel free to include these features as well.
We are looking for dynamic wireframes that alert the user, help the user monitor the events, and visually present solutions and strategies for how to solve them. The user is able to do this through a few key screens and through a series of processes and required functionality. We are looking for you to analyze the problem and propose a solution for what screens are needed and the best way to present the information/ functionality on those screens.
Required Screens/ Functionality:
These are not explicit requirements for screens and how they should be organized. If you think there is a better way to organize the content in different screens or in a different order please show us. We are open to your ideas on what is the best user experience based on the content and required features and functionality.
Screen 01 - Dashboard
- Allows user to receive alerts for potential or actual crisis events. Think more robust alerts than just standard app alerts/ notifications. There should be more context and information presented or available. This could also incorporate monitoring of operational processes / technology to create a "healthcheck" view.
- View a list of current events that have happened (based on internal and external data). Think about information flows from News sites or information suppliers (e.g. market data vendors, credit rating agencies, etc.)
- View a list of potential crisis events / scenarios and what their probability is of them actually happening. In other words, the app needs to correlate information to be predicative around potential events.
- Monitor and review current crisis events
- Select crisis areas of interest to view more details about the specific event or operational process. This could include a quick informative note via hover or the ability to dive into greater detail.
Screen 02 - Critical Crisis Event Detail
- Clicking on a specific crisis event will take the user to some kind of details screen
- Help users to understand more about the crisis event
- Output updated information including documents such as plans & playbooks pertaining to this specific crisis
- Review list of potential decisions (activation of playbooks, internal and/or external communications, raising capital, etc.) and how those would impact the crisis event and the FI
Key and Required Features:
These features must appear within your wireframes and be as user friendly as possible. How these get worked into your solutions and what screens they belong on is up to you. Again, we are looking for your expert UX skills to make the best experience :
- Search (systematic or user initiated)
- Correlation (i.e. how are events connected, actions specific to the actual user)
- Alerting and Notifications
- Scenario Analysis: Allowing the user to analyze the severity of the event/ scenario that they have been alerted.
- Different views/filters for different users (some may be individual customer-centric while other may be concerned with just capital market events)
- Document Linkage with process support
Event Scenarios:
A global financial institution with consumer, commercial, and capital markets businesses needs a platform that is able to gather and correlate structured (possibly currency exchange rates or portfolio positions) and unstructured data (news articles and sentiment) from internal and external sources. They need to be able to view alerts and triggers, list actions (both completed and suggested) and view/select the tools to accomplish them (plans & playbooks) and view the modeled results so that executives can make the best informed decisions possible.
There are 2 critical events scenarios that we would like you to use for the purposes of this challenge, based on the problem statement above. How would a application help to predict a scenario, show the correlation between many scenarios, and enable someone to react to a scenario?
Scenario 1: UK withdrawal from the European Union
Potentials effects:
- Rapid devaluation of Pound Sterling (GBP)
- Increased volatility in foreign exchange rates, equities, and related derivatives markets
- Capital flight (people taking money out of a country or financial institution)
Scenario 2:ATM Network cyber attack
Potential Effects:
- Reputational impact for the financial institution
- Increased volume of teller requests for cash
- Core system contagion / isolation (action by the FI)
- Increase in credit card usage / utilization
Target Devices
Make sure that your solutions and layout adapt and work on all devices. Think about how inputs, navigation, functionality, etc. will need to change. Make sure you are following responsive design best practices and current designs trends
- Desktop - 1280px (height can expand as needed)
- Tablet - 1536 x 2048px (height can expand as needed)
- Mobile - 640 x 1136px (height can expand as needed)
Target User
- Senior corporate managers that lead a business, operations or technology group (and thus need to react to an event that negatively affects the group they manage)
Learn Axure:
New to Axure? Here are some quick tutorials to help you get started.
http://www.axure.com/learn
Judging Criteria
- Overall User Experience
- Completeness and accuracy of the wireframe as defined in the challenge spec
- How well your wireframes provide a consistent user flow.
- How well your wireframe captures all the functionality.
- Any suggestions, interactions and user flows you recommend (provide any notes or comments for the client).
Submission and 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 as clickable HTML files generated by Axure. All the content must be listed and the pages are linked together to show page flow.
Source Files
- Wireframes should be built in Axure. The resulting source files used to generate the clickable HTML files.
- All the content must be listed and the pages are linked together to show page flow.
- All fully editable original source files of the submitted wireframe as required by the contest under "Source Files" in the sidebar should be included in your Source zip file.
Final Fixes
As part of the final fixes phase you may be asked to modify content or user click paths.
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.