A project for two: clarify roles and expectations before you begin

Why does a project between two people call for explicit agreements?

A simple phrase can hide two different projects. “Make an album together” might mean choosing a few photos for one person and designing a carefully crafted printed object for the other. Neither of you is necessarily wrong. But if the difference stays out of sight, each of you may interpret the other’s choices as a lack of effort or a desire to control everything.

Atlassian’s project management resources distinguish among roles, tasks, and decision-making authority. As a pair, you don’t need to recreate a business organization. You can keep one practical idea in mind: being responsible for a task, giving input, and making a decision aren’t quite the same thing. Your agreement should spell out what you’re actually entrusting to each other.

You can start on your own by clarifying your intention, then invite the other person to do the same. This preparation isn’t a shared decision. It helps you come to the conversation with more precise words and open questions.

How do you organize a project as a pair before getting started?

1. Say what each of you wants from the experience

Talk about the outcome, but also about the experience you want. One of you wants to learn page layout; the other wants to quickly finish a family keepsake. These expectations can coexist if you plan room to experiment and a limited final version. They can also reveal that the same project won’t easily meet both of your needs.

Ask what would make the experience disappointing. Spending every weekend on it, having to follow up constantly, or seeing an image published without approval are very different answers. Hearing them early makes it possible to discuss concrete boundaries. The guide to telling your own desires apart from outside expectations can help you name what matters to you without imposing it.

2. Define a first version you both agree on

Choose an outcome small enough to describe in a few sentences. Specify the audience, format, and what isn’t included. For an album, the audience might be just the two of you; for a workshop, a small group you already know. Don’t imply that public sharing is a given if you haven’t discussed it.

Also write down what will show that this version is finished. “When we’re happy with it” can be too vague. “When the selected pages have been reviewed and the people photographed have given the necessary permissions” is more concrete. The guide to defining success offers guidance without turning your creation into a performance contract.

3. Divide visible and invisible tasks

Choosing images is visible. Following up, finding files, preparing for the meeting, or checking responses is less visible. Bring these tasks into the open before concluding that the workload is fair. Fairness doesn’t always mean the same number of items: a small task can require more attention than another.

For each part, note who will take it on, what she needs, and when the other person can receive a version. Avoid automatically making yourself the coordinator because you came up with the idea. If you prefer that role, say so; if you don’t, the discussion should make that possible. You can break the project into milestones before dividing things up.

4. Distinguish feedback, approval, and autonomy

Decide which matters each person can handle on her own. Choosing a file name is different from publishing the album or committing to an expense. Clear autonomy avoids constant approval requests, but it shouldn’t become an assumed blanket permission.

You could agree that each person can edit her own text freely, that structural changes will be discussed, and that any distribution requires two explicit approvals. These rules are examples; adapt them to the content and the people involved. If rights, money, or professional work are involved, seek the specialized information you need instead of improvising a legal agreement.

How can you talk about availability without comparing yourselves?

Describe what you can offer during the current period, not what you wish you could give in an ideal week. “A time slot on Saturday and a quick review” is clearer than “I’ll do my best.” The other person may have different availability without being less committed to the project.

Plan how you’ll communicate. Some decisions can be handled in a message; others call for reviewing the document together. An ongoing conversation across several apps can multiply versions and expectations. Choose one place for the master file and a simple way to signal when a response is needed.

Don’t promise to be available all the time. You can agree that a routine message can wait until your next planned check-in. If a deadline calls for a faster response, say so explicitly and make sure it’s realistic. To build estimates, the journal of the time actually required helps you draw on experience instead of comparing people.

What should you do when a disagreement comes up?

Start by returning to the subject of the disagreement. Are you talking about the audience, the expected quality, the time available, or personal taste? A discussion about a color can hide a difference in priorities: finishing this week or continuing to explore. Naming the real issue helps you avoid a long debate over a detail that won’t resolve anything.

Each of you can explain what you want to preserve, then suggest an option. You can test two versions, ask for focused feedback, or narrow the scope. The guide to asking for feedback on a creative work can help if you choose to get an outside perspective, but that person doesn’t have to become a referee unless they agree to it.

If you can’t reach an agreement, taking a break or keeping separate versions may be better than forcing a decision. A shared project shouldn’t require one of you to routinely give up your boundaries. In a relationship where expressing disagreement leads to threats, humiliation, or fear, an organizational worksheet isn’t enough to make the exchange safe.

Plan for the unexpected and the end

Talk about what happens if one of you no longer has the time or the desire to continue. Can they step away from the next stage? What happens to the work already done? Who can keep it, change it, or show it? These questions are especially important for personal writing, photos, or stories involving other people.

Taking a break doesn’t automatically give the other person permission to publish. Having already contributed doesn’t mean that every future use is accepted either. Keep a record of specific agreements and check back with the person if the use changes. To pick things back up, a creative project journal can preserve the state of the work without replacing shared decisions.

Finally, plan a brief check-in after the first stage. What was clear? What task was overlooked? What did you appreciate about working together? The nonjudgmental review lets you talk about how the process is working without turning the meeting into an evaluation of your friendship.

A useful first meeting

Come with an idea of the outcome, a realistic sense of your availability, and an important boundary. Compare these three things before getting into the technical details. If you discover a difference, treat it as a starting point. It’s better to adjust now than to count on enthusiasm to resolve an essential difference.

End the meeting with one action item for each of you and a follow-up date you choose together. You can keep a personal note in your decision journalbut the shared recap should be clear and accepted by the other person. Sending a recap doesn’t mean they’ve agreed to a new decision.

For a complementary perspective, watch this video from Adriana Girdler.

Sources

• Atlassian. Project roles and responsibilities for high-performing teams.

The suggested exercises are editorial adaptations, not individually validated protocols. The example situations are fictional.