Warning: Cannot modify header information - headers already sent by (output started at /webroot/b/e/benedi1/primary/www/wp-content/themes/bloghill/inc/sections/project.php:211) in /webroot/b/e/benedi1/primary/www/wp-includes/rest-api/class-wp-rest-server.php on line 1723

Warning: Cannot modify header information - headers already sent by (output started at /webroot/b/e/benedi1/primary/www/wp-content/themes/bloghill/inc/sections/project.php:211) in /webroot/b/e/benedi1/primary/www/wp-includes/rest-api/class-wp-rest-server.php on line 1723

Warning: Cannot modify header information - headers already sent by (output started at /webroot/b/e/benedi1/primary/www/wp-content/themes/bloghill/inc/sections/project.php:211) in /webroot/b/e/benedi1/primary/www/wp-includes/rest-api/class-wp-rest-server.php on line 1723

Warning: Cannot modify header information - headers already sent by (output started at /webroot/b/e/benedi1/primary/www/wp-content/themes/bloghill/inc/sections/project.php:211) in /webroot/b/e/benedi1/primary/www/wp-includes/rest-api/class-wp-rest-server.php on line 1723

Warning: Cannot modify header information - headers already sent by (output started at /webroot/b/e/benedi1/primary/www/wp-content/themes/bloghill/inc/sections/project.php:211) in /webroot/b/e/benedi1/primary/www/wp-includes/rest-api/class-wp-rest-server.php on line 1723

Warning: Cannot modify header information - headers already sent by (output started at /webroot/b/e/benedi1/primary/www/wp-content/themes/bloghill/inc/sections/project.php:211) in /webroot/b/e/benedi1/primary/www/wp-includes/rest-api/class-wp-rest-server.php on line 1723

Warning: Cannot modify header information - headers already sent by (output started at /webroot/b/e/benedi1/primary/www/wp-content/themes/bloghill/inc/sections/project.php:211) in /webroot/b/e/benedi1/primary/www/wp-includes/rest-api/class-wp-rest-server.php on line 1723

Warning: Cannot modify header information - headers already sent by (output started at /webroot/b/e/benedi1/primary/www/wp-content/themes/bloghill/inc/sections/project.php:211) in /webroot/b/e/benedi1/primary/www/wp-includes/rest-api/class-wp-rest-server.php on line 1723
{"id":58,"date":"2014-09-25T16:07:58","date_gmt":"2014-09-25T16:07:58","guid":{"rendered":"http:\/\/www.benedictireland.com\/?p=58"},"modified":"2016-02-04T12:54:55","modified_gmt":"2016-02-04T12:54:55","slug":"designing-for-banking-mobility","status":"publish","type":"post","link":"http:\/\/www.benedictireland.com\/?p=58","title":{"rendered":"Designing for banking mobility"},"content":{"rendered":"

Banks aren\u2019t thought of as \u2018helpful guardians of financial wellbeing\u2019, but as unflinching holders of \u2018our\u2019 money. Existing mobile banking experiences do little to counteract this, and don\u2019t take into account the users needs and context. User\u2019s we\u2019ve interviewed want help managing their finances. This doesn\u2019t mean an interview with a bank manager, but nudges when they are spending a bit too much, or a pat on the back when they\u2019re saving.<\/p>\n

With increased competition, ever-stricter regulation and government switching legislation, loyalty to banks is at a low point. To turn that around, we need to respond to customer needs and take a look at how they actually want to manage their finances.<\/p>\n

Branch-centric banking customers are generally more accepting of wait times, and more accustomed to visiting the branch to perform banking tasks. When necessary, they will call or use an ATM, and rarely will they log onto their account online. But this behaviour is changing.<\/p>\n

Customers are increasingly embracing mobile technology, and the expectation is now that their banking relationship can be handled through their mobile device. For many, it\u2019s the primary device, it\u2019s with them all day long, and many other customer experiences are served through it. Leveraging that behaviour is key to generating reliance and loyalty.<\/p>\n

So we need to be on their mobile devices, providing the services they need. Balance and activity, Forecasting, Mobile payments and transfers, Savings and debt reduction, and Education and support are all identified as critical by users.<\/p>\n

 <\/p>\n

5 top tips for banking mobility<\/strong><\/p>\n

1) App or responsive website?<\/em><\/p>\n

To begin the digital relationship, the website is often the first port of call. However, once behavior becomes more frequent, users tend to download an app. For an account servicing banking experience, an app provides enormous power. The ability to work offline for certain tasks (balance caching), and to maintain a logged in state behind a simple passcode, apps provide a far faster, more mobile-appropriate experience. Ideally, you\u2019ll provide both.<\/p>\n

2) Offer the appropriate features<\/em><\/p>\n

