WEBVTT

NOTE
Podcast: Data Stories
Episode: Formalizing Design with Gabrielle Mérite and Alan Wilson
Publishing Date: 2023-03-08T13:40:01+01:00
Podcast URL: https://datastori.es
Episode URL: https://datastori.es/170-formalizing-design-with-gabrielle-merite-and-alan-wilson/

00:00:00.515 --> 00:00:04.037
<v Gabrielle Mérite>Especially when we make guidelines that are going to be used potentially by

00:00:04.037 --> 00:00:07.819
<v Gabrielle Mérite>hundreds of people, we have such a responsibility to do them properly.

00:00:28.031 --> 00:00:32.674
<v Moritz Stefaner>Hi everyone, welcome to a new episode of Data Stories. My name is Moritz Stefano

00:00:32.674 --> 00:00:34.935
<v Moritz Stefaner>and I'm an independent designer of data visualizations.

00:00:35.776 --> 00:00:39.757
<v Moritz Stefaner>In fact, I work as a self-employed truth and beauty operator out of my office

00:00:39.757 --> 00:00:41.698
<v Moritz Stefaner>here in the countryside in the north of Germany.

00:00:42.499 --> 00:00:46.280
<v Moritz Stefaner>And usually I record this podcast together with Enrico Bertini,

00:00:46.280 --> 00:00:50.462
<v Moritz Stefaner>who is a professor at Northeastern University in Boston. But today I'm solo.

00:00:51.142 --> 00:00:55.804
<v Moritz Stefaner>But luckily I'm joined by two guests today, which you will hear about in a minute.

00:00:56.405 --> 00:01:00.846
<v Moritz Stefaner>Just in terms of introductions, on this podcast, we talk about data visualization,

00:01:00.846 --> 00:01:04.348
<v Moritz Stefaner>data analysis, and generally the role data plays in our lives.

00:01:04.348 --> 00:01:08.700
<v Moritz Stefaner>The topic today is data design themes, design systems, style guides,

00:01:08.700 --> 00:01:10.130
<v Moritz Stefaner>guidelines, design languages.

00:01:10.491 --> 00:01:15.633
<v Moritz Stefaner>You can already see there's a whole cosmos of new formats emerging here in this

00:01:15.633 --> 00:01:21.195
<v Moritz Stefaner>space that we want to explore together today. And hopefully you'll learn something new.

00:01:21.816 --> 00:01:24.889
<v Moritz Stefaner>And it's an exciting new emerging field.

00:01:27.173 --> 00:01:30.294
<v Moritz Stefaner>I hope we can shed a bit of light on these mysterious terms.

00:01:31.274 --> 00:01:35.335
<v Moritz Stefaner>Before we dive right in, just a quick note, our podcast is listener supported.

00:01:35.675 --> 00:01:40.917
<v Moritz Stefaner>We don't have any ads. So if you enjoy the show, you might consider supporting

00:01:40.917 --> 00:01:45.439
<v Moritz Stefaner>us. You can do this with recurring payments on patreon.com slash data stories.

00:01:45.439 --> 00:01:50.251
<v Moritz Stefaner>So then there's a little donation you do every time we publish an episode.

00:01:50.601 --> 00:01:55.302
<v Moritz Stefaner>Or you could also send us one time donations on paypal.me slash data stories.

00:01:55.302 --> 00:01:59.584
<v Moritz Stefaner>It's always much appreciated, also small amounts. It just keeps us going.

00:01:59.584 --> 00:02:04.806
<v Moritz Stefaner>And we also have a bit of cost, so any contribution you can make is super appreciated.

00:02:05.546 --> 00:02:12.708
<v Moritz Stefaner>If you don't have or don't want to do monetary support, you can also just support

00:02:12.708 --> 00:02:14.729
<v Moritz Stefaner>us on social media or give us a good rating.

00:02:15.349 --> 00:02:18.230
<v Moritz Stefaner>Anything helps. And if not, it's also fine. Just keep listening.

00:02:18.771 --> 00:02:20.211
<v Moritz Stefaner>Anyways, let's get started.

00:02:21.091 --> 00:02:27.814
<v Moritz Stefaner>Let's dive right in. And now I can reveal our guests. our guests today are Gabrielle and Alain. Hi.

00:02:27.814 --> 00:02:28.714
<v Gabrielle Mérite>Hi, Moritz.

00:02:28.714 --> 00:02:33.756
<v Moritz Stefaner>Hello. Thanks for joining me. Quick introduction. So Gabrielle,

00:02:33.756 --> 00:02:35.757
<v Moritz Stefaner>can you tell us a bit about yourself?

00:02:35.757 --> 00:02:41.840
<v Gabrielle Mérite>Yeah. Hi, I'm Gabrielle Merite. I'm French. I'm an independent information designer.

00:02:41.840 --> 00:02:47.142
<v Gabrielle Mérite>So I help ethically driven organization uncover important truth and share stories

00:02:47.142 --> 00:02:49.523
<v Gabrielle Mérite>with intention backed by data.

00:02:50.303 --> 00:02:56.446
<v Gabrielle Mérite>And I'm also currently, for another month, the senior DeDeviz designer at Pentagram

00:02:56.446 --> 00:02:58.386
<v Gabrielle Mérite>in the team of Georgia Alubi.

00:02:58.386 --> 00:03:02.248
<v Moritz Stefaner>Which we also had on the show a few times and who's of course well known.

00:03:03.088 --> 00:03:05.649
<v Moritz Stefaner>And yeah, it's exciting to see you two work together.

00:03:05.810 --> 00:03:07.270
<v Gabrielle Mérite>Yeah, the incredible Georgia.

00:03:09.911 --> 00:03:10.751
<v Moritz Stefaner>Ellen, how about you?

00:03:11.832 --> 00:03:14.952
<v Alan Wilson>Yeah, I'm Alan Wilson. I'm a principal designer at Adobe.

00:03:16.910 --> 00:03:22.232
<v Alan Wilson>Where I work primarily on the experience cloud, which is Adobe's enterprise

00:03:22.232 --> 00:03:28.694
<v Alan Wilson>business. We make marketing software and other tools to help large organizations

00:03:28.694 --> 00:03:31.795
<v Alan Wilson>keep their messaging and help their customers.

00:03:32.716 --> 00:03:38.358
<v Alan Wilson>And I guess the main thing that we'll be discussing today is my contributions

00:03:38.358 --> 00:03:41.879
<v Alan Wilson>to the design system at Adobe, which is called Spectrum. Right.

00:03:41.879 --> 00:03:47.831
<v Moritz Stefaner>Yes. And this is also how we got in touch around two years ago because I started

00:03:47.831 --> 00:03:53.153
<v Moritz Stefaner>working together with Core, an agency in the UK on a design system for the World Health Organization.

00:03:53.483 --> 00:04:00.965
<v Moritz Stefaner>And yeah, and we sort of uncovered this whole world of wow, there's so much

00:04:00.965 --> 00:04:02.006
<v Moritz Stefaner>happening in this space.

00:04:02.006 --> 00:04:06.507
<v Moritz Stefaner>And it's also really hard to orient yourself. Like it sounds so easy if somebody

00:04:06.507 --> 00:04:10.249
<v Moritz Stefaner>says, oh, we need some database style guide or guidelines.

00:04:10.249 --> 00:04:12.569
<v Moritz Stefaner>Can you help us do that? You know, everybody's like, yeah, sure,

00:04:12.569 --> 00:04:16.751
<v Moritz Stefaner>that sounds great. And then once you look into, oh, what do we do?

00:04:16.751 --> 00:04:20.392
<v Moritz Stefaner>What do we actually do now? What do we offer? What's the format?

00:04:20.893 --> 00:04:24.234
<v Moritz Stefaner>What's the scope of the whole project? You realize, oh, it's not even that clear.

00:04:24.234 --> 00:04:28.156
<v Moritz Stefaner>And everybody needs to figure out what they're doing in that space.

00:04:29.396 --> 00:04:34.058
<v Moritz Stefaner>And so, yeah, so there's so many flavors and approaches you can do.

00:04:34.058 --> 00:04:39.120
<v Moritz Stefaner>And so, yeah, I got in touch with you, Alan, and a few other folks who have

00:04:39.120 --> 00:04:44.002
<v Moritz Stefaner>experience in the field to help us guide along a bit. And here we are.

00:04:46.703 --> 00:04:50.004
<v Moritz Stefaner>So I know both of you have been working on these types of projects.

00:04:50.004 --> 00:04:54.686
<v Moritz Stefaner>So before we go into all the nuances, what the differences between different

00:04:54.686 --> 00:04:58.768
<v Moritz Stefaner>subgenres are, maybe we can start with the purpose.

00:04:58.768 --> 00:05:02.809
<v Moritz Stefaner>What, in your experience, do people hope to achieve when they start building

00:05:02.809 --> 00:05:03.810
<v Moritz Stefaner>a design style guide or start formulating design guidelines?

00:05:03.810 --> 00:05:08.572
<v Moritz Stefaner>Building a design style guide or start formulating design guidelines.

00:05:08.992 --> 00:05:12.729
<v Moritz Stefaner>What do you think? What's the hope connected to that? Or what's the value to

00:05:12.729 --> 00:05:15.175
<v Moritz Stefaner>an organization to have something like that?

00:05:15.935 --> 00:05:22.878
<v Alan Wilson>I guess I'll go first. I think the main value is answering questions, right?

00:05:23.918 --> 00:05:28.700
<v Alan Wilson>As organizations grow, you have to coordinate a lot more to make sure that you

00:05:28.700 --> 00:05:31.061
<v Alan Wilson>as a group have a coordinated voice.

00:05:31.061 --> 00:05:37.543
<v Alan Wilson>Space. Questions are very common, right? What font should I use?

00:05:37.543 --> 00:05:39.164
<v Alan Wilson>What are our standard colors?

00:05:39.504 --> 00:05:42.985
<v Alan Wilson>How do we lay out this particular document type?

00:05:46.067 --> 00:05:49.748
<v Alan Wilson>People need standards to communicate in a unified way.

00:05:51.469 --> 00:05:55.971
<v Alan Wilson>One of the things I like about this space is there's just such a broad range

00:05:55.971 --> 00:05:59.556
<v Alan Wilson>as you already touched on of ways to answer those questions.

00:06:00.237 --> 00:06:01.839
<v Alan Wilson>But for me, it's all about.

00:06:02.821 --> 00:06:08.603
<v Alan Wilson>Helping people do their jobs more effectively and efficiently by answering questions

00:06:08.603 --> 00:06:10.623
<v Alan Wilson>that they have a difficult time answering on their own.

00:06:10.623 --> 00:06:11.524
<v Moritz Stefaner>Mm-hmm.

00:06:11.524 --> 00:06:12.544
<v Gabrielle Mérite>I love that answer.

00:06:14.145 --> 00:06:16.546
<v Moritz Stefaner>Yeah, that seems pretty comprehensive already.

00:06:16.546 --> 00:06:20.427
<v Gabrielle Mérite>Yeah, I had a way more like strict like dot list. Yeah.

00:06:21.407 --> 00:06:27.950
<v Gabrielle Mérite>But I love that answer of answering question because I think it answers a lot on the definition.

00:06:28.570 --> 00:06:33.452
<v Gabrielle Mérite>I see, on mine, I kind of see like four kind of point of values.

00:06:35.132 --> 00:06:38.614
<v Gabrielle Mérite>Efficiency, just the idea of answering questions faster.

00:06:39.514 --> 00:06:43.815
<v Gabrielle Mérite>So just people being able to reuse design to know what to do.

00:06:44.336 --> 00:06:46.096
<v Gabrielle Mérite>All these things come into efficiency.

00:06:48.637 --> 00:06:51.578
<v Gabrielle Mérite>Consistency, which I think is the one that people don't always see.

00:06:51.578 --> 00:06:56.320
<v Gabrielle Mérite>But for an organization, being able to reproduce a design over and over or reuse

00:06:56.320 --> 00:07:00.942
<v Gabrielle Mérite>some time of... set of rules and principle that they can build upon, scale.

00:07:01.962 --> 00:07:04.123
<v Gabrielle Mérite>And I think Alan is going to know that more than me.

00:07:06.424 --> 00:07:11.225
<v Gabrielle Mérite>And then the one that I don't see often, but to add pentagram in my work that's

00:07:11.225 --> 00:07:12.446
<v Gabrielle Mérite>been pretty important, which is recognizability.

00:07:15.227 --> 00:07:18.668
<v Gabrielle Mérite>So in those guidelines in Style Guide, the idea of being able to produce something

00:07:18.668 --> 00:07:21.829
<v Gabrielle Mérite>that is recognized by an audience, like brand them.

00:07:22.250 --> 00:07:25.891
<v Gabrielle Mérite>And we don't talk about that often in data viz, but that's really important

00:07:25.891 --> 00:07:27.691
<v Gabrielle Mérite>to me when creating style guides.

00:07:27.691 --> 00:07:33.574
<v Moritz Stefaner>Yeah. Yeah. And in the like more branding and PR and advertising world,

00:07:33.574 --> 00:07:35.674
<v Moritz Stefaner>brand guidelines are super common, right?

00:07:35.674 --> 00:07:39.156
<v Moritz Stefaner>And often we just receive them as, oh, here are our brand guidelines.

00:07:39.156 --> 00:07:42.717
<v Moritz Stefaner>Can you make sure the charts, you know, fit into that?

00:07:42.717 --> 00:07:48.299
<v Moritz Stefaner>Right. And so, yeah, that's already where we touch these wider like communication

00:07:48.299 --> 00:07:52.440
<v Moritz Stefaner>contexts. But in this world, it's very common to have like a big book with the

00:07:52.440 --> 00:07:55.507
<v Moritz Stefaner>fonts we use, these are the colors we have. This is how we pick photos.

00:07:55.929 --> 00:07:58.816
<v Moritz Stefaner>You don't crop photos like this, you crop them like that and so on.

