0:14Justin Norris: You know, the classic way of describing rev ops is people process and platforms. And while that may not be a perfect formulation, it's a pretty accurate description. Of what we do, what they don't tell you in RevOp school is that the people pillar is by far the hardest one to manage building and systems, creating processes, you know, those are challenging, but they're ultimately rewarding things to do. You get a big payoff at the end when there's a finished product and you have a lot of control. On the other hand, getting other people to actually do something is
0:45a whole other story, and it can be. Maddening to work with revenue teams that seem determined to do anything but follow the process that you've designed I'm, not suggesting anyone is out to get us, but it does point to the fact that enablement Is a huge part of our job and rev ops. And it often doesn't work very well. We create documents that no one reads. They sit in knowledge bases that no one visits. We spend our time responding to Slack messages from confused users or sending chatter reminders, asking people to just please follow the process for like the 500th time.
1:18And I may be exaggerating a bit to make a point, but not by much. So today's guest thinks that there is a better way to do software enablement. And he helped found a company to deliver on that promise. It's called Tango. And our guest is the company's COO, Dan Jovachini. Dan, so glad to have you here. Daniel Giovacchini: Great to be here, Justin, and, really well articulated opening on, a lot of the challenges I think that, you know, folks face out there with, with change in management, and that's exactly what we spend most of our days thinking about. Justin Norris: I spend a lot of my day dealing with those exact challenges.
1:50So they hit close to home. and I'm wondering, Dan, as I was looking through your background, I saw you spent about seven years in the VC world. So before we pivot into Tango and enablement and all that, I want to be opportunistic and just get your perspective, putting your VC hat on again for a minute, what is going on? You know, we've experienced a fairly strange. reset in the market over the past few years, it's impacting a lot of SAS companies, things have really changed. The old playbooks don't work the same anymore. What are you thinking about as, as kind of a founder?
2:22What should other founders be focused on to survive and thrive in this environment and that kind of thing? Daniel Giovacchini: Yeah, it's a great question. I mean, you for so long, it seemed like there was finally a sense of normal and bull market and, you know, it was just bigger fundraising rounds happening year after year. And, and then suddenly we, we hit this new bear market. and some ways. Tightening and economic slowdown. it's part of what precipitated that, but it was also, we were probably just overheating on, a number of areas of, of software spend in particular, and,
2:57uh, markets that kind of founders and VCs both looked at and said, Oh, we've seen this happen somewhere else. And why can't it happen here? Like the Uber for, for X playbook or something for every market. And, kind of where that got us, I think is starting to. Really get back to me. Think about the customer, what are their organizational level challenges and problems? And, you know, what are their operating hurdles that, that they need to get passed and no matter if you're a founder, your company, you know, working on
3:28a, an end user focused tool and the marketing stack, or if you're something that helps, you know, org wide for HR. You really all have to tie back to some organizational level initiative. And if you can't map to a customer OKR, you should stop and think about how you can. and so, you know, I think that, slow down in funding and, difficult fundraising environment kind of 2021, uh, 2023 started to reinforce probably some healthier
3:59innovation behaviors and healthier, really like product marketing and sales pitches from, from founders and companies. And, then I has obviously just become the theme of the moment and. It's, there's never been a better time to be insanely curious about what's possible, if you're an operator within a company and, and all these new tools and technology that's available, or if you're, you're a vendor yourself or a founder or VC and think about your product and, and your longterm, value creation path, right?
4:31at the same time, that's a lot of noise. And, and so, you know, how do you cut through the noise? Make sure that you're, you're building a product or a business or a service that matters, for a long time. that's getting back to that probably, you know, healthier behavior of saying, Hey, how do we map to real organizational level challenges and problems for our customers? Justin Norris: it 10 years, you know, it was almost like a crazy, drug trip or something like that. And now things have kind of come back down.
5:02to reality in the sense that, customer acquisition costs that are completely untethered from business fundamentals, we're sort of normalized software purchasing behavior that, doesn't really make sense economically. It's kind of normalized. So I definitely see what you're saying as a, as someone who's often a software buyer and is having to make business cases for software. The rules of that game have definitely changed for me. And I think for a lot of my peers, how have you found the discussion around your category of, kind of like enablement and, digital adoption, have
5:36the dynamics there changed at all? Daniel Giovacchini: You know, they really have changed with AI, especially in the last year or two here. And, chat GPT came out and a lot of founders and a lot of VCs looked at the underlying models, chat GPT used and said, okay, this is amazing. What else is possible? And, you know, I'd say we were still in the middle of a big discovery phase here for where's the application layer value going to accrue and, where are we going to start to see, the massive productivity improvements that, people
6:10are sensing that are possible, but, you know, we're still waiting to come to fruition in a lot of cases. And, a couple of early examples of, areas that you've seen the impact right away. certainly data analytics tools, certainly customer service conversations, and you can point to vendors and those categories that. I've started to do just show ROI cases that have kind of never been seen before. but as you think about enablement and process and, you know, a lot of the world that both you and I spend a lot of time in, what you're
6:41starting to see is potentially two paths to take an enablement. And one is, somewhat, Search focused query focused, and you can think chat, GBT. You can think chat UX. You can think, glean as a, company that's, been more, more and more talked about on the, the venture scene, but okay, we can be really information centric and, center our enablement initiatives around, unstructured text knowledge.
7:11Right. And we're just going to bet that. Operators are going to know the right questions to ask, and they're going to be able to go retrieve answers. And we were able to suddenly index all that information in a much more powerful way, and AI is going to help serve results, you know, and that's going to improve how people work. There's another path that's probably more, We're going down, right? Which is just in the flow of work enablement. And so that's almost betting that, Hey, instead of being information centric, let's be process centric. Let's think about. Where a user operator is spending time, what tools they're in, what
7:45information might they need, when might they need it, and let's try and serve it to them proactively or make it available at their fingertips in such a way that We're not actually requiring them to go and, understand the right query to be asking to unblock themselves or to do their job better, to find answers to serve a customer, you know, kind of whatever it might be. So I think that's kind of where. there's two paths in front of us in the enablement space. And you're seeing companies take kind of two different approaches
8:17if you want to be simplistic. And, you know, there's going to be a place for both, but it's sort of within, if you're an operator, you kind of start to think about, you know, which, which one makes most sense For your situation for your company. Justin Norris: You know, when we think about the sorts of rev ops use cases, we often encounter CRM enablement or some other sort of tool enablement, or, you have a revenue or marketing sales CS user needs to do a certain thing in a certain place. The, in the flow of work model just seems commonsensically the way to go, because
8:50nobody cares to go, like you said, ask a question or know the right question. There's so much more room for error. There's so much more user discretion. Why not just show them what to do in the moment that they need To know that information most and in the place where they are. And we'll get a bit deeper into tango itself, but I'm just curious, like what's the, at the market level, what's the argument against doing that? Cause it just seems that is the way that you should do it to me. Daniel Giovacchini: Yeah. I mean, different information types, right? So there's a lot of the unstructured conversation that happens about product,
9:21customer market, competitor, internal strategy, decisioning, and a lot of that just fundamentally lives within. A slack, a teams, a knowledge base, email. and so, you know, there is golden knowledge that lives there. And you know, how do you potentially surface that in ways? And if we think, Hey, you're a seller and you're talking to a new account for the first time. and there's been some new, product developments that perhaps you should
9:55be aware of for that account, or there's been some new competitive Intel that's been discussed somewhere. If you actually want to surface that, that information, you know, for that seller, You're going to want to potentially search against a lot of these other, knowledge repositories. And, you know, it's not to say you can't serve that up, in the moment. But, right now we're in the flow of work enablement where that technology is. And that that thinking is it hasn't quite incorporated all That general market company, customer information.
10:26So that's probably just still a bridge that kind of needs to be crossed technologically to start to make that all available. But I totally think, the end vision, if we put our heads together, it should be less proactively serve this up when people need it and not require them to search for Justin Norris: Got it. Cool. Well, we'll dig a bit more into that, but maybe first we'll just turn back the page a little bit and just talk about founding a company, starting with this idea and how you go from there to MVP.
10:57Daniel Giovacchini: There's a lot of thoughts and literature out there on founding a company and, the best way to go about early product development, problem discovery. You know, there's a couple things that I think have stood true as far as, the test of time And just fundamental truths about good innovation practice. And I think there's a couple of things that are pretty outdated. So, for starters, first trap to fall into is feeling like you have a great idea and you have a solution that the market just needs and you Go just build it.
11:30it's how a lot of founders and it's how a lot of stories get told about companies is you have this sudden golden insight about something that, you or others have experienced and you just go build it. It's so often not the case. And you go look at the actual evolution stories of, companies in their earliest days. And. You can start with an idea, but it's going to iterate so much. It's going to change based on the first time you go and actually ask
12:00about, what are those organizational level OKRs that you have? What are actual problems that are top of mind, for this ICP that you thought you understood what, other competitive products are out there that maybe you weren't aware of. And so, the quick lesson there is just. You should really think about entering a problem space and not entering into building a solution. And the more you can be curious about your problem space early on and be open and flexible to iterating and serving true North on your compass as
12:32how do we provide the most value for customers that, you know, they uniquely do not have somewhere else, that's, what's going to really guide you down the I think the most successful path. the other one is, is related to building too. And this could apply for products or services, but lean startup method came out and this minimum viable product concept came out, pretty early on and, sort of entrepreneurial lore. And. What still stands true about it is you should absolutely be going to
13:03get feedback as fast as possible. What has changed is you should not be launching half baked versions of a solution. So, you know, as you get through that problem space discovery, and as you figure out, something that you have a strong hypothesis is, is going to be a game changer for, for your customer, you really need to take advantage of your launch moment. And this is due to. the cost of starting a company of creating a product, all of that has, being driven down to zero.
13:33And, you know, even with AI, right, people are going to create products and software and services, you know, way faster than they ever had historically. And if you're a, an individual contributor, if you're a buyer, user champion, no matter what you are at a company, there's just. Hundreds and thousands of products that you can be going to try every day. And, the excitement of something new it's very much become noise and less become a delightful moment in your day. So if you're going to come out and launch a new product or service to the world,
14:06really try and get your launch right. so we read this article early on from first round review. They put out amazing content, you know, especially For builders of companies in the early stages. And the title of the article is don't serve burnt pizza. And it hit us just at the right moment in time. And we sort of made it, one of our, manifestos, but, think about creating a minimum lovable product, not just a minimum viable product, and, that means first impressions really do matter. take the extra six months to really get your product marketing, right.
14:39Put that extra design touch if you are a product company to really think through that, that service offering. so when you launch, you can take advantage of that and that early momentum is what you're going to need to propel you in those early days to then be on the path to, whatever it is, securing more funding or reaching more customers or hiring more of your team. Justin Norris: You know, that narrative around, iteration has been a constant, I think with every founder that I've spoken to that has come on the show. I think Eloqua started as a chat product.
15:09Marketo started as some sort of AdWords interface. Like the ideas changed really drastically. I'm curious, how did you know when you had iterated to the place where you had something that was a minimum lovable product, as you put it? Daniel Giovacchini: Yeah, awesome. So, we actually set out to solve this. Be curious in this problem space of learning on the job and solve this, kind of, problem we felt was out there of just, it takes too long to get good at what you do. And this is really from a, tactical perspective of how do I be successful
15:44in my new role at a company? And, we did more discovery and we, we kind of traced this, path to, well, learning the tools that you use is actually this like Kind of fundamental barrier to contributing to job performance and, getting past that ramp or nesting period into, you know, okay, I'm actually taking inbound volume for the first time, or I'm, you know, answering chat conversations, you know, that are real, real live, live customers.
16:14but we. You know, for us, it was, okay, we think there's an interesting hypothesis or idea around the best people on your team have figured out something unique to your company about how to be successful and how they work. And, we borrowed this a little bit from gong and chorus in the. The sales tech stack where they figured out that, you know, Hey, there's a lot of golden insight for teams and companies in the conversations of your top sellers,
16:47and they're doing things on those sales calls that everybody could learn from. And so, we went around and got curious about, Hey, learning on the job is really hard. Is this a problem, for you as a VP, is this a problem for you as a new hire, we got a lot of certainty and learned that, Hey, this would be a problem worth solving. And then we had this hypothesis of like, if you could actually understand what makes Susie from Scottsdale so good at what she does, and then make that the basis for, training and enablement, would that potentially be interesting? And, we.
17:18Kept pulling on that thread. And, so we did get into product development and what we realized is that, you know, whoa, this, wasn't just something for customer support or for, you know, BPOs and call centers where learning the actual, click process or click stream of how do I navigate my tools. Was valuable and actually spread to way more functions. And it was way more of a horizontal. Problem space. Then, then we kind of initially realized, and, the moment it clicked
17:51for us that we were close to something that was minimum lovable was we went and did these controlled pilots with five or six different teams at, five or six different companies, different functions, and, it was free. we tried to charge initially, but that was even difficult. And so we just made it free. And it was the moment where, instead of us just like begging people to use it, they started to use it on their own and they started to ask about, Hey, would this be possible? Would there be more features here?
18:21Hey, could I get somebody else on? And so, you know, we use this like kind of controlled beta environment to sort of assess some of that minimum lovable component. and, we said, okay, we think we have something here. Now let's take the three to six months extra to go get this ready for a launch. And, you know, we're going to make a bet that we can really land a first impression based on these early learnings with a broader audience. And we were fortunate that, that we did. Justin Norris: When you mentioned those horizontal use cases, I'm curious, what are some good examples?
18:53Cause was mentioning before we hit record, I've used Tango a few times in my company but it's been mostly focused on, software navigation, click stream stuff. Like you said, where would you go from there? Daniel Giovacchini: Yeah. So, You kind of look at it and we realized that like, Hey, the target market for trying to teach other people how to use software, it's really anybody who's tried to take a manual screenshot, paste it into Google doc and write out some steps and send that to somebody to tell them how to do something right. Or in a Slack thread or in a, you know, email conversation.
19:27And so. we really thought it was like going to be customer support and, potentially call centers again. But, it was every function, from engineering to, consultants and consulting firms to HR professionals. You're trying to learn how to use the performance management software. And I guess, we just didn't totally realize that this friction really does exist as, as much as. software has, improved, the ability to go get tasks done.
19:59we take it for granted and a lot of cases, and, especially from an ops and enablement perspective, you know, people are very familiar with tools, very, very tech savvy. Um, you know, especially if you're in a venture backed company, but you think about other people who choosing technology is not the central component of their job. and it's frustrating and people don't want to, spend the time, going and learning and the help docs, how to use the software, navigate it and try and. trial and error on their own.
20:31so, that's kind of what I was referencing when, you know, horizontal, it's just this, peer to peer teaching of, of how to use software Justin Norris: Across more functions, more teams, sort of anywhere in the organization. Daniel Giovacchini: Exactly. Justin Norris: so you have that magic moment where you're like, oh, this is something that people want to use And I can imagine that's a very interesting feeling as a founder who's gone through this Sort of hero's journey of building a product and iterating on it Then you start to think about go to market and how to commercialize it at a at a bigger scale What was the dialogue there?
21:04Daniel Giovacchini: you basically have two to three choices when you're launching a product and thinking about go to market motion today's day and age. Right. And. you have a bottoms up version, where you say, Hey, you think anybody can use this? You think that your products can somewhat teach itself. And then you have a top down version where, You're saying, Hey, the value of this software, the benefits of this, service need to be explained.
21:34They can't be taught or discovered. and then maybe you have something in the middle where, there's interactive demo experiences started to become, more popular, and you can use that to divert people into sales conversations or a self serve journey. So, maybe that's a new one. That's, kind of emerging more, but, you know, for us. We looked at it and, again, we had initially thought, okay, this is very targeted, at a couple of specific functions. but when we realized that, you know, Hey, this is more horizontal than we
22:05thought really the litmus test for should you go bottoms up or should you go. Horizontal PLG is how quickly can you provide time to value and get users to an aha moment? that's basically referring to Can they get something of value from using your product in a single player fashion? in more or less 60 seconds or or under right around there and if you can you're gonna see a lot of benefits of bottoms up and plg You People are going to go in,
22:39understand your product, get something from it, be so wowed that they're going to want to tell people about it. they're going to want to potentially come back to it and think more about how they could use it in a bigger fashion. make it part of their routine. If you can't, then you're very likely just to get a bunch of tire kickers early on. Maybe they're interested in checking it out, but you're not going to get people hooked. and that could be for a couple reasons. It could be. Do you have a fundamentally multiplayer experience? Do you need multiple people involved?
23:09You know, a team to actually get value from your products. If you do, it's going to be very hard to convince that first person who finds you to invite a team to try something out. it's too much to ask without having ever proved anything to them or given value to them up front. or, if it's not multiplayer. But the product experience actually just fundamentally is more complex or requires more configuration or set up, then you're really going to need to teach them why they need to do it.
23:39And super unlikely you're gonna be able to do it in a self serve fashion. You're gonna want to talk to them and have somebody really experienced sell the benefits and get them into a trial or a sales process. Justin Norris: So you, I'm, I'm making an educated guess, the bottom up motion is where you land. At least that's how I've encountered your tool. And I will say to your credit that it is pretty easy, to go through it. Maybe it's a good time to just, I'll describe to you my experience as a user of a tool like this, like what I did. Tell me if I'm wrong, but, you sign up, you go and you hit
24:11record, you do a thing like in CRM. Click, click, click, click, click. And it just captures those steps for you. Like screenshots, each one sort of automatically describes what you're doing. And then you can go through and beautify the descriptions and tweak them. But, that to me was the aha moment. It's like, Oh, it just sort of captured it all right there. And this kind of, magical way and created a, an experience for the user consuming that, that I think is objectively just much better a Google doc with screenshots or even like a loom, which I also really like, but a loom you have to like kind
24:42of hunt and search and start and stop. And this really does have it broken out in a very nice way. So is that the typical experience that your users are going through what I just described? Daniel Giovacchini: that's the typical experience. a hundred percent of our users go through that exact experience you just described. And, what we intentionally designed into that experience actually borrowed on a lot of game design principles. And we recently actually put out a little. piece about this, but there are specific mechanics built in to ensure that you as a user are going to get something of value.
25:15Within that, that 60 seconds and we're not going to let you go necessarily on side quests early on. So we're not actually going to give you power user features as you're going through and capturing your process. We're not going to let you edit it while you're in that recording session. We're not going to let you, turn on audio video and actually make a video out of it. It's very intently designed to get you to. A near finished state or an actually over 60 percent of cases, it's an already
25:46finished state, really without ever. Getting tempted to do anything other than, do your process with tango capturing it and then we're showing you the process you're capturing and we're sort of teaching you how the product works as you go through that. first capture experience. So, it's very intentional. We put every user basically through that capture journey. and they, at the end of it have something of value and they've learned how the product works. and that's part of what fueled our, bottoms up motion and why
26:17a lot of people refer to it as very intuitive and easy to use. Justin Norris: And the challenge I imagine, or I'm curious about is, so if I take my company, for example, like I said, we probably have one or two or a small handful of tangos in our, or whatever we have obviously underneath, under the free plan of what you offer, what's the moment of truth that is going to get a user to go from that stage to actually, we need to put up a credit card to get the value that we're looking for. Daniel Giovacchini: Yeah.
26:48Great question. So I mean, the first aha moment is, is getting you excited as a free user. It's, capturing your, first workflow on your own software. And, number one and sort of our. Activation journey, there's, sort of two separate paths we want you to go down. You know, if you're a smaller company, if you're a freelancer, you're an SMB, we potentially want you to, swipe your credit card and become a paid user. we strive that say, Hey, if you're a power user, you know, 10 percent of the free users in that market, we think should sort of, be paid users.
27:21And, the ones where we want that to be true are if you have needs around branding or if you have needs around security. And so we say, Hey, if you're using this in a power user fashion, it's likely that you're using Tango. To build, your own service or product, right. Or to like offer tango to a customer, or you are using it within. Your team in a way that, you really do need, more privacy or more branding.
27:54And if you're just otherwise using it, casually, or, it is more of a, a one off thing for you, then we want it to be free because we want you to share more tank creates more tangos, share them, and not feel inhibited. So privacy and branding are the two where we want you to pay as a SMB or, freelancer user of Tango. If you're within a larger company, we want to convert you on what's possible with your team and within a larger organization. Software training initiative.
28:24So if you're creating documentation, it's likely because there's some bigger effort happening at your company. You're either bringing on new hires, you're rolling out new software, you're doing a process improvement project. You're teaching reps, I mean, you know, you're in rev ops, you're teaching reps about how to use, some new functionality, some new field perhaps within the CRM. so we want to then convince you that, Hey, there's a really powerful. Team based experience here where, this is our, our newest offering. Actually, if you actually get your whole team on board, we're going to let you
28:58pin these updates and these processes right on top of the software that people are using, and it's no longer gonna. Be a link that you send them, in Slack or, living in an LMS or a knowledge base. So, you talked about, you guys use it as a free user. that's great. We want you to get excited about, what Tango can do. To potentially help here and there with, the process. at some point we would want you to be convinced that, Oh, Hey, we do have these larger software training initiatives and there's suddenly a
29:28powerful team based experience where we should talk to the Tango sales team about how we could set that up on top of our CRM or on top of our, core business software And benefit even more. Justin Norris: So let's pivot in a bit deeper into that product experience because that what you just described that overlay Wasn't something I'd seen before I saw it on your website just well prepping for this interview and I thought oh, that's really cool it's kind of like those like onboarding wizards that you get sometimes when you first sign up for a product But those
29:58are often very annoying because they constrict you a little bit and they you must feel like you're not Like they're mediating between you and the product. Whereas this, at least in the example that I watched, it was quite fluid. Like it's actually, just guiding you along through what you need to do. So maybe just talk about that and, what you've seen so far, perhaps in the market or what your vision is for how people would implement. Do Daniel Giovacchini: Yeah, totally. So we're big believers that for learning process or learning software, you should learn.
30:29While you're using it, you should learn, actually in, this case, the CRM, right? So the alternative, the status quo, you know, maybe what a lot of folks do today, which totally understandable, but what it is, is you're sending out a Slack update, you're jumping on top of a, team call and screen sharing a new process, or you're sending out a loom video to talk through something. And people are going to hear it. perhaps a couple of people who are particularly good with technology or savvy, we'll pick it up and there's going to be a lot of
31:01people who kind of just ignore it. They're going to forget, they're going to listen with one ear and they're not going to take the new tool or the new process and incorporate it into their workflow. what do we want instead? Well, we basically want that the first time you're going to go, you're going For example, you're creating a new deal in the CRM, a new opportunity, and, there's a new field that you need to fill out. We want you at that exact moment to, learn and, be more or less instructed that, Hey, this new field has been created.
31:31here's exactly how to use it. And, All you have to do is, and in our case, hover over this, tool tip or, have this, this process appear, you know, for the first time you're on one of those sub pages or page, we do a lot with kind of URL detection in our product. And that's when you're actually going to see it. And see, okay, well, I now know that this is exactly the new process update and you're far more likely to incorporate that into your routine, having learned it right in the moment that you need it or should be doing it.
32:02so that's the kind of fundamental. argument for, people learning software and process retention and compliance and adherence is going to be so much higher if it's right there when they need it versus, done separately and hope that somebody remembers. Justin Norris: you have any data, like a data point around, adoption is X percent higher or like how much more quickly someone could learn a process if they're doing it this way versus reading an article in a knowledge base or seeing
32:33a synchronous training like three weeks ago and then they go to do it and it's already been forgotten at that point. Daniel Giovacchini: Yep. So kind of the easiest thing to measure. Has been with kind of net new software rollouts and try and compare, either to a similar rollout at the company that did not use Tango or perhaps the same software rollout at a different company. And, I'll mention a case study that, that we just did to help illustrate, but it was a large workday rollout. So this is more HR software, less CRM, but, it's a 1500 person company
33:04and had to roll out workday and, teach everybody at the company. Okay, here's how you use workday to find your pay stubs, submit for PTO, uh, enroll in dental insurance, et cetera, et cetera, et cetera. And what they found, with Tango by putting the instructions kind of exactly on the screen where people needed them, that they saw a 90 percent reduction in internal I. T. Support ticket requests and basically going back to those owners of the software and asking for help or asking for clarification.
33:37so that's one way to measure it is sort of saying, hey, post rollout. in this case, it's helpful that it was HR software because it's stuff people had to do for employment. you know, in a CRM case, the danger is that you actually don't get asked those questions for support, right? You don't actually get people circling back. You just get people who ignore you and, you find out, you know, later on that they weren't doing it. but we, saw it sort of 90%. Reduction in support tickets with this customer. And, that basically goes to, prove that, when the information is, right there, you
34:07are that much more likely to, successfully incorporate that new information and, completing your, task or your process. Justin Norris: One of the things that I thought was novel was it seemed that there is some, kind of what, at least one of your AI features. And that there was some intelligence to allow for flexibility in the process that the user would carry out. Cause sometimes these things are rigid where it's like, you have to click on this and you have to click on this and it's like, click on a lead. Well, it could be many leads. It could be many different things. how did you solve for that problem of, having a structure, but creating
34:39flexibility at the same time, Daniel Giovacchini: Definitely. So, there's certainly complexity and how you configure process instruction based on, you take a CRM, for instance, you have parent. URL pages and you have, kind of children sub pages and we'll take a company record. And if you want process instruction to only show up for one specific company because they're very unique versus do you want process instruction to show up for every company and all of those sub pages and all those sub URLs. So that's one example where.
35:09that's a power user feature that we help people learn how to modify and create. And it's actually very easy and practice, but it is a complicated, nuanced part of the technology and part of the delivery of the products when you configure it right, it can be. much more powerful or you've also realized there's many more edge cases. So, this is why this experience, we actually work much more in a sales and success led fashion versus product led because figuring out something like that is difficult. but yeah, you essentially want to say, Hey, Ask yourself a few questions about
35:42either a process or enablement tip. Is this something I want everybody to globally see on every instance of, a page just like this? or is it something we, only want them to see uniquely on a specific page? So that's one question to ask. Another question to ask is, is this something we want people to see every time they come, or is this something we only want them to see one time, and it really is just like a, see it for the first time. And we don't want to show it again. so, those are usually the main kind of, okay, if we're gonna do real
36:16time enablement in the flow of work. those are the two main questions along with user groups and permissions. So do we want just new hires to see this or, you know, experienced team members, or we want just the sales team to see this versus just the success team. those are the main questions to ask and you're on your way to providing like curated enablement. So Justin Norris: then in terms of. The place of a tool like Tango within a bigger knowledge management ecosystem. So like I have a knowledge base, for instance, we use confluence, and
36:46that's very important for some things. And then we also like the company that I work for in my day job, we sell an LMS and mostly, targeting the L and D buyer. but some, similar overlapping use cases. And so that has another repository of knowledge. Do you aim to. eat all those things eventually subsume them in your broader vision of where you'll be in like five or 10 years or play alongside them. What will that look like? Daniel Giovacchini: knowledge bases and LMS is serve very important functions
37:18that aren't necessarily going to go away. Okay. and that's really that general information about, what is our industry, what is our product, who are our competitors, of this information that you would need as context and background to be successful at then, you know, using your tools and completing processes. So, that's very much, still critical and important. What we would argue is that. You should not be teaching how to use software, how, to complete tasks, how to go about process from within a knowledge base or an LMS.
37:50And if you want to reference it there, that's great. So we very much believe in deep linking process, instruction, deep linking. tango workflows or folders, from within knowledge bases or LMS is, and you can then go learn in the tools, and actually experience the process through the tools instead of, within a scorn file or something, embedded in LMS or knowledge base, So that to us, makes a lot of sense, to reinforce tool based
38:22learning systems, learning in there, but actually trying to teach through a PowerPoint or, put a video inside the knowledge base, you expect people to watch and memorize that's actually what we would expect to completely go away. Justin Norris: And do you see yourself again, thinking about your product vision, could you ever be a complete knowledge management solution, and have like your knowledge base, or do you always imagine yourself partnering alongside other vendors like that in the knowledge management stack? Daniel Giovacchini: I think and this is very much a, partnership
38:53driven, vision, I believe. So if we do say, Hey, there's many types of knowledge, there's many types of learning. Some tools are going to be much more specific and well suited for, this type. And some are going to be more suited for that type. the question for. real time enablement for what Tango is trying to do and help, you know, it really is a kind of like co pilot vision, right. Of how people, while they work, while they're doing, can we partner with other tools to surface their information in the flow of work when that's relevant?
39:26And, bi directionally. For LMSs, for example, you're always going to have cohort based onboarding. You're always going to have crops of new hires starting, and they're going to need, some hand holding in their first number of weeks that's probably always best delivered, through an LMS. And, so there's their bi directional, um, instruction then where stuff that might live in software and tools can also be, served through the LMS. it's all about, I think, designing the best upfront learning experience and
39:57the best sort of knowledge management, serving knowledge when people need it. And that's likely going to be through a combination of tools. Justin Norris: Makes perfect sense. I want to pivot to you for a second and like your role in the org. You're the COO, which, like all operations, jobs, it can mean many different things I find. So I'm curious about you see your role, your place within the org, the sorts of responsibilities you have. Daniel Giovacchini: if you actually go back and look at, you know,
40:28Fundamentally, what is operations? It is helping your company deliver and support your product or service offering, right? And be most efficient as possible in doing that. So operations to me is really everything outside of. Core product development or like core service delivery. And then if you think back office operations about how does our company be efficient to then ultimately deliver this product or service.
41:02And then you think about, and especially the last, 10, 15 years, right? Like rev ops is the fastest growing job and certain 2023 reports, according to Forbes. a lot of these other, function specific operations. Yeah. groups are really about, okay, how do we make, their efforts more efficient? so as, we're fast growing, kind of early stage company by all means. but what does that mean? It's, it's how do we. Most efficiently operationalized around bringing, our core products, to market.
41:33And so that's, a little bit of back office, in the early days is overseeing some of that function, but also very much sales marketing. Support, success and, the enablement of those really customer facing people on those teams. How do we set up structures and make sure all these, groups and functions are speaking the same language, drawing on the same philosophy as they make their decisions and as fluid away as possible. And it's chaotic early on. but certainly as you hit milestones, you get more certainty and you
42:06build more foundation in different areas and you're able to get more precise and more prescriptive. Justin Norris: As a COO, there's a pretty broad scope of activities that fall under your purview. And as a consequence of that, there are like a million things that you could be thinking about or doing at any given point in time. And I'm really interested in the problem of prioritization in a situation like that. Because I think that's something that many operators can relate to at any level. So I'm curious, How do you making those decisions day to day?
42:38Like I need to move this company forward relatively early stage. As you said, it's chaotic. What am I going to do today? It's a hard question to answer sometimes. Daniel Giovacchini: It's the ultimate question to answer. starts with working backwards from where are we in our product market fit journey when you're in early stages. And if you're an early stage company, whether your product or service, you're, you're racing to. best version of product market fit that you can, optimally achieve within, your timeframe and, working backwards from that, that helps you prioritize.
43:11So in certain weeks, it's, we're not learning fast enough, right? Or like we are not the feedback loop. Between sales and marketing is not strong enough to the point where we're putting out effective messaging or positioning because we're not understanding, you know, what's actually happening on, sales calls. And so that's like, okay, crap, we have to use call recording technology better. We have to set up a different meeting structure and a meeting cadence to achieve that. But it all comes from like, okay.
43:43You know, we're not learning fast enough to help us get to product market fit. or it could be like, Hey, we're not having the right conversations. And so, we really have to go look at what we're doing from a marketing perspective. so once you're kind of in the sort of more post product market fit phase, I think the North star then is, you have your, six, 12 months. Okay. Ours or strategy. That's kind of the timeframe, that feel like is, more in vogue now for all stage companies is three months is, too little more than a year is, too much. but you have your company level priorities and, um, what's going
44:14to help you hit those the fastest. and so going and finding, being maniacal about removing friction or blockers or organizational, lethargy, right? How do you go find that stuff and, blow through it? that's kind of the, next prioritization function in my mind. And the last thing I'll mention is you do need a longterm mindset, right? So one of our values actually is, this, leave it better. and we highlight people, within the company, within the team every month, and, it's basically.
44:45who is making sure that as we build and as we stand up, new process or new functionality or a new go to market motion for the first time, who's thinking about the systems mindset, who's thinking longterm, that we're making decisions and we're implementing things in such a way. That, they're going to endure and we're not just cutting corners and hastily, saying we completed tasks. So, that to me is more a mindset. That's a culture of values thing you need to build harder to work into a prioritization structure. So we think about that one from a values perspective,
45:17Justin Norris: Really appreciate you coming on, sharing a bit about your journey and about how you're thinking about this problem. it's certainly, as I mentioned to you earlier, like I just nerd out about this stuff, because it's so hard and I think so annoying when it doesn't work. it's really cool, to find some ways to make it work better. So big fan of what you folks are doing. We'll include a link in the show notes for, anyone. listening, who wants to check you out and yeah, thanks for spending some time with me. Daniel Giovacchini: of course, love having the conversation and, uh, love learning from you and the other guests as
45:48well. Justin Norris: Cheers.