Podcast appearances and mentions of chris fair

The latest edition of America's Top Cities is out today and DMOU had the opportunity to talk with Resonance's Chris Fair on how the rankings are determined and why they matter. It's no surprise that big cities dominate the top 50 because they have more assets than smaller cities. But, there are some surprising cities in the bottom 50 that point the way to how DMOs can elevate community brand and magnetism to increase awareness and interest. Chris breaks it all down in this exclusive interview on how the rankings have evolved post-COVID. Cool stuff.

Time now to chat fitness, David Hogg caught up with VI Personal Trainer Chris Fair to hear about his sight loss, his CrossFit journey and an upcoming documentary.

Raji Sohal, CKNW contributor interviewed Chris Fair, CEO Resonance Co. Consultancy

Chicago is ranked number 13 on bestcities.org‘s latest report showing the top 100 world’s best cities of 2021. President and CEO of Resonance, Chris Fair, joins Lisa Dent, filling in for John Williams, to dive deeper into how these rankings come about and why Chicago is ranked at number 13. The Resonance is a leading […]

Chicago is ranked number 13 on bestcities.org‘s latest report showing the top 100 world’s best cities of 2021. President and CEO of Resonance, Chris Fair, joins Lisa Dent, filling in for John Williams, to dive deeper into how these rankings come about and why Chicago is ranked at number 13. The Resonance is a leading […]

Ep 352 - Can Granville St be Re-Imagined? Guest - Chris Fair   Granville Street – at least the part of it that is within the downtown area – was redesigned in 1974 and it was “supposed to reflect Vancouver's unique identity, character and sense of place,” according to Heritage Vancouver.    The street, unfortunately, is a mishmash of planning over the decades that don't always work as well as hoped for. And let's face it, the street is supposed to be a pedestrian mall where people want to be. They want to eat, shop, and be entertained in a lively and friendly space.   One element of a pedestrian mall is to be pedestrian. Granville Street is kinda pedestrian and kinda not. It's really a transportation corridor that begrudgingly accommodates foot traffic and cyclists along with hundreds of buses and taxis and police cars. In other words, it is not even close to a true pedestrian mall.   The Downtown Vancouver Business Improvement Association says, “It's sorta working but with adjustments, it can be fantastic. We did it in 2010 for the Olympics and it was great. Let's do it again.” To that end, DVBIA hired Resonance Consultancy to re-imagine Granville Street. The company is a Vancouver success story – the team has worked with huge international players who sought to and accomplished stunning upgrades and turnarounds around the world.   Stuart McNish invited Chris Fair, the CEO and the 2013 Place Brand Thought Leader, to join him for a Conversation That Matters about Re-Imagining Granville Street.   Please become a Patreon subscriber and support the production of this program, with a $1 pledge https://goo.gl/ypXyDs 

