Frameworks for Scaling Success | Dick Polipnick

Episode transcript

Setting the Foundation: Vision, Communication, and Radical Candor

Brendon Dennewill: Dick, thanks so much for joining me today on the Brendon Dennewill podcast. It's great to have you here.

Dick Polipnick: Thanks, Brendon. I'm excited to be on. I forget now how long we've known each other, but from the very first time we met, I knew that at some point, whether once or multiple times, we would have the opportunity to work together in one way or another. So I was very pleased last year when that finally did happen in a more official way, in your role as VP of Marketing at GoRoute, which is a very exciting business that we are very happy to be a part of supporting.

Brendon Dennewill: You've got a rich history of innovation in marketing and business strategy, and I know you've shared with me that revenue operations, or RevOps, is something you're very passionate about. I'd like to dig in and share some of your experiences with our audience, in the hopes that some of what you've learned, like many of us who've been in business for a while, can help our audience short-circuit some of the mistakes that every business leader makes at some point. So thinking back to some of your previous roles: from your perspective, what are the elements that separated teams that scaled more efficiently from the ones that didn't?

Dick Polipnick: That's a great question. I'm a big believer that the tone of an organization starts at the top and ripples throughout. Setting the vision and having that true North Star for every single person in the company, and making sure that if leadership gets hit by a bus, they've not only set that goal and that vision but communicated it. That's the twofold piece: setting it and communicating it.

You can set the vision in an internal leadership meeting on a quarterly basis, but if it never gets communicated to everyone in the organization, it's worthless. Leaders might be making day-to-day decisions on where to allocate budget or who to hire next, but if that's not communicated down to the deepest level of the organization, that's the big differentiator of scalability. You can have a company with the same funding, the same talent, the same headcount, the same market opportunities, and the company that wins is the one painting that crystal clear vision and doing a good job communicating it.

I keep coming back to communication because I'm a big fan of Radical Candor. It's a tool I've brought with me from company to company, and it's amazing how quickly it gets picked up. People either love it or absolutely despise it. I call it my anti-Minnesota-Nice policy, because otherwise everybody beats around the bush and doesn't get to the core of the issue.

On my first day at every company I've joined, I send an intro email: my name is Dick Polipnick, I like hiking, jiu-jitsu, et cetera. But I also include a link to a quick TED Talk on Radical Candor, and say: this is how I prefer to communicate and be communicated with. If I come off as straight to the point or even abrasive sometimes, that's why. And once I preface any direct comment with "radical candor" before continuing the sentence, people know to lower their defenses. I'm not attacking them. I'm attacking a problem we're both involved in trying to solve. Painting a clear vision and communicating that vision is, by far, the biggest differentiator.

Brendon Dennewill: That makes a lot of sense. It doesn't matter what operating system a business uses. Having some form of vision at the top is always the first step, and you're right: creating the vision is one thing, but continuously communicating it to bring the team along is such a critical, and often harder than expected, piece of the puzzle. Some leaders have an innate ability to communicate well, and others need to find partners who can help make sure that communication actually takes place.

I was actually fortunate enough to meet Kim Scott a few weeks ago, and her latest book, Radical Respect, is an extension of Radical Candor. I learned more from her in a few hours than I could reading the book many times. Her two-by-two graphic makes it so much easier to put into practice. And you're right about Minnesota: I believe she's originally from there but spent time on the East Coast, in Silicon Valley, and in the South, and found that her tools can break through cultural norms, provided you adapt to the local culture. By being direct and framing how you communicate, you can give people real-time feedback when they're straying from the vision or core values, which I imagine is the next piece of this process.

Core Values as a Day-to-Day Decision-Making Framework

Dick Polipnick: Absolutely. During my time at Online Growth Systems, a B2B software agency I owned for six years before selling to a company doing a rollup strategy, I got promoted to the number-two person in the entire umbrella organization within 30 days. I was scaling multiple agencies across the United States, consolidating shared resources, and setting the tone as the parent organization.

One of the big things I learned there was that core values are a critical, close secondary piece to the North Star. The challenge is that in day-to-day moments, a vision statement alone doesn't give a customer success representative enough guidance. When they're confronting a frustrated customer and deciding how to respond, the North Star isn't always enough to make that answer clear. That's where core values come in.

A lot of people who haven't been part of a healthy core-value-driven organization think it's just rah-rah fluff: something you write in your business plan, put on a plaque, and never reference again. Healthy, scaling companies actually lean on those core values as daily decision-making filters. They ask, "How does this decision match our core values?"

