Ep 4: Radical Responsibility in Manufacturing and Small Business

Radical Responsibility: Why Owning Outcomes Is Genuinely Empowering (Episode 4)
The Integrate Intelligently Podcast, Episode 4 — with Jeff Bickler and Scott Bickler (CADTALK)

Jeff: Hello, I'm Jeff Bickler, welcome to The Integrate Intelligently Podcast — I'm your co-host, joined by my brother, founder and CEO of CADTALK, Scott Bickler. The podcast is sponsored by CADTALK, an integration platform for engineering software — CAD, PDM, and PLM — with popular ERP systems. Over the last few episodes, we've been walking through our core values, and today, episode four, we're covering another one: Radical Responsibility.

The Power of Radical Responsibility
Jeff: Radical Responsibility — I think the name speaks for itself in some ways, but it's really the idea of owning something from start to finish. That doesn't mean you don't collaborate or involve others, but you make sure it moves from initiation all the way through to completion, rejecting the idea that you're somehow blocked purely because of someone else. A lot of organizations lack this — you see constant finger-pointing, silos, "that's not my job." What we're really after is breaking down those silos, so people, both at the office and in life, take radical ownership of seeing things through to their conclusion. Scott, you developed these values — what drove Radical Responsibility specifically? Is there something from your own life, from childhood through your career, that shaped this one?

Scott: It really stems from working at other companies before we started this one, and seeing the traditional failure points that show up in organizations over time. At past jobs, there was a lot of "well, I told so-and-so, and I don't know what happened after that," or "we were waiting on someone else to pick up the ball" — dropped balls everywhere. When you found a company yourself, and it's just you, or you and one other person, you quickly realize — cliché as it sounds — the buck genuinely stops with you. There's nobody else to delegate blame to, nobody to say "I'm waiting on so-and-so." You realize pretty fast that the market, and your customers, genuinely don't care whose fault something was — you have to overcome it and figure out how to deliver the result they're looking for regardless. Sometimes people say "the customer didn't respond to me," and my reaction is: what did you do to make sure they responded? What did you do to move it forward? The customer's paying us for an outcome, and they want that outcome regardless of what happens along the way.

This ties into another one of our values, Outstanding Outcomes — but the core idea here is: if something's handed to you, you own it, and you drive it to completion, instead of saying "it's sitting over there, that's someone else's responsibility." It's always your responsibility to keep pushing it forward, even when it's technically outside your direct control.

Jeff: Do you think that's a direct result of starting your own company — did founding CADTALK force you into this, or did it come from somewhere earlier?

Scott: I think it's largely necessity. In the early days, when we were genuinely struggling to get things off the ground, it was very tempting to fall into that same trap — "the customer didn't follow up," "the vendor we worked with didn't include us." It always felt powerless in that moment, like you had no real control over the outcome, so it must be someone else's issue, outside of you. And even if that's technically true, it's simply not helpful. I've come to prefer framing things around what's actually useful, rather than strictly what's technically your responsibility — because even when something genuinely isn't in your control, choosing to believe you do have some agency over it turns out to be far more useful. It lets you take actions you otherwise wouldn't. Take that earlier example — a customer has a bad internal process causing an issue. You could say "that's their problem," or you could say "I'm going to try to convince them, educate them, get them to the outcome they're actually paying for, and take ownership of making sure they get a genuinely good result." Once you adopt that belief — I own this, I have to make it happen — you naturally take actions well beyond what most people would.

As a founder, there was also genuinely nobody else to ask half the time — no one to turn to and say "I need you to make this call." You're the only person who can. As the company's grown, we've deliberately tried to push that same sense of ownership further down into the organization, so people can own things and make decisions themselves, rather than everything constantly funneling back up to me.

Jeff: I remember hearing about how CADTALK actually started — you deciding, over 20 years ago now, that you wanted to build an application, an idea you genuinely had, and just starting it. Can you share an example from those early days — a moment where you couldn't rely on anyone else, and had to figure out a way around it yourself to get what you needed?

Scott: I actually remember something even before the company itself — I was working at a manufacturing company at the time, and we used to joke about being on "Project BIFF" — a reference from a Dilbert cartoon, "Big Improvements For Free." I'd started as a co-op, then moved into IT, and part of my role was going around to different departments identifying software changes or process improvements we could make. But I had literally no budget — so I couldn't buy any tools or software; all I really had was my own time.

Being Radically Responsible: What Does It Really Mean?
Scott: I remember being genuinely frustrated multiple times — "if I could just buy this one tool, I could get this done" — and feeling limited because I had no budget or real control over that. Over time, though, I found open-source projects, or figured out how to build something myself — I had to push harder and dig deeper, and honestly, that constraint built real character. Constraints genuinely hone you; they force extra work and extra research you wouldn't otherwise do. I could have simply said, "I need budget for this, there's nothing I can do without it, this project's stalled" — but instead, because I still felt responsible for the outcome, I couldn't just sit there doing nothing. I'd find a way — cobble something together from open source, or whatever we already had — to still make real progress despite having no budget at all. That's a genuine example, even before we started the company, of that same underlying approach.

