You can know exactly what matters and still spend your entire day doing something else. Here's why I think our productivity tools miss this problem.The Problem Isn't Always ProductivityI've used task managers, calendars, notes, reminders, and project management tools for years.They all solve useful problems.A task manager can tell me what I need to do.A calendar can tell me when I need to do it.Notes can help me remember something.A project management system can tell me what is happening across a project.But there is a question these systems don't necessarily answer:Did the decisions I made today actually reflect what I said mattered?That question started bothering me.Because there is a strange situation many people experience:You know what you should be doing.You have written it down.You may even have planned the day around it.And yet, by the end of the day, your actual behavior looks completely different.Nothing dramatic happened.You didn't consciously decide to abandon your priorities.Instead, a series of small decisions moved you somewhere else.That's what I started calling decision drift.What Is Decision Drift?Decision drift is the gradual gap between:what you intended to focus onandwhat your decisions actually caused you to focus on.Imagine starting Monday with three intentions:Build the first version of a product feature.Spend an hour talking to potential users.Protect the evening for personal time.By Friday, you might have:answered dozens of Slack messages,attended meetings,fixed minor issues,spent hours checking analytics,responded to email,jumped between five unrelated tasks.You were busy.You may have completed twenty things.But the important work didn't move as much as you expected.That's the interesting part.The problem wasn't necessarily a lack of productivity.The problem was that productivity was directed somewhere else.Why Task Lists Don't Show ThisThis isn't an argument against task managers.Tasks are useful.The problem is that a completed task doesn't tell us why that task was chosen.Suppose I have these five completed tasks:✓ Answered email ✓ Fixed a small UI bug ✓ Joined a meeting ✓ Updated documentation ✓ Researched a new toolA task manager can correctly tell me that I completed five tasks.But imagine my actual intention was:"I need to spend today validating whether customers actually want this product."Now the important question becomes:How did those five decisions relate to that intention?Maybe they were necessary.Maybe they weren't.The task list alone doesn't tell me.This creates an interesting distinction:Execution tracking asks:What did I do?Decision awareness asks:Why did I choose to do it?And another question goes one step further:Did those choices move me toward what I actually cared about?The Hidden Cost of Small DecisionsWe usually think major decisions create major consequences.But daily life is mostly made up of tiny decisions.Should I check this notification?Should I answer this message now?Should I attend this meeting?Should I fix this small issue before continuing?Should I research this new tool?Should I open social media for five minutes?Should I switch tasks?Individually, these decisions don't look important.But hundreds of them accumulate.The problem isn't necessarily that any one decision was terrible.It's that the combined direction can become different from the direction we originally intended.That's why I think productivity needs another layer:not just tracking activity, but noticing direction.Intent Is Not the Same as a TaskOne thing that became particularly interesting to me while working on this problem was the difference between an intent and a task.Consider:"I want to build a company that customers actually want."That's an intention.It might translate into many different actions:interview users,analyze feedback,build a prototype,improve onboarding,send outreach,remove a feature,talk to a potential customer.None of those tasks is the intention.They are decisions made in service of it.That's important because intentions tend to remain relatively stable while tasks constantly change.If we only track tasks, we can lose sight of the thing those tasks were supposed to serve.A Simple Model for Decision DriftI've been thinking about this using four layers:1. IntentWhat actually matters right now?Not everything that matters in life.Just the current context.For example:Validate the product with real users.2. DecisionsWhat am I choosing to do?For example:Send five user interviews.Work on onboarding.Check analytics.3. OutcomesWhat actually happened?Maybe:Sent two interviews.Spent three hours redesigning a button.Checked analytics twelve times.4. PatternDoes this keep happening?This is the layer that interests me most.One distracted afternoon isn't particularly meaningful.But if I repeatedly intend to talk to users and repeatedly spend my available time polishing the product instead, that's a pattern.And patterns are much more useful than isolated failures.From Task History to Decision MemoryThis led me to another idea:Productivity software should eventually remember decisions, not just tasks.A task list remembers:"You planned to do X."A decision memory could eventually tell you:"You repeatedly planned to do X, but when given competing choices, you tended to choose Y."That's a fundamentally different type of information.It's not about judging whether Y was good or bad.It's about making the pattern visible.Because sometimes we don't need another productivity technique.We need to see what we're already doing.What I Started BuildingThis idea eventually became Edorena, a web application I'm currently building.Edorena is an experiment around this problem.Instead of starting with a giant task list, it starts with what matters in a particular context.Then it tries to help people notice the relationship between their intentions, decisions, and patterns over time.I'm still building and testing it, so I don't want to claim that I've solved this problem.I haven't.That's actually why I'm writing about it.I'm interested in whether this is a useful way of thinking about productivity at all.A Practical Experiment You Can Try Without EdorenaYou don't need another application to test the idea.Try this for one week.At the beginning of each day, write down one important intention.Not ten goals.One.For example:"Today I need to make progress on customer discovery."At the end of the day, don't ask:"Was I productive?"Instead ask:What did I actually spend my attention on?Write down the three biggest things.Then ask:Did my decisions move me toward my original intention?Don't score yourself.Don't create a productivity grade.Just observe.After five days, look for repetition.You might discover something interesting.Perhaps meetings are the problem.Perhaps notifications aren't actually the problem, but unclear priorities are.Perhaps you consistently choose easy work when difficult work becomes uncomfortable.Perhaps you spend too much time preparing and not enough time shipping.Or perhaps your original intention wasn't realistic in the first place.The value isn't the answer.The value is seeing the pattern.Productivity Is Becoming More About DirectionWe have become very good at measuring activity.We count:tasks completed,hours worked,meetings attended,messages answered,habits maintained,projects completed.But activity isn't the same as direction.Someone can have an extremely productive day that moves them further away from what matters.That's the part I think deserves more attention.Maybe the next generation of productivity tools won't only ask:"What are you doing?"Maybe they'll also ask:"Is what you're doing still connected to what you said mattered?"I don't know whether that becomes a large software category.I'm still testing the idea myself.But after building and using productivity systems for years, I think there is an interesting gap between managing work and understanding the decisions that shape our work.And that gap may be worth exploring.DisclosureI'm the founder of Edorena, a product mentioned in this article. Edorena is currently in beta, and the product is being developed around the ideas discussed above. The purpose of this article is to explore the concept of decision drift rather than present Edorena as a proven solution