Why we built UnaTask
It’s 6 on a Friday and the list is longer than it was on Monday. Here’s the problem we set out to fix, and the week we’re aiming for instead.
The UnaTask team, Building UnaTask. Jun 21, 2026. 5 min read.
It’s 6 on a Friday. The team has done good work all week, you can feel it in how tired everyone is. And yet the list on the board is longer than it was on Monday. Someone asks the question every team asks eventually: where did the time go?
Nobody has a good answer, because the time didn’t go anywhere dramatic. It leaked. Fifteen minutes hunting for the decision buried in a chat thread. A task that lived in one tab while the calendar lived in another. Two people doing the same thing because nobody could see who had it. The work was never the problem. The overhead around the work was.
Picture the smallest version of it. A teammate asks, in chat, “can you get the deck to the client before Thursday?” You say sure. The message scrolls away. Thursday arrives with no deck, not because anyone forgot to care, but because “sure” never became anything a person could see. Multiply that by a team and a month, and you have the quiet way good work goes missing.
We’ve been on teams like that. You probably have too. Not bad teams, good people quietly worn down by the friction of staying organized. We built UnaTask because we wanted that friction to disappear, so the week ends with the list shorter and the team less tired.
What we believe
A few convictions shape everything in the product.
- A list is a wish. A plan has a time on it.
- Focus is something the tools should protect, not something you white knuckle alone.
- A team works best when the work is visible: who has what, and who is buried.
- Fewer apps, fewer tabs, fewer “wait, where did we say that?” moments.
Our mission
Help teams spend their hours on the work that matters, and protect the hours they need to do it.
That’s the whole thing. Everything else serves it. If a feature doesn’t give you back time or attention, it doesn’t belong here. That single test has killed more ideas than it has shipped, and the product is better for it.
Why simple is the hard part
It’s easy to add another field, another view, another setting, and end up with software that needs its own onboarding course. We’d rather keep the surface small and the defaults sensible, so the tool fades into the background and the work comes forward. Simple is not the absence of power. It’s power you don’t have to think about.
In practice that means your tasks and your calendar live in one place, so a plan has a real time on it. It means the work shows up where your team already is, in chat, in the inbox, in a meeting, instead of asking everyone to come to it. And it means the focus you set aside for hard work is treated as real, not as the first thing to get booked over.
We’re early, and honest about it. There’s a lot still to build, and we’re building it in the open, shaped by the teams who use it every day. But the Friday we’re aiming for is clear: the good tired kind, where the week’s work is visible, finished, and didn’t cost more than it was worth. If that sounds like the week you’d rather be having, give it a try, and bring the team whenever you’re ready.