Jeff: That struggle really is what builds character and pushes you forward. I think Radical Responsibility genuinely hardens you in a good way — because if you instead say "I don't know how to do that, so it's not on me," or "I wasn't trained for this, that decision isn't mine to make," you end up limiting yourself — your own growth, your own ability to improve. If you don't take responsibility for figuring something out, you never get the opportunity to actually build the thing, or travel abroad, or accomplish whatever it is — you never get past the obstacle in your way. But if you take that responsibility on — regardless of the obstacles, regardless of what happens, I'm going to own this and see it through — that pressure, even though it's self-imposed, is really what shapes you. Would you describe Radical Responsibility as fundamentally self-imposed pressure?

Scott: I actually think of it as more empowering than pressuring. If you're genuinely responsible for something, you're implicitly admitting to yourself that there's something you actually can do about it, rather than something you can't. People tend to have all kinds of reasons why they can't do what they want, and they almost always point externally — "I can't because of my parents," "because of my spouse," "because of my kids," "because I don't have this resource." They're constantly pointing elsewhere for why they can't move forward, and that's genuinely disempowering. I always want to ask "and then what?" — "I can't do this because of X." Okay, so I guess you're just never going to succeed at this, ever? People rarely actually agree with that when you put it that plainly — which tells you they're really just looking for permission to not try. So to me, being radically responsible is fundamentally freeing rather than constraining — you're declaring you have the ability to actually do something about it, and because you own it, you can move it forward, despite whatever's happening around you, instead of hunting for reasons why you can't.

Taking Actions Beyond the Norm
Jeff: That reminds me of a teacher I once heard about who worked with a lot of at-risk youth, kids from genuinely difficult backgrounds. They'd come in with excuses — "I couldn't do my assignment because of this," or "I just didn't care" — the usual finger-pointing. Her response was always the same, almost brutally simple: "so what — now what?" Her underlying message was consistent: yes, the situation genuinely stinks, it's unfair, you got dealt a bad hand — just like anything in life, a job you're handed, circumstances you're born into, even something as trivial as losing your hair when you wanted to be a hair model. Instead of dwelling on that, the real question is always: so what — now what are you actually going to do about it? Because how you respond is really the only thing genuinely within your power. That's the only thing you're actually responsible for — not the external conditions, but your own response to them.

Scott: Tactically, you see this constantly with employees too — people are afraid to take ownership because they're afraid something might end up being their fault. So they defer decisions back up the chain, or just say "I don't know what to do," and you end up in this transactional back-and-forth — "do this," "okay, checking," "now do this next thing," constantly cycling — versus a genuinely transformative management style: "here's the outcome I need, you own getting there." Otherwise you get this whack-a-mole pattern — "do this," "I got stuck," "try this instead," "still stuck, don't have the training" — and the manager just keeps knocking down objections one at a time.

A genuinely useful tactical framework I picked up is called "1-3-1" — I believe it comes from Dan Martell — one problem, three possible solutions, and one recommendation. The idea is nobody can bring you a problem without also bringing those three things — they can't just dump it in your lap for you to fully solve. That forces them to actually think it through themselves, which kickstarts real ownership over the outcome, because once they've genuinely worked through that thinking, they tend to move forward on their own rather than staying stuck. You also have to genuinely foster that — let people know it's okay to make a decision, and if they make one you'd have made differently, still support it: "that's fine, at least you made the call." Otherwise you inadvertently teach people that you want to be consulted on everything and decide everything yourself, which backfires. People are naturally hesitant to take ownership unless they're genuinely empowered to.

Jeff: I see that with my own kids, and I saw it teaching too — it's just human nature to avoid responsibility when you can, because responsibility, as you said earlier, isn't necessarily painful, but it's genuinely harder. It's easier to hand it off to someone else — "you take care of that." Not to get political, since that's not what this show's about, but especially around election season, you see a lot of people wanting someone else to fix the problem — "if the right people get elected, everything gets fixed." But really, everything external is largely a reflection of ourselves. If things aren't in a good place — society, a business, whatever — that's often a reflection of what we as individuals are choosing to do, or not do. Handing the responsibility to someone else means you get what's easiest for them, not necessarily what you actually want — and if you don't hold yourself accountable, nothing genuinely changes, because the outside world really is a reflection of what's happening on the inside, both individually and organizationally, since an organization is really just a collection of people.

