AD
Episode
450
Interview
Web News

How to Be a Good Client to Your Web Developer

Recorded:
January 21, 2026
Released:
February 10, 2026
Episode Number:
450
Powered by

Most website project delays aren’t caused by bad code - they’re caused by communication and decision-making issues.

In this episode, Matt and Mike flip the script and talk about how clients can be better partners to their web developers. From vague feedback and false urgency to scope creep and decision-by-committee, we break down the most common developer pet peeves, why they matter, and what small communication changes can dramatically reduce costs, speed up timelines, and improve final results.

This isn’t about blaming clients - it’s about understanding how modern web projects actually work.

Listen

Also available on...
Spotify
Apple
YT Music
PodBean
RSS
...and many more, check your podcast app!

Who’s in This Episode?

Matt Lawrence
Host
Web developer, podcast host, podcast producer, always gaming
MPorterBridges
Mike Karan
Host
Podcast host, X aficionado, and Lead Engineer @Cyfrin
htmleverything

Show Notes

Why This Episode Exists

  • I acknowledge that communication is difficult and that we don’t live in a utopia - so the concepts and topics covered in this episode will likely never be followed to the letter in practice (and they’re imperfect in their own right)
  • Most website project delays aren’t technical - they’re communication and decision issues
  • Small changes in how clients communicate can help:
    • Reduce cost
    • Speed up timelines
    • Improve final quality

The Most Common Developer Pet Peeves (And Why They Matter)

  1. “Can We Just Do Something Like This?” (No Context)
    • The Issue
      • Just a verbal ask, sometimes accompanied by a screenshot - with no explanation of what they specifically like, or why they like it
    • The Solution
      • Devs need details, details help devs boil down what the client want into a tangible solution
  2. Changing Scope Without Acknowledging It
    • The Issue
      • Treating all changes as “small asks” (ie “It’s just a small change” “Can we quickly add this?”)
    • The Solution
      • Ask if something is a “small ask” or if it’s achievable in scope - try to adhere to the original plan, or make space (ie extend deadlines) if more work is needed
  3. Late or Incomplete Content
    • The Issue
      • Copy, content, and/or requirements are late (or never received)
    • The Solution
      • A clear pipeline of content-to-dev where deadlines are set (ie all home page placeholder text will be finalized by Dec 1), and a clear place where assets are placed (ie all images are in Google Drive, all text in PDF email attachments)
  4. Decision-by-Committee
    • The Issue
      • Too many stakeholders (conflicting feedback and decision-making)
    • The Solution
      • Clear decision-making hierarchy with deadlines set for decisions and strict cut-off dates (ie By Dec 12 we will have all the page designs done, with a hard cut-off for minor revisions set to Dec 15)
  5. Vague Feedback
    • The Issue
      • A lot of clients will say things like “It just doesn’t feel right” or “Can you make it pop?”
    • The Solution
      • Have a meeting with colleagues or even your developer to distill those feelings about the design into real actionable changes (ie It needs to pop more, let’s remove the dark mode and add some bright colours to see what it looks like)
  6. False Urgency
    • The Issue
      • When everything is urgent, nothing is. Clients will often say that everything needs to be done “quickly” or is a “priority” in order to get things done quickly. This breaks down the severity hierarchy - delaying everything (even things that are actually urgent)
    • The Solution
      • Clearly communicate the severity of changes and issues with expectations (ie Is a typo something we can change later? Or do I need to find a laptop quickly on a weekend to log in and fix?)

How to support the show

Patreon

Prices subject to change and are listed in USD

  • Support the show from as little as ~$1/month
  • Get a shoutout at the end of the episode (while supplies last) for just ~$3/month
  • Help support the HTML All The Things Podcast: Click Here

Scrimba Discount - Coding Courses!

Learn to code using Scrimba with their interactive follow-along code editor.

Join their exclusive discord communities and network to find your first job!

Use our affiliate link for a 20% discount!!

  • Click the link to take you to the Scrimba site
  • A pop-up should appear on your screen with the discount amount and instructions on how to claim it
  • Discount is for new accounts only

We receive a monetary kickback if you use our affiliate link and make a purchase.

HTML All The Things logo

    Podcast

    Blog

    Contact

    Copyright©2024
    Legal