The Challenge That Made Me Grow.
The Challenge That Made Me Grow.
Date. 2021 — 2025.
Company. Tinybird.
Role. Product Designer.
Services. UX/UI, Prototyping, Product Strategy, System Design, Dashboards, Iconography.
Tools. Figma, FigJam, Lottie, GitLab, Tinybird, FullStory, Screen Studio, Basecamp, Slack, Notion.
Situation — A Mountain of Data and the Race Against Time.
Situation — A Mountain of Data and the Race Against Time.
Tinybird had a clear promise: process real-time data and let users extract value from it in seconds.
Tinybird had a clear promise: process real-time data and let users extract value from it in seconds.
But there’s a big difference between promise and reality. The interface users worked with didn’t truly enable that speed. It wasn’t bad, but it was far from optimal. The structure had limitations that slowed down data exploration and manipulation.
But there’s a big difference between promise and reality. The interface users worked with didn’t truly enable that speed. It wasn’t bad, but it was far from optimal. The structure had limitations that slowed down data exploration and manipulation.
The consequence? Too much time lost between clicks, configurations, and unnecessary steps. And in a world where every second counts, that was not an option.
The consequence? Too much time lost between clicks, configurations, and unnecessary steps. And in a world where every second counts, that was not an option.
The team already had some clients and a functional product, but it was time to evolve.
The team already had some clients and a functional product, but it was time to evolve.
It wasn’t just about improving what existed—it was about rethinking the experience from the ground up.
It wasn’t just about improving what existed—it was about rethinking the experience from the ground up.
How could we make sure that any user, regardless of their technical level, could interact with an enormous amount of data in the most efficient way possible?
How could we make sure that any user, regardless of their technical level, could interact with an enormous amount of data in the most efficient way possible?
Task — Designing a Seamless Experience in Record Time.
Task — Designing a Seamless Experience in Record Time.
The challenge was clear: we had to turn a functional platform into a fast, intuitive, and powerful tool. Something that would let users build complex queries in seconds, with an interface that didn’t get in their way but instead enhanced their workflow.
The challenge was clear: we had to turn a functional platform into a fast, intuitive, and powerful tool. Something that would let users build complex queries in seconds, with an interface that didn’t get in their way but instead enhanced their workflow.
As a designer, my mission was to make all this technological power visually clear, easy to interact with, and—most importantly—fast.
As a designer, my mission was to make all this technological power visually clear, easy to interact with, and—most importantly—fast.
Working alongside one of the founders and a team of brilliant developers, we built a system that eliminated friction, reduced unnecessary steps, and maximized productivity.
Working alongside one of the founders and a team of brilliant developers, we built a system that eliminated friction, reduced unnecessary steps, and maximized productivity.
But I set one rule for myself from day one: design with the least amount of elements possible.
But I set one rule for myself from day one: design with the least amount of elements possible.
Why have five button styles when three were enough?
Why use nine shades of gray when three could do the job just as well?
Maximizing simplicity without sacrificing functionality was the key to ensuring that the system scaled without becoming an uncontrollable monster.
Maximizing simplicity without sacrificing functionality was the key to ensuring that the system scaled without becoming an uncontrollable monster.
Action — From Chaos to Clarity.
Action — From Chaos to Clarity.
The data doesn’t lie. So the first step was to analyze how users were interacting with the platform.
We used metrics, session recordings, and interviews with key customers. What we found confirmed our hypothesis: users were spending too much time navigating the interface and tweaking settings instead of actually analyzing their data.
Armed with this insight, we started designing solutions.
One of the biggest changes was in the visualization of Data Sources. Initially, we had a fixed container width, but customers using ultra-wide monitors wanted to take full advantage of their screen space. So, we redesigned the layout to expand to 100% width, significantly improving readability and efficiency in data analysis.
We also streamlined the query bar interaction, removing intermediate steps and allowing users to build queries more naturally and intuitively.
And yes, at Tinybird, we didn’t forget the small details that make users smile.
Whenever a customer successfully transformed their data into a functional API Endpoint, a burst of digital confetti appeared on the screen. Functionally? It did nothing. Emotionally? It made all the difference.
Customer reactions were immediate—they loved it.
It was a small celebration in an environment that could otherwise feel overly technical and cold.
The data doesn’t lie. So the first step was to analyze how users were interacting with the platform.
We used metrics, session recordings, and interviews with key customers. What we found confirmed our hypothesis: users were spending too much time navigating the interface and tweaking settings instead of actually analyzing their data.
Armed with this insight, we started designing solutions.
One of the biggest changes was in the visualization of Data Sources. Initially, we had a fixed container width, but customers using ultra-wide monitors wanted to take full advantage of their screen space. So, we redesigned the layout to expand to 100% width, significantly improving readability and efficiency in data analysis.
We also streamlined the query bar interaction, removing intermediate steps and allowing users to build queries more naturally and intuitively.
And yes, at Tinybird, we didn’t forget the small details that make users smile.
Whenever a customer successfully transformed their data into a functional API Endpoint, a burst of digital confetti appeared on the screen. Functionally? It did nothing. Emotionally? It made all the difference.
Customer reactions were immediate—they loved it.
It was a small celebration in an environment that could otherwise feel overly technical and cold.
Result — Speed, Clarity, and a Scalable Product.
Result — Speed, Clarity, and a Scalable Product.
The improvements weren’t just well received—they transformed the way users interacted with the platform.
The improvements weren’t just well received—they transformed the way users interacted with the platform.
Key metrics:
Key metrics:
48% reduction in the average time needed to build a complex query.
28% increase in successful, error-free queries.
22% fewer clicks required to convert data into an API Endpoint.
Significant adoption of ultra-wide monitors after implementing full-screen Data Sources view.
Beyond the numbers, the most important validation came from the users themselves.
Post-implementation interviews showed a high level of satisfaction.
The platform was no longer just fast at processing data—now, it was fast in interaction as well.
Beyond the numbers, the most important validation came from the users themselves.
Post-implementation interviews showed a high level of satisfaction.
The platform was no longer just fast at processing data—now, it was fast in interaction as well.
Final Reflections.
Final Reflections.
This project taught me one clear lesson: simplifying isn’t about removing—it’s about multiplying.
In design, there’s always a temptation to add more elements, more options, more features. But the real challenge is doing more with less.
Every design decision we made at Tinybird was guided by that principle. And the results confirmed it: the clearer and more direct the path, the faster users reach their destination.
I also learned that being the first designer at a company is a unique opportunity to lay a strong foundation.
Tinybird taught me that the best designs aren’t the ones that scream for attention—they’re the ones that just work, allowing users to focus on what truly matters.
In this case, turning data into value in the shortest possible time.
This project taught me one clear lesson: simplifying isn’t about removing—it’s about multiplying.
In design, there’s always a temptation to add more elements, more options, more features. But the real challenge is doing more with less.
Every design decision we made at Tinybird was guided by that principle. And the results confirmed it: the clearer and more direct the path, the faster users reach their destination.
I also learned that being the first designer at a company is a unique opportunity to lay a strong foundation.
Tinybird taught me that the best designs aren’t the ones that scream for attention—they’re the ones that just work, allowing users to focus on what truly matters.
In this case, turning data into value in the shortest possible time.
© 2025 Juanma Jiménez | Designed in Figma & developed in Framer.
13:30
© 2025 Juanma Jiménez | Designed in Figma & developed in Framer.
13:30
© 2025 Juanma Jiménez | Designed in Figma & developed in Framer.
13:30
© 2025 Juanma Jiménez | Designed in Figma & developed in Framer.
13:30