00:07:58.816 --> 00:08:02.645
<v Moritz Stefaner>And yeah, I think in database it's a bit more new that we would,

00:08:03.314 --> 00:08:07.536
<v Moritz Stefaner>be so explicit about this is our approach, right? Yeah.

00:08:07.536 --> 00:08:12.158
<v Alan Wilson>I think one of the reasons data is emerging more and more in the style guide

00:08:12.158 --> 00:08:15.499
<v Alan Wilson>space is because people are using it more and they have more questions about it.

00:08:16.780 --> 00:08:20.341
<v Alan Wilson>So we're traditionally style guides focused on how you use the logo and how

00:08:20.341 --> 00:08:24.042
<v Alan Wilson>you use photography and other visuals to communicate.

00:08:24.422 --> 00:08:28.124
<v Alan Wilson>People are using charts to communicate and they have questions about how to best do that.

00:08:28.124 --> 00:08:33.506
<v Moritz Stefaner>Yeah. Yeah. Yeah. So it's a natural evolution of us actually mattering, which is good.

00:08:33.506 --> 00:08:38.767
<v Gabrielle Mérite>Yeah, precisely. And there's this idea of like, you know, authority.

00:08:39.588 --> 00:08:44.229
<v Gabrielle Mérite>I think in the world where trust is hard to gain, for organizations that have

00:08:44.229 --> 00:08:47.771
<v Gabrielle Mérite>gained that trust or are trying to gain that trust, having that recognizability

00:08:47.771 --> 00:08:54.263
<v Gabrielle Mérite>of like, oh, this specific data visualization is coming from this institution that I'm familiar with.

00:08:54.573 --> 00:08:57.534
<v Gabrielle Mérite>And I can recognize that a very first look seems really important.

00:08:58.635 --> 00:08:59.975
<v Gabrielle Mérite>In the public discourse.

00:08:59.975 --> 00:09:05.358
<v Moritz Stefaner>Yeah. Cool. So I think we have the motivation is clear.

00:09:05.358 --> 00:09:09.640
<v Moritz Stefaner>So you want consistency, you want a scale design, you want to make sure all

00:09:09.640 --> 00:09:12.801
<v Moritz Stefaner>outputs coming from one source have a minimum level of quality,

00:09:12.801 --> 00:09:17.323
<v Moritz Stefaner>they're recognizable, they look from the same family at least.

00:09:21.426 --> 00:09:27.178
<v Moritz Stefaner>And not have to be a mysterious process process that some gifted rock star designers

00:09:27.178 --> 00:09:31.149
<v Moritz Stefaner>can only do, but sort of scale the capability to anybody.

00:09:32.890 --> 00:09:36.552
<v Moritz Stefaner>Ideally, right, that, oh, with the right ruleset and the right tools and the

00:09:36.552 --> 00:09:41.134
<v Moritz Stefaner>right building blocks, anybody can now make a chart that looks like coming from

00:09:41.134 --> 00:09:42.854
<v Moritz Stefaner>that organization and is solid.

00:09:45.387 --> 00:09:49.429
<v Moritz Stefaner>That's the hope. It's a big goal, of course. But now we're looking into,

00:09:49.429 --> 00:09:51.110
<v Moritz Stefaner>okay, how can we enable that?

00:09:51.110 --> 00:09:56.352
<v Moritz Stefaner>What are the things we can supply? And this is super crucial to be clear about that.

00:09:56.352 --> 00:10:01.374
<v Moritz Stefaner>That's a trap I ran into in a few projects that we weren't really clear what

00:10:01.374 --> 00:10:05.636
<v Moritz Stefaner>the difference is between a style guide or a guidelines or a component system.

00:10:05.636 --> 00:10:09.417
<v Moritz Stefaner>System. I like all these things. And then you realize, oh, they actually wanted

00:10:09.417 --> 00:10:13.839
<v Moritz Stefaner>to have a big book with lots of data with do's and don'ts.

00:10:13.839 --> 00:10:17.241
<v Moritz Stefaner>And we were like, oh, we thought we're just designing a database theme,

00:10:17.241 --> 00:10:19.181
<v Moritz Stefaner>like pick some colors, right.

00:10:19.181 --> 00:10:24.263
<v Moritz Stefaner>And so there's a whole spectrum of possible outputs you can have, right.

00:10:24.263 --> 00:10:27.885
<v Moritz Stefaner>And maybe let's talk about a few of them.

00:10:27.885 --> 00:10:32.747
<v Moritz Stefaner>And I try to organize it from small to big. So I think the smallest thing is

00:10:32.747 --> 00:10:37.570
<v Moritz Stefaner>probably like a design theme, where you say like, these are the colors and fonts

00:10:37.570 --> 00:10:41.051
<v Moritz Stefaner>you can use for a given charge or something like this.

00:10:41.852 --> 00:10:45.734
<v Moritz Stefaner>And maybe a brand has multiple themes like a light theme and a dark theme.

00:10:46.495 --> 00:10:51.037
<v Moritz Stefaner>It's like a skin you can apply to a chart like an Excel template type thing maybe.

00:10:52.658 --> 00:10:57.880
<v Moritz Stefaner>Then the next step is maybe a design system. Alan, is Spectrum a design system?

00:10:58.221 --> 00:10:59.661
<v Moritz Stefaner>Where's Spectrum on that ladder?

00:10:59.661 --> 00:11:04.384
<v Alan Wilson>Yeah, Spectrum is a design system and I would put it further down,

00:11:04.384 --> 00:11:06.565
<v Alan Wilson>maybe even at the very bottom.

00:11:06.565 --> 00:11:09.907
<v Gabrielle Mérite>At the bottom. I'm also in the bottom.

00:11:09.907 --> 00:11:10.207
<v Alan Wilson>Yeah.

00:11:13.099 --> 00:11:16.260
<v Alan Wilson>When I think design system, I think the difference between

00:11:16.260 --> 00:11:19.201
<v Alan Wilson>a design system and a style guide or a theme

00:11:19.201 --> 00:11:24.663
<v Alan Wilson>or just a set of guidelines is a design system has infrastructure behind it

00:11:24.663 --> 00:11:31.646
<v Alan Wilson>So that when you make a change those changes roll out into all the places that

00:11:31.646 --> 00:11:37.988
<v Alan Wilson>they need to maybe there's also software components that exactly implement that stuff and Yeah,

00:11:37.988 --> 00:11:42.970
<v Alan Wilson>yeah And it provides resources for all parties that are involved.

00:11:42.970 --> 00:11:46.091
<v Alan Wilson>So the designers get the design assets they need,

00:11:46.091 --> 00:11:50.123
<v Alan Wilson>the engineers have the engineering components that they're going to use,

00:11:50.123 --> 00:11:55.575
<v Alan Wilson>and anyone else in the organization has the guidelines and materials,

00:11:55.575 --> 00:11:58.496
<v Alan Wilson>templates, things they need to do their work.

00:11:59.556 --> 00:12:04.858
<v Moritz Stefaner>And so, okay, cool. So we have design themes, automated in the design system,

00:12:04.858 --> 00:12:05.738
<v Moritz Stefaner>and super well documented.

00:12:06.639 --> 00:12:09.200
<v Moritz Stefaner>So then how about guidelines and style guides?

00:12:09.940 --> 00:12:14.062
<v Gabrielle Mérite>How does that fit in? I don't know how Alan feels about it to me.

00:12:14.062 --> 00:12:18.803
<v Gabrielle Mérite>So I work hard on that one. I was like, is there a difference between guidelines and style guides?

00:12:19.424 --> 00:12:23.225
<v Gabrielle Mérite>And I think we use it pretty freely in the design world.

00:12:23.225 --> 00:12:27.927
<v Gabrielle Mérite>It kind of, we use it, at least in the, you know, bright side of things,

00:12:27.927 --> 00:12:30.488
<v Gabrielle Mérite>we use it kind of like whatever, we can exchange them.

00:12:30.488 --> 00:12:33.649
<v Gabrielle Mérite>However, I could see a difference where for me, like one guideline could be

00:12:33.649 --> 00:12:38.390
<v Gabrielle Mérite>like do and don'ts versus a style guide is kind of putting all those guidelines together.

00:12:39.551 --> 00:12:43.753
<v Gabrielle Mérite>So to me, style guide is a collection of rule. You know, it tells you what you're

00:12:43.753 --> 00:12:46.153
<v Gabrielle Mérite>allowed to do and not to do given a context.

00:12:48.465 --> 00:12:52.056
<v Gabrielle Mérite>And I guess I'm going to go one step further, but there's to me,

00:12:52.056 --> 00:12:56.177
<v Gabrielle Mérite>the style guide, if you think about, if you remove style and you just keep guide,

00:12:56.177 --> 00:13:00.979
<v Gabrielle Mérite>then you can also include elements of voice again, to that branding element.

00:13:00.979 --> 00:13:04.700
<v Gabrielle Mérite>So not just doing dance on design, on color choices, but yes,

00:13:04.700 --> 00:13:07.621
<v Gabrielle Mérite>on tonality, on content, on way

00:13:07.621 --> 00:13:12.443
<v Gabrielle Mérite>more than just the look and feel and the practicality of design elements.

00:13:12.443 --> 00:13:15.044
<v Gabrielle Mérite>So that's how I see the difference in guideline and style guides,

00:13:15.044 --> 00:13:18.765
<v Gabrielle Mérite>but in the design world, we definitely use them almost as exchangeable.

00:13:19.466 --> 00:13:22.787
<v Moritz Stefaner>And that part cannot be automated or implemented well in software,

00:13:22.787 --> 00:13:25.847
<v Moritz Stefaner>right? Like, how do you automate tonality?

00:13:27.269 --> 00:13:33.891
<v Moritz Stefaner>Can you? I don't know. But at least, let's say, a style guide or design guidelines

00:13:33.891 --> 00:13:38.113
<v Moritz Stefaner>are usually targeted at people making charts. Right? Is that fair to say?

00:13:38.113 --> 00:13:41.674
<v Alan Wilson>I mean, I think all of these are targeted at people making charts.

00:13:41.674 --> 00:13:47.116
<v Alan Wilson>But to Gabriel's point, some focus more on the aesthetic part of the problems

00:13:47.116 --> 00:13:48.376
<v Alan Wilson>and the aesthetic questions.

00:13:48.817 --> 00:13:54.338
<v Alan Wilson>And others focus on the technical questions and implementations and things and

00:13:54.338 --> 00:13:55.859
<v Alan Wilson>systemize things a bit more.

00:13:55.859 --> 00:13:56.159
<v Moritz Stefaner>More.

00:13:59.220 --> 00:14:04.161
<v Moritz Stefaner>Yeah, so you can see already, it's this muddy mess of people,

00:14:04.161 --> 00:14:05.061
<v Moritz Stefaner>machines, data, audiences.

00:14:08.963 --> 00:14:12.965
<v Moritz Stefaner>It's an exciting space. And then really think about, okay, how can we abstract

00:14:12.965 --> 00:14:17.246
<v Moritz Stefaner>principles there and re-covering rules and not just solve problems once,

00:14:17.246 --> 00:14:22.568
<v Moritz Stefaner>but more or less for once and all, which is of course the hard part.

00:14:23.588 --> 00:14:27.370
<v Gabrielle Mérite>It's funny because it reminds me of what Alan was saying about the design system.

00:14:29.090 --> 00:14:33.185
<v Gabrielle Mérite>So at least just like Alain had placed it at the end, to me it's what encompasses

00:14:33.185 --> 00:14:37.193
<v Gabrielle Mérite>everything, including Style Guide, but also design theme, design language,

00:14:37.193 --> 00:14:41.815
<v Gabrielle Mérite>like the actual components and little design elements, like templates that you may have created.

00:14:42.535 --> 00:14:47.897
<v Gabrielle Mérite>And I would call it a repository of institutional knowledge that solves problems,

00:14:47.897 --> 00:14:51.058
<v Gabrielle Mérite>that keeps happening. Like that's how I would define it probably without even

00:14:51.058 --> 00:14:52.618
<v Gabrielle Mérite>putting like what it is inside.

00:14:53.619 --> 00:14:58.941
<v Gabrielle Mérite>It's just a big, big, big repository and it can be flexible depending on your institution.

00:14:58.941 --> 00:15:00.702
<v Moritz Stefaner>Yeah, right.

00:15:00.702 --> 00:15:09.366
<v Alan Wilson>Yeah. I think another thing worth calling out is that sometimes data visualization is its own thing.

00:15:09.366 --> 00:15:13.488
<v Alan Wilson>There is a datavis style guide, and it lives up separate from the brand guide

00:15:13.488 --> 00:15:16.759
<v Alan Wilson>and the user interface guidelines and other resources.

00:15:18.611 --> 00:15:23.213
<v Alan Wilson>But more and more, we're seeing all three of those things. And other things as well come to,

00:15:35.319 --> 00:15:37.799
<v Alan Wilson>content guidelines in important ways that we need to account for.

00:15:37.799 --> 00:15:38.399
<v Moritz Stefaner>Yeah. Yeah.

00:15:40.208 --> 00:15:45.070
<v Moritz Stefaner>Yeah, so there's a lot of overlaps with adjacent, maybe other design systems,

00:15:45.070 --> 00:15:49.952
<v Moritz Stefaner>like the branding or the UI design, and we need to see how we fit in with all of that.

00:15:51.213 --> 00:15:56.955
<v Moritz Stefaner>I guess what's unique to data visualization is often the extra design vocabulary you need,

00:15:56.955 --> 00:16:02.557
<v Moritz Stefaner>like specific color scales that work, have certain functional properties or

00:16:02.557 --> 00:16:09.400
<v Moritz Stefaner>or chart types and all the things we're all familiar with, legends and axes and whatnot.

00:16:10.600 --> 00:16:14.882
<v Alan Wilson>Yeah, one of the challenges with writing guidelines for data is that differs

