About Deb Kaminetzky:
Deb Kaminetzky is the founder and principal of De Facto Project Management, where she works with teams during technology implementations so projects run smoother, cost less, and deliver the business results they were meant to. With more than a decade of experience across law, mediation, SaaS implementations, AV/IT integrations, and enterprise rollouts, she helps business, legal, and technical teams stay aligned and resolves competing stakeholder priorities before they derail a timeline. Her focus is on people, priorities, and outcomes, because successful implementations are never just about technology. As well as being a public speaker and software implementation trainer, Deb holds PMP, CSM, and LSSGB certifications.
What you'll learn about in this episode:
- Why the biggest misconception about project managers is that they're just “box checkers.”
- What a PMP certification actually requires, and how Deb's legal background sharpens her risk-anticipation and stakeholder management.
- The twenty dollar rule: a simple policy that keeps small missing parts from stalling an entire project, and Valiant's own version of it.
- What critical path actually means, illustrated through an office move with a lease deadline that can't move.
- A COVID-era story about a licensing rule nobody thought to check, and how it avoided thousands of dollars a day in fines.
- Why Deb believes project managers should be brought in before a project is even sold, not after.
- Why adoption, not just hitting the deadline and the budget, is the real third metric of project success.
- How to make good decisions with 85 to 90 percent of the facts, and why reversibility matters as much as information.
Transcript:
Megan Quick: Hello and welcome back, our dear audience, to The Creative Stack. It's a show about the intersection of creativity and information technology. I'm your host, Megan Quick, and I am joined by Georg, my co-host and the president of Valiant Technology. Georg, how are you today?
Georg Dauterman: We have a great guest today that I cannot wait to talk to, this is gonna be really exciting.
Megan Quick: We've been looking forward to this all week. Everyone, please welcome our fascinating guest, Deb Kaminetzky. Deb is the founder of De Facto PM. Deb, hi, how are you today?
Deb Kaminetzky: Hey, I'm good, so happy to be here.
Georg Dauterman: Excellent. I've known Deb for a while now, we've had great conversations, and I told Megan we have to have her on the podcast. So, I always like to start with the superhero origin story, how everyone gets to where they are in life. You have a really interesting background, I know a little bit of it, but I'd love to hear you go over it again, your professional history, how you ended up in project management and operations work, it's such a unique niche.
Deb Kaminetzky: I started out as a teenager loving video games, I always loved technology. My dad was an immigrant, and he decided I wasn't going to waste my time on a fad, he wanted me to do something like medical school or law school, the kinds of things immigrants aspire for their children. So I did, and I made them happy, but I kept my finger in technology, always self-taught, learning things. I ended up working for a family company doing commercial property management for a while, all kinds of projects, a lot of them IT projects, HVAC, elevators, all sorts of things where being interested in the technology of how something gets done is really helpful toward making a project go smoothly. Then I practiced law after that, and I didn't love it. I liked certain aspects of it, but not the area of law I was in. I did have a creative outlet for my tech love though, doing a lot of continuing legal education programs and committee work for bar associations on the intersection of law and technology, things like how to secure your technology, what technology to use. I once demoed twenty-five different law practice management systems so I could do a lecture for the New York State Bar on that. Then one day my dream job came up, and I say that tongue-in-cheek. I had an opportunity to work for a Microsoft vendor on a project called Zero Touch Deployment, training MSPs on how to deploy and image Microsoft Surface laptops in the cloud and have them drop-shipped from the distributor to the end user. Everyone's probably thinking, big deal, everyone does that now, but this was 2019, it was groundbreaking.
Georg Dauterman: It's still pretty hard, people think zero-touch is easy, but it's harder than people realize, it's not as simple as you think. It's still magic in my opinion, when it works exactly the way it's supposed to, I'm always amazed.
Deb Kaminetzky: I describe it as auto-magically, not automatically, because it does seem like magic, which is why it's so fascinating.
Georg Dauterman: When it works, it works great, and when it breaks, man, it's a whole thing. So, was it difficult to leave practicing law to work in a corporate setting, with all the normal day-to-day corporate stuff?
Deb Kaminetzky: It was definitely different. I ended up leaving New York, left my husband here so I could pursue this, I told him, look, I'm not going to get this opportunity again and I want to pursue it. I flew off to Seattle with two suitcases, put my law firm on a shelf, and thought, okay, examining the risk here, either this is going to go really well, or I could always come back to what I was doing. From my perspective, this was an opportunity. I talk about risk a lot in project management, the flip side of risk is opportunity, and I never want to tell people to be risk-averse, because if you don't take any risks at all, you're never going to accomplish anything.
Georg Dauterman: You want to leave the house, correct.
Deb Kaminetzky: Right, you won't get up in the morning. This was a great opportunity for me to see, okay, can I actually do this? Clearly, here we are in 2026, yes, I did it. When I came back to New York after that year-and-a-half assignment, I came back as a tech person, I was no longer considered a lawyer, I'd just done this tech job, and nothing makes people believe you can do something more than having actually done it.
Georg Dauterman: It's a recency bias, and also something so specialized and unique, and a name people recognize too, I think that's a really powerful component of it. So after you came back, where'd you go from there?
Deb Kaminetzky: From there I wound up working for an MSP, not one I had trained, interestingly, and the way I arrived there was also interesting. Different people were trying to help me get jobs, and the best way to get a job is to have somebody help you. I was introduced to the president of this MSP by a well-meaning contact who told him I'd make a great account executive. I met with him, and within five minutes he said, you don't really want to be an account executive, do you? I said, not at all. He said, but you took the meeting, why? I said, because you're the president of an MSP. He said, so what do you want to do? I said, I want to do project management. He said, well, we happen to need one, I'm going to introduce you to our VP, I met HR last, after the decision was already made. That really is the way to get it done, I know traditionally people think you just send in your resume, but meet with people, even if they're not necessarily the person you think is going to help you, because people get things done. AI is a big issue, I understand, but people get things done.
Georg Dauterman: Right, AI and HR systems and applicant tracking systems don't hire people, the person who has to make the decision, that's a human in the loop, it's really important to keep that in mind, that's why people still talk to each other. So now you're in project management, which is sort of what you were doing with the Microsoft work, but now at an MSP, what happened then?
Deb Kaminetzky: Then I ended up getting spirited away by an ATS company, an applicant tracking system software company, who wanted me to be a project manager for them. My boss at the MSP, who I'm still close with, was sad to see me go, but understood there was a lot I was going to learn over there, and I did. I learned a lot of really great things, and I learned some ways I would never run something in a million years. After that I worked for a nonprofit, also learned a lot, and after that I opened up my own company. So instead of switching careers by getting another college degree, I spent about four and a half, five years working in various corporate scenarios, learning as much as I possibly could, and parlayed that into my company, where I do project management and solutioning. It's been great.
Georg Dauterman: That's great. Project management is sort of a strange catch-all term, I like to be more precise. I know you have a PMP, which most people do not have, what exactly is a PMP, and how does it help a company, why would they want a PMP-certified project manager?
Deb Kaminetzky: I have a PMP, which is one of my designations, I have three, I also have a Scrum Master and a Lean Six Sigma Green Belt. The PMP specifically is Project Management Professional, and you have to have three years of running projects before you can even sit down to take the test. It's a formal test, three sections, I think sixty questions each, you either take it at home or at a testing center. I opted for the testing center because I didn't want to risk my electricity going out counting as an automatic fail, I felt risk-wise it was better to take it at the center. I passed it on the first try, as I did with the bar and all the other tests I've taken, which just means I'm a good test-taker, that's all that means, but part of that is understanding what they want you to know, it's not just memorization, it's analysis and decisions. The reason a company might want somebody with a PMP is because they have the project management experience and have also passed a test understanding all the different aspects of a project. In my case, having been an attorney for a number of years makes me better than just having a PMP, because when it comes to risk, handling different stakeholders, the mediation experience in rooms or on Zooms with people, understanding when to speak, when not to speak, when to let somebody else speak, asking really good questions, guiding the witness, which you're not supposed to do in law, but it really comes in handy when you're doing technology projects, because you want to make sure everything is clear, everything has been surfaced, assumptions are pressure-tested, all of that.
Georg Dauterman: I also feel like people trained as attorneys are taught to think a very specific way, a deeper understanding than the average person, because no one close-reads the same way an attorney close-reads. I'll glance over something and think, that looks good, and the attorney's like, stop, stop, did you actually read this?
Deb Kaminetzky: We once had a psychologist come speak to us about how attorneys have something called anticipated anxiety, where we're thinking of every single thing that could go wrong. That can be a good thing, because we're able to predict all the different things that could go wrong and have mitigation steps in case they happen, so people don't get blindsided.
Georg Dauterman: Just talking about project management, having that anticipation of what can go wrong and walking through the scenarios is so powerful, because you can guide the people you're working with to know what's going to happen and how it's going to work. Most people don't really know what a project manager actually does, especially if they don't work in technology. What are some of the things you think are important, or surprise people?
Deb Kaminetzky: A lot of people have a misconception that project managers are literally box checkers, this is done, this is done, this is done. One of the things we do is, there's almost always things that come up that people want in addition to what's in the contract, the nice-to-haves, the heated steering wheel, the "we just finished the kitchen, now the living room looks shabby" moments. We point out the pros and cons of doing those things at the same time, whether we need to make a phase two, whether you absolutely have to do something before you lose the capacity to do that second project, all of that, to make sure people are making really good, informed decisions. So often I've seen projects sold by a salesperson who didn't necessarily understand all of that, and then the client is left with something they're not happy about, or didn't know was going to happen. Having someone there saying, this is how it will go if you do this, have you considered these three other things, if you want to do this I'll almost never say no, I'll say, I'd recommend against it, and here's why, because I'm not going to tell the client what they absolutely should choose, but they need to understand what they're choosing. I don't want them to come back and say, I wouldn't have chosen this if you'd told me that was going to happen.
Georg Dauterman: I've lived that excuse myself, if I knew that was the situation I never would have done this. You have to make space for that, but also have the courage and conviction to tell people when something could be wrong. I think that's important in technology or any job really, but especially in this specific field, you have to be able to tell people, this may not go well, and I'm obligated to tell you why.
Deb Kaminetzky: Right, and also the people management of it, we're in a very strange position where nobody reports directly to us, yet we have to manage all these people without authority. You have a whole engineering team, all these different people, and you're not their actual manager, but you're the manager of the project, you still have to finesse that to make them want to do certain things. When I worked for the MSP, after two or three times getting a call from engineers, we don't have such-and-such cable, I instituted a new rule: if they had any item missing under twenty dollars, they were to go to the nearest supply store, buy it, bring the receipt back. Because otherwise, both of them aren't working right now, I'm not working right now, and that's more money than the twenty-dollar item. Later we can find out whether it was lost or not ordered, but that's not how we should be doing this.
Georg Dauterman: We have a two-hundred-dollar rule here at Valiant, inflation's gone up a lot. We'll very similarly derail a project for a twenty or thirty or hundred-dollar item, when you look at everyone's salaries, the downtime window, and the waterfall delays it causes downstream, just get it done, make the decision early in the process. In terms of what made you specialize in IT projects versus building projects, or that sort of thing?
Deb Kaminetzky: I had done building projects too, like I said. There was never any question I wanted to be in technology, the question was, at my advanced age, back in 2019, what was I going to do in technology? Chances are I wasn't going to be a software engineer, I didn't want to go into sales. There were all different sorts of things I could do in a technology system, and project management was the one I felt I'd be really good at, add the most value, and made the most sense for me. Although you don't need to know the technology to the point where you could do it yourself, you don't have to be an engineer to manage the project, you do need, in my opinion, to understand it well enough to know, for instance, is this engineer BS-ing me, or does it really take that long to do whatever it is. Even with migrations, which notoriously can fail and just not happen and you have to start over, how much time do you actually need to plan, leaving buffer. Buffer, for people who don't know, is the time in between, like going to your doctor, you leave fifteen minutes earlier than you think you need in case of traffic, or you can't find a spot. That's called buffer in a project. To know how much buffer you need, you have to understand all the different order of operations, what needs to happen. A lot of project management software has this really cool aspect where if you move one subtask it will move the others, but not if it's on what we call the critical path, something that can't be moved. In the MSP world, somebody's moving from one office building to another, there's a drop-dead date, your lease ends September 30th, you need to be in October 1st, that date cannot move. It'll show up as a red dependency if you try to move it, because you can't move the furniture on October 2nd if you're already supposed to be out by that date.
Georg Dauterman: I think so many people don't fully grasp the idea of the critical path, it's one of the areas we try hard to explain, especially when people start working on technology projects, any project in general. Have you ever seen someone blow past a critical path in a way that's been really ugly?
Deb Kaminetzky: I'd like to feel I've seen it all over the past seven years, but I'm sure something will happen.
Georg Dauterman: The universe never ceases to amaze me in novel ways, you're like, I never would have thought that was the case, but here we are, it's pretty amazing.
Deb Kaminetzky: Like last year I think we had two earthquakes, and I never would have thought we'd have earthquakes, but that could make a difference in a project.
Georg Dauterman: A hundred percent, we've had weather delays no one discussed, snow, and a truck can't get where it has to go, a delivery is delayed, and that was a critical component, and now what do we do?
Deb Kaminetzky: Weather's always on my risk register, earthquakes in New York have not been, but now they are.
Georg Dauterman: Now they are, hurricanes I'm sure are on there too. So, all the years we've been doing this, we always love a good disaster here at Valiant. Do you have a good off-the-rails story for us, or something you're like, man, this is bad?
Deb Kaminetzky: I'll give you an example of something that could have been off the rails, except I was there. During COVID, the MSP I worked for started getting a lot of requests from C-suite individuals who didn't want to go into their Manhattan offices because of COVID, asking, can you duplicate or replicate the setup I have in my office at home, so I can work from home but still have all my security protections, my SonicWall, all my things. These projects started coming across my desk, I noticed the first one, then more of them. I'd worked for the New York City Department of Consumer Affairs when I was in law school, and this was just a fluke, information I happened to have, and I said, there's no handyman line item to poke holes and affix these things on the wall in people's homes. They said, but it's a commercial project. I said, yes, in somebody's house. They said, but it's commercial. I said, but it's in somebody's house. They said, okay, so what happens now? I said, without a handyman, technically there's a five-hundred-dollar fine per day for every single one of these out there. You've sold ten, that's five thousand dollars a day. That fine can be avoided if you get a handyman to do this. And they said, okay, there was no more question at that point, because they understood what could have happened. So I prevented that from happening.
Georg Dauterman: You gave them the risk, the reason for the risk, and how to mitigate it, that's a huge difference.
Deb Kaminetzky: Right, or they wouldn't have even realized, that's the other thing.
Georg Dauterman: We don't do housework in houses, we might have done it once or twice a long, long time ago, not admitting to any kind of crime, but it's a very different job, someone's home is different from a business, there's no COI to pass, if it's a residential building it might have completely different insurance rules. We stopped doing that for years, we have a partner for it and send that work to them. But you hit the nail on the head, it's a very different gig, and you'd never know. Actually, the first time you and I met, you were telling me about this in passing, and I thought, I didn't know that, I went and looked it up because it was so interesting, who would know that working at an MSP. Very few people would, I think it's a good intersection.
Deb Kaminetzky: And it wasn't something anyone would have done except for COVID, people were trying to find ways to get things done, which is admirable. I have a few other stories, but in the interest of time I'll let you go to your next question.
Georg Dauterman: You and I will have to catch up over a cup of coffee sometime, I don't drink either, so coffee's where it's at. Out of all this, what was the really vital thing you learned from that experience, good intentions but someone didn't know? What was your takeaway?
Deb Kaminetzky: My takeaway, and one of the reasons I started my company doing solutioning as well, is that project management should get involved in projects at the very beginning, before the project is sold. Because a good project manager would be able to point out some of those risks early, so you understand how you're scoping it, what else is going on. And it's not just that type of thing, in businesses there's frequently other things going on, like, do they have good processes or not. I had somebody tell me they needed AI automations, and I asked, what kind of automations do you have now? He said, we don't have any. I said, okay, let me explain the difference, you have to have your process first, because if you automate something that's bad, it will just happen faster. Anyone who's seen that episode of Lucy with the chocolates knows, you don't want to make something faster unless it's good, you've tested it, you know it works. That's what you need to do first. And also the fact that you're selling somebody something based on what they say they want and what they're telling you they want to achieve, but sometimes there's a mismatch between what the customer says they want and what they could actually have, understanding the pros and cons of which way to go, and their participation in it, the fact they'll have to give up time from their regular job to help make sure the thing gets tested and adopted. That's why I feel it's good to have project management involved from the beginning, not just, we now have a project, let's slap somebody on it to manage it.
Georg Dauterman: You said something that hits one of my pet peeves and things I want to solve. I've worked in IT most of my adult career, and one of the things I've seen time and again is a failure of adoption on a project. I think that's something a good project manager can get ahead of, discussing adoption before the project even gets started.
Deb Kaminetzky: Yes, absolutely, that's one of my pet peeves too. I've worked in places where the project got stood up and people just didn't like it. Everybody says project management equals on time, on budget, but from my perspective there's a third one: adoption. Because if it's on time and on budget but nobody uses it, it's a paperweight, and what did you actually accomplish? Nothing, in my opinion. By getting a project manager in early, you get stakeholder engagement, making sure you're speaking to the correct stakeholders. I can tell you, many times there are people in an organization doing things outside the official software or process, and people don't even necessarily realize it, because they didn't like the last thing that got stood up, so they're doing it a different way, or using a different software, or there's that spreadsheet only they invented and only they know how to maintain. You want to make sure you're interviewing a good cross-section of people who are going to be working with whatever the solution is. Also, when people have something to say about the solution, they're more likely to adopt it. You tell a kid, go clean your room, they'll resist you. You say, your room is a mess, what should we do? Listen to what they have to say, maybe I'll do the closet this week and the shelves next week, okay, great plan, and they're more likely to do it because they came up with it, they had something to do with it. And then there's the change management aspect, making sure training is happening. Training should never be an afterthought from the very beginning, we need to talk about what kind of training there will be, who will do it, how. I was once introduced to a company looking for training after they'd just finished implementing a solution, and I told them, whoever did your implementation would be in the best position to do the training, because they've gotten to know your company and understand where you were and where you are now. I only train on things I've been present for, because it makes so much sense, I don't have to go back and find all of this out. The training absolutely has to be planned for as part of the project.
Georg Dauterman: I've found that as well, it's always the afterthought, or the one where leadership doesn't participate in the training, even though they're the ones who need to lead by example for everyone else's behavior, that one always gets me going. And just to go back to AI for a second, everyone wants AI magic, but it's not magic, it's a tool, and it needs project management, application support, all the things we've always had, that's not going to change. Do you have thoughts on AI? I always love hearing your perspective.
Deb Kaminetzky: Of course I have thoughts on AI. For one thing, compliance-wise, I always want to make sure people understand what they're putting into anything AI, are you letting it use your stuff for training or not. People think, yeah, I toggled that off, but if you read the terms and conditions, this is the legal half of my head talking, sometimes there are other things you need to do to opt out besides just pressing a toggle. You need to understand all of that, you need your own clients to know whether you're using it or not, there need to be policies. Those things go a bit beyond project management, but they have to do with people's IT and their IT stack. It can be really, really good, but you've got to get those processes down, understand what you're trying to accomplish, how you want it accomplished, and then you can use AI for certain aspects of it. And going back to what you said about leaders, I like to record trainings and give them to the client to hold onto, so a month from now when they're practicing they can go back and look at it. I don't like trainings that go into the ether. AI is wonderful, but you really have to have a strategy for it, you can't just say, there's this new shiny AI software somebody's telling me about and it's going to solve all our problems. It can solve some of your problems, and create others. You need to understand, and testing is very important, test it, see what it does before you put it into production.
Georg Dauterman: We're definitely seeing this with clients, looking at it as a magic-wand situation. I've heard a quote recently, it doesn't do as much as you think in the beginning, but it's going to do a lot more in the end, that's how I'm approaching it too, right now it's not doing everything we think it can or will do, and it's going to do a lot of new, novel things we haven't thought about, which is cool.
Deb Kaminetzky: I love that you're calling it a magic wand, because magic wands make rabbits disappear.
Georg Dauterman: That's a good way to put it. I've talked to so many leadership folks and executives who are unfortunately in this FOMO mode, afraid they're behind, missing out, getting leapfrogged, and maybe they are, maybe they're not. I think there are a lot of AI frauds out there too, people saying they're doing all this stuff, and I think, like anything else, it's an amazing technology, but not what people think it is at first blush.
Deb Kaminetzky: Right, there are also a lot of people who know how to do things with AI, or know how to teach you to do things with AI, but aren't necessarily considering all the implications, compliance, security, all of that. It's a bit like a surgeon, they've been trained in the whole first-do-no-harm thing. A lot of people out there today know how to do certain things and can get it done, but after that, it doesn't affect them if something goes wrong. You really need a strategy, ask the right questions, think about those things. I'm not saying be afraid, and I'm not saying don't do it. I actually have a friend trying to learn all these AI things to do himself, and I asked him, have you considered that by doing it all yourself, you're never actually going to get it done? You might need to delegate parts of it to somebody else. But by the same token, you need to understand who you're hiring, ask the right questions, and if you don't know what the right questions are, ask somebody who does, there are people who can help with that. Because you want to set this up well, you want a good result. And the FOMO, I get it, you don't want to be the last person to adopt, but you also don't want to be the first. I've been saying my whole life I want to be the second person to try teleportation, because I'd love to be able to just be somewhere else without traveling, but I don't want to be the first person to do it, I want to see what happens to the first person.
Georg Dauterman: Yeah, I don't want to turn into a fly, or a bucket of jelly. A hundred percent.
Deb Kaminetzky: I'm a huge sci-fi fan, so I get that. There's definitely a balance, you shouldn't take too long, but you also shouldn't be too quick, and I realize that sounds like a horrible answer, there's never a right time. I'd say, and this is another thing with project management, being able to make a good decision with somewhere around eighty-five to ninety percent of the facts is the sweet spot. Yes, there's ten percent you don't know, and the people who want to be absolutely sure will never take a risk. But on the other hand, you don't want to say, I've got fifty percent of the information and I'm fine either. There's a kind of mathematical sweet spot for how much you need.
Georg Dauterman: You don't want to be the fire-aim-ready person, any more than you want to be the person cowering under your sheets every day, there's a balance to it.
Deb Kaminetzky: And is it retractable, that's another big one. Can we revert? If you can revert, you can go forward with a little less information. If it's something you can't undo, then I'd want more information.
Georg Dauterman: We like to call that the one-way trip here at Valiant. Is this a one-way trip, is there no path backwards? And if the answer is yes, if we do this there's no way back, then we really have to think long and hard about what we're going to do. So, in the interest of time, and you and I could keep talking for hours, what are three project management truths, the ones you live by, and if you don't, you're kind of bonkers?
Deb Kaminetzky: I did have some notes on this. I already said some of them, but to me, on time and on budget are nice to haves, the idea is you want adoption, and you want whatever you're setting up to achieve what you're trying to achieve. That's number one. Number two, it's okay to pivot or abandon a project. Some people say, but we've already spent so much time or money, the sunk cost theory, but it's okay to say something newer has come up and this is going to be better, or something has changed in our business or out in the world, and we no longer feel this is necessary. That's okay, it's better than finishing something just for the sake of finishing it. And the third is document, document, document. By that I mean, document what you did, how you got there, how you could fix it, your training, everything. I like to have retrospectives at the end of every project, talking about what we did that went well, that we want to repeat, and what we did that didn't go well, that we don't want to repeat, and why it didn't go well. Because if you don't do that, you're going to be set up for the same exact problems on the next project.
Georg Dauterman: I could tell you, even here, it took us many years, and I'm almost embarrassed how many years it took to build a formalized postmortem project process. Way longer than it should have, we all kind of knew better, we were trained to do it, but the actual act of doing it can get very hard. When you start doing it and stop making the same dumb mistakes over and over, it almost looks like magic on some level, because everyone else we work with does this, that, the other thing, and you're like, well, we've made that mistake, we documented it, and we knew how not to do it again.
Deb Kaminetzky: And from the client's perspective, they may have a new person coming in who doesn't know because they weren't there. So the client themselves should document it too, if they get a new VP or CEO, a merger or acquisition, whatever, "yeah, we considered that, these are the reasons we didn't do it," is a lot better than, "we don't want to do that."
Georg Dauterman: Or the dreaded, "that was before I was even here, that's just how it's always been," which is a terrifying comment for anyone to say, in my opinion. When you hear it, you think, okay, yikes. So, Deb, this has been amazing, I'm going to let Megan take us home, because she does a way better job than I do, I start chatting, I go off the rails, so I let her do it.
Megan Quick: That's just the risk when we like our guests, obviously. Deb, I always take notes during these interviews, and I have a few things that really stuck out to me. I think this episode is going to be so helpful for so many people, I hope they listen and it shifts perspectives for people who are too intimidated to start figuring this stuff out, this is a good, comfortable place for them to start, and you've made this knowledge so clear. I wanted to say, the flip side of risk is opportunity, I love the twenty dollars of room, two hundred dollars of room if you're at Valiant, to go get whatever you need and not stall the project. I have a theater background, that feels very theater, we just gotta keep going, guys, we gotta get this done. And I really loved "what are the right questions, and if you don't know what the right questions are, find the person who knows the right questions," those were the gems you dropped during the interview. Deborah, if you want people to find you, where can they find you after they listen to this episode?
Deb Kaminetzky: I'm on LinkedIn, Deb Kaminetzky, I'm the only Deb Kaminetzky on LinkedIn, part of the benefit of having an unusual last name. And DeFactoProjectManagement.com, spelled exactly that way, is my website. I'm on Google too, and I think AI is picking up some of my stuff. I work with vendors, MSPs, and clients, never at the same time, because if I'm representing one, I'm not representing the other.
Georg Dauterman: Conflict of interest, it's important, it's critical, very cool.
Megan Quick: I love your attorney mindset, this is great. Deb, thank you so much for joining us today, and if y'all enjoy The Creative Stack, please like and subscribe, you can find us wherever you get your podcasts. Thank you so much for joining us, Deb, I won't be surprised if you're a guest again on The Creative Stack, we really, really enjoyed having you today.
Deb Kaminetzky: I had an awesome time, thank you so much.
Georg Dauterman: Thank you so much, thanks, alright, bye.
Megan Quick: Have a great day everyone, see you next time.
Nov 18, 2026