Tableau UI Kit: Streamline Dashboard Creation with this tool | with Robert Janezic

0:00Hey it's Tim here. In today's video we're

0:01doing a very different kind of video. We're

0:03going to be

0:04looking at something called the Tableau UI

0:06Kit. This is a prototyping tool for helping

0:09you plan

0:10your Tableau dashboards and I'm going to

0:11let Robert explain the whole capability of

0:13this tool

0:14himself, but I think it's an important

0:15aspect of Tableau dashboarding that just

0:17doesn't get much

0:18coverage and I also think a lot of people

0:20are sleeping on this tool. Now Robert hasn

0:22't sponsored

0:23me for this video, this is just a straight

0:25discussion with me and him talking about

0:27the

0:27benefits of prototyping but also the way

0:29the UI Kit works and how you can actually

0:32use it for

0:32more than just Tableau. As ever I hope you

0:34enjoy this video and let's get stuck in.

0:36Yeah we can get started right away and just

0:40introduce yourself.

0:42Yeah so my name is Robert Janizek, I'm a

0:46product designer working in the Tableau

0:50Center of Excellence at JPMorgan Chase. So

0:54that basically means that I design websites

0:58and

0:59applications for our 150,000 plus user

1:05Tableau base and so at that scale we need

1:09to start

1:10creating applications and things that help

1:14our user base, so it's my responsibility

1:19to design those websites and applications.

1:23So that's generally what my

1:26responsibilities are.

1:27What about the product? Tableau UI Kit.

1:32The product yeah Tableau UI Kit. So the

1:35Tableau UI Kit is, how familiar are you

1:40with UI kits in

1:42general before the Tableau UI Kit? So I'm

1:45fairly familiar with them, I've used, I've

1:48done a bit

1:48of web design way back when I used to use

1:51UI kits when I looked at things like Boot

1:53strap which

1:54Twitter developed to help people build

1:57websites. I've also used them to look at

1:59interface design,

2:01so that's sort of my background but for the

2:03benefit of everyone who's probably watching

2:05and has never had to do that maybe just

2:06explain a bit about what they are.

2:08Yeah so I would say most of the people in

2:11the analytics world,

2:15I'm not saying that the Tableau UI Kit was

2:17their first introduction but it could have

2:19been,

2:19I'd say it's probably a good likelihood

2:22that it was for them and their team. So

2:25UI kits are a set of components and styles

2:31that help designers build websites and

2:37applications

2:38faster. So for example if you went to like

2:42Gumroad or something or one of those

2:46websites or you just

2:46went to the Figma community and you looked

2:48up UI kit, there would be, you would see

2:50hundreds

2:51or maybe even thousands of different UI

2:56kits. So it's basically a way to build

3:00things faster

3:02and the thing is people have different

3:04opinions about the way certain components

3:06and styles should

3:07look. So some of them are really opinion

3:10ated, right? So that means that they have a

3:14very

3:14specific style that they're going for in

3:16the UI kit if you want to build a website

3:18in that general

3:19style. And then some of them aren't opinion

3:22ated where they're just like super super

3:25base like

3:27component where it's just a button but we

3:29're not getting too crazy on the button it's

3:31just like

3:32the most base version of it and it's kind

3:35of up to you to change the style. So there

3:37's a lot of

3:38different kits and so the Tableau UI kit is

3:41, you know, it's all of those things I

3:43mentioned but

3:44it's for Tableau specifically. So it helps

3:47you prototype and design Tableau dashboards

3:51before

3:51you actually start creating, developing the

3:56Tableau dashboard inside of Tableau.

3:59Amazing, amazing. Might it be a good idea

4:01to just show people then we can get into

4:04the semantics of

4:04how you got there, how you came up with the

4:06product, the stuff that people really want

4:08now but it probably helps to show people.

4:11Yeah, so when you first open the UI kit you

4:16're just

4:16going to see a bunch of, you know,

4:19instructions and things to get you started,

4:22you know, what is

4:23this, what vendor am I using to purchase. I

4:27'm using Lemon Squeezy. I just recently

4:30switched from

4:30Dumbroad for some fee reasons and then we

4:34have like general info, styles, components

4:38and all

4:39these things and I'm not going to, you know

4:41, talk about all these in depth but, you

4:43know, anyone can

4:44come in here and they can. It's really well

4:46documented. Yeah, I wanted to make sure

4:49that

4:49everything is well documented and it's easy

4:51to understand and things like that.

4:54Compared to most

4:54Figma UI kits this is top tier

4:56documentation. Yeah, I wanted to really

4:58make sure everything

4:59was good. And then we jump into examples

5:02and for version 2.0, you know, my last

5:06version I did have

5:07examples but I didn't, I don't think I

5:10spent enough time on them and I really

5:12wanted to make

5:13sure that the examples that were here

5:18really showed what you could do with the

5:21kit. And it's

5:24not like I'm saying, you know, if you have

5:28the UI kit you'll be able to design a

5:31dashboard like this

5:33in 30 seconds. It does take design

5:37knowledge to understand how to create

5:41something like this but

5:42a lot of the components that I've built

5:45into the UI kit help you, kind of help you

5:47get further along.

5:49Like for example, if you're not familiar

5:50with application design and you're just

5:53kind of

5:54familiar with the way you kind of see in

5:56the Tableau community, you might not really

5:58know what,

5:59you know, the best practices of navigation

6:03are or like how most application, you know,

6:07designers

6:08would usually do a sidebar or how would

6:10they do a top nav bar. And so I spent a lot

6:13of time really

6:14focusing on making sure that the dashboard

6:16components that you could have like, you

6:19know,

6:19just a sidebar or something like this is

6:21very similar to what you would see if you

6:24decided to

6:26sign up for some sort of application and

6:27you would see something similar to this,

6:29right? It's using

6:30all the same contrast, all the spacings

6:33correct and things like that. So it is

6:36opinionated in

6:37that way. Yeah, I did provide an opinion

6:41about what I think good application design

6:45is and

6:46although this is for Tableau, it's kind of

6:48the same although it's a little bit harder

6:50to make,

6:51do it in Tableau. You kind of have to do

6:55stuff but I wanted to make sure that

7:00everything was,

7:01you know, well designed essentially. Yeah,

7:04there's some parameters that you've kind of

7:07set in but

7:08also, just going back to a couple of the

7:10things you said, that first point you made

7:13about thinking

7:14about an application, it's actually a

7:15really pertinent point because a lot of the

7:17time

7:17people are asked to make dashboards that

7:19should be applications, that should have

7:21that level of sort

7:22of consideration and thought because we

7:24always hear about, you know, analytics

7:26leaders calling

7:27their analytics solutions products, right?

7:29Yeah. If those things are products, they

7:31should be treated

7:32as such and actually an application sort of

7:34mindset gives you a better framework to

7:37making

7:37sure you build things in like a in a

