Turning Compliance from Burden to Strategic Advantage

In cybersecurity, the conversation too often starts with fear.

Budgets are allocated reactively. Audits are endured. And frontline IT staff brace for impact, knowing they’ll have to slow down, jump through hoops, and prove their work to outsiders who often don’t understand it.

Jason Young, CEO of Pylon, has a different take.

In our latest episode of the Disciplined Troublemakers Podcast, Jason shared how he and his team helped the Defense Health Agency (a massive entity inside the U.S. Department of Defense) save $25 million by doing one thing most companies fail at: reducing burden.

Not security theater. Not extra dashboards. Real, measurable time and cost savings.

How? 

By talking to the people who do the work.

Not the executives. Not the compliance officers. 

But the sysadmins, network engineers, and ops teams whose workflows are directly affected by compliance initiatives.

Jason’s origin story is part technician, part auditor. He’s seen both sides of the house. That’s why his company doesn’t treat compliance as an abstract policy. They see it as an operational bottleneck that can be untangled if you listen to the right people.

“We make RMF suck less,” was their internal motto at a DOD trade show. They printed the phrase on a mug. 

It disappeared in under an hour. Because everyone in the room felt it.

Jason’s team didn’t just automate tasks or streamline reports. They asked: 

What if we just stopped doing things that didn’t add value?

Sometimes, solving a problem means doing less.

That principle, burden reduction, is central to Pylon’s success. By removing friction from IT operations, they freed up hours and improved morale. Compliance stopped feeling like an enemy. It became part of the job, not a disruption to it.

This is where the conversation shifted into leadership.

Jason isn’t a command-and-control CEO. He’s a student of culture, autonomy, and alignment. He talked about hiring subject matter experts and giving them room to work. About measuring outcomes, not effort. About thought work and the mental “spring” that can wind too tight without recovery.

That’s where motorcycles and martial arts came in. Both force you to be present. Both remind you to unwind. And both offer the kind of clarity that can’t be scheduled or micromanaged.

At the end of the day, Pylon isn’t just selling cybersecurity software.

They’re offering relief. For burned-out teams. For overburdened systems. For organizations that know compliance is important, but don’t know how to make it work without grinding their people into the ground.

And Jason’s reminder is a powerful one:

Culture eats policy for breakfast.

Burden is the red flag. Value is the fix. And sometimes the smartest move isn’t more AI or automation, but simply asking: 

“What if we stopped doing this altogether?”

—

Want to hear the full conversation? Listen to the episode on the Disciplined Troublemakers podcast or connect with Jason at pylonsecure.com.

Transcript

Scott Shagory:
Well, welcome back to the Discipline Troublemakers podcast. I’m your host, Scott Shagory. Here on DT, we talk about scaling tech companies and helping CEOs do that with greater ease and flow. Today, we’ll be talking with Jason Young. Jason is the founder and CEO of Pylon Cybersecurity, a firm he founded in 2011. Pylon helps security managers automate network compliance through real-time services, which ensures data accuracy and definitive chain of custody. In 2024, Jason and the team saved the Defense Health Agency, which is a combat support agency within the USDOD, that supports medical services and readiness for the Army, Navy, as well as for the Air Force, I believe, and saved them $25,000,000 by optimizing their cyber compliance workflows, which is a big deal. Today we’ll be talking with Jason about the challenges and the opportunities of scaling cybersecurity companies, no small feat.

Scott Shagory:
And so, Jason, thank you for carving out time today to talk with us and welcome to the Disciplined Troublemakers podcast.

Jason Young:
Thanks, Scott. I appreciate it. Appreciate the reach out too.

Scott Shagory:
No. You’re welcome. You’re welcome. And it’s always nice to reach out to folks. And if they’re comfortable sharing, you know, make sure that my audience and, you know, your new audience can go ahead and learn from what you and the team have actually done. So I guess to open it up, obviously, I’ve shared a little bit on the intro here. I’m guessing there’s gonna be, you know, more in terms of, you know, both who your ideal audience is, if you have it, as well as kind of the key challenge in the key sauce around what you do. Is it, you know, quote unquote primarily focused around compliance, but, usually, compliance has lots of pieces to it, at least in my experience.

Scott Shagory:
So right. What does that look like for you or for the team and the company?

Jason Young:
Yeah. It’s a good question. It’s sometimes very murky when people say compliance. So I guess in our world, we’re talking about the governance and regulatory frameworks around information technology. So we’re very focused around the US government and primarily the Department of Defense because they have a lot of IT regulation, as you could imagine.

Jason Young:
So I guess, what that means, I’ll maybe share a little bit about why I even care about it, because it’s not a, certainly not a hot topic in the news. Right? IT compliance. Yep. That’s true.

Scott Shagory:
But it’s important, though. I think, you know. Whether it’s data, which is ultimately privacy. I mean, the costs associated with either getting it wrong or a ransomware attack, let alone being sued. I mean, it’s instantly global. Although DOD is obviously, you know, a quite different market. It explodes in lots of pieces instantly. Yeah.

