Progask
← Blog

Part 7 of 8 · Thu 29 Oct 2026 · 3 min read

Two people said no. Here's what they taught us.

Eight of ten survey respondents asked for early access to Progask. Two declined. Their reasons were the most useful feedback we got.

At the end of our survey we asked one last question: would you like early access to a tool that tries to solve these problems?

Seven said yes. One said maybe. Two said no, thanks.

It would be easy to celebrate the 80% and move on. But in a survey this small, the two no's are worth as much attention as the yeses, because they tell us exactly how Progask could fail.

Both were team leads who work with 6–15 people. Both use AI chat every day. And both gave thoughtful reasons.

"One more app" is a real cost

The first team lead rated an auto-updating board 2 out of 5. When asked why, they said they would rather keep everything in one app than use several apps for the same job.

They also chose "None — I want to stay in full control" when asked what AI could do on their board, and said their current setup suits their needs.

What makes this interesting is their slip story. It was the most painful one in the survey: a bug fix way past deadline, an engineer who stopped replying, and an escalation to the engineer's manager just to get an update. The problem is clearly real for them. The solution they don't want is another place to check.

What we took from it: they're right. Our own data says 90% of people already use two or more tools, and switching between them is a frustration in itself. A task tool that asks you to come to it, open another tab and keep it updated is adding to the problem. That's why Progask works through the AI chat people already use, so planning, and the changes to a plan, happen where they're already working.

"My system already works"

The second team lead rated the idea 3 out of 5, and explained that they colour-code their tasks, so stagnant ones are easy to see.

This person also told the only story in our survey where a slip was caught early, from the board itself: a task whose status stayed the same while the others moved on. Their homemade system does exactly what we want Progask to do.

But asked what they'd change about how they manage tasks today, they named updating the status of many tasks by hand. And their top-ranked frustration? Manually updating and moving cards.

So the system works, and the upkeep is the cost. They've built an early-warning system, and they pay for it by updating it by hand.

What we took from it: don't try to replace a system someone is proud of. Take over the chore that keeps it running. The value we need to prove isn't "a better board". It's "the same clarity, without the manual updates".

They weren't the only satisfied ones

To be fair to the data, contentment wasn't limited to the two no's. Asked what they'd change, one respondent who said yes to early access said nothing yet, since everything seemed fine as it was, and another couldn't think of anything.

That's a useful reality check. Many people have a setup that's good enough, and "good enough" is the strongest competitor any new tool has. Progask has to save people time from the first week, or they'll go back to what already works.

Why we're sharing this

A launch series that only quotes enthusiasts isn't much use to anyone. The objections above shaped real decisions: meet people inside the tools they use, leave decisions and control with people, and focus on removing upkeep rather than adding features.

If you're one of the people who'd say "no thanks, my setup works", we'd like to hear from you too.


About the survey. In October 2026 we asked 10 people who work with at least two others how they manage tasks. Respondents came from a paid research panel (Opionate) and answered 17 questions, including a short story about the last task that slipped. Ten people is a small group, so read these numbers as early signals, not industry statistics. We plan to run a larger round.

Progask is free during the beta.

Start this week free