7:39standard way across a whole team. But also

7:42this sort of

7:43second point you touched on which is guide

7:45rails, not sort of limiting you to just

7:47Tableau because

7:48in the real world you might also be embed

7:50ding let's say Tableau inside of another

7:52platform,

7:52in which case some of what you're showing

7:55is actually possible if you take sort of

7:57the Tableau

7:58Chrome out of the way and you put your own

8:00sort of finish to it. So I think this is

8:03very applicable

8:03and it also makes people think about

8:05actually should we do this somewhere else

8:07or could we

8:08prototype it in Tableau and then build it

8:10elsewhere? That's sort of all part of the

8:12conversation and this tool kind of brings

8:14you into that world with Tableau at its

8:17heart if that makes

8:18sense, right? Yeah, I like exactly what you

8:20just said. It brings you into that world,

8:21right? Where

8:22certain most Tableau developers aren't

8:26familiar with designing an application. So

8:31for example, if

8:33you know a Tableau developer was tasked

8:36with, "Hey, we need to create this

8:38financial application

8:42and I need you to be the user interface

8:45designer and I need you to create this

8:49application design

8:50from scratch. Would you know how to do it?"

8:53And I would say for most Tableau developers

8:56the answer

8:57is no because in general historically Table

8:59au design is definitely different from

9:02application

9:03design. So for example, if you went to the

9:04Figma community right now and you looked up

9:06dashboard,

9:07you're not going to see Tableau dashboards.

9:09You're going to see like application dash

9:12boards and

9:13they're designed a lot differently. And I

9:15think there's a few reasons for that. One,

9:19you can literally do anything in code. So

9:21the things that you're designing they can

9:24actually

9:24build. And two is there's just not as much

9:29design experience in the Tableau community.

9:33But that makes sense, right? They're not

9:36designers, right? They're analysts.

9:42I'm not expecting someone that spends 95%

9:47of their day in Tableau and in doing SQL

9:52and doing

9:52data analytics stuff to be like top tier

9:55designers. Like I'm not expecting them to

9:58post. It's

9:59unrealistic, right? So for someone that is

10:02in Figma at 95% of my day and that's whose

10:06job it is

10:07to do those things. I feel like I can help

10:11people get a really good base with a lot of

10:15those things

10:16by creating these opinionated components

10:18essentially. And it's not like I have all

10:23of these dashboards built in Tableau. It's

10:26kind of up to the person to take these and

10:29be like,

10:29"Hey, I don't know how to..." Oh, for

10:32example, like this small thing right here.

10:35I don't

10:35necessarily know how to do this rounded

10:37corner thing in Tableau. Let me just

10:40implement it how

10:41I would implement it in Tableau. But I do

10:45feel like it's kind of my responsibility to

10:48give the best version of what it could be.

10:51And then you decide whether or not you want

10:54to spend

10:54the time implementing it inside of Tableau.

11:00In a way, you've sort of harnessed the UI

11:04application

11:05expertise and turned it into an aspiration

11:07for people who build dashboards. Because I

11:09always

11:10think that I might get cancelled for saying

11:12this, but I always think Tableau dashboard

11:15design

11:15tends to track about four years behind

11:18actual design trends. And that's not

11:21because of the

11:23users. It's because Tableau itself hasn't

11:25done enough work to bring through modern

11:27design trends

11:28in other design capabilities into the

11:31product. And so we're limited mostly

11:33actually by the tool.

11:35Yeah. And there's a lot of things, there's

11:38a lot of features that Tableau could

11:40add that could really help people not only

11:43design faster, but also be able to design

11:48at a higher

11:49level. So if Tableau, I know this has been

11:51a feature request for everywhere, you can

11:55set all

11:56of your defaults upfront. Templates. That'd

12:00be great. You could create something in

12:04Tableau.

12:04Let's say you have a really cool KPI and

12:07then use the same functionality that Figma

12:10does,

12:10which is componentizing. You componentize

12:13that KPI and then you can easily just drag

12:15that in next

12:15time and populate it quickly. These are all

12:18things that would really help people. I can

12:22't imagine

12:23those would be implemented anytime soon,

12:27but if I can help in any way, that's kind

12:31of...

12:31Yeah, exactly. On that last point, I

12:34thought metrics were exactly that. When I

12:36saw metrics,

12:37I was like, "Yes, let me put this in a

12:39dashboard." And it's never happened. It's

12:41so frustrating.

12:43But absolutely, if we go back to UIKit, I

12:45think the opinions you've built into this

12:51are actually quite well-grounded, but also

12:53might expose people to... It's like a

12:57shortcut to a form

12:58of structure that people haven't really

13:00thought through. If you zoom out and you

13:01look at

13:02everything you've done, there's quite

13:04clearly a style guide. There's quite

13:05clearly a format.

13:06And everything looks like it's come out of

13:09the same house or organization. There is

13:12also a

13:12consistent use of things like font and

13:16color. And the red amber indicators are all

13:19well applied.

13:21You're flipping through these as I speak.

13:23So you've done a lot of work actually to

13:25really apply the thought. So what I was

13:29going to suggest next is just show us what

13:32it can do.

13:32Show us how someone would use this. Yes, I

13:35think it'd be good if... So I'll just do a

13:38new page.

13:40Actually, this is the actual version that

13:43people see. So I probably don't want to do

13:45it.

13:45Probably don't want to do it. Probably don

13:46't want to do it in here.

13:47They do it on the production version. I've

13:52done that before.

13:55Yeah, because they would actually be able

13:57to see that. Like if they were in it on the

13:59...

13:59If they went from the website, then they

14:01could actually see it. So the concept of a

14:06UIKit and

14:07what Figma is so cool is that you create a

14:10kit, you create your components, you have

14:14your styles

14:15that you want to use, you publish that

14:18library, you publish the library. And then

14:21anyone that has

14:22access to that library can open any new Fig

14:26ma file, be able to enable the library, and

14:30then

14:30pull in the components they want. So for

14:33example, if I went to assets here and I

14:36looked up the

14:38different kits that I have here, I have

14:41Tableau UIKit 2.0. Enable that and then you

14:45can see on

14:46the left here all of the different

14:47components that you have access to

14:50instantly. And so all of this

14:51is coming directly from the UIKit that I

14:55was just in. So any changes that you would

14:59make in your

15:02version of the UIKit, you would make the

15:03change, publish the change up, and then

15:05when you come back

15:06into this file that's using the same exact

15:08library, it would say, "Do you want to

15:10refresh?" etc.

15:11So just for everyone's clarity, that first

15:15page we saw, that's like the template, that

15:18's like the

15:18starting point. And from that, these

15:20components on the left are sort of

15:22generated, which means if

15:24you're in an organization, you could rest

15:26yle that top layer as a UX designer, as a

15:28marketing person,

15:29whatever. And then when people come to sort