Scott Shagory:
And so it’s actually, it’s not exciting maybe, but it’s usually important to get right.

Jason Young:
Yeah. It’s not the kind of sexy thing out in the news, but, you know, when breaches happen or when data is lost, like, sometimes it’s unquantifiable, the damage that happens. I mean, in the defense industry, it could be national security. You know? I know that term gets thrown around a lot, but, you know, if you think about it, you know, in our context, there are military men and women that are deployed out in the field. And if their medical records were to be compromised or maybe the systems that are supporting some life-sustaining activities. Like, IT could actually lead to actual real death. You know? So, I mean, we, we take it seriously.

Jason Young:
So let me share. I started my career as a systems administrator. So I think, like, turbo nerd, you know, hands-on keyboards, doing the work, and I kinda got trial by fire into the defense industry in this regulatory kind of intense situation, what we’ll call it. It’s very intense where it was like, we gotta do this massive thing. And it was like, oh my gosh. Like, how in the world? So yeah. I had to learn very quickly on the technical side how to implement these security controls. And then I had the opportunity to move to the other side where I got to be the checker or the auditor to audit folks like myself in the past.

Jason Young:
And so I got to see both sides of the house here, and that’s kinda what inspired Pylon and kind of where we are today where it was very manual. Like, a lot of the rumors you hear about the government and their process, it’s true. It’s just very manual, very labor-driven. Lots of people, like, kinda pushing the noodle. And so we, and my passion was, like, it doesn’t have to be this way. That there’s no way that this is the way the world works. You know? Especially, you know, at that time, 02/2011, I was like, the technology exists. Why are we not doing anything about it? And so that was the beginning there.

Jason Young:
So we started looking at why it is so manual? Why is this so incredibly burdensome, and what can we do about it?

Scott Shagory:
Yeah. No. I think that’s true. I mean, before I’ve been doing more recent stuff, you know, as a founder myself, worked for Raytheon and Northrop Grumman for many, many years and did so, you know, on the federal side, not on the DOD or intelligence community side. So no black box work to be clear. And yeah. I mean, those processes exist for a reason, but the iteration of them or lack thereof is really challenging.

Scott Shagory:
And the data piece, as you mentioned, just a few minutes ago is a big deal. So I’ve been working for the federal government for a few years before pivoting into tech and working for Northrop and Raytheon. And that was at a period of time where OPM was hacked by a nation-state. And so, you know, China has all my fingerprints. China has all sorts of data about me. And we could argue whether that’s relatively safe in the grand scheme of things versus, you know, private actors and things of that nature. But it is. It’s a big deal.

Scott Shagory:
It was me and quite a few million other people. There was absolutely nothing I could do about it. I got a letter. They were thoughtful. OPM and others were thoughtful enough to send me a letter saying that, yes, indeed, Scott. Your data was breached and this nation-state now has it. And that was it. That was basically it.

Scott Shagory:
Go about your day. And so

Jason Young:
Good luck.

Scott Shagory:
It does. Yeah. Exactly that. Good luck. So it is more important and valuable to get that stuff right than you often think. And that’s certainly true. I mean, we’re filming this and then recording it in early April. And so it was just what is it? Last week or a little bit more with 23andMe. Yeah.

Scott Shagory:
Filing for bankruptcy. So, you know, again, a lot of anxiety for those folks who have shared their very, very critical data. So, so yeah, no arguments with you there.

Jason Young:
Yeah. I would say, maybe you perceive this at Raytheon or not, but there is a perception that the cybersecurity efforts or at least the regulation tends to it’s necessary to extract value out of the transaction. Meaning it must be slower, or it has to inject burden, or it has to make things perform less. And I think if I were to say the stream that we’re trying to paddle up against is we’re trying to challenge that, is that it doesn’t have to extract value. It could add value into the system if you just thought about it differently. Yeah.

Scott Shagory:
I mean, my take on it after, you know, talking with over the years a number of, you know, cyber folks either on the, you know, those doing the work, those, as you say, doing on the audit side, or those just selling into the marketplace is that, unfortunately, most teams, most people, even folks in the federal space, you know, do think of cyber really as, you know, something they have to spend money on. They recognize it’s important, certainly. Their job in some cases depends upon it. But it’s not really perceived as a strategic asset. We haven’t yet made that leap. There are some exceptions out there, but unfortunately, for many, the reality of it is it’s a cost center and not a driver of, if you will, business value and obviously in the federal space, how we define that. So, you know, it’s a bit different.

Scott Shagory:
It’s not about turning a profit. But again, I think just the framework or the mentality or just the way in which oftentimes cyber, generally speaking, is thought of. It’s the red team, it’s the blue team, it’s compliance. It’s whatever that happens to be often about power projection that it’s thought of, I think, very differently and it’s unfortunate that that is the case.