00:16:14.882 --> 00:16:21.564
<v Alan Wilson>from brand guidelines and others is some of the other areas are just self-evident

00:16:21.564 --> 00:16:23.645
<v Alan Wilson>and really easy to explain the guidelines for.

00:16:24.266 --> 00:16:29.207
<v Alan Wilson>And data visualization has its own language and its own set of things.

00:16:30.588 --> 00:16:36.890
<v Alan Wilson>I mean, it intersects with data literacy and some specific domain expertise

00:16:36.890 --> 00:16:38.801
<v Alan Wilson>that you might need to be effective.

00:16:40.052 --> 00:16:43.092
<v Alan Wilson>And often I find myself in writing the guidelines, I'm like,

00:16:43.092 --> 00:16:45.994
<v Alan Wilson>man, I need them also to read these books.

00:16:45.994 --> 00:16:51.375
<v Alan Wilson>Or I find myself wanting to teach data visualization as a discipline,

00:16:51.375 --> 00:16:55.517
<v Alan Wilson>and then I can give them guidelines on how to best use visualization.

00:16:56.898 --> 00:17:01.559
<v Alan Wilson>And if you don't have that foundation, sometimes the guidelines come off a bit

00:17:01.559 --> 00:17:03.420
<v Alan Wilson>short because they have to be so basic.

00:17:05.200 --> 00:17:06.280
<v Gabrielle Mérite>Yeah, same problem here.

00:17:07.621 --> 00:17:11.823
<v Moritz Stefaner>Yeah, and maybe that's the first real learning I think we all share probably

00:17:11.823 --> 00:17:15.924
<v Moritz Stefaner>is like, you really need to define really well what the purpose of the whole

00:17:15.924 --> 00:17:18.345
<v Moritz Stefaner>thing is and what your audience is.

00:17:18.345 --> 00:17:23.297
<v Moritz Stefaner>Like, is it skilled information designers that use it or should it be implemented

00:17:23.297 --> 00:17:27.508
<v Moritz Stefaner>in an automated system or should it be for total novices,

00:17:27.508 --> 00:17:32.030
<v Moritz Stefaner>like a foolproof system, because that will shape everything in terms of what

00:17:32.030 --> 00:17:35.231
<v Moritz Stefaner>do we even supply people with and in which form, right?

00:17:35.231 --> 00:17:40.394
<v Moritz Stefaner>And yeah, I think if you skip that step, it's going to fall on your feet really soon.

00:17:42.315 --> 00:17:44.115
<v Moritz Stefaner>That's my experience at least.

00:17:46.937 --> 00:17:51.058
<v Moritz Stefaner>But maybe to make this a bit more concrete, maybe we can talk about some of

00:17:51.058 --> 00:17:53.239
<v Moritz Stefaner>the projects you've been working on in that space.

00:17:53.239 --> 00:17:57.541
<v Moritz Stefaner>That gives people a bit of an idea of, okay, what are the different challenges

00:17:57.541 --> 00:18:02.323
<v Moritz Stefaner>and the different types of flavors that exist? So, Alan, do you want to talk

00:18:02.323 --> 00:18:03.623
<v Moritz Stefaner>a bit about Adobe Spectrum?

00:18:03.623 --> 00:18:09.646
<v Alan Wilson>Sure, sure. So Adobe Spectrum is our design system.

00:18:10.627 --> 00:18:13.167
<v Alan Wilson>If you want to take a look at it, you can find it at spectrum.adobe.com. And,

00:18:18.054 --> 00:18:20.875
<v Alan Wilson>Yeah, the first thing I want to point out is that it's a whole team.

00:18:20.875 --> 00:18:22.316
<v Alan Wilson>There's a lot of people involved.

00:18:22.696 --> 00:18:28.738
<v Alan Wilson>And so I am a small piece of that whole ecosystem that builds and maintains that.

00:18:30.939 --> 00:18:35.501
<v Alan Wilson>And the design system was about two years old before we introduced the data viz guidelines.

00:18:36.721 --> 00:18:40.943
<v Alan Wilson>We really struggled to articulate and structure the guidelines in a way that

00:18:40.943 --> 00:18:43.644
<v Alan Wilson>would make sense and be relevant to our users.

00:18:44.704 --> 00:18:47.445
<v Alan Wilson>And we still have a long way to go. I feel like the guidelines right now are

00:18:47.445 --> 00:18:53.828
<v Alan Wilson>pretty basic, but yeah, we have that. And the primary purpose of our guideline

00:18:53.828 --> 00:18:56.048
<v Alan Wilson>is to help people who are building software.

00:18:56.048 --> 00:18:57.089
<v Moritz Stefaner>Right.

00:18:57.089 --> 00:19:03.131
<v Alan Wilson>So it is used for our, you know, dot com website and some other things,

00:19:03.131 --> 00:19:09.133
<v Alan Wilson>but the primary focus is for how do we build, you know, really good software using that system.

00:19:09.133 --> 00:19:11.914
<v Moritz Stefaner>Cool. Gabrielle, how about you?

00:19:11.914 --> 00:19:16.442
<v Gabrielle Mérite>So I worked on quite a couple and I can't talk about everything.

00:19:16.884 --> 00:19:18.988
<v Gabrielle Mérite>So I'll talk about the one I'm publicly allowed to.

00:19:19.910 --> 00:19:23.075
<v Gabrielle Mérite>I think the one that's the most public that you can see on the pentagram website

00:19:23.075 --> 00:19:24.338
<v Gabrielle Mérite>is the Deloitte insight.

00:19:25.904 --> 00:19:28.524
<v Gabrielle Mérite>It's a guideline and templates, so it's not full design systems.

00:19:29.645 --> 00:19:31.446
<v Gabrielle Mérite>And so, DeLaw Insight is a magazine.

00:19:31.806 --> 00:19:34.187
<v Gabrielle Mérite>It also has a web platform attached to it.

00:19:36.028 --> 00:19:39.309
<v Gabrielle Mérite>And previously, before I even joined Pentagram, the team with George Ilobby

00:19:39.309 --> 00:19:42.270
<v Gabrielle Mérite>had actually built guidelines for them before editorial database.

00:19:43.110 --> 00:19:47.052
<v Gabrielle Mérite>So, we're more creative application. So, that was used only by information designer

00:19:47.052 --> 00:19:49.673
<v Gabrielle Mérite>that already knew the roles and were pretty comfortable with it.

00:19:50.273 --> 00:19:54.775
<v Gabrielle Mérite>Talking about audience here. And the issue that came back when they came back

00:19:54.775 --> 00:19:58.616
<v Gabrielle Mérite>was that we cannot give those guidelines pretty much to our normal designers.

00:19:58.616 --> 00:20:04.789
<v Gabrielle Mérite>So the team actually use external, a lot of external designers that are around

00:20:04.789 --> 00:20:07.620
<v Gabrielle Mérite>the world with different backgrounds from different countries.

00:20:07.620 --> 00:20:10.841
<v Gabrielle Mérite>And they produce like hundreds of data viz per month.

00:20:11.581 --> 00:20:16.663
<v Gabrielle Mérite>And they're quite fast, so fast turnaround, you know, little supervision.

00:20:16.983 --> 00:20:20.905
<v Gabrielle Mérite>So we were in contact with more of the creative direction marketing data this

00:20:20.905 --> 00:20:24.926
<v Gabrielle Mérite>team within the organization, not so much the designers.

00:20:25.327 --> 00:20:30.558
<v Gabrielle Mérite>So we had to create templates and guidelines knowing that we have no contact

00:20:30.558 --> 00:20:32.529
<v Gabrielle Mérite>with the final designer that's going to use them.

00:20:33.010 --> 00:20:37.531
<v Gabrielle Mérite>And they are not specialized in information design, not always at least.

00:20:37.531 --> 00:20:40.812
<v Gabrielle Mérite>And they have a high turnaround themselves because they're external contractors.

00:20:41.793 --> 00:20:43.093
<v Moritz Stefaner>So it had to be pretty... It's really

00:20:43.093 --> 00:20:46.494
<v Moritz Stefaner>hard mode. It's like all the hard parameters are switched on, right?

00:20:46.655 --> 00:20:52.697
<v Gabrielle Mérite>Yeah, it had to be pretty strict. And also, we were working for both web and print.

00:20:52.697 --> 00:20:53.617
<v Moritz Stefaner>Of course.

00:20:53.617 --> 00:20:56.538
<v Gabrielle Mérite>Why not? So just to add a little bit to that.

00:20:56.538 --> 00:20:58.999
<v Moritz Stefaner>So yeah, and a bit of spice, you know.

00:20:58.999 --> 00:21:02.921
<v Gabrielle Mérite>And the law inside covers any themes, so it can be any type of data,

00:21:02.921 --> 00:21:06.462
<v Gabrielle Mérite>whether it's about people, but you know, economic, like anything,

00:21:06.462 --> 00:21:09.263
<v Gabrielle Mérite>everything, throw it in together in one package.

00:21:10.204 --> 00:21:15.605
<v Gabrielle Mérite>So that was probably one that I can talk quite a bit on. And the other one is

00:21:15.605 --> 00:21:18.126
<v Gabrielle Mérite>for a nonprofit organization that I cannot name.

00:21:18.707 --> 00:21:22.928
<v Gabrielle Mérite>They work in the gender equality space. And this one was tricky because we had

00:21:22.928 --> 00:21:26.729
<v Gabrielle Mérite>to do it and they hadn't produced any work yet.

00:21:27.350 --> 00:21:33.112
<v Gabrielle Mérite>It was made simultaneously to a brand. And so they knew what type of data they were working with.

00:21:33.932 --> 00:21:37.433
<v Gabrielle Mérite>But they had not produced anything. So we didn't have anything to even review.

00:21:37.433 --> 00:21:41.535
<v Gabrielle Mérite>We had to do from start and we had to make sure it would be used by designers

00:21:41.535 --> 00:21:46.076
<v Gabrielle Mérite>and non-designers for social media, PowerPoints, anything possible.

00:21:46.817 --> 00:21:50.618
<v Gabrielle Mérite>So that was another challenge on really sensitive topics too.

00:21:50.618 --> 00:21:53.519
<v Gabrielle Mérite>So definitely interesting different challenges here.

00:21:55.060 --> 00:22:00.121
<v Moritz Stefaner>Yeah, so you can see already it's quite different requirements and you need

00:22:00.121 --> 00:22:04.783
<v Moritz Stefaner>to be smart about what you do, right? And how that will play out.

00:22:04.783 --> 00:22:08.937
<v Moritz Stefaner>So maybe talking about process, then how do you...

00:22:10.721 --> 00:22:15.103
<v Moritz Stefaner>Address this? Like, do you first build a lot of chart examples,

00:22:15.103 --> 00:22:19.064
<v Moritz Stefaner>like in your design team, and then say like, okay, what are the recurring patterns?

00:22:19.064 --> 00:22:23.876
<v Moritz Stefaner>What seems to work? What doesn't seem to work? Or do you do it more top down in terms of,

00:22:23.876 --> 00:22:27.399
<v Moritz Stefaner>okay, we have the following principles, we have the following project constraints,

00:22:27.399 --> 00:22:31.249
<v Moritz Stefaner>you know, and sort of do it very like deductive in the sense that,

00:22:31.249 --> 00:22:37.071
<v Moritz Stefaner>okay, only one solution, you know, seems to work anymore, now that we have like defined everything?

00:22:37.632 --> 00:22:43.153
<v Moritz Stefaner>Or is it a mixture? Like, how did you address these? How did you approach this

00:22:43.153 --> 00:22:45.014
<v Moritz Stefaner>project? Maybe Gabby, you can.

00:22:45.454 --> 00:22:49.676
<v Gabrielle Mérite>Okay, I'll start. It might be very different because we so we even me as an

00:22:49.676 --> 00:22:52.637
<v Gabrielle Mérite>independent or within Pentagram, we are external contractors.

00:22:53.457 --> 00:22:56.938
<v Gabrielle Mérite>So we don't have access to everything internally in the organization that might

00:22:56.938 --> 00:22:59.439
<v Gabrielle Mérite>be quite different than the way Alan works typically.

00:23:00.980 --> 00:23:04.201
<v Gabrielle Mérite>So the way I like to work is I start with what I call analysis phase,

00:23:04.201 --> 00:23:08.683
<v Gabrielle Mérite>which is just looking at obviously who the organization is.

00:23:08.683 --> 00:23:11.984
<v Gabrielle Mérite>The more classic design brief analysis of who the client is,

00:23:11.984 --> 00:23:14.725
<v Gabrielle Mérite>what do they know, what do they don't know.

00:23:14.725 --> 00:23:17.966
<v Gabrielle Mérite>So if they have data visits, it's great because it gives you a great insight

00:23:17.966 --> 00:23:20.647
<v Gabrielle Mérite>on what has been produced, what type of data do they work with,

00:23:20.647 --> 00:23:23.888
<v Gabrielle Mérite>what are the mistakes they keep making, what are the problems they keep.

00:23:23.888 --> 00:23:26.409
<v Gabrielle Mérite>You can even have a whole almost user research phase.

00:23:26.409 --> 00:23:30.450
<v Moritz Stefaner>So the idea is to... First the diagnosis, then the prescription, right?

00:23:32.731 --> 00:23:36.372
<v Gabrielle Mérite>Yeah, a little bit. But just identifying existing useful patterns,

00:23:36.372 --> 00:23:40.854
<v Gabrielle Mérite>things that have worked too and things that are not working in the current applications,

00:23:40.854 --> 00:23:42.435
<v Gabrielle Mérite>and who is working with it.

00:23:42.435 --> 00:23:45.276
<v Gabrielle Mérite>It's way harder when we have a project, like I was talking earlier,

00:23:45.276 --> 00:23:49.737
<v Gabrielle Mérite>where we don't have access to those existing applications, because there's none.

00:23:51.278 --> 00:23:54.129
<v Gabrielle Mérite>But there's always a base somewhere of what data are they going to use?