At Online Growth Systems, Radical Candor was so important to me that it became one of our five core values. Every quarter at our all-day offsite, I would ask every person on the team, from the most tenured to someone hired two weeks prior, to recite all five core values word for word. I would buy them coffee if they could. A five-dollar coffee is a big motivator at 7 AM. The veterans would go first, giving newer folks the chance to hear the values five or six times before being asked. By their second quarterly meeting, every single person had every value memorized.

By having those values memorized, team members can continue running the organization day to day, whether I'm on vacation or I get hit by a bus. They have five additional filters to run decisions through. A customer success representative confronting a difficult situation can ask, "How do I apply core value A here?" and that narrows the best path forward from several options down to one, without needing to consult a manager or dig through an SOP document.

Brendon Dennewill: Absolutely. We did a series of recap episodes summarizing what we learned from podcast guests last year, and the overwhelming theme came down to what we called leadership and culture. Without leadership and culture at the forefront, you can't really create an effective vision or core values, or ensure those things are communicated regularly. So thanks for validating that.

Assuming you have that foundation in place: good leadership, a clear vision being communicated, and core values driving hiring, firing, and decision-making. What's the next thing that separates companies that scale more effectively from their competitors?

Operating Frameworks: EOS, Scaling Up, and the Bones of the Organization

Dick Polipnick: It's going to be the framework or methodology you're following. Whether you're practicing the Rockefeller Habits, Scaling Up, the Entrepreneurial Operating System, Scrum, or Kanban boards, those frameworks are how you structure the bones of the organization. You hire around them and build your day around them.

I'm very Type A, so my calendar is booked out in 15-minute increments with every minute accounted for. Though sometimes I'll intentionally leave a morning open for an offsite walk in the woods to think through a major company-altering decision that can't be solved in 15 minutes. But getting back to it: the structure of the organization matters, and you model it after whichever framework suits you or that you have experience with.

I'm a hyper fan of EOS and have brought that methodology with me at every single company, as much as the organization can tailor it to their needs. A weekly L10 might not always need to be 90 minutes: a lot of the startups I've worked with have done well with a 60-minute weekly L10. Quarterlies, an issues list, a transparent organizational chart: these are things that, in my experience, separate companies that stagnate or die from those that hyperscale or outpace their competitors.

Brendon Dennewill: That's exactly why I asked: a lot of our guests have started by drawing parallels between an operating system like EOS, which we also run on, and other frameworks. A large proportion of our clients run on EOS, especially those here in Minnesota. EOS is growing like crazy globally. I was just speaking with our implementer last week about our upcoming quarterly planning, and he mentioned there are now 850 EOS implementers worldwide. I remember when there were maybe 20.

But the interesting thread is that when you put EOS, Scaling Up, RevOps, and GTM side by side, they're all versions of the same thing. They all have a vision layer, a people layer, a data layer, and a systems layer. In RevOps, we call our four pillars people, process, data, and technology. Whether you use EOS terminology or RevOps terminology, you're really talking about the same components. And your point is that you need a framework. Once you have the vision, leadership, and culture as a foundation, you need a way to execute and scale.

I know what the next piece is, because it's either going to be data or technology. So: you have vision, leadership, communication, and frameworks in place. The next ingredient is access to good, reliable, accurate, real-time data. Depending on the system, you might call these OKRs, KPIs, or metrics. And once you have that, you ask how technology can help you move faster. You've worked a lot in SaaS, which is fundamentally a technology industry. When you put all four components together, how do you describe a business that had those in place and scaled dramatically better than a competitor with seemingly identical resources?

GoRoute: A Real-World Example of Data, Technology, and Scale

Dick Polipnick: I'll use GoRoute as the example. For listeners, GoRoute is a coach-to-player communication company. We make smart watches for sports teams. A coach has a tablet in the dugout or on the sidelines, selects the play or pitch they want to call, and a watch on the wrist of the catcher or a player vibrates with that signal. The pitcher and catcher are now aligned without any audible or visual signs. There's a funny parallel here: just like in companies, you want clear communication. You have a system, the GoRoute system, to execute on that communication.

We're now layering AI on top of our data. A post-game data report can help coaches make better decisions going forward. We call it intent data versus result data: you told a pitcher to throw a fastball, did they throw a fastball or something else? You can now compare those data points, look at heat mapping, and build success ratios per pitcher, per inning, per pitch type. AI can then say, in this type of game situation, you should use this pitcher and this call. Coaches are being flooded with technology and data today more than in the last 100 years combined.

