References Made on the Show
- Justin Cutroni
- Google Analytics IQ (GAIQ)
- Urchin acquisition by Google
- Lehr und Kunst
- Simo Ahava
- Da Vinci Tools
- Google Reader
- The First 90 Days (Book)
- Adam Greco’s Adobe Analytics Top Gun Training
- (Book) Dare to Lead: Brave Work. Tough Conversations. Whole Hearts. Hardcover – Brené Brow
- (Podcast) Episode 1012 – Brené Brown — WTF with Marc Maron
- Hans Rosling
- (Podcast) Not So Standard Deviations
- (Podcast Episode) #77 – Back to Statistics
- (Podcast Episode) #75 – Data Science Lite
- (Article) Managing Oneself — by Peter Drucker
[music]00:04 Announcer: Welcome to the Digital Analytics Power Hour. Tim, Michael, Moe, and the occasional guest, discussing digital analytics issues of the day. Find them on Facebook at Facebook.com/analyticshour. And their website analyticshour.io. And now, the Digital Analytics Power Hour. 00:27 Michael Helbling: Hi, everyone. Welcome to the Digital Analytics Power Hour, this is episode 116. You know, not many people can see it but there is this imperceptible line that you cross in a product’s life cycle where you have to make some decisions about how people are actually going to figure out how to use your product. You know when you’re a startup or you’re really small, you’re just trying to provide decent documentation at least, or hopefully, users figure things out on their own, but as you grow, you need to make sure people know how to use your product. It’s no different in the analytics space. I mean there’s a plethora of tools and technologies that we all use now, and knowing how to use them well can seem more than a little daunting. So that’s what we’re gonna talk about. Analytics education at scale. Hey Moe, you have a stand-out analytics education moment? 01:21 Moe Kiss: I do actually. It was so bad. It’s when I got my first job in digital analytics, and I had to pass the GAIQ exam and I thought that I spent like a day convincing myself I was gonna fail. And now I’m like, “Ugh, honestly.” 01:34 Tim Wilson: Wow, look at that. Kissing up to the guest. Well done. 01:38 MH: Okay, Tim. Hey, let me finish my intro. Tim. 01:41 MK: That was legit my first one. 01:43 MH: No. That was really good and I think Tim, you shouldn’t, you should treasure that experience.
[laughter]23:08 JC: Diatribe there from the word event. You switched from the word event to training. And events aren’t training. Training is training. And I think if you wanna go to training, it’s a very different thing than an event. Events are in my opinion marketing. 23:24 MK: Okay. 23:24 JC: Almost all the time. 23:25 MK: Okay, that’s very helpful. 23:27 TW: I think you can also look at who’s organizing it. It’s just based on the Google, on the cloud side. Like I went to an event that was around, I don’t know, it was like TensorFlow and Colab, like it was an event where they were marketing it but they also were very clear they were having a third-party speaker come in and walk through soup the nuts how they were doing something. I think it was a Colab project that they were walking through. I mean it was mostly over my head. So it was one where they were… It was marketing, but they were marketing to the machine learning, the developer crowd, and there was legitimate takeaway stuff. So I think it’s even… I think there can be events that based on who they’re targeting at the event can still wind up giving you something you can walk away with. 24:13 JC: Well, I mean, do you remember, I don’t know, I may be dating myself, but I remember 15 years ago when every vendor in the analytics space, they would have that classic marketing tool where you’d get a one-hour webinar and the first 30 minutes was like a deep dive expert thing and then the second 30 minutes was a vendor marketing pitch, right? 24:34 MK: Yeah. 24:34 JC: You’d have like, “Oh, here’s Expert X,” and talking about something technical, and then it’s like, “Oh, here’s our marketing team for 30 minutes.” 24:42 MK: But… 24:42 TW: I remember them as being flipped that it was like we’re gonna get to what you actually want, but first, you’re gonna have to… 24:47 JC: Yeah, yeah. Start with the PowerPoint and then do the demo after. 24:51 MH: And maybe that was it. 24:52 MH: But actually, our industry has to include education and marketing because we have to educate people on what to buy. So that’s a little different than more well-established professions that have been around for 100 years versus 25 like that. 25:07 JC: Well, I mean, are you… So are you talking… Are you talking about just like educating people about the industry and why they need to care about education, or care about like analytics or… 25:17 MH: No, like educating why you should care about this differentiated feature of our product and how it will affect your business, those kinds of things. So like there’s a function of education that is also marketing. 25:28 JC: Well, so that’s really interesting, right? Because I think that’s marketing, and one of the ways that I… 25:33 MH: Yeah, I agree. 25:33 TW: I agree. 25:34 JC: Yeah, I mean the way that I… ‘Cause I sit right next to our marketing teams because our marketing teams tell the why story. My team and education tells the how story. 25:45 TW: That’s a good way to think of it. 25:46 MH: Yeah, and that educating on our new features, to me, it’s marketing and you’re getting such a… You’re getting completely one-sided view of what the feature and the value and the benefits. So I hope people are going to those with a high degree of skepticism, not being like, “I heard one side educating me on what this awesome functionality is. I must go buy that.” I don’t know. 26:14 JC: Yeah, to me, it’s… And that’s the way I’ve been trying to draw the line and the content that we… The line in the sand that the content that we create is like our content is about the how. Now, in our how story, if we have an hour, we might have three minutes of why at the beginning, which I think is really important to set the context, but I think marketing’s job is really the why. They’re there to differentiate the feature, extol the feature, and we’re there to tell people why to push the buttons or the best way to push the buttons. 26:47 MK: But if there is a use case ’cause as you guys are talking about this, I’m like, “Wait, is that marketing?” I obviously have a totally uninformed opinion, if everyone else is agreeing, except me, but I always think about the context of a use case. If someone is like, “Here’s something that you can do, a piece of analysis that you’re interested in, and this feature will let you do it this way with these parameters,” and yada, yada, yada, that’s where I get the most value. It’s like, “Oh, now, here’s something I can go and do with this.” Or it’s something I can go back to my CMO and say, “Hey, this is why we need this tool because it will allow me to do this.” And so, I feel like it can be a blurry line. 27:24 JC: But it doesn’t tell you how to do it. If it doesn’t dive deep into the details and say like, “All right, well, first, you need to create a data connector. And then once you create the data connector, you need to drag this widget into the workspace. Then you need to apply the filter.” 27:41 MK: Oh no, I totally… I apparently want that, too. I’m like, “Now, tell me how to do it so that I can actually go and do it.” 27:47 JC: And I think that’s where education comes in. It’s the totally telling you how to do it. 27:51 MH: Okay, so what role does the community play for you in that? Because there is a huge community, and they’re… Up until recently, there was a massive Google Plus GA group that would share knowledge. Google then mercilessly… 28:08 TW: What happened to that Google Plus group? 28:09 MH: Cut down it’s… No, this is… 28:11 JC: I don’t work in that part of the business. 28:13 MH: Pour a little bit out for it. Rest in peace. But there’s also the Measure Slack today, which is becoming a place. And back in the old, old days, which we actually just realized, that still exists, is the Yahoo Web Analytics Forums back when we were all kids. Yeah, exactly, throwing it back. And then there is sort of the individual gravity well that is Simo Ahava in terms of the content that he produces and educates people on. There’s a whole, almost community around just his content. 28:42 MK: There is literally community around his content. 28:44 MH: Oh, yeah. So talk about that a little bit, the context of how you approached that because I think that’s also interesting for people who wouldn’t know how to balance or look for new opportunity, even. 28:53 JC: Yeah. Well, I think that’s… And I think any part… I think with an educational effort, it’s an ecosystem play. And so, obviously, we said there’s some standard stuff you need to do in order to support some very definite business objectives like reducing service costs. But the ecosystem play is great because it can handle a lot of those edge cases that Tim might have mentioned. So if there is a gray area that’s very unique, it may not get as much attention from the stuff that we create, but there’s a thirst for that. And especially a product like Google Analytics, there’s always been a very passionate user base, and that’s where the ecosystem of experts comes in and should be encouraged. And I know that for us, we make a conscious effort to share that content through our social channels to promote that content because it is good, valuable content that fits the needs of a certain segment of users. And for us, it’s very intentional that we promote that stuff that people are making, like Simo and lots of other folks out there. 30:04 TW: Well, even, if you take Jeff Sauer’s, the Jeffalytics, that it’s in… He’s actually delivering content in the same format. But presumably you’re saying, “Look, if it’s meeting a need that you guys aren’t meeting, but it drives them to use the product, then good on you.” 30:21 JC: Totally. From our perspective, someone signing up for Jeff’s courses is probably gonna have a very different experience. I don’t know the details, but I’m sure there’s a lot more interaction with Jeff. I’m sure there’s some type of a little bit more opportunity to answer questions or whatnot. That’s something that doesn’t really happen with our stuff just because of the scale of it and our ability to provide that type of experience. But at the end of the day, our goal, whether it’s our content or the ecosystem creating the content, is for people to push the buttons better. We want them to be successful in their jobs. And again, Google is more successful when people use our products better. If it’s Analytics, if it’s AdMob, if it’s part of the GMP like DV 360, that’s what we want. We want more educated users that use the products better because they’re gonna help the other side of the equation. The education will help better product usage, which in theory, should drive growth of our business. 31:24 MK: Okay, so just one thing, though, you have all these, I guess, advocates out there that are talking about the platform that are filling this need. It’s also really tough, though. What if they suggest stuff that you disagree with from a, I guess, “This is the best way to use the product,” or best practice… 31:42 TW: I don’t think Simo has ever recommended hacking the tool and maybe using it in a way that maybe it wasn’t exactly. That’s a good point. 31:49 JC: Nobody’s ever done that before. I don’t know anything about people… 31:52 MH: I mean, there’s whole products built on top, right, so Stephane Hamel Da Vinci tools, which changes the way the product works. 32:00 JC: Yep. Yeah, I know. Absolutely. And I think, again, ultimately we want people to do their jobs better, and so if people are using the product in different and unique ways, as long as they’re not breaking terms of service. As long as they’re not doing things that are against our relationship with that user, then that’s totally fine. If you’re storing first name, last name, e-mail address, in Google analytics, then we’re gonna be a little bit bent out of shape on that. But if you’re figuring out some way to create primary keys and store them in systems, and then join those in BigQuery, like good on you. 32:41 MH: So, if we’re talking various of these discussions, this probably goes back to when you were talking about the different forms. Online versus in person, different needs, and this whole topic which obviously is at its core, we’ll wind up, we’re focusing on the Google analytics ecosystem scale, but that easily broadens to other broader analytics products. But it’s occurring to me that it actually is equally applicable to enterprise analytics programs, and a lot of the thoughts, like I’ve watched and worked with companies that are saying, “Hey we’re rolling out this new platform.” And they figure out how they’re gonna train all the users at launch with putting 0.2% thought into how do we handle the person who starts and needs to use the tool a week later? How are we giving people a refresher? What about the people who sitting and watching a video isn’t gonna work, they need some hand-holding? And a lot of what we’re talking about here to me seems like wow, if you actually are a small group who’s rolling out a platform in the organization and it’s again possible, I’m thinking about one [chuckle] specific scenario right now, which this is really hitting home with me. 33:57 MH: That idea that you know what, you do need to deliver the same information through multiple channels, in an on-demand format, in a documentation format, in an in-person format, in a consultative format. Those are all fine. Trying to design, we’re going to… And even to the partners, the super users. Who in the organization is really jumped on board, they’re in one group that is one user, but they have become really engaged with it. How do you take advantage of them, as Evangelists, as pushing the tools, providing content. So, that was just a… Did not have that thought coming in to this discussion, but it seems like a hundred percent it applies. 34:40 JC: Yeah. I think I followed you, and I think kept with it.
[laughter]34:47 MH: Now you’ve had the true analytics power hour experience. 34:51 JC: I think I may have even convinced you of something, but yeah. I mean, there are some… Obviously it depends on the size of your company, right? And again, what are your objectives? And so, big global corporations, like their go to market teams will probably think a lot about education. Product… 35:10 TW: They should. 35:11 JC: They should. Like, they should be. 35:13 TW: Right I mean, a lot more, it’s like hey we bought the tool, we implemented it, and we’re already are over budget and a little extended on our timeline, so we’re done. Why are insights not emerging? Because they didn’t. But, that was the cynical Tim. 35:26 JC: Oh, really? Cynical Tim exists? I didn’t… 35:28 MH: Tim educates out of frustration usually.
[laughter]35:37 JC: I know exactly what you mean. It’s like, I’ve had many of those moments. 35:42 MK: Yeah, but it’s funny actually. Because this has been coming up quite a bit. As we talk about, I guess, how do you immobilize people within an organization, get them to pick up a tool, whatever it is. As we see the transition from data warehouse to data lake, one of the conversations that I’ve also been privy to, which I’ve found pretty frustrating, is the, “Oh, we’re gonna put everything in a data lake, so therefore we don’t need to document.” The idea is that everyone in the business learns it inside-out, and back to front by playing around and getting stuck into it, and so documentation is a waste of time. And I recoiled with shock horror, because why would you have someone play around for three hours to figure out what a particular metric is? 36:26 JC: Some people don’t learn that way. Some people don’t learn by playing around. That’s not their modality. They learn by sitting down and reading a book. 36:34 MK: Yes. So okay, great. Now I feel justified. This is good. I’m still on the I do believe in documentation, but… Yeah. I’ve been part of some very heated discussions. 36:44 TW: You’re okay with putting comments in code as well? ‘Cause you had that brief tangent where you were saying that was the new thing too, was if your code’s written well enough. 36:51 MK: The new thing is to have no comments in code, because your code should be good enough that anyone reading it can figure out what you’re doing. I believe in comments in code. Well ’cause what if you’re the new person? How the hell are you meant to learn if you don’t know what that thing is yet? You’re gonna go, you’re gonna look it up? 37:06 MH: But that does bring up something, and I wanna change gears a little bit, to make this a little more closer to home. So, oftentimes, at least in my experience and other people, you are dealing with people who are brand new to our industry, and let’s paint that in a broad way. Not just digital analytics, but even some of the other areas that you even functionally cover within the world of Google, and things like that. Coming directly out of college, perhaps. Or in a couple of cases, even had people coming from different careers, and making the switch over. If you were saying to… Sitting next to a person like that today Justin, what advice would you give them about how to shape their educational path as it pertain to… You can keep it within the world of Google if you want, or you can go more broadly in terms of analytics today. Where would you… How would you assess, and then create a plan for them? 38:02 JC: Ah, man. Now I’m creating personal learning plans for people. I wasn’t expected to do that on a Tuesday night. 38:08 MK: Yeah, but the thing, I’ve already figured out my next event/training session, and what I should go to and what I should say no to, so this is super helpful. 38:16 TW: Justin, just tell them to reach out to you on Google+, and you will give them a personal learning plan. 38:21 JC: My hourly billing rate is under four figures, so… 38:23 TW: Subscribe to my blog on Google Reader, and you’ll see. And then connect with me on Google Plus and it’ll be free, it’ll be a free personal learning plan. 38:33 JC: So I guess, I think speaking about analytics specifically, if I was in a job, the first thing that… One of my favorite books is the first 90 days. I don’t know if anyone’s ever read that, The first 90 days. Good book to read if you ever get a new manager or if you ever start a new job. And it’s basically, “Make sure you know what your boss wants.” [chuckle] That’s the gist of it. But if I was in a new job, new in analytics, I would first of all get a clear understanding of what is expected of me from my boss like what do they expect me to do? And then I would start to figure out like, “Okay what do I need to know in order to do that?” And in my looking back through everything that I’ve done, I would always start on the business side of things. And I always start to think about like, “Alright, how does this expectation that he has of me… How does that fit into the business?” So if I’m a new analyst and I’m doing something measurement-related he’s gonna ask me for some data or some insights, and I’m gonna wanna have a super clear understanding of like, “How does that make him look good? How does that help him do his job? 39:38 MK: Or her. 39:39 JC: Or her. Sorry, thank you very much. And I would also understand the organizational layout. So, how does my boss, how does she interact with her peers in order to have the business be more successful? And then I would start to dig into, “Alright, how do I solve these problems? How do from an analytics perspective, if it’s a tool, how do I get this tool to work for me?” And I would look at lots of different sources of information. I think, again, everyone should know how they learn. I’m a tinkerer, I like to play with stuff. I get a very high level overview, and then I’m like, “Let me kill myself with this thing, let me shoot myself in the foot,” and I wanna play with stuff. So I would go down that path. Someone else might sign up for an online course, someone else might sign up for specific training. Adam’s training or something if they’re using one of Adobe’s tools. But I think I would tie everything back to what is expected of me, what do I have to deliver. And then more importantly, like how do I get that done? 40:44 MH: Oh I think that’s good, ’cause I think you said a couple of things that really stood out to me in that actually some of the highest priority things were actually more soft skill-focused than hard skill-focused in terms of how you might approach that. So I think that’s pretty interesting Tim that not just hard skills are important, yeah. 41:05 TW: Can we talk about emotional intelligence for a little bit? 41:08 MH: Oh. 41:09 MK: Okay, I do have one more tangent I wanna go down before we finish off. 41:14 MH: You are on thin ice Moe. You go, we’ve got maybe a few more minutes. 41:21 MK: Okay, so I was listening to a podcast the other day, and one of the things that they were talking about was open-source and how open source is incredibly difficult to maintain. One of the issues is documentation. I suppose, just as someone that works in this space what do you think is the path forward for Open Source? Because listening to it, it was like only people that are super new and motivated are really gonna be able to contribute to open source, and eventually it gets to a point where all of the experts are so busy with their high-paying super amazing jobs that they don’t have the time or the will. And the maintenance is really tough. And I suppose I’m just curious to hear your perspective about where you think that fits in because, obviously we’re talking about Google has heaps of resources, but for those open source tools there often isn’t any. 42:11 JC: Yeah, and I think… And I’m just riffing off the cuff here, but if I had to take a guess, I would say anyone getting involved with open source code is probably a developer or probably pretty technical, and I think that’s an area where… 42:29 TW: Or a mess because they were recovering analysts maybe? 42:34 JC: That might be it, right, yeah exactly. But I think that’s where… A spot where like… We were talking about developers, and developers going right to the really hardcore documentation. I think the open source community in general tends to be technically adept. And so, would it be great if there was really good documentation or other educational stuff? Sure but does the audience actually need it? Maybe not, and then maybe even go on one step further, like what’s the business objective of open source? It’s not really there to make a ton of money, it’s not really there… They’re not really worried about their support costs they’re worried about the project growing, getting adopted getting implemented, getting used. And again, the audience that’s gonna do that probably can figure it out. 43:28 MK: Yeah that’s fair, that’s fair. I just always wonder like how closely is adoption tied to some type of education, whether that is documentation or learning? Like to grow, is that necessary? 43:39 JC: Yeah, so that’s an awesome question. And that’s actually how we measure some of our education. One of the things that I’ve pushed the team to do over the last three years is literally create attribution models so that we can understand, “Okay if someone reads a piece of documentation watches a video or take a course here and then they enable a feature seven days, 10 days, 30 days later. We actually think about our success in education based on those types of attribution models and so, I absolutely think that feature adoption and configuration is something that you should measure as part of your education program. And it’s all on that side of driving usage and revenue in the business versus obviously the whole save the money part. 44:24 MH: All right, we do have to start to wrap up, but this has actually been really an awesome conversation. Maybe ’cause you’re an awesome guy. I don’t know, it’s weird. 44:34 JC: Oh, were you talking to Tim? You’re talking to Tim.
[laughter]44:38 MH: But one thing we do like to do on the show is what we call Last Call. We go around the horn and talk about something we’ve found that’s interesting that might be interesting to others. So, Justin, you’re our guest, do you have a last call you wanna share? 44:51 JC: Yeah, so my journey… Like, I’m basically management now, which is fun, scary and all sorts of things. And, as a manager and a leader, one of the things that I’ve embraced a lot is vulnerability and the works of Dr. Brene Brown. She writes a lot about… 45:09 MK: That was just it. She’s on Netflix now. She’s famous. 45:13 JC: I was a fan boy way before Netflix, so… 45:16 TW: So are Moe and Michael, ’cause I was like, “She’s on WTF with Marc Maron.” I know that name. Who is she? I’m like, “Oh.” 45:22 JC: No, no. Way before, with the TED Talks, like way before, way before. So, I think, her latest book, Dare to Lead, is great. If you are management or if you’re in a position of leadership, if you have a team, or if you ever interact with other human beings, it’s a lot of good stuff in there. 45:41 MK: I actually just finished it. And one of the things that I most like about it is the fact… And I think maybe this is the mistake that people have about vulnerability, just being honest about everything is not being vulnerable. And I think that the way that she describes it is actually really valuable, especially for someone like me, who is really honest. 46:00 TW: So, my deepest exposure to her was listening to the recent episode of her on Marc Maron, who, he’s funny ’cause he is… It was not a typical guest of his, and I literally went through the whole thing, and she is delightful and hilarious, and I am not following this at all, which either means that I am deceiving myself, or I’m a sociopath. 46:21 JC: Well, so here’s one more thing. All of her stuff comes from data. She’s done years and years and years of research to understand this stuff. So, even if you’re like, “Oh that’s bull crud. I don’t buy vulnerability.” 46:39 MK: Yeah. 46:40 JC: There’s data. 46:41 MH: No, no, no, but… 46:42 JC: There’s data, Tim. Data, Tim. 46:44 MH: Data, Tim. 46:45 MK: Data. 46:49 TW: To be clear, I’m not saying whatever she’s saying is not right or wrong. I’m just like, huh? 46:55 MK: This makes me awkward. 46:57 TW: It’s like… 46:57 JC: It’s just that Tim does not seek to benefit in that way in his life. 47:01 MH: Or maybe… Maybe if we put it into some type of chart, maybe a pie chart for you, Tim. 47:06 TW: Jeez. 47:08 TW: This guy is full of great ideas. 47:09 JC: Actually, you know what, Tim? I’m sorry. I know pie charts are old. We’ll make it the donut.
[laughter]47:15 TW: There you go. 47:15 MH: Wow. 47:16 JC: Because the donut is so much better. 47:18 TW: But as a tribute to Hans Rosling, can we make it a donut that then moves over time? 47:22 JC: Yes, as long as there are at least five, we’ll make it a 3D donut that also moves through space and time so we can have five… 47:29 TW: Do not disparage the memory of Hans Rosling by trying to bring in a pie chart into what the genius that was. 47:37 JC: Or Google tie-in. Motion charts. 47:39 TW: Anyway, may he rest in peace. 47:42 MH: Okay, well, bring it back around. 47:46 MK: Okay, I’ve got a solid one, team. So, I’ve started listening to another podcast called Not So Standard Deviation. It’s by Hillary Parker of Stitch Fix, and Robert Peng, who was a university professor and I can’t remember the university, but it’s very famous. 48:02 MH: He’s at John Hopkins, I think. I got my one hour Coursera course was Roger Peng, I believe. Yeah. 48:06 MK: Yeah, yeah. Same. Same. Anyway, so there’s two episodes that I’ve listened to that I recommend. One, back to statistics. They spent a whole episode on statistical significance, whole episode, good hour. I’m honestly impressed that you could talk about it for an hour, but also learn some stuff. 48:25 TW: I’m wondering when you say good hour. I wondered, which meaning of, that it was for an entire solid hour. Okay, it was good. 48:32 MK: And I was like, they were talking about that one idea for an hour, that’s what impressed me. And the level of detail, which was actually very good. The second episode, which was episode 75, which is called Data Science Light. I do preface this though, by skip to minute 19 and 35 seconds ’cause the first 19 minutes, they’re talking about milk, which is weird, but after that, after minute 19, they’re actually talking about maintaining open source stuff, which is what I alluded to before. And basically if you’ve contributed to R packages, how do they get maintained, what if there are dependencies or the packages, all that sort of stuff, which I also found super interesting. So, Not So Standard Deviation is my listen for the week. 49:15 MH: My last call is a booklet I recently read. It’s not really a book, it’s a booklet. So there’s this guy, a lot of people know who Peter Drucker is, but we’re now at a time where most have forgotten. And there’s this little booklet. I think it was a reprint of an article he wrote called “Managing Oneself” which is a really easy read. It’s probably something you could read over your lunch break. It’s really, really short. 49:41 MH: In it, he covers a bunch of different things that are great sort of starting points. So I highly recommend it. It will actually lead you probably to a number of other Peter Drucker type books. But that book was a nice easy way to kind of surface what I would call key topical areas that Drucker felt like were really important. And it really resonated with me because. Like you Justin, not in the exact same way, but having become a leader over the years, and having to try to grow myself, you’re always looking for ways to give yourselves paths to develop and grow. So that book was very helpful. So, I don’t know. Drucker is a little bit strange. He definitely has some older ideas. After I read through a book with a couple of co-workers where it was pretty obvious in that book. He didn’t think women would be in business, so it was sort of like, “This guy should do this,” and I was like… Or girl, like, “What are you talking about?” So anyways, different time. Good book, take it for what it is. Alright, so that’s our last calls. As you’ve been listening and waiting for us to get through our last calls, you’ve probably have been thinking about a number of things or questions or ideas or comments, or educational material that you wish Google would come out with, and this is your chance, so we’d love to hear from you. 51:03 MH: Probably the best way to get in touch with us is through the Measure Slack or on our LinkedIn page, or on Twitter. I don’t know to what extent, Justin, you’re our active on Twitter, or at all, but if you know his Twitter account, you could try to reach out to him that way. 51:18 JC: It’s just my name, I have a Twitter account, it’s active. Unless, I don’t think they’ve kicked me off yet. 51:23 MH: See, there you go. But probably the best way to talk to Justin is through the wonderful people that work across Google as part of a team. But we would love to hear from you, love to hear your thoughts, so please reach out to us. Justin, thank you so much for taking the time to come on the show. It’s been a pleasure to have you. 51:42 JC: Thanks everybody, This was super fun. It was really good to catch up and I really enjoyed our discussion. 51:47 MK: Ditto. 51:48 MH: Awesome. Well I know that I speak for both of my co-hosts, Tim and Moe, when I encourage all of you out there, no matter how you learn, that as you learn, you keep analyzing.
[music]52:03 Announcer: Thanks for listening and don’t forget to join the conversation on Facebook, Twitter, or Measure Slack Group. We welcome your comments and questions. Visit us on the web at analyticshour.io, Facebook.com/analyticshour, or at Analytics Hour on Twitter. 52:23 TW: Smart guys want to fit in, so they’ve made up a term called analytics. Analytics don’t work. 52:30 MH: Analytics, oh my God, what the fuck does that even mean? 52:39 JC: If I still cared about that, that would be something I would use later [chuckle] 52:45 MH: So you don’t want me to talk about how Jeff Goldblum was driving across the desert with the school children trying to get away from Thanos? 52:53 MH: I will not sit here and have you malign our guests, Tim. 52:58 MK: I can’t believe that’s the thing kids do now. In my days, we were trying to smuggle booze and stuff. 53:06 MH: I have a very structured way of thinking, so I’ve really honed the way I think. And so any information that’s not necessary or mandatory, I completely move it right out. 53:16 MK: But I think knowing that I’m a Zennial is actually mandatory. 53:19 MH: Yeah, obviously it didn’t make the cut. 53:22 TW: Now that I work with them, though, I realize that he makes the decision very quickly and he gets a lot of type one and type two errors go through that filter. 53:31 MH: Oh yeah, a lot. 53:34 TW: We use this thing called Google Docs. I don’t know if you’re familiar with one of the nice benefits of it? 53:39 MH: Yeah, I really think it’s gonna catch on actually. A lot of companies will start using it someday. 53:45 MH: I think Jim gets annoyed with things like rainy days and everything [chuckle] 53:51 MK: Crackle, crackle, crackle, pop, pop, pop. Snap, snap. I was thinking. I was like, “There’s definitely a third one and I’m missing it.” Oh shit. 54:04 MH: I was so confused and probably our listeners are too. I have no idea, Tim. 54:10 TW: Okay. 54:10 MK: Oh, just throw out a guess. 54:14 TW: The whole episode I’ve been Googling. I thought it was Latin and it turns out it’s actually German. 54:18 MK: I knew it was German. 54:19 MH: I did say it was German. 54:20 MK: You should have been listening instead of Googling. My personal motto is “Chutzpah”. 54:25 TW: Is that Latin? 54:27 MK: I love that that’s where your mind went. Not like, “Oh, interesting.” 54:33 MH: I like that you can hold a conversation and search the internet at the same time, for German phrases that are also college mottos. 54:40 MK: He’s got mad skills, mad skills. 54:42 MH: I’m having trouble just sitting.