00:23:54.619 --> 00:23:55.959
<v Gabrielle Mérite>Where is it going to be published?

00:23:56.640 --> 00:24:00.241
<v Gabrielle Mérite>So I like the science in space and understanding, again, who is going to use the guidelines and,

00:24:02.164 --> 00:24:05.065
<v Gabrielle Mérite>This is the audience of the guidelines. So is it designer or non-designer?

00:24:05.385 --> 00:24:06.925
<v Gabrielle Mérite>Because it's not always for designer.

00:24:07.406 --> 00:24:10.587
<v Gabrielle Mérite>But also who's the final audience of the data visualization?

00:24:11.007 --> 00:24:12.687
<v Gabrielle Mérite>So there's a second layer.

00:24:12.687 --> 00:24:13.808
<v Moritz Stefaner>It's a double hop.

00:24:14.388 --> 00:24:18.870
<v Gabrielle Mérite>Yeah, there's a double hop here of like, OK, typically, if you work for a nonprofit,

00:24:18.870 --> 00:24:22.231
<v Gabrielle Mérite>the final product is going to be a public, a very uninformed public,

00:24:22.231 --> 00:24:26.152
<v Gabrielle Mérite>or on a sensitive topic. So what are the constraints already that I impose on

00:24:26.152 --> 00:24:28.683
<v Gabrielle Mérite>the project? So there's all this analysis phase.

00:24:29.394 --> 00:24:33.155
<v Gabrielle Mérite>And then I guess it's a bit of a mix match. What I like to do is a bit more of like,

00:24:33.155 --> 00:24:38.997
<v Gabrielle Mérite>if it doesn't exist anymore, it's kind of like doing design first and then link

00:24:38.997 --> 00:24:43.979
<v Gabrielle Mérite>that back to the foundation of, I find it difficult to build the foundation

00:24:43.979 --> 00:24:45.679
<v Gabrielle Mérite>first, decide the colors, everything

00:24:45.679 --> 00:24:47.860
<v Gabrielle Mérite>without testing them, because you're gonna end up changing them.

00:24:48.220 --> 00:24:51.861
<v Gabrielle Mérite>So I tend to, even if the project doesn't include making templates,

00:24:51.861 --> 00:24:55.143
<v Gabrielle Mérite>kind of templatize a little bit, like test out some basic charts or things they

00:24:55.143 --> 00:25:00.224
<v Gabrielle Mérite>use regularly to see if we can start finding patterns and put that back into guidelines.

00:25:01.605 --> 00:25:06.407
<v Gabrielle Mérite>So that's kind of how it works. The only added thing that I do and then Pentagram

00:25:06.407 --> 00:25:10.328
<v Gabrielle Mérite>does too is what we call creative direction, which is maybe a little different

00:25:10.328 --> 00:25:11.708
<v Gabrielle Mérite>than a traditional style gal,

00:25:11.708 --> 00:25:15.930
<v Gabrielle Mérite>which we're trying to find what makes those these evolutions stand out.

00:25:15.930 --> 00:25:20.311
<v Gabrielle Mérite>How do we connect them to the voice of the brand?

00:25:21.472 --> 00:25:25.593
<v Gabrielle Mérite>And so it's not just through just colors and typefaces, but is there something

00:25:25.593 --> 00:25:28.674
<v Gabrielle Mérite>specific, a specific way of a specific shape you use systematically.

00:25:29.915 --> 00:25:31.455
<v Gabrielle Mérite>So not just basic charts.

00:25:31.455 --> 00:25:36.417
<v Moritz Stefaner>Like an actual design idea in a sense that there is, there's like a design approach to it.

00:25:36.417 --> 00:25:39.878
<v Gabrielle Mérite>Is there a metaphor that we can use throughout? Is there something that makes

00:25:39.878 --> 00:25:43.719
<v Gabrielle Mérite>it stand out that's just not a design decision, but that makes it unique?

00:25:44.039 --> 00:25:47.641
<v Gabrielle Mérite>And so that is a little more, on the creative side, that's less common.

00:25:47.801 --> 00:25:51.962
<v Gabrielle Mérite>And then it's even harder to explain in Style Guides. But it's part of that

00:25:51.962 --> 00:25:55.283
<v Gabrielle Mérite>thinking. And then usually you test that on basic chart and then you test that

00:25:55.283 --> 00:26:00.424
<v Gabrielle Mérite>on editorialized charts because all client usually needs editorial charts and not the most basic.

00:26:00.500 --> 00:26:04.282
<v Gabrielle Mérite>You know, the most traditional charts, just to check if it works in conjunction

00:26:04.282 --> 00:26:08.143
<v Gabrielle Mérite>with other organizational systems, like does it work in a magazine spread,

00:26:08.143 --> 00:26:09.644
<v Gabrielle Mérite>does it work in social media format?

00:26:11.104 --> 00:26:15.846
<v Gabrielle Mérite>And then we systemize that and we put that all together in like extended guidelines.

00:26:15.846 --> 00:26:19.927
<v Moritz Stefaner>Yeah, but there's an interesting tension because of course you and Georgia of

00:26:19.927 --> 00:26:24.049
<v Moritz Stefaner>course are typically known and booked for a super creative, unique,

00:26:24.049 --> 00:26:26.350
<v Moritz Stefaner>one of a kind work, right?

00:26:26.350 --> 00:26:32.432
<v Moritz Stefaner>And now the expectation is you do that, but also make it repeatable. Right?

00:26:32.892 --> 00:26:35.253
<v Gabrielle Mérite>And so I think there's an interesting tension there.

00:26:35.253 --> 00:26:36.233
<v Moritz Stefaner>Yeah.

00:26:36.233 --> 00:26:39.694
<v Gabrielle Mérite>It's definitely a challenge. It's actually quite interesting because we end up creating,

00:26:39.694 --> 00:26:43.836
<v Gabrielle Mérite>to me, it's almost like I split the guidelines into traditional charts with

00:26:43.836 --> 00:26:47.837
<v Gabrielle Mérite>the most traditional bar charts, bar charts, whatever you need to have that

00:26:47.837 --> 00:26:50.418
<v Gabrielle Mérite>needs to be made in PowerPoint, like we've got custom design,

00:26:50.418 --> 00:26:53.199
<v Gabrielle Mérite>especially if we have users that are not designers.

00:26:53.199 --> 00:26:57.881
<v Gabrielle Mérite>So PowerPoint, Canvas, RowGraph, the easy building building blocks that can

00:26:57.881 --> 00:27:01.542
<v Gabrielle Mérite>be reproduced and used for anything we port. But then we usually have a second

00:27:01.542 --> 00:27:04.303
<v Gabrielle Mérite>section that's for designers, an information designer.

00:27:05.303 --> 00:27:09.065
<v Gabrielle Mérite>And sometimes it can overlap a little bit. It can be very simple things that

00:27:09.065 --> 00:27:12.506
<v Gabrielle Mérite>you can do. Adding a shadow, adding a texture, photography.

00:27:13.726 --> 00:27:17.407
<v Gabrielle Mérite>How do you use photography? Do you crop it? Do you not crop it? Is it textured?

00:27:17.768 --> 00:27:23.029
<v Gabrielle Mérite>Is it black and white? Does it use a color? So this is something that we add

00:27:23.029 --> 00:27:27.931
<v Gabrielle Mérite>that's almost branding and that adds customization into the guidelines.

00:27:27.931 --> 00:27:32.453
<v Moritz Stefaner>Cool. Yeah, that makes a lot of sense. And yeah, it's super interesting.

00:27:32.853 --> 00:27:36.454
<v Moritz Stefaner>Ellen, I could imagine your process is totally different because you don't work

00:27:36.454 --> 00:27:42.416
<v Moritz Stefaner>in an agency, but it's more this ongoing big ship instead of the little dinghy

00:27:42.416 --> 00:27:44.577
<v Moritz Stefaner>with the little party on it.

00:27:44.577 --> 00:27:48.498
<v Alan Wilson>Yeah, yeah. Earlier in my career, I worked for agency.

00:27:49.799 --> 00:27:53.400
<v Alan Wilson>And we did a lot of brand guides and things of that nature, which certainly

00:27:53.400 --> 00:27:57.962
<v Alan Wilson>informed a lot of the work that I do now, but yeah, it is different.

00:27:57.962 --> 00:28:02.804
<v Alan Wilson>And I do think there's no one process for this stuff. It really is,

00:28:02.804 --> 00:28:08.586
<v Alan Wilson>part of the problem here is figuring out what an organization needs and how

00:28:08.586 --> 00:28:09.926
<v Alan Wilson>you can best deliver that.

00:28:11.847 --> 00:28:16.329
<v Alan Wilson>But for us, and one of the advantages of being an internal team is we can deliver

00:28:16.329 --> 00:28:19.630
<v Alan Wilson>things incrementally, right? It's not a single deliverable.

00:28:21.531 --> 00:28:25.172
<v Alan Wilson>We can do something and then add to that over time.

00:28:25.772 --> 00:28:30.694
<v Alan Wilson>And so that's the approach that we've taken is, and we try and prioritize the

00:28:30.694 --> 00:28:34.015
<v Alan Wilson>most important, most valuable, the things that are gonna have the biggest impact

00:28:34.015 --> 00:28:35.416
<v Alan Wilson>and then keep adding to that.

00:28:35.896 --> 00:28:40.487
<v Alan Wilson>And at some point we'll reach a threshold where, the incremental value isn't

00:28:40.487 --> 00:28:41.898
<v Alan Wilson>worth the incremental cost.

00:28:43.099 --> 00:28:46.780
<v Alan Wilson>Be that, actually monetary costs are just costing complexity because as your

00:28:46.780 --> 00:28:53.314
<v Alan Wilson>system grows, You can't grow indefinitely or it becomes unusable because it's

00:28:53.314 --> 00:28:54.427
<v Alan Wilson>too big and too complicated.

00:28:57.155 --> 00:29:01.897
<v Alan Wilson>Starting to run up against the bounds of what we feel is an appropriate level of complexity.

00:29:02.237 --> 00:29:07.859
<v Alan Wilson>But yeah, we do start with the end in mind.

00:29:07.859 --> 00:29:13.361
<v Alan Wilson>So we'll often produce a lot of example screens and visualizations and UIs and

00:29:13.361 --> 00:29:21.443
<v Alan Wilson>then write the guidelines that would produce those, if that makes sense. So we work backwards.

00:29:21.443 --> 00:29:26.225
<v Moritz Stefaner>Retrofit, basically. What would have been the rules that would have made these

00:29:26.225 --> 00:29:28.106
<v Moritz Stefaner>choice that obviously seem to work.

00:29:28.106 --> 00:29:33.197
<v Alan Wilson>Exactly. I feel like that's a good approach.

00:29:34.988 --> 00:29:38.689
<v Alan Wilson>But at some point you have enough guidelines that you don't have to start with

00:29:38.689 --> 00:29:42.570
<v Alan Wilson>the end and you can just take what's existing and expand it a little and then

00:29:42.570 --> 00:29:46.632
<v Alan Wilson>see what comes out of it. Yeah.

00:29:46.632 --> 00:29:50.413
<v Moritz Stefaner>That's something we also struggled with a lot is you want to get started somewhere

00:29:50.413 --> 00:29:55.815
<v Moritz Stefaner>and build stuff and see stuff. Otherwise, how could you even progress in the

00:29:55.815 --> 00:30:00.177
<v Moritz Stefaner>project? project, right? You need something visual to work with and to debate.

00:30:00.997 --> 00:30:04.519
<v Moritz Stefaner>At the same time, you feel like it's such a big system. And if we just keep

00:30:04.519 --> 00:30:08.660
<v Moritz Stefaner>making graphics, you know, it's never be a proper system system, right?

00:30:08.660 --> 00:30:13.742
<v Moritz Stefaner>And so when when do you introduce these rules? Or do you redo all the example

00:30:13.742 --> 00:30:17.364
<v Moritz Stefaner>charts you did before if some design decision changes?

00:30:17.724 --> 00:30:23.606
<v Moritz Stefaner>Like, you know, how do you keep it dynamic also? And one thing I found there

00:30:23.606 --> 00:30:27.348
<v Moritz Stefaner>is this design tokens approach that I'm super excited about.

00:30:27.348 --> 00:30:31.230
<v Moritz Stefaner>It's like, so if you're a bit technical inclined or you like coding anyways,

00:30:31.230 --> 00:30:36.392
<v Moritz Stefaner>then I think that's worth looking into because it's a really neat way to sort

00:30:36.392 --> 00:30:39.613
<v Moritz Stefaner>of store all the basic design decisions in the standardized format.

00:30:39.613 --> 00:30:44.977
<v Moritz Stefaner>And then ideally if the brand color changes or if the background color changes,

00:30:44.977 --> 00:30:47.662
<v Moritz Stefaner>it all trickles through your implementations.

00:30:50.036 --> 00:30:52.776
<v Moritz Stefaner>There's also the risk that you could then keep perfecting that system.

00:30:57.138 --> 00:31:03.680
<v Moritz Stefaner>And it becomes a little hobby to clean the token structure and rethink about the hierarchies then.

00:31:04.761 --> 00:31:08.362
<v Moritz Stefaner>But I think that helped me a lot to think about, okay, what are the building blocks?

00:31:10.102 --> 00:31:14.064
<v Moritz Stefaner>We need a background color. We also need a sort of a shaded background color.

00:31:14.064 --> 00:31:16.704
<v Moritz Stefaner>We need two text colors or maybe three, right?

00:31:19.086 --> 00:31:20.706
<v Moritz Stefaner>Them by how they look, but what

00:31:20.706 --> 00:31:24.287
<v Moritz Stefaner>they do. Oh, it's the high contrast or the low contrast version of it.

00:31:24.287 --> 00:31:29.909
<v Moritz Stefaner>And that helped me a lot to think about it in a structured way on the basic

00:31:29.909 --> 00:31:33.090
<v Moritz Stefaner>LEGO building block level and stay flexible in terms of, oh,