15:31of prototype their dashboards here, those

15:34things are

15:35sort of updating across the whole

15:36organization. Yeah, exactly. And usually

15:40for large

15:41organizations, it's really important

15:43because there's actually design system

15:46teams where

15:46their entire job is. Yeah, right. And I'm

15:49not going to even get into the difference

15:50between UIKits and

15:51design systems. Just know that there's

15:53design system teams, that their job is to

15:56create the

15:56components, do the documentation, push the

15:59updates, notify people when the updates

16:01have been made,

16:02etc., etc. So I can start creating a

16:04dashboard here. And now in previous

16:06versions of the kit,

16:08I had a dashboard component that would

16:11actually let you drag an entire dashboard

16:15in,

16:16and then you could change some of the

16:17settings. I decided to get rid of that

16:20for this version 2.0 because I thought it

16:23was too limiting in people's idea of what

16:27you could do

16:27with the kit, right? So they would only

16:29think that they could use the dashboard

16:31component,

16:31and they couldn't customize it anymore. So

16:34I really went back to the roots of what a

16:36UIKit is.

16:37It's separate parts of a page that you can

16:40combine together to create something. So

16:45for this example,

16:45let's say I want to create an application

16:48style Tableau dashboard. The first thing

16:51that I would

16:51probably want is I need to figure out

16:53navigation, right? So generally when I see

16:56Tableau dashboards

16:57and navigation, it's generally not done

17:00correctly. And that's my opinion, right? I

17:04often see

17:05navigation combined with filtering, also

17:10combined with supplemental links to

17:14different resources. So

17:15you'll see four links that are evenly

17:18distributed, and one of them's a filter,

17:21the other one's a

17:22different navigation to a different page,

17:25and then one's a help. And that's generally

17:28not

17:29what you want to do because there's not

17:31enough proximity between the three things.

17:33There's no

17:34distinction between the two actions that a

17:36person can take. So generally what you'll

17:39see in an

17:39application is something like this. So I

17:43actually probably want to do a sidebar

17:45navigation. So I'll

17:47do sidebar. It automatically pulls the

17:49sidebar navigation in. And you can see on

17:52the right-hand

17:53side here, with the new Figma features, it

17:57's made this super easy. Now, the reason

18:02this version took

18:03me so long is because I created a bunch of

18:06new components using the new features, but

18:09I also

18:10completely revamped all of the old

18:12components to use the new features.

18:15That takes time.

18:18Yeah, it takes a lot of time. So I started

18:20to add new things like component props,

18:25like using the

18:26Boolean, using the content, and using

18:29nested instances. And I'll walk you through

18:33what those

18:34things mean. And so basically in terms of a

18:37UI kit organization, it significantly cuts

18:41down on the

18:42amount of components. I think maybe some of

18:44the people that were familiar with version

18:471.5, they

18:49probably saw that one component could have

18:5120, 30, 40, 50, 60. I think one of them had

18:55over 100

18:56different instances. And the reason there

19:00was 120 plus different component variants

19:04is because if

19:07you wanted to hide one thing in component,

19:09you would have to create an entire new

19:10component.

19:11But that's completely changed in the new

19:13version where you can actually just do a

19:15Boolean hide,

19:17essentially, and you only have to do one

19:19component. So I'll show you what's going

19:21here.

19:21Do I want this? What type? Do I want it to

19:25be horizontal? This is horizontal. That's

19:28vertical,

19:28which is icon and that's stacked together.

19:31And then there's icon only. So often we see

19:35in the

19:35UI kit or in the Tableau world, I see a lot

19:37of people doing this, which is icon only,

19:41which is

19:41great. Now, one potential downside is if

19:45you're doing that Tableau wise, you need

19:49some sort of way

19:50for you would have to do some sort of tool

19:52tip. So the person understands what this is

19:55. Because when

19:56you're doing an application design, you can

19:59either do, there's usually like a arrow

20:02here and you can

20:03pop the sidebar out left and right, or

20:06there's some sort of hover action tool tip

20:09that says

20:10what it is. I always like this, just so you

20:13always know exactly what's going on. There

20:16's no question

20:17about what is this. And then you can say,

20:20do you want a logo? Yes or no? Sure. How

20:23many links do

20:24you want? I only want three links. Do I

20:26want trailing links? And now this is what I

20:29'm talking

20:29about, the distinction between links, right

20:31? The different things. So the top three

20:34would be for

20:35your navigation to different dashboards,

20:37right? And so that makes sense. They're all

20:39linked together,

20:40there's good proximity. So the second would

20:44be like, do you have resources or support?

20:50Yeah. Some sort of supplemental link that

20:53doesn't necessarily have any navigation to

20:57different

20:57dashboards. And that's an important

20:58distinction between those two things. I don

21:01't want trailing

21:02links. And I've also been seeing a lot of

21:05people doing things like this. Footers. Who

21:10's logged in,

21:12things like that. There has been a trend on

21:14Tablight Public, I noticed that actually.

21:18Yeah. I'd say mostly they probably saw it

21:22on Dribbble and all of them have,

21:26they all have avatar, which makes sense,

21:29right? Usually you'll have some sort of

21:31avatar somewhere,

21:32whether it's in the top nav bar or on the

21:34sidebar. It's somewhere. And I think it's

21:36important. I

21:37think it's cool. We just want to make sure

21:39that we're putting it in the right location

21:41and it's

21:42designed well, essentially. Yeah, exactly.

21:45So let's start designing this. Now,

21:47previously in other versions, you had to

21:49click down and get down

21:51and go all the way into it and be like, "

21:52Hey, all right, I don't want to change this

21:54." Now,

21:55with this new version, you don't have to do

21:57that. You can still do this where you just

21:59click on the

21:59actual design or you can just use all the

22:01features on the right. So for this example,

22:04let's say I

22:06want sales. That's great. And I want it to

22:10be selected. I want it to be active and I

22:14don't want

22:14this one to be active. I see. I see.

22:17And then claims and then users or something

22:22like that.

22:24That's simple.

22:25These icons don't really make sense. So

22:27there's a really cool new feature in Figma

22:29called

22:29InstanceSwap. And it's basically a way to

22:33change... What's the best way to explain it

22:40?

22:40It's usually used for icons. It's used for

22:43icons a lot. So the UI kit comes with, I

22:47think it's

22:47250 plus different icons. Each of the icons

22:50is a different component. And because of

22:52that,

22:53you can create an InstanceSwap, which means

22:55I can just say, "Hey, maybe I want...

22:58There's probably a dollar." Yeah. So you

23:03just do that and it just swaps it out.

23:05Nice. Nice.

23:07And so you can just go through and just

23:13change them to whatever you want. And it's

23:15super quick.

23:16And you don't have to go to this place and

23:18then copy it and then go and bring it in

23:21here and paste

23:22it and then do all that stuff. That's

