korrents
Meaghan Choi

Meaghan Choi

@meaghan-choi · 20 positions · 0 changes of mind

Design Lead for Claude Code at Anthropic.

Everything they publish, on ppll ↗

Meaghan Choi 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.

Filter All topics · Newest first
  1. Anthropicdesign

    the invisible thinking that goes behind building a product. That's one that I think I expect and hire for at Anthropic and I think has been the long unsung hero of product designers everywhere is like the mental model, the interaction model, like the base primitives that compose how you think about what you're interacting with.
    spoken · machine transcript hear it at 3:38 · all korrents from this recording

    ↗Meaghan Choi - Designing Claude Code (and what's coming next)youtube.com 1st of 20 in this recording

  2. developer tools

    Because you're serving developers, they have very specific expectations with the CLI actually that you want it to be extraordinarily information dense. Like you would show more in a CLI than you would ever probably show in like a guey, like a graphical interface, because there's no such thing as progressive disclosure.
    spoken · machine transcript hear it at 5:03 · all korrents from this recording

    ↗Meaghan Choi - Designing Claude Code (and what's coming next)youtube.com 2nd of 20 in this recording

  3. developer tools

    keyboard shortcuts are massive. I would say like there are power tools like Figma and other places where they do consider keyboard heavier but like the primary way you interact with a terminal is keyboard shortcuts.
    spoken · machine transcript hear it at 5:27 · all korrents from this recording

    ↗Meaghan Choi - Designing Claude Code (and what's coming next)youtube.com 3rd of 20 in this recording

  4. empathydesign

    I think it's really important that you feel a little bit of warmth from these tools. You don't want to be super super detached from them.
    spoken · machine transcript hear it at 9:18 · all korrents from this recording

    ↗Meaghan Choi - Designing Claude Code (and what's coming next)youtube.com 4th of 20 in this recording

  5. designsimplicity

    The UI part of itself is extremely simple because in my goal, we're trying not to invent new UI. We want it to feel so natural that it just becomes intrinsically part of your workflow.
    spoken · machine transcript hear it at 13:47 · all korrents from this recording

    ↗Meaghan Choi - Designing Claude Code (and what's coming next)youtube.com 5th of 20 in this recording

  6. design

    Those are the really important pieces that we spend a lot of time thinking on that we won't offload because it's about the user model relationship and behavior and like these design polish pieces or some of these updated ones are like really easy ones to offload.
    spoken · machine transcript hear it at 33:37 · all korrents from this recording

    ↗Meaghan Choi - Designing Claude Code (and what's coming next)youtube.com 6th of 20 in this recording

  7. design

    it doesn't have to be all of your time. And so knowing when to use these tools for execution and offload and knowing when you need to go deep and do the thinky work is a skill set. And I think that's one that I see people doing wrong.
    spoken · machine transcript hear it at 35:11 · all korrents from this recording

    ↗Meaghan Choi - Designing Claude Code (and what's coming next)youtube.com 7th of 20 in this recording

  8. Anthropic

    you might be asking Claude to do execution when you you should actually be asking Claude to do the early thinking. The execution is wrong. Like the shape of the execution is incorrect. And Claude is not good today at telling you if your idea is wrong, it'll just execute on the thing that you ask it to do.
    spoken · machine transcript hear it at 35:25 · all korrents from this recording

    ↗Meaghan Choi - Designing Claude Code (and what's coming next)youtube.com 8th of 20 in this recording

  9. design

    sometimes knowing when it needs that craft and polish or knowing when just the shape of it is actually what you're trying to test is really important. And so you might launch something or test something that looks terrible, but what you're actually testing is the underlying mental model of the shape of product. And I don't think it's worth polishing that thing actually because it might not even make sense.
    spoken · machine transcript hear it at 39:00 · all korrents from this recording

    ↗Meaghan Choi - Designing Claude Code (and what's coming next)youtube.com 9th of 20 in this recording

  10. design

    that experimentation of mental models doesn't require that high of craft and it's better done actually in speed in the open in iteration as opposed to spending a lot of time polishing something that's actually the wrong full wrong shape
    spoken · machine transcript hear it at 39:34 · all korrents from this recording

    ↗Meaghan Choi - Designing Claude Code (and what's coming next)youtube.com 10th of 20 in this recording

  11. agencyproduct managementsoftware quality

    I tend to find the more we can share responsibility of what we think quality looks like in our product and not be the gatekeepers but educate and kind of delegate around us so that both our engineers and product partners feel that quality is something that they own and drive too.
    spoken · machine transcript hear it at 39:48 · all korrents from this recording

    ↗Meaghan Choi - Designing Claude Code (and what's coming next)youtube.com 11th of 20 in this recording

  12. designsoftware quality

    I don't think and it never has been historically only design's responsibility to mean quality the most successful organizations feel like it's owned by everybody
    spoken · machine transcript hear it at 40:29 · all korrents from this recording

    ↗Meaghan Choi - Designing Claude Code (and what's coming next)youtube.com 12th of 20 in this recording

  13. design

    invest in like how you define your quality and how you uplevel it and then share that as a workflow that anyone on your team can use and don't do it to stop them. Although it is important to know when to stop and hold the bar, but try and do it in a way that like is additive and is teaching and guiding rather than stopping.
    spoken · machine transcript hear it at 42:29 · all korrents from this recording

    ↗Meaghan Choi - Designing Claude Code (and what's coming next)youtube.com 13th of 20 in this recording

  14. design

    we're still going to need a lot of fixed interfaces. So there's two concepts now that UI can fall into. There's fixed and then there's like adaptive or like non-deterministic is kind of and I think there's just so much that needs to be reliably stable that you don't want to relearn and you don't want to be dynamic like a login screen, billing settings
    spoken · machine transcript hear it at 43:49 · all korrents from this recording

    ↗Meaghan Choi - Designing Claude Code (and what's coming next)youtube.com 14th of 20 in this recording

  15. design

    Knowing what should be fixed and what should be adaptive or dynamic is a really important decision for you as a designer to make as you're designing these features because I think often people will assume that everything should be customized because it can. I'm very much of the opinion that a lot of people don't want everything to be customized.
    spoken · machine transcript hear it at 44:14 · all korrents from this recording

    ↗Meaghan Choi - Designing Claude Code (and what's coming next)youtube.com 15th of 20 in this recording

  16. designsimplicity

    Just because it can build and just because it can be a function doesn't mean it needs to be. It adds a lot of product bloat. It makes it very complex.
    spoken · machine transcript hear it at 47:13 · all korrents from this recording

    ↗Meaghan Choi - Designing Claude Code (and what's coming next)youtube.com 16th of 20 in this recording

  17. simplicity

    in terms of like full functionality, things can be a little bit simpler than they are right now. And not every idea is good or necessary. Sometimes adding it is worse.
    spoken · machine transcript hear it at 47:24 · all korrents from this recording

    ↗Meaghan Choi - Designing Claude Code (and what's coming next)youtube.com 17th of 20 in this recording

  18. curiosity

    Being very open-minded and curious, I think is really useful. Like hold your opinions, develop them, and then be willing to let go and update how you think about things.
    spoken · machine transcript hear it at 48:33 · all korrents from this recording

    ↗Meaghan Choi - Designing Claude Code (and what's coming next)youtube.com 18th of 20 in this recording

  19. design

    design used to be so structured and processed that it feels like you really want to cling to that. But I'm urging people to do the opposite which is like lean into the chaos, develop new ways of working and like continuously update.
    spoken · machine transcript hear it at 49:05 · all korrents from this recording

    ↗Meaghan Choi - Designing Claude Code (and what's coming next)youtube.com 19th of 20 in this recording

  20. designproduct management

    But I think discernment on what should be built, how to best build it in a way that suits your product and what you're trying to express and what role you should play in building it and where that craft should fall is like a big one. Like that's the core builder process right now.
    spoken · machine transcript hear it at 49:36 · all korrents from this recording

    ↗Meaghan Choi - Designing Claude Code (and what's coming next)youtube.com 20th of 20 in this recording