When a Collaboration Sounds Exciting, Agree on This First

A promising collaboration can make you want to start right away. You see what each person could bring, picture what the two of you could build, and assume the details will sort themselves out along the way. That assumption is where confusion begins. Nobody is careless, but each person fills the gaps with their own idea of what is fair and normal, and two people rarely fill the same gap the same way. The fix takes about an hour at the very beginning and costs nothing.

Imagine two organizations planning a joint event. One believes it is responsible for the venue and the promotion, while the other expects its partner to handle both. They have not decided who approves the event details, whose logo appears on the materials, or when each organization will start promoting. Three weeks out, the flyer goes live with only one logo, the partner learns about a date change from a social media post, and the same guests get contacted twice. Everyone was excited, and everyone was working from a different set of assumptions.

Before the work begins, schedule one conversation of 30 to 45 minutes, by video or in person. Open a blank shared document, such as a Google Doc or a Word file, and type four labels at the top: Who is doing what, Credit, Decisions, and Timeline. Fill in each section together while you talk so both people watch the same words appear and can correct them on the spot. A guide to the formation phase of a business collaboration from Business Cornwall makes the same case, saying roles, responsibilities, and accountabilities need to be identified so everyone is clear about what is expected of them.

Start with who is doing what. List every task the project needs, put one name next to each task, and describe what that person will hand over. "We'll both help promote" can mean a single post for one person and a three week campaign for the other, so be more specific than that. Name who designs the graphics, what sizes and file types they come in, who writes the announcement, who proofreads it, who contacts which guests, and who sets up registration and watches the sign ups. A good test is whether a stranger reading your notes could tell who to ask about each task.

Next, agree on how each person receives credit, because credit has a visible side and a legal side. On the visible side, decide whether both organizations are named in the announcement and in what order, which version of each logo goes on the materials and where it sits, which accounts get tagged in social posts, and whether either of you may show the finished work in a portfolio or case study afterward. On the legal side, the University of California's copyright guidance explains that people who prepare a work together, intending their contributions to merge into one piece, generally own it jointly and equally unless they agree otherwise. Each of them must also account to the others for profits from licensing it. That default may not match what you intend, so say out loud who owns what you create together and write it down. Nolo, a legal publisher, lists credits among the items a joint ownership agreement should settle. If the project involves money, original writing, design, photography, or software, have a lawyer review your notes, since this article is general information and not legal advice.

Then decide who makes the decisions. Sort choices into three groups. Small choices, such as the wording of one social post, can belong to whoever owns that task. Shared choices, such as the event date or the budget, need a yes from both people. Final approval, such as signing off on the finished flyer before it is printed, should belong to one named person so work never stalls while two opinions compete. Bain & Company built a well known framework for this called RAPID, introduced by Paul Rogers and Marcia Blenko in a 2006 Harvard Business Review article titled "Who Has the D?" As Mind Tools and Asana describe it, the framework separates the people who recommend, the people who must agree, the people who give input, the people who carry out the decision, and one person who decides. You do not need the full framework for a small project, but its core idea works at any size: one decider, a short list of people with a true veto, and everyone else giving input. Also agree in advance on what happens when you disagree, for example that both of you pause for a day, each writes down what you want and why, and the person with final approval then decides.

Last, set the timeline. Begin with the date the finished work must be delivered and work backward, putting a date on the first draft, feedback, revisions, final approval, the start of promotion, and delivery. Give each reviewer a set number of days, such as two business days, and leave a few days of cushion before the final date. Check holidays, travel, and time zones while you are at it. Then agree on what happens when a date slips, such as telling the other person within one business day through the channel you both check, whether that is email or text.

It also helps to decide what happens when the project grows beyond the original plan. Someone suggests adding a video, a second speaker, or a printed program, and each idea sounds small. Project managers call this scope creep. PM Study Circle reports that the Project Management Institute's guidance treats change as inevitable and says it should be controlled through a change process, with each request recorded along with who asked, why, the effort involved, and the budget impact. Your version can be simple: pause, write the request down, and answer three questions. Who will do the work, does any date move, and does it cost anything? A 2026 poll from the Institute of Project Management found that 45 percent of respondents named unclear objectives as the most frequent trigger of scope creep, which is why the four conversations above come first.

You do not need a complicated agreement for every small project. A clear email or shared document can capture the essentials. Send a short recap the same day, while the conversation is fresh; the Business Writing Blog recommends same day, and HeroThemes suggests a window of 30 minutes to two hours. Use a subject line that explains itself, such as "Recap: joint event plan, decisions and next steps." State each decision as a decision, then list each task with its owner and its deadline, the three parts the Business Writing Blog says every action item needs. Close with a direct request, such as "Please reply to confirm this matches what we agreed, or send corrections by Friday," and keep that reply with the document so either of you can point to it later.

A collaboration should leave room for good ideas to grow. Clear roles, credit, decisions, and deadlines give those ideas a fair chance to succeed. They also protect the relationship, because a disagreement about a document is far easier to settle than a disagreement about memory. The hour you spend on this conversation is the cheapest part of the whole project.