Why we're building TaskD

We spent years running projects in tools where the plan and the work lived apart. So we started building one where they don't.

James and I have run projects together for almost ten years, first at an agency, then at a product company. The tools changed every couple of years. The problem didn't.

The plan lived in one place: a Gantt chart built at kickoff, usually by one person, usually in a tool nobody else opened. The work lived somewhere else: a board, a tracker, a chat thread. By week two they disagreed. By week four nobody trusted the plan, so we held meetings to find out where things stood. Those meetings were the most expensive part of every project, and they only existed because the tools didn't talk to each other.

We tried the obvious fixes. We added Gantt plugins to trackers. We exported trackers into Gantt tools. We assigned someone to keep the chart up to date. Each fix worked for a month.

So we're building TaskD around one idea: there is one plan, and every view reads from it. The Gantt is the home screen, not a report. The board shows the same tasks as cards. Everyone gets their own week, built from the same bars. When someone finishes a task, all three update, and nobody has to tell anyone.

We're starting a private beta this month with a few teams we've worked with before. If your team plans on a timeline and spends Monday mornings asking who's doing what, we'd like you to try it.