A Digital Strategy Podcast
Your Tech Stack Is a Business Decision. Is Anyone Treating It Like One?
Episode Summary
Most technical projects fail not because of bad technology — but because the people buying, scoping, and implementing it never fully agreed on what they were building or why. In this episode of The Weekly Set, Symon and Marcello are joined by Deborah Kaminetzky, founder of Defacto Project Management, who gets called in when high-stakes technical projects are complex, off the rails, or both. With a background in law, corporate operations, and project management, Deborah brings a rare perspective: she understands both the business side and the build side — and knows exactly where the gap between them lives. Together, they unpack why so many organizations treat technical decisions as IT problems instead of business strategy, how vague goals and rushed timelines create expensive do-overs, and what it actually takes to set a project up for adoption — not just delivery. If you have ever inherited a system nobody uses, signed a contract before defining your workflow, or been handed a scope that one person wrote in isolation, this conversation is for you.
Episode Notes
What We Cover
- Why delivery on time and on budget is not the same as project success
- The 'meeting of the minds' problem: how misaligned expectations sink projects before kickoff
- Free text fields vs. structured data — and why that distinction matters for every dashboard you want to build
- Why AI makes strategy more important, not less: if you don't know where you're going, it'll get you there fast
- The warehouse problem: why the people closest to the work always know something leadership doesn't
- Technology adoption as the real success metric — and what training actually needs to look like
- How to run discovery when clients say it isn't necessary (and why that response is a red flag)
- Past state / future state: mapping where you are vs. where you want to be before touching a platform
Key Takeaways
- Technical decisions are business decisions. If they're being made without input from operations, finance, or end users, the scope is already wrong.
- Shadow IT is a symptom. When people build workarounds, it's because the official system didn't solve their actual problem — and your data is now fractured across both.
- Discovery is not optional. If a client won't let you talk to stakeholders before scoping, they are setting you up to build the wrong thing with confidence.
- The goal is adoption, not deployment. A project isn't done when it's launched. It's done when people are using it and it's doing what it was supposed to do.
- Slow down to go fast. The foundational work — workflow mapping, stakeholder interviews, requirements definition — is the work that prevents the $80K change order.
About the Guest
Deborah Kaminetzky is the founder of Defacto Project Management. She brings a background in law, mediation, and corporate operations to high-complexity technical implementations — specializing in ERP, CRM, and platform projects where business requirements and technical execution need to stay tightly aligned. She works across industries and is known for being the person in the room willing to ask the questions nobody else will.
About the Hosts
Symon Oliver, RGD is Design Director and Marcello Gortana is Executive Director at Tennis — a B2B web design and product development agency. The Weekly Set covers the decisions, patterns, and hard truths behind technical projects, vendor relationships, and agency operations.
Chapter List
- 00:00 — Navigating Complex Technical Projects
- 02:16 — Common Failure Patterns in Project Management
- 05:52 — The Role of AI in Project Efficiency
- 10:20 — Understanding Client Needs and Workflows
- 14:45 — The Importance of Business Outcomes in Tech Decisions
- 18:21 — Breaking Down Communication Barriers
- 21:58 — Defining Project Success and Adoption
- 25:48 — The Foundation of Successful Projects