Maybe we don’t have a productivity problem. Maybe we have a context problem.
I used to think being organized was mostly about having the right system. A good board, clear priorities, a calendar that actually reflects reality, tasks written down instead of kept somewhere in your head, all the things that are supposed to make work feel manageable. And to some extent, that’s true. But the more I’ve looked at how people actually work, especially freelancers, solopreneurs and people juggling several projects or clients at once, the more I’ve started wondering whether we’re trying to solve the wrong part of the problem. Because most work doesn’t begin as a task. It begins as an email from a client, a comment in a document, something mentioned during a call, a Slack message sent late in the afternoon, a WhatsApp message you tell yourself you’ll remember later, a file shared without much explanation or a tiny request added almost casually at the end of another conversation. Somewhere between all of those things and the actual work, someone has to make sense of it, and usually that someone is you.
We talk a lot about productivity, task management and prioritization, but most productivity tools start at a point where the messy part has already happened. You open the tool and create a task, give it a title, add a due date, assign it to a project and maybe decide how important it is. Everything looks nice and structured. But before you can do any of that, you first have to understand what the task actually is. You have to read the message, work out whether the client is asking for a change or simply sharing feedback, remember which version they are referring to, connect it with something discussed during a meeting two days earlier, find the relevant file and decide whether “sometime this week” actually means Thursday because they have a presentation on Friday. Only then can you create the neat little task. That process may take thirty seconds or ten minutes, but it happens over and over again throughout the day, and I think we underestimate how tiring it is. Not because any individual step is particularly difficult, but because it constantly forces you to switch context and keep small pieces of information active in your head.
This is also why someone can have a beautifully organized project management system and still feel overwhelmed. The system itself may be perfectly fine. The problem is that it only contains the things that successfully made it into the system in the first place. The email you forgot to turn into a task isn’t there. The small thing a client mentioned during a call isn’t there. The feedback sitting in a Google Doc isn’t there. The voice message you planned to listen to again isn’t there. So when you open your task manager and see twelve tasks, you don’t necessarily have twelve tasks. You have twelve tasks that were captured. Everything else still lives in the surrounding communication, in files, in conversations and sometimes just in your memory. That distinction feels subtle until something important gets missed, and then suddenly it becomes the entire problem.
There’s also a strange point where a productivity setup itself becomes another thing you have to manage. You might use Gmail for client communication, Slack for one project, WhatsApp for another, Google Drive for files, Notion for notes, a calendar for meetings and something like Trello, Asana or ClickUp for tasks. Every tool makes sense individually, but together they create a new job: keeping everything synchronized in your head. Where was that feedback? Did I already add this to the board? Was the new deadline mentioned in email or during the call? Which file is the latest one? Did I reply to that client or only think about replying? At some point the problem stops being “How do I organize my tasks?” and becomes “How do I make sure nothing disappears between all the places where work happens?” That feels like a much more interesting problem because it isn’t really about productivity in the traditional sense. It is about maintaining context.
Client communication makes this particularly obvious because clients rarely communicate in neat task-manager language. They don’t usually write: “Task: Update landing page copy. Deadline: Thursday. Priority: High. Project: Website launch.” They write something more like: “Hey! We had another look at the page and I think the headline still feels a little too formal. Could we try something friendlier? Also maybe the second section should mention the new offer. We have a meeting on Friday so it would be amazing if we could see something before then.” For a human being, there is quite a lot of structure hidden inside that message. There is probably a task, maybe two. There is a deadline. There is context. There might even be an implicit priority. But none of that becomes structured work until somebody interprets it. Which means we spend a surprising amount of time manually translating communication into action, and because this translation feels small and happens in little fragments throughout the day, we rarely count it as work.
That has changed the way I think about productivity a little. Maybe the biggest improvement isn’t always helping people complete tasks faster. Maybe it’s reducing the amount of mental effort required to understand what needs attention in the first place. Less remembering, less copying, less searching, less “I know there was something else…” and less opening five different apps just to reconstruct what happened with one client. If you could reduce that layer of invisible administrative thinking, work might feel significantly calmer even if the actual number of tasks stayed exactly the same. The benefit wouldn’t necessarily be that you suddenly complete twice as much work. It might simply be that your brain no longer has to act as the integration layer between every tool you use.
This is also where I find AI more interesting than another productivity chatbot. There’s obviously a lot of AI being added to work tools right now: chat with your workspace, generate a project plan, summarize a document, create tasks from a prompt. All of that can be useful, but I’m more interested in something slightly less spectacular and maybe more practical - AI that quietly helps connect messy communication with structured work. Something that notices that a client message contains an action, recognizes a deadline, understands which project the conversation belongs to, connects a new request with previous context or helps surface something before you forget it exists. Not another place where I have to ask AI what to do, but something helping me notice what already needs to be done. To me, that feels much closer to the real friction in day-to-day client work.
Of course, we might be completely wrong, and that’s exactly what we’re trying to find out. It’s very easy to fall in love with a problem once you’ve spent enough time thinking about it. You start noticing examples everywhere. Every forgotten email becomes evidence, every frustrated freelancer becomes validation and every messy workflow looks like proof that your theory is right. That’s dangerous because there’s a big difference between a problem people recognize and a problem they care enough about to actually change their behavior. So before making too many assumptions, we’re trying to understand how people really manage this today. How does work reach you? What usually gets lost? What do you still copy manually? Which tools genuinely make things easier, and which ones mostly create another place you need to check?
We’re working on a product called Hyzo around some of these ideas, but right now I’m much more interested in whether the problem itself is real than in convincing anyone that we already have the answer. So we put together a short discovery survey for freelancers, solopreneurs and people working across multiple client projects: https://tally.so/r/ODy8q8
And if surveys aren’t your thing, I’d love to hear your answer to just one question here: Where does most of your work come from before it becomes a task? Email, Slack, meetings, WhatsApp, comments in documents, your own notes - or does everything already flow perfectly into one system and this entire theory is nonsense?
The last answer might actually be the most useful one.
The part that landed for me is that most tools start after the messy work is already done. Turning a vague client message into a real task is the actual job, and it is pure context stitching, not prioritization. I have the same pattern when shipping software. The board looks clean while the inbox, call notes, and half remembered decisions are where the fatigue lives. A useful system would capture that raw signal first, with the source attached, and only force the neat task shape after the meaning is settled.
Sublime perspective. Context overrides raw execution every single time. True leverage belongs to those who control the signal architecture. 👑🛡️
This is a much better way to frame the productivity conversation. A lot of what looks like procrastination or lack of focus is really the cost of constantly rebuilding context—switching between Slack, email, meetings, docs, tickets, and dozens of browser tabs just to remember what we were trying to accomplish in the first place. We keep adding productivity tools, but every new tool can become another place where context gets fragmented. The real breakthrough may not be helping people work faster, but helping them preserve context: what was decided, why it was decided, what changed, and what needs attention next. Reduce the cognitive cost of reconstructing that story, and productivity becomes a natural outcome rather than something we have to constantly optimize for.
mine mostly arrives mid-thread, as a reply to something already in motion. the email vs slack split never predicted anything for me though. what predicted it was whether a thing showed up self-contained or as a fragment that only makes sense against an earlier conversation.
self-contained survives bad capture. fragments get lost with good capture, because you save the message and the part you actually needed was why it mattered.
if it's useful for the survey: ask people to open something they saved two weeks ago and say whether they still know why they kept it. the ones they can't are usually the mid-thread ones.
That’s a really good distinction: self-contained vs. mid-thread feels much more useful than thinking in terms of channels. And I love the “open something you saved two weeks ago” test. It gets straight to whether the context actually survived, not just whether the message was captured. I’m definitely stealing that for our discovery questions :)
This makes me think the real problem is not just capturing tasks, but preserving the context behind them. A task can tell you what to do, but not always why it matters, what was already tried, or what constraints came from earlier conversations. That context is often what gets lost between tools.
Yes, exactly. Sometimes the task itself is the easy part - it’s the little bits around it that matter most. Why the client asked for it, what changed, what was already discussed, what not to repeat. Once that context gets scattered, even a simple task can become surprisingly hard to pick up again.
Exactly. That “why” is often the first thing that disappears, even though it can be the most important part when someone picks the work up later.
Most of my work already starts as a task. The gap appears at the other end: the work gets finished in Claude Code, but the result never flows back, so the board has context when the task is assigned and loses the truth when the task is completed. I have started thinking of task capture and task reconciliation as the same problem in opposite directions. Are you looking only at the intake side, or also at the return path after the work happens?
What I keep coming back to is that most task managers assume the task is already the source of truth. But in reality, the source of truth is often the conversation that created it.
The interesting question for me is: how much of that original context do we actually need to preserve for a task to still make sense two weeks later?
Curious how others here think about that.
The framing I'd add is that context isn't one thing — there's the context you can write down and the context you can't. Tool-switching cost is the visible half and the one everyone measures, but the expensive part is usually reconstructing why you made a decision three weeks ago. That never lived in any tool, so no amount of consolidation recovers it.
Which one are you pointing at? A tool can hold the first kind. I'm less sure anything holds the second.
That’s a really useful distinction. I think we’re mostly pointing at the first kind - context that exists somewhere, but gets separated from the task as work moves between tools. But the second kind is probably the harder and more interesting problem. Maybe the goal isn’t to “capture” all of it, but to preserve enough of the trail around a decision that reconstructing the why later becomes much easier.
Do you find that missing context is usually genuinely unwritten, or was it there at some point and just became impossible to find?
Your point about preserving context rather than just capturing tasks really clicked with me. I have a practical solution I’d love to show you and potentially prototype around this problem.
What’s the best way to reach you?
Thanks! Feel free to DM me here on IH :)
The distinction between captured tasks and work still stuck in communication is spot on. One test I'd add: save the source message and one sentence about why it matters when you create a task. If that takes more than 20 seconds, capturing the task is probably the bottleneck. That's part of why I built DictaFlow: saying the task and its context is often faster than turning a messy Slack thread into neat fields, and you won't have to reconstruct the reason two days later.
I really like the 20-second test. It makes me wonder if the goal shouldn’t be “capture all context automatically”, but rather make adding the missing bit of context almost effortless. If you had to pick one, what usually matters more in practice: preserving the original source, or adding that one sentence about why it matters?
The context problem framing feels more useful than the usual “use a better task manager” advice. A task can be perfectly organized and still be wrong or incomplete if the context that produced it is scattered across five different places. The interesting product question is whether Hyzo can reliably reconstruct that context without creating another inbox people have to manage.
Yes, I think that’s exactly the risk. If a tool is supposed to reduce mental overhead, but ends up becoming another place to check and maintain, it probably makes the problem worse, not better. That’s the line I keep thinking about too: what would make something like this feel quietly helpful rather than like another inbox in disguise?
That’s the part I’d be most interested in understanding better. I’d be happy to continue the conversation by email — what’s the best email to reach you on?
Happy to keep it here for now - would be curious to hear your thoughts on that question.
That makes sense. I think the key question is whether Hyzo can make the context available at the moment it’s needed without asking the user to actively maintain another system.