Scott Shagory:
And so you see it elsewhere, you know, with people and teams getting laid off in Fortune 500 companies just because it’s a way of cutting costs immediately. We haven’t been hacked this year, at least not significantly. So we’re safe and we’re okay, so we can let this team of 10 go. Mhmm. And it’s just I think it’s very frustrating, but it is what it is. And so as a result, you gotta, as you well know, sell into that marketplace or reframe your value proposition in a way that is powerful. So it’s we save, you know, 10 times, but we also do this, this, and this. It’s understanding what somebody’s bleeding neck problem or I call it the level 10 bleeding neck problem is.

Scott Shagory:
And if you can really solve for that, they tend to, you know, be you can change them in ways or they’re open to change in ways that they weren’t before, but that can be a very tough sell when it’s about risk reduction, not about, you know, a massive upside opportunity is my take on it. So

Jason Young:
Yeah. It’s well said. Like, I think not always like you stated, but I think people tend to enter the space out of fear more than out of, like, I’m gonna two x my ROI by doing cyber. It’s like, if I don’t do this, I’m gonna halve my ROI or negative ROI if something bad happens. And I think that is the unfortunate part. And I think what it really does is it spawns off all kinds of other really negative things. Like, correct.

Jason Young:
The thing I perceived in IT operations was, like, my job was to keep the system running, keep it running well, and to keep my users’ experience positive. And then the cloud of cyber comes over and demands that I do things that impact the performance, that impact the user experience. And I must accept that that’s just necessary, and it’s for the good of the world. And it’s this negative trade-off that we have to just swallow as if that’s the only way. This was extraordinarily highlighted. We’re at a trade show. So the DOD uses a process called the Risk Management Framework. That’s a regulatory framework.

Jason Young:
Yeah. And we just made this cup that said, “We make RMF suck less.” You know? And we were just highlighting that, like, no one will say it out loud, but everyone hates this thing. And, like, we made maybe a hundred cups, and we couldn’t keep them at our booth. They, like, flew. They were gone in, like, the first hour. And that to me was kinda like, oh yeah. Everybody hates this.

Jason Young:
And then we started asking questions like, why? Why is it so hated in the world? And it was because, like IT operations, they didn’t see any value in it. It was like, okay. Audit is happening. Now is where, like, my work gets worse. Now is where I have to, like, focus on doing a bunch of things that I don’t want to do, that I’m not paid to do, and entertain this team for a week or a month, and they’re gonna tell me all the things that I’m doing wrong, and I disagree with half of them. And it’s this whole interaction that was like, no. That’s the cultural problem around cybersecurity and IT operations that we intend to change.

Scott Shagory:
No. And I think that’s great because it is often an emotional response to things rooted in, you know, grounded in reality. No question about it. Where if you can, you know, create some sort of hook so that you’re never having a shallow conversation, say, in the sales space around specs sheets or, mhmm, features and stuff, but you’re getting to outcome and then you’re getting a transformation or something that they never even thought was possible. However small that might be for that particular team, maybe the economic buyer, hopefully both because that way everybody’s aligned instantaneously. It really just shifts the entire conversation and all of a sudden people can start to get maybe not excited about it, but they can just feel relief and have a belief system around that belief that in fact, they made the right decision by choosing you and your team, or a piece of it or whatever that happens to be. It’s just, again, about shifting people so that that change ends up being something they look forward to.

Scott Shagory:
They don’t grit their teeth and think, okay, here comes Jason again. And he’s gonna make my life hard. And he’s gonna do all these things to me, even though, of course, that’s simply not true. Everyone, you know, objectively knows that. So, so yeah. What does, for you and the team, either for the rest of this year and next year, what does scale look like for you and the team, you know, now?

Jason Young:
For us, I mean, our kind of laser focus is we look for a burden. Burden is the thing that is our red flag that there is a problem to solve there. And our development team is so fantastic at always pushing us to remember who we’re building the product for. Just always remember. It has to be solving the problem of our personas that we’re building the product for.

Scott Shagory:
Mhmm.

Jason Young:
And so for us, scale is how do we find the burden in those people and put the solution in their hands that actually solves their problems? So one of our early learnings when we first launched was that it wasn’t that our end users had to use our products. It’s what they wanted to do.

Scott Shagory:
Mhmm.

Jason Young:
And so as a cyber product, the learning for us was actually solving a pain point. They got hours back in their day. So we were able to measure it by saying, like, they can spend less time in the office because now there’s a thing that they don’t have to do. And so, we call it burden reduction, and then we’re like, ah, if we actually find the real problem and solve the actual problem, not the stated problem, and I’ll say that is different many times. You know?

Scott Shagory:
Yeah.

Jason Young:
Yep. We hear it often, like, here’s the problem. Then we start asking the people, like, the person that stated the problem never has done the work. They’re not in the chain at all. And then when you talk to those people, you’re like, oh, it’s actually something wildly different.

Scott Shagory:
You know?

Jason Young:
Yeah. So when you actually solve that problem, then it feels like magic, and the users in the system want to participate as opposed to the obligatory participation.

