Technical skill alone does not make a successful web project. Most projects that go over budget, miss deadlines, or end in frustration fail for communication reasons: the requirements were never fully understood, the client expected something different from what was scoped, feedback arrived late or in scattered emails, or nobody explained who was responsible for the site after launch. This topic treats client relations as a professional skill set you can learn and practice, not a personality trait.
The lifecycle runs from first contact through discovery, proposal and scope agreement, regular progress reporting, structured feedback and revision rounds, handoff and CMS training, and finally ongoing support and maintenance communication. Each stage has its own tools and habits: discovery questionnaires and stakeholder interviews, written scope documents and change-order policies, status updates on a predictable schedule, consolidated feedback rounds with a stated limit, training sessions and documentation for the client's content editors, and clear escalation paths when something breaks. When conversations do get difficult — a missed deadline, a scope dispute, an unhappy stakeholder — a calm, documented, solution-focused approach protects both the relationship and your professional reputation.
As you watch the videos below, look for three things: the specific questions practitioners ask during discovery, the moments where expectations are put in writing rather than assumed, and the listening behaviors that make a client feel genuinely heard. Try to connect each practice to a stage of the project lifecycle, and think about how you would document it — in a discovery form, a scope statement, a status email, or a maintenance agreement.
A practicing web designer walks through an end-to-end client website process, from intake and discovery through design, build, delivery, and the project management system used to keep it organized (the description mentions a free Trello template). Expect an overview of how the phases connect and where client touchpoints — approvals, updates, and revision rounds — fall within them. It is framed as hard-won practical experience rather than theory.
It gives students a realistic, start-to-finish view of a client project, which is the backbone of this topic and places requirements gathering, expectation setting, progress updates, and handoff in their proper sequence.
Laura Brandenburg of Bridging the Gap presents five requirements elicitation techniques used by business analysts to discover what stakeholders actually need. The video is likely to cover approaches such as interviews, document analysis, observation, workshops, and prototyping, along with when each technique is the better choice.
It directly supports the Requirements Gathering and Discovery subtopic with structured, profession-standard methods from a channel dedicated to business analysis training, giving students vocabulary and techniques beyond simply asking a client what they want.
Harvard Business Review explains why common listening signals like nodding and saying "mm-hmm" can fall short, and presents concrete habits that make listening genuinely effective. The guide focuses on attention, clarifying and reflecting back what was said, and responding in ways that confirm understanding.
Active listening is the underlying skill for discovery interviews, feedback sessions, and difficult conversations, and HBR is a credible, concise source for professional communication practice.
These videos focus on MO5, the client communication outcome. The web design process video maps professional communication onto the full project lifecycle — discovery, updates, approvals, revisions, and delivery — while the business analysis video supplies concrete requirements elicitation techniques for the discovery phase, and the Harvard Business Review guide builds the active listening skill that underpins expectation setting, feedback management, and conflict resolution. Together they also reinforce MO3 and MO4 indirectly, since handoff, CMS training, and scheduled maintenance communication are the points where a webmaster's operational responsibilities are explained and agreed upon with stakeholders.
These videos were chosen from YouTube on October 3, 2026. Each has captions; the player turns them on. Videos on YouTube can be changed or removed — if one no longer plays, tell your instructor. If a player does not appear, use its Watch on YouTube link.