Radical Collaboration: Who Decides and Who Benefits?

A neighbor helps define what a building should become. A designer turns the idea into a plan. A contractor prices the work. A property partner creates a route to the site. A funder helps pay for it.

They are contributing to the same project, but they are making different commitments. They may receive different benefits and hold different authority. Calling them all partners does not explain the relationship.

A community project should make clear who can influence a decision, who is accountable for making it and what each contribution earns or enables. Those answers should be available before people commit work or resources.

This is part three of BBD's Radical Collaboration series. After defining the approach and examining shared resources, we turn to power and participation.

The aim is a relationship people can understand and choose. Someone should know whether they are offering advice, performing paid work, joining a governing body or entering an ownership arrangement.

Radical Collaboration starts before decisions close

Suppose a neighborhood workshop is being considered. Residents may know when deliveries would obstruct the street. Potential users can explain which equipment they need. A wheelchair user can identify an entrance problem immediately.

Invite that knowledge before the design closes. Bring questions the team can still act on: whether the use fits, which activities matter, what hours would work and what might make the space inaccessible or unaffordable.

An invitation should also identify fixed constraints. The building may have one possible owner, a limited footprint or a use that requires approval. People can work with real constraints when those constraints are explained.

The International Association for Public Participation distinguishes levels of public involvement, from informing people through giving them final decision authority. Each level implies a different promise to the public.

Its public participation framework is a useful reference. A project should name the role it can offer and then follow through on that promise.

If neighbors are advising, say how that advice will be considered. If members hold a formal vote, explain the governing process. Do not make a listening session sound like a power it does not actually confer.

Put authority beside responsibility

Shared decisions need an operating structure. Someone has to sign contracts, supervise work, approve spending and respond when a commitment is missed. A project cannot leave those duties floating between everyone involved.

Match the structure to the decision. A qualified professional assesses structural safety. A project entity authorizes an acquisition. An operator handles routine bookings within agreed rules. Members may govern defined long-term choices.

The project can invite broad input while keeping those responsibilities clear. Local knowledge informs the brief; professional work tests feasibility; the authorized body decides whether the commitments can be made.

What the space should serve. Neighbors, potential users and local businesses. Authority to make clear: Who approves the project brief.

Whether the building is suitable. Qualified assessments and user requirements. Authority to make clear: Who can proceed with site control.

How the work is delivered. Workers, designers and affected partners. Authority to make clear: Who approves scope, contracts and changes.

How shared space operates. Users, neighbors and the operator. Authority to make clear: Who sets rules and resolves complaints.

How value is retained or used. Members and other parties with defined rights. Authority to make clear: The governing agreements and decision process.

This is a planning aid, not a universal governance model. A project's actual legal and operating arrangements determine the final allocation of authority. The point is to make that allocation legible.

Contribution needs terms people can rely on

An organizer asked to arrange a session needs to know the deliverable, date, budget and reviewer. A contractor needs access permission, scope and payment terms. A neighbor offering an introduction may need no work assignment at all.

Treat those commitments according to what they are. Useful knowledge deserves acknowledgment. Professional work needs a proper agreement. A person accepting an unpaid role should understand its scope and limits.

“We are all building this together” is a reason to be careful with one another's time. It should never become a substitute for explaining compensation or a reason to keep adding unpaid work.

A work brief can be short. State what is needed, who authorizes it, when it is due, how acceptance is determined and what payment or approved benefit follows. Include a route for questions and changes.

The person offering the work must have authority to make the commitment. Enthusiasm does not authorize a payment, property access or a future benefit on behalf of an organization.

Keep work, review and benefits distinguishable

A record that work was submitted is different from a decision that the agreed work was accepted. Payment or a program benefit may require another authorization. Participants should be able to see where they are in that process.

Imagine a designer agrees to produce two layout options. The reviewer accepts them, then asks for a third based on a new use. The team should identify whether that is included work or a new scope before the designer begins again.

The same care matters when a project changes. If an inspection rules out the building, accepted research and design work still have the terms originally agreed. The project's disappointment should not silently move the cost to contributors.

Records help make those obligations visible. They should show the request, the deliverable, the review and the authorized outcome. They also need a way to correct errors and resolve disputed judgments.

Three scale models show different allocations of one workshop between open workbenches, teaching and small studios. — Shared decisions require visible alternatives and tradeoffs. AI-generated editorial illustration.

Be specific about what people can gain

A project may create several kinds of value: paid work, skills, access to equipment, usable space, membership rights or an ownership interest. These benefits have different meanings, conditions and time horizons.

A worker's fee pays for a defined service. A lease gives rights to use space under its terms. A training opportunity has requirements and a learning outcome. A governance role provides authority over specified decisions.

An ownership arrangement has to explain what is owned, through which entity, with which rights and obligations. A general promise of “a stake” leaves too much for the reader to guess.

BBD's ambition is to connect useful contribution with lasting participation in the places it helps create. That ambition must be expressed through the relevant project and program agreements.

EQTBLT credits should be understood through those terms. A balance alone does not give someone property title, a guaranteed cash payment, housing or an investment return. A proposed benefit and a delivered benefit are different stages.

That clarity makes the invitation stronger. People can evaluate what is available, what still has to be established and whether the commitment fits their circumstances.

Radical Collaboration must account for unequal power

An owner, a lender, an experienced professional and a first-time volunteer do not enter a project with the same bargaining position. A collaboration that ignores this can reproduce the imbalance it hoped to change.

Put relevant information within reach before a decision. Give people time to read it. Explain unfamiliar terms. Provide a way to ask questions without having to challenge a well-connected person in a crowded room.

Participation also has costs. A meeting time can exclude shift workers. A long process can favor organizations with paid staff. Transport, childcare, accessibility and language needs can affect who is able to remain involved.

A team should budget for the participation it says it values. When resources are limited, acknowledge the gap and look for practical alternatives. Do not describe a narrow group as the whole community.

Power is also visible in who can say no. Someone should be able to decline a task, question an estimate or identify a conflict without being treated as an obstacle to the mission.

Use disagreement to improve the decision

Consider a proposed evening workshop program. Users want access after work. Neighbors are concerned about noise. The operator sees an additional staffing cost. All three are relevant to whether the service can last.

The team can examine quieter activities, limited evening hours, staffing options and a review after a trial period. It should show the consequences and identify who has authority to choose among them.

After the decision, publish the reason and the next review point. If a suggestion was rejected, explain the constraint. If new evidence changes the answer, update the record and tell the people affected.

A person may still disagree. The process becomes more credible when they can see that their concern was understood, considered and answered with a reason they can examine.

Make the relationship worth staying in

The strongest invitation gives people both purpose and clarity. They understand the place they are helping create, the contribution being requested and the rights or benefits attached to their role.

They also know how to raise a problem. A collaboration needs a path for review, a way to change an agreement and terms for leaving. Those arrangements support a durable relationship because participation remains an informed choice.

If you have a skill or service to bring, explore contributing to BBD. If your organization can support a project, start a partnership conversation. A specific role should come with specific terms.

Questions about decisions and benefits

Does attending a community meeting make someone a member or owner?

No. A meeting can inform or shape a decision. Membership, voting and ownership rights require the applicable admission process and agreements. The organizer should explain which role the meeting offers.

Should every contribution receive the same reward?

Different commitments call for different terms. The project should explain its method, apply it consistently and provide a way to question errors. Equal respect does not require pretending every task has the same scope.

How can a contributor check what they are entitled to receive?

Start with the accepted work scope and relevant program or project agreement. Ask who authorizes the benefit, which conditions apply and what record confirms delivery. A slogan or account balance cannot answer all of those questions.