23:24usually what you would do. You would go

23:28find the SVG somewhere,

23:31copy it, bring it over here, put it into

23:33the auto layout, and then it's a whole

23:35other thing.

23:37And so you can change what your avatar

23:40looks like. So initials, icon, image. I'll

23:45keep it.

23:46Icon. What do I want the size to be? And I

23:49could change this to Tim. And then Tim

23:53email or something like that. And you can

23:54change it to whatever you want.

23:56So from here, great. That's one part of our

23:59dashboard. And that's how I think about

24:02dashboards. Whenever I see someone post

24:05something on Tableau, I think, "All right,

24:08what are the

24:09distinct sections of this?" In general,

24:12every dashboard is only a few things. You

24:17have

24:17some sort of navigation, something,

24:20navigation. You have some sort of header.

24:24That's your title

24:25and the things you have in the top section.

24:27Maybe you have an info thing. And then you

24:29have your

24:29content. Content is your charts, your KPIs.

24:33That's your content. So there's really

24:37three main

24:38sections of every single dashboard. And so

24:41from here, I would want to put some sort of

24:44header.

24:45So I can go here. Header. And these are

24:51documentation headers. Where is my header?

24:55Oh, heading. That's right. Oops. Heading.

25:02And so I'm not going to design everything

25:06right now,

25:06but I'm going to do the menu right here. So

25:09it looks pretty crazy. And so what I tried

25:12to do here

25:12is I looked through every single reference

25:16I could of every single possible thing that

25:19I've seen

25:20anyone put inside of a header. And I added

25:23it all to this. And you have the ability to

25:26take out or

25:27put... Basically take out the one you don't

25:29want. So for this instance, we could do

25:32breadcrumbs.

25:33I'll keep that. I don't really want a logo.

25:35This could be profit dashboard. And it'll

25:42be created.

25:42Or maybe last refreshed today or something.

25:47I don't know. I don't want metadata. Do I

25:52want

25:52buttons? Sure. I'll keep a button secondary

25:56. And button groups are really good.

26:02Button groups are really good. If, for

26:04example, you wanted to... You know what? I

26:09'll keep the

26:10button group. And then do I want an

26:12information icon? No. I don't want an

26:15avatar because I already

26:16have an avatar. And then I don't want a

26:18slider. Great. Nice. So what I would do

26:22from here is

26:22start actually designing this entire square

26:25section. So I would take a frame. And I

26:28would

26:28just call this main. This is my main area.

26:34Put it right here. And then I don't do

26:40anything unless

26:40it's auto layout. So I would instantly take

26:43these two things and add them to auto

26:45layout using Shift A.

26:48That's for everyone's benefit. Auto layout

26:54is a capability in Figma that allows you to

26:57...

26:57Now correct me if I'm wrong here. But it

26:59allows you to group assets together. But

27:00then as you shift them,

27:02it keeps the relative positioning and

27:05proportionality reasonably good.

27:08Yeah. And that's the simplest way. And a

27:10super quick example. I have two things here

27:14.

27:14And you can't really do this in PowerPoint.

27:17I want these two things, no matter how big

27:20I make...

27:22So I'll do two of these things. I'll put it

27:25in auto layout. And now I know that there's

27:2795 pixels

27:28between these two things. I want to change

27:30it to 24. So now I know there's 24 pixels

27:33between these

27:34two things inside of this frame. And if I

27:35make it bigger, nothing happens. But the

27:38cool thing with

27:38auto layout is you can change the

27:40constraints. So I can say, "Hey, I want

27:42these two things

27:43inside of this frame to fill container and

27:46fill container." So if I make the

27:48overarching...

27:50And it automatically scales with it. It

27:52stays 24 pixels, etc, etc. So I'll go back

27:56to it.

27:57I only discovered this two months ago. It

28:00just blew my mind. I was like, "What is

28:03going on?"

28:03Yeah. For me, it was natural because I was

28:08already using flex a lot, which is

28:11something...

28:11Right. Right. So you're looking for it.

28:13Coding where it's the same equivalent. Auto

28:17layout in Figma is just flex in coding. So

28:21you could say,

28:21"Do I want it to be flex row or flex column

28:25? What do I want the gap to be?" Which is

28:28what you would

28:29do in code, essentially. So I'm going to

28:32take this header and put it into here. And

28:36I'll make that

28:37auto layout as well. And how many pixels do

28:40I want on the left and right? I'll do 32.

28:43And I would only

28:44want... Sure, I'll do 32. And I'll say fill

28:49container. So I have my first thing, and

28:52now I

28:53need to start doing content. So I need to

28:55... Well, maybe we can change some of these

28:58things.

28:59So a cool thing about the new features with

29:02Figma is something called nested instances.

29:06So this is a component. It's a heading

29:08component. But within that heading

29:12component, there's a lot

29:13of other components. And previously in Fig

29:16ma, you couldn't say, "Hey, show me all of

29:18the

29:19nested components that are in this, and

29:23show me all the things that they can do,"

29:26essentially.

29:27So what you'll notice is if I click on the

29:30heading, it's not just the heading

29:32options that you have, you also have bread

29:35crumb as well. So you could do things like

29:37...

29:37You can change the actual things inside the

29:40component. That's a really important thing

29:44to know.

29:45And so, okay, let's start adding some dash

29:48boards. So what I would go to here is... It

29:53's called layout.

29:57Just drag layout, and it looks like nothing

30:00. Doesn't look like anything. You'd be like,

30:03"All right, what do I do with this?" So the

30:05new Figma features make this super easy. So

30:09you would choose whichever... Let's say I

30:13want two rows or three rows, for example,

30:17and then you would see what's happening

30:19here. So you have three different things to

30:21replace.

30:22And this is using the new feature. And so

30:25there's also something called preferred

30:27instances. So

30:28I would say for these things, I want to

30:31swap the top one with bar chart, the second

30:39one with

30:40a gantt chart, and the third one with a

30:46tree map, let's say, for example. And you

30:49instantly get those

30:50things in the exact place that you were

30:53supposed to put it, essentially. And so

30:57what you could do

30:58from here is you could put it in here, and

31:00you would fill container, fill container.

31:02And so if

31:04I did this, something is probably going to

31:06break. Yep, you'll notice that it breaks,

31:08right?

31:09- It keeps the height. - But what you want

31:10to do is you want to do fill container.

31:12You want this to be fill container, and

31:15then fill container. And it's good to...

31:19If you don't know something is going to be

31:21responsive, you can just make it bigger and

31:23see what breaks. - What happens, yeah.

31:26- So it's important to get it responsive so

31:28that if you get some feedback and you need

31:32it to make

31:32it larger, for example, you don't have to

31:35do any manual work, right? It's

31:37automatically done for

31:38you. - It's still true.

31:39- Yeah, it's already done for you. So that

31:43's one way of doing it. What you could do is

31:47something

