How to find out what's new with Tableau: Friday Thoughts Episode 1

0:00Hey, it's Tim here. In today's video, I'm

0:01doing something slightly different. I'm

0:03starting

0:03something new on Fridays, I'm basically

0:05going to be sharing my thoughts on any

0:07topic pretty much

0:08that comes up in the questions in the

0:10comments or something that I come across

0:12quite often.

0:13But it's not really a tutorial and it's not

0:14really something that I can show you. It's

0:16just something

0:17I can talk about. So every Friday, I'm

0:19going to be talking about something. In

0:21today's video,

0:22I thought I'd talk about something I do a

0:23lot of which is keeping in touch with what

0:25's new in

0:26Tableau. Now, I actually gave a much sort

0:29of longer version of this in the Tucson

0:31user group,

0:32go ahead and check that video out. It's

0:34available on Tableau's own YouTube channel.

0:37And you can see

0:38basically some sort of pretext to what I

0:40was talking about, which was when you

0:42approach new

0:43releases, you really have to sort of step

0:45back away from the product and almost step

0:48away from

0:48the product excitement and just evaluate

0:51what's been released in a more pragmatic

0:53way. And so

0:53in this video, what I wanted to do is

0:56highlight how I do that and how I go

0:57through that process.

0:59Then at the very end, I'm going to try and

1:01sort of break down a product release as

1:02such,

1:03sort of show you how you should look at

1:05these things. And maybe how you can make

1:07better

1:07judgments about whether the features that

1:09are being released are actually good for

1:11you,

1:11your organization or for the group of users

1:13that you look after. So I'm sorry for the

1:16long intro,

1:17let's get stuck in. Okay, so I've got

1:19something up on screen, which is just

1:21something I prepared for

1:22the Tucson user group. And it's essentially

1:25a list of all the places that I go to, to

1:27find out about

1:28what's new in Tableau. And so I'm just

1:30going to go through each of them one by one

1:32. And I'm going to

1:33sort of talk about the value of each one.

1:35Now note the subheading here, which is that

1:38the information

1:39that's available about what's new in Table

1:41au is available in lots of places. But in no

1:44two places,

1:44will you find the same thing because in

1:46each place, something different is being

1:48communicated.

1:49And that's why you've really got to sort of

1:51cover your bases and look at all these

1:53places because

1:54sometimes it's the details that really

1:56count with these releases, and they're not

1:58always in

1:58one place. So let's first start up with the

2:01beta process. So the beta process is an

2:04important part

2:05of software development, essentially a

2:07couple of months, maybe two to three months

2:09before the

2:09actual release Tableau make available what

2:12they're planning to go live with. And

2:14essentially, it's

2:15being made available so that you can use it

2:17, you can test it, you can make sure that it

2:19does what

2:20it's supposed to do. But most importantly,

2:22you're also helping them find bugs. So they

2:24often ask for

2:25feedback. And they often ask you to use the

2:27product in a particular way. Or they just

2:30tell you to use

2:30it as much as you want on real data. So you

2:32can figure out how it works. Now, words of

2:35caution

2:35here, you should never use a beta on

2:37production software or hardware. And it's

2:40essentially

2:40supposed to be used on development software

2:43. So a lot of organizations should have a

2:46development

2:46version of Tableau running, whether it's a

2:49dev version of Tableau server or a dev

2:52version of

2:52Tableau desktop. And the reason you test

2:54these things is to find out sort of any

2:56quirks that

2:58might happen when you deploy it across 1000

3:00s of people in an automated way. So it's

3:02actually a

3:03good thing to be part of. And what you get

3:05to find out is essentially how the features

3:07work.

3:08With each beta pre release is obviously

3:09some documentation telling you what's new,

3:11how it works. And there's also

3:13documentation that's going to help people

3:15use it. So if there's

3:16any issues with that documentation, this

3:18also gets pulled up during this process.

3:21Now, the thing I

3:21really value the most about the beta

3:23process is the fact that developers

3:25actually feed into this.

3:26So you actually get a more, I think, honest

3:29perspective of what product marketers and

3:31product

3:32devs were actually intending this feature

3:35to be used for. And there's this thing in

3:37the Tableau

3:38community where a feature comes out, and we

3:40don't use it how it's supposed to be used.

3:42And this kind

3:43of behavior comes out right through in the