On this week's episode, Steph and Chris respond to a listener question about how to know if we're improving as developers. They discuss the heuristics they think about when it comes to improving, how they've helped the teams they've worked with plan for and measure their growth, and some specific tips for improving. Rails Autoscale (https://railsautoscale.com/) Rubular regex playground (https://rubular.com/) The Pragmatic Programmer (https://pragprog.com/titles/tpp20/the-pragmatic-programmer-20th-anniversary-edition/) Go Ahead, Make a Mess by Sandi Metz (https://www.youtube.com/watch?v=xi3DClfGuqQ) Confident Code - Avdi Grimm (https://www.youtube.com/watch?v=T8J0j2xJFgQ) Therapeutic Refactoring - Katrina Owen (https://www.youtube.com/watch?v=J4dlF0kcThQ) Refactoring, Good to Great - Ben Orenstein (https://www.youtube.com/watch?v=DC-pQPq0acs) Transcript CHRIS: There's something intriguing about the fact that we're having this conversation, but the thing that's recorded just starts at this arbitrary point in time, and it's usually us rambling about golden roads. But, I don't know; there's something existential about that. STEPH: It's usually when someone says something very funny or starts singing [laughs], and then that's when we immediately: record, record! CHRIS: I've never sung on the mic. That doesn't sound like a thing I would do. STEPH: [laughs] CHRIS: Hello and welcome to another episode of The Bike Shed, a weekly podcast from your friends at thoughtbot about developing great software. I'm Chris Toomey. STEPH: And I'm Steph Viccari. CHRIS: And together, we're here to share a bit of what we've learned along the way. So Steph, how's your week going? STEPH: Hey Chris, it's going really well. Normally I'm always like, wow, it's been such an exciting week, and it's been a pretty calm, chill week. It's been lovely. CHRIS: That sounds nice actually in contrast to the "Well, it's been a week," that sort of intro of "I don't know, it's been fine. It can be really nice." STEPH: By the time we get to this moment of the week, I either have stuff that I'm so excited to talk about and have a little bit of a therapy session with you or share something new that I've learned. I agree; it's nice to be like, yeah, it's been smooth sailing this whole week. In fact, it was smooth sailing enough that I decided to take on something that I've been meaning to tackle for a while but have just been avoiding it because I have strong feelings about this, which you know but we haven't talked about yet. But it comes down to managing emails and how many emails one should have that are either unread that are just existing. And I fall into the category of where I am less scrupulous about how many unread or managed emails that I have. But I decided that I'd had enough. So I used a really nice filter in Gmail where I said I want all emails that are before 2021 and also don't have a user label, so it's has:nouserlabels because then I know those are all the emails that I haven't labeled or assigned to a particular...I want to say folder, but they're not truly folders; they just look like folders. So they're essentially like untriaged or just emails that I've left hanging out in the ether. And then I just started deleting, and I got rid of all of those that hadn't been organized up until that point. And I was just like yep, you know if I haven't looked at it, it's that old, and I haven't given a label by this point, I'm just going to move on. If it's important, it will bubble back up. And I feel really good about it. CHRIS: Wow, that is -- I like how you backed me into a corner. Obviously, I'm on the other side where I'm fastidiously managing my email, which I am, but you backed me into that corner here. So, yeah, that's true. Although the approach that you're taking of just deleting all the old email that's a different one than I would have taken [chuckles] so, I like it. It's the nuclear option. STEPH: Okay, so now I need to qualify. When you delete an email, initially, I'm thinking it's going to trash, and so it's still technically there if I need to retrieve it and go back and find it. But you just said nuclear option, so maybe they're actually getting deleted. CHRIS: They're going into the trash for 30 days; I think is the timeline. But after that, they will actually delete them. The archive is supposed to be the place where you put stuff I don't want to see you anymore. But did you archive or delete? STEPH: Oh, I deleted. CHRIS: Oh, wow. Yeah. All right, you went for it. [laughter] STEPH: Yeah, and that's cool. And it's in trash. So I basically have a 30-day window where I'm like, oh, I made a mistake, and I need to search for something and find something and bring it back into my world; I can find it. If I haven't searched for it by then in 30 days, then I say, you know, thanks for the email, goodbye. [chuckles] And it'll come back if it needs to. CHRIS: I like the approach. It would not be my approach, but I like the commitment to the cause. Although you still have...how many emails are still in your inbox now? STEPH: Why do we have to play the numbers game? CHRIS: [laughs] STEPH: Can't we just talk about the progress that I have made? CHRIS: What wonderful progress you've made, Steph. [laughter] Like, it doesn't matter what I think. What do you think about this? Are you happy with this? Does this make you feel more joy when you look into your email in the Marie Kondo sense? STEPH: It does. I am excited that I went ahead and cleared all this because it just felt like craft. So I have taken what may be a very contentious approach to my email, where I treat it as this searchable space. So as things come in, I triage them, and I will label them, I will star them. I will either snooze them to make sure I don't miss the high actionable emails or something that's very important to me to act on quickly. But for the most part, then a lot of stuff will sit in that inbox area. So it becomes like this junk drawer. It's a very searchable junk drawer, thanks to Google. They've done a great job with that. And it feels nice to clear out that junk drawer. But I do have such an aversion to that very strong email inbox zero. I respect the heck out of it, but I have an aversion; I think from prior jobs where I was on a team, and we could easily get like 800 emails a day. My day all day was just triaging and responding to emails and writing emails. And so I think that just left a really bitter experience where now I just don't want to have to live that life where I'm constantly catering to what's in my inbox. CHRIS: That's so many emails. STEPH: It was so many emails. We were a team. It was a team inbox. So there were three of us managing this inbox. So if someone stepped away or if someone was away on vacation, we all had access to the same emails. But still, it was a lot of emails. CHRIS: Yeah, inbox zero in a shared inbox that is a level that I have not gotten to but getting to inbox zero and actually maintaining that is very much a labor of love and something that I've had to invest in. And it's probably not worth it for most people. You could convince me that it is not worth it for me, that the effort I'm putting in is too much effort for not enough reward. Well, it's one of those things where I find the framing that it puts on it, like, okay, I need to process my email and get it to zero at least once a day. Having that lens makes me think about email in a different way. I unsubscribe from absolutely everything. The only things that are allowed to come into my email are things that I will act on that actually deserve my attention, and so it forces that, which I really like. And then it forces me to think about things. I have a tendency to really hold off on decisions. So I'm like, ah, okay. I can go see friends on Saturday or I can do something else. Friends like actual humans, not the TV show, although for the past year, it's definitely more of the TV show than the real people. But let's say there's a potential thing that I could do on the weekend and I have to decide on that. I have a real tendency to drag my feet and to wait for some magical information from the universe to help this decision be obvious to me. But it's never going to be obvious, and at some point, I just need to pick. And so for inbox zero, one of the things that comes out of it for me is that pressure and just forcing me to be like, dude, there's no perfect answer here, just pick something. You got to just pick something and not wasting multiple cycles rethinking the same decision over and over because that's my natural tendency. So in a way, it's, I don't know, almost like a meditative practice sort of thing. There's utility there for me, but it is an effort, and it's, again, arguably not worth it. Still, I do it. I like it. I'm a fan. I think it's worth it. STEPH: I like how you argued both sides. I'm with you. I think it depends on the value that you get out of it. And then, as long as you are effective with whichever strategy you take, then that's really what matters. And I do appreciate the lens that it applies where if you are getting to inbox zero every day, then you are going to be very strict about who can send you emails about notifications that you're going to receive because you are trying to reduce the work that then you have to get to inbox zero. So I do very much admire that because there are probably -- I'm wasting a couple of minutes each day deleting notifications from chats or stuff that I know I'm not necessarily directly involved in and don't need action from me. And then I do get frustrated when I can't adjust those notification settings for that particular application, and I'm just subscribed to all of it. So some of it I feel like I can't change, and then some of it, I probably am wasting a few minutes. So I think there's totally value in both approaches. And I'm also saying that to try to justify my approach of my searchable inbox. [laughs] CHRIS: There are absolutely reasons to go either way. And also, to come back to what I was saying a minute ago, it may have sounded like I'm a person who's just on top of this. I may have given that impression briefly. I think the only time this has actually worked in my life is when Gmail introduced snooze both in the mobile app and on the desktop. So this is sometime after Google's inbox product came out, and that was eventually shut down. So it's relatively recent because, man, I just snooze everything. That is the actual secret to achieving inbox zero, just to reach the end of the day and be like, nah, and just send all the emails to future me. And then future me wakes up and is like, "You know, it's first thing in the morning. I got a nice cup of coffee, and this is what you're going to do to me, past me?" So there's a little bit of internal strife there within my one human. But yeah, the snoozing is actually incredibly useful and probably the only way that I actually get things done and the same within any task management system that I have; maybe future me will do this. STEPH: I think you and I both subscribed to the that's a future me problem. We just do it in very different ways. But switching gears a bit, how's your week been? CHRIS: It's been good, pretty normal, doing some coding, normal developer things. Actually, there's one tool that I was revisiting this week that I'm not sure that we've actually talked about on the show before, but it's Rails Autoscale. Have you used that before? STEPH: I don't think I have. It sounds very familiar, but I don't think I've used it. CHRIS: It's a very nice, straightforward Heroku add-on that does exactly what you want it to do. It monitors your web and worker dynos and will scale up. But it uses a different heuristic than -- So Heroku has built-in autoscaling, but theirs is based on response time, which is, I think, a little bit laggier of a metric. Like if your response time has gotten bad, then you're already in trouble, whereas Rails Autoscale uses queue time. So how long is a request waiting before? I think it's at the Heroku router; it goes onto the dyno that's actually going to process the request? So I think that's what they're monitoring. I may be wrong on that. But from the website, they're looking at that, and you can configure it. They actually have a really nice configuration dashboard for configure between this range, so one to five dynos at most, and scale in this way up and in this way down. So like, how long should it wait? What's the threshold of queue time? Those sorts of things. So they have a default like just do the smart thing for me, and then they give you more control if your app happens to have a different shape of data, which is all really nice. And then I've been using that for a while, but I recently this week actually just turned on the worker side. And so now the workers will autoscale up and down as the Sidekiq queue -- I think for the Sidekiq side, it's also the queue time, so how long a job sits in the queue before getting picked up. And there are some extra niceties. It can actually infer the different queue names that you have. So if you have a critical, and then a mailer, and then a general as the three queues that Sidekiq is managing, you really want critical to not back up. So you can tell it to watch that one but ignore the normal one and only use -- Like, when critical is actually getting backed up, and all the other stuff is taken over then -- Again, it's got nice knobs and things, but mostly you can just say, "Turn it on and do the normal thing," and it'll do a very smart thing." STEPH: That does sound really helpful. Just to revisit, so Heroku for autoscaling, when you turn that on, I think Heroku does it based on response times. So if you get into a specific percentile, then Heroku is going to scale up for you to then bring down that response time. But it sounds like with this tool, with Rails autoscaling, then you have additional knobs like the Sidekiq timing that you'd referenced. Are there some other knobs that you found really helpful? CHRIS: Basically, there are two different sides of it. So web and background jobs are going to be handled differently within this tool, and you can actually turn them on or off individually, and you can also, within them, the configurations are specific to that type of thing. So for the web side, you have different values that you can set as the thresholds than you do on the Sidekiq side. Overall, the queue name only makes sense on the Sidekiq side, whereas on the web side, it's just like the web requests all of them 'Please make sure they're not spending too much time waiting for a dyno to actually start processing them.' But yeah, again, it's just a very straightforward tool that does the thing that it says on the tin. I enjoy it. It's one of those simple additions where it's like, yeah, I think I'm happy to pay for this because you're just going to save me a bunch of money every month, in theory. And actually, that side of it is certainly interesting, but more of my app will be responsive if there is any spike in traffic. There's still plenty of other performance things under the hood that I need to make better, but it was nice to just turn those on and be like, yeah, okay. I think everything's going to run a little better now. That seems nice. But yeah, otherwise, for me, a very straightforward week. So I think actually shifting gears again, we have a listener question that we wanted to chat about. And this is one that both of us got very interested to chat about because there's a lot to this topic, but I'm happy to read it here. So the overall topic is improving as a developer, and the question goes, "How do you know you're improving as developers? Is your improvement consistent? Are there regressions? I find myself having very different views about code than I did even a year ago. In some cases, I write code now in a way that I would have criticized not too long ago. For example, I started writing a lot more comments. I used to think a well-named variable obviated the need for comments. While it feels like I'm improving, I have no way of measuring the improvement. It's only a gut feeling. Thanks. Love the show." And this comes from Tom. Thank you, Tom. Glad you enjoy the show. So, Steph, are you improving as a developer? STEPH: I love this question. Thanks, Tom, for sending it in because it is one that I think about but haven't really verbalized, and so I'm really excited to dive into this. So am I improving as a developer? It comes down to, I mean, we first have to talk through definitions. Like, what does it mean to become a better developer? And then, we can talk through metrics and understanding how we're getting there. I also love the other questions, which I know we'll get to. I'm just excited. But are there any regressions? And also, in my mind, they already answered their own question. But I'm getting ahead of myself. So let me actually back up. So how do you know you're improving as a developer? There are a couple of areas that come to mind. And for me, these are probably more in that space of they still have a little bit of a gut feeling to them, but I'm going to try hard to walk that back into a more measurable state. So one of them could be that you're becoming more comfortable with the work that you're doing, so if you are implementing a new email flow or running task on production or writing tests that become second nature, those types of activities are starting to feel more comfortable. To me, that is already a sign of progress, that you are getting more comfortable in that area. It could be that time estimates are becoming more accurate. So perhaps, in the beginning, they're incredibly -- like, you don't have any idea. But as you are gaining experience and you're improving as a developer, you can provide more accurate estimates. I also like to use the metric of how many people are coming to you for help, not necessarily in hard numbers, but I tend to notice when someone on a team is the person that everybody else goes to for help, maybe it's just on a specific topic, maybe it's for the application in general. But I take that as a sign that someone is becoming very knowledgeable in the area, and that way, they're showing that they're improving as a developer, and other people are noticing that and then going to them for help. Those are a couple of the ones that I have. I have some more, but I'd love to hear your thoughts. CHRIS: I think if nothing else, starting with how would we even measure this? Because I do agree it's going to be a bit loose. Unfortunately, I don't believe that there are metrics that we can use for this. So the idea of how many thousand lines of codes do you write a month? Like, that's certainly not the one I want to go with. Or, how many pull requests? Anything like that is going to get gamified too quickly. And so it's really hard to actually define truly quantifiable metrics. I have three in mind that scale the feedback loop length of time. So the first is just speed. Like, how quickly are you able to do the same tasks? So I need to build out a page in Rails. I need a route; I need a controller. I need a feature spec, those sort of things. Those tasks that come up over and over: are you getting faster with those? That's a way to measure. And there's an adage that I think comes from biking, professional cycling, that it never gets any easier; you just go faster. And so the idea is you're doing the same work over time, but you just get a little bit faster, and you're always trying that edge of your capabilities. And so that idea of it never gets any easier, but you are getting faster. I like that framing. We should be doing the same work. We should never get too good for building a crud app. That's my official stance on the matter; thank you very much. But yeah, so that's speed. I think that is a meaningful thing to keep an eye on and your ability to actually deliver features in a timely fashion. The next one would be how robust are the things that you're building? What's the bug count? How regularly do you have to revisit something that you've built to change it, to tweak it either because it doesn't exactly match the intent of the feature that you're developing or because there's an actual bug in it? It turns out this thing that we do is very hard. There are so many moving pieces and getting the design right and getting the functionality just right and handling user input, man, that's tricky. Users will just send anything. And so that core idea of robustness that's going to be more on a week scale sort of thing. So there's a little bit of latency in that measure, whereas speed that's a pretty direct measure. The third one is…I don't know how to frame this, but the idea of being able to revisit your code either yourself or someone else. So if you've written some code, you tried to solve a problem; you tried to encode whatever knowledge you had at the given time in the code. And then when you come back three months later, how easy is it to revisit that code, to change it, to extend it either for yourself (because at that point you've forgotten everything) or for someone else on the team? And so the more that you're writing code that is very easy to extend, that is very easy to revisit and reload that context into your head, how closely the code maps to the actual domain context I think that's a measure as well that I'm really interested in, but there's the most lag in that one. It's like, yeah, months later, did you do a good job? And so the more time you spend, the more you'll have a measure of that, but that's definitely the laggiest of the measures that I have in mind. STEPH: I love that adage that you shared that it never gets easier, but you get faster. That feels so relevant. I really like that. And then I hadn't considered the robustness. That's a really nice one, too, in terms of how often do you have to go back and revisit issues that you've added? CHRIS: You just write code without bugs; that's why you don't think about it. STEPH: [laughs] Oh, if only that were true. CHRIS: Yeah, if only that were true of any of us. STEPH: To keep adding to the list, there are a couple more that come to mind too. I'd mentioned the idea that certain tasks become easier. There's also the capability or the level of comfort in taking on that new, big, scary, unknown task. So there is something on the Teams' board where you're like, I have no idea how to do that, but I have confidence that I can figure it out. I think that is a really big sign that you are growing as a developer because you understand the tools that'll get you to that successful point. And maybe that means persuading someone else to help you; maybe it means looking elsewhere for resources. But you at least know how to get there, which then follows up on your ability to unblock yourself. So if you are in that state of I just don't know what to do next, maybe it's Googling, or maybe it is reaching out for help, but either way, you keep something moving forward instead of just letting it sit there. Another area that I've seen myself and other people grow as developers is our ability to reason about quality and speed. It's something that I feel you, and I talk about pretty often here on the show, but it comes down to our ability to not just write code but then to also make good decisions on behalf of the company that we are working for and the team that we're working with and understanding what matters in terms of what features really need to be part of this MVP? Where can we make compromises? And then figuring out where can we make compromises to get this out to market? But what's really important then for circling back to your idea of revisiting the code, we want code that we can still come back and trust and then easily maintain and make updates to. And then I feel like I'm rambling, but I have a couple more. Shall I keep going? CHRIS: Keep going. Those are great. STEPH: All right. So for the others, there's an increase in responsibilities that I notice. So, in addition to people coming to you more often for help, then it could be that you are receiving more responsibilities. Maybe you are taking on specific ownership of the codebase or a particular part of the team processes. Then that also shows that you are improving and that people would like you to take leadership or ownership of certain areas. And then this one, I am throwing it in here, but your ability to run a meeting. Because I think that's an important part of being a good developer is to also be able to run a meeting with your colleagues and for that to be a productive meeting. CHRIS: Cool. I like that one. I think I want to build on that because I think the core idea of being able to run a meeting well is communication. And I think there's one level of doing this job where it's just about doing the job. It's just about writing the code, maybe some amount of translating a specification or a ticket or whatever it is into the actual code that you need to write. But then how well can you communicate back out? How well when someone in project management says, "Hey, we want to build an aggregated search across the system that searches across our users, and our accounts, and our products, and our orders, and our everything." And you're like, "Okay. We can do that, but it will be hard. And let's talk about the trade-offs inherent in that and the different approaches and why we might pick one versus the other," being able to have that conversation requires a depth of knowledge in the technical but then also being able to understand the business needs and communicate across that boundary. And I think that's definitely an axis on which I enjoy pushing on as I'm continuing to work as a developer. STEPH: Yeah, I'm with you. And I think being a consultant and working at thoughtbot heavily influences my concept of improving as a developer because as developers, it's not just our job to write code but to also be able to communicate and help make good decisions for the team and then collaborate with everyone else in the company versus just implement certain features as they come down the pipeline. So communication is incredibly important. And so I love that that's one of the areas that you highlighted. CHRIS: Actually speaking of the communication thing, there's obviously the very human-centric part of that, but there's, I think, another facet of technical communication that is API design. When you're writing your code, what do you choose to expose and make accessible to collaborators? And I don't just mean API in the terms of a REST API that people are heading, but I mean a class that you have in your system. What are the private methods, and what are the public methods? And how do you think about the shape of it? What data do you expose? What do you not expose? And that can be really impactful because it allows how can you change things over time? The more that you hide, the more you can change. But then, if you don't allow your collaborators to access the bits that they need to be able to work with your system, that's an interesting one that comes to mind. It also aligns with, I don't think you were saying this exactly, but the idea of taking on more amorphous projects. So like, are you working within a system and adding a new feature, or are you designing a system? Are you architecting? The word architect that role can sometimes be complicated within organizations, but that idea of I'm starting fresh, and I'm building a system that others will then work within I think this idea of API design becomes really interesting in that context. What shape do you give to the system that we're working within, and what affordances? And all of that. And that's a very hard thing to get right. So it comes from experience of being like, I used some stuff in the past, and I hated it, so when I am the architect, I will build it better. And then you try, and you fail, and you're like, well, okay, but now I've learned. And then you try it, and then you fail for different reasons. But the seventh time you try, it may be just that time you get the public API just right on the first go. STEPH: Seven times's a charm. That's how that goes, right? CHRIS: That is my understanding, yes. STEPH: I think something that is related to the idea of are you working in a structured space versus working in a new space and then how you develop that API for other people to work with. And then how do you identify when to write a test and what to test? That's another area that you were just making me think of is that I can tell when someone has experience with testing because they know what to test and what feels important to test. And essentially, it comes down to can I deploy with confidence? But there are a lot of times, especially if you're new to testing, that you're going to test everything, and you're going to have a lot of probably useless slow tests. But over time, you will start to realize what's really important. And I think that's one of the areas where then it does start to get harder to measure yourself as a developer because all of our jobs are different, and we work with different tech stacks, and we all have our unique responsibilities and goals. So it may be hard to say specifically like, "Oh, you're really good at X, Y, and Z, and that's how you know that you're improving as a developer." But I have more thoughts on that, which we'll get to in a moment where Tom mentioned that they don't have a way of measuring improvement. Shall I go ahead and jump ahead to I have no way of measuring that improvement, or shall we talk about regressions next? CHRIS: I'm interested in your thoughts on the regressions question because it's not something that I've really thought about. But now that he's asked the question, I'm thinking about it. So yeah, what are your thoughts on that? STEPH: My very quick answer is yes, [laughs] that there are regressions mainly because I respect that our brain can only make so much knowledge readily available to us, and then everything else goes into long-term storage. We can access it at some point, but it takes additional time, or maybe it takes some practice to recall that skill. So I do think there are regressions, and I think that's totally fine that we should be focused on what is serving us most at the moment and be okay with letting go of some of those other skills until we need to refine them again. CHRIS: Yeah. I think there's definitely a truth to true knowledge and experience with, say, a framework or a language that can fade. So if I spend a lot of time away from JavaScript, and then I come back, I'm going to hit my head on a few low ceilings every once in a while for the first couple of days or weeks or whatever it is. It was interesting actually that Tom highlighted the idea of he used to not write comments, and now he writes more comments, and so that transition -- I think we've talked about comments enough so our general thinking on it. But I think it's totally reasonable for there to be a pendulum swing, and maybe there's a slight overcorrection. And you read some blog posts that tell you the truth of the world, and suddenly, absolutely no comments ever that's the rule. And then, later on, you're like, you know, I could really use a comment here. And so you go that way, and then you decide you know what? Comments are good, and you start writing a bunch of them. And so it's sort of weaving back and forth. Ideally, you're honing in on your own personal truth about comments. But that's just an interesting example to me because I certainly wouldn't consider that one a regression. But then there's the bigger story of like, how do we approach building software? Ideally, that's what this podcast does at its best. We're not really a podcast about Rails or JavaScript or whatever it is we're talking about that week, but we're talking about how to build software well. And I think those core ideas feel like they're more permanent for me, or I feel like I'm changing those less. If anything, I feel like I'm ratcheting in on what I believe about good software. And there are some core ideas that I'm just refining over time, not done by any means, but it's that I don't feel like I'm fundamentally reevaluating those core ideas. Whereas I am picking up a new language and approaching a new framework and taking a different approach to what tools I'm using, that sort of thing. STEPH: Yeah, I agree. The core concepts definitely feel more important and more applicable to all the future situations that we're going to be in. So those skills that may fall into the regression category feel appropriate because we are focused on the bigger picture versus how well do I remember this rejects library or something that won't serve us as well? So I agree. I am often focused more on how can I take this lesson and then apply it to other tech stacks or other teams and keep that with me? And I don't want that to regress. But it's okay if those other smaller, easily Google-able skills fall to the side. [laughs] CHRIS: Wait, are you implying that you can't write rejects just off the top of your head or what's…? STEPH: I don't think I could write any rejects off the top of my head. [laughter] CHRIS: Fair. All right. You just go to rubular.com, hit enter, and then we iterate. STEPH: Oh yeah. I don't want to use up valuable space for maintaining that sort of information. Rubular has it for me. I'm just going to go there. CHRIS: I mean, as long as you have the index of the places you go on the internet to find the truth, then you don't need to store that truth. STEPH: A moment ago, you mentioned where Tom highlights that they have different views about code that they wrote, even code that they wrote just like a year ago. And to me, that's a sign of growth in terms that you can look back on code that you have written and be like, well, maybe this would be different, or maybe this is still a good idea, but the fact that you are changing and then reevaluating, I think that is awesome because otherwise, if we aren't able to do that, then that is just a sign of being stagnant to me. We are sticking to the knowledge that we had a year ago, and we haven't grown since then versus that already shows that they have taken in new knowledge. So then that way, they can assess should I be adding comments? When should I add comments? Maybe I should swing away from that idea of this is a hard line of don't ever do this. I think I just have to mention it because there is one that I always feel so deeply about, DRY. DRY is the concept that gives me the most grief in terms that people just overuse it to the point that they do make code very hard to change. All right, that's my bit. I'll get off my pedestal. But DRY and comments are two things [chuckles] that both have their places. CHRIS: I don't know if your experience was similar, but around DRY, I definitely have had the pendulum swing of how I feel about it. And I think again, that honing in thing. But initially, I think I read The Pragmatic Programmers, and they told me that DRY is important. And then I was like, absolutely, there will be no duplication anywhere, and then I felt some pain from that. And I've been in other systems and experienced places where people did remove duplication. I was like, oh, maybe it would have been better, and so I slowly got out of that mindset. But now I'm just in the place of like, I don't know, copy and paste not now, there was a period where I was like, just copy and paste everything. And then I was like, all right, I think there's a subtle line. There's a perfect amount of duplication, and that's the goal is to figure out that just perfect level. But for me, it really has been that evolution, and I was on one side, and then I was on the other side, and then I'm honing back in. And now I have my personal truth about duplication. STEPH: Oh, me too. And I feel like I can be a little more negative about it because I was in the same spot. Because it's a rule, it's a rule that you can apply that when you are new to software development, there aren't that many rules that are so easy to apply to your codebase, but DRY is one of them. You can say, oh, that is duplication. I know exactly what that is, and I can extract it. And then it takes time for you to realize, okay, I can identify it, but just because it's there, it doesn't mean it's a bad thing. Perfect duplication, I like it. CHRIS: Coming back to the idea of when we look back on our code six months, a year later, something like that, I think I believe the statement that we should always look back on our code and be like, oh, what was I doing there? But I think that arc should change over time. So early on in my career, six months later, I look back at my code, and I'm like, oh, goodness, what was happening there? I was very much a self-taught or blog internet-taught programmer just working on my own. I had no one else to talk to. So the stuff that I wrote early on was not good is how I will describe it. And then I got better, and then I got better, and I hope that I'm still getting better. And it's something that probably draws me to software development is I feel like there's always room to get a little bit better. Again, even back to that adage of it doesn't get any easier; you just go faster. Like, that's a version of getting better in my mind. So I hope that I can continue to feel that improvement and that ratcheting up. But I also hope that that arc is leveling off. There is an asymptotic approach to "good software developer." People in the audience, you can't see my air quotes, but I made air quotes there around good software developer. But that idea of I shouldn't look back probably this far into my career and look back at code from three months ago and be like, that's awful. That dude should be fired. I hope I'm not there. And so if you're measuring over time, what does your three months ago look back feel like? Oh, I feel like it's a little better. Still, you should look back and be like, oh, I probably would do that a little bit different given what I know now, what I've learned, but less so, I think. I don't know, what do you think about that? STEPH: Yeah, that makes sense. And I'm also realizing I haven't looked back at my code that much since I am changing projects, and then I don't always have the opportunity to go back to that project and then revisit some of the code. But I do agree with the idea that if you're looking back at code that you've written a couple of months ago that you can see areas that you would improve, but I agree that you wouldn't want it to be something drastic. Like, you wouldn't want to see something that was more of an obvious security hole or performance issue. I think there are maybe certain metrics that I would use. I think they can still happen for sure because we're always learning, but there's also -- I may be taking this in a slightly different direction than you meant, but there's also a kindness filter that I also want us to apply to ourselves where if you're looking back three months ago to six years ago and you're like, oh, that's some rough code, Stephanie. But it's also like, yeah, but that code got me to where I am today, and I'm continuing to progress. So I appreciate who I was in the past, and I have continued to progress to who I am today and then who I will be. CHRIS: What a wonderfully positive lens to put on it. Actually, that makes me think of one of -- We may be getting into rant territory here, but we talk a lot about imposter syndrome in the software development world. And I think there's a lot of utility because this is something that almost everyone experiences. But I think there's a corollary to it that we should talk about, which is a lot of people are coming into this industry, and they're like one year in, and the expectation that one year into a career that -- The thing that we do is not easy as far as I can tell. I haven't figured out how to make it easy. And the expectation that someone's going to be an expert that early on is just completely unreasonable in my mind. In my previous career, I was a mechanical engineer, and I went to school for four years. I actually went to school for five years, not because I was bad at school, but because I went to a place that had a co-op. And so I had both three different six months experiences working and four years of classroom education before I even got any job. And then I started doing things, and that's normal in that world. Whereas in the development world, it is so accessible, and I really feel like that's an absolutely wonderful thing. But the counterpoint of that is folks can jump into this career path very early on in their learning, and the expectation that they can immediately become experts or even in the short order I don't think is realistic. I think sometimes, when we talk about imposter syndrome, we may do a disservice. Like, it's not imposter syndrome. You're just new, and that's totally fine. And I hope you're working in an organization that is supportive of that and that has space for that and can help you grow in a purposeful way. In my mind, it's not realistic to expect everyone to be an expert a year in—end rant. STEPH: Well, I would love to plus-one your rant and add to it a little bit because I completely agree. I also love the phrasing that you just said where it's not that you have imposter syndrome; it's just that you are new and that team should be supportive of people that are new and helping them grow and level up. I also think that's true for senior developers in terms that you are very good at certain skills, but there's always going to be some area of the web or some area of software development that you are new to, and that is also not imposter syndrome. But it's fine to assess your own skills and say, "That's something that I don't know how to do." And sometimes, I think that gets labeled as imposter syndrome, but it's not. It's someone just being genuine and reflecting on their current skills and saying, "I am good at a lot of stuff, but I don't know this one, and I am new to this area." And I think that's an important distinction to make because I still want -- even if you are not new in the sense that you are new to being a software engineer, but you still have that space to be new to something. CHRIS: Yeah, it's an interesting, constantly evolving space. And so giving ourselves a little bit of permission to be beginners on various topics and for me, that's been an experience that's been continual. I think being a consultant, being a freelancer that impacts it a little bit. But nonetheless, even when I go into organizations, I'm like, oh, years in technology that only came out two years ago. That's pretty fresh. And so it's really hard to be an expert on something that's that new. STEPH: Yeah. I think being new to a team has its own superpower. I don't know if we've talked about that before; if we haven't, we should talk about, it but I won't do that now. But being new is its own superpower. But I do want to pivot back to where Tom mentioned that I have no way of measuring that improvement. And I think that's a really great thing to recognize that you're not sure how to measure something. And my very first honest suggestion if you are feeling that way is to go ask your manager and ask them how they are measuring your improvement because that is their job is to understand where you're at and to understand your path as a developer on the team and then helping you set goals. So since I'm a manager at thoughtbot, I'll go first, and I can share some ways that I help my team measure their own improvement. So one of the ways is that each time that we meet to discuss work, I listen to their challenges, and I take notes; I'm a heavy note-taker. And so once I have all those notes, then I can see are there any particular challenges that resurface? Are there any patterns, any areas where they continuously get stuck on? Or are they actually gaining confidence, and maybe something that would have given them trouble a couple of weeks ago is suddenly no big deal? And then I also see if they're able to unblock themselves. So a lot of what I do is far more listening, and I'm happy to then provide suggestions. But I am often just a space for someone to share what they are thinking, what they're going through, and then to walk through ideas and then provide suggestions if they would like some, and then they choose a suggestion that works best for them. And then we can revisit how did it go? So their ability to unblock themselves is also something that I'm looking for in terms of growth. And then together, we also set goals together, and then we measure that progress together. So it's all very transparent. And what areas would you like to improve, and then what areas would it be helpful for thoughtbot or as a consultant for you to improve? And then if I am fortunate enough to be on a project with them and see how they reason about quality and speed, how they communicate the type of features they're most comfortable to work on, and which tasks are more challenging for them, I also look to see do people enjoy working with them? That's a big area of growth and reflects communication, and reliability, and trust. And those are important areas for us to grow as developers. So those are some of the areas that I look to when I'm helping someone else measure their own improvement. CHRIS: I really like that, the structured framing of it, and the way that you're able to give feedback and have that as a constant, continuous way to evaluate, define, measure, and then try and drive towards it. Flipping things around, I want to offer a slightly different thing, which isn't necessarily specifically in the question, but I think it's very close to the question of how do we actually improve as developers? What are the specific things that we can try and do? I'm going to offer a handful of ideas. I'd be super interested to hear what your ideas are. But one of the things that has been really valuable for me is exploring different languages and frameworks. I, without fail, find something in every new language or framework that I then bring back to the core things that I'm working with. And I've continued to work with Rails basically throughout my career, but everything else that I'm doing has informed the way that I work with Rails and the way that I think about building code. As specific examples, functional programming is a really interesting frame of mind, and Elm as a language is such a wonderful, gentle, friendly, fun introduction to functional programming because functional programming can get very abstract very easily. I've also worked with Haskell and Scala and other languages like that, and I find them much more difficult to work with. But Elm has a set of constraints and a user-centric approach that is just absolutely wonderful. So even if you never plan to build a production Elm application, I recommend Elm to absolutely everyone. In terms of frameworks, depending on what you're using, maybe try and find the thing that's the exact opposite. If you're in the JavaScript space, I highly recommend Svelte. I think it's been very informative to me and altered a number of my opinions. A lot of those opinions were formed by React. And it's been interesting to observe my own thinking evolve in that space. But yeah, I think exploring, trying out, -- Have you ever used Lisp? Personally, I haven't, but that's one of the things that's on my list of that seems like it's got some different ideas in it. I wonder what I would learn from that. And so continually pushing on those edges and then bringing that back to the core work you're doing that's one of my favorite things. Another is… It's actually two-fold here. Teaching is one, and I don't mean that in the grand sense; you don't have to be an instructor at a bootcamp or anything like that but even just within your organization trying to host a lunch and learn and teach a concept. Without fail, you have to understand something all the better to be able to teach it. Or as you try and teach something, someone may ask you a question that just shakes the foundation of what you know, and you're like, wow, I hadn't thought about it that way. And so teaching for me has just been this absolutely incredible forcing function for understanding something and being able to communicate about it again, that being one of the core things that I'm thinking about. And then the other facet sort of a related idea is pairing, pair with another developer, pair with a developer who is more senior than you on the team, pair with someone who is more junior than you, pair with someone who's at the same level, pair with the designer, pair with the developer, pair with a product manager, pair with everyone. I cannot get enough pairing. Well, I can, actually. I read a blog post recently about 100% pairing, and I've never gotten anywhere close to that number. But I think a better way to put it is I think pairing applies in so many more contexts than people may traditionally think of it. People sometimes like to compartmentalize and like, pairing is great for big architecture design, but that's about it. And my stance would be pairing is actually great at everything. It is very high bandwidth. It is exhausting, but I have found immense value in every pairing session I've ever had. So, yeah, those are some loose thoughts off the top of my head. Do you have any how to get better protips? STEPH: Yeah, that's a wonderful list. And I'm not sure if this exactly applies because it's been a while since I have seen this talk, but there is a wonderful talk by Sandi Metz. I mean, all of her talks are wonderful, but this one is Go Ahead, Make a Mess. And I believe that Sandi refers to or highlights the idea of trying something new and then reflecting on how did it go? And that was one of the areas that I learned early on, one of the ways to help me progress quickly as a developer. Outside of the suggestions that you've already shared around lots of pairing that was one of the ways that I leveled up quickly is to iterate quickly. So I used to really focus on the code that I was writing, and I thought it needed to be perfect before my colleagues could review it. But then I realized that the sooner that I would push something out for feedback, then the faster I would get other more experienced developers' input, and then that helped me learn at an accelerated rate and then also ship more frequently. So I'd also encourage you to just go ahead and iterate quickly. We talk about with software in general, we want to iterate on the code that we are pushing up for other people to look at and then give us feedback on and then reflect on how did it go? What did we learn? What are some areas that we can improve? I feel like that self-evaluation is huge, and it's something that I know that I frankly don't do enough because one, it also prompts us to appreciate the progress that we have made but then also highlights areas where I feel strong in this area, but these are other areas that I want to work on. CHRIS: While we're on the topic of talks that have been impactful in our journeys of leveling up as developers, I want to quickly list three that just always come to mind for me: Avdi Grimm's Confident Code, Katrina Owen's Therapeutic Refactoring, and Ben Orenstein's Refactoring from Good to Great. There's a theme if you look across those three talks. They're all about refactoring, which is interesting. That tells you some stories about what I believe about how good software is made. It's not made; it's refactored. That's my official belief, but yeah. STEPH: Love it. That's also another great list. [laughs] For additional ways to level up, there are some very specific areas where it could be maybe do code katas or code exercises, or maybe you subscribe to certain newsletters, stay up to date with a language, new features that are being released. But outside of those very specific things, and if folks find this helpful, then maybe you and I can make a fun list, and then we could share that on Twitter as well. But I always go back to the idea of regardless of what level you're at in your career is to think about your specific goals, maybe if you are new to a team and you're new to software development, then maybe you just have very incremental goals of like, I want to learn how to write a test, or I want to learn how to get better at PR review or something very specific. But to have real growth, I think you have to first consider where it is that you want to go and then figure out a way to measure to get there. Circling back to some of the ways that I help my teammates measure that growth, that's one of the things that we talk about. If someone says, "Well, I want to get better at PR review," I'm like, "Great. What does that mean to you? Like, how do you get better at PR review? How can we actually measure this and make it something actionable versus just having this vague feeling of am I better?" I think I've ended up taking this a bit more broad as you were providing more specific examples on how to level up. But I like the examples that you've already provided around education and then trying something outside of your comfort zone. So what's coming to mind are more of those broad strategies of goal setting. CHRIS: I think generally, you need that combination. You need how do I set the measure? How do I think about improvement? And then also ideally a handful of tactics that you can try out. So hopefully, we provided a nice balanced summary here in this episode. And hopefully, Tom, if you're listening, you have gotten some useful things out of this conversation. STEPH: Yeah, this was fun. We managed to take this topic and make a whole episode out of this. So thanks, Tom, for sending in such a great topic. CHRIS: Frankly, when I saw the topic, I was certain this was going to happen. [chuckles] This was an obvious one that was going to fill up the time for us. But yeah, with that, I think we've probably covered plenty here. Should we wrap up? STEPH: I'm sure there's more, but sure, let's wrap up. CHRIS: The show notes for this episode can be found at bikeshed.fm. STEPH: This show is produced and edited by Mandy Moore. CHRIS: If you enjoyed listening, one really easy way to support the show is to leave us a quick rating or even a review in iTunes, as it really helps other folks find the show. STEPH: If you have any feedback for this or any of our other episodes, you can reach us @_bikeshed or reach me @SViccari on Twitter. CHRIS: And I'm @christoomey. STEPH: Or hosts@bikeshed.fm via email. CHRIS: Thanks so much for listening to The Bike Shed, and we'll see you next week. Both: Byeeeeeee. Announcer: This podcast was brought to you by thoughtbot. Thoughtbot is your expert design and development partner. Let's make your product and team a success.

Some brands are lucky enough to have a built-in audience of millions, while others need to develop an audience from scratch. Chris Mainenti has been on both sides of the coin and he knows that in either situation, once you have a base of potential customers paying attention to you, the next challenge is converting those browsers to buyers. Chris is the Director of Commerce Strategy at Discovery, Inc. where he is helping turn the millions of viewers who tune into Discovery’s channels such as HGTV, TLC, Food Network and more, into customers who buy across various platforms. On this episode of Up Next in Commerce, Chris explains how he put his history of building audiences at previous companies to work at Discovery — including some tips for young companies on how to utilize newsletters. And he discusses how to use the data you collect as a starting point for creating a more personalized, one-to-one relationship with your audience on various platforms. Plus, he looks into the future to predict how shoppable experiences will be made possible with universal add-to-cart and buy-now options. Main Takeaways:Developing Your Audience: Audience development goes beyond marketing. When you are building your audience, you have to know who you are as a brand and understand the audience you have and want to bring in, and what they want and need. In the early days of a brand, certain audience development strategies work better than others, including tapping into the power of newsletters.Lights, Camera, Take Action: Every company is collecting immeasurable amounts of data, which then needs to be sorted, analyzed and acted on. But the actions you take should be nuanced and applicable to the specific needs of specific audiences. For example, it would be wrong to lump together all of the women in your audience because a woman who is exploring your dot-com presence is likely looking for something different than a woman that is scanning a QR code on their TV. Those segments of women shop differently, and therefore should be approached in unique ways after the data tells you what they each want.Dreams of a Universal Cart Experience: Many believe the future of ecommerce revolves around the development of a universal cart experience. Every business wants to create shoppable moments and engage with customers across many different platforms. But getting to this nirvana means you also have to remove all the friction points.For an in-depth look at this episode, check out the full transcript below. Quotes have been edited for clarity and length.---Up Next in Commerce is brought to you by Salesforce Commerce Cloud. Respond quickly to changing customer needs with flexible Ecommerce connected to marketing, sales, and service. Deliver intelligent commerce experiences your customers can trust, across every channel. Together, we’re ready for what’s next in commerce. Learn more at salesforce.com/commerce---Transcript:Stephanie:Welcome back to Up Next In Commerce. This is your host, Stephanie Postles co-founder of mission.org. Our guest today is Chris Mainenti, the director of commerce strategy at Discovery Inc. Chris, welcome to the show.Chris:Thank you, Stephanie. I appreciate you having me on and talking all things commerce here in the current climate that we're in.Stephanie:Yeah. I am very excited to have you guys on. I was just thinking about how long Discovery channel, and all the other channels, HGTV, and Food Network and Travel Channel have been in my life and with that, I want to hear a little bit about your role at Discovery. I mean, it seems like there's so much going on, so many digital portfolios that you guys have over there, and I think just a lot behind the scenes that an average consumer wouldn't even know. So, I'd love to hear what you're up to at Discovery. What is your day-to-day look like?Chris:Sure. So, I would say, first and foremost, for commerce specifically in the digital media space, we're probably slightly different than a lot of others. We're really multifaceted in terms of how we work, and who we work with across the org. Obviously, like you said, Discovery is huge, has a ton of major, major worldwide brands. So, we actually sit on the portfolio wide level with our lifestyle brands, and we're really in the weeds with them on the day-to-day basis. And, that really starts with, obviously, our editorial teams. That's our bread and butter, that's our voice and our authority in this space. So again, that's really where we begin, and that's obviously where we're doing our content output, and producing all of this great shopping content for our different audiences, and again pulling our experts from all of these different brands to come together.Chris:So again, folks are really getting the full spectrum of expertise in all of these different categories. And from there, it just really starts branching out into other groups. So, we work heavily with our ad sales and branded content teams, where we work on much larger partnerships and deeper integrations which we can talk about today as well. We have a licensing team, where we work on licensed products, and we take our learnings that we're seeing on our shopping content on a day-to-day basis, and analyze that, and then speak with licensing to see where there may be some room to actually create a new line with one of our partners.Chris:We also, believe it or not, and I know you don't know this, we have a video games team at Discovery, and we work closely with them as well on trying to find those shoppable moments, and again bringing our brand and our voice into those games when they're being built. So again, we're always serving the reader no matter who or where they are, and again pivoting as necessary. So, those are just a few groups, and obviously our marketing and ops, and audience development teams were heavily embedded with as well when it comes to promotion.Chris:So again, there are just, I would say, a lot of areas that we focus on. I know in the beginning it was always all about, commerce is part of diversifying your revenue streams at a digital club. But, we see it more as now, we're trying to diversify our commerce stream into all of these other areas. So again, a lot of exciting stuff has already happened, and we're working on some cool stuff too as we head into next year. So, a lot of exciting stuff in an area that's obviously blowing up for a variety of reasons.Stephanie:That's a lot going on there. It's actually really interesting because you just mentioned video games, and I just did a recap episode with one of my coworkers for the first 50 episodes of this show, and the one thing I was bringing up was like, "I think there's a big opportunity in having shoppable moments in these worlds or video games." And, we were mentioning Unreal and Epic Games specifically, that I hadn't really seen that yet. So, it's interesting that you guys are starting to explore that arena, because it feels like that's something of the future, but it's needed, and that's where everything's headed.Chris:Yeah. And again, I can't stress enough. I mean, our portfolio is just so suited for so many of these different, avenues that we could always find something where, again, we're not being gimmicky just to say we're there. This is our bread and butter, and we're making sure that we stick to our tried and blue, into who we are, and not shy off too much, and again just try to say, "We did something here or there." Really making sure we're always serving our audiences and giving them what they want on the platforms they want.Stephanie:Yeah. Which I think that's a really good jumping off point, then because that was actually my one biggest question I had of how do you strategically think about what an audience wants without disrupting the content? I mean, it seems so tricky, because you see a lot of shows, and whatever it may be where you might have product placement in a show or a movie, but it might not actually uplift sales, because it wasn't done correctly. Where I was also just talking about the Netflix original, the organizing show where they partnered with the container store, and how they had an instant, I think was a 17% uplift in sales after that show aired. That worked, and many others don't. So, how do you guys think about making those shoppable moments, and actually having it work?Chris:Sure. First and foremost, I think, you have to be honest and say, "Look, not everything is going to hit." And honestly, it's not always meant to always hit. So, I think we go into that, first being real with the current situation, and understanding not everyone is going to want every single thing. We're always talking about integrating, promoting, so on and so forth. So, I would say that's first. Secondly, again, we start with, what's our expertise? What do we believe in? And, what do we want to showcase to our various audiences across all of these different platforms? And then, from there is when we start to really start getting down to the nuances.Chris:And look, we have created what we dub internally as the commerce hub, where we're bringing in data feeds from all different platforms, our affiliate networks, our in-house reporting platforms, social, so on and so forth, bringing that all together. And again, understanding, what are people consuming? And, what is their mindset when they're on social, versus linear, versus a DTC, or our dot-coms. And, really starting to look and pull out trends from that. I always like to say I prefer the term data influenced versus data driven, because you can't just take a dashboard of data, and sort in descending or ascending order, and say, "Okay. Whatever is at the top or bottom, do or don't do." And, call it a day.Chris:We focus much more heavily on insights, and use that data as a jumping off point, but then do very, very deep analysis, and pull actionable insights out of that for all of our different brands and teams for when they're creating new content, or when we're optimizing old content. Again, wherever that is. And then, I think lastly with that comes, how do we visualize that to the audience. On digital.com, is it more about, again, really simple to read, simple call to actions to buy items. Again, on linear, what is that? A QR code experience? Is it some type of more deeper integration with a smart TV company on our TV E experiences? Is it more deeply integrated where you can actually tap to purchase within the app? So on and so forth.Chris:So again, there's just a lot of things that we're looking at. We never make it cut and dry, that's probably because personally I don't think anything is ever cut and dry, especially this space and shopping behaviors across, not only brands but the platforms those brands are on, and that's how we look at it. I know that's a lot, and that sounds a bit crazy, but we do really pride ourselves on, again, using these things as a jumping off point and then really diving in deep and making sure that we're serving our audiences, again, where they like to consume this content.Stephanie:Got it. Yeah. It sounds like everything is very custom, and every channel and project you start from scratch where you start figuring out what your audience might like. But, do you have any internal formulas where you're like, "Well, we always follow this in the beginning." and then, it goes crazy after that, because we find other things out. Is there anything that's similar among all the campaigns or projects that you're working on, at least from a starting point?Chris:Yeah. I think, honestly, it's probably not surprising whenever you're talking about items on sale, or whenever we're talking about certain merchants, or price points, or categories, like organizing and cleaning is always up there for us. We know very specific furniture categories that do very well for us. So, we do have our basic what we call playbooks that we start off with, but like you said, we still are always constantly learning and pivoting as necessary. I think a perfect example is in the beginning of the year, I don't think anyone in this world saw what was coming, so we were doing our thing, and then when everything started to unfold, we got together and we had to pivot. And again, the good thing about Discovery's brands is, again, we are so widespread in terms of the categories that we're experts in, that we were able to easily pivot and, again, make sure we're giving our audiences what they need at that moment.Stephanie:Do you see more companies starting to shift? Like media companies turning into ecommerce companies, and ecommerce companies turning into media companies. I've heard that saying quite a bit, especially over the past six months, but it feels like you guys have been there for a while. Do you see other companies looking to you for maybe best practices of like, "How do I make this shift?" Or, "Should I make this shift?"Chris:100%. I think, the beauty in that is that we can coexist and really do things that benefit each of us. I don't think this is an either, we succeed or they succeeded. This is, I think a space where we can coexist. The way I always like to frame this when I'm talking to our merchant partners, and talking internally, is we're really here to humanize the star review. When you come to us, you're not just going to see, again, this is a four out of five, or this is a five star, item, and that's it from the random ecosystem of the internet. We are heavily focused on saying, "Look, here are the things we recommend, and why." And, I think that's where our partners can really leverage us, and where you're really seeing us shine. Again, we don't have to just throw a bunch of random stuff out there and hope for the best.Chris:Again, given our brands and our standing in this space, we can really leverage our expertise and authority there when growing this portfolio with all of our partners. To be honest with you the thing that drove me to Discovery the most was, "Wow, these are huge brands, with huge audiences, and huge respect. Now, we just got to tie all of that together, and go from the moment of inspiration to action." And then again, that's what we've been working on.Stephanie:That's really cool. With all the data that you were mentioning earlier, since you joined have you seen any changes in consumer shopping behavior?Chris:So, yes. Obviously, the biggest one occurring this year, and that was with online grocery. I think it's no surprise that it's been building up now for a year or two in terms of mainstream, but it never really caught on. It's only a five to 10% of folks are really engaging and entertaining the online grocery space. But then again, obviously, earlier in the year when things started to shut down, and people were uneasy about going out, we did see huge spikes in that space, obviously, on our FoodNetwork.com site. And, I would say that continued for a bit, and did peter out a bit recent months which, again, is obviously expected. So, I think that's probably one of the big ones.Chris:The other thing that we have seen, not so much in terms of major shifts in shopping behaviors, just more increased sales in categories that we already know are performing. So, organizing and cleaning is always been a winner for us, and then as the months went on, we've just seen it doing better for us. I think we do a lot of buying guides where we talk about the best cast iron skillets on Food Network, or the best humidifiers on HGTV. We started to see those things gain more and more traction as we went, and we're attributing some of that to us really getting our audience to trust us, and now know that they can come to us as a trusted resource to really be a personal shopper for them.Chris:And again, we've seen that across the board in all of our main categories. The only other thing I'll say in terms of, not only, I wouldn't say shifts in behaviors, but just something else we've pulled out from the data is that, everyone loves a good deal and good price points, but our audience is willing to spend more, especially when those items are either offered at a discounted rate for a holiday or something, or if we've worked with the merchant to get an exclusive discount for our audience, so we have also seen uptakes in that as well. But again, holistically, we haven't seen any huge shifts outside of, like I said, the online grocery, which again is expected given the situation we've been in.Stephanie:Yeah. That makes sense. Yeah. I saw for the Food Network, I think you had a subscription platform and you partnered with Amazon. Was that something that was already in the works, or did that get sped up once everything was happening with COVID?Chris:Yeah. So, that was already in the works with our DTC group, and for folks who don't know that's our subscription platform on the Food Network side that we call internally FNK, because it's just easier. And yes, that was in the works, and again we're working more and more in getting that to more and more folks who are really looking to get more classes, get more recipes, just be more intimate with our brand. Stephanie:Yeah. It looked very cool. I was on there looking around at, "Oh, you can follow these chefs and have cooking classes with them, and then you can tell your Amazon Echo to order it for you the exact things you need." And, it looked like it would be really fun to engage with that.Chris:Exactly. It goes back to that 360 approach that we have really been focused on, when it comes to our shopping portfolio.Stephanie:Yeah, that's very fun. So, you've talked a lot about partnerships where you've touched on a bit. But, tell me a little about what does a partnership look like from beginning to end? What does that process look like when you're finding a partner, figuring out how to actually strategically partner with them in a way that benefits both parties? What does it look like behind the scenes?Chris:Sure. So, I think there's really two paths there, there's the partnership stuff that we handle directly with merchants through affiliate networks, and so on and so forth. And, for that we do a lot of research on our end, again we already know what type of product hits, what type of merchants hit. So, one thing we do is take that and then say, "Okay. What are similar merchants in this space?" And then, we'll reach out and discuss the opportunity of working together on that front. And then I would say, on the other side, bigger picture stuff is, again, we're heavily embedded with our ad sales team on much larger partnerships.Chris:And, I think a great example of that is our shop the look campaign with Wayfair, which is a deep integration that spans across linear and digital that, again, was really spearheaded by our sales team that we then came in and assisted with. But, for folks who don't know, basically what this is, when you go to any of our photo inspo on hgtv.com, you'll see a little flyout of all the products within the image that are shoppable on Wayfair.com. And obviously, that's not just a basic integration that you just wake up one day and do. So for that, we came together and we've said, again, "What can we do that is going to benefit both of us, that's going to serve our audiences for the long run, and really make a successful integration here?" So again, that's what turned into shop the look.Chris:It's one of our best partnerships that we have across our dot-coms right now, and it's super successful, our audience loves it. And again, I think It's always starting with, "Well, what is the goal? And, what do we want to achieve from this?" I think sometimes people get too focused on, "What looks cool?" And like, "Let's just do that." We wanted to really focus on, "Well, what's the goal here?" And, what do we think we can create that's actually going, again, to help our audiences that come to hgtv.com be inspired and feel comfortable, making purchases based off of what they're seeing.Chris:So, that's really how we approach these, we're super particular about who we work with, and what that looks like. You mentioned the Amazon partnership, we have a really strong relationship with them as well. And for us, again, it's always looking at the brand and our audiences first and saying, "What makes the most sense for them?" And then, that's when we start peeling the layers here, and figuring out what are those experiences that we could bring to them on different platforms.Stephanie:Yeah. I think that's really smart. Like you said, not to just do something because it looks cool or seems cool, but actually do something that you know the audience will like, and will convert into sales to also help the partner. What are some of the success metrics for the shop the look campaign for example? What did you go into hoping to achieve when you set up that partnership? Is it affiliate based, or what do you guys look for and be like, "Oh, this is a successful campaign versus the previous ones that were maybe okay, or good."?Chris:Yep. So, I think just simply put it, consumption and sales are the big ones. Consumption being, are we seeing more and more folks coming to these different integrations across our platform, and then again how are they translating into sales? Looking at things like, "Okay, so we are getting them to Wayfair.com, but once they're on Wayfair.com what are they doing?" So obviously again, looking at conversions, average order value, so on and so forth. Again, just to really gauge what these audiences are looking like, as the days, weeks, and months go by. I would say, one of the things that we were looking for, especially as COVID first hit was, "Are we seeing an increase, a decrease? What are we seeing in terms of shopping behaviors across our platform?" And again, the metrics we looked at for that was, obviously, click through rates, conversion rates, average order value. Because we even saw in some instances where experiences weren't driving as many views or clicks, but the average order value was much higher.Chris:And again, just goes to show that our audience is a very qualified audience that trusts us, and is willing to spend with us. So, we try to pull out all of these different metrics. I think one of the things with commerce that is either for better or worse, is that you can't just look at one metric and just live and die by that number. So again, that's why we have a handful. And look, we also pivot based on what that platform is, what the experience is, who the partner is, so on and so forth. So, we don't have a one size fits all solution, again, that was done by design. And, that's how we approach these things. And again, just making sure that we stay true to who we are, and we're benefiting everyone involved.Stephanie:Got it. How do you keep track of, if there's a TV viewer who's watching HGTV, and then you're trying to send them to maybe Wayfair to shop that look like, what are the best practices with converting those people, but also keeping track of them in a way that's not maybe creates friction? Are you telling them, "Go visit this URL."? Or how do you go about that?Chris:Yeah. So, totally right. I think, obviously, the most common ways of driving from linear to digital is the QR code experience. And, we're actually working on some of those solutions as we speak and trying to understand, again, what will it take to bring more linear folks from TV down to digital, and like you said, make this a frictionless seamless experience? So again, is that as simple as a QR code, or again is this more about a stronger deeper integration that's a bit more sophisticated and partnering up with folks who can actually understand what is on screen at any moment, and then surface that product on screen.Chris:Again, if you have a smart TV and allowing folks to enjoy that experience, or again, when it comes to TV E we have our go apps that you could log into with your cable subscription. And again, obviously, it could be more sophisticated on your mobile device. So, what does that look like? Is it again, while you're watching it at minute three or whatever, five minutes in, do you surface what is currently being seen in the screen and saying, "Look, shop this room?" And, what do you do from that point down to the device. Can it be as simple as just a tap to buy, or do you have to tap and then open up a new browser window? What do those integrations look like? Again, ultimately trying to find the most frictionless experience. So, I think we're still experimenting with that. I don't think anyone in this space has really nailed that down in terms of what is shoppable TV, or just shoppable video in general? And again, how do we go beyond what just looks cool and turn that into actionable?Stephanie:Yep. Yeah, I think creating a frictionless experience is key, and there's a lot of room for innovation in that area. I'm even thinking about just Instagram, where I'll find a blogger I like and I really like her outfit, and then it's like, "Okay. Well, now go to the link in my bio." And then, that's going to open a LIKEtoKNOW.it app, and then maybe you'll be able to find the outfit. But at that point, it's probably just on the home screen if that new app. And, it just feels like there's so many places for a customer to drop. I guess I was just really eager to look at that outfit, so I stuck with it. But any other time, I probably would been like, "Oh, that's too much work." It seems like there's just a lot of room for innovation around this shoppable moments, whether it's TV, social, video, audio, anything.Chris:Yeah. I mean, I think you nailed it right there. I think Instagram is a perfect example, and that's a platform we're looking at as we speak, and we have some ideas around that as well. Because like you said, our goal here is to, how do we cut out all of these extra steps that are unnatural? Normally, when you see a product you like, you want to be able to say, "Okay. Great. Let me buy that." Not let me go to a bio, let me click this link, let me wait for this page to load, let me do that checkout experience is completely different from the platform I was just on. And then obviously, you're playing around with browser settings and everything else.Chris:So, I think you're spot on, and again that's something we're heavily focused on, again, literally as we speak. And, what does a more integrated Instagram shopping experience look like for Discovery and our partners? So, there's going to be more to come on that soon. But, we are thinking about that, and trying to find, again, these ways to make it as frictionless and seamless as possible. Again, no matter where our audience is consuming our content.Stephanie:Yeah. Well, it seems like if anyone can figure it out, it would be all because it's not like you're trying to put your products on someone else's show, or having to utilize someone else's platform. You have your own platform, you have your own shows, you can build new shows, and try out different ways to influence. There's shopping behaviors. That seems like there's just a ton of opportunity for you to experiment with everything that you all have.Chris:Yeah. No. A 100%, and those are these ad conversations we're having with a lot of our partners as well, and understanding from their world how they see it, and then bringing our world into that, and marrying that together, again, so we can coexist here, and at the end of the day just create a better experience for our viewers.Stephanie:Yep. Love that. So, what are some of your favorite platforms that you guys are experimenting with right now? You said, you were looking into Instagram, but what's really performing for you, and what are some of the more moonshot platforms that you're trying out, and you think it will be good, but you're not so sure?Chris:Sure. Yeah. I mean, obviously, the bread and butter is our shopping content on our dot-coms, those are our top performers. But, I will say some of the more areas of interest, again we already spoke about Instagram. But, another one where we are seeing some really good traction, believe or not, is in the Apple News space, most notably on Food Network. We're getting a lot of traction on that platform, and seeing what our audiences are resonating with the most on Apple News, which I again I know it maybe a shock to some folks, but I think-Stephanie:Yeah. So, tell you more about that. I mean, I have an Apple phone, but I have not opened up Apple News probably since I got the phone, so tell me more about, what are you guys doing there?Chris:Sure. Yep.Stephanie:Because you're the first person who said this.Chris:Okay. All right. Again, understood I know that's not always the first thing that jumps into someone's mind when you're talking about commerce, and lifestyle brands, especially because they name Apple News. But again, I know you don't really use it, but again this is just the basic free version that's included with your device when you get it. And again, we're syndicating our day-to-day content onto that platform. And, we've built really strong audiences across Apple News. And again, it's a similar experience to our dot-coms, just slightly different because it has to fit obviously the specs of the Apple News platform. But again, we just have seen some really strong successes in different areas, again most notably in the buying guide space, or sales events that are happening, and dabbling with pushing notifications for that.Chris:Obviously, with some of the recent shopping events that occurred, we built a push notification strategy around that as well, and it did really well for us. So again, I think that's one of those ones that is also intriguing to us. But I think, again, the high level, we really are trying to be everywhere it makes sense, but also really tailoring our content and strategy based on what that platform is. So, for some of the stuff that's working on Apple News may not make sense for Instagram or vice versa, so on and so forth. So I think, again, those are two areas. And I would say, the last thing that we're really, or me personally is really intrigued by, is this universal cart experience/straight to cart experience that more and more folks are dabbling with. There's a handful of platforms out there that can help publishers do this.Chris:And for folks who aren't familiar with this, it's basically saying, if someone comes to HGTV, or FoodNetwork.com, or tlc.com, and they see an item they like on there, instead of saying, "Buy now on X merchant site." And getting thrown off to that merchant, you could hit buy now, or add to cart, and you could actually check out within our platform, which I think is definitely going to be a big piece of the puzzle for the future of commerce on digital publishers. I think the big question will just be adoption, and then what does that look like. I think, again, Discovery is in a perfect position for this, because folks are already coming to us for this expertise, and know and love our brands already. So, there won't be a lot of convincing in terms of like, "It's okay to check out with us as well."Chris:But again, we're anticipating some shopping behavior adoptions that are going to occur during that process. But again, I think that's an area where you really start to open up a lot of new doors here when it comes to shopping for digital media sites. And, I think that's when it gets even more exciting for deeper integrations with Instagram shopping for example.Stephanie:Yep. Yeah, I love that. I mean, I'm excited to look into the Apple News more. And, I was just intrigued by that, because I like hearing things that others have not said yet. Because I'm like, "Oh, that means there could be opportunity there if you know how to work with the platform." Especially, if you can set up a push notifications. That's huge to make it in front of Apple users. And then yeah, I completely agree about the being able to shop instantly from a page. We just had the CEO of Fast on, Domm. And, I thought it was really interesting how he was talking about how every website should have buy now buttons under every single individual products, and he went into the whole thing of, "You actually will have higher conversions." Because of course, I was like, "Well, then you have to get past the minimum shipping amounts, and maybe higher order values, if you let me add stuff to a cart." And he said, "Based on everything they've seen, people will buy more if they can buy it instantly." And, it'll batch it in the background and ship it out after the fact, all together. So-Chris:Yeah.Stephanie:... I think you said it.Chris:Yeah. Convenience is key. I mean, everyone likes convenience, and again that's our hypothesis as well here, that we do plan to see increased conversions by building a more intimate shopping experience across our dot-coms with a lot of our partners.Stephanie:Yeah, that's great. So, the one big topic I also want to touch on was about audience development. So, when you guys, you have these huge audiences that you can tap into, but for especially a smaller brand, I want to hear how you all think about building that audience to then eventually being able to sell some products to them as well. What does that process look like? And, how can a new brand do that?Chris:Sure. So, I think first and foremost, I think it's important to understand what is audience development as it relates to your brand and organization. I think the biggest misconception with the term audience development is, "Oh, yeah, it's just another word for marketing." But it's not, and this has been written about it as well. And, I think the easiest way to think about this just in a very basic form is, marketing is more about how you want to look to the world as you bring those audiences in initially. More on the branding side of things, whereas dev is now like, "Okay. So, who are we to the world?" And, really drilling down on understanding those audiences that were brought in and who they are, and then building those audiences through different engagement tactics and community tactics.Chris:So, I think that's always a good place to start, to understand how those two worlds kind of then meet. And then once that happens, to answer your specific question, again start with understanding who your audiences are, and where they are. I think sometimes and probably not so much now, but in the past when I was first getting into this space, I think a lot of people just thought that, "Well, content is content. It could be put anywhere, and it's going to work the same way everywhere. Obviously not the case, even more so for shopping content, and behaviors. So, it's really, again, drilling down and pulling out insights based on, "Okay. Who is my Facebook audience? Who is my newsletter audience? Who is my Apple News audience?Chris:And, really starting there, and once you understand high level who they are, what they like, what they're consuming. More specifically when you talk about newsletters, what type of keywords are working to increase open rates, and so on and so forth, then you could start drilling down on the specifics. Saying like, "Okay. High level, here are the different topics and content archetypes that are working, now how do we build out an editorial calendar with that in mind." Again, with the understanding that we're not just going to set this and forget this across the board. What this looks like in newsletters is going to be slightly different than how we're positioning it on Facebook for example, and so on and so forth. So, I really think that's the key right there, and using data to your advantage and saying, "Okay. Well, here's all the different metrics that we're currently compiling, which ones can we look at, and pull from to better understand what these audiences are coming to us for." And again, working with your editorial teams, and the branding teams to bring that all together and say, "Okay. Now here's the plan for output."Stephanie:Yep. Got it. So, if you don't have an audience, and you're starting really from scratch, where would you start? Because I read quite a few articles, maybe from your past life at other companies about you increasing conversion rates by 60%, through maybe newsletters or increasing newsletter subscriptions? Is that maybe a place that you would start? Or where would you recommend someone brand new, who's like, "I don't really have an audience. I have five followers on Instagram."? What's the best way to acquire an audience and then keep them around to build it?Chris:Yeah. So I would say, if we're talking about limited resources and funding, I do think newsletters are a great place to start. And that's really because, it gives you an opportunity to have this one-on-one intimate relationship with the folks on the other side that for the most part you're not having to be held against what the algorithm is going to decide to show at any given day. Obviously, you have to worry about, spam and junk mail and things like that. But for the most part, if you're running a really clean newsletter list or lists, you don't have to worry about that so much. So, I do think, starting in the newsletter space is a really low budget, friendly way to start growing audiences, and it's really great to use as a gut check to see what is resonating. You could look at your open rates, you could look at your click to open rates.Chris:Again, you can monitor what the churn is and stop to see if what you're producing is causing people to drop off for good, so on and so forth. So I do think, for publishers where it makes sense that is a great place to start. You can obviously acquire new users through a bunch of different audience development tactics, whether it's on site widgets or modals, or do some small paid spend to try to bring folks in, and do the sweepstake partnerships as well. Again, obviously I'm a little biased, just because that is part of my background. But again, over the years, newsletters, again, I know they're not the sexiest platform to talk about, but they have been the most consistent in terms of performance and really bringing your most loyal and engaged users from that platform.Stephanie:Yeah, I completely agree. And, you also get access to quite a bit of data that you don't on other platforms, and if you can figure out how to properly engage with them, you could have newsletter subscribers for years to come, which is everyone's goal.Chris:100%. Yeah. And, I think even to take that one step further, you could even start to get more and more personalized where you get to a point where you're launching a newsletter to half a million people, and no two newsletters are alike because it's all based on past user behaviors that you were seeing within email and the dot-com, and again adjusting that based on different predictive intelligence tools. So again, I think 100% there's a lot there, and if done correctly, and go a long way. I mean look, this has been tried and true in the space. We see a lot of folks who start there, we're even seeing in the news media space a lot of journalists, and editors, and things like that backing off from the larger brands, and going this newsletter route to get their word and opinion out. So yeah, I think email is here to stay, and it's going to be a huge piece of the puzzle moving forward.Stephanie:Yep. I agree. So, you've been in the media world for a while, I think I saw at least back to 2012, maybe even before then.Chris:Yeah.Stephanie:I went as far as I could on your LinkedIn, I think it cut off.Chris:No, you got it. Yeah. I have been in media basically since the day I got out of college. So-Stephanie:Okay. Well, this is the perfect question for you then. What do you think the future of online commerce in media look like? Maybe in 2025 or 2030, what does that world look like?Chris:Yeah. So, I think it's going to be an extension of what we talked about a little earlier about this universal cart experience, and turning digital publishers into this space where audiences can come and also feel comfortable making those purchases. And again, not being bounced off to third party sites, and really being able to start building an even stronger shopping relationship with your audiences, because again with a universal cart experience, also comes a lot more first party data where you could, again, focus on more one-to-one relationships with your audiences, again, specifically in the shopping space, which I think is key.Chris:And, I don't foresee a place where merchants are going to have a huge problem with this, because, again, you're just helping to legitimize their product. Like your previous guest said about increased conversions. I think that's another huge piece of this puzzle. So again, it's really just now, again, bringing this all together, this whole 360 approach and saying, "Look, you're not just coming to us for flat inspirational content, you're now coming to us for the inspiration, and the ability to take action immediately." Again, versus being bounced off to one, two, three other platforms depending on which platform you're on, like your experience with Instagram.Stephanie:Yep. Yeah, I love that answer. Really good. So, now that we're talking a little bit about the future, what do you not understand today that you wish you did?Chris:What do I not understand today that I wish I did? That's a that's a good question. So, as it relates to commerce?Stephanie:Yep. Or the world, where you're like, "I really just wish I knew more about this." But yeah, it could be a commerce one, that would be cool too.Chris:Sure. I would say, I think not so much about not understanding this, but more not understanding why it's not better. And, that goes back to, I would probably say, affiliate data, and what that data looks like, and what partners have access to, or don't have access to. Obviously, being a part of many different networks, and merchants being on all different networks and so on and so forth, it becomes, quite difficult to manage all of that data coming in, and really having a platform that can easily bring this all together in a unified way. We do have a really strong partner that we work with to aggregate a lot of this data. Again obviously, it's never going to be perfect, because you're pulling it from all different places, and you have to understand, "Well, how does this platform leverage conversion rates and click through rates, versus this platform?" And again, just like, "What do those measurements look like?" And, the methodology behind them.Chris:So, that becomes challenging. But, I do think that's probably one of the biggest things that I just wish. And, I know it's not easy, hence the reason why it hasn't really been done yet. But, finding a more universal way to bring all this data into one data warehouse. Again, we were working on some stuff along those lines, but just high level, just generally speaking in this space, I do think that's one of the more challenging situations that a lot of digital media folks are in when it comes to with the shopping space.Stephanie:Yeah. That's a great answer. It does feel like a lot of technologies in general started out in that way. Very chaotic, things are everywhere, data is everywhere, and then things eventually end up in a dashboard, or it starts coming together in a more useful way. So, I hope that world comes to be in the future as well.Chris:Yeah. I mean, look, at the end of the day, that's only going to help all parties. It's going to help the audience, it's going to help the media company, it's going to help the merchant, so there's definitely reason to really get this right. But again, then, to do a bit of a 180, I think that's why you're going to start seeing these universal cart experiences take off more and more, because it does make that a bit cleaner in terms of what you're going to have access to and when.Stephanie:Yep. Very cool. All right. So, we have a couple minutes left, and I want to jump into the lightning round, brought to you by our friends at Salesforce Commerce Cloud. They're the best. This is where I'm going to throw a question in your way and you have a minute or less to answer. Are you ready?Chris:Let's do it.Stephanie:All right. What's Up next on your... Well, do you have Netflix? I would say Netflix, and I'm like, "He's going to be like, "No.""Chris:I do.Stephanie:Okay. What's up on your queue? And then, you can also tell me what's up on your Discovery queue?Chris:Fair. So, I'll start with us first.Stephanie:All right. Go ahead.Chris:And, I think this is so obvious, but huge 90 Day Fiancé fans. And, I will say my wife actually started that. I wasn't always, but she was like, "Come on, we got to watch it." And, this was a couple years ago. And, once I started, we have been heavily invested ever since. So, from a brand standpoint, we're 90 Day through and through. So, I think again-Stephanie:I like it.Chris:Yeah. Probably obvious to a lot of folks just because of the success of it, but that is our thing there. And then, she's also actually a huge fan of Discovery ID, it's her favorite channel by far. So, we got both ends of the spectrum there, right?Stephanie:Yep.Chris:Discovery ID, the DLC. But again, that just goes to show the strength of our portfolio. And then, on a personal front, I would say, what we're actually currently watching is the Borgias on Showtime. If you haven't watched it, I highly recommend it. But, it's three seasons, so that's good for me. I'm not a huge binger, but I can get through a three season watch, so we're currently in the middle of that.Stephanie:Cool. I have to check that out. Yeah. 90 Day Fiancé, so I have a twin sister, and she's obsessed with that show, and she's been telling me I need to watch it. And, I've been like, "No, I'm not watching that." So, now that you say you also enjoy it, maybe I'll have to want to check that out.Chris:Yeah. Come on. It's only fitting now. You got to at least give it a shot.Stephanie:Yeah. I think I will after this. That'll be the rest of my day.Chris:Perfect. So, I've succeeded tonight.Stephanie:You did-Chris:I converted someone.Stephanie:You can tell everyone, "I got a conversion."Chris:Exactly.Stephanie:What's Up next on your reading list?Chris:On my reading list. So, this is also probably slightly depressing, but I'm actually currently reading the Plague.Stephanie:That's [inaudible 00:49:47]. I mean, I don't even know what that is, but I'm like, "No." I mean, is it good?Chris:Yeah. I mean, so far, I'm only maybe a quarter of the way in. it's just eerily similar to the situation we're currently in, and obviously this was not written recently. This is old Camus. But yes, so that that's what I'm currently reading. So, not exactly an uplifting read, but I do think interesting to say the least in seeing some of these parallels that, again, just six, seven months ago we thought were just crazy things you would read or watch on Netflix.Stephanie:Yeah. Well, if you enjoy the full read, let me know, maybe I'll check that out.Chris:Will do.Stephanie:Next up, if you were to have a podcast, what would it be about, and who would your first guest be?Chris:That is interesting. If I had a podcast. For me, I think I probably wouldn't fall into the current podcasting world that pulls a lot of talent from different areas, and makes that the centerpiece of their podcast. I would much rather try to get in the weeds with folks who are making a difference on a local level. I think especially in this political climate, I think that sometimes gets lost that we think it's only the top that matters, and nothing lower does, which I think is completely false. I think everything starts at the local level. So, I would love to give more exposure and light to those folks who are doing the dirty work on the ground which, again, sometimes gets lost in the standard media cycles, or across social media for example.Stephanie:Yes, I love that. It's also something we're exploring here at Mission is local level podcasts, because I think that's what people are leaning into now. They have lost that also a sense of community with everything that's been going on, and you might want to know what your neighbors or community is up to, and also what they're doing, like you said, on the ground level. The next one-Chris:100%. I think it's super important. Go ahead.Stephanie:Yeah. What does the best day in the office look like for you?Chris:The best day. So, when that was a thing-Stephanie:When you went to the office, and you weren't just in your house in New York.Chris:Exactly. Honestly, the best part about that is, being able to... And, now I feel it even more, is having that change of scenery, and being able to have those face-to-face interactions with folks. I recently read a study where, I think it came out that people were actually working longer hours, and having more meetings, while working from home, because they don't have those passerby conversations in the hall, or going in and out of the restroom, and so on and so forth. Which, again, I don't think people appreciate until it's gone. And for me, that's been a huge piece of the puzzle that's been missing during these times is that, human interaction. I think everyone wants to think that working from home is the future, I'm just not sold on that yet.Stephanie:Yeah. I think the flexibility, maybe, but I think a lot of people are eager to get back and see their coworkers, and have coffee together and whatnot. So, there'll be pent up demand, as economists would say.Chris:Exactly.Stephanie:All right, Chris. Well, this has been such a great interview, where can people find out more about you and all the fun work you're doing at Discovery?Chris:Sure. So personally, you can find me, Chris Mainenti on LinkedIn, and we can connect there if you'd like to chat further. But more importantly, if you love our brands, you know where to catch us on TV. And then, similar to dot-com, HGTV, Food Network, TLC, Travel Channel. We're everywhere and we look forward to continuing to serve our audiences wherever they are, and really helping them through these trying times that we're all in.Stephanie:Yep. And most of all, go watch 90 Day Fiancé, everyone. I mean, I feel like you need that fun.Chris:Exactly. For the handful who haven't yet, including you, obviously.Stephanie:Yeah. I know. Such a veil. All right. Thanks so much, Chris. It's been fun.Chris:Likewise. Thanks so much again. Bye-bye.

On BIV Today... Resonance Consultancy president and CEO Chris Fair discusses what B.C.'s summer tourism season could look like as the province proceeds with its post-pandemic recovery plan. 

Join us for Episode Four as host Paul Tremlin and Chris Fair, Youth Baseball Director for Extreme Baseball and Softball Club, deep dive into the importance of coaches developing athletes and the role that competition plays in the overall development and success of athletes. Special segments include the importance of coaches continuing to educate themselves, how to build a practice plan for athlete development during the season, and if you can still win and be a 3D coach.

Join us for Episode Three as host Paul Tremlin and Chris Fair, Youth Baseball Director for Extreme Baseball and Softball Club, dive deep into what it means to Run The Marathon in youth sports. Chris then continues to dive into phase one of building youth sports the right way, as well as shares his tweet of the week featuring Matt Lisle, talks 3D Coaching, and more!

Chris Fair, President & CEO of Resonance, joins the Destination Marketing Podcast to talk about the World's Best Cities and premier the new list. Topics discussed include the methodology for the World's Best Cities rankings, the core six categories, and focusing on the customer experience in your destination.  "We tend to think 'more is better'. We've been conditioned to attracting more visitors, and all the metrics by which we're generally judged are quantitative. I think there's a real lack of understanding or appreciation for the qualitative side of the destination side. I think to date, we would all agree the customer experience or the visitor experience is important, but we don't know how to measure it. And that's really what we're trying to address here." - Chris Fair on focusing on other factors than just the quantitative side of things. 

Chris Fair helps places — communities, cities, regions — think about the future.That thinking drives the design of everything from the branding of a destination, to the design of streets, buildings and other public spaces, and what is put in them in order to make a city not just liveable, but loveable.Fair’s belief? That if you stop looking at how people behave, and begin understanding how people may want to behave in the future (in part through creative disruption, and of course big data), you have the best possible chance at helping a place realize its full economic potential. Beyond tourism, this applies to business attraction and retention, not to mention drawing in the talent that keeps economies bumping along.In some cases, this approach — thinking about lifestyle and what sorts of experiences might resonate with people — can actually save a city. In his opinion, this was the case with one of the most interesting revitalizations of a downtown in the world. (For that answer, you’ll have to listen in.)In the process of explaining his placemaking approach and the rationale behind it, Gord gets the Calgary-born creative to reveal how his company, Resonance Consultancy, was inspired in part by his passion for skiing and his eye for opportunity; casting aside creative writing two decades ago to leverage the Intrawest investment in Mont Tremblant into his own company, a bilingual media outlet. Today, Resonance has an international footprint and is known for helping translate contemporary lifestyles in a way that local governments can “get their heads around”.Some interesting questions are posed, and not necessarily resolved in this conversation: Is Vancouver a resort city only for the rich, or a real place? Does liveability necessarily equal prosperity? Should we make Vancouver less attractive so more people can afford to live here down the line? How do we prioritize public amenities so they don’t just result in elite experiences?And of the superstar cities of the 21st century, where does Vancouver rank? Read more »

Let’s dig into the data! In this episode, we discuss the findings from the Future of Cannabis in Canada Report – a new research study from Resonance Consultancy and Valens. How do Canadians feel about cannabis since legalization? Where are we going next? We’re joined by futurist and Resonance President, Chris Fair, to get answers to these questions and more.For more on this episode, and to download the full report, visit: https://www.valensgroworks.com/news/extracted-episode-13-the-future-of-cannabis-in-canada-with-chris-fairFor more on Resonance Consultancy, visit: resonanceco.com Thank you to our podcast partner: Leafly.caConnect with us at: extracted@valensgroworks.com

Chris Fair of The Laser Comedy Show joins us to talk about his unique, visual form. He also discusses building tension, the difference between an audience of adults versus and audience of kids, how studying sketch will improve your improv, promoting shows, and being heckled by children, as well as bands that are actually one […] The post The Laser Comedy Show | Next At Bat: Episode 116 appeared first on NoisePicnic Podcast Network.

Sarah and Chris talk about lasers, passing out drunk and more! Chris Fair is an improvisor and creator of the Laser Comedy Show www.lasercomedyshow.com. You can follow him on Twitter at @laserimprovshow. He'll be performing at the upcoming Chicago Improv Festival in May.  Sleeping with Sarah is a podcast where comedian and narcoleptic, Sarah Albritton interviews people in her bed. They talk about sleep, comedy, and relationships. Visit www.sleepingwithsarah.com for more information. You can follow Sarah on Instagram @sarahalbritton & Twitter:@sarahalbritton or visit her at www.sarahalbritton.com. Music by Josh Bryant. You can view the video version of the podcast on Sarah's Youtube channel.