Road mapping from Design to Development
In my last blog post I discussed the process of going to an application developer and estimating how long a build would take. Specifically, the redesign of the mobile experience that myAT&T offers for iOS.
Since then I have mapped out the road map to bringing the design into reality based on the estimations that came out of the developer meeting.
I approached this task through 2 lenses simultaneously. The first was assessing what unique capabilities and benefits does using your AT&T application on mobile have as opposed to a brick and mortar store or the online web application. The mobile application is unique in that you can access it anywhere, at anytime. Filtering through the tasks deemed most important from our user research:
- Make a payment and set up Automatic payments
- Suspend or remove a device
- Change a plan
- Set and update account security
- Compare usage to available plans
- Upgrade a device.
What is most important? How does the mobile app make any of these more valuable?
Changing a plan
The reasoning behind a user changing their plan comes down to how much they are using their phone. Usually people use more data than they have allocated for themselves. Therefore when you are nearing your data limit, if your phone reminded you of that unfortunate event and you had the myAT&T application you could change your plan right then and avoid future charges.
The second lense that I assessed things through in parallel to the first was the fact that this is a mobile application. It being a mobile application that houses sensitive data and potentially vulnerable actions means it needs to be secure. For this reason, partnered with developing the Change a plan flow I developed the Login, Add Card, and Add billing address flows simultaneously.
This development method of moving forward the functionality that was pertinent to the mobile medium as well as functionality that was pertinent to the user felt like an effective plan for providing value to the parties that really matter.