Scott Shagory:
Yeah. No. I think that’s true. You know, where you can do exactly that, truly understand what the problem is with the person or team that’s experiencing it and then, you know, truly solve it. It’s sort of like a job interview where you can talk there with the recruiter and they might understand a company that they work for very well, but not necessarily the actual team who’s doing, you know, x work with, you know, node.js and some other very technical component stuff or cloud-based infrastructure, whatever it happens to be, AI, of course. And you just get a very different perspective on what it is that they’re really truly frustrated with, and can you help them with that particular technical and then ultimate business challenge with the broader team? And if you can do that, yeah, you just become immediately evaluable and nobody forgets who you are after that.

Jason Young:
Yeah. Yeah. And also, it informed us of, you know, at least with our software. By knowing where the problem exists, you can amplify value back up the chain. So in terms of IT operations and compliance, we found that there’s an interesting shift. And when we started looking at where the burden actually lies because we would hear from, you know, cyber folks, people were in the community, of the problems. Mhmm. Right? But a lot of the cyber folks didn’t actually own the work that must be done.

Jason Young:
It was IT operations. So yeah. If you think about it, in terms of a door and a lock. Right? IT operations is the door. The compliance and regulatory folks are the lock. So, like, you can take the lock off and the door still works. But if you take the door off, no locks are necessary. Right? The whole thing falls apart.

Jason Young:
And so when we started digging into that, we’re like, you know what? I think the world right now is tending to revolve around regulation and compliance, but it actually should revolve around the IT operations shop. Like, they’re the ones that do the work. They’re the ones that have the hands on the keyboards. They’re the ones that make the changes on the security controls, and we just got this backwards. And we need to realign.

Scott Shagory:
Yeah. No. It’s so true. My background’s in computer networking, so things Cisco and Juniper gear back in the day, border gateway protocols, all that stuff. When it comes to Spanning Tree. Yep. Spanning Tree Protocol. Yes.

Scott Shagory:
Back when that was not always easy to configure. No. And the Cisco gear was very good gear for what it was as well as the OS and stuff. But just like you say, a lot of manual work and I think even today there’s still a huge amount of what we could call sysadmin or manual work that is being done and that will change. But it does require people, bodies, decision-making, and a bunch of other stuff. So I guess leading into the next question here, you guys obviously have a clear understanding of your immediate customer and obviously have experience within the DOD as it is the big 800-pound gorilla.

Jason Young:
Mhmm.

Scott Shagory:
You know, how do you guys find or uncover the deep intel that does give you decision superiority as I like to call it over competitors in the marketplace. Obviously, there are RFPs or whatever the DOD has is the equivalent. You know, those are standardized and we, you know, could talk about that. But I think the important piece is how do you guys navigate having that decision superiority so you do win that $25,000,000 or that contract that saved $25,000,000 or other sorts of things within the DOD marketplace, if you will.

Jason Young:
Yeah. The simple answer is we care about the users, the lowest users. Like, if you think about the RFP, how that comes out, what’s really happening there is it’s someone high up in the chain contemplating some work that must be done over five years and pretrying to rationalize a solution that is so complex down at the detailed level. I just don’t know how it ever produces any results because what it does not do is it does not contemplate agility and changes over time and movement in the kind of conditions on the field. It’s like, you know, in the DOD world today, they’re looking at $500,000,000 contracts over ten years, and it’s like, how could that possibly be agile? You know? Because the secret sauce is, like, it does not care about the lowest level guy that must walk into the office and log into the thing and make a change. You know? Like, and so our secret sauce is we go talk to that guy.

Jason Young:
And just like, what do you do? How does this work for you? And then, lo and behold, they have amazing things to tell us. You know? And then if we take that honest feedback and we’re like, you know what? The problem actually is, like, if this little workflow improved 5%, that translates into 90% at the end of the chain. You know, it all gets better the whole way through. And, like, if you were to just ask the senior leadership, they would say, like, the problem is maybe the documentation’s wrong. But all the way down here, that’s not actually it. It’s just a symptom or a result. And so, again, when I say we’re paddling upstream, like, we’re constantly paddling upstream because, like, it’s not popular to say, like, well, let’s talk to Jeff, the junior sysadmin. Let’s see what he thinks.

Jason Young:
No. Nobody cares about Jeff. You know? It’s like, what do we do?

Scott Shagory:
Yeah. Yeah. No. It’s true. The folks at the bottom have the most amount of doo-doo that falls out of the sky and hits them constantly.

Jason Young:
Yeah. Lots of great ideas come out of the sky. “Hey, Jeff, I have a great idea for you.” And he’s like, I don’t care about that.