00:31:33.090 --> 00:31:35.951
<v Moritz Stefaner>I think we should change the text color on all charts.

00:31:35.951 --> 00:31:39.712
<v Moritz Stefaner>That was much easier because we had that system in place. So yeah.

00:31:42.413 --> 00:31:47.455
<v Gabrielle Mérite>That's the benefits of design systems. Because I think instead of the GAN line

00:31:47.455 --> 00:31:53.057
<v Gabrielle Mérite>constrained versus as a design system and tokens and components and patterns

00:31:53.057 --> 00:31:54.537
<v Gabrielle Mérite>help you be more flexible.

00:31:54.537 --> 00:31:58.318
<v Gabrielle Mérite>In my opinion, it's like, it's more, we're giving you the blocks and then you can make it yourself.

00:31:58.859 --> 00:32:02.279
<v Gabrielle Mérite>And here are just a couple of rules about big mistakes you could make.

00:32:03.480 --> 00:32:06.120
<v Gabrielle Mérite>And you know, at Pentagram we do a lot of just the rules only.

00:32:06.561 --> 00:32:10.782
<v Gabrielle Mérite>And I think that can be constraining and not flexible for an organization.

00:32:12.321 --> 00:32:19.604
<v Alan Wilson>Yeah, on the flip side, I think it allows that creative work to have greater impact.

00:32:22.705 --> 00:32:27.227
<v Alan Wilson>So if you have to design every chart by hand, you spend a lot of time designing

00:32:27.227 --> 00:32:29.667
<v Alan Wilson>the same thing again and again and again and again.

00:32:30.248 --> 00:32:34.329
<v Alan Wilson>But if you have a system and you're designing the system and playing with the

00:32:34.329 --> 00:32:40.151
<v Alan Wilson>tokens, the output scales up really quickly. I mean, it's nearly infinite,

00:32:40.151 --> 00:32:42.972
<v Alan Wilson>You have so many different outputs that can be automated.

00:32:44.273 --> 00:32:46.253
<v Alan Wilson>And so, yeah, it's that flip.

00:32:48.414 --> 00:32:54.076
<v Alan Wilson>The other side of it, right, is that the creativity that is left to do is more

00:32:54.076 --> 00:32:55.517
<v Alan Wilson>impactful and less menial.

00:32:57.008 --> 00:33:00.719
<v Gabrielle Mérite>Yeah, I love that. Because I think sometimes what you hear is,

00:33:00.719 --> 00:33:04.580
<v Gabrielle Mérite>well, we don't need one because we want to do creative things, but it's the opposite.

00:33:04.580 --> 00:33:07.061
<v Gabrielle Mérite>If you remove the small choices of picking the right font sizes,

00:33:07.061 --> 00:33:11.723
<v Gabrielle Mérite>font sizes, picking the right font away, then you can spend more time actually

00:33:11.723 --> 00:33:15.665
<v Gabrielle Mérite>looking for creative solution, but you have some blocks that are predefined

00:33:15.665 --> 00:33:18.146
<v Gabrielle Mérite>that makes it way faster. And repeatable, obviously.

00:33:18.567 --> 00:33:22.909
<v Gabrielle Mérite>So I tend to agree, I think it actually opens up more flexibility, if anything.

00:33:22.909 --> 00:33:29.472
<v Moritz Stefaner>Yeah. But it's an ongoing thing. And I think another big challenge is,

00:33:29.472 --> 00:33:32.393
<v Moritz Stefaner>I think the initial version is easy to build, right?

00:33:35.195 --> 00:33:38.757
<v Moritz Stefaner>Like how do you make it grow? How does it evolve over time?

00:33:39.297 --> 00:33:44.720
<v Moritz Stefaner>And how do you not have it end up like the German administration that has lots

00:33:44.720 --> 00:33:51.426
<v Moritz Stefaner>of really good rules that in isolation make a lot of sense, but it's a bit too many of them overall.

00:33:52.709 --> 00:33:54.781
<v Moritz Stefaner>And so how do you manage?

00:33:57.382 --> 00:34:02.123
<v Moritz Stefaner>Complexity when things grow, right? Or even out of your hands at some point.

00:34:02.123 --> 00:34:04.204
<v Moritz Stefaner>Like, what's the life cycle of the whole thing?

00:34:05.005 --> 00:34:08.946
<v Alan Wilson>Well, my experience is the opposite. I think the first step is the hardest. Interesting.

00:34:09.536 --> 00:34:14.008
<v Alan Wilson>The initial thing is so hard. Maybe it's just my nature that I want it to be

00:34:14.008 --> 00:34:16.249
<v Alan Wilson>whole or complete in some way.

00:34:16.249 --> 00:34:20.510
<v Alan Wilson>And just right from the beginning. Exactly. I have that kind of perfectionist

00:34:20.510 --> 00:34:23.191
<v Alan Wilson>mentality. I don't want to put something out out there until it's ready and

00:34:23.191 --> 00:34:24.872
<v Alan Wilson>I really am confident in it.

00:34:25.592 --> 00:34:28.853
<v Alan Wilson>But my, and so my experience is that part is the difficult part,

00:34:28.853 --> 00:34:33.305
<v Alan Wilson>but once you do have something out there, then delivering incremental value

00:34:33.305 --> 00:34:36.856
<v Alan Wilson>is a lot easier because you have a good feedback loop, right?

00:34:36.856 --> 00:34:42.318
<v Alan Wilson>You know what people are using, you know what they like, you're hearing feedback.

00:34:42.318 --> 00:34:47.100
<v Alan Wilson>I mean, designers have feedback, right? They'll tell you what is and isn't working

00:34:47.100 --> 00:34:50.681
<v Alan Wilson>for them and you can spend time with them to get into the why.

00:34:50.741 --> 00:34:55.943
<v Alan Wilson>And then for me, the rest of the process is more natural. It's a lot more service

00:34:55.943 --> 00:34:58.544
<v Alan Wilson>oriented where you're like, oh, okay, well, this isn't working,

00:34:58.544 --> 00:35:03.526
<v Alan Wilson>so let's focus on fixing it, or this doesn't exist yet, so let's create that thing.

00:35:05.047 --> 00:35:09.288
<v Alan Wilson>And it's really just how many people need that. And that can be a little more

00:35:09.288 --> 00:35:13.310
<v Alan Wilson>harder to determine, but you're just trying to measure impact.

00:35:14.911 --> 00:35:19.252
<v Moritz Stefaner>Well, like, Gabby and I, we are brought in as external consultants, your in-house.

00:35:21.193 --> 00:35:28.195
<v Moritz Stefaner>What do you think? What can the roles of external consultants be versus in-house folks?

00:35:28.755 --> 00:35:33.217
<v Moritz Stefaner>I've also met people who said, design system? No, we don't work with external

00:35:33.217 --> 00:35:34.637
<v Moritz Stefaner>people on our design system.

00:35:34.637 --> 00:35:38.869
<v Moritz Stefaner>That doesn't make sense, right? Because they've begun in three months,

00:35:38.869 --> 00:35:44.421
<v Moritz Stefaner>then it takes care of the actual work that happens afterwards.

00:35:46.062 --> 00:35:52.147
<v Moritz Stefaner>Or is there something we can do? I don't know. What's going to take on that?

00:35:52.147 --> 00:35:57.674
<v Alan Wilson>Well, at Adobe, we treat Spectrum like a product, like any other product at Adobe.

00:35:57.674 --> 00:36:02.839
<v Alan Wilson>It's a thing that we build. The differences, our user base is almost entirely

00:36:02.839 --> 00:36:08.144
<v Alan Wilson>internal. We do have some external people, vendors and partners and so on,

00:36:08.144 --> 00:36:09.185
<v Alan Wilson>and so on that use Vectrum.

00:36:10.139 --> 00:36:16.281
<v Alan Wilson>The primary audience is internal. And so I don't know how you would have a similar model with an agency.

00:36:17.421 --> 00:36:21.843
<v Alan Wilson>Not to say that agencies don't play a role in creating some of the initial work

00:36:21.843 --> 00:36:27.605
<v Alan Wilson>or coming in and helping you audit it or bring new life to it, bring new ideas.

00:36:30.466 --> 00:36:34.037
<v Alan Wilson>Sometimes things can get a little stale internally because you're just kind

00:36:34.037 --> 00:36:38.089
<v Alan Wilson>of recycling the same set of ideas among the same set of people,

00:36:38.089 --> 00:36:40.130
<v Alan Wilson>so fresh perspective can be really useful.

00:36:41.730 --> 00:36:44.571
<v Alan Wilson>I also think it depends on the nature of your organization, how big it is,

00:36:44.571 --> 00:36:49.953
<v Alan Wilson>right? If you are a relatively small startup, you can't spare even a single

00:36:49.953 --> 00:36:54.635
<v Alan Wilson>person to run a design system. That would be ludicrous to consider.

00:36:55.035 --> 00:36:59.257
<v Alan Wilson>And so having someone build something for you that you can just use and maybe

00:36:59.257 --> 00:37:03.278
<v Alan Wilson>touch up every year or so might be a better route to go.

00:37:04.479 --> 00:37:06.760
<v Alan Wilson>There's as many solutions as there are problems.

00:37:06.760 --> 00:37:10.861
<v Moritz Stefaner>Yeah, that's true. Gabby, any thoughts on that?

00:37:10.861 --> 00:37:15.703
<v Gabrielle Mérite>No, you raise a good point. Because I found it frustrating as a designer who

00:37:15.703 --> 00:37:20.544
<v Gabrielle Mérite>makes guidelines as a contractor, to just, we dropped it to a client and we're out of here.

00:37:21.425 --> 00:37:24.886
<v Gabrielle Mérite>Like, no feedback matters. There's a scope that's defined, there's a budget

00:37:24.886 --> 00:37:28.427
<v Gabrielle Mérite>that's defined. So if the scope was that we don't get feedback on it,

00:37:28.427 --> 00:37:30.908
<v Gabrielle Mérite>we don't get feedback on it. Even though it works or it doesn't work,

00:37:30.908 --> 00:37:32.969
<v Gabrielle Mérite>it doesn't matter almost because we get paid.

00:37:34.009 --> 00:37:35.930
<v Gabrielle Mérite>Unfortunately, that's how the business works.

00:37:38.731 --> 00:37:42.912
<v Gabrielle Mérite>I hear you, Alan, and I agree. I think there's a space for it where a small

00:37:42.912 --> 00:37:46.313
<v Gabrielle Mérite>organization cannot afford, they don't have the time and the resources to set

00:37:46.313 --> 00:37:48.954
<v Gabrielle Mérite>it up, like the initial big phase of doing that work.

00:37:49.814 --> 00:37:54.556
<v Gabrielle Mérite>But I do think that the development and the incremental changes needs to be

00:37:54.556 --> 00:37:57.537
<v Gabrielle Mérite>done internally, otherwise you're going to end up paying an external agency

00:37:57.537 --> 00:38:01.618
<v Gabrielle Mérite>for everything and they are not as familiar to your organization needs.

00:38:02.042 --> 00:38:03.304
<v Gabrielle Mérite>Than the organization itself.

00:38:05.928 --> 00:38:09.089
<v Gabrielle Mérite>As an extraordinary don't say that we have a value that we bring.

00:38:09.089 --> 00:38:11.650
<v Gabrielle Mérite>Maybe it's at the initial phase, maybe it's at a big review phase,

00:38:11.650 --> 00:38:15.451
<v Gabrielle Mérite>maybe it's just to, you know, nobody has time. So, you know,

00:38:15.451 --> 00:38:18.212
<v Gabrielle Mérite>you give them, you let them do kind of the work and then you take over.

00:38:18.952 --> 00:38:23.174
<v Gabrielle Mérite>But yeah, we cannot if you're going to maintain it, it has to be done internally.

00:38:23.174 --> 00:38:27.735
<v Gabrielle Mérite>I think, you know, oh, sometimes we can come at consulting to solve issues.

00:38:27.735 --> 00:38:33.077
<v Gabrielle Mérite>But I really think that, you know, our values are definitely limited here. We can't do it all.

00:38:33.298 --> 00:38:37.419
<v Alan Wilson>Well, and I think that's part of the value of a design system,

00:38:37.419 --> 00:38:39.359
<v Alan Wilson>is it needs to be a living thing.

00:38:40.120 --> 00:38:45.822
<v Alan Wilson>Because if it's static, it just doesn't continue to solve problems.

00:38:46.142 --> 00:38:50.263
<v Alan Wilson>You need it to evolve to solve the different problems that you encounter.

00:38:50.263 --> 00:38:55.625
<v Moritz Stefaner>So, yeah. Yeah, and I've been thinking a lot about that too.

00:38:55.625 --> 00:39:02.027
<v Moritz Stefaner>How do we actually make sure people use the things that we design and keep using?

00:39:02.027 --> 00:39:05.129
<v Moritz Stefaner>And they say like software is either maintained or abandoned.

00:39:05.129 --> 00:39:08.230
<v Moritz Stefaner>And I feel like the same might happen with design systems.

00:39:08.230 --> 00:39:12.091
<v Moritz Stefaner>If you don't like have somebody internally always pushing for this,

00:39:12.091 --> 00:39:15.773
<v Moritz Stefaner>the system we use, it's cool. This is how you use it. Right.

00:39:15.773 --> 00:39:20.135
<v Moritz Stefaner>And so you need also these these advocates and people who do onboarding with

00:39:20.135 --> 00:39:22.155
<v Moritz Stefaner>new folks to keep it going and so on.

00:39:22.616 --> 00:39:27.657
<v Moritz Stefaner>And yeah, and somehow you need to think about that whole social process around it as well.

00:39:27.657 --> 00:39:32.539
<v Moritz Stefaner>Right. Yeah, the other thing I was thinking about, maybe it's good also not

00:39:32.539 --> 00:39:38.682
<v Moritz Stefaner>to have so much rules, but more, maybe supply more templates or tools or like

