top of page

Anticipation: what it was like to build and release a new feature before all competitors

The Context

In Brazil, people are more familiar buying installments, and for not harm the sellers, the card machines offers a functionality to anticipate this installments.

For example: I salled a product that cost R$ 200, installments in 4X, I would receive R$ 50/month during four months, but if I antecipate, I will receive all the money in the same day!

​

The opportunite

Thinking about more flexibility for the sellers, the Central Bank of Brazil decided to desburocratizy this antecipations, now it could be not only directly with the card machine, but also in another financial institutions.

flow.png

The App

An app where you can manage all your sales, fees of transactions and more.

 

Complete management of your business?

​With this reduction of bureaucracy, now our user could have the COMPLETE management in the palm of his hand, without depending on other applications.

raiox.png

Fine, life is good. But how we could do that? 

The first step was understand the scenario with the team, that was product, customer success, marketing and UX. After that the four teams had each one a mission and goal, that was:

Product:

​Make partnership with the Registry (public company responsible for recording transactions), and find which informations are necessary to antecipate.

CS:

Understand all the process of anticipation and predict all the possible doubts that the user could have.

Marketing:

Share in the social medias and blog about what is the new debureaucratization and how it could benefit small business and big companies.

UX:

Plan a research to understand the user needs, why they anticipate? and how we could pass all this informations in a simple way.

Let’s work!

As a first step, me and my partner created a research planning, including:

  • Context; 

  • Goal; 

  • Deadline (we needed to be the first one in the market); 

  • Expected results; 

  • Next steps.

Why are our users anticipating today?

To answer this question, the CS team helped us get in touch with our users, and we got the necessary answers to our three questions about how is the context and experience nowadays with their card machine apps. They did a quick interview with 68 users through phone calls.

Why do you anticipate your sales nowadays?

71% 

Anticipate due to cash flow and/or working capital

What do you think about the experience?

86%

Had no problems and/or found the process okay

If you could anticipate the sales of all your machines in one place, what else would be important to you?

31%

I wish there were better tax than the card machines

26%

I would like it to be in a practical and functional way

análise de dados.png

Benchmarking: Taking a look at our competitors

Like 86% of the users in the discovery said that they had no problem antecipating with their own card machine, we decided to realize a benckmarking to understand the flow of each one, we can resume it in:

  • Select the value that desires; 

  • Confirm bank account; 

  • Security confirmation (a password); 

  • Transaction preview.

UserFlow: Points of contact

With the product team we created all the points of contact in the funcionality. We needed to predict all the possibilities inside the flow, pass all the right status for each situation, and how we would pass that.

​

With this information I started to create the screens, first wireframings and when the concept were finished, I did the high fidelity. The result it's right below:

screens.png

Not done, yet. Time to test the concept!

Usability test: First round

All the flow was okay 5/5 approved, the users felt a lot of similarity with what they already do in the card machine, but without the part of needs to enter in each app.

But a point of attention: 3/5 in the home page had some difficult to find the antecipation and 4/5 would like to know about the fee, previously.

result.png

Usability test: Second round

In this flow we had 5/5 approval, everyone was able to find the anticipation within the app and managed to perform the task of anticipating.

Next steps:​

  • Track application success;

  • Review all incoming tickets for the support team;

  • Review reviews in app stores.

Final considerations:​

​We had success in all the process, because all te teams were working together. The engineering team was always lined up about the concept that was being created. Anyway, the team work was responsible to release the new feature in time, and we were the first. 

bottom of page