The Small Practice — Is that a revision or a new assignment?
Original fictional demonstration written for Product Desk Studio. The host, clients, projects, and numbers in the examples are invented. The times below are script cues for a planned recording.

[00:00] Host: A consultant I’ll call Leah sent a customer onboarding email to a client for review. The brief was simple. Write to people who had already signed up, point them to the setup guide, and help them get their first task done. Then a reviewer asked if she could rewrite it for people who had attended a webinar and hadn’t signed up yet. The reviewer called it a tweak. I understand why. Same product, same company, same blank document. But before she agreed to anything, Leah asked who the email would go to and what those readers should do next. Those two questions changed the conversation.

[01:15] Host: The new readers needed a reason to try the product. Existing customers needed a reason to open the setup guide. If you change what the reader knows and what you want them to do, the whole argument changes. You could keep the same file name and still be doing a different job. On the other hand, suppose a product manager says customers call the setup guide a getting-started checklist. That’s an edit. It makes the original job clearer. And if the link leads to the wrong page, fix it. You don’t need a scope conversation to correct something you got wrong.

[02:30] Host: Here’s what I write down before I take on a project. Who’s it for? What should they do after they see it? What am I handing over? For Leah, the answers were existing customers, open the setup guide, and one onboarding email. Put those answers somewhere the client can find them. One sentence in the kickoff email is enough for a small job. A scope document no one can find when a comment comes in doesn’t help much. And the sentence needs to be specific. “Write something about onboarding” doesn’t give you much to work with when everyone remembers the meeting differently.

[03:45] Host: There’s a gray area. A client might say they want to make an onboarding email friendlier. Then you ask what they mean and they say new customers have stopped finishing setup because they can’t find the first step. That’s useful feedback. You might need to move the link, cut a paragraph, or change the order. You’re still writing to the same person for the same reason. I’d make the change. But if they want to turn one email into a three-email sequence, the audience and goal could stay the same and the handover still changes. Each of those three questions can uncover new work on its own.

[05:00] Host: Sometimes the brief was fuzzy because you wrote it badly. Say you said “for new users,” and the client thought that meant people who hadn’t signed up yet. You meant people who were already in the product. I’d start by owning that ambiguity. Ask which audience matters most now and check whether the work can still fit the original time and price. You might absorb a change you helped create. If it genuinely adds work, say what you can fit and what needs a separate estimate. The three questions help you diagnose a change. They don’t turn every misunderstanding into an invoice.

[06:15] Host: One phrase I like is, “I can finish the onboarding email we agreed on, or I can estimate the webinar follow-up if that’s more urgent.” Sometimes the client says, “Actually, please finish the original. The webinar idea can wait.” Sometimes they say, “Let’s switch.” If they switch, write down what happens to the original draft, the new price if there is one, and the new due date. Wait for their written agreement before you start the new work. That is usually a short email. The client can make the choice without sitting through a meeting or trying to read your mind.

[07:30] Host: The other source of scope trouble is five people giving feedback on one draft. They may all have a good reason to care. I still ask for one person to send the final set of notes. Imagine sales wants the opening to mention the webinar and support wants it to get straight to setup. You can explain what each would do. You probably shouldn’t choose a business priority for them. Ask the designated reviewer to settle it, then send the consolidated comments. If the decision slips, write back with the delivery date you can actually make. A round of edits is about one set of decisions, not one email per person.

[08:45] Host: There’s a low-drama way to practice this. Open a recent job that got harder late. Find the first comment that added real work. Then look at the kickoff email. Which of the three answers would have helped? If it was the audience, add a plain description of who already knows what. If it was the handover, name the deliverable and count it. If it was the action, use a verb a reader can actually do. You only need to change one line in the next proposal. The goal is to catch the change while everybody can still decide what to do about it.