Scott Shagory:
Yeah. No. It’s true. I was, you know, in that role for a number of years, and it’s something you really don’t forget because it is those technical trade-off choices in some cases that you have to make. And you don’t officially have that decision-making authority, but it has a huge impact on your team and the organization and can come back to bite you in some way. So it’s no surprise that a lot of people are very, or understandably risk-averse, particularly in a DOD environment, the federal space in general, of course. So, yeah, it’s just, and it’s not always easy to find someone to turn to. So even if it is your immediate boss, let alone going up chains of command when obviously the priorities are different.

Scott Shagory:
Yeah. It’s a challenging space and one in which, you know, the answers aren’t always easy. And if you’re an outsider thinking, you know, standard private business, it just doesn’t work in quite the same way and it’s tough to explain.

Jason Young:
So yeah. Yeah. Again, our dev team, there are a couple of guys who are just fantastic, but they will always say, like, when we’re evaluating a new feature or an idea, they always ask a question like, well, what if we did nothing? You know? Because sometimes the answer is just to stop doing something. You know? Like, and we found that to be true, you know, where we look at a workflow and we’re like, the cheapest thing to do to solve this is to just not do it anymore. Produce has no value. So the answer is, don’t pay us anything. Just stop doing that. There’s nothing for you.

Scott Shagory:
Yeah. No. It’s true. We often think we need to take endless action, and you hear about that, you know, mindset gurus, to just practical doing to augment your capability to, you know, a million different stories about it. But it is so true. Sometimes actually doing less is the most important thing. The most important thing of all.

Scott Shagory:
And,

Jason Young:
Sometimes folks forget why the process even exists. It just existed so long. No one asked, like, what is the value of this? Like, what does it produce? And you’re like, I don’t know. It’s just the rules. We have to do it. And it’s like, what if you didn’t do it? You know?

Scott Shagory:
Yeah. No. It’s true. I guess, you know, thinking about before a break here, a short break, what do you think, transitioning slightly, what do you think is most misunderstood in the marketplace today about what your company does? We’ve kind of hinted and talked around it a bit. Yeah. Is there something that either the DOD broadly speaking, if we can call that the marketplace, or it’s again, who you’re, you know, selling into at the DOD. What do you think is most misunderstood about what you and the team do?

Jason Young:
It’s a great question. It’s a hard one too. I think there’s a big push in the world today that everyone must consider AI. But I don’t know if everyone’s really sat back and answered the question of why AI in a particular context and specifically in a business context. Yeah. Because the question I always ask is, like, it’s cool. It’s neat to chat with, but what problem is it solving for you in your workday? And I think a lot of times when we talk about our tech, you know, it’s like, we didn’t invent some crazy new sci-fi magical thing. We just applied the technology of today in a very specific way to a very specific workflow.

Jason Young:
Mhmm. And, like, when you do that and it actually solves a problem, that’s what feels like magic. But it wasn’t a giant large language model that’s chatting with you. It just accomplishes the thing that must be done in the most efficient way. And so I think the thing we encounter is questions like, when’s Pylon gonna have AI? And it’s like, well, for what? You know, like, what is the problem that we’re solving with AI? Like, you can chat with ChatGPT today, and it’s like, do you feel it’s fantastic? But does that help you move the ball from your system into the authorization effort? Like, does that solve that for you, or you just want someone to talk to and, like, I’ll talk to you. I’ll talk to you for free?

Scott Shagory:
Mhmm. Yeah. No. It’s interesting. And I think for that, you know, junior developer or network person or somebody else up and down the, I’ll call it the ops team, you know, they’re so overburdened right now with just stuff to do. So much. They’ll play with some AI agents.

Scott Shagory:
They’ll play with some workflows on some different orchestration layers that are available out there for free or some small nominal sum. You know, there’s a variety of things out there that I think are really very cool and I think will be powerful. But it’s a question of, yeah, how are we truly applying this and what does that look like? What’s the infrastructure look like at the DOD? I’m sure they’re gonna have to have it be, you know, secret, secret, you know, TOPS, TS, yeah. You know, etcetera. The different levels, and whatnot. So, yeah. It’s just I think sometimes it’s nice to play with in the context of one’s immediate work, but you’ve got, you know, 20 different fires that are burning, and you know one can handle three of them. So which ones do you do until you start getting screamed at?

Jason Young:
Well, I agree. But it does some amazing administrative stuff. You know? We use it quite a bit in our company. I think that’s part of the math of scale. You know, we’ve avoided having to hire folks because we’re able to offload it to AI tools. You know, like, our marketing team is very small and super efficient. They’re able to run really lean because of AI and a lot of the copy work that it can do. And yeah.

Jason Young:
It’s incredible. But in a large organization where you’re talking to multiple groups, you know, where the chain of custody of the work is extraordinarily complex, a generalized chatting model, it doesn’t quite finish the process. You know, like, there’s still a structured workflow that has to happen. And so, you know, my mind always goes to, like, it’s cool, but how does it inject into this very complex workflow? You know? And if you don’t think about that, it’s kinda just a shiny widget for the organization.

