Lily Dart

@lily_dart

Head of Design Systems at . 15 years in design. 8 yrs public speaking. All about diversity, inclusion, and design at scale. Pronouns: she/her 🏳️‍🌈 🥄

London
Vrijeme pridruživanja: svibanj 2009.

Tweetovi

Blokirali ste korisnika/cu @lily_dart

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @lily_dart

  1. Prikvačeni tweet
    23. lis 2019.

    Super excited to say that I am unhurriedly looking for my next work opportunity. (Plz RT!) I am a Head of/Director level design and product human. I build awesome inclusive teams that deliver measurable outcomes. A mini cv thread:

    Prikaži ovu nit
    Poništi
  2. proslijedio/la je Tweet
    prije 5 sati

    The Accessibility Guidelines Working Group is ready to rename Silver, the next generation of guidelines to eventually replace WCAG (because it’s more than just the Web now). I vote for “DIGG” (Digital Accessibility Global Guidelines). And you? How would you rename WCAG?

    Poništi
  3. proslijedio/la je Tweet

    💯 this. 🙌 We thought is necessary to clearly define what we consider a Design System. For us it must include Design, Documentation & Code. Anything less and we don’t consider it a Design System.

    Poništi
  4. proslijedio/la je Tweet
    prije 9 sati

    I think design tools need to hear this message more that anyone. Calling the part of your product that generates design docs a design system is not helpful.

    Poništi
  5. proslijedio/la je Tweet

    "UX trends" doesn't mean anything. You are literally writing "user experience trends" there's no trends in user experience, there's experience, habits, mental models, expectations, etc. There's interface trends, patterns that become a trend, technologies, methods, tools maybe.

    Prikaži ovu nit
    Poništi
  6. prije 11 sati

    are a step change in how we contribute to the creation of products and services as . They are about collaboration, the design community doesn't own them alone. So, hold onto that progress rather than co-opting the term to rename design-only practices.

    Prikaži ovu nit
    Poništi
  7. prije 11 sati

    "But Lily, this feels like gatekeeping 😱. Why are you nitpicking terms like this?" It's important because documentation on its own doesn't ensure our customers will see what we've designed. Only code can do that. We shouldn't see code or collaboration with devs as optional.

    Prikaži ovu nit
    Poništi
  8. prije 11 sati

    A needs to involve every skill you need to design and deliver the front end of your product or service. That's research, content, UI, UX and developers. Design documentation is an awesome achievement, but it doesn't deliver anything to customers on its own.

    Prikaži ovu nit
    Poništi
  9. prije 11 sati

    Morning! Quick reminder that if your doesn't include code it's actually documentation. Your documentation might describe your visual language (which is a system of sorts), but a is both documentation *and* tooling to deliver that language.

    Prikaži ovu nit
    Poništi
  10. proslijedio/la je Tweet

    Say it with me: design research should never be about *validation*. It's always about *evaluation*.

    Prikaži ovu nit
    Poništi
  11. 30. sij
    Poništi
  12. proslijedio/la je Tweet
    30. sij

    I’m doing a talk in the summer called “minimum viable content”. I know what I think minimum viable content is. But I’d love to hear what you think it is. Tell me here here, or DM me. RTs appreciated!

    Poništi
  13. 30. sij

    In case you missed it yesterday, my (long) thread on leading and lagging . I know plenty of people in and who haven't been taught the groundwork for understanding metrics. Leading/lagging is a key part of that groundwork, if thats you.

    Poništi
  14. 29. sij

    This whole thread is amazing but I particularly want to draw attention to this point. I wouldn't be where or who I am without . The fact I have that experience means I add value, so being defined by it is not a negative thing.

    Poništi
  15. proslijedio/la je Tweet
    29. sij

    What a great job, I am jealous of whoever you recruit !

    Poništi
  16. 29. sij

    TLDR: - Understand what is a leading or lagging metric is for the system you are working with - Don't try to influence lagging metrics or you will break another part of your system - Most helpdesks need to measure customer satisfaction as their key focus

    Prikaži ovu nit
    Poništi
  17. 29. sij

    E.g. as described above, speed of resolution is a lagging metric for complexity. Speed also is responsible for satisfaction in some cases (e.g. a severe problem), so it becomes a leading metric there.

    Prikaži ovu nit
    Poništi
  18. 29. sij

    In order to influence satisfaction or any other lagging metric in a system, you have to identify those leading metrics. And just to be confusing, a metric might be both lagging and leading depending on the framing by which you look at it.

    Prikaži ovu nit
    Poništi
  19. 29. sij

    Speed of resolution might be a leading influence on satisfaction but on its own it's not a reliable predictor. Complexity, severity, keeping the customer informed and updated - they all play a part as leading metrics.

    Prikaži ovu nit
    Poništi
  20. 29. sij

    In this case, customer satisfaction is your lagging metric. Because beyond actually fixing stuff, it's the real output of the helpdesk/service desk system: keeping customers happy and trusting in your services.

    Prikaži ovu nit
    Poništi
  21. 29. sij

    For a helpdesk or service desk, customer satisfaction is generally the most important measure too. If you close a ticket quickly but you don't really fix the problem, the customer will be annoyed. Take a week to solve a non-urgent issue, the customer might be happy with that.

    Prikaži ovu nit
    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·