00:39:38.682 --> 00:39:42.343
<v Moritz Stefaner>really easy one-click solutions, you know, to do something.

00:39:42.343 --> 00:39:46.905
<v Moritz Stefaner>So think about what's the threshold to even using your design system.

00:39:46.905 --> 00:39:52.187
<v Moritz Stefaner>Like if it seems to be a big burden or like a big like, oh, I need to read this

00:39:52.187 --> 00:39:57.691
<v Moritz Stefaner>whole book before I can make a single tried, you know, then that immediately might be off putting.

00:39:57.691 --> 00:40:01.095
<v Moritz Stefaner>And if you're then not there to enforce it, it's like, yeah,

00:40:01.095 --> 00:40:04.378
<v Moritz Stefaner>we don't care so much about this big rule book.

00:40:06.881 --> 00:40:10.083
<v Moritz Stefaner>So yeah, but then again, you need to know really well what people want to make

00:40:10.083 --> 00:40:12.526
<v Moritz Stefaner>with it. And maybe that's often not that clear.

00:40:13.547 --> 00:40:14.948
<v Gabrielle Mérite>It's interesting to think that...

00:40:15.946 --> 00:40:19.307
<v Gabrielle Mérite>External contractors like me, for instance, are designer and use guidelines.

00:40:19.727 --> 00:40:22.928
<v Gabrielle Mérite>So we are often like the consumer of the product itself.

00:40:23.349 --> 00:40:28.330
<v Gabrielle Mérite>And so I guess the way I see it, I've changed quite a bit of the way Starguide

00:40:28.330 --> 00:40:32.832
<v Gabrielle Mérite>in agency work is often, Starguide only is a big PDF of 60 pages.

00:40:32.832 --> 00:40:38.114
<v Gabrielle Mérite>You know, PDF, all school, sometimes made for print. So vertical, right?

00:40:38.114 --> 00:40:39.134
<v Moritz Stefaner>Also books, real books.

00:40:41.435 --> 00:40:44.376
<v Gabrielle Mérite>So it's interesting how you can just come in and be like, I know what I would

00:40:44.376 --> 00:40:47.497
<v Gabrielle Mérite>like. So to your point, I think sometimes we don't have access,

00:40:47.497 --> 00:40:50.358
<v Gabrielle Mérite>at least I didn't have access to the designer that would be using the book,

00:40:50.358 --> 00:40:52.219
<v Gabrielle Mérite>but I was like, here's what I wish I had.

00:40:53.300 --> 00:40:57.501
<v Gabrielle Mérite>So, you know, text style, paragraph style made in advance in Illustrator.

00:40:58.501 --> 00:41:00.222
<v Gabrielle Mérite>Paragraph style made in advance in Figma.

00:41:00.222 --> 00:41:01.682
<v Moritz Stefaner>Template documents, right?

00:41:01.682 --> 00:41:04.123
<v Gabrielle Mérite>Just that kind of thing. I don't want to have the copy paste,

00:41:04.123 --> 00:41:05.644
<v Gabrielle Mérite>the goddamn hex code anymore.

00:41:07.305 --> 00:41:10.446
<v Gabrielle Mérite>Just things like that. So I think it's interesting how, you know,

00:41:10.446 --> 00:41:14.068
<v Gabrielle Mérite>But sometimes we forget also, we do things a certain way.

00:41:14.488 --> 00:41:19.351
<v Gabrielle Mérite>So it's interesting how sometimes having somebody new coming in can help with

00:41:19.351 --> 00:41:22.873
<v Gabrielle Mérite>that or can look at it being like, I'm not sure this is working for me.

00:41:22.873 --> 00:41:25.914
<v Gabrielle Mérite>Because I also find places where they're like, well, we do use the brand guidelines.

00:41:25.914 --> 00:41:27.095
<v Gabrielle Mérite>We don't really know what we need.

00:41:30.177 --> 00:41:34.699
<v Gabrielle Mérite>So there's a balance in everything of asking the audience, having your own input

00:41:34.699 --> 00:41:38.201
<v Gabrielle Mérite>and being flexible enough to change how we do things every time.

00:41:38.201 --> 00:41:40.322
<v Gabrielle Mérite>For a new client, for instance, I change it every time.

00:41:40.863 --> 00:41:44.945
<v Gabrielle Mérite>Everything, including the basic charts or the decision charts,

00:41:44.945 --> 00:41:49.406
<v Gabrielle Mérite>and decided what chart to use when, It's different for every client, depending on the topic.

00:41:50.824 --> 00:41:55.426
<v Gabrielle Mérite>So it's definitely interesting how the audience can, can like force us to adapt

00:41:55.426 --> 00:42:00.367
<v Gabrielle Mérite>every time, even for just the initial brief. And then I can imagine internally how that changes.

00:42:00.367 --> 00:42:00.787
<v Moritz Stefaner>Yeah.

00:42:01.928 --> 00:42:08.070
<v Alan Wilson>I mean, I have a very similar experience. The very first foray I had into this

00:42:08.070 --> 00:42:12.551
<v Alan Wilson>was like a 60 page PDF, exactly as you described.

00:42:13.212 --> 00:42:17.473
<v Alan Wilson>And we printed it out and it actually, everyone loved it. Cause they had,

00:42:17.473 --> 00:42:19.233
<v Alan Wilson>we didn't have anything like that before.

00:42:19.674 --> 00:42:23.195
<v Alan Wilson>And so people like engineers and designers had it at their desk and they'd have

00:42:23.195 --> 00:42:28.457
<v Alan Wilson>it flipped open to pages, but they would be typing in those X codes and rebuilding

00:42:28.457 --> 00:42:29.407
<v Alan Wilson>the buttons themselves.

00:42:30.558 --> 00:42:34.199
<v Alan Wilson>And so it was only a week or two before an engineer was like,

00:42:34.199 --> 00:42:38.120
<v Alan Wilson>can we just get this in Git so that I don't have to rebuild all this stuff?

00:42:38.120 --> 00:42:43.222
<v Alan Wilson>And we had designers that are like, where's the, this is how old I am as a designer,

00:42:43.222 --> 00:42:47.043
<v Alan Wilson>where's the Illustrator template for this or the Photoshop template for this?

00:42:47.043 --> 00:42:49.663
<v Moritz Stefaner>Or the palettes you can download and all that stuff.

00:42:50.864 --> 00:42:52.985
<v Gabrielle Mérite>Yeah, I just want an AAC file with my call of help.

00:42:52.985 --> 00:42:58.947
<v Alan Wilson>Thank you. Exactly. And so we started to create those. And so it slowly evolved

00:42:58.947 --> 00:43:05.249
<v Alan Wilson>from a PDF that people printed and kept on their desk to a website with downloadable resources.

00:43:05.950 --> 00:43:09.411
<v Alan Wilson>And I think it's really important to meet people where they are.

00:43:10.621 --> 00:43:15.233
<v Alan Wilson>There are times when you need to push people into new and different tools to

00:43:15.233 --> 00:43:19.395
<v Alan Wilson>better do their job. But for the most part, they have the tools to do their

00:43:19.395 --> 00:43:21.575
<v Alan Wilson>job and they just need you to provide the resources.

00:43:21.995 --> 00:43:25.136
<v Alan Wilson>And so if your users are in PowerPoint.

00:43:25.136 --> 00:43:26.637
<v Moritz Stefaner>Make it easier.

00:43:26.637 --> 00:43:29.758
<v Alan Wilson>Exactly, if they're in PowerPoint and that's what they're using to build their

00:43:29.758 --> 00:43:33.740
<v Alan Wilson>charts or Excel, you've got to provide those Excel and PowerPoint templates.

00:43:34.540 --> 00:43:38.441
<v Alan Wilson>It pains me sometimes to say that, but it's true. And likewise,

00:43:38.441 --> 00:43:43.503
<v Alan Wilson>if they're in R or Tableau, use the tools that they use, provide the resources

00:43:43.503 --> 00:43:49.426
<v Alan Wilson>in that tool's format that form tools language and you'll be more successful by far.

00:43:51.206 --> 00:43:56.347
<v Moritz Stefaner>Yeah, I think that's interesting. And I think that also, if you take that super serious means,

00:43:56.347 --> 00:43:59.869
<v Moritz Stefaner>really, you can't be too picky about all this, the design details,

00:43:59.869 --> 00:44:05.751
<v Moritz Stefaner>really, like, what the spacing is exactly, or, you know, what type of tricky

00:44:05.751 --> 00:44:10.473
<v Moritz Stefaner>access configuration you have come up with, but really be more really clear

00:44:10.473 --> 00:44:12.533
<v Moritz Stefaner>about these are our underlying principles.

00:44:12.934 --> 00:44:16.375
<v Moritz Stefaner>And this is what, like, qualities all all of our charts should have in terms

00:44:16.375 --> 00:44:23.958
<v Moritz Stefaner>of accessibility or voice or whatever, but then being really flexible about how that happens.

00:44:23.958 --> 00:44:26.779
<v Moritz Stefaner>And maybe there as a designer, we need to be a bit more like,

00:44:26.779 --> 00:44:33.742
<v Moritz Stefaner>the details don't matter that much, it's fine as long as the general direction is good.

00:44:34.682 --> 00:44:39.684
<v Alan Wilson>Or am I being too generous here? No, there's a lot of truth to that.

00:44:39.684 --> 00:44:44.146
<v Alan Wilson>But I feel like one of my roles as a designer is to never give up on the ideal, right?

00:44:45.286 --> 00:44:51.308
<v Alan Wilson>So I always- It's facing matters. It does. That rounded corner makes a difference,

00:44:51.308 --> 00:44:58.171
<v Alan Wilson>right? It's only a one pixel axi, but just round that corner and it just makes it sing, right?

00:44:59.411 --> 00:45:03.152
<v Alan Wilson>And you can get that if they're working in one tool, but in another tool,

00:45:03.152 --> 00:45:04.613
<v Alan Wilson>like it just doesn't support that.

00:45:04.613 --> 00:45:10.935
<v Alan Wilson>So there's a reality to what you're saying, but I do think we need to advocate

00:45:10.935 --> 00:45:15.256
<v Alan Wilson>for the ideal and then compromise as needed.

00:45:15.256 --> 00:45:21.299
<v Moritz Stefaner>Yeah, yeah. You can have one gold standard implementation also,

00:45:21.299 --> 00:45:23.919
<v Moritz Stefaner>where you say this is how it really should look like.

00:45:24.340 --> 00:45:27.181
<v Moritz Stefaner>That's how it's meant, but then maybe flexible on.

00:45:28.561 --> 00:45:32.982
<v Moritz Stefaner>In a different context, it's fine if it doesn't hit all the design details.

00:45:32.982 --> 00:45:39.825
<v Gabrielle Mérite>I also found it, it's often that, to me, the pixel close, those precise details

00:45:39.825 --> 00:45:44.777
<v Gabrielle Mérite>helpful sometimes for specifically non-designers or people who are like not,

00:45:46.049 --> 00:45:50.891
<v Gabrielle Mérite>I think this, because we can't teach them design, we have to give them really

00:45:50.891 --> 00:45:57.873
<v Gabrielle Mérite>precise rules so that they don't have the understanding of what the right spacing in, text hierarchy.

00:45:58.213 --> 00:46:01.635
<v Gabrielle Mérite>And so we see it regularly when researchers make PowerPoint,

00:46:01.635 --> 00:46:03.695
<v Gabrielle Mérite>right? No offense to researchers out here.

00:46:04.736 --> 00:46:08.957
<v Gabrielle Mérite>We respect you, we used to be there, we know how it feels. But I think sometimes

00:46:08.957 --> 00:46:12.018
<v Gabrielle Mérite>they just don't have the sense, they don't have time to even learn,

00:46:12.018 --> 00:46:13.559
<v Gabrielle Mérite>and we don't wanna make them designers.

00:46:13.879 --> 00:46:17.340
<v Gabrielle Mérite>So it's more, those rules can also be set up sometimes just to actually help

00:46:17.340 --> 00:46:20.661
<v Gabrielle Mérite>them without having to like give them free workshop on how to do database.

00:46:20.661 --> 00:46:24.956
<v Gabrielle Mérite>It's just like, here is it easy. You just have to follow this exact guidelines,

00:46:24.956 --> 00:46:28.984
<v Gabrielle Mérite>this exact pixel, this exact roundling corner in your software,

00:46:28.984 --> 00:46:33.386
<v Gabrielle Mérite>we give it to you so that you don't have to think about it really and to make your job faster.

00:46:34.946 --> 00:46:37.387
<v Gabrielle Mérite>Otherwise, interpretation is nice, especially as designers, we know how to do

00:46:37.387 --> 00:46:42.169
<v Gabrielle Mérite>things. So we feel more comfortable taking some freedom into interpretation of the guidelines.

00:46:42.549 --> 00:46:47.391
<v Gabrielle Mérite>But I think for other users, it might be really important to just help with

00:46:47.391 --> 00:46:50.412
<v Gabrielle Mérite>that and just give really precise guidelines that just makes their work easier.

00:46:50.412 --> 00:46:54.934
<v Moritz Stefaner>But then I'm thinking if the exact one-to-one look really matters,

00:46:54.934 --> 00:46:58.595
<v Moritz Stefaner>then maybe it's actually better to supply a software that creates the thing

00:46:58.595 --> 00:47:05.818
<v Moritz Stefaner>as it should look, or a template, because otherwise you end up with really long, super detailed specs.

00:47:05.818 --> 00:47:08.299
<v Gabrielle Mérite>I think so, but it's hard to sell to clients sometimes.

00:47:10.640 --> 00:47:15.262
<v Gabrielle Mérite>At the industry level, I think that's what I run into is often we get scoped

00:47:15.262 --> 00:47:17.303
<v Gabrielle Mérite>for just the guidelines and no templates.

00:47:17.303 --> 00:47:19.924
<v Gabrielle Mérite>And they may come back six months later and ask for the templates.