One reason GoRoute is outscaling competitors is because we have all of those components in place. We use EOS. We have a great CEO who sets a clear company vision and North Star. We have a leadership team that communicates that vision to everyone, whether you're in customer support or on the growth team. Every single person knows our core values, our North Star, and our key differentiators.

Right now, we're building comparison landing pages to educate coaches on when they should pick GoRoute, and being candid about when a competitor might be the better fit. We truly believe we are the better system, and the data proves it. But one thing I love, as much of a data and technology person as I am, is that my favorite growth strategy is word of mouth. It's the hardest to track and the hardest to initiate, because it requires near-perfect execution across so many categories: an amazing product, strong customer retention, ideally negative churn where growth outpaces any losses. When your customers are that excited, they tell everyone in their industry. Everyone in an industry knows each other. They go to the same conferences, the same clinics, the same forums, the same Slack channels. Good tools spread like wildfire.

Brendon Dennewill: That's really good. You were talking about net revenue retention, NRR, which does lead me to a broader question. So many business efficiency concepts, including RevOps itself, originated in SaaS. Metrics like LTV and CAC started there. But you've worked in professional services and other industries as well. What learnings from SaaS do you think other industries could or should adopt? Because SaaS has gotten very good at moving quickly and staying deeply connected to the customer, and ultimately that's what drives any business.

Lessons from SaaS: Universal Metrics, Kanban, and Transparent Data

Dick Polipnick: I'm almost a stickler about this: I think nearly every metric from the SaaS growth side should be used by every industry. Software is optimized for speed, fast decision-making, and efficient scaling. Those are things every business wants, whether you're in insurance, manufacturing, or e-commerce.

A favorite example is Kanban, which is Japanese for "billboard." It was coined by Toyota. They had a large board inside the factory displaying how many cars were at each stage of the manufacturing process: upholstery, tire checks, fabrication. Every worker on the factory floor could look up at any moment and know exactly where there was a slowdown or extra capacity, without physically walking the floor. That was real-time data communicated transparently down to every layer of the company.

That concept has been translated into countless tools. One of my favorites is Trello, owned by Atlassian. It's essentially a set of columns for tasks that move left to right. I run a hybrid of Kanban and Scrum: backlog, to do, doing, awaiting approval, and complete. Every quarter, the team goes through the completed column together as a retrospective. What did we accomplish? What did we learn? What can we do better?

Another great story involves Andrew Carnegie and Charles Schwab, who was reportedly the first person in history to earn a million-dollar salary. Carnegie hired Schwab to fix his worst-performing steel plant. Schwab took a piece of chalk and wrote a single number on the factory floor: the number of shipments the night shift had completed. When the day shift came in and saw it, friendly competition kicked in. They erased it and wrote a higher number. The night shift responded in kind. Ideas started being shared. Process improvements emerged organically. That single number on a floor turned into healthy competition and better performance across both shifts. Lean manufacturing and Six Sigma trace similar roots.

Brendon Dennewill: I like the way you connected those ideas. We actually use Trello to manage our podcast production. We have about seven columns and move episodes through them so we always know what stage each one is at. And of course, both being HubSpot fans, the HubSpot Deals board works the same way. A CRO or sales leader looks at their deals board first thing in the morning to see where things are moving and where they're stuck.

What I appreciate about where you went with the Carnegie story is that data can also be used to influence behavior in a healthy way. A good leader knows when to intervene: if the team goes from five to six to ten to eleven, at some point you redirect the energy before people burn out. The point is, you have data and mechanisms that drive the right behaviors. And all of us as leaders have learned the hard way that what you think is incenting good behavior sometimes incents exactly the wrong thing. You adjust, you learn. As we say around here: you're either winning or learning.

GoRoute and Denamico: Applying RevOps Principles in Practice

Brendon Dennewill: GoRoute, at its core, is really a data company that uses technology to deliver that data to its customers. As you were describing it earlier, I was thinking it's almost like GoRoute has brought the Moneyball concept to high school teams across multiple sports. Those of us who've seen Moneyball have probably watched it multiple times: you can take a perceived underdog team and outperform the most expensive rosters in the league by looking at data and identifying specific skill gaps rather than paying for star power.

The fact that GoRoute has made that accessible to high school teams across all kinds of sports is remarkable. And Daniel on our team, who works with GoRoute, is a total baseball enthusiast. I think his dream is to have been a catcher, so working on the communication layer between pitcher and catcher with the data and technology that makes it all better is right in his wheelhouse.