3:44beta. So you can sort of talk to the

3:46developers, see how

3:47they're thinking you should use it, and

3:49then see anything that sort of comes up

3:50that you know, you

3:51could also use it for but wasn't

3:52necessarily, you know, in their in their

3:54trailer blind. So that's

3:56the beta process in a nutshell, at the end

3:58of the beta process, typically the software

4:00comes out.

4:00And boom, voila, we have the release, and

4:02you can get involved with the beta process,

4:05it's really

4:05super easy. I'll put a link up on the

4:07screen now, or I'll put a link in the

4:08description so you can

4:09dive in. But that's pretty much the beta

4:11process, you get to find out about stuff

4:13before it comes

4:14live. Now, there is an NDA, of course,

4:16which is why people don't often talk about

4:18these things

4:19widely. But you know, in most recent years,

4:21actually, people have sort of just been

4:23talking about the features anyway. So that

4:26's been an interesting trend. So the kind of

4:29release,

4:29the release kind of has a little less

4:31excitement, because essentially, things

4:33come out a little bit

4:34earlier than they're supposed to. But that

4:36's not that's not a bad thing. I guess we

4:37need to learn

4:38what these features are going to be used

4:39for. And you know, the community really

4:41sort of go all out

4:42and find out what's what's good and what's

4:44not. Okay, the next place you can find out

4:46about what's

4:46new in Tableau is the product marketing

4:48blog. Now, the product marketing blog is

4:50just a Tableau blog,

4:51essentially. But in essence, this is where

4:54Tableau really sort of get into its sort of

4:57prose

4:57and voice. This is where Tableau really

5:00talks to you in the way that they want you

5:02to perceive

5:02the product. And this is sort of important

5:05in two ways, because this is also the stuff

5:07that gets

5:07picked up by product reviews. It's also the

5:09stuff that gets picked up by, you know,

5:12people like

5:13Gartner who really evaluate what's new with

5:15the product. And this is the stuff that

5:17tends to go

5:18the furthest because when Tableau say there

5:19's something new, the press engine gets

5:21going,

5:22the marketing engine gets going. And

5:24because of that you really want to lead

5:26with your best foot.

5:27So what the product marketing team tend to

5:29do is they pick the best products and to

5:32sort of go out

5:33with and that doesn't necessarily mean

5:34Tableau desktop or Tableau prep, just

5:36essentially means

5:37look, which features are going to, you know

5:39, really gain people's attention and really

5:42sort

5:42of catch fire and move forward. And so it's

5:45always interesting because you can really

5:47see when product

5:48marketing sort of gets that wrong, because

5:50they'll obviously champion a feature for

5:52one thing, and

5:53then it gets picked up and used for

5:55something completely different. And because

5:57we have the

5:58beta process, and we also have the release,

6:00what also happens sometimes is that there's

6:03a little

6:04bit of a lag between when the features

6:06released, and then when the community

6:08figures out how to use

6:09it to do incredible things. And so there's

6:12this sort of two month window where a

6:14feature can sort

6:15of get multiple moments of airtime because

6:18it comes out, people like it, it's great.

6:20And then a

6:21few days later, someone has figured out

6:22something great. And then a few more days

6:24later, things just

6:25sort of go wild. So it's definitely

6:27something to be aware of the product

6:29marketing blog is a good

6:30place to go. But it's often a perspective

6:33that's coming from Tableau from a marketing

6:36perspective.

6:36So if you're a user of Tableau, you just

6:39want to get to the point. And it doesn't

6:41tend to have

6:42all the detail of what's new. And so for

6:44that, we actually go to the official

6:46product release page,

6:47which is the next thing I'm going to talk

6:49about. Okay, so the official product

6:51release page is by

6:52far the most thorough, I'll actually put

6:54some sort of clips of it in front of the

6:56screen right now.

6:57And the reason it's thorough is because it

7:00actually has very, very clearly spelled out

7:02each

7:03of the key features that are being released

7:04. Now this obviously this has obviously been

7:07cleansed

7:07by the product marketing team. And they're

7:10sort of encapsulated. So you'll tend to

7:12find they sometimes

7:13group features. So they might group all the

7:15web ordering related stuff in one in one

7:18release,

7:19they might group all the features related

7:21around a particular aspect. For example, in

7:23the most recent

7:24release, they put all the R-data

