Teaming up? Start here.


Art created with AI software

Are you thinking of teaming up?

In many blockchain communities, there is a tendency for community members to participate in funding proposals. The community often has a treasury which gives out grants for various projects that help flesh out the ecosystem. The reason is to encourage adoption of the blockchain, while adding value to the community. And while that is great, in these contexts, people from around the globe get together without really knowing each other. So, how should they team up for the project?


A brief checklist for those planning to team up.

Here, in no particular order of priority, is a list of items which are helpful for teams which are teaming up.


The idea of dropping these here is to give an elaboration of each item later on.


1. KYC of each team member - national identity card, passport or driving license.

2. Contact detail of each member: e-mail address and telephone numbers;

3. Wallet address for individual members;

4. Multisig Wallet address for team;

5. Breakdown of each member's role and responsibility.

6. Scope of the project (basic or detailed).

7. Timeline


Now that we have a list, let's dive into it.


I. KYC of each team member

For the uninitiated, KYC means "know your customer". It's what the bank does when you go to open an account with them. "Hi sir, can we see some identification papers," they tell you, "and can you please fill out this form." It's necessary to put a name to a person, and to identify the person. This is compliance with anti-money laundering (AML) rules, which have been promoted by FATF (Financial Action Task Force), an intergovernmental body for the development of AML laws.


In the Web3 ethos, there is no doubt that privacy and anonymity are important considerations. Many Web3 advocates would frown if you were to try to conduct KYC on them.  However, as a team member of a Web3 project, when you want accountability, you need to conduct the KYC among yourselves. This way, in case the project runs into difficulties, at least members are less likely to disappear. This would be in line with your goal of keeping the project transparent and members accountable.


II. Contact Details of Team Members

For obvious reasons, you will need to contact each member because it is a team effort. Therefore, share your mobile telephone number and email address with each other. Try to make sure that the mobile telephone number can be used to contact each other over messaging apps like Telegram, WhatsApp, or Signal.  


III. Wallet address of Each Team Member

There is again another obvious need to ensure that each member will be paid. So, for purposes of keeping things transparent, each member should provide the detail of his designated wallet for the purpose of the project. You don't have to give your "regular" wallet, if it is filled with embarrassing NFTs or if it has a large amount of crypto in it. You could prepare a new wallet, and give its address to the team. The idea is to ensure that there is auditability as the project progresses, so that the payments due to each member can be tracked. 


IV. The Team's Wallet Address

The team needs to designate a team wallet to receive funds from the project sponsor. For a project under the auspices of the Project Catalyst, for example, or some other blockchain foundation, it is commonplace for teams to specify that funds be disbursed to a team wallet. 


For purposes of a team wallet, it is best if it is multisig (multisignature), meaning that funds can be withdrawn only if two or more members approve the withdrawal. This ensures that the funds are not dissipated by one single member, while ensuring that the project is not held ransom by that same one member. However, be aware that multisig wallets cannot protect against collusion by members who are intent on draining the team wallet jointly.


V. Scope of each member's responsibility.

There must be some basic idea about what each member has to do for the project. So, if you can, draw up a list of duties for each member so that, at the very least, you can keep tabs on what they have agreed to do for the team. Bear in mind that projects sometimes expand or pivot in unexpected ways, so, a periodical re-evaluation of what each member's scope of work will be necessary to make sure that the project's goals are being met and covered by all the members.


If necessary, you can first scope out the project, to make sure that you have a list of what needs to be done, before assigning it to individual members. (So, maybe you should do the next step before this one.)


VI. Scope of the project

When embarking on a project, it is good to have a clear outline of the project's goals, and what each of the members think the project should cover. That way, there won't be any falling out when members suddenly diverge on the important aspects of the project, which could conceivably lead to the collapse of a team as some members head off to start a fork of the project.


The project is started with the vision of the founding members, and of course, it should be captured. All the goals of the project, what it aims to accomplish, and what it aims to offer, should be laid down in writing. But this isn't carved in stone, and a periodical re-examination is good. So, for best results, a balance should be struck between capturing exactly what the project is about, and making sure that it is flexible enough to change parts of, to ensure that it stays relevant. 


What would be bad would be to totally change the scope of the project, unless there are very good reasons to do so e.g. something that you want to deliver has become academic, or it has become illegal. So to avoid the project becoming totally illegal, you try to find a way to change it and keep it relevant.


Projects which are vaguely defined may cause members to face serious disagreements later on, when they discover that their shared goals are incompatible in the implementation. On the other hand, making things too clearly spelt out may mean that the project members are too tightly constricted.


When the project is breaking new ground, it may be better to adopt an agile approach, in which the goal is iteratively developed over time. There is a whole discussion outside the scope of this article about the benefits of agile vs waterfall approaches, mostly in relation to project management. 


VII. Timeline

Like all things, a project needs to have a sense of timing. Otherwise, you may end up waiting forever, and that may not necessarily be a good thing. (If you have a friend in his 30's still waiting on his childhood crush, that's one good example.) 


Indeed, a project needs to break down its milestones, and each of those milestones should have some kind of timeline to it, so that the project can be managed. The danger here is giving ourselves too much, or too little, time. But there's a first time for everything, and these things can be adjusted over time. It is better to go into a project knowing that there is a timeline, and if you are unable to achieve it, then you come out and be truthful about it, and then you adjust it again.


Having said that, it seems clear that there will be a need to measure the progress of your project by the time elapsed, and the scope that have been accomplished. Otherwise, your stakeholders could come to the conclusion that the project is being poorly managed because it has no metrics by which its progress is being measured.  And that could mean the plug being pulled on the project.


To avoid that problem, identify the milestones, and put in timelines which are realistic.


Formalize it with a teaming agreement

This website is being run by the BCTA team, which got its name from the phrase, "Beyond Create Teaming Agreements". The story of that is that, we got together with the idea of creating a template for teaming agreements which members of the community can use in the future.


Teaming agreements are often drawn up by members of a team, who are teaming up for the first time. However, even experienced team members can choose to use a teaming agreement to avoid conflict while working on their shared goals. In many cases, the team has no idea about where their funding is going to come from, how much funding they would raise, and things like that. Thus, it makes sense to enter into an agreement that recognises this situation, and says, "We want to work together, and if we are funded, this is  what we will do..." 


The teaming agreement kicks in if the team members receive funding, but in some cases, they can agree to fund it out of their own pockets. In other cases, they may have applied to several places for funding, and that too, can be reflected in the agreement.


So what goes on after the project is funded? In some cases, the parties form up an entity such as a private limited company. In some other cases, they decide to form a DAO, which is unincorporated. Each team has its own idea of what works, but there are benefits of incorporating a company from the costing / taxation side of things because you can expense them out and claim a reduction of profits. However, with corporate entities you may run into trouble when a key member of a distributed team suddenly decides to disappear or become incommunicado.


One issue which often arises is, how often should funds be paid out to members? For some members who shoulder more work than others, they may rely on the funds in order to sustain themselves. It becomes important for them to ensure that their financial needs are being met, while they are contributing their time and energy to the project. However, the other team members may not see the pressing need for the funds to be disbursed, because they do not feel the pressure. This point is worth speaking about among the team members.


Thanks for reading this article!

If you would like to give feedback on our content, please reach out to our team on social media. The editor in charge of this website is Mr Kevin Koo (@kevinkoosk on Twitter).