What we learned from our first 50 beta teams

Four months into the beta, we've watched 50 teams plan real projects in TaskD. Three things surprised us, and one changed the product.

We opened the beta in December with a handful of teams we knew. By April there were 50: agencies, product teams, an events company, and a few internal IT teams. We sat in on planning sessions, read every support message, and asked the same question at the end of each call: what did you open first this morning?

Surprise one: people open the Gantt when it's the default. In most tools the timeline is a tab you have to go looking for. When it's the first thing you see, people use it daily. Several teams told us it replaced their standup doc.

Surprise two: managers care about workload more than dates. We expected leads to ask for better date tracking. Instead the most requested feature was seeing who was overbooked next week. Dates slip because people are overloaded, and they wanted to catch the cause, not the symptom. Team workload moved up our roadmap as a result.

Surprise three: nobody wanted more fields. We asked teams what was missing and braced for a long list of custom fields. What we got was the opposite: fewer required fields, faster task creation, keyboard shortcuts. The request we heard most was "let me add ten tasks in a row without touching the mouse."

What changed. The board. We'd built it as a separate view with its own columns. Beta teams kept asking why moving a card didn't move the bar. They were right. We rebuilt the board so its columns are the statuses on the Gantt and its cards are the same tasks. That one change is now the core of the product.

We're keeping the beta open through the summer. If your team plans on a timeline and is tired of updating two tools, we'd like to hear from you.