Scott Shagory:
Yeah. No. I think that makes a lot of sense. Well, why don’t we go ahead and take a short break, and we will be right back. Purple Finch Group helps technology CEOs innovating at the edge of chaos create operational fitness across their technology stack and team of talent. Achieving significant and measurable scale, selling your story, and finding time to think and plan can feel like a bridge too far. So if you’re a CEO whose company has found product-market fit but is struggling or you’re a CEO whose company is looking to accelerate existing momentum, we can help with proven blueprints for optimal scale. Shifting from incremental addition to exponential multiplication can be absolutely achieved with less effort and stress.

Scott Shagory:
To get in touch, I can be reached at Scottwith2t’s@purplefinchgroup.com. Now back to the interview. Well, we are back here on the Discipline Troublemakers podcast with Jason. And so let me go ahead now post-short break and shift, shifting the question just a little bit here, which types of work do you do now as the CEO that you enjoy most or gives you the most energy? Is there anything there in your role that you really, really like?

Jason Young:
Man, I always find the questions about being a CEO to be the most challenging, you know, because I don’t think that when I was young, I had a vision of, like, this is what I’m gonna be. You know? Like, mom, I’m gonna be a CEO. Like, I don’t think I ever had that kind of vision. Sometimes I feel like it just happened to me, you know, where the reality of it was is like, I think my wife would probably agree with this statement that I tend to be a deviant, and I’ll, I’ll I tend to like to challenge the status quo, and that’s what I thought I was doing. You know? I was like, there’s something wrong here. We gotta fix this, and then I ended up being the CEO. So yeah. I always find those questions hard because it wasn’t like an intentional action for me.

Jason Young:
It was just the thing that must be done. Mhmm. But I will say I really love being around people. Like, I love, especially expert people. And so, you know, as we’ve grown as an organization and brought on just some fantastic subject matter experts in their field, I feel like I get to be, like, an observer in watching, like, a master class happen. You know? And I think that one of my most favorite parts is when you see it, it’s like, that’s amazing. And they’re doing it inside of my organization. It’s like, I don’t even understand it most of the time, but it’s absolutely incredible, and I’m just grateful that they’re even here. You know?

Scott Shagory:
Mhmm.

Scott Shagory:
Yeah. Well, I mean, I think that’s a sign though that, you know, if you’ve attracted that caliber and not just attracted but retained and they, you know, play well together in the sandbox, so to speak, you’re obviously doing a great deal right. And whether that is a little bit more hands-off, maybe it is hands-on, but only from the kind of the vision side of things and so forth. And then just, if you will, to borrow a simple phrase, not micromanage them to death, but to let them go off and do their thing, provide them with, you know, resources and so forth and accountability, but then kind of move from there. And they identify with you, you know, that’s, you know, that’s the essence of it here. You can add lots of layers and so forth. But at its core, it’s about, you know, leading a group of people to some place that is in theory, you know, better and greater, not just for the team and for yourself, but ultimately for obviously your perfect client or your industry that you’re in that you wanna go ahead and reshape. And it doesn’t have to be that complicated.

Scott Shagory:
It can be, but it doesn’t really need to be. It’s true. Quite that complicated. Yeah. No. It sounds good.

Jason Young:
I agree. I found, I think one of the hardest transitions into the role was kind of breaking free of maybe, like, an era or a culture that I grew up in.

Scott Shagory:
Mhmm.

Jason Young:
Which was time-based. You know, it’s like, you have to be here between this time and this time, and that’s how we know the work’s getting done. And what I found was that was just a not true belief. And so, like, controlling time doesn’t produce the result. And that was, like, a hard pill to swallow because I was challenged. And I don’t know where I think I might have seen it on YouTube or something where it was a logo designer. And he was challenging somebody about the cost of the logo, and he’s like, so if I gave you this perfect logo, you know? And but, but you said it was $10,000, but what if I told you it took me five minutes and it’s kinda like, oh, that’s uncomfortable. Like, how is it still worth it? You know? And to me, that taught me that, like, the functions are autonomy and trust.

Jason Young:
And what you want is the outcome, not the time effort in it. And so why then must we be concerned about the time? Why would we penalize someone for being really efficient with their time and then taking time to let their mind recover from the hard intellectual thought work that was done? What’s wrong with that if the outcome is achieved? Right? And so that took a while to settle in and be like, yeah. That’s the right culture for us. Like, we really have to, like, have this strong culture of autonomy and trust and flexibility, and what we measure is the outcomes, the results, not the effort prior to the result.

Scott Shagory:
Oh, yeah. No. I mean, but you think about, you know, most of us going to school was regimented. There were, you know, calendars and times and everything, and you were expected or you learned to observe and measure yourself within that. And when you think, most professionals, whether it’s, you know, CPAs, lawyers, most people, and even in the Fed space, you know, you have to very carefully as a contractor document what you’ve done and the amount of time that you’ve used otherwise, that’s otherwise known as fraud. So there’s all sorts of mechanisms, and when you think about going into sales, everyone’s trying to then compare you. And so it’s wise, you know, specs and feature sets are so prominent because you can just like buying a new computer, you can just line all that stuff up in a spreadsheet or equivalent and then just look very quickly and efficiently. But it doesn’t really get to the unique context that you might have, which in, you know, as you’ve explained, is really your team’s creative abilities and everything else.

