DoReply
Get things done

Plan a project and board

Turn a desired result into a project, visible work streams, and cards that people and agents can execute.

Create a board that explains the work at a glance and gives every delegated outcome a clear home.

Select an existing project above and open its board to apply the guidance directly.

Quick steps

Before you begin

Write one sentence that describes the project's result, who needs it, and what constraint matters most. Identify the people responsible for the outcome and the team that should own its resources and budget.

1. Create the project boundary

Create the project in the appropriate team. Add a description with the goal, stakeholders, important constraints, and shared definition of success. Invite only the people and agents who need project access.

Set a project budget appropriate to the work. Treat it as an operating limit, not as a substitute for reviewing individual results and costs.

2. Define the visible work streams

Create epics for coherent streams that someone will want to scan separately, such as research, implementation, launch communications, and support readiness. Give each epic columns that describe meaningful stages in its flow.

Prefer states that help a teammate decide what to do next. A small sequence such as Ready, In progress, Review, and Done is often enough. Add a specialized stage only when it changes ownership or policy.

3. Choose serial or parallel execution

Use serial execution when order is fundamental. Use parallel execution when independent cards can run together. In either mode, add explicit dependencies where one result is a real prerequisite for another.

Keep unscheduled ideas in the backlog. Move work into a sprint or active column when it is ready to receive attention and has enough context to act on.

4. Create outcome-sized cards

Split the project into results that one owner can complete and another person can review. Name each card for its deliverable. Add its context, constraints, definition of done, tasks, dependencies, and source material.

Assign people and agents based on responsibility and capability. Assignment does not start an agent run; it prepares the card for an explicit delegation.

5. Walk the board from left to right

Before starting work, check that every active card has an owner and finish line, dependencies point to real prerequisites, and each output has a durable destination. Remove duplicate stages and cards that describe activity without an outcome.

What good looks like

A newcomer can open the board and identify the project's purpose, active work streams, blocked outcomes, review queue, and owners without asking for a private status report.

Next steps