A new project comes up in a meeting, and someone says, “Let’s divide the work according to what each person is good at.” It sounds sensible until two people want to develop ideas, no one volunteers to check the details, and the most experienced colleague is expected to coordinate everything again. Choosing a role takes more than knowing which tasks you enjoy. You need to identify where you can deliver a concrete result and what the project needs right now.
Start with the project’s needs, not a label for yourself
If you start with “I’m a creative person,” you may overlook the fact that the project needs someone to sort through unclear requirements. It is more useful to first identify specific activities and the outcomes expected from them, then consider who is suited to each one.
For a new initiative, discuss three questions as a team: What needs to be completed first? Which decisions are still uncertain? Where would a mistake or delay cause the biggest problem? This can bring overlooked tasks to light, including work that is easy to miss in the initial excitement.
Separate ability, preference, and capacity
To make a better choice, distinguish among three factors:
- Ability: What can you do, and what results have you achieved? For example, you may be able to prepare a clear comparison of three suppliers.
- Preference: What kind of work suits you? You may enjoy uninterrupted time for analysis even though you can also lead a meeting.
- Capacity: How much time, attention, and support do you have right now? An excellent organiser may not be the right coordinator if they are already managing two other projects.
These factors sometimes align, but not always. You may be very good at checking data carefully and still find the work tiring after a few hours. Or you may be drawn to creative work but need guidance to do it. Neither is a reason to avoid that kind of task forever. The key is to distinguish your current readiness from your interest in learning.
Match your skills to specific parts of the work
A simple map of work contributions can help a team divide tasks. It is not a way to sort people into fixed types. One person can take on different roles in different projects, and each category involves more than one skill.
| What the project needs | When this role is useful | How to assess your readiness |
|---|---|---|
| Ideas and options | When it is not yet clear which solution to choose | Can you suggest several options and explain their limitations? |
| Analysis and review | When data, details, and risks matter | Can you explain how you checked your conclusions? |
| Planning and coordination | When many people and deadlines depend on one another | Can you identify dependencies and highlight decisions that are still open? |
| Communication and connecting people | When different requirements need to be brought into alignment | Can you turn a discussion into a clear agreement? |
| Delivery and completion | When a plan needs to become a usable outcome | Can you complete a specific step independently and hand it over? |
It is fine to recognise yourself in several categories. In practice, it often helps to choose one main responsibility and one supporting contribution. For example, you might develop solution proposals and help test them. It is less helpful to promise to take on an entire process just because every part of it sounds interesting.
Choose a role in four steps
You can use this process in a team meeting or when preparing for a conversation with your manager. It does not require a personality assessment or a complicated evaluation.
- Define the outcome. Instead of saying, “I’ll help with communication,” write, “By Friday, I’ll collect requirements from three stakeholders and prepare a shared summary.” The outcome should be clear to other people, too.
- Identify evidence from your experience. Think of a similar task you have completed. It does not have to be part of the same kind of project. If you organised changes in a small team, that experience may also help you plan a new task.
- Be clear about unknowns and limits. Say what you do not yet know, how much time you need, and where you would value input. Missing information or decision-making authority cannot be replaced by effort alone.
- Agree on a check-in point. Decide when you will review whether the arrangement is working. For an unfamiliar project, it may be wiser to assign tasks for a short phase first rather than for several months.
You could say: “I can contribute most by developing options. I’ve prepared similar comparisons before, but I’ll need a partner for the technical implementation. I suggest I deliver a proposal by Thursday, and then we can agree on what comes next.” This is more useful than simply saying, “I’m creative.”
When several people want the same appealing task
For example, two colleagues may both want to lead a project’s opening presentation. One knows the subject matter; the other is good at guiding discussions. The choice does not have to be a contest over who is the “better leader.” The team can separate preparing the content, facilitating the meeting, and documenting the decisions afterwards.
Splitting the work only helps if it does not create more confusion. For each part, clarify who has the final say and how information will be handed over. Working together does not mean sharing responsibility so broadly that no one knows who must finish the task.
Necessary work may not appeal to anyone
In a new project, less visible tasks are often left undone: version control, recording decisions, tracking errors, or keeping others regularly informed. Without someone taking these on, a project can have plenty of ideas but few results.
The answer is not to automatically assign unpleasant work to the most conscientious person on the team. That turns reliability into a reason to pile on more work. Instead, discuss the scope, time required, and how the task should be shared.
There are several options: simplify the process, divide routine work among several people, rotate responsibility, or set aside an appropriate amount of time for it. If the task involves expert review and a high risk of error, rotation alone is not enough; it also requires the right competence and a clear approval process.
Someone whose strength is attention to detail could say: “I’m happy to take on the review if we agree that it will take about two hours a week. I can’t do it on top of my full workload on the other tasks.” This prevents a strength from becoming an invisible obligation.
A worked example from launching an internal service
Imagine a four-person team tasked with introducing a simple internal system for submitting requests. This is a hypothetical example, not a description of a specific company.
Anna enjoys exploring options and can turn conversations with users into proposals. Boris understands data and spots unclear assumptions, but feels less confident facilitating meetings. Cyril reliably completes practical tasks but does not want to coordinate other people. Dana has experience organising work and reaching agreements between departments.
At the outset, they agree that Anna will gather user needs and develop two possible solutions; Boris will check the criteria and risks; Cyril will prepare a small working prototype; and Dana will coordinate deadlines and responsibilities. They also set a date for a joint review.
After the first phase, they discover that some requirements are more technically demanding than expected. Cyril needs Boris’s help checking the data, while Anna has no further user interviews to conduct. The team adjusts the arrangement: Anna prepares a user guide, and Boris helps review the solution. Changing roles is not a failure of the original agreement. It is a response to a better understanding of the work.
Use the project to learn, without taking unnecessary risks
Not every task has to build on what you already do best. A new project can be an opportunity to try something different, such as leading a short meeting or preparing an initial budget comparison. But development works best when the conditions are right.
Separate work you can handle independently from work you can do with support. Do not hand over tasks with major financial, safety, or operational consequences to someone without experienced oversight simply to give them a chance to try something new.
If you want an opportunity to learn, make a specific request: “I’d like to prepare the first draft of the schedule this time. Please review it before we send it to the others.” This gives you a concrete experience without implying that you already know the whole process.
Signs that a role does not suit you or is poorly defined
A task going badly does not necessarily mean you lack the ability to do it. The cause may be unclear instructions, an unavailable colleague, an unrealistic deadline, or too much work happening in parallel. Before deciding you are not capable, check what can be changed.
Pay particular attention to these situations:
- You keep waiting for decisions. You may lack authority or the necessary information, rather than the ability to do the work.
- Everyone comes to you for help. The coordinator role may have quietly expanded to cover every problem.
- You can do the task, but it drains you. Review its scope and frequency; you do not have to give it up immediately.
- Errors occur during handovers. The collaboration between roles may need adjustment, not just one person’s performance.
If the problem keeps recurring, revisit the outcome you originally agreed on. What exactly has changed? Could the task be narrowed, divided, or supported in a different way? Only then decide whether to hand the role to someone else. In a workplace with too few people, or where requirements keep changing without agreement, a better distribution of strengths may not be enough on its own.
Agree on one specific contribution at your next meeting
Before the next work-planning discussion, write down three short sentences: “I can contribute by…,” “To do that, I need…,” and “The work will be complete when….” For the first, include experience or evidence; for the second, specify time or support; and for the third, describe an outcome that can be checked.
Then ask whether the project really needs that role. If it does, agree on the first deliverable and a check-in point. If it does not, look for a related task or a chance to learn. Your strengths have the greatest practical value when they meet a genuine need—you do not have to prove yourself by taking on everything.
