From one piece Luis Ouriach - How are design systems changing? 19 beliefs, in the piece's order there
-
Their words
because there's so much software on the market, because there's so many websites, so many businesses, we have to focus on sales, we have to focus on getting revenue, and getting users, and sign-ups, and acquisitions. So, the pixels are secondary to the success of the business
-
Their words
more people are going to be able to create their ideas. We're not in a position to tell people what they can or can't make
-
Their words
we are the experts in seat to bring something to market and if we're outsourcing our ideas, our output, our definitions of anything to a tool, then we just need to ask ourselves what we really want to be doing
+ 16 more
-
Their words
sometimes you need to feel something to know what's wrong and it can take a lot longer often to draw out on the canvas than to say hey generate me a web page for this thing
-
Their words
the canvas is very important for ideation, collaboration and general direction exploration, but the browser is where we commit to it
-
Their words
a little phrase that we kind of throw around internally is not faster, but further. And that enables people who aren't technical jump in the browser, test something out
-
Their words
community, people, users, passion is still incredibly important for the success of an idea. It's just that we're doing it faster, but we can't skip the quality no matter how fast we want to move
-
Their words
It feels like it's getting wider. And the reason it feels like it's getting wider is because the access to tools is so vastly different based on your security standards as a company
-
korrents.com
Relying on code generation without a very strict indication of brand feeling ends with everything looking the same.Their words
if we rely just on generation of code without a very strict indication of brand feeling, we end up with all the things looking the same
-
Their words
Writing down before you commit to a pixel is the best way to get buy-in for an idea. And you're not going to get the ability to ship an idea unless you get buy-in
-
Their words
Maybe we can get higher fidelity prototypes that we can test and validate a lot faster, and still throw them away, because that is the point of prototype a lot of the time, is to just test an idea
-
Their words
The designer is still doing something specific to a designer's role. It's not oh, the PM can contribute to prototypes now, therefore I'm not going to make one.
-
Their words
hanging out together as a team more and building rituals that allow you to collaborate synchronously, asynchronously. That is a Slack channel, it's a document, it's a Figma file or other file that you prefer to collaborate in, but doing that as a unit, and not saying, "I'm the product manager, therefore I own the PRD. I'm a designer, therefore I own the design.
-
Their words
we have to decide as an individual, as a company, or even as a team within a company, what are our roles actually now, and what are the tools taking over, and decide that as soon as we possibly can before that decision is made for us
-
Their words
taking the label of design system off what we're doing is going to help. It's going to bring you out of the corner and out of the silo and to the center of an organization's change
-
Their words
to me a design system is a bar of quality in an organization. And that's everyone's job
-
Their words
the importance of those docs, whatever form that they were in before, is going to be the foundation of everyone's workflow going forward. They might just be written slightly differently and for a different format, for a different output, but guidelines are becoming paramount for everything we need to do
-
Their words
the less we invest in a system, the more we're going to generate just honestly rubbish into our systems that will just pile up like a landfill over the next couple of years
-
Their words
the system becomes the centerpiece of all successful engineering work because the more we rely on a tool to create our code, the more we rely on a system to tell that tool what to code. And the less we invest in a system, the more we're going to generate just honestly rubbish into our systems