How to Track One Company Project Across Every Team (Without Chasing Anyone)
Every team says it is on track. The project still slips. The fix is not another status meeting. It is one place where every team's real work shows up by itself.
A company project, say a website launch, touches Design, Engineering and Marketing. Each team plans in its own way and its own tool. The person responsible for the launch ends up asking each team for an update, copying answers into a slide, and finding out on Thursday what was blocked on Monday.
The information existed the whole time. It just lived in three places nobody could see at once. Here is a setup that fixes that without asking anyone to change how they work.
Why cross-team projects go dark
The usual answer is one big shared board for the project. It works for a week. Then each team goes back to its own list, because that is where its other work lives, and the shared board turns into a second copy that nobody updates.
Copies drift. A task marked done in Engineering's sprint still says in progress on the launch board. So the project owner chases people, and the chasing becomes the job.
The idea: one project, every team, live
Instead of moving work into the project, let the project collect it. The project is a channel with one sub-list per team. Anyone can send their own task into it, and pick the team it belongs to.
The task does not move and is not copied. It stays in the person's own workspace and also appears on that team's board in the project. Updating it in either place updates both, because it is the same task.
Don't move work into the project. Let the project collect it.
What the project owner sees
The project opens on a canvas. The goal sits on top: what the project is and when it is due. Below it are the team boards, side by side, each a live Kanban: To do, In progress, Blocked, Done.
Cards move as people work. An arrow between two teams shows a dependency, such as Marketing's launch email waiting on Engineering's pricing page. You see the blocked card before anyone has to tell you about it.
Set it up in four steps
1. Duplicate the template. In Taskpend, open Templates, find Website Launch and press Duplicate. The copy lands in Channels and becomes a real channel. Rename it to your project.
2. Send tasks in with #. Anyone on the team types #Website Launch (or your project's name) on their own task and picks a team, for example Engineering.
3. Keep working where you work. The task stays in your own list, and shows on the team's board in the project. A task that arrives without a status starts in To do, so nothing goes missing.
4. Open the canvas. The project owner sees every team's progress in one place, without a status meeting.
Make it your own
The three teams are just the project's sub-lists. Rename them, add a fourth, or remove one; every child of the project is a team people can pick when they send a task in.
Duplicate the template again for the next project. Each copy is its own channel with its own canvas, so a company can run several projects side by side and still see each one in a single view.
Takeaways
- One shared board turns into a second copy that nobody updates.
- A project channel collects each team's real tasks, without moving or copying them.
- Type #ProjectName on your own task and pick a team; it shows on that team's board.
- The canvas shows every team's live board under the project goal, with dependencies as arrows.
- Start from the free Website Launch template in Taskpend.
Taskpend is a nested outliner with mirrored tasks, six views and AI agents that execute. Free for individuals.