Scott Shagory:
And does that foster them to the very best that you guys are capable of? And the answer is no. You need trust and you need autonomy and you need a few other of these other ingredients. And if that’s truly in place, you can then go ahead and create all sorts of cool things in the sandbox. But without it, it ends up being very constricted, which I think somewhat paradoxically may be in a compliance space where you might expect that to happen. It can’t happen without what you’ve just described, which I think, again, is reflective of controlling versus kind of, if you will, it’s a cliché, but empowering in ways that make things different for people who are trying to solve some very complex challenges with the DOD, which is not easy to do and do well and consistently.

Jason Young:
Thought work. We think of ourselves as thought workers, and now we really have to think about how we can be the best thought workers. Well, I know for me, I can answer that question of someone creating stress on my mind, you know, and, like, pressuring doesn’t unlock really efficient thought work. And so, like, that’s another hard truth, you know, where time off is almost as valuable, maybe more valuable, in thought workers than time on. And so, it creates this, like, uncomfortable tension where you have to be like, yeah. You should take some time off. And the goal is so that your mind can unwind. Because the reality of thought work is you just get wound up around really complex ideas, and it’s almost like a spring.

Jason Young:
If you don’t let the spring unwind, it just breaks at some point. And so, we have to hold like, it’s one of our values that you gotta have the freedom to not do thought work so that you can do thought work really efficiently. And I know in the government, that is a crazy concept. You know? Like yeah. That time off is actually good for the work product, you know, and that it’s very challenging for a lot of those folks to encounter that.

Scott Shagory:
Yeah. No. For me, whenever I have that spring that gets wound up, personally, for me, that’s time, assuming weather permitting, it’s not in January or December or something, getting out of my Ducati and just going ahead and riding out. I’m just outside of Va. So not that far away. I’m in Piedmont and it’s just a comfortable place to ride greenery and all those sorts of things.

Scott Shagory:
And because you do need to be ideally present when you’re riding a motorcycle, there are consequences if you’re not, that, yeah, it forces you to live in a motorcycle.

Jason Young:
Are we related? We might be related.

Scott Shagory:
So it’s just, I think it is important and you don’t realize it until you stop being able to produce quality content or compete with that unique solution and you just find yourself stuck, in a way that is just something you can’t or find difficult to unwind. And so for me, I’ve got a few things like martial arts, one or two others that are consistently able to break me out of that cycle. And I think we all need to identify with whatever that might be. If it’s simply going to the beach and reading a book or getting on your KTM or something else, whatever those things are, you know, spend real time intentionally refining those, if you will, so that you really get to the essence of what that joy actually is. And that’s really powerful.

Jason Young:
Yeah. 100% agree. I love to adventure ride. That’s the thing that owns, putting the bags on and then going out into the wilderness hundred miles away from anything. And I think there’s important realities there. You know, that we like to talk about in our culture because you have to acknowledge the spaces where you can actually do that because not being working does not necessarily mean that your mind is unwinding. And so, like, we talk about shower ideas a lot.

Jason Young:
You know? It’s like, I had a shower idea. Well, an interesting thing is, like, why do one have ideas in the shower? Why is that a common thing? And it’s my belief that you can’t do anything else in the shower. You can’t have a screen. There’s water everywhere. So you’re kind of there on your own. You know, again, you’re by yourself with just you and your mind, and so your mind has to unwind. It’s like boredom is this critical ingredient into the thought worker where you have to seek the space where your mind can do nothing else. And then that’s where it kind of unloads, and then the ideas start to flow.

Jason Young:
But I think we’re big on culture, but I think culture trumps everything. And I’ve read a book recently that I can’t remember the author’s name. It was “Recoding America,” I think. Jennifer, I don’t wanna get her name wrong. Palka? Fantastic book. Her statement was, “Culture eats policy all day long.” Like, you can have rules everywhere. If your culture doesn’t support it, it doesn’t matter.

Jason Young:
And for me, it’s like the culture is everything. That is the true secret sauce. Like, I would say behind it is that we really, really, really care about culture because it’s the bedrock for all the thought work that must happen, and we have to do everything we can to protect it because it’s so very fragile. Like, it’s just the most. Yeah. One bad drop of ink, it just ruins the culture. And so you just guard it constantly.

Scott Shagory:
Yeah. No. I think yeah. That drop of ink, red ink, I don’t know, into a glass of water or something. You can’t once it’s there, you can’t, you cannot extract it back out. Mhmm. Yeah. No.

