Case Study
Embraer Code AI
1.1 Challenge
Generate clean and reliable code. Easy.
How to make the experience of use Tardis more easier and reliable than write a code?
Authentication, application layers, endpoints. Tardis is capable of do that in seconds, but how to make developers trust that code is ready for use?
steps of process
from research to launch
1. Discovery
How Tardis should work, behave and look?
The starting process was try to undestand what things already exist who solves similar problems. Doing deep structured interviews with potential users and stakeholders i was able to gather information about the developers preferences, flows and journeys that they are already use to.
That was a great point for the research, cause decreased the learning curve and made me understand how the Tardis tool works.
Product vision
Flows and user journeys
2. Ideation
Coming up with some solutions
After sessions of interviews and co-creation sessions with the stakeholders, we reached out enough information to start drawing solutions.
wireframes
What we'll need in each feature
3. Prototypes
Coming up with some solutions
After sessions of interviews and co-creation sessions with the stakeholders, we reached out enough information to start drawing solutions.
Architectural works, in the material form of buildings, are often perceived as cultural symbols and as works of art. Historical civilizations are often identified with their surviving architectural achievements.
Design system
components and style guide
4. Testing and new features
Usability score and improvements
After implementing the main features, I created a Usability Score to measure the evolution of the ease of use of the Tardis and its features. Sent to a group of key users, it returned a score above the market average and is an important metric to measure the evolution of the product.
Let´s
work
togheter!
Contacts
Magnocalderon@gmail.com
BR +55 11 97031-5955
IT +39 328 232 0412