The Empowering Nature of Radical Responsibility
Scott: People avoid taking responsibility largely because it's genuinely difficult — admitting "that was my fault" hurts, it's an ego hit. So people avoid it. But the real trade-off is short-term versus long-term pain. If something at CADTALK doesn't go well — a project's poorly implemented, we don't serve a customer well — that's ultimately on me, I'm the CEO. It doesn't matter whether I personally forgot to send an email; I'm still responsible, because I influence the direction we set as a company. Choosing to own that, and accept the short-term ego hit of "this didn't go the way it should have, and I'm responsible," is exactly what empowers you to actually make it better going forward. Avoid that, and you're doomed to repeat the same mistake indefinitely. It really is a short-term-pain-for-long-term-benefit trade-off.

Jeff: How does blame factor into all this? I remember reading about a cultural contrast — American culture tends to be more blame-oriented than, say, Japanese culture, at least according to one book I read. In America, if something breaks, the instinct is often "who broke it," identifying and holding someone accountable, sometimes punitively. The author's argument was that in Japan, the instinct tends to be less about assigning blame and more simply "this thing's broken, let's fix it" — less focus on fault, more focus on the next needed action. Does that instinct to assign blame get in the way of Radical Responsibility? I know avoiding blame is a real, common dynamic in companies, families, everywhere — people are genuinely afraid of the consequences, sometimes real career consequences, of being blamed for something even when it wasn't truly their fault. How do you balance genuinely wanting to be radically responsible with not wanting to be unfairly blamed for something outside your control?

Scott: Good question, and I'd honestly forgotten that specific cultural comparison, though I've heard something similar. If you can genuinely remove blame from the equation, and just accept that things go wrong sometimes — entropy, basically; not to get too technical, but the second law of thermodynamics essentially says everything tends toward disorder over time — something can just break because that's simply what systems do over time. Once you assign blame to that, you're effectively building in a punishment people will naturally try to avoid going forward. But if you can foster a culture that accepts systems fail and people forget things sometimes, you get people genuinely saying "this went wrong, let's focus on fixing it," rather than "who's at fault here." That's admittedly harder to sustain with genuinely repeated issues — it's hard not to eventually say "so-and-so just isn't doing their job" — but I think it's genuinely more productive, where possible, to push a culture where figuring out fault matters less than making sure it's corrected and doesn't happen again.

Jeff: That's honestly not far from what I used to teach, or hold myself to personally — genuine personal responsibility, which is a bit different from situational responsibility. Take a car accident, for example — you might not be at fault for the accident itself, but you're still responsible for everything you personally do in and around that event. So maybe Radical Responsibility is really about that distinction — did I take personal responsibility to do everything within my own power, even in a genuinely complex situation with a lot of stakeholders where some things really are outside your control? And if blame gets assigned right away, you're really just looking for someone to punish. Whereas if you can say, "I fulfilled my personal responsibility, I did everything I genuinely could," then even if you're unfairly blamed afterward, you at least know you upheld that value yourself.

Scott: Responsibility also extends beyond a pure fault question sometimes. We've had situations where someone leaves the company, and everything that went wrong beforehand quietly gets pinned on them, since they're not around to defend themselves. That genuinely undermines Radical Responsibility — the blame itself doesn't actually matter, because the underlying problem still exists. "So-and-so messed up the project before they left" — okay, but what's happened with it since? If the answer is "nothing," then we're the ones failing to be responsible now. Being radically responsible means taking ownership of something regardless of what happened before you — "yes, this was in bad shape, but I'm taking ownership of it now, and driving it to the right outcome," rather than leaving it as an unfinished thing you can conveniently blame on someone no longer around. It's both — taking responsibility for things you didn't personally cause, and picking up something that genuinely needs finishing and owning it going forward.

Jeff: There's also a genuinely positive side to responsibility when things go well — being able to say "I was responsible for that, I was a big part of making that happen" feels great, and it should. But taking responsibility regardless of the outcome is really the core of it — even when something's genuinely gone poorly, or someone's unhappy, being able to say "I made a mistake, here's how I'm fixing it, here's what I'll do differently next time" matters. Some problems are thornier than others — you might genuinely take responsibility eight times out of ten and miss it twice; that's just normal, part of striving toward any value without expecting 100% perfection from yourself.

Cultivating Radical Responsibility: Practical Tips
Jeff: What about within a team specifically, rather than purely individually? I imagine there's real potential for confusion there — especially in a business like ours, working across integrations with a lot of different stakeholders. How do you make sure each team member genuinely understands their piece of a shared, collective responsibility, versus their individual task-level responsibility?