Scott Shagory:
It’s true. It’s so true. How has, I guess, the kind of the semi-final question here, how has being the CEO of your company, has that either transformed you? How has that reshaped you in a way? Because you’ve been doing it for a while. This will be your fourteenth year. Yeah. So you’ve had a sense of real feel for how you’ve shifted, I would imagine, over those fourteen years? Is there something, you know, a single thing in particular or anything that you wanna highlight that you feel, you know, comfortable with sharing with the audience?

Jason Young:
Yeah. I think it’s very much challenging my kind of view of the world and our kind of workforce and even, mhmm. I would say being a dad most importantly. And, like, you really encounter people’s view of reality, and it doesn’t matter what you think about that at all. It’s just like your children, you know? Like, you encounter their view of reality, and to them, it is real, and that is true. And there’s nothing that you can force to make it different. So it kinda forced me to observe it and participate, you know, because everyone has a little bit different take on reality.

Jason Young:
And there’s, I guess, a sense of I don’t control this, and I can’t control it. And I also shouldn’t. I just merely have to accept it and understand what the view of reality is, and then the goal is to align. You know? And it’s kind of a vulnerable position, you know, but I don’t know any other way to deal with that. You know? It’s maybe akin to trust. Right? You can’t, I can’t force you to trust me, Scott. I can only offer trust to you. That’s my only card I have to play in the trust scenario.

Jason Young:
And so when we’re dealing with an organization, it’s a bit of that where it’s like, I have to accept your view of reality and offer trust. And that’s where we start. And then we start talking about, like, how do we align and start collaborating. And it’s a very vulnerable condition, but I think it just has to be that way.

Scott Shagory:
Yeah. No. I think we’re reminded of that a lot now in terms of people’s perception of what objective reality is or what’s important to them, the way they see the world. And I think the analogy around kids is great because that shifts so quickly typically too as they get older or have particular experiences that are very powerful. And we’ve all had them and I think we’ve all can look back on our lives and say, okay. I did believe this for this period of time, but it obviously turned out to be something else or my awareness shifted. And I now perceive that as being something different. Yeah.

Scott Shagory:
It’s a great way to, I think, remind us all how temporary that is. Yeah.

Jason Young:
And there are some consequences too if you approach it wrong. Right? Like, I could go to my kids and say, your reality is wrong, and here’s why. All I’m really doing is pushing myself outside of the circle of the things that they’re gonna talk to me about. Right? Like Mhmm. I’m the one that gets the consequence in that. Like, I don’t actually change their reality. And so I believe the way I have to encounter it is to be like, yeah. Tell me more.

Jason Young:
I wanna be inside your circle. Like, I wanna know more of why that is important to you, why you think about that. And it was this fine dance of staying inside that line of, like, you can trust me to talk to you about that, and we can work together to achieve the end goal. And what I realized is that it’s the same in the workforce. There’s no difference. Right? We’re just dealing with adults rather than children, but it’s the exact same engagement.

Scott Shagory:
Yeah. No. It is so true, and it’s certainly been my experience professionally either, again, in my old roles or this one now, is where, you know, a CEO tech CEO might be in his or her head is where they are. And that’s the experience that they’re having, be that good or challenging or a bit of both. It is so true where meeting people where they are in time and space is essential and really critical because that’s where the connection happens. And it’s not any place else by sort of ramming stuff either in their direction or telling them that they’re wrong. And I think we make that mistake too often, unfortunately.

Jason Young:
I totally agree. I think we can accept anybody where they’re at and disagree with them. They can be totally wrong. Like, agreement cannot be the condition of acceptance. So you can be like, you’re wildly wrong, but it’s cool. Let’s talk.

Jason Young:
Right? Like, acceptance first, then we can talk about disagreement. You know?

Scott Shagory:
Yeah. No. It is so true. Well, with that, let’s go ahead and finish out the interview. How would you like folks who want to, how would you like people to get in touch with you? Would that be either via LinkedIn or maybe your website or something else? What would be best for that?

Jason Young:
Yeah. I’m on LinkedIn quite a bit. That’s a great place to reach out. And then our website, pylonsecure.com. Mhmm. We would love to show you our software. Obviously, we’re very proud of it. You know? I’m clearly biased, but anybody who wants to see it, I’d love to show it to them. And so there are some ways to contact us through the website.

Jason Young:
But, yeah, either of those would be great.

Scott Shagory:
Yeah. Sounds good. Well, Jason, thank you very much for carving out time to chat with us today here on the Discipline Troublemakers podcast. And to all of you out there either watching or listening, we’ll be back with another episode very soon. Cheers.

Jason Young:
Thank you, Scott.

Scott Shagory:
Thank you for tuning into the Discipline Troublemakers podcast, and we hope you found the episode valuable. If you did, please subscribe to the Discipline Troublemakers podcast on your favorite platform and leave a review. Putting this podcast together is a group effort, so I’d like to provide a shout-out to Heartcast Media and their team for all of the assistance they provide with each episode. If you wanna get in touch with me directly, I can be reached at Scott@purplefinchgroup.com. Purple Finch Group is the sponsor of this podcast. We have another podcast episode out very shortly. Stay tuned.