The deliverable has been delivered — shipped — launched. While some might reduce this artifact’s value to its current form and function, we all know firsthand that design and product teams can spend months brainstorming, researching, testing, and prototyping to get to that finished product.
The value lies not only in the final deliverable but in the process — the insights gained along the way. Often overlooked once the sprint ends and tickets close, this very information that cost the team so much time and effort disappears (whispers in dramatic voice) like vapor at the end of the waterfall.
What if you could integrate those hard-earned insights and the work that gleaned them into your design system? With Luro, you can do just that.
The what and the why
Design systems capture the what. What is it? A product card with an image, description, and a full-width call-to-action button at the bottom. What they tend to miss is the why. Why does the product look and function this way? What principles, research, user tests, and analytic data informed these decisions?
In my experience, the why takes the most time and costs the most money. It’s also where I provide the most value as a designer. I am not merely the picker of fonts, the dropper of shadows, the executor of deliverables. My greatest value as a designer lies in orchestrating the process and gathering insights — applying the whys to create the optimal what.
Those insights don’t cease to be valuable after a product ships but instead become more valuable as historical resources that contextualize design — provenance. This accounting of how we arrived at our solution should be retained and organized, accessible to others when needed to prevent repeat work and inform confident decision making.
Luro is a platform that captures the what and the why.
The most intuitive file structure known to humankind
We built Luro to center around your components and your site/product. Any insight or metric you want to integrate to Luro can be mapped to these two things, so not only are they easy to find, but they surface themselves when most relevant. Luro can capture contextual insights like:
Brainstorming sessions and mood boards
User research and personas
When you add these insights to Luro and relate them to the relevant components and pages, you’re on your way to laying the framework for a glorious org-wide hive mind! And yes, they’ll be easier to find when you pick up work again tomorrow.
We built Luro to help capture the full value of your design work — the platform where you can showcase the why alongside the what.
As roles and responsibilities within product teams evolve and some tasks become automated, the onus is on us to think more broadly about design and the value we bring to projects. We should be leading conversations about the future of design and its increasing importance to organizations looking to get the most out of the technological advancements that lie ahead.