Dick Polipnick: Before we move on, I'd love to tie some of these threads together. One of the most recent features we launched at GoRoute was an internal-facing tool built with Denamico, and it directly connects to a lot of what we've been discussing: transparent data across the company, baked into our technology and operating system.

We have access to data that nobody else in our industry has. Many competitors use radio frequencies or other communication methods. We use a cellular network, which means we can store data in the cloud and see trends across the industry. For example, we can track how many plays are being sent by new customers during their first weeks of the season, and compare that against expected benchmarks. If a first-year customer is off pace, it automatically flags a ticket inside our HubSpot environment for a customer success representative to reach out.

Here's where Radical Candor comes in again: we actually tell that coaching team they are off pace. For a coach, that's a huge red flag. Nobody wants to be off pace. It signals that competitors might be practicing more or using the system more effectively. Within 24 hours of receiving that message, usage skyrockets. And at that point, the statistical likelihood of that customer renewing their contract is infinitely higher than if the system is sitting in a locker room collecting dust. You did all that customer acquisition work for nothing if they cancel.

Now we can provide that data transparently across the company and automate the initial outreach, so the customer success representative only needs to engage if there's a reply or a question. We can do this at scale for thousands of teams with a small team. This connects directly to the AI trend: leveraging technology and data to scale a team to tens, hundreds of millions in annual revenue with a tiny headcount. Microsoft recently reported their highest revenue per employee in company history, and a lot of that is driven by AI. This is a project we worked on with Denamico, and it's a beautiful marriage of everything we've been talking about: communication, Radical Candor, data, systems, and operating principles.

Brendon Dennewill: I really like that example, because GoRoute customers aren't investing in the product because it's a nice-to-have. They're investing because it's going to make them better as a team. And Radical Candor in that context is helpful feedback grounded in data. If you're not collecting the data, you can't learn from it. If you're not sharing it with the customer, you're doing them a disservice, because what they're paying for is the ability to make better data-driven decisions. That gets at some of the cultural challenges many businesses face. Whether it's Minnesota Nice or any other cultural norm, you have to be clear about what value you're providing to the customer and communicate every relevant data point. Baking that into your core values ensures your team does it not because they were told to, but because it aligns with who you are as a company.

Technology Adoption: The 1-3-1 Framework and Phased Rollouts

Brendon Dennewill: A lot of people who listen to the Brendon Dennewill podcast are at some sort of decision point around implementing new technology, whether AI-related or not, and many have had a previous implementation that didn't go well. What goes into your decision-making process when evaluating whether to implement new technology? And how do you think about adoption timelines?

Dick Polipnick: There are multiple layers to that question, because adoption can happen at the leadership level, within one department, or by one individual. I'm a big fan of phased rollouts because they increase adoption rates, increase the likelihood of success, and make the timeline much more manageable.

For a piece of technology that touches multiple departments, like HubSpot or Trello, cost is always the first factor. Does it fit your budget? Sometimes a new tool comes onto the market mid-year after the budget is already allocated. What I do in that situation is look for parallel use cases: are there companies in adjacent industries getting strong results? If I believe we can replicate or exceed that success, within our budget and timeline, then we move forward. If not, I put it in a "not now, but later" bucket, and I've done that plenty of times.

Right now, AI is a specific case worth addressing. I believe AI features will be commoditized within the next 12 months. The feature-for-feature comparisons winning customers today are going to compress quickly into a race on speed and cost. Does that mean you should wait until it's cheap? Absolutely not. Why would you skip the next 12 months of competitive advantage, especially when it's still harder for competitors to adopt? Once everyone has cheap AI, the differentiator shifts to who uses it most creatively. Get ahead of that curve now.

For all other technology decisions, I use something called the 1-3-1 framework, which I originally pulled from Dan Martell's toolbox, and he pulled it from someone else's. It produces a 1-3-1 proposal, and I use it with everyone in my organization, from the CEO on down. The structure is: one isolated problem, three potential options, and one recommendation.

The one problem requirement sounds obvious, but it isn't. People often come in describing six different problems, each of which could have a different solution, different timeline, and different budget. I stop them and say: isolate it to one single problem. Then bring me three options. Those don't have to be three different pieces of technology. One of the three could always be the status quo, staying with what you have. Sometimes the best decision is to do nothing and keep the course.