31:47like this, which I think more people should

31:51probably do it this way if they want to get

31:54really custom with their charts that they

31:55're having here. Obviously, you could just

31:57keep it

31:58like this. And if you're like, "All right,

31:59well, I just want to know what charts are

32:00in which section,"

32:01that's fine. But if you want to see what it

32:03actually would look like, I could do maybe

32:07like,

32:07oops, or a chart, drag it in. I want it to

32:13be vertical. I want... Do I want any of

32:21this stuff?

32:22No. Y-axis, I want five. And I want this to

32:29be large. And then I could just go through

32:34and

32:35change it to whatever I want. I could

32:37change it to darker or something.

32:42Something or other I could do. - I could

32:44put comp palettes in there as well.

32:45- I'll do... Actually, I'll do largest.

32:47Oops. Get back to primary five. Primary

32:53five. And I'll

32:54make these dark. Sure, maybe that's as

32:58custom as you want to do it. And now what

33:02you could do is

33:05detach this. Let's say... I think teams

33:07have certain scenarios that they want to...

33:11Let's say they want to put it into here,

33:13but this isn't a component. They could

33:16detach it, make it into another component.

33:18And this could be like

33:19par chart for me. And I could try to call

33:23it and make it a component. And then when I

33:27go into

33:29my content and I go to chart swap one, I

33:33could look for par chart for me. Where is

33:38that?

33:40Oh, these are the preferred. Par chart.

33:49There we go. And it automatically puts it

33:52in.

33:52- Wow. Absolutely. Yeah.

33:53- So it's a slightly easier way if you want

33:56to focus on each chart at a time and you

33:58don't want to have to keep clicking in and

34:00getting to the actual stuff. I recommend

34:05potentially

34:05just building your chart at a time and

34:08figuring out what layer you want. Make it

34:12however custom

34:13as you want, and then you can just swap it

34:15in that way. And there's a lot of different

34:17ways

34:17you can do it. It's whatever is easiest for

34:19you, honestly. So that's a simple example.

34:24- It's a great example. And I think the one

34:29... Whenever I've talked about UI kits

34:32generally,

34:32let's say in an audience that isn't

34:35familiar with UI kits, they'll see this

34:37process. And the first

34:38thing they'll do is they'll say, "Oh, but I

34:40could do all of this much quicker in Table

34:42au just using

34:42Superstore." And I always say, I think you

34:45're kind of missing the point. To me, the

34:48point here is

34:50that you're almost designing the product

34:54without having to sit in front of the

34:57product. And what

34:58this allows you to do is to also then put

35:00it in front of maybe potentially an end

35:03user and have

35:04them sort of interact with it, maybe even

35:06play with it as if it's the real thing. I

35:08know that

35:08we haven't exactly looked at it here, but

35:10it is possible in Figma to add things like

35:12interactions.

35:13And when you click on something, you go to

35:15something else. And those interactions

35:19are typically hard to sort of socialize

35:21until you've built the actual dashboard.

35:23And this

35:24is a much lower cost way of doing that

35:26before you actually go and get your data

35:28team to see

35:29if that interaction is possible in the

35:31first place. You can kind of test that

35:32interaction,

35:33see if it works. If it is possible, then

35:35you go and build a data pipeline to enable

35:37that interaction,

35:38which is often it happens the other way

35:40around. - Yeah. And I think for me, it's

35:42feedback and

35:44change at the design level is much less

35:47costly than it is at the engineering level.

35:50And so I do

35:52hear people say, "Why am I doing it in Fig

35:54ma? Why don't I just do it in Tableau?" And

35:58I won't

35:58disagree with the fact that for some people

36:01, and when I say some people, I mean like

36:04the top

36:071% to half 1% of people are that skilled.

36:10And that's good in Tableau, like

36:13technically on how

36:15to do like all the Tableau stuff, but also

36:18so good at design that they can also do all

36:22that at the

36:23same time on Tableau. I'm not saying there

36:25's not unicorns out there because I've seen

36:27people in...

36:28- But they are unicorns. - They are unic

36:30orns. Most people...

36:31- Yeah, not every organization can afford

36:33that either.

36:33- Most people aren't good enough at Tableau

36:35or they don't have the design skills to do

36:39that all

36:40in Tableau. And doing it as a prototype, it

36:43's really great for feedback. You would do

36:46this,

36:47you would show it to your stakeholders, you

36:49would get feedback, you would quickly

36:51change things,

36:51and you would get sign off. You say, "Hey,

36:54this is the design. Either you do it

36:57yourself,

36:57now you go in Tableau and you actually

37:00build that dashboard, or you have a

37:02different developer if

37:03it's a really big organization." They might

37:05have designers and then developers. That's

37:07usually how

37:08it goes for web. If you're building an

37:11application, you almost no companies unless

37:14it's a startup,

37:15have people that do both. Most people are

37:18either designers or they're engineers.

37:21And I think a disadvantage that a lot of

37:24Tableau developers have is they almost have

37:29to be

37:30everything. They have to be designers, they

37:33have to know how to deal with data, they

37:37have to know

37:37how to use Tableau. Most companies aren't

37:40set up where you have the distinction

37:42between designers

37:44and engineers. So I think this kit, the kit

37:47that I built, really tries to help the

37:50people

37:50that might be a little struggle with design

37:54, because I think a lot of people do

37:57struggle

37:59with design. And I mean struggle has in

38:01terms of getting it really good. It's hard.

38:08- Yeah, that's fair.

38:09- It takes a lot of practice to get

38:12something designed really well.

38:15- Yeah, yeah. I think a lot of the

38:18challenge with design is that you see two

38:21approaches. One where

38:24people perceive it as adding more, adding

38:26more flair, almost like an exhibition, if

38:29that makes

38:29sense, which is kind of not typically how

38:32actually design is framed. Design is

38:34usually framed around

38:35function. So like, how can I help the user

38:38do whatever they're trying to do better?

38:40And that

38:41leads to aesthetic design, but also

38:43functional design paired with that. And

38:46that is very hard to

38:47do unless you sort of have experience at it

38:49. And actually, when you focus on that, you

38:52tend to find

38:53that leads to reductionism, actually. It's

38:55like, what doesn't need to be here? Let's

38:58remove that

38:58and just keep it simple. - Yeah, and I

39:01think a lot of,

39:02another issue that I find with the Tableau

39:05community is you don't know what you don't

39:09know.

39:10And in terms of like, you don't know what

39:13good design is until you get good design.

39:15- Until you go outside of the community to

39:18see that.

39:19- And so there are examples in the Tableau

39:21community, like, you know, like Ludovic,

39:24like is amazing. And I talk with him

39:27frequently and he's a really great designer

39:29. I think he's

39:30definitely like one of the best in the

39:32community for sure. But also Ludovic is a

39:36unicorn, right?

39:38There's not a lot of Ludovics out there. So