7:26capabilities in two brackets, R-data for

7:29viewers and R-data

7:31enhancements in one bracket. And then we

7:33had R-data lenses in a separate bracket.

7:35The reason

7:36being is that sort of two distinct things

7:38enhancements can kind of go with the new

7:40capabilities for viewers. But the R-data

7:42lenses, which are entirely new, needed

7:44their own space.

7:45And so you can kind of get this separation

7:47of features where it's actually one big

7:50feature,

7:50but it's been split up in sort of digest

7:52ible chunks, which makes total sense. And

7:54but you've

7:55also got to look out for that because you

7:56might hear that, hey, this is new. But

7:58actually, when

7:58you drill into it, there's several things

8:00that are new in that. And the other thing

8:02to watch out for

8:03is that this also captures a lot of the

8:05things that are really hard to talk about

8:07things like new data

8:09connectors. And those are the kind of

8:10things you can scan very quickly. And if

8:12you use that

8:13connector, great off to the races, and you

8:15're pretty much good to go. However, there

8:17are also

8:18a lot of things in there that aren't

8:20necessarily relevant. So you do have to

8:22filter this list out a

8:23little bit and work with it as much as you

8:25can. What I tend to do is break it down

8:27into the three

8:28different users. So are you a creator? Are

8:30you a viewer? Or are you explorer? And I've

8:33done it in

8:34that order, because those to me are the

8:35most meaningful sort of, that's the most

8:38meaningful order.

8:39So the creator is someone who builds stuff

8:41for people to use, the viewer is the

8:43largest group of

8:44those people who use that content. And the

8:46explorer is sort of this middle house. So

8:49really, the

8:49explorer and the viewer are the you know,

8:51the key items and the key people that are

8:52using content

8:53and making content. And the explorers are

8:56sort of viewers on their way to greatness,

8:58I tend to call

8:59them so the explorers tend to have a little

9:01bit more flexibility to do more things.

9:04They've been

9:04given a little bit more trust to manage

9:06content, but they're not quite there yet in

9:08terms of

9:09licensing, so they don't have the ability

9:11to create a lot of content. But I'm pretty

9:13much sure that in

9:13the future, this is going to change and it

9:15's going to change the dynamic of how the

9:17product works.

9:18But nevertheless, the Fiswick product

9:19release page is great, and one of the best

9:22places to go and I

9:23highly encourage you go there first after

9:25each release. If you already in the beta

9:28process, you'll

9:29already know most of the things in that

9:31page. But interestingly, sometimes the

9:33stuff in there that

9:34hasn't been in the beta as well. So you don

9:36't actually know what's in the release until

9:38it's on

9:38this page. So this is how we know what's

9:41what. There is also a sort of rogue version

9:43of this

9:44called the coming soon page, which is

9:46essentially the same page but before the

9:48release. So before the

9:50release is called coming soon. And it's

9:51essentially what's been talked about in the

9:53beta process.

9:54And then after the release is the actual

9:56release page with the final set of features

9:59and features

10:00come in and out all the time. So you could

10:02even find that something gets launched on

10:04day one,

10:04and then it gets pulled because there's a

10:06bug, there's a security feature that's sort

10:08of not

10:09up to scratch. And so when you go to this

10:11list, don't worry if something appears and

10:14then disappears,

10:14it's just it's just sort of the flow of

10:16software design. Sometimes things go wrong,

10:18you need to

10:18fix it. And things have to sort of be re

10:20evaluated for the next release. New in the

10:23most recent

10:24versions of tablet is a summary video. So

10:26the summary video is actually quite nice

10:28because

10:28what it is essentially another video that's

10:31been put out by Tableau this time summar

10:33izing

10:33everything that's new. Now, unfortunately,

10:36it's not necessarily a video showing you

10:38how things work. It's just telling you what

10:40's new. So it's very short six minutes

10:42really,

10:43really cool. I'd like to think they've

10:44started doing this more because there's

10:46lots of people

10:47in the tablet community making great video

10:49content. And so Tableau sort of, you know,

10:51trying to put its own voice into that

10:53because of course, you want to have some

10:55sort of stewardship

10:56of the narrative when you release a product

10:58. So of course, you want to go with your

10:59video.

11:00And because you know what's in the release,

11:01you have the edge there because you can

11:03actually make

11:03a video telling people what's in the

