Latest / 5 Minute UX / Defining Scope of Work in a Proposal
Transcript
- 0:08This lesson is Defining Scope of Work in a Proposal. Let's get
- 0:12started.
- 0:18When you sit down to draft a scope of work, the first move is
- 0:21to draw a hard line between what you do and what they do. The
- 0:24document exists to prevent scope creep by explicitly identifying
- 0:27which components of the project the designer is responsible for.
- 0:29It equally names which components the client is
- 0:32responsible for, removing any ambiguity from the start. This
- 0:34division isn't just about listing tasks; it's about
- 0:37defining the boundary of your commitment. You must also
- 0:39specify what aspects of the project are included within the
- 0:42proposal and the estimated price. By stating exactly which
- 0:44deliverables fall under that price, you create a clear,
- 0:47signed paper trail. The result is a document that protects both
- 0:50parties from drifting into unclear territory. Once you’ve
- 0:52mapped this three-part division of labor, the foundation for the
- 0:55rest of the proposal is set.
- 1:02Before you draft a single line of scope, you need to understand
- 1:05the project ecosystem. This isn't just a buzzword; it's the
- 1:08specific context that shapes your proposal. It starts with
- 1:10analyzing the environment you are working within, which means
- 1:13getting a handle on the company culture first. Next, you
- 1:15determine the general type of work involved, such as
- 1:17identifying the specific types of sites being designed. This
- 1:20distinction matters because a marketing site has very
- 1:22different structural needs than a complex e-commerce platform.
- 1:25Finally, you map the people involved, paying close attention
- 1:28to their specific roles and responsibilities. Knowing who
- 1:30makes decisions and who provides feedback prevents you from
- 1:32writing a scope that assumes the wrong stakeholders are
- 1:35available. These three elements form the base for outlining your
- 1:38role. Once you have this clarity, you can write a
- 1:40proposal that reflects the actual reality of the
- 1:42engagement. This groundwork ensures your scope definition is
- 1:44accurate from the start.
- 1:52The proposal itself has hard structural limits that keep it
- 1:54effective. You need to keep the entire document to two to three
- 1:57pages maximum. This constraint forces you to be precise about
- 1:59what you are actually offering. The reason for this brevity is
- 2:02to include only the outputs that the designer is able to deliver
- 2:05to the client. By restricting the content to what you can
- 2:07physically hand over, you prevent the need for further
- 2:10updating of the document. It also stops you from having to
- 2:12revisit project pricing later on. Think of this as a reusable
- 2:15system. While every project has varying flavors, there is a core
- 2:18structure common to all proposals that can be reused
- 2:20from project to project. You adapt this base framework to fit
- 2:23the specific client or work type. This ensures consistency
- 2:25in how you present your scope of work. Once you have this tight,
- 2:28reusable structure in place, the next step is drafting the
- 2:31specific language that defines who does what.
- 2:39Use the template language to anchor your scope immediately.
- 2:41Start with, "We were approached by [Client] to provide all
- 2:44services required to build [Project Type]." This
- 2:46establishes the context without overcommitting to undefined
- 2:48details. Next, specify your focus clearly. State, "[Your
- 2:51Company] will focus solely on the [UX Design Aspects] of the
- 2:54[Client]’s website." This explicit limitation defines
- 2:56exactly what you are delivering and what you are not, which
- 2:58prevents scope creep. Avoid making specific pricing
- 3:01commitments before you have defined the project details. The
- 3:03exception is when you are working on a basic project and
- 3:06have prior similar experience with that client. In those
- 3:08cases, you have enough context to provide reasonable estimates.
- 3:11This approach keeps the proposal tight and protects you from
- 3:14ambiguity. It ensures the document reflects only the
- 3:16outputs you can actually deliver, maintaining a clear
- 3:18paper trail for both parties. By drafting this way, you create
- 3:21a signed agreement that explicitly states who handles
- 3:23what, eliminating the gray areas that lead to disputes.
- 3:31Take the draft you just wrote and read it against one specific
- 3:34standard: does it explicitly state, "we are going to do this
- 3:37and you are going to do that"? If the sentence only describes
- 3:39your work without naming the client’s responsibilities, you
- 3:42have an ambiguous area where the division of labor is not
- 3:44explicitly written. That gap is exactly where disputes start,
- 3:47because the document no longer serves as a signed paper trail
- 3:49to support you when things go sideways. The reason this
- 3:51matters is that scope creep doesn’t usually arrive as a
- 3:54sudden demand; it seeps in through those silent zones where
- 3:56no one wrote down who handles the content, or who manages the
- 3:59hosting. So when you verify your draft, look for any spot where a
- 4:02task is implied but not assigned. If you find one, close
- 4:04it. This check brings you back to the core insight of the
- 4:06entire process: clarity is not a nice-to-have, it is the
- 4:09structural foundation that keeps the project from collapsing
- 4:11under its own weight. You started by dividing the labor
- 4:14into three distinct parts, and you end by confirming that every
- 4:16part has a named owner. That is what makes the proposal hold.
- 4:22Welcome to The Take. I'm joined by a fellow practitioner and
- 4:25together we're going to dig into Defining Scope of Work in a
- 4:28Proposal — what it means in practice and what's worth
- 4:30remembering.
- 4:32[HOST] The lesson emphasized that scope creep seeps in
- 4:35through silent zones where tasks are implied but not assigned. I
- 4:38find that's the hardest part to catch in a draft. [LEARNER]
- 4:41It's, because we often assume the client knows their own
- 4:44obligations. We write about what we'll design, but we forget to
- 4:48explicitly state what they must provide. [HOST] Exactly. If the
- 4:51document doesn't name the client's content delivery, that
- 4:54gap becomes a dispute later. We need to treat their
- 4:56responsibility as a deliverable too. [LEARNER] I try to use a
- 5:00checklist for that now, but it feels clunky. It breaks the flow
- 5:03of the narrative in the proposal. [HOST] It might feel
- 5:06clunky, but clarity beats flow in a legal document. A narrative
- 5:09that sounds nice but leaves ownership ambiguous is a
- 5:12liability, not a style choice. [LEARNER] Fair point. I've been
- 5:15using AI to draft these sections to speed things up, though. It
- 5:18generates smooth text, but it often misses those specific
- 5:21boundary lines. [HOST] That's a common trap. AI predicts the
- 5:24most likely professional phrasing, which tends to be
- 5:27vague and collaborative. It rarely suggests hard boundaries
- 5:30unless you force it to. [LEARNER] So I have to
- 5:33explicitly prompt it to identify who does what. I can't just let
- 5:36it write the scope from a high- level brief. [HOST] Right. You
- 5:39have to feed it the division of labor first. The AI is just a
- 5:42formatting engine, not a scope definer. It can't know your
- 5:45specific constraints. [LEARNER] That makes sense. I was relying
- 5:49on it to be smarter than my own draft, but it's just averaging
- 5:52out the ambiguity. [HOST] And that averaging is dangerous. It
- 5:55blurs the lines between your work and theirs. You need to
- 5:58inject your specific, hard-edged definitions into the prompt.
- 6:01[LEARNER] I guess I need to stop treating it as a writer and
- 6:04start treating it as a typist. [HOST] Precisely. It types what
- 6:08you dictate. If you dictate a clear division of labor, it can
- 6:11format it well. If you dictate a vibe, it'll give you a vague
- 6:14document. [LEARNER] I like that framing. It puts the
- 6:17responsibility back on me, which is where it belongs. [HOST] It
- 6:20does. The AI can help with the two-page limit and structure,
- 6:23but it can't decide who owns the hosting. That's your call to
- 6:26make. [LEARNER] So the next time I draft this, I'll list the
- 6:29exclusions first. Then I'll ask the AI to weave that into the
- 6:33language. [HOST] That's a solid approach. Start with the hard
- 6:36boundaries, then let the tool handle the polish. The structure
- 6:39holds the project together, not the prose.