Scott: There's a real difference between team dynamics and individual accountability. When there's a specific task or outcome that needs to happen, I generally prefer having one single, clearly named, responsible party. It ties back to that classic bystander-effect story — I believe it was in New York City, a situation where a crime happened and everyone assumed someone else would call the police, so nobody actually did. The advice that came out of that: if there's an emergency, don't just yell "someone call 911" — point directly at one specific person and say "you, call 911." I hold a similar belief with tasks — clearly assign it: "you are responsible for this." If they say "I'll be on vacation next week," fine — then you're responsible for finding someone to cover it while you're out. That keeps it unambiguous who's actually holding the ball, and what the next action needs to be.

Conclusion and Closing Remarks
Scott: When it's more of a broader departmental goal — say, hitting a specific customer satisfaction target — that naturally requires everyone contributing something, and there's a real element of positive peer pressure within the group pushing toward that shared outcome. It's a bit less direct than a single named task, but you can still always trace it back down to smaller, individually-owned activities that ladder up to the larger goal — every major outcome breaks down into smaller pieces that someone can genuinely own individually, with the team collectively applying that positive peer pressure to make sure everyone follows through on their piece.

Jeff: I remember growing up, peer pressure was always framed negatively — DARE programs, "don't get pressured into smoking" — but peer pressure can genuinely be positive too, pushing good behavior, which you see constantly in strong teams and sports environments. So — if someone genuinely isn't practicing Radical Responsibility today, how do they actually start? If you're early in your career, or just haven't operated this way before, what's the first step?

Scott: I think it starts with genuinely understanding the outcome you're actually working toward. If someone hands you a task, you can ask directly: what's the actual outcome you're looking for here? That lets you choose your own next steps and drive toward it yourself, and you can ask, "can I make some decisions here" to bring more of it genuinely under your own purview. The other technique: when you start feeling stuck — "I need this, someone else has to decide" — ask yourself, "if I genuinely had full control over this, what would I actually do?" How could I move this forward anyway, rather than assuming there's no path without someone else's input? That reframing shows you actually do have ownership — you're choosing to do whatever it takes to move to the next step, rather than stopping at the first roadblock and looking for someone else to hand you the answer. Even if your instinct is "I need to check with my boss first," ask yourself, "if I had to produce an answer right now, what would it be?" — try one thing, then another, keep moving in that direction. You build that muscle over time, and often realize you didn't actually need to ask in the first place — you just wanted certainty, and needed to get comfortable moving forward despite some uncertainty.

Jeff: Radical Responsibility is genuinely a little scary — there's real risk in it, unless you already know exactly how to do the thing or exactly how to reach the outcome. Declaring "I own this, it's on me" today can feel intimidating. But it's genuinely empowering too, because it pushes you to become a better person overall — at home, at work, as a friend, a son, a father, a brother. All of those relationships benefit from that same ownership mindset.

It reminds me of my sister — she doesn't live in Cincinnati anymore, moved to a different state, and I set up a standing monthly call with her specifically because I wanted to make sure we stayed genuinely connected despite the distance. I took responsibility for that relationship because it mattered to me — something I genuinely valued. I think we can apply that same principle across every part of life, not just at the office. Even with my own sons — I wanted them to have a genuine relationship with their uncle, and rather than just assuming that relationship would naturally happen on its own, I took responsibility for actually setting up a regular event to make it happen. Radical Responsibility really applies across every part of life — not just workplace accountability, but accountability in every relationship you have.

Scott: Completely agree — everyone tends to wait for the other person to act first. Someone has to go first, and honestly, it might as well be you.

Jeff: Exactly. What do you think genuinely holds people back — is it purely fear, or something else? People often say they "should" do something, without genuinely wanting to.

Scott: I think it often comes down to whether they genuinely value the thing enough, or feel like they do but their actual behavior doesn't reflect it. You can usually tell what someone genuinely values by looking at how they actually spend their money and their time — that's a pretty honest signal. People say they value something, but the reality doesn't always match.

Jeff: Maybe the ultimate form of Radical Responsibility is genuine honesty with yourself — acknowledging, "I don't do this, and here's the actual reason why," or "I do this, and here's my real reason." Because then you genuinely own it — that itself is taking responsibility.

Scott: The phrase that always comes up is "I don't have time for that" — and I like reframing it as "I'm choosing not to make time for that," because that's really what's true. Everyone genuinely has the same 24 hours; saying "I don't have time" is really just a softer way of saying it isn't currently worth prioritizing for you.

Jeff: Speaking of time, we're about at the end of our session here. Scott, really appreciate this one — these conversations about our values, and honestly getting a bit philosophical looking inward at ourselves, are genuinely valuable. Any closing thoughts?

Scott: Just that I think everyone could genuinely benefit from taking a bit more responsibility for the outcomes in their own life. All our values matter to me, obviously, but this is one I remember thinking through quite deeply when we first developed it — a genuinely important one.

Jeff: Great — thanks, Scott, really appreciate this discussion. Just a reminder, this is The Integrate Intelligently Podcast — I'm Jeff Bickler, this is Scott Bickler, thanks for listening.