11:05release before it goes out. So that's sort

11:08of one notable

11:09advantage of Tableau doing that. But it's

11:11also a good thing because you have a nice

11:13six, five minute

11:13video that covers everything. I'll put a

11:15link to some of those in the description. I

11:17'll put one up

11:18on the screen now so you can see what that

11:19kind of looks like. But nevertheless, it's

11:21a really good

11:22video. I highly encourage you to watch it.

11:24At this point, you should know everything

11:25in the release.

11:26But there's a big but here, not everything

11:28has been covered. So when you go to the

11:31individual

11:32product help pages, there's always a link

11:34that tells you what's new. And this is a

11:37really

11:37important part because not only does it

11:39list what's actually new in this release,

11:42in more

11:42detail than some of the other pages, but it

11:45also links to the documentation. And this

11:47is where

11:48things really start to come online. Because

11:50often there's a new feature. And if you

11:51just look at the

11:52interface, you don't have any call outs

11:54telling you what's new. And so this is

11:56actually really

11:57good because it tells you how to use the

11:59new features. So the product help pages and

12:02documentation

12:03by Tableau is really, really good, you

12:05should always check it out. But when

12:07something's new,

12:08this is the first place I tend to go to to

12:10actually find out how to use it. And Table

12:13au is really good

12:13at highlighting quirks, because there's a

12:15lot of consideration that goes into how

12:17these things

12:18work. So all of that is captured in the

12:20documentation. And often, you can sort of

12:23very

12:23quickly understand how something's going to

12:25work just by reading that without even

12:26touching. So if

12:27you not necessarily have time to open up

12:29Tableau and try things, this is a sort of

12:32nice alternative,

12:33you can go to the documentation, skim read

12:35it, and you're pretty much there. Of course

12:37, you can also

12:38wait until you know, someone makes a video

12:40about the feature, like I sometimes do. But

12:43nonetheless,

12:43the documentation should be really your

12:46first port of call. That's the absolute

12:48sort of

12:49a gospel of what's new. And it pretty much

12:51tells you exactly how everything works.

12:53That's where I

12:54get my information from. And so it's the

12:55first hand source of information. Now, the

12:58remaining

12:59ones are probably the most undervalued part

13:02of this process. When I say that, I just

13:04mean that

13:05people don't really appreciate how much

13:07comes from these remaining sources. Okay,

13:09so the first one is

13:10a Tableau community. Now, of course,

13:12everyone appreciates that a lot of the new

13:15things are

13:15shared and communicated by the Tableau

13:17community. But the key thing here is we all

13:19do it at different

13:20paces in different places. And we all

13:23appreciate completely different things. And

13:25it's just

13:26impossible to capture all of that in one

13:28place. So for this one, you really actually

13:30have to work

13:31hard to listen to what people are saying

13:33about the new features. And sometimes it

13:36takes, you know,

13:37I've seen features and be completely ripped

13:39open by people in the community two to

13:42three months

13:43after the release, because you've worked on

13:45a project and you found some sort of weird

13:46use case

13:47that something's been enabled, and suddenly

13:49you're off to the races. The other thing is

13:52that

13:52sometimes features get staged. So if we

13:54take relationships, for example, they came

13:56out in

13:57version one, and the subsequent versions

13:59have sort of improved in a big way to the

14:02point where

14:03some of the things we were complaining

14:04about in the first part, aren't really

14:06issues now in the

14:07third or fourth iteration of relationships.

14:10And so the thing here to bear in mind is

14:12when something

14:12comes out, it doesn't mean that's the end,

14:14it doesn't mean that Tableau is done, you

14:16've actually

14:17got to sort of stay in tune with the future

14:18, especially if it's something that's going

14:20to help

14:21you, you got to stay in tune with the

14:22future over probably six to seven releases,

14:25and six to seven

14:26releases means six to seven quarters, which

14:28kind of means you're really need to dial in

14:30for about

14:31two years when something completely new

14:33comes out. A good example, explain data and

14:35ask data. Since

14:36those have come out, we've had something

14:38about them in virtually every release. So

14:40if I did a

14:41video two years ago about ask data, it's by

14:43no means relevant anymore, because the

14:45product has

14:46changed so much. And they've added so many

14:48new features that it's moved on miles. And

14:51the most

14:51recent release made it available for

14:53viewers. And now even the licensing has

