Advertise on podcast: A Digital Strategy Podcast

 Key  topics Definition of technical debt in web development How small decisions compound over time Real-world examples of web debt Strategies for auditing and addressing web debt   Chapters 00:00 Technical Debt in Web Development 00:19 Understanding Incremental Web Debt 03:19 The Impact of Technical Debt 08:21 Real-World Examples of Technical Debt 14:49 Addressing Technical Debt 17:42 Final Thoughts and Takeaways 20:09 outro.mp4   Resources Tennis - Web Design & Development Agency - https://tennis.co Symon Oliver on LinkedIn - https://linkedin.com/in/symonoliver Marcello Gortana on LinkedIn - https://linkedin.com/in/marcellogortana Links You can learn more about Tennis at our website. Be sure to follow us at LinkedIn, YouTube, Instagram, or Twitter

Notes Why does a website project that everyone agrees is needed keep dying in the finance meeting? Usually it's not the budget — it's the pitch. Symon and Marcello break down how to reframe a web investment as a business initiative, not a creative one, and walk through exactly how to build a case that finance can actually approve. Topics covered: current cost audit (hosting, content ops, lost leads), opportunity cost of inaction, competitive and technical risk, how to connect a website to revenue (and when you can't), OPEX vs. CAPEX considerations, phase-based budget structuring, and how to build a measurement plan before you ask for money.   Chapter List (YouTube + Podcast) 0:00 — Intro: Why website projects die in the finance meeting 1:41 — The business case is already there — it's a framing problem 2:20 — Why most website business cases fail 4:13 — Looking at risk: compliance, accessibility, and fines 5:13 — Current costs: what your website is actually costing the business 7:00 — Opportunity cost: the website as a go-to-market tool 7:46 — Risk of inaction: technical debt and competitive positioning 9:00 — The investment ask: phasing, fiscal year alignment, flexibility 9:25 — Defining project objectives from day one 10:30 — How to connect a website to revenue (and when you can't) 12:13 — Content bottlenecks as the baseline business case 13:34 — Page speed: the metric that impacts both UX and search 14:34 — Indirect value: brand credibility, talent, partner perception 16:22 — How Tennis grew its own inbound with SEO and AEO 19:10 — When the full budget won't get approved: the phase-based ask 21:00 — What to do first if you need to pitch in the next 60 days 22:28 — Build the measurement plan before you ask for the budget 23:00 — OPEX vs. CAPEX: how finance wants to spend matters 24:49 — Final takeaway: stop pitching a website Links You can learn more about Tennis at our website. Be sure to follow us at LinkedIn, YouTube, Instagram, or Twitter

Most projects don't fail because the team couldn't build. They fail because the team tried to build everything at once. In this episode, Symon and Marcello break down why project scope creep and feature bloat are the real killers of product development timelines—and what to do about it. They walk through how to run a fast complexity audit before committing to any digital project, why a discovery phase and product requirements document (PRD) belong on every project regardless of size, and the difference between a proof of concept and an MVP (they're not the same thing, and confusing them is expensive). Whether you're scoping a website redesign, building your first web application, or evaluating a vendor for a complex B2B product—this one will save you from a very avoidable mistake. In this episode Why ambitious timelines and bloated scope are a reliable path to failure  The complexity audit: how to pressure-test a project before you commit  Proof of concept vs MVP  what each one is actually for  What the Think Phase and a proper PRD do that no kickoff call can  Four rules for phased delivery that actually ships Chapters 0:00 — Intro 0:36 — You can't boil the ocean 3:25 — The complexity trap 5:19 — Feature bloat in the real world 7:57 — Proof of concept vs MVP 10:37 — The discovery phase and the PRD 14:43 — Four rules for phased project delivery 19:31 — Wrap About Tennis Tennis is a B2B Web Design and Product Development Agency based in Toronto. We help mid-market teams turn complex digital problems into staged, ROI-driven builds—where each phase moves something real and earns the right to expand. tennis.digital → Follow us on LinkedIn Links You can learn more about Tennis at our website. Be sure to follow us at LinkedIn, YouTube, Instagram, or Twitter

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

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

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

Takeaways Total cost of ownership includes hidden costs like hosting and labor.Organizations often underestimate the costs associated with website redesigns.Hosting costs can vary significantly and are often overlooked.Labor costs related to managing technology can add up quickly.RFPs rarely include detailed descriptions of hosting and management costs.Cultural attitudes towards websites affect how costs are perceived.Incremental delivery can help manage costs more effectively.Clients often lack awareness of their total spending on technology.Effective communication is key to understanding project costs.Managed hosting can provide peace of mind despite higher costs.  Chapters 00:00 Introduction to Total Cost of Ownership04:28 Understanding Hidden Costs in Website Redesigns10:16 The Role of Hosting and Labor Costs16:14 Challenges in RFPs and Cost Management22:08 Cultural Perspectives on Website Value25:55 Hard Truths About Total Cost of Ownership Links You can learn more about Tennis at our website. Be sure to follow us at LinkedIn, YouTube, Instagram, or Twitter

Takeaways Organizations often lack a structured way to evaluate vendors.A scorecard can help monitor vendor performance over time.Identifying triggers for audits can prevent larger issues.Communication is a critical factor in vendor relationships.Documentation is essential for transparency and accountability.Systemic issues can often be masked by one-off problems.Regular evaluations can help maintain healthy vendor relationships.Quality drift should be monitored to ensure standards are upheld.Establishing clear criteria for success is vital.Future planning can alleviate pressure during vendor evaluations.  Chapters 00:00 Evaluating Vendor Relationships01:56 Understanding Audits and Scorecards03:04 Ongoing Evaluation of Vendor Success05:51 Identifying Triggers for Vendor Audits09:03 Distinguishing Between One-off Issues and Systemic Problems10:41 Establishing Evaluation Criteria13:40 The Importance of Communication and Reporting14:57 Key Categories for Vendor Evaluation Links You can learn more about Tennis at our website. Be sure to follow us at LinkedIn, YouTube, Instagram, or Twitter

Takeaways The importance of a flexible process in project management.Documentation is critical for continuity and clarity.Scope should be viewed as a hypothesis, not a contract.Effective communication is key to navigating project risks.Governance helps promote decision clarity and accountability.Understanding client expectations is crucial for project success.Regularly reviewing and updating processes is essential for improvement.  Chapters 00:00 Introduction and Weekly Recap11:14 The Importance of Documentation in Processes13:33 Process Philosophy and Governance16:27 Navigating Project Risks and Flexibility19:25 The Role of Communication in Project Management22:14 Understanding Scope and Change Management25:14 Final Thoughts on Process and Client Relationships Links You can learn more about Tennis at our website. Be sure to follow us at LinkedIn, YouTube, Instagram, or Twitter

Takeaways MVPs aren't about shipping fast, they're about learning fast.The term MVP has been misunderstood and often co-opted.Validation should come from real user engagement, not speculation.A good MVP strategy involves identifying risky assumptions and defining success metrics.An MVP can be a scrappy version of a product, but it must still show commitment to the idea.  Chapters 00:00 Introduction to MVPs01:28 Understanding the Misconceptions of MVPs06:37 Real-World Examples of MVPs09:38 MVPs in Product Thinking11:11 When to Use an MVP14:19 The Importance of Speed in MVP Development15:30 Crafting an Effective MVP Strategy24:01 Hard Truths About MVPs29:36 Conclusion and Key Takeaways Links You can learn more about Tennis at our website. Be sure to follow us at LinkedIn, YouTube, Instagram, or Twitter

Takeaways The trend of single user apps will continue to grow.Compliance will increasingly involve product and design teams.Dynamic web pages may become a reality this year.Websites should be treated as living systems, not static products.Customer journeys are becoming more complex and non-linear.Sales tech stack integration with websites is essential for success.AI will play a significant role in web design and functionality.Accessibility compliance will become a standard expectation.The importance of design systems will increase as technology evolves.Understanding customer data and behavior is crucial for effective marketing.  Chapters 00:00 Welcome Back and Personal Updates01:53 Predictions for 2026: Trends in Web and Product Design05:38 The Rise of Compliance in Design09:38 Dynamic Web Pages and AI Integration13:18 Websites as Living Systems19:13 Customer Journeys: A Non-Linear Approach24:59 Sales Tech Stack Integration with Websites Links You can learn more about Tennis at our website. Be sure to follow us at LinkedIn, YouTube, Instagram, or Twitter

Takeaways Design is interpretive and has a rich history.Aesthetics is often mistaken for the entirety of design.Design involves planning and execution, not just visuals.The complexity of a project influences the design approach.Research and problem identification are crucial in design.De-risking the design process helps in decision-making.Accuracy in design outcomes is essential for success.Agility allows for effective pivots in design projects.Documentation aids in maintaining clarity during pivots.Design should be evaluated beyond just aesthetics.Chapters 00:00 Introduction to Design Perspectives02:49 Defining Design: A Multifaceted Approach06:12 The Four Pillars of Design08:59 Aesthetics vs. Functionality in Design11:48 De-risking the Design Process14:41 The Importance of Accuracy in Design18:00 Agility and Flexibility in Design20:56 Conclusion: The Depth of Design Beyond Aesthetics Links You can learn more about Tennis at our website. Be sure to follow us at LinkedIn, YouTube, Instagram, or Twitter

Takeaways Websites can now serve as growth engines.Defining clear goals is crucial for website success.Sales and marketing teams must collaborate effectively.Data analytics is essential for informed decision-making.A strong content strategy is foundational for growth.Eliminating unnecessary tools can streamline processes.Long-term planning is vital for website design.Understanding lead movement through the organization is key.Integrating technology into marketing strategies enhances effectiveness.The website should be part of a larger growth ecosystem.  Chapters 00:00 Website as a Growth Engine07:32 Defining Website Goals and Success Metrics08:00 Understanding SaaS and B2B Marketing Dynamics10:18 The Importance of Metrics in Marketing12:38 Integrating Website with Growth Ecosystem16:12 Sales and Marketing Collaboration18:21 Essential Technologies for Growth27:50 Redesigning Websites for Sales and Marketing34:16 The Hard Truths of Website Strategy Links You can learn more about Tennis at our website. Be sure to follow us at LinkedIn, YouTube, Instagram, or Twitter

AEC is facing a perfect storm + digital disruption. Johanna Hoffman (Oomph Group) explains what’s happening, why it won’t revert, and how firms can reposition, align BD/marketing, and turn their website into a growth engine. Find Johanna Hoffman: https://www.linkedin.com/in/johanna-hoffmann-b35b251/  Find Oomph Group: www.oomphgroup.com  Find Marcello Gortana: https://www.linkedin.com/in/marcellogortana/  Find Symon Oliver: https://www.linkedin.com/in/symonoliver/  Find Tennis: www.designtennis.com    Links You can learn more about Tennis at our website. Be sure to follow us at LinkedIn, YouTube, Instagram, or Twitter

Takeaways Associations have unique digital needs due to their member-driven nature.Building in public can lead to valuable feedback.Monolithic systems are tightly coupled and may limit flexibility.Modular systems allow for more customization and scalability.Portals are essential for member engagement and retention.Requirements gathering is crucial for effective technology solutions.Mapping out existing systems can reveal inefficiencies.Testing software before commitment is vital for long-term success.Associations often struggle with outdated technology solutions.The right tech stack depends on the specific needs of the organization.Chapters 00:00 Introduction to Building in Public05:23 Understanding Associations and Their Digital Needs07:10 Exploring the Tech Landscape for Associations11:20 Monolithic vs. Modular Systems17:50 The Importance of Portals in Member Engagement20:01 Requirements Gathering and Future Planning Links You can learn more about Tennis at our website. Be sure to follow us at LinkedIn, YouTube, Instagram, or Twitter