In the past two posts in this series, we looked at the need of following a user-first design approach to enterprise software implementation instead of a system-driven approach, as well as the steps involved. In this final post in the series, we will dive deeper into rapid visualizations, a cornerstone of Rapid Design & Visualization, and the role prototyping plays in enhancing or customizing the design of SaaS solutions.
The old adage, “a picture speaks a thousand words” captures what user interface prototyping is all about: using visuals to describe thousands of words’ worth of design and development specifications that detail how a system should behave and look.
In an iterative approach to user interface design, rapid prototyping is the process of quickly mocking up the future state of a system, be it a website or application, and validating it with a broader team of users, stakeholders, developers and designers. Doing this in a rapid and iterative manner generates feedback early and often, improving the final design and reducing the need for changes during development.
My previous post described why we should follow a user-first, design-led approach to enterprise software implementation instead of a system-driven approach. Yes, even with modern user interfaces like Salesforce Lightning, SAP Fiori & UI5, Pega, or SharePoint on Office 365. The benefits include saving time and money, easier implementation and roll-out, and satisfied (and happier) users.
This post describes our process, a focused version of Rapid Design & Visualization (RDV), Capgemini’s user-centered design methodology.
Software implementations today are different from what they were just a few years ago. Gone are the days when software packages were implemented with little to no opportunity for customization and could only be run on computers in an office. Users were an afterthought and had to deal with a steep learning curve. They also had to adapt their processes to the software.
Fast forward to today, when we have Software as a Service (SaaS) disruptors like Salesforce, and traditional software like SAP and SharePoint that look nothing like their earlier versions. Software today is increasingly available:
- in the cloud,
- with modernized interfaces,
- featuring responsive designs that work across desktop and mobile devices,
- is more usable out of the box, and
- the user interface is constantly being improved.
The Internet of Things is here to stay. Bain predicts that annual IoT vendor revenues could exceed $450 billion. That same survey found that about 90% of respondents remain in the planning and proof-of-concept stage and only about 20% expect to implement solutions at scale by 2020. At CES this year, apart from the theme of “Alexa everywhere”, there were many examples of existing products becoming smart and connected.
Ask 10 people for a definition of IoT and you will get a dozen different answers. My favorite definition is from openSAP combined from by Gartner, Wikipedia, and Digital Trends,:
“The Internet of Things (IoT) is the network of physical objects that contain embedded technology to sense and interact with their environment and each other to collect and exchange data to make our lives better.”
There are over 2 million iOS apps and almost as many Android apps, in a growing app economy. However, for every Flappy Bird app that gets lucky and goes viral, there are thousands of apps that take time and hard work to launch, and persistence to maintain, grow and avoid the app graveyard. While we typically hear about overnight success stories, this article explores the more typical experience of an appreneur, or app entrepreneur.
I spoke with one such appreneur, Amit Murumkar, about his journey with Canvsly over the past 3 1/2 years. Canvsly helps parents capture and store their children’s artwork for posterity and avoid the piles of paper.
Noah was concerned. He was the “UX Guy” for the corporate office of a regional Quick Service Restaurant (aka fast food chain) that was in the process of creating a mobile app that would allow their customers to customize their meals, place orders and earn rewards. He had been seeing users’ expectations increasing, and they were less forgiving of poor mobile experiences. That’s why he firmly believed that it was important to test the usability of their mobile user experience given users’ higher expectations, smaller screens, and constraints of wireless, battery-powered devices. Noah was concerned because he had never conducted mobile usability testing, even with years of traditional usability testing experience. That, and the fact that the first round of testing was just a month away.