A common example might look like: Option A, stay with the status quo; Option B, a more expensive, longer-to-implement solution with higher potential ROI and multi-department applicability; Option C, cheaper and faster to implement but limited to one department and likely requiring a switch in six months. Then one recommendation from those three options, backed by the 80/20 rule: 80% of the time I go with my team member's recommendation, 20% of the time I override it with one of the other options. In rare cases, a hybrid recommendation is appropriate, such as "go with Option C now with the plan to migrate to Option B in six months when we have more budget and resources."

What this process does is force the team member to do real research, gather data, and think through the options. And what I've found, almost every time, is that I'll get a Slack message that says: "As I was preparing the 1-3-1, the answer became completely obvious. Going with this." The process enables team members to solve their own problems without escalating, which is exactly how you build an organization that scales without creating dependency on leadership at every decision point. Combined with appropriate spending authority, team members can make decisions independently within defined limits, which supports both scalability and employee autonomy.

Brendon Dennewill: I really like that. We use Dan Sullivan's Impact Filter, which he originally designed for the visionary or CEO to sell themselves on an idea before presenting it to the team. The intent is similar: you have to do the thinking before you pitch it. I'm going to look into the 1-3-1.

You mentioned earlier the M3D framework. Is that related?

Monthly Data Deep Dives (M3Ds): A Scalable Cadence for Growing Companies

Dick Polipnick: M3Ds are something I coined and really refined at Gym Desk, the company I was at before GoRoute. Gym Desk is software for gym and studio owners: Jiu-jitsu studios, yoga studios, weightlifting facilities. It handles everything from member management and payment integrations to class schedules and even key fob authentication for 24-hour access. A complete suite for running a fitness business under one roof at a great price point. We had exceptional product-market fit, strong differentiation from incumbents who had grown complacent, and we grew extremely fast.

With hypergrowth, you need systems built to handle that velocity. In Scenario A, you're growing so fast that you say "I don't have time to look at the data." But you might be dumping money into a growth channel whose ROI has deteriorated significantly in the last six months, and you're burning cash without realizing it because things still "feel" like they're working. In Scenario B, you're too attentive, looking at data every day for metrics that only need weekly or monthly review. You get lost in the details and waste time on noise.

M3Ds, or Monthly Data Deep Dives, are the sweet spot between those two extremes. The structure is this: once a month, every person on the team owns a set of channels and presents a pre-prepared 20-minute deep dive on their data. They cannot wing it. No pulling up a dashboard in real time and interpreting it on the fly. They prepare in advance, and the format is up to them: HubSpot dashboards, a spreadsheet they manually update each month, a slide deck. It changes from person to person and often from month to month.

After the 20-minute presentation, there are five minutes of Q&A open to anyone on the call, but questions must be tied to a specific data point from the presentation. Then there are five minutes for an action plan, where I typically make the calls: cut this budget in half, double that one, try this approach. We make big directional decisions on a monthly basis that set the course for that channel owner for the next 30 days.

Everyone in the company is invited to these sessions, but attendance is mandatory for the relevant department. The reason: the person who owns our email channel might see data from our social media channels that influences their next month's direction. They might see that a click-through improvement upstream is driving better conversion rates downstream on their own channel. That kind of cross-pollination produces insights that siloed reviews never surface.

I've found this cadence is ideal for companies in the zero-to-50-million revenue range. You're agile enough to act on monthly insights, and you frankly cannot afford to wait 90 days. You might be 12 days into a quarter and already know you need to change direction. Having a monthly cadence creates those early course-correction checkpoints.

And it ties back to everything we've discussed: the team member owns their channel day to day, aligned with the core values and the North Star we set at the top. The M3D is the monthly course correction, the "a little left, a little right." Then we come together, the 1-3-1 proposal for any recommended changes is presented in the last five minutes of the M3D, and we make a decision. That full loop: autonomous ownership, transparent data, structured review, and clear decision-making, is what I've found dramatically accelerates growth and increases employee satisfaction. They're not being micromanaged. They're being monthly managed.

Brendon Dennewill: You can see how this layers on top of a 90-day EOS or Scaling Up cadence. Essentially, you're creating monthly mini-rocks that feed into your quarterly rocks and annual goals. For companies that have the agility to operate this way, I can see how this speeds everything up considerably. Really cool.

Dick Polipnick: And it's definitely more suited for scaling businesses. Quarterly makes more sense at 50 million and above, where you have the infrastructure to absorb a longer cycle. But when you're going from zero to 50, you both have the agility and the urgency to operate on a shorter cycle.

Brendon Dennewill: Really cool, Dick. It was so good to have you on, and I look forward to our next conversation.

Dick Polipnick: That sounds great. Thanks for having me.

Subscribe