Easy Bill

Easy Bill is a mobile web page for users who use Digiturk set-top boxes in their homes; to track and pay their monthly bills quickly and review details from their mobile phones. Here I was responsible for the design of Easy Bill as a Senior Product Designer.

The goal of the project

To send detailed e-invoices to users every month, direct users to e-invoice, and decrease the printed invoice usage.

How will the system work?

  1. An SMS will be sent to users every month.
  2. The SMS will have a link to direct users to the mobile webpage.
  3. On this page, there will be usage details, discounts, and pay-and-watch content.
  4. When the user clicks to pay button, they will be directed to the Digiturk Online Transactions page to pay the bill.

Data collection

I collected existing printed invoice samples from the finance department. The important issue here was to compare the billing information of users who use 1 set-top box at home and users who use more than 1 set-top box.

Mockups

I prepared mockups for these two different types of users. 

Prototypes

Then I created the prototypes. After discussions and feedback sessions with stakeholders, I finalized the prototype studies.

User testing

I decided on main research topics and prepared questions for 8 real Digiturk users to test the prototypes.

Some of the questions are as below;
  1. Are the elements used in the interfaces understandable?
  2. Is the hierarchy of the given information correct?
  3. Is the information given in the interfaces understandable? Is it enough?
  4. Is the user sufficiently guided while performing the action?
  5. Can users easily find the information they are looking for in the existing prototype?
  6. Is the total amount to be paid clear?
  7. How should the billing titles be in memberships with a side room membership?
  8. How should the campaign discounts be displayed?
  9. Should prepaid amounts be included in the invoice?
  10. The display of the contract expiry time and the number of days watched leading to the partial price is clear and sufficient to me.
  11. Are the concepts of Packages and Additional Services understood by the user? How should grouping be done?
  12. Do users want to see all the information on the invoice on the digital invoice?
  13. Are users looking for the serials service as additional services or under packages?

User test results

I have ranked the results in order of importance. Together with the stakeholders, we decided which items I should update. (Green zones are translated only.)

UI

According to the results, I studied the designs on Sketch. As a result of short meetings with stakeholders, I finalized the designs. I integrated the final designs for the software developers into the Zeplin application.