It\u2019s tempting to provide a fully featured experience, in which a user can perform any task they want to. But is that absolutely necessary? 80% of the time, a user wants one of very few tasks: Balance, Alerts, Payments and transfers. So focus on doing those brilliantly. This can inform build priority, and ultimately allow you to get to market faster.<\/p>\n

3) Design for interruption<\/p>\n

It\u2019s tempting to assume users always finish the task they start. The reality is, when they are on their mobile device, they\u2019ll get interrupted.\u00a0Bus stops, network interruptions, bumping into a friend or just watching TV. Tasks get interrupted frequently.\u00a0Ensuring that the user is secure and logging them out is good, but ultimately often means they\u2019ll have to start again, resulting in frustration. Providing fast, pre-authenticated log in methods and caching or saving progress will go a long way to ensuring the user does complete their task.<\/p>\n

4) Consider the platform<\/p>\n

Most banks have strong brands, designed to differentiate them from their competition on the high street. All offline literature is heavily branded, and adverts immediately identifiable. However when the user is on their device, over-branding the interface can create a negative experience as a whole. The user will be used to their device, the way it works and the way Ui controls like drop menus work. Coding appropriately you\u2019ll leverage the learned behaviours of the users device, and more carefully consider the usage of branding. Platform-agnostic information architecture design means we can design a single set of features and services, which can then be quickly appropriated to various platforms and OS\u2019s. Android (and now iOS) devices have NFC. They also have different links to the OS controls, different user interfaces, and different task focuses. Respect the user\u2019s digital environment and you\u2019ll make them more comfortable using your products.<\/p>\n

5) Deliver task-focused experiences<\/p>\n

When you\u2019re paying for lunch and need to know your balance, you don\u2019t want a welcome screen and sales messages getting in the way. Focus on the users tasks, and leave the rest behind. Speed and simplicity provide the key to making your product usable.<\/p>\n

Allow the customer to quickly get to the functions they need, when they need them. This will mean focusing the experience on the core functions, and leaving less important functionality a click away in the UI. Context is another important factor, allowing us to further tailor the experience. If we know the user has just gone overdrawn, we can tell them. We can even provide them the next action: \u2018Transfer money from your savings account, madam? Certainly.\u201d Focusing on the task at hand usually means providing clear, linear journeys, with the shortest number of steps possible. Removing the requirements to gather additional information in a sign up or registration journey is far more likely to result in the user completing that task, and using your product more and more frequently. Making their banking easier.<\/p>\n","protected":false},"excerpt":{"rendered":"

Banks aren\u2019t thought of as \u2018helpful guardians of financial wellbeing\u2019, but as unflinching holders of \u2018our\u2019 money. Existing mobile banking experiences do little to counteract this, and don\u2019t take into account the users needs and context. User\u2019s we\u2019ve interviewed want help managing their finances. This doesn\u2019t mean an interview with a bank manager, but nudges…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[2],"tags":[],"jetpack_featured_media_url":"","_links":{"self":[{"href":"http:\/\/www.benedictireland.com\/index.php?rest_route=\/wp\/v2\/posts\/58"}],"collection":[{"href":"http:\/\/www.benedictireland.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.benedictireland.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.benedictireland.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.benedictireland.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=58"}],"version-history":[{"count":2,"href":"http:\/\/www.benedictireland.com\/index.php?rest_route=\/wp\/v2\/posts\/58\/revisions"}],"predecessor-version":[{"id":60,"href":"http:\/\/www.benedictireland.com\/index.php?rest_route=\/wp\/v2\/posts\/58\/revisions\/60"}],"wp:attachment":[{"href":"http:\/\/www.benedictireland.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=58"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.benedictireland.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=58"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.benedictireland.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=58"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}