00:47:19.924 --> 00:47:23.505
<v Gabrielle Mérite>That happens regularly. But you wish you could sell it and be like,

00:47:23.505 --> 00:47:26.326
<v Gabrielle Mérite>you're going to need this. Believe me, you're going to need this.

00:47:26.827 --> 00:47:30.688
<v Moritz Stefaner>And the guidelines. Yeah, this is where this initial scoping comes in,

00:47:30.688 --> 00:47:33.970
<v Moritz Stefaner>in terms of, okay, what do you hope to achieve? Who is this for?

00:47:34.512 --> 00:47:37.556
<v Moritz Stefaner>What are the actual things we should supply because of that, right?

00:47:38.850 --> 00:47:41.951
<v Moritz Stefaner>Yeah, interesting. And at the same time, the whole tooling landscape is shifting

00:47:41.951 --> 00:47:44.392
<v Moritz Stefaner>too, right? It's like, what do you do your charts in?

00:47:45.373 --> 00:47:52.095
<v Moritz Stefaner>There's a new answer to that every two years. And ideally, our stuff should

00:47:52.095 --> 00:47:55.817
<v Moritz Stefaner>survive a few of these iterations as well in terms of tooling.

00:47:55.817 --> 00:47:59.138
<v Moritz Stefaner>And so there are a lot of challenges there.

00:48:01.180 --> 00:48:04.040
<v Moritz Stefaner>I think we need to sort of wrap things up semi-soon.

00:48:05.581 --> 00:48:09.803
<v Moritz Stefaner>I have two more questions. So one is about are there any caveats,

00:48:09.803 --> 00:48:14.785
<v Moritz Stefaner>traps, failures, things you wish you would have known before somebody sent you

00:48:14.785 --> 00:48:22.969
<v Moritz Stefaner>on that impossible journey that you could share with our audience who might be new to the field,

00:48:22.969 --> 00:48:27.791
<v Moritz Stefaner>like something valuable to avoid or just stuff that happened.

00:48:29.171 --> 00:48:32.772
<v Alan Wilson>Oh boy, I would say be humble and listen.

00:48:34.213 --> 00:48:38.815
<v Alan Wilson>I remember early on I had just discovered histograms and I'm like,

00:48:38.815 --> 00:48:43.697
<v Alan Wilson>oh histograms, okay. And I thought I understood what a histogram was.

00:48:44.277 --> 00:48:51.560
<v Alan Wilson>And I was writing guidelines and explaining to people and six months later I

00:48:51.560 --> 00:48:54.981
<v Alan Wilson>realized I was wrong about some fundamental things.

00:48:56.882 --> 00:49:02.744
<v Alan Wilson>And it was difficult to eat that crow and fix the wrongs that I had done.

00:49:03.484 --> 00:49:07.746
<v Alan Wilson>Because people trusted me, right? I taught them things and I thought I was right

00:49:07.746 --> 00:49:12.468
<v Alan Wilson>and they thought I was right. And I wish I had just been taking a little more

00:49:12.468 --> 00:49:16.229
<v Alan Wilson>time to educate myself before I had put forth these things.

00:49:17.792 --> 00:49:23.006
<v Moritz Stefaner>So early feedback and really get people to comment on everything.

00:49:23.006 --> 00:49:23.606
<v Alan Wilson>Yeah, yeah.

00:49:26.106 --> 00:49:30.388
<v Gabrielle Mérite>Yeah, I like that you said people trust me, because to my point,

00:49:30.388 --> 00:49:36.610
<v Gabrielle Mérite>I think, especially at Contractor, we get a lot of trust, and they hire us as experts, right?

00:49:36.610 --> 00:49:41.372
<v Gabrielle Mérite>So we tend to be trusted, and you know, whatever we say, it's going to be the

00:49:41.372 --> 00:49:43.192
<v Gabrielle Mérite>Bible. And I found it problematic.

00:49:43.733 --> 00:49:49.695
<v Gabrielle Mérite>Not problematic, but I found that it's a lot of responsibility that we forget, I think.

00:49:50.535 --> 00:49:54.877
<v Gabrielle Mérite>And I wrote about this recently, but I think especially when we make guidelines

00:49:54.877 --> 00:49:58.958
<v Gabrielle Mérite>that are going to be used potentially by hundreds of people or templates,

00:49:58.958 --> 00:50:01.459
<v Gabrielle Mérite>it's, we have such a responsibility to do them properly.

00:50:01.819 --> 00:50:05.221
<v Gabrielle Mérite>So not just for the users so that they're usable, easy to understand,

00:50:05.221 --> 00:50:09.943
<v Gabrielle Mérite>et cetera, et cetera. But I think we need to meet the big caveat when I got

00:50:09.943 --> 00:50:13.504
<v Gabrielle Mérite>lines is we don't approach like ethics in database and guidelines.

00:50:13.504 --> 00:50:15.445
<v Gabrielle Mérite>We're like, here's the job. This is how you make it.

00:50:15.865 --> 00:50:20.006
<v Gabrielle Mérite>Especially when you like me and you work with a lot of data that like social data. So bad people.

00:50:20.707 --> 00:50:24.728
<v Gabrielle Mérite>Of course, I think it's getting more common, accessibility, some kind of rules.

00:50:25.288 --> 00:50:28.289
<v Gabrielle Mérite>It's becoming more common, but I still see a lot of it as just like,

00:50:28.289 --> 00:50:30.210
<v Gabrielle Mérite>here's the colors, here's the thing, do whatever you want.

00:50:30.210 --> 00:50:33.881
<v Gabrielle Mérite>And I just, I want to start this conversation with,

00:50:33.881 --> 00:50:39.813
<v Gabrielle Mérite>you know, maybe we shouldn't, the colors matter, but maybe we should also question

00:50:39.813 --> 00:50:46.135
<v Gabrielle Mérite>like, should guidelines also offer more guidance on when do you actually need to do database?

00:50:46.135 --> 00:50:50.824
<v Gabrielle Mérite>Which database should you be doing? Like should you actually emphasize differences

00:50:50.824 --> 00:50:53.498
<v Gabrielle Mérite>between social groups, ethnicity for instance?

00:50:53.498 --> 00:50:58.960
<v Gabrielle Mérite>Like we have research nowadays that shows that maybe it's a problem to raise awareness this way.

00:50:58.960 --> 00:51:02.681
<v Gabrielle Mérite>And I'm wondering, and I know it's a little further than what designers are,

00:51:02.681 --> 00:51:07.023
<v Gabrielle Mérite>I think we get caught into the detail of design, but at least designers like

00:51:07.023 --> 00:51:09.443
<v Gabrielle Mérite>me who work on guidelines for those big organizations that,

00:51:09.443 --> 00:51:13.265
<v Gabrielle Mérite>you know, approaches like sensitive topics, I'm just wondering if there's a

00:51:13.265 --> 00:51:19.893
<v Gabrielle Mérite>place for us to be more responsible and think twice about the work we do and

00:51:19.893 --> 00:51:21.757
<v Gabrielle Mérite>give guidance on maybe even terminology.

00:51:22.509 --> 00:51:27.080
<v Gabrielle Mérite>Like, how do we use, you know, ethnicities? Yeah, texts. Like,

00:51:27.080 --> 00:51:32.622
<v Gabrielle Mérite>you know, how are we, can we promote transparency in how data is sourced within

00:51:32.622 --> 00:51:35.323
<v Gabrielle Mérite>the guidelines? Like, I think there's so much more we can do with it that's

00:51:35.323 --> 00:51:36.803
<v Gabrielle Mérite>not just design related.

00:51:38.084 --> 00:51:42.625
<v Gabrielle Mérite>So I guess that's my big statement. I just want designers to be a little more,

00:51:42.625 --> 00:51:45.026
<v Gabrielle Mérite>but to also space is happening.

00:51:45.026 --> 00:51:48.047
<v Moritz Stefaner>Think about more than decoration of numbers, right?

00:51:48.047 --> 00:51:52.388
<v Gabrielle Mérite>Yeah. And also have that humility, you know. I think he makes a great point.

00:51:52.388 --> 00:51:56.350
<v Gabrielle Mérite>We are a little bit approaching a top-down approach, like designers say something,

00:51:56.350 --> 00:51:58.130
<v Gabrielle Mérite>and we are problem solvers.

00:51:58.771 --> 00:52:02.372
<v Moritz Stefaner>Yeah, and also the hope is with this design system, it's the Bible.

00:52:02.372 --> 00:52:08.054
<v Moritz Stefaner>It's once and for all, this is how you do it. And we all know this is not how it works.

00:52:09.354 --> 00:52:13.716
<v Moritz Stefaner>You can be brilliant at your job and do it for 30 years, and still every project

00:52:13.716 --> 00:52:16.477
<v Moritz Stefaner>is new, and there's always uncertainties and doubt.

00:52:16.777 --> 00:52:20.258
<v Moritz Stefaner>And you could always do it this way or that way, and in the end you just make

00:52:20.258 --> 00:52:25.120
<v Moritz Stefaner>an informed judgment call. but there's no absolute truth in design, right? And so, yeah.

00:52:27.201 --> 00:52:31.302
<v Alan Wilson>I love that point because I think there's so many decisions that lead up to

00:52:31.302 --> 00:52:32.762
<v Alan Wilson>the final product of a visualization.

00:52:33.863 --> 00:52:40.085
<v Alan Wilson>And a visualization doesn't often acknowledge those things, right?

00:52:40.706 --> 00:52:45.797
<v Alan Wilson>I think that's one of the most problematic pieces of data visualization is because

00:52:45.797 --> 00:52:51.049
<v Alan Wilson>it's so easy to trust. That's why we see so many problems emerge around dishonest

00:52:51.049 --> 00:52:52.510
<v Alan Wilson>charts and things of that nature.

00:52:53.130 --> 00:52:59.253
<v Alan Wilson>Even the most well-intentioned individual is obscuring the actual truth to some

00:52:59.253 --> 00:53:04.274
<v Alan Wilson>extent in an effort to tell a story or to simplify a problem or illustrate a point.

00:53:05.735 --> 00:53:08.896
<v Alan Wilson>So I don't know how to solve that, but, and it goes back to,

00:53:08.896 --> 00:53:12.918
<v Alan Wilson>I guess, one of my earlier points about the desire to educate people,

00:53:12.918 --> 00:53:14.378
<v Alan Wilson>not just about styles, but about

00:53:14.378 --> 00:53:17.599
<v Alan Wilson>data literacy and all the overlaps and intricacies of data visualization.

00:53:20.182 --> 00:53:25.305
<v Alan Wilson>I just, I think that's an important thing. And to your point,

00:53:25.305 --> 00:53:26.766
<v Alan Wilson>Gabriel, we can't lose sight of that.

00:53:28.380 --> 00:53:32.741
<v Gabrielle Mérite>Yeah, I don't know how to do that in guidelines. It's definitely an education maybe,

00:53:32.741 --> 00:53:36.413
<v Gabrielle Mérite>but it is about, I think we tend to focus designer,

00:53:36.413 --> 00:53:40.604
<v Gabrielle Mérite>we're taught for a long time that we are like solution maker,

00:53:40.604 --> 00:53:44.606
<v Gabrielle Mérite>you know, but we should focus on approaches, on like something that's flexible,

00:53:44.606 --> 00:53:49.807
<v Gabrielle Mérite>agile, and that gives space to others to give the opinion and take decision,

00:53:49.807 --> 00:53:52.688
<v Gabrielle Mérite>you know, give them the best tool, including an educative tool,

00:53:52.688 --> 00:53:56.350
<v Gabrielle Mérite>to make those decisions rather than just get really strict guidance that might

00:53:56.350 --> 00:54:02.232
<v Gabrielle Mérite>be also found false or harmful in 20 years, because I think we see a lot of that nowadays.

00:54:03.633 --> 00:54:07.174
<v Moritz Stefaner>Yeah, that's a great point. Maybe it's related to my last provocation that I

00:54:07.174 --> 00:54:11.295
<v Moritz Stefaner>want to throw in here, because maybe I'm just getting old, but I find that a

00:54:11.295 --> 00:54:14.816
<v Moritz Stefaner>lot of design is really boring these days. Like web design is super boring.

00:54:14.816 --> 00:54:17.417
<v Moritz Stefaner>Everything looks the same. There's like big round buttons.

00:54:18.978 --> 00:54:23.199
<v Moritz Stefaner>You know, I feel like there's like five templates and they are just applied all over the whole web.

00:54:24.720 --> 00:54:28.602
<v Moritz Stefaner>And I think in a way it's cool because everything's super easy to use now.

00:54:28.602 --> 00:54:33.003
<v Moritz Stefaner>No surprises. It's like, cool, I know my way around.

00:54:34.004 --> 00:54:38.506
<v Moritz Stefaner>On the other hand, I feel like if we streamline everything and everything gets

00:54:38.506 --> 00:54:45.368
<v Moritz Stefaner>formalized and optimized and templatized and standardized, where's the fun in that?

00:54:48.910 --> 00:54:54.619
<v Moritz Stefaner>No, don't we abstract away all the interesting, a bit uncomfortable,

00:54:54.619 --> 00:54:59.694
<v Moritz Stefaner>weird, edgy things? If everything becomes formalized and standardized?

00:55:00.134 --> 00:55:03.116
<v Moritz Stefaner>And are we contributing to that with our design system work?

00:55:03.116 --> 00:55:05.236
<v Moritz Stefaner>That's something I've been thinking about.

00:55:05.236 --> 00:55:10.128
<v Gabrielle Mérite>I have a thought on that. So it's an interesting question because you said,

00:55:10.128 --> 00:55:15.382
<v Gabrielle Mérite>I know my way around, which I think most people do, and the idea of we've standardized

00:55:15.382 --> 00:55:17.986
<v Gabrielle Mérite>web design, for instance, is pretty standardized.

