Latest / 5 Minute UX / Writing a Design Proposal to Protect Both Sides
Transcript
- 0:07This lesson is Writing a Design Proposal to Protect Both Sides.
- 0:11Let's get started.
- 0:18The design agreement does three distinct things before any
- 0:20actual work begins. First, it acts as a paper trail that backs
- 0:23up the designer if misunderstandings arise later.
- 0:25Second, the signature itself creates a formal agreement on
- 0:27who handles specific aspects of the project, what is included in
- 0:30the scope, and the estimated price. Third, and most
- 0:32importantly, it defines the terms that protect both the
- 0:34designer and the client in the event that project conditions
- 0:37change. This protection isn't just about legal liability; it's
- 0:39about operational stability. When a client signs, they are
- 0:42explicitly accepting responsibility for providing
- 0:44timely access to their resources, which prevents the
- 0:46designer's timeline from slipping due to missing
- 0:48information. It also establishes financial security, ensuring the
- 0:51designer gets paid for completed work even if the client loses
- 0:53funding and kills the project. Without these defined terms, the
- 0:56relationship relies on goodwill, which tends to evaporate the
- 0:58moment a deadline is missed or a budget gets cut. The primary
- 1:01function of this document is to remove ambiguity from the start.
- 1:04It transforms a handshake into a shared understanding of
- 1:06expectations, roles, and financial commitments. By
- 1:08locking in these definitions, both parties can move forward
- 1:10with the confidence that their interests are secured. This
- 1:13clarity sets the stage for the specific content elements that
- 1:15need to be included next.
- 1:22The agreement must detail the terms of the relationship
- 1:24between the client and the vendor. It also specifies the
- 1:26payment schedule for the client, which dictates when and how
- 1:29funds move. You must include a clear identification of who is
- 1:31handling what aspects of the project. This prevents overlap
- 1:33and clarifies responsibility. The document outlines the
- 1:36specific aspects of the project included within the proposal. It
- 1:38also states the price estimated for the included work. Together,
- 1:41these five mandatory content elements form the core of the
- 1:43agreement. They define the boundary between your UX focus
- 1:45and other potential components. This structure ensures both
- 1:48parties understand the scope. It protects the designer from scope
- 1:50creep. It also protects the client from unexpected costs.
- 1:52The proposal serves as a shared reference point. It reduces
- 1:55ambiguity in the early stages. It sets expectations for
- 1:57deliverables. It establishes the financial framework. It
- 1:59clarifies roles and responsibilities. It creates a
- 2:01baseline for success. It mitigates potential conflicts.
- 2:03It supports project stability. It fosters trust between
- 2:06partners. It enables efficient workflow. It promotes
- 2:08transparency. It encourages accountability. It drives
- 2:10progress. It ensures alignment. It sustains momentum.
- 2:19The moment a client accepts the project, the proposal must make
- 2:21them aware of their obligations to the project’s success. You
- 2:24specifically address the risk that if the client does not
- 2:26provide timely access to their resources, the designer’s
- 2:28timeline will slip. This clause forces the client to commit to
- 2:31the workflow, ensuring that delays are not treated as the
- 2:33designer's fault. Next, you protect against the risk of non-
- 2:35payment if a client loses funding and kills the project.
- 2:38Without a formal agreement, the designer runs the risk of not
- 2:40getting paid for work already completed. The proposal ensures
- 2:42the designer is paid for work already completed even if the
- 2:45project is terminated. This financial security is non-
- 2:47negotiable for your business stability. These protections
- 2:49are not just administrative tasks. They are the specific
- 2:52mechanisms that define the terms of the relationship between the
- 2:54client and the vendor. By defining who handles what, you
- 2:56create a clear boundary. This clarity prevents the most
- 2:59uncomfortable situations in project history, keeping the
- 3:01working relationship professional and predictable.
- 3:09When you sit down to draft the scope of work, you need a
- 3:11specific template to anchor the boundary. Start by stating, "We
- 3:14were approached by [Client Company name] to provide all
- 3:16services required to build [Project Type]." This sentence
- 3:19establishes the overall context and the client’s specific goal.
- 3:21It tells them exactly what the final deliverable is supposed to
- 3:24be, removing any ambiguity about the end result. Next, you must
- 3:27explicitly state your limitation. Write, "[Your
- 3:29Company name] will focus solely on the [user experience design
- 3:31Aspect(s)] of the [Client Company name]’s website." The
- 3:34word "solely" is critical here because it draws a hard line
- 3:36around your expertise. It clearly separates your user
- 3:39experience design work from other potential components like
- 3:41development or content strategy. This clarification prevents the
- 3:44client from assuming you will handle every part of the website
- 3:46build. By using this two-part structure, you apply the scope-
- 3:49of-work template to delineate the specific UX design aspects
- 3:52included in the project. It protects you from scope creep
- 3:54and protects the client from over-promising. Once this
- 3:56boundary is set, you can move to the next step of the drafting
- 3:59sequence.
- 4:05Here is the spoken narration for Section 5. [0:00] The moment
- 4:07the handshake happens, you must begin drafting immediately. This
- 4:09is the critical window to maintain momentum before the
- 4:11initial energy fades. You need to spend the right amount of
- 4:13time composing the agreement, not just the bare minimum.
- 4:15[0:08] Why this urgency? Because the sooner the proposal is
- 4:17approved and signed, the sooner work can begin. There is a
- 4:19direct link between the ink drying and the clock starting.
- 4:21If you wait, the delay compounds into a later launch date.
- 4:23[0:18] More importantly, signing the proposal is the prerequisite
- 4:25for beginning to get paid for the work. Without that
- 4:27signature, you are not a vendor. You are a favor. You are working
- 4:29on a handshake, which is the most unstable foundation in
- 4:31business. [0:30] So, here is the decision you must weigh
- 4:33right now. Do you start drafting today, or do you wait until the
- 4:35scope feels perfectly clear? The risk of waiting is that clarity
- 4:37never arrives. The risk of starting is simply doing the
- 4:39work. [0:42] Your job is to apply the scope-of-work template
- 4:41to delineate the specific user experience design aspects
- 4:43included in the project. This is the moment you protect both
- 4:45parties by defining the terms. [0:52] This is the final step.
- 4:47You have defined the scope, identified the risks, and set
- 4:49the terms. Now, you execute. The lesson has come full circle. You
- 4:51started with the need for protection. You end with the
- 4:53action that provides it. Draft it now.
- 4:52Welcome to The Take. I'm joined by a fellow practitioner and
- 4:54together we're going to dig into Writing a Design Proposal to
- 4:57Protect Both Sides — what it means in practice and what's
- 5:00worth remembering.
- 5:02[HOST] The word "solely" in that scope template is doing more
- 5:05heavy lifting than most people realize. It’s the only word that
- 5:08actually stops the bleed. [LEARNER] It’s a hard line to
- 5:11draw, though. Clients often assume UX includes the copy.
- 5:14[HOST] Exactly. That’s where the ambiguity lives. If you don’t
- 5:18carve out content strategy, they will. [LEARNER] I’ve lost weeks
- 5:21to that. They expect the headlines to be part of the
- 5:24wireframes. [HOST] That’s why the clause about resource
- 5:27obligations has to be explicit. If they own the content, they
- 5:30own the delay. [LEARNER] But writing that clause feels
- 5:33adversarial. It sounds like I’m blaming them before we start.
- 5:36[HOST] It’s not blame, it’s logistics. You’re just defining
- 5:40who holds the bottleneck. [LEARNER] Fair point. I guess I
- 5:43frame it as "dependency" rather than "obligation." [HOST] That’s
- 5:46a better way to say it. It keeps the tone professional without
- 5:49losing the teeth. [LEARNER] Speaking of teeth, the payment
- 5:52schedule for terminated projects is where I usually get pushed
- 5:56back. [HOST] They want the full refund if the project dies. It’s
- 5:59a common tactic. [LEARNER] I had a client say they’d only pay for
- 6:03"completed deliverables." But how do you define complete?
- 6:06[HOST] You define it by the milestones, not the final
- 6:09product. That’s the key. [LEARNER] So if I finish the
- 6:11research phase, that’s paid. Even if the design never
- 6:14happens. [HOST] Yes. The work is done. The value is delivered.
- 6:18You don’t get to re-litigate that later. [LEARNER] It’s tough
- 6:21to enforce, though. They just stop responding. [HOST] That’s
- 6:24where the signed agreement becomes your leverage. You stop
- 6:27working. You invoice. [LEARNER] I hate that part. It feels like
- 6:31a relationship failure. [HOST] It’s a business reality.
- 6:34Goodwill evaporates the moment the budget is cut. [LEARNER]
- 6:37True. I need to stop relying on them being nice. [HOST] Exactly.
- 6:40Rely on the document instead. [LEARNER] What about using AI to
- 6:44draft these proposals now? It’s getting pretty good at the legal
- 6:47boilerplate. [HOST] It’s great for the standard clauses. But it
- 6:50misses the nuance of your specific scope. [LEARNER] So I
- 6:53use it for the structure, but I write the scope myself. [HOST]
- 6:57Yes. The "solely" part. That has to be human. It has to be
- 7:00intentional. [LEARNER] I like that. The machine handles the
- 7:03shield, you handle the sword. [HOST] That’s the right mental
- 7:06model. Keep the protection automated, keep the definition
- 7:09manual. [LEARNER] It makes me feel less lonely in the drafting
- 7:13process, too. [HOST] It should. You’re not just filling out a
- 7:16form. You’re building the foundation. [LEARNER] And the
- 7:19foundation is where most projects collapse. [HOST]
- 7:22Precisely. Get it right now, or pay for it later.