Divide responsibility in a founding team

Working well together on an idea does not automatically explain who will answer a customer, approve a promise or resolve an urgent disagreement. A founding team needs a practical division of responsibility alongside enthusiasm. Start with the work that will happen next, rather than impressive job titles.

Map a real week of work

List the activities needed to move one customer request through the business: first reply, assessment, offer, delivery and follow-up. Add internal work such as checking information, maintaining tools and preparing accounts for professional review. Use concrete actions rather than broad labels like operations.

For each activity, name one person who keeps track of completion. Other people can contribute, but the team should know who notices if nothing happens. Check that the person's actual availability matches the responsibility rather than assuming everyone has the same working hours.

Identify decisions that belong together

Some decisions can stay with the person doing the work; others change commitments for the whole business. Discuss examples, such as accepting a shorter deadline or promising a new service. Decide what requires consultation before anyone speaks on behalf of the team.

Y Combinator's co-founder questions include roles, responsibilities and handling disagreements. These conversations are useful before a problem becomes urgent. Formal ownership, remuneration and binding agreements need their own appropriate professional advice; a task board does not resolve them.

Test the handover with a small example

Use a fictional enquiry and walk through it together. What information does the next person need, where will it be found and how do they know it is ready? If a founder is away, identify a substitute and the decisions that must wait.

Agree on one place to record commitments. A quick conversation can remain quick, but a changed deadline should not exist only in one person's memory. Keep confidential information in an appropriately restricted location.

Set a review point

Revisit the arrangement after a defined work cycle or a meaningful change in demand. Ask where work waited, where two people acted twice and where nobody was clearly responsible. Change the arrangement around those observations rather than debating titles in the abstract.

A useful division of responsibility is specific enough to guide today's work and flexible enough to revise. It makes cooperation visible while leaving room to discuss difficult choices before they turn into conflicting promises.

Sources: Y Combinator: 10 Questions to Discuss with a Potential Co-founder.