Projects and deliverables
Break a campaign, rollout or client project into deliverables and individual tasks. Connect the work through parents and children, with owners, due dates and supporting material close to each action.
Manage projects, everyday tasks, commercial pipelines and creative production on boards shaped around your process. Keep owners, deadlines and supporting material clear, then add Butter and workflow automation where they help.
Use custom boards to organise projects, everyday tasks, pipelines and production work into clear stages. Give each task an owner, dates, priorities and supporting context. Follow progress in a Kanban board or list, connect larger work through parent and child tasks, and add Butter or workflow automation where it helps.
Kanban has roots in Lean manufacturing, where making work visible helps people understand what is ready, what is in progress and what is waiting. The same principles are useful for project teams, studios and everyday operational work.
Give each column a clear meaning and agree what needs to be true before a task moves on. A growing review queue can prompt a discussion about a hand-off, while blocked cards show where someone needs help. Keep the task's owner and next action clear so work can move with purpose.
Your team can agree how much work to start and what to pull next, using the board to support those working practices. Review recurring delays and adjust the stages or hand-offs as you learn. These are Lean-inspired ways to use a visual board, rather than a claim that the board provides factory scheduling or automatically enforces a work-in-progress policy.
A board manager can rename, reorder and hide columns, and add columns for the stages the team needs. Each column has an underlying status kind: to do, active, done or cancelled. The four preset statuses remain available even when their labels or visibility change.
For example, an everyday work board can use Ready, In progress, Review and Done, while a production board can name the stages around briefing, shooting and preparing finished assets. Agree what a stage means so everyone understands the hand-off.
A column represents the task's place in the process. Its separate importance and urgency fields describe its priority. Keeping those concepts distinct lets you represent both where the work is and how much attention it needs.
Break a campaign, rollout or client project into deliverables and individual tasks. Connect the work through parents and children, with owners, due dates and supporting material close to each action.
Start with My tasks across the boards you can reach. Check priorities, due dates, blocked work and overdue items, then use the task details and estimates to decide what needs attention next.
Use stages such as Incoming, Qualified, Proposal, Decision and Won or Not proceeding. Keep the next action, owner, follow-up date and discussion on each card as the opportunity moves through your process.
Track work through Brief, Pre-production, Ready to shoot, Shot, Editing, Review and Assets ready. Keep briefs, references, responsibilities, deadlines and feedback with each shoot or deliverable.
Give a task an owner, due date, importance and urgency. Mark it blocked when progress depends on something else, and add an effort estimate where it helps planning.
Use formatted details for the brief, findings and next steps. Attach documents and files so people reviewing the card can open the supporting material they have access to.
Explain changes in comments, reply in a thread and mention the people who need to respond. The task's activity records field changes and the reasons added with them.
Use the Kanban view to follow work by status, or switch to a list when you need a table of tasks. Search by title and filter for your tasks, blocked work or overdue items. Collapse a column to focus the board without changing its tasks.
My tasks gathers work assigned to you across the boards you can reach. Use it to review what is due, check the next action on a card and decide which work to tackle or discuss with the team. Your personal board stays private to you, while shared boards provide a common place for a team's process.
Open a card to read its details, update its fields and follow the conversation. Moving work to another status can include a comment explaining the decision, giving the next person useful context.
For example, a producer can begin the day by checking shoots awaiting samples, editing tasks due today and assets waiting for review. The board provides the shared progress view; each person's task list helps them identify their own next action.
Boards have four levels, with default names Initiative, Project, Story and Task. A board manager can rename those levels to suit the organisation.
Give a task a parent at a higher level on the same board, then follow its parents and children from the task. A task does not have to sit directly below its parent in the hierarchy. This lets a small action belong to a larger project without inventing intermediate work.
For example, a production team could name its levels Campaign, Shoot, Deliverable and Task. A seasonal campaign contains a footwear shoot; the shoot contains an image-set deliverable; and the deliverable contains preparation, selection and retouching tasks. Each item can have its own owner and status.
Changing a level can unlink relationships that no longer fit. The interface warns before those changes, and the tasks remain on the board.
Attach a Task Tool to an AI step in a workflow. Choose the boards it can use and whether it can read, create, update or comment. Set a limit on the number of tool rounds available in a run.
The agent receives instructions and access to those tools, then chooses which tool actions it needs for the task. For example, a classification agent can check an existing review board, create a card for a new update, set its status and explain the classification in a comment.
Different agents can have different access to the same board. A summary agent might only read and comment, while a criteria-review agent reads decisions without changing the tasks. Permissions and board scope define what each one can do.
Fixed Create Task, Read Task and Update Task steps are also available when the workflow already knows the action to take. A Task Trigger can start a workflow for selected events, such as creation, a watched field change, a status transition or a comment. Configure filters and run limits to suit the process.
See how business updates become an outreach review queue for an example combining classification, task tools, notifications and instruction review.
Ask Butter to find, read, create or update tasks you can access. Mention Butter in a task comment when you want help with that piece of work.
You can also assign a task to Butter and start an unattended run. Butter uses the details as its brief, adds a plan, can divide larger work into child tasks, and reports when the result is ready for review. If it cannot continue, it marks the task blocked and explains what it needs.
Butter working on an assigned task is separate from an AI step using a Task Tool inside a workflow. Both use tasks, but you choose their briefs and permissions in their respective settings.
Assignments, mentions and replies can notify the people involved. The mobile app brings task updates and conversations within reach when people are away from their desks.
For a scheduled digest or another custom notification, build a workflow that reads the relevant tasks and sends a chat message. Choose the audience, schedule and selection rules rather than assuming every board change creates the same alert.
Add an effort estimate, run your timer against a task or log time already spent. Logged time contributes to the task's record, helping the team compare the work planned with the effort recorded.
Share a board with people or teams at view, comment, edit or manage level. Board access applies to its tasks, and organisation admins can see the boards. Comment access is needed to read task discussions.
An attached document retains its own access controls. Attaching it to a task gives people a route to it, while its permissions decide who can open it.
Your personal board cannot be shared. Where external sharing is allowed, an accepted friend can own and open an individual task without receiving access to its whole board.
Choose the stages for a project, pipeline or everyday process. Give each task an owner and a clear next step, then add automation where it helps the work move.
No card. Your data stays in your organisation.