How to run a product launch on one board

Launches go wrong in familiar ways. The date lives in a slide deck, the tasks live on a board, the design files live in a chat thread, and requests from sales arrive in DMs. Two weeks out, someone asks "are we on track?" and nobody can answer without an hour of digging.

This guide walks through running a launch from one board: setup, planning, the routine work, requests, sharing progress, and the review afterwards. The examples use Taskeni, but the structure works in most board tools. Where a step needs a paid Taskeni plan, we say so.

1. Set up the lists around decisions, not departments

A common mistake is one list per team: Design, Copy, Web, Social. Make the lists stages of work instead, so a card's position tells you how close it is to done.

A setup that works for most launches:

Planning: ideas, briefs, and anything not yet assigned.
In progress: someone is working on it.
Needs review: waiting for a decision from someone else.
Published: live, sent, or shipped.

In Taskeni, the Marketing campaign template creates these four lists with Email, Social, Content, and Launch labels. Design-heavy launches can use the Design workflow template (Ideas, In design, Review, Shipped) on a second board.

Two settings make the board stricter, in a good way:

Set the last list as the completion list. A card that lands in Published is marked done. Nobody has to remember to tick it, and the progress numbers stay honest.
Put a task limit on Needs review. If reviews pile up, the count turns red. Five things waiting on one approver is a scheduling problem, and the board should show it.

Use labels for the channel (Email, Social, Web) and custom fields for anything you'd otherwise put in the description and search for later: the audience, the budget, a link to the final file. Custom fields show as columns in Table view, which is handy when someone asks "which emails are still unscheduled?"

2. Plan backwards on a timeline

Once the launch date is fixed, plan backwards from it. Give every task a start date and a due date, not just a due date. A due date alone tells you when something should be finished; a start date tells you when the work collides with everything else.

Then switch to Timeline view. Taskeni shows four weeks at a time, with each task as a bar and a line for today. Three things to look for:

Stacks. Five bars in the same week for one designer is a problem you can fix now by moving dates or reassigning, not in launch week.
Gaps before review. If the copy is due the same day the page goes into review, there's no slack. Move one of them.
Late starters. Tasks that start in the final week of the launch are usually underestimated. Bring them forward.

For a closer look at a single week, Calendar view has month, week, and agenda layouts. Drag a task to another day to reschedule it.

If the work depends on other work (the landing page can't start until the copy is approved), mark it. Open the landing page task and add the copy task under Blocked by. Both tasks then show the link, so the person waiting knows exactly what they're waiting for.

3. Write down the routine work once

Every launch has work that repeats: the weekly social batch, the Monday status note, the newsletter, the post-launch metrics check. Recreating these by hand is how they get forgotten.

Make each one a recurring task instead. Taskeni supports daily, weekday, weekly on chosen days, monthly, and custom intervals, and can end a series on a date or after a number of occurrences. That's useful for a six-week campaign: "every Tuesday, ending after 6".

Each occurrence is created a week ahead as its own task, with the original's checklist copied in. Comments stay with the week they were written in, so this week's approval doesn't get mixed up with last week's. If a holiday week needs skipping, skip that one occurrence and the rest of the series stays as it was.

Add reminders to the tasks with hard dates. A reminder can go to the assignee on the due date, or one day, two days, or a week before. For the press release or the email send, a week's notice is worth setting.

4. Take requests through a form, not a DM

During a launch, other teams will ask for things: a one-pager for sales, a banner for a partner, a last-minute social post. If those requests arrive in chat, they don't show up on the plan, and the plan stops being true.

Give the board a request form. In Taskeni, each board can have a public form page. The requester fills in a title, the details, an optional due date, and a file, plus any custom fields you choose (say, "Audience" and "Channel"). No account is needed. Each request becomes a task in the list you pick, with the requester's email attached. They get a receipt, and another email when the task is done, so they stop asking "any update?"

For your own team, every board also has an email address. Forward a request email to it and it becomes a task, with the subject as the title and attachments as files.

5. Review where the work is

Design and copy reviews eat launch schedules because feedback scatters. Keep it on the task:

Attach the file to the task. Paste a screenshot or drop the file in.
Pin feedback to the image. In the file preview, add a pin, click the exact spot, and write the comment. Pins are numbered on the image and listed in the thread, and each one can be resolved when it's fixed.
@mention the reviewer. They get a notification, and the mention picker only offers people who can see the board.
React instead of replying. An Agree reaction says "approved" without another comment in the thread.

If you've turned on AI helpers, Catch me up on a long review thread summarizes what was decided and what's still open, with each point linked to the comment it came from.

6. Show stakeholders the plan without a status meeting

Leadership, a client, or a partner agency usually needs to see progress but not take part in it. There are two ways to handle that.

Invite them as a guest if they need to comment or approve. Guests see only the boards they're added to. On the Free plan each board can have 3 guests; Pro and Business have no limit.

Send a read-only share link if they only need to look. On Pro and Business, anyone who can edit a board can create a link that shows its lists and tasks as a board or a list, with titles, due dates, labels, checklist progress, and optionally assignee names. Comments, files, and time logs are never shown. Visitors don't sign in. Set the link to expire after 7, 30, or 90 days, check the view count to see whether it was opened, and revoke it after launch.

A share link replaces the weekly "where are we?" email with a page that's always current.

7. Review the launch with real numbers

After launch, before everyone moves on, spend 30 minutes on what happened. Taskeni's Home screen has a This week review that lists what was done, what slipped, what started, and what's due next week, per board and per person. Copy it as Markdown into your retrospective notes.

On Pro and Business, reports add three numbers for the board over the last 4, 12, or 26 weeks:

Cycle time: the median and 85th percentile days from when work started to done. If review tasks have a long 85th percentile, approvals were the bottleneck.
Throughput: tasks completed per week. Compare launch weeks with normal weeks.
Overdue trend: open overdue tasks at the end of each week. A rising line in the last two weeks means dates were set too tight.

Filter by assignee or label to see whether one channel or one person carried the load, and download any chart as CSV.

Then archive the launch board, or save its best tasks as templates for next time.

A checklist to copy

Stage lists, with Published as the completion list and a task limit on Needs review.
Start and due dates on every task, checked in Timeline.
Blocked-by links, recurring tasks, and reminders on hard deadlines.
A request form for other teams.
Feedback pinned on images, approvals as reactions.
A guest invite or share link for stakeholders, and a review after launch.

The Marketing campaign template gets you most of the way. Start free, or read more about planning features and client sharing.