# The right people around the problem.

> How Webvelopment organises project responsibilities, specialist input and client collaboration.

Canonical page: https://webvelopment.co.za/about/our-team/

Language: en

People & collaboration

Know who to turn to for a design question, a business decision or a release approval. We agree the responsibilities your project needs, including where our work meets your team's knowledge and any specialist input.

[Let’s talk](https://webvelopment.co.za/contact/)

## A team model built around the brief

![Two colleagues working side by side with laptops and notebooks.](https://webvelopment.co.za/images/lifestyle/pair-programming-1400.webp)

Illustrative photography · [Christina @ wocintechchat.com M / Unsplash](https://unsplash.com/photos/two-women-using-macbook-pro-KzU0ezL9tJo)

Your project may need design, development, content and marketing input, but the balance depends on the work. A new enquiry website raises different questions from a feature being added to an existing product. We start with what you need to achieve and identify the responsibilities needed to get there.

The proposal should then name your delivery contact and explain the contributions required. People, capacity and availability are confirmed for the engagement; this page describes how those responsibilities fit together.

## Clear responsibilities help everyone

A delivery lead coordinates the agreed work and reviews. Design, engineering, content and marketing responsibilities are identified where the project needs them. On your side, we need someone who can bring feedback together, settle priorities and involve colleagues who know the business details.

That person does not have to know everything. Your sales team might explain what makes an enquiry useful, while an operations colleague confirms what happens after a form is submitted. Knowing whom to ask helps us turn those answers into useful content and behaviour.

## Specialist input, with boundaries

Some projects need translation review, photography, legal advice or help from a platform provider. We identify those needs during scoping and clarify whether the work is included, supplied by your team or commissioned separately. Any required credentials or language coverage need to be verified for the people involved.

For example, if your team is arranging photography, agree which images the design needs and when they can be supplied. If legal wording needs approval, identify who will obtain it before planning publication. These dependencies affect the work even when the specialist is outside the delivery team.

## Working with your existing team

If you already have an agency or product team, tell us how work reaches them and how they review it. Collaboration may take place in your existing systems where access, security and workflow allow. Agree who assigns tasks, where design or code feedback belongs, and who can authorise a release.

Bring any relevant design files, technical guidance and access requirements into that discussion. It helps establish where our contribution starts, what your team retains and how completed work moves between us.

[Read about our delivery process](https://webvelopment.co.za/about/our-process/) or [talk through the roles your project needs](https://webvelopment.co.za/contact/).

## A clear role map before a promise of capacity

Before work starts, the engagement should make these responsibilities easy to find:

- Your main delivery contact and the work they coordinate.

- Who prepares and reviews each relevant output, such as page copy, designs or code.

- Who supplies business information, assets and specialist approvals.

- Who can approve the finished work and authorise production changes.

One person may hold several responsibilities. The useful question is whether each task has someone able to move it forward, with any availability or coverage requirements agreed.

## Ask who owns a decision before asking for a headcount

Consider a common review situation: one colleague wants a shorter enquiry form, while another needs more information to prepare a quote. Someone on your side needs to weigh that trade-off. We can explain the design and implementation implications, but your business priorities guide the choice.

Use the same approach for technical questions. Agree who assesses a proposed change and who approves its release. Coordination, technical leadership and specialist review are separate responsibilities, so check which are included in the engagement.

[Review the project process](https://webvelopment.co.za/about/our-process/) · [See the work to discuss](https://webvelopment.co.za/work/) · [Discuss the roles your brief needs](https://webvelopment.co.za/contact/).

## Questions for a better brief

A few useful answers before you decide.

### Will we know who is responsible for the work?

The proposal and working agreement should identify your delivery contact and who is responsible for the relevant outputs. They should also explain where to send feedback and whom to contact if a question remains unresolved. Confirm named personnel and availability as part of that agreement.

### Who should act as our internal decision-maker?

Choose someone who can bring feedback together and resolve priorities, with access to colleagues who can confirm product, operational and commercial details. They do not need to answer every technical question personally. When reviewers disagree, this person should help settle the instruction before we implement the change.

### How are specialist needs handled?

Raise known needs during scoping, including translation review, legal advice, photography or platform-provider support. We can then clarify what is included and what needs a separate arrangement. Name the person arranging each contribution and allow for it in the plan, especially where other work depends on receiving it.

### Can the collaboration follow our existing delivery tools?

We can discuss using your tools where access, security and practical workflow allow. Show us where tasks live and how your team reviews work. Agree where final feedback goes and who authorises release, so a comment in a chat or design file is not mistaken for approval.

### Does a dedicated arrangement remove the need for product leadership?

No. A contributor still needs clear priorities, business context and someone to approve the work. A separately managed workstream may include delivery coordination, if agreed. Be explicit about who sets product priorities, makes technical decisions and approves scope or budget changes.

### How do we avoid becoming dependent on one person\u2019s memory?

Keep key decisions, account ownership and operating instructions somewhere the relevant people can find and maintain them. Plan the handover around tasks your team will actually perform, such as updating a page or managing an enquiry, and agree which need a demonstration. Confirm personnel arrangements, confidentiality and any transition obligations in the engagement terms.

Let’s move things forward

## Start a conversation

Tell us what you are working towards. We’ll help you find a practical next step.

[Let’s talk](https://webvelopment.co.za/contact/)