From napkin sketch to functional artifact
Analysis, synthesis and data architecture
After spending several hours staring at the diagram, I was able to identify and decompose the main component pictured above: a table with different values, input fields, and information that needed to be displayed in a clear way for users to access and interact with their queries.
Identifying this component allowed me to ask the right questions, clarify what was of higher importance and what could be removed or displayed as secondary information.
What I learned from this project
Collaboration is key
In a span of four weeks, I presented my work over multiple conversations with back-end and front-end engineers. By asking questions, taking notes and pushing forward, my understanding the technical aspect of the project expanded and the end result was a byproduct of that.
Simplify complexity
Even when something appears to be technical and complex, their main components can be understood and brought to simple terms. By leaning into information architecture and hierarchy, asking questions and focusing on smaller parts of the whole.
End thoughts
The aim of this project was to ship a good minimal version of the product for initial testing with a highly technical audience. We accomplished that with a short sprint, focused on half of the complete product. After a month, we completed and launched the product, simplifying the way in which users created their contracts and registered them in Lagrange's zk network.
Contract registration
Alternatives for time visualization
In 2024, Lagrange launched their dashboard and tool to make it easier for developers to register their contracts and queries and make use of their zero knowledge technology. I led in various capacities—research, product, and interface design—and collaborated with engineers to fully conceptualize the features and product details.