00:55:17.986 --> 00:55:20.969
<v Gabrielle Mérite>I think there's a question of like, it's standard that's for who?

00:55:22.750 --> 00:55:27.991
<v Gabrielle Mérite>Because we're in this conversation, right? We're standards, you're centric and then Americans.

00:55:28.391 --> 00:55:33.193
<v Gabrielle Mérite>And I think we need to ask this question of like, when we do that,

00:55:33.193 --> 00:55:38.195
<v Gabrielle Mérite>when we automatize things, when we do this thing of standardizing,

00:55:38.195 --> 00:55:40.596
<v Gabrielle Mérite>do we take into account enough people?

00:55:42.517 --> 00:55:45.698
<v Gabrielle Mérite>I think we all have this thing of like, this is how design is done.

00:55:46.798 --> 00:55:49.939
<v Gabrielle Mérite>Modernism, it needs to be clean and minimal and sensitive.

00:55:50.439 --> 00:55:51.200
<v Moritz Stefaner>Like, why?

00:55:51.200 --> 00:55:55.581
<v Gabrielle Mérite>You know, when you look at design from East Asia, like, it might look very different.

00:55:55.581 --> 00:55:58.462
<v Gabrielle Mérite>And to the eyes of American designers like me, I mean, like,

00:55:58.462 --> 00:56:01.563
<v Gabrielle Mérite>it's messy. It doesn't respect text hierarchy. It's not albedica.

00:56:02.404 --> 00:56:05.245
<v Gabrielle Mérite>Well, no, albedica doesn't write like in the story, guys.

00:56:06.405 --> 00:56:10.847
<v Gabrielle Mérite>So it's interesting how I wonder, I'm not against it. I actually found it like, to me, automating.

00:56:11.427 --> 00:56:16.149
<v Moritz Stefaner>But you question if it's actually true or if it's just a slice of reality or...

00:56:16.149 --> 00:56:21.351
<v Gabrielle Mérite>Is it for the right thing? When is it used? How is it used? For who is it used?

00:56:21.351 --> 00:56:25.272
<v Gabrielle Mérite>Is I think those questions that, you know, are like, I find challenging.

00:56:25.272 --> 00:56:29.534
<v Gabrielle Mérite>Like, I want to automate my workflow. I want to, I think it's so practical to

00:56:29.534 --> 00:56:30.994
<v Gabrielle Mérite>have those technology, Figma components.

00:56:32.135 --> 00:56:37.036
<v Gabrielle Mérite>Like, it's so great. I just wonder if we automate, we tend to repeat a certain

00:56:37.036 --> 00:56:41.078
<v Gabrielle Mérite>point of view in design that has been put by a certain type of population.

00:56:41.498 --> 00:56:45.339
<v Gabrielle Mérite>And maybe it doesn't apply to everyone, it's not fit for every audience.

00:56:45.339 --> 00:56:50.961
<v Alan Wilson>Yeah, I agree with that. I think that I like that.

00:56:52.342 --> 00:56:57.864
<v Alan Wilson>I think my take on it is that sometimes it's an enabler. We've talked about

00:56:57.864 --> 00:56:58.904
<v Alan Wilson>that a little bit already.

00:57:00.145 --> 00:57:05.206
<v Alan Wilson>By systemizing design, it enables you to design a lot of things at once.

00:57:05.987 --> 00:57:09.648
<v Alan Wilson>And that's really cool. And I think that's really powerful.

00:57:11.389 --> 00:57:15.990
<v Alan Wilson>And typically, the thing that kind of design you're enabling is,

00:57:15.990 --> 00:57:19.891
<v Alan Wilson>to your point, more it's pretty expected and not terribly exciting.

00:57:21.352 --> 00:57:26.734
<v Alan Wilson>But it works and it's usable. But that's not to say you couldn't build a system

00:57:26.734 --> 00:57:30.575
<v Alan Wilson>that is just wild and crazy and super creative.

00:57:32.816 --> 00:57:38.858
<v Alan Wilson>So I think I'm really excited for the next 10 years because I think not only

00:57:38.858 --> 00:57:43.820
<v Alan Wilson>are the tools that we to do this work going to continue to evolve and change,

00:57:43.820 --> 00:57:48.762
<v Alan Wilson>and there's going to be new ones and things, I think the work that comes out

00:57:48.762 --> 00:57:51.223
<v Alan Wilson>of those tools is going to be better too.

00:57:51.223 --> 00:57:57.005
<v Alan Wilson>I think one of the challenges to being creative isn't necessarily the systemization,

00:57:57.005 --> 00:57:58.565
<v Alan Wilson>it's the feedback loop, right?

00:57:59.105 --> 00:58:03.847
<v Alan Wilson>Right now, like I author my system over here, and then I see the results over

00:58:03.847 --> 00:58:09.109
<v Alan Wilson>here, and it's very difficult to kind of connect all those dots.

00:58:09.109 --> 00:58:14.102
<v Alan Wilson>And I think software is going to get better and better providing creative feedback

00:58:14.102 --> 00:58:17.411
<v Alan Wilson>loops for all types of design, not just.

00:58:18.065 --> 00:58:21.686
<v Alan Wilson>The kind of traditional print and web design that we've done up until now,

00:58:21.686 --> 00:58:23.477
<v Alan Wilson>but the more system level design.

00:58:23.477 --> 00:58:28.649
<v Moritz Stefaner>If you think about AI tools, they can generate hundreds of variations of something,

00:58:28.649 --> 00:58:30.970
<v Moritz Stefaner>and then you pick and curate and combine.

00:58:31.830 --> 00:58:34.791
<v Moritz Stefaner>That's a whole new thing. Exactly.

00:58:34.791 --> 00:58:40.003
<v Gabrielle Mérite>I think the idea of curating, I'm obsessed with AI, I think it's going to change

00:58:40.003 --> 00:58:42.534
<v Gabrielle Mérite>how we approach things. I think it's a tool.

00:58:42.874 --> 00:58:46.835
<v Gabrielle Mérite>It's just a tool. So we need to use it as a tool and it's not a finality.

00:58:46.835 --> 00:58:49.656
<v Gabrielle Mérite>It's not just you run it and then you just dump it and that's done.

00:58:49.656 --> 00:58:54.338
<v Gabrielle Mérite>And if we involve human beings in it and we still have a customization of it,

00:58:54.338 --> 00:58:58.840
<v Gabrielle Mérite>you know, and we we curate the result, then then that's the it seems like the

00:58:58.840 --> 00:58:59.880
<v Gabrielle Mérite>right approach to do that.

00:58:59.880 --> 00:59:04.582
<v Moritz Stefaner>Yeah. Yeah. And maybe Lego is a good metaphor in a sense that it's super standardized.

00:59:04.582 --> 00:59:09.343
<v Moritz Stefaner>Like Lego is the most standardized tool you could think of or toy you can think of, right?

00:59:09.343 --> 00:59:14.025
<v Moritz Stefaner>Actually, each block is super boring, but you can build anything out of it.

00:59:14.025 --> 00:59:18.507
<v Moritz Stefaner>It's like endless fun, right? And so maybe, yeah, thinking about more like,

00:59:18.507 --> 00:59:19.987
<v Moritz Stefaner>oh, it's building blocks.

00:59:19.987 --> 00:59:23.548
<v Moritz Stefaner>It's something you can play with and build stuff out of, you know,

00:59:23.548 --> 00:59:29.861
<v Moritz Stefaner>is a better thought than it's a book of laws. You have to abide to it. Yeah.

00:59:29.861 --> 00:59:33.592
<v Gabrielle Mérite>It might also help with gatekeeping in a way. Like, I wonder how much,

00:59:33.592 --> 00:59:37.814
<v Gabrielle Mérite>when I'm seeing AI mid-journey, like how much of now people who are creative

00:59:37.814 --> 00:59:42.735
<v Gabrielle Mérite>but never got the chance to be educated, have the time to learn Photoshop can produce art.

00:59:43.056 --> 00:59:46.257
<v Gabrielle Mérite>There's so much, obviously it's a little further away from a discussion,

00:59:46.257 --> 00:59:49.738
<v Gabrielle Mérite>but automation and all those tools that are going to make our work practical

00:59:49.738 --> 00:59:52.379
<v Gabrielle Mérite>is also going to allow more people to join the community of designers.

00:59:52.759 --> 00:59:57.081
<v Gabrielle Mérite>Like, designers are going to take a bigger, you know, a bigger umbrella,

00:59:57.081 --> 01:00:01.122
<v Gabrielle Mérite>maybe we'll have more people with different opinions and different backgrounds.

01:00:01.623 --> 01:00:05.544
<v Moritz Stefaner>It's a good point. So the more people we bring in, immediately we have more

01:00:05.544 --> 01:00:10.326
<v Moritz Stefaner>diversity because there's more viewpoints represented. Yeah.

01:00:10.326 --> 01:00:13.087
<v Moritz Stefaner>Oh, now I'm thinking about AI plus design systems.

01:00:13.368 --> 01:00:18.050
<v Moritz Stefaner>That's such a combination, right? If you had Infigma, like you have your little...

01:00:18.050 --> 01:00:19.111
<v Gabrielle Mérite>I've seen some.

01:00:19.111 --> 01:00:20.452
<v Moritz Stefaner>Some people are working on some.

01:00:20.452 --> 01:00:21.733
<v Gabrielle Mérite>It's definitely coming. I'm

01:00:21.733 --> 01:00:25.515
<v Gabrielle Mérite>like, I don't have to do the components by hand anymore. It'd be great.

01:00:25.915 --> 01:00:30.438
<v Moritz Stefaner>That would be kind of nice. Just write a little text. Make all the buttons we need.

01:00:30.438 --> 01:00:37.682
<v Moritz Stefaner>And here we go. Yeah. You could also teach, as you said, a design idea or a

01:00:37.682 --> 01:00:43.666
<v Moritz Stefaner>principle or a certain approach and then just see a hundred variations of that.

01:00:43.666 --> 01:00:45.147
<v Moritz Stefaner>I think that's exciting.

01:00:48.278 --> 01:00:54.600
<v Moritz Stefaner>Cool. So I'm glad there's a positive spin to my slight doubt at the end.

01:00:54.600 --> 01:00:59.682
<v Moritz Stefaner>But I think there is an interesting tension there. And it's what I also want to keep exploring.

01:01:00.843 --> 01:01:06.165
<v Moritz Stefaner>Like how can we make work that lasts and is really like professional and solves

01:01:06.165 --> 01:01:08.365
<v Moritz Stefaner>people's problems, but also still

01:01:08.365 --> 01:01:13.347
<v Moritz Stefaner>keep things exciting and inspiring and provoking also sometimes, right?

01:01:13.347 --> 01:01:18.369
<v Moritz Stefaner>So I think that's the the eternal design tension that we all have to deal with.

01:01:18.369 --> 01:01:21.870
<v Moritz Stefaner>Wonderful. I think that was a great conversation.

01:01:22.471 --> 01:01:27.993
<v Moritz Stefaner>I hope we didn't confuse you all with our design system nerd talk.

01:01:29.053 --> 01:01:33.374
<v Moritz Stefaner>We'll put a few links in the show notes to the examples we discussed, a few resources.

01:01:34.015 --> 01:01:39.037
<v Moritz Stefaner>And yeah, maybe we can do a follow-up episode on AI plus design systems now

01:01:39.037 --> 01:01:40.417
<v Moritz Stefaner>that we're all excited about.

01:01:42.538 --> 01:01:47.280
<v Moritz Stefaner>Yeah. In the meantime, thanks for joining me and see you soon.

01:01:47.280 --> 01:01:55.823
<v Moritz Stefaner>Thank you, Moritz. Bye-bye. Hey, folks. Thanks for listening to Data Stories again.

01:01:56.543 --> 01:02:00.865
<v Moritz Stefaner>Before you leave a few last notes, this show is crowdfunded and you can support

01:02:00.865 --> 01:02:06.187
<v Moritz Stefaner>us on Patreon at patreon.com slash data stories, where we publish monthly previews

01:02:06.187 --> 01:02:07.927
<v Moritz Stefaner>of upcoming episodes for our supporters.

01:02:08.808 --> 01:02:14.930
<v Moritz Stefaner>Or you can also send us a one-time donation via PayPal at paypal.me slash data stories.

01:02:15.470 --> 01:02:19.812
<v Enrico Bertini>Or as a free way to support the show, if you can spend a couple of minutes rating

01:02:19.812 --> 01:02:22.273
<v Enrico Bertini>us on iTunes that would be very helpful as well.

01:02:23.113 --> 01:02:26.574
<v Enrico Bertini>And here's some information on the many ways you can get news directly from

01:02:26.574 --> 01:02:31.956
<v Enrico Bertini>us. We are on Twitter, Facebook and Instagram, so follow us there for the latest updates.

01:02:32.316 --> 01:02:36.298
<v Enrico Bertini>We have also a Slack channel where you can chat with us directly.

01:02:36.498 --> 01:02:42.499
<v Enrico Bertini>And to sign up, go to our own page at datastory.es and there you'll find a button

01:02:42.499 --> 01:02:43.680
<v Enrico Bertini>at the bottom of the page.

01:02:43.680 --> 01:02:47.660
<v Moritz Stefaner>And there you can also subscribe to our email newsletter if you want to get

01:02:47.660 --> 01:02:51.801
<v Moritz Stefaner>news directly into your inbox and be notified whenever we publish a new episode.

01:02:51.801 --> 01:02:54.762
<v Enrico Bertini>That's right! And we love to get in touch with our listeners,

01:02:54.762 --> 01:02:58.883
<v Enrico Bertini>so let us know if you want to suggest a way to improve the show or know any

01:02:58.883 --> 01:03:04.384
<v Enrico Bertini>amazing people you want us to invite or even have any project you want us to talk about.

01:03:04.744 --> 01:03:10.986
<v Moritz Stefaner>Yeah, absolutely. hesitate to get in touch, just send us an email at mail at data story dot es.
