A Digital Strategy Podcast

Tennis

A Digital Strategy Podcast explores how design, technology, and business intersect to shape the way organizations grow and adapt. Through thoughtful discussions and interviews with leaders in tech, design, brand, and marketing, the show shares practical strategies, frameworks, and stories for navigating today’s digital landscape. Hosted by the team at Tennis, the podcast blends sharp takes on the industry with candid conversations about the systems, tools, and decisions that drive lasting impact.

  1. Your Tech Stack Is a Business Decision. Is Anyone Treating It Like One?

    1D AGO

    Your Tech Stack Is a Business Decision. Is Anyone Treating It Like One?

    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. Website: https://defactoprojectmanagement.com/ LinkedIn: https://www.linkedin.com/in/deborah-kaminetzky-pmp-fractional-project-manager/ 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 Links You can learn more about Tennis at our website. Be sure to follow us at LinkedIn, YouTube, Instagram, or Twitter

    36 min
  2. Your product timeline isn't broken. Your definition of done is.

    MAR 6

    Your product timeline isn't broken. Your definition of done is.

    Product teams don't miss deadlines because they're slow. They miss them because no one ever defined what "done" actually means. In this episode, Symon and Marcello dig into the structural and cultural gaps that quietly blow up product timelines — and what you can borrow from the services world to fix it. What we cover: No governance = no finish line. Without a roadmap and defined milestones, scope is infinite. Teams can take as many liberties as they want with what counts as complete — because nothing ever officially is. You can't think and make at the same time. Conceiving a feature and building it simultaneously is one of the most common (and costly) product anti-patterns. Strategic thinking has to happen before the work starts, not during. Agile isn't a cure-all. Every Agile project Symon and Marcello have joined without managing themselves has introduced friction. Scrum roles, dashboards, ceremony overhead — it's not wrong, but it's also not free. Feature creep needs a scorecard. We reference the RICE framework (Reach, Impact, Confidence, Effort) as a baseline for evaluating whether any feature is actually worth building — before anyone opens Figma. The HiPPO effect is real. When the highest-paid person's opinion drives the roadmap, you get flavor-of-the-week features and no strategic coherence. Investor-clients can quietly hijack your roadmap. When early clients are also investors, their feature requests carry disproportionate weight — often at the cost of actual product direction. Stakeholder alignment is your first deliverable. Before scope, before design, before a single line of code — get everyone at the table and make the plan the first collaborative output. Resources mentioned: RICE Scoring Framework (Reach, Impact, Confidence, Effort) r/buildinpublic on Reddit Chapters 00:00 Intro — Why speed is the promise, delay is the reality 00:43 Who we are and what we're covering today 01:21 Deliverables world vs. product world — a culture clash 02:10 Root cause #1: No roadmap, no governance 03:15 Root cause #2: Thinking and making at the same time 04:00 Root cause #3: Agile's hidden baggage 04:30 Root cause #4: Feature creep and RICE scoring 05:16 The HiPPO effect — when the highest-paid opinion runs the roadmap 06:20 What mature product orgs do differently 07:14 The investor-client trap — when funding steers features 08:00 Why teams struggle with "done" — too many stakeholders 09:30 What happens after launch (the part nobody plans for) 10:40 Sequencing as a discipline — installing a mini operating system 11:36 Practical advice: where to start depending on your lifecycle stage 13:29 Stakeholder alignment IS a deliverable 14:22 Hard truths and closing takeaways Links You can learn more about Tennis at our website. Be sure to follow us at LinkedIn, YouTube, Instagram, or Twitter

    16 min
  3. The SaaS Apocalypse and the Rise of AI-Driven Custom Tools

    FEB 27

    The SaaS Apocalypse and the Rise of AI-Driven Custom Tools

    Key topics: The concept of the SaaS apocalypse and its driving factors How AI tools like Claude Code, Claude, ClawdBot and others are enabling bespoke app development The declining economics of SaaS subscription models The impact of AI on employment, stock markets, and investor behavior The importance of UX and integration in product development Strategic shifts for SaaS companies: focusing on core features and tight integrations The probable future: distributed, fragmented software ecosystems with interoperable components Timestamps: 00:00 - Introduction to the SaaS apocalypse and its relevance 02:17 - How ChatGPT and AI tools are simplifying development workflows 05:04 - The disruption of traditional SaaS pricing and value propositions 07:55 - What is the SaaS apocalypse? Overview and core fears 09:20 - Impact on stock markets and investor sentiment 11:27 - AI's rapid evolution and implications for white-collar jobs 12:23 - Key technical drivers: Claude code, agent reasoning, and automation 14:49 - Lowering costs and decentralizing software creation 16:05 - Consumer versus enterprise AI adoption challenges 18:14 - Adoption rates in AI: lessons from color TV history 19:03 - User behavior trends and incremental AI adoption 21:04 - Market shifts: smaller, focused tools vs. bloated platforms 22:36 - Importance of UX and strategic integrations in product success 24:06 - Building with network effects: integrations over feature bloat 25:37 - The future landscape: distributed, interoperable, fragmentated SaaS ecosystem Links You can learn more about Tennis at our website. Be sure to follow us at LinkedIn, YouTube, Instagram, or Twitter

    18 min

About

A Digital Strategy Podcast explores how design, technology, and business intersect to shape the way organizations grow and adapt. Through thoughtful discussions and interviews with leaders in tech, design, brand, and marketing, the show shares practical strategies, frameworks, and stories for navigating today’s digital landscape. Hosted by the team at Tennis, the podcast blends sharp takes on the industry with candid conversations about the systems, tools, and decisions that drive lasting impact.

You Might Also Like