Latest / 5 Minute UX / Defining Deliverables and Client Assets
Transcript
- 0:08This lesson is Defining Deliverables and Client Assets.
- 0:11Let's get started.
- 0:19The project proposal must explicitly list the assets and
- 0:21resources expected from the client. This section defines
- 0:24what you need from them to start. First, identify the
- 0:26personnel. You need timely access to all required employees
- 0:29from the client company. Without these specific people, the work
- 0:32stalls. Next, secure the existing assets. This means
- 0:34timely access to all required project assets in their current
- 0:37state. It specifically includes any source files if available.
- 0:40Finally, define the content requirements. You need content
- 0:43as required for any aspect of the project. This includes, but
- 0:45is not limited to, copy, imagery, and audio. By naming
- 0:48these three categories, you set clear expectations. This
- 0:51prevents later disputes over missing materials. With these
- 0:53inputs locked in, the work can begin.
- 1:01Deliverables are the work product created by the designer
- 1:03and turned over to the client. When you draft this section, you
- 1:06must provide descriptions of any work product that might be
- 1:08included, even if it does not ultimately get produced. This
- 1:11comprehensive listing prevents ambiguity about what the project
- 1:13actually entails. You should use the word "may" to indicate
- 1:16potential deliverables, which acknowledges the possibility of
- 1:18that work without committing to it. This conditional language
- 1:21prevents the "can of worms" where a client claims, "I read
- 1:23about that deliverable type in the proposal, but I don't see it
- 1:26here." By framing expectations this way, you protect the scope
- 1:29while maintaining transparency. The next step is structuring
- 1:31these items with specific introductory statements and
- 1:33detailed descriptions.
- 1:40When you draft the deliverables section, start with a clear
- 1:42introductory statement to set the context for the client. You
- 1:45might say, "Your company name provides a variety of
- 1:47deliverables throughout the course of a project." Then, you
- 1:50personalize it for the specific engagement. You add, "For Client
- 1:52Company name, we have identified the following deliverables."
- 1:55This framing signals that the list is tailored to their needs,
- 1:58not a generic template. It establishes a professional tone
- 2:00right away. Next, you list the specific items in order,
- 2:03starting with the foundational document. The first item is the
- 2:05Creative Brief. You describe its purpose clearly and concisely
- 2:08for the reader. You explain, "The Creative Brief is the first
- 2:11step of the project." This document helps you create a
- 2:13quick and effective, high-level overview of the project. By
- 2:16defining it this way, the client understands its role
- 2:18immediately. They know it is an overview, not a detailed
- 2:20specification. This structure keeps the proposal readable and
- 2:23authoritative. Each deliverable gets its own line with a brief
- 2:26description. You avoid clutter by keeping the descriptions
- 2:28focused on function. The client sees exactly what they are
- 2:31getting and why it matters. This clarity prevents confusion later
- 2:33in the process. It sets the stage for the more complex items
- 2:36that follow.
- 2:43When you start defining deliverables, clarify who is
- 2:45doing what. Identify the roles interacting in the project, such
- 2:48as a job seeker versus a client, or a content producer versus an
- 2:50editor. This prevents confusion about whose responsibility
- 2:53specific tasks belong to. Next, distinguish between your primary
- 2:56deliverables. These are items widely referenced throughout the
- 2:59work, like functional specifications, wireframes, and
- 3:01site maps. You must briefly explain how these differ so
- 3:04stakeholders understand exactly what they are reviewing.
- 3:06Consider this decision: a stakeholder says, "We need a
- 3:08mobile app." Is that a requirement or a preference? It
- 3:11is likely an idea disguised as a need. Your job is to dig deeper
- 3:14and clarify it into a solid statement. That statement
- 3:16becomes the yardstick for the project’s success. If you do not
- 3:19separate needs from ideas early, you build the wrong solution.
- 3:22By pinning down these definitions, you create a shared
- 3:24language. This clarity turns vague requests into measurable
- 3:27outcomes.
- 3:33The direction for your deliverables usually starts with
- 3:35an input artifact. You might receive a formal business
- 3:38requirements document directly from the client. In an Agile
- 3:41release train or product team, you'll work from epics and user
- 3:44stories. Sometimes, the foundation is simply a creative
- 3:46brief or project brief. You may also rely on meeting notes that
- 3:49capture key decisions. A well- articulated site map or task
- 3:52flow often provides the structural backbone. Even notes
- 3:55on a napkin can offer crucial direction. These artifacts
- 3:57define what you are building. They turn abstract goals into
- 4:00concrete targets. When you identify the specific input
- 4:03artifact, you anchor your deliverables to reality. This
- 4:05prevents scope creep and misalignment. You know exactly
- 4:08what the client expects. You know exactly what you will
- 4:10produce. This clarity is the final piece of defining your
- 4:13project.
- 4:17Welcome to The Take. I'm joined by a fellow practitioner and
- 4:19together we're going to dig into Defining Deliverables and Client
- 4:23Assets — what it means in practice and what's worth
- 4:25remembering.
- 4:27[HOST] The "can of worms" warning about conditional
- 4:29language hit home. I used to think listing every potential
- 4:32asset was thorough. [LEARNER] It’s a trap. If you list it,
- 4:36they expect it. "May" is the only way to keep the door open
- 4:39without handing over the keys. [HOST] Exactly. But I worry
- 4:42clients skim. They see the word "may" and assume it’s just a
- 4:45formality. [LEARNER] That’s where the client assets section
- 4:48becomes your shield. If you explicitly demand their source
- 4:51files and personnel access, the scope locks in. [HOST] Right.
- 4:54You can’t blame them for missing assets if you didn’t define the
- 4:58requirement upfront. It shifts the burden back to them.
- 5:01[LEARNER] True. But what about the input artifacts? I’ve seen
- 5:04teams start building from a napkin sketch. [HOST] That’s
- 5:07risky. A napkin sketch is a hypothesis, not a requirement.
- 5:10You need a solid anchor to prevent scope creep. [LEARNER] I
- 5:13agree. But sometimes the client doesn’t have a formal business
- 5:16requirements document. They’re agile, but messy. [HOST] Then
- 5:20you have to distill their epics into a clear creative brief.
- 5:23That brief becomes the single source of truth for the
- 5:26deliverables. [LEARNER] Makes sense. But where does AI fit in
- 5:29here? I’ve seen tools generate these briefs in seconds. [HOST]
- 5:32AI is great for drafting the structure, but terrible for the
- 5:35nuance. It misses the political context of *who* needs to
- 5:38approve what. [LEARNER] Yeah. It can write "The Creative Brief is
- 5:42the first step," but it can’t tell you that the CFO is the
- 5:45real bottleneck. [HOST] And that’s the difference between a
- 5:48template and a strategy. The human insight defines the actual
- 5:51work product. [LEARNER] So the AI handles the syntax, but you
- 5:54handle the semantics. [HOST] Precisely. The proposal protects
- 5:58the scope, but the relationship protects the project. You need
- 6:01both to survive the first sprint.