39:42I think people kind of need to understand

39:45that

39:46not everything can be like top notch. I

39:48would just say, try your best and try to

39:51improve

39:51on your designs one thing at a time. And

39:55the good thing is by creating a prototype,

39:58you can get feedback really quickly. And

40:00you're not worried about the hacks that you

40:02have to do.

40:02If you think you're struggling with design,

40:05prototyping is something that could really,

40:08really help you with your skills. 'Cause it

40:11's in a tool that is made for designers.

40:15- For design. - And so it reduces friction.

40:18So Tableau,

40:19for example, it's pretty clunky design-wise

40:23doing a lot of these things, but for Figma,

40:26it's like, it's butter. And so if you can

40:29reduce the friction at all for improving

40:33your design

40:34skills, I think that's a major plus. And it

40:38's not like I'm saying if you use the UI kit

40:41,

40:42you're just gonna build these, the nicest

40:44dashboards of all time, but over time you

40:47can

40:47understand, all right, how did Robert build

40:50these components? Why did he put this thing

40:53there?

40:53Is there a specific reason? Et cetera, et c

40:58etera. And so if you ever need some

41:02inspiration,

41:04just go to the examples and be like, all

41:06right, why did he do this? Et cetera, et c

41:08etera.

41:09- It's pretty good. So I guess probably

41:13leads me to a question I should have asked

41:16sooner,

41:17but I think it's better to ask it now,

41:20which is, what led you to build this? At

41:22what point,

41:23there must have been an inflection point

41:25where you decided, right, I think this is

41:27needed out there.

41:28I know people go and want this. Let's start

41:31building.

41:32- Yeah, so it took me a while. It was kind

41:37of funny. So I mentioned it to Zach, Zach

41:44guys,

41:44who I work with. And I kind of put it off

41:48for a while. Like I had this idea like a

41:52couple of years

41:52ago, like two and a half to three years ago

41:56. And the reason I started to go down that

41:59path is my

42:00career was completely changing. Before I

42:03was kind of in what you would imagine is

42:07what a lot of the

42:07people are in the tablet community, which

42:10is analyst. You're an analyst. You have

42:12some data.

42:13You have stakeholders. You need to create

42:16some sort of solution for the stakeholders

42:20to have them

42:21get to actionable insights, the whole nine

42:25yards. But my career completely switched to

42:29product

42:30design. And so I wasn't even like using

42:33Tableau 50% of the time. It went down to

42:37like zero to

42:39like one to 5%. And I was in Figma all day.

42:42And so I was getting really familiar with

42:44design systems

42:46and UI kits and palettes and type scales

42:49and spacing scales and things like that.

42:55And I just noticed there was, first of all,

42:58there was nothing out there like a Tableau

43:02UI kit that

43:03helps people prototype. And it also stemmed

43:06from things that happened to me previously

43:09at different

43:10jobs where I actually, I had to prototype

43:13as well, but I did it in PowerPoint. And

43:18a bad place actually. Yeah. So I used to

43:22prototype in PowerPoint and I'm like, this

43:26is a nightmare.

43:26I mean, the reason I'm saying it's a

43:28nightmare is because I had no reference.

43:30Well, I thought it

43:33wasn't that bad at the time because I had

43:35no reference to Figma. I didn't have the

43:37reference

43:37about what a good UI kit can do and what a

43:40tool like Figma could actually do. So I

43:43think sometimes

43:44when people are like, I just don't

43:46understand the difference between

43:47PowerPoint and Figma,

43:49I really try my best to articulate the

43:53differences. But I think sometimes it is

43:57something where you're like, you just have

43:58to use it. You just have to try it. Yeah.

44:01It's just

44:01another universe of tooling. Not because

44:05PowerPoint is bad. It's just not made for

44:09that. It's not made

44:11for design at scale. Right. And so it's

44:15made for the office user. Yeah. Which you

44:19can't spend time

44:21like building components. Yeah, exactly.

44:23Right. Like it's a completely different

44:25thing. It's a

44:26completely different thing. And so once I

44:28started using Figma and once I started

44:30using UI kits,

44:31and once I kind of left the Tableau world

44:34of just building Tableau dashboards, I was

44:37like,

44:37all right, I'm going to build a Tableau UI

44:42kit. Right. And it took me a while because

44:45I knew it

44:46was going to be a ton of work. And I didn't

44:49see any. I saw no reference to it really

44:52anywhere

44:52else. I was like, I don't really see it. I

44:55'm not seeing it. So I don't really have a

44:58reference of

44:58how it should be built. So it took me a

45:02while to wrap my head around. You might

45:05notice in the left

45:06hand side sidebar here, like, all right,

45:09where do you put your documentation? How do

45:13you section off

45:14like scales and things like that? You can

45:17see I have different sections and everyone

45:19does it

45:20different, but I did it in this way. Yeah.

45:24And it took me a while to understand how

45:28different

45:28companies even organize a UI kit. Right.

45:32And so how are you going to show the

45:35component?

45:36Are you going to say what you want, what

45:39the component does? And so it took me a

45:41while to

45:42understand that. The first version, I think

45:45looking back at it now, it was pretty rough

45:47.

45:47But like I never did it before. I never

45:52created.

45:54Yeah, I never created a UI kit from scratch

45:57. And then, you know, seeing version one to

46:01now is,

46:02it's kind of night and day. Yeah. So I'm

46:04actually really proud of, you know, the way

46:06it looks now.

46:07And I put so much time into the detail

46:10about everything. And it's just cool to see

46:16the value.

46:17Because, you know, I get it's generally

46:19like enterprise, you know, people are

46:22purchasing

46:22it to like practice and stuff, but it's a

46:25lot of companies. And they're like, oh, we

46:28're getting

46:28a lot of like, genuine value out of this.

46:30And that's really great to hear. Right.

46:33Like, it's

46:33nice to know that the time that went into

46:36it was worth it, essentially. Yeah. So yeah

46:41, I think in

46:43my opinion, this is the part of dash

46:46boarding that I don't think enough

46:49organizations realize

46:52they need. And you also can't really

46:55appreciate the benefit of this. If A, you

46:59have a unicorn in

47:00your organization. Yeah. Right. That's just

47:02that's kind of gets in the way because they

47:05will do most

47:05of this things faster in the product and

47:08have it ready to go. But also, you have to

47:10be at a certain

47:11level of maturity to actually understand

47:14the workflow of getting your product, well,

47:16your

47:16dashboard, which is now called a product by

47:19mistake there, but actually intentional,

47:21from inception,

47:22all the way to delivery, and then setting

47:24up a feedback loop for that to sort of keep

47:27going,

47:28unless you have that entire flow, something

47:30like this, you don't you don't kind of get

47:33the most

47:33value out of it, because this enhances the

47:35speed at which you go from start to finish.

47:38And then

47:38back again, basically, you have to have

