korrents
Brian Lovin

What Brian Lovin thinks about design

@brian-lovin · 20 positions · 0 changes of mind

Product designer at Notion working on AI products, and maker of the read-it-later app Shiori.

Everything they publish, on ppll ↗

Brian Lovin did not write this page.

We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.

7 dated positions, 2026, in their own words. Our reading of what Brian Lovin has said — not written or endorsed by them.

7 positions so far — this page is not yet offered to search engines.

  1. Our readingAs soon as you realize you can't design half of this stuff in Figma, what you are really designing is the harness for the agent to do longer things and verify its own work.

    Their wordsLike as soon as you realize you can't design half of this stuff in Figma, what you're really designing is the harness for the agent to do longer things and verify its own work. And a lot of that means using AI in your day-to-day work and just getting like a feel.

    ↗Brian Lovin - How to level up with AI as a designeryoutube.com 1st of 20 in this recording

  3. Our readingDesigners should be designing right at the boundary of the current model, hoping the next one solves it; understanding what is possible and pushing the edges even if you get stuck is probably a good place to be right now.

    vibe coding

    Their wordsI think where designers need to be designing right now is like right at the the boundary of the next the current model, like hoping that the next one solves it, right? Like we're all shipping shitty vibe-coded slop just hoping like, "Ah, the next model's definitely going to clean this up, right?" And I think that's probably a good a good place to be right now as a designer is really understanding what's possible, trying to push the edges even if it sucks and you get stuck

    ↗Brian Lovin - How to level up with AI as a designeryoutube.com 2nd of 20 in this recording

  5. Our readingPeople trying to use AI to automate knowledge work or simplify their job are very early adopters, and their tolerance for sub-par experiences is quite high.

    Their wordsif you're really trying to use AI right now to automate knowledge work or simplify your job or like remove a process at your company, you're a very early adopter and the tolerance for those people for like kind of sub-par experiences is actually quite high.

    ↗Brian Lovin - How to level up with AI as a designeryoutube.com 3rd of 20 in this recording

  7. Our readingDepending on the work it is totally fine to design predominantly in Figma, but the barrier to trying making something in code is so low that everybody has probably dabbled with it.

    Their wordsI think it's totally fine depending on what you're working on, but I would say the barrier to entry to try making something in code is so low that I I think everybody has dabbled with it.

    ↗Brian Lovin - How to level up with AI as a designeryoutube.com 5th of 20 in this recording

  9. Our readingIt is getting very easy to move between disciplines, and the person to be is one who can move fluidly between types of working instead of getting caught up in the box they are in at a company.

    Their wordsAnd you want to be the kind of person that can move between those types of working very fluidly and not get caught up in, but what's my what's the box I'm in at this company, right?

    ↗Brian Lovin - How to level up with AI as a designeryoutube.com 17th of 20 in this recording

  11. Our readingA PM who can design around their spec to see if it holds up to reality is what you want, and so is an engineer who really cares about building great visual component systems.

    Their wordsYou want a PM who can design around their spec to see if their spec holds up to reality. You want an engineer that really cares about building great visual component systems so that they can prototype beautiful things without needing a designer to come in and tell them to nudge stuff around, which is really annoying.

    ↗Brian Lovin - How to level up with AI as a designeryoutube.com 18th of 20 in this recording

  13. Our readingSomeone newer to the field will probably be fine by focusing on making things for real people that solve a real problem, iterating quickly, and learning to do that faster, without worrying about not knowing how to code or write a PRD.

    Their wordsif you can just focus on making things for real people, that solve a real problem, iterate quickly, try and make the thing as good as you can and stop worrying about but I don't know how to code. I don't know how to write a PRD. Like who cares? Just like ship the thing and solve the problem and learn how to do that faster. Uh you'll be fine.

    ↗Brian Lovin - How to level up with AI as a designeryoutube.com 19th of 20 in this recording