14:55changed. So that's

14:56something you just got to be aware of, and

14:58to stay in touch with, you know, what's

14:59changing with

15:00Tableau. The last one is still underrated,

15:03that is using it yourself. And I'm the kind

15:06of person who

15:07likes to Yeah, okay, I read the

15:08documentation, I rarely actually intend to,

15:11I read the documentation

15:12because I'm trying to find out how to get

15:14at the thing I want to get at. So when you

15:16use a product

15:17yourself, you actually discover the nuances

15:20that really sort of make it work for you.

15:22And also can

15:23sometimes break it for you, if that makes

15:25sense. So sometimes you have this

15:26expectation that

15:27something's going to work one way, and it

15:29works a slightly different way. And if you

15:31wait until you

15:32need that feature, that's when you're going

15:34to get disappointed the most. So if you use

15:36the feature

15:37upfront, and maybe use it, like you know,

15:39in the beta process, you can actually feed

15:41back into the

15:42product development and make it a better

15:44feature for when it's released. And so

15:46using it yourself,

15:47although is sort of far down this list, I

15:49think is one of the most important ones,

15:51because until

15:52you've used it, you don't really know how

15:53to use something, you don't really know how

15:55to show

15:55someone else how to use it. And one of my

15:57colleagues has always said, look, the best

15:59way

16:00that you know, whether you know something

16:02is how well you can teach it to someone

16:04else.

16:04And essentially, anybody using it, will you

16:06be able to do that. So that's sort of a

16:09really good

16:10measure for how you well you understand the

16:11feature and just make sure that that's

16:13something

16:13that you put aside time to do. It does take

16:15time, you'll never use all the features. I

16:17don't do

16:18videos and all the features, I don't get

16:20time to touch every single feature. It's

16:22virtually

16:22impossible. You know, five years ago, that

16:24was possible today. And that's just not

16:26possible

16:26anymore. So you have to choose wisely what

16:28you spend time with. And you just have to

16:30go with

16:31flight. The very last page is the known

16:33issues page. Now no one likes to talk about

16:35problems. But

16:36sometimes sometimes in a release, they are

16:39bugs. And bugs can really ruin your day, if

16:41you're not

16:42aware that they exist. And I've had this a

16:44couple of times, there was a really weird

16:47quirk back in,

16:48I think it was 2019.4 or something, some

16:51really old version anyway, where aggreg

16:54ations in a very

16:55specific instance weren't working correctly

16:58. And I just happened to be building

17:00something

17:01right in the sweet spot for that particular

17:04instance. And I spent three days trying to

17:07understand what was going wrong. And it

17:08wasn't like three straight days, it was

17:10just sort of

17:10three days of revisiting it, trying to fix

17:12it, trying to do something else, trying to

17:14fix it,

17:14not working. And then I suddenly just

17:17thought, wait, is this a bug? And so what I

17:20did is I went

17:20to the known issues page, and there it was

17:22a bug. Now just think how much time I would

17:24have saved if

17:25I went there straight out if I went there

17:27right at the beginning. And so the known

17:28issues page is a

17:29good place to go and check if things are

17:32working the way they're intended. And often

17:35after a brand

17:36new release, that is actually when there's

17:38the most issues. So if you take the most

17:41recent release 2021.2

17:43the first release of that 2021.2 release

17:47will have bugs, it's just inevitable.

17:50There's some things that don't get caught

17:52when you're building software. And it's

17:54funny because

17:55people always say, well, did they never

17:56test it? Well, here's some maths for you.

17:59Let's say you have

18:00100,000 beta testers, let's say your Apple,

18:02you have 100,000 beta testers, and you give

18:05them access

18:05to your operating system. That's great. And

18:08when you test it with 100,000 people, you

18:11see this

18:11problem, but it turns up in 0.001% of users

18:14, right? And so 100,000 users. So that's

18:17roughly

18:18one person that out of 100,000 people that

18:22had this problem. So in your parlance, that

18:25's not a bug,

18:25that's just a weird quirk related to one

18:27person. And you're not going to chase it

18:29down because you

18:29don't know whether it's the user, the

18:31device, the quirk, the environment they're

18:33in. It's just not

18:34worth chasing time for that one bug. Now,

18:37imagine you then roll out the software to a

18:40billion people,

18:42suddenly the 0.01% is actually a meaningful