47:40that flow to really realize that if you

47:42have this, and you're

47:43just setting up your analytics team, you

47:44just started talking to your stakeholders,

47:46you probably

47:48need to get going a little bit build a few

47:49dashboards to understand, okay, where does

47:51this

47:52where does this process fall over, and then

47:54start to use this to help sort of solve

47:56that problem?

47:57Yeah, I completely agree on that. I think,

47:59I think people might think that I would

48:01always say you have

48:02to prototype in every scenario, no matter

48:06what. But one of the instance instances

48:09where doesn't

48:11really make sense is exactly what you

48:13mentioned, you're just getting Tableau. And

48:16if your company

48:17is just getting Tableau, and you don't

48:20really have a reference of, first of all,

48:22even what Tableau is

48:24that much, or how to build them, or the

48:26process that you would go from an idea of

48:29some sort of

48:30product to the end result, something like

48:33this doesn't really make as much sense,

48:35because you're

48:35just not mature enough. Obviously, you can

48:39look into it for just interest, right? But

48:42yeah, if

48:44you're not mature enough, I generally see

48:47this as one of, I think it's a pivotal part

48:50of the process.

48:51But it's, I'd say it's a piece that comes

48:56later. Yeah. And, but once you start with

49:01it,

49:03you can't really go back in my, you can,

49:07you can totally go back. It's just that

49:11you just see tremendous value with the

49:15design. Sometimes it's hard to quantify

49:17the benefit of a good design. And the way

49:21that I would think about quantifying a good

49:26design is,

49:29one is there's no complaints. It's

49:32absolutely seamless. Good design is so good

49:35because you

49:36never notice it. You always know. You don't

49:39understand. You always know where to go

49:41next.

49:41You're never confused about what you should

49:44be doing. You always understand if I click

49:48this,

49:49it's going to change this. It's so obvious.

49:51And I just think it's something that

49:59people could really benefit from. Yeah. I

50:03think one category that I can say,

50:07you, it makes like, let me rephrase what I

50:10'm saying. One part of Tableau where I think

50:13it'd

50:14be stupid not to use this is embedding.

50:17Because in embedding, you are essentially

50:20building a product.

50:22It just goes without saying you're building

50:24a web platform, you're building the Chrome,

50:26you're building everything around the Table

50:27au visualization. And it lends itself

50:30beautifully

50:30to this because you can come in here and

50:33actually incorporate the UI kit for your

50:35embedding product

50:36alongside this to actually give people a

50:39genuine sense of what the end solution is

50:41going to look

50:41like in the platform. And so I'd almost

50:44sort of say, if you're doing embedding, I

50:49don't understand

50:49why you can't look at something at all like

50:51this. Because if you're taking Tableau that

50:53seriously,

50:54you're going to go and embed it in your

50:55organization. This to me is such a small,

50:58like, but important part of that process.

51:00Yeah, you're absolutely right. Like, for

51:02example,

51:02this first one, you know, this could be

51:05your dashboard or something. And this is

51:07what your

51:08application navigation was like, because

51:12this is actually what an application

51:15navigation would look

51:16like. Right. So this is like exactly what

51:18it could look like. So you're kind of, you

51:21know, covering

51:23was it two birds with one stone, that's

51:27saying. Yeah. And obviously, you know, if

51:31you really need,

51:33obviously, there's kits out there. Like

51:37this is not a web UI kit and a Tableau UI

51:40kit. But it has

51:41a lot of like the main things you need for

51:44application, right? We have like avatars,

51:47badges, button groups, which are really big

51:49buttons. You have chips, which are really

51:51big as

51:51well. Yeah, headings layout, but the other

51:54thing is, things like that. The other thing

51:58is, like,

51:59whoever whoever's building your web

52:01platform likely has something like this for

52:04the platform. And what

52:06they'll do in that Tableau space is put

52:08like some generic image from dribble in

52:10that space, which

52:11looks nothing like Tableau. Yeah. Whereas

52:13you've got that Tableau bit right done. So

52:15in my mind,

52:16I'm sort of imagining web agency turns up

52:18with their UI kit that sort of explains how

52:21the website

52:22and the platform works. And then you turn

52:24up with this Tableau UI kit and the two

52:25kind of match made

52:26in heaven kind of come together and the

52:28client for the first time can actually see

52:30what they're going

52:31to get before it gets built, which is like

52:34never happens. Yeah. And a quick a quick

52:36thing on dribble.

52:40Not to go on a full dribble rant here. In

52:44the design community, dribble is looked at

52:48like,

52:48there's really great work on dribble. But

52:51it's the same thing with any social media

52:53platform.

52:54Things are, let's say Twitter, things are

52:58worded in a specific way to get the most

53:01amount of

53:02engagement. The same thing happens with

53:04dribble. So the things that you generally

53:07see as most

53:08popular, right, which I see a lot in the

53:10Tableau community, they'll like, kind of

53:12take whatever

53:13they see on dribble and then try to do in a

53:15Tableau dashboard. Those are not real

53:18applications

53:19that people design and realize. There's all

53:23there's like a ton of like skew morphism

53:26and like,

53:27crazy effects that you would not see in a

53:30real application. So what I would say is,

53:34there's really great designers that are

53:37putting stuff on dribble that are basically

53:40building in

53:41public. That's kind of what they call it.

53:43They're building in public, they're

53:45building some sort of

53:46product. And they're showing you the

53:48process along the way. So if you can find

53:51those people

53:52that are creating a real product, and they

53:54're showing you real screenshots of real

53:57things

53:57they're going to implement, that would help

54:00you a lot more than just looking at the

54:02trending page

54:03of dribble. Because they're just they're

54:06crazy designs and no one is actually no,

54:08there's

54:09actually a common like meme that you'll see

54:11around. It's like the designer designing

54:13the thing. And

54:14then it's like the engineer, which is just

54:16like completely bummed out. They have to

54:18like engineer

54:18this crazy design that makes no sense. And

54:22so just be careful with that.

54:26So yeah, it's good advice. It's good advice

54:30. I, I fall guilty of, you know, opening up

54:33a

54:33Chrome tab and googling something to get

54:36like a bunch of images just so I can sample

54:39like

54:39what I think it should look like. And I'll

54:42just sort of do a quick scan of that. And

54:44then I'll

54:44try and sort of replicate something in my

54:46head. But actually, you're right. Like, the

54:48context is

54:49so important, the context of that book,

54:50especially if you want something that works

54:52. And that is so

54:54important. So yeah, generally, I mean,

54:57everyone has different tastes, right? My

55:01general cases,

55:02which is why, you know, I love Apple so

55:05much. And I love the ARC browser, like we

55:09were talking

55:09about earlier. I love these opinionated

55:13designs on things that are easy to use,

55:16just work.

55:19And they're just clean, super clean. I love

55:23clean. I know some people don't.

55:26Some people kind of love, they like, they

55:30like the color they like, not like flat

55:34design.

55:35You know, they're, they like other stuff.

55:37That's their taste. But I just love clean,

55:39realistic designs, essentially.

55:46And I think everyone should have an opinion

55:48. Yeah, like, that's what Rob likes. I'm a

55:53real

55:53fan of like, there's a current trend in

55:55design where things look like they're all

55:58made of glass.

55:59Like, I don't know why, but that kind of

56:01glass morphism, like that. Yeah, glass

56:04morphism.

56:04Yeah, it looks super cool.

56:07There's so many different tastes. But you'd

56:09have to have an opinion. And as long as you

56:11can stand

56:12behind it. And key thing here, you

56:15understand what makes that design work,

56:17then yeah, like,

56:19run with it, make it work in whatever

56:21context you want it to work. But if you

56:23want people to use

56:23your product, dare I say your opinion doesn

56:26't matter. Right? You've actually got to

56:29build for

56:30people and they might not go with that flow

56:32. And actually, sometimes the right thing to

56:34do is to

56:35put your sort of design sense to one side,

56:37and try and say like, what what will these

56:39people accept?

56:40What will they adopt? Right? Because those

56:42are the two things that have to work in an

56:44enterprise

56:44context as well. Exactly. And that's what

56:47the prototypes are great for. Like you

56:49mentioned,

56:50like you mentioned earlier about, you know,

56:52using the prototype feature I have in the

56:54top right here.

56:54Yeah. What I like to do, you know, with our

57:00application design is, you know, you have

57:02the

57:02prototype, and then you have functionality,

57:04you give them the prototype and say, hey,

57:06what,

57:07ask them specific questions. Like, if you

57:09're going to do this, where would you go?

57:11And you kind of

57:12Yeah, you kind of give them prompts. And

57:14you watch their mouse about like, where are

57:17they going? What

57:18are they clicking? Clearly, you said this

57:20one thing, and they're going to this

57:21different section.

57:22So something must be off. Yeah. And so it's

57:25really great for that as well.

57:27Amazing. Thank you so much. Thank you so

57:29much. This has been super valuable. I'm

57:33gonna I am long

57:35overdue a purpose of this UI kit. So I'll

57:37definitely be purchasing myself and using

57:40it. I think

57:41there is I would love at some point to do a

57:44video on like, I'm going to design a

57:46dashboard from

57:47start to finish, but I'm going to do it in

57:49like an opinionated way, right? And I'm

57:51going to

57:52prototype it, we're going to come up with

57:54the date of the story, everything, and it

57:56might be like a

57:56six hour stream. But just want to give

57:59people sort of a view into that kind of

58:01process. Because I

58:02think until you see the whole process, in

58:04the most ideal way, you can't really

58:06critique sort of

58:07different parts and see what works for you

58:09and see what what you can try, but also get

58:11some hints as

58:12to here's how to do it. Like it's not as

58:13complicated as it looks a lot of the time.

58:15It's just

58:16just requires you to get Yeah, I love that

58:17idea. Because, you know, I've done sessions

58:21like this

58:21where I'm kinda I'm kinda showing it off. I

58:25'm also like, you know, explaining what it

58:28is, and just

58:30like the general concept of a UI kit. And I

58:32'm showing how to build a dashboard. But I

58:35've never

58:36like, taken the I've never done a video,

58:39taking the full kit and saying, all right,

58:42I'm going to

58:44build a great looking dashboard from start

58:48to finish. Usually I stop at the chart

58:52where I never

58:52actually show how I style the entire chart.

58:56So it would be interesting to just do a

58:59full, like full

59:01build of some sort of exactly. And I don't

59:04want it to make it seem like you can build

59:07literally

59:08anything you can possibly think of using

59:10the Tableau UI kit. I think that's an issue

59:12some

59:12people run into with like, they're like, Oh

59:14, I'm trying to do this one specific thing.

59:16But it's

59:16such a niche thing that they're trying to

59:19do. Like I can't. I can't build for every

59:23scenario that

59:23someone's gonna. Yeah, so I think it would

59:26be good. It would be good to show like, Hey

59:28,

59:28I have this one use case for this dashboard

59:31. And I need to do this custom thing. How

59:34would I do this

59:35custom thing and add it into this dashboard

59:37? And how would I use the two together and

59:40like,

59:40doing custom and the kit together? Because

59:44most people that are doing websites, unless

59:48they want

59:48their website to look like all the other

59:52websites, they're going to take the UI kit

59:54and customize it

59:55to the way that they want for a truly new

59:59experience, not just like boilerplate.

60:04So yeah, true. Yeah, so that'd be

60:07interesting. So be good fun. I'll let you

60:10know when I do that.

60:11I'm trying to do more live streams. So that

60:13's something that we're, it's breaking the

60:17ice. I

60:17don't have the stamina of these Twitch

60:19streamers. I can go on like eight hours at

60:21a time. I just

60:22like, wow, I did it once. I don't know. I'm

60:25gonna need to do this for a long time

60:27before I get to

60:28that level. It's crazy. They do it all day.

60:30I mean, but it is their every day, five

60:32days a week

60:33is their living. Like they literally make

60:35some of them make a ton of money, some of

60:37them not so much.

60:37But I think there's a portion of content

60:43that could really be sort of opened up with

60:46live

60:47streams because too much, you get the

60:49polished view of like, here's a 10 minute

60:51video, 50 minute

60:52video, I'm going to build this. The end

60:54solution is there. The thing that I think

60:56people value a lot

60:58is like vanilla to the end. Like just start

61:02from nothing. Let's see your process.

61:05People, I think three or four of those

61:07would really go a long way in helping

61:09people sort of

61:10understand the Tableau world better from

61:13nothing to server, from nothing to Tableau

61:17cloud,

61:17but from prototype to Tableau embedding,

61:21those are sort of like a few of the top

61:24things I want

61:25to do. Tableau server installs is the

61:26classic one everyone asks for, but no one

61:28will watch

61:29as a YouTube stancer. Those have always

61:32been my favorite videos to watch where,

61:36you know, you get a lot of people of, you

61:38know, they're doing, I mostly at this point

61:42only follow,

61:44you know, like design people on Twitter.

61:47And yeah, a lot of my favorite content is

61:53like a long form,

61:54like how do I actually like straight up,

61:57how do I design? I'm stuck in this portion.

62:00What's my

62:01mindset? How do I continue? What are my

62:04strategies? And so usually you just see the

62:08end result and you

62:09have no idea all of the like insanely small

62:12decisions that go into getting to that

62:15final

62:16product. So there's definitely not everyone

62:19's going to watch it, right? Like, because

62:21it is

62:22like longer and not everyone loves that,

62:24but it's in my opinion, the most valuable

62:27in terms of like

62:28concrete learning, in my opinion for design

62:32specifically for me.