18:45number of people. And now you've actually

18:47got to start

18:48paying attention to these bugs. And that's

18:49sort of what happens here with software

18:51development. Of

18:52course, Tableau do their best to make

18:54everything work. But you just can't catch

18:56everything. And so

18:57there are actually subsequent releases of

19:00Tableau for each version that pretty much

19:02go on. And

19:03Tableau actually do communicate when they

19:05stop supporting a specific version and a

19:08specific

19:08release. That's something to be aware of.

19:11Now, as we move into the browser world,

19:14that's going

19:14to happen less and less because as

19:16everything moves to the browser, Tableau

19:18will always be

19:19up to date, essentially, the browser

19:21version will be getting hot fixes, I assume

19:23, almost weekly and

19:24daily as I see the issues coming in. So

19:26whilst it's a pretty sort of old way to

19:28think about it

19:29with software installations, going forward,

19:32you should see this have less and less

19:34significance,

19:35i.e. you shouldn't have to go to the known

19:37issues page because a lot of the issues

19:39will be ironed

19:40out as people start to use it almost in

19:42real time. Okay, so that's pretty much all

19:45the places to find

19:46out about what's new in Tableau. I'm sure I

19:48haven't got all of them. If you've got one

19:49that

19:50you know about that I've just forgotten to

19:52miss out of this list, then let me know in

19:54the comments

19:55below. I'd love to know your thoughts. Now,

19:57before I go, I just want to do one last

19:59thing, which is

20:00to talk about how you should look at the

20:02features when they're released. And I've

20:04got this little

20:05slide here. Let me go to this next page

20:07here, which is where are Tableau features

20:09heading? And

20:10this is always an interesting question I

20:12ask every single time. And if you don't pay

20:15attention to it,

20:16you'll actually sort of miss the signals

20:18that Tableau sort of give you at conference

20:20,

20:20you'll miss the signals that Tableau give

20:22you in lots and lots of different places.

20:24And the questions I tend to ask is, you

20:26know, right at the top of this page, where

20:29is Tableau

20:29heading? The next one is, what role will

20:32Salesforce play in that direction? Now, the

20:34reason this is a

20:35specific question at the moment, is because

20:37the Salesforce acquisition closes roughly a

20:39year and a

20:40half, two years ago. And when these

20:42acquisitions close, especially at the scale

20:45that they're at,

20:46and it takes time for the influence of the

20:48parent company to sort of trickle through

20:50into the

20:51company that's acquired. So you'll see that

20:54in sort of small ways initially, then you

20:56start to

20:56see it in big ways. And so so far, I think

20:59we've only seen it in small ways in terms

21:01of product

21:02features and the way the product works. I

21:04think what's going to happen in the future,

21:06we're going

21:06to start to see in big ways. And that is an

21:08important dynamic. Because for the

21:11community

21:11that's mostly just been on its own, you

21:13know, looking after itself, and the Tableau

21:16community,

21:16that is we we're going to have to start to

21:18integrate ourselves with the Salesforce

21:20community

21:20a lot more because we won't just be a

21:22product on our own, we'll actually have to

21:24integrate with

21:25other products, especially some of the

21:27Salesforce 360 capabilities. And so that's

21:32going to

21:32happen one of two ways, either Salesforce

21:34users are going to come to Tableau, or

21:35Tableau users

21:36are going to go to Salesforce. But whatever

21:38happens, it's going to have to happen on

21:40both

21:40sides. And so seeing that into play when it

21:43comes to features and how things are

21:44working is going

21:45to be a really important dynamic. Okay. And

21:47the last thing is, what does the history of

21:50feature

21:50releases tell us? I've already touched on

21:52this a little bit throughout the talk. But

21:54when I look at

21:54a feature, I always go back and I look at

21:56like previous features to see, okay, how

21:58are they going

21:59to start to roll this out, that gives you a

22:01hint of where things are going. And so one

22:04of the nice

22:04things with the new release, for example,

22:07is the explained data and ask data. Now,

22:11they use up a

22:12really interesting part of the interface

22:15that sort of been added on and it sort of

22:17sort of started

22:18sort of coming in with metrics. So with

22:20metrics, when you click to enable a metric

22:22on server,

22:22you get a panel on the right hand side. And

22:25that was really interesting, because that

22:27panel on the

22:27right hand side has never really existed.

22:29And with explained data, Tableau starting

22:32to use that panel

22:33on the right hand side a little bit more.

22:36And this this right hand side is sort of a

22:38small thing,

22:39it's becoming more and more sort of feature

22:41. And but as they, you know, add more stuff

22:44to the

22:44product, and you have to start to spread

22:47aspects of the software across the screen.

22:50And these sort

22:51of panels, especially this one on the right

22:53hand side, seems to me like it's going to

22:54be an assistive

22:55panel, it's going to be primarily designed

22:58for people who are using the visualization

23:01rather

23:01than people who are building the

23:03visualization. And so that's just something

23:05small thing to sort

23:06of look at and an example of how things

23:08work. But nevertheless, I think it's really

23:10, really cool to

23:12sort of just try and sort of look ahead and

23:13see where things are heading and how things

23:15could end

23:16up with the features. Now, a very, very

23:19final thing is the Tableau blueprint. And

23:21the reason

23:22I bring this up is not because this is a

23:24video about Tableau blueprint, but

23:27essentially, when

23:29you think about features, each of the

23:31features that Tableau releases, tends to

23:34answer a question

23:35that intersects with some part of this flow

23:37. Okay. And something we've seen in the last

23:40few years is

23:40Tableau really ramping up the elements of

23:43the product that capitalize on things like

23:46the

23:46community and governments, and not

23:49government governance. And so this is

23:51really interesting.

23:53And this is actually really important,

23:56because if a feature that you're thinking

23:58of that Tableau

23:59should build doesn't really sit nicely on

24:01one of these intersections or multiple of

24:03these

24:04intersections, then in my view, you're

24:06really going to struggle to get that, you

24:08know, feature

24:09on a plate. Because if you look at this

24:11sort of flow backwards, and not necessarily

24:13from right

24:14to left, but if you just look at the flow,

24:16and you think about how Tableau perceive it

24:18,

24:18but product devs are going to be trying to

24:21answer questions that sit within these

24:23pillars. And these

24:24pillars are sort of much, much higher level

24:26, they're more strategic about, you know,

24:28what are

24:28we going to solve this year? Or how are we

24:30going to move things forward over the next

24:32three years,

24:33what's going to be one of the important

24:35avenues. And a big avenue that is really

24:37apparent that

24:38Tableau is tackling is this capability of

24:41empowering not just the authors of data

24:44visualizations and analytics, but actually

24:47the users directly. So giving the users the

24:50ability to use visualizations, without

24:52needing to go back to the authors and ask

24:55them to enhance

24:56them, you know, giving people the everyday

24:59people the power to just analyze data

25:01naturally without

25:02having to open up Excel without having to

25:04do something else, essentially almost

25:06getting rid

25:07of this idea of having to build dashboards

25:09to get answers to questions, because that

25:11takes time,

25:12it takes a lot of sort of patience as well.

25:14And in some organizations, it's not done

25:16well, either,

25:17even if they have the resource. So that's a

25:19really interesting dynamic. And you can

25:21kind of see that

25:22in Tableau strategic direction as well. And

25:25so these kind of high levels of strategies

25:28do

25:28actually influence the bottom end of what

25:30comes out of Tableau. So it's really,

25:32really important

25:33to sort of stay in tune with that as much

25:34as you possibly can. And so that's it. This

25:36has been a

25:37long video, I'm going to end this here. I

25:39just wanted to do something very casual,

25:41talk to the

25:41screen and talk about my thoughts on a

25:43particular aspect. So that's been my

25:45thoughts on how to stay

25:46in touch with new releases in Tableau. And

25:48let me know what you'd like me to talk

25:50about next week.

25:51I've got a couple of ideas. And there's one

25:54issue that really drives me out the wall.

25:56And that is

25:56hacks in Tableau. So I might talk about

25:58that next week. If you want to know more

26:00about that, let me

26:01know in the comments. But if there's

26:02anything else, this is the time this is

26:04your chance every Friday,

26:06I'm going to sit and talk to the camera

26:08about something. So this is your

26:09opportunity to sort

26:10of feed into that. So I'd love to hear your

26:12thoughts on what you'd like me to talk

26:14about.

26:14Thanks for watching. If you've enjoyed this

26:16, you know what to do. Otherwise,

26:18I'll catch you in the next video.