# 'Time saved' is the wrong way to talk about AI > Source: > Published: 2026-07-22 16:47:56+00:00 # 'Time saved' is the wrong way to talk about AI "Where did the time go?" It is a familiar question at the end of a dizzyingly busy day. Lately, there are many more opportunities to ask it. One task turns into the next before you have much time to think about the last one. By that measure, it was a productive day. But was it? Because while it is true that AI can compress what used to be hours of work into minutes, celebrating that alone is what should really be questioned. Saving minutes is not the same as spending them well — it is important to distinguish the two if you want to actually create anything of value. Most people would agree that saving time is a worthwhile goal. It is also one of the easiest ways to evaluate what AI can do. Of course, there is another kind of time investment happening too. I recently dubbed [learning how to apply AI to our first job](/blog/5-insights-from-product-leaders-on-ai-and-the-future-of-pm) as our "second job." But even while we are making that investment, we still often judge AI by (1) whether we used it and (2) whether it saved us time. If a task that once took an hour now takes 10 minutes, we naturally conclude that we saved 50 minutes. But that calculation only tells us how long the task took. It says nothing about whether those 50 minutes led to a better decision or outcome. At Aha! we have always believed there is a difference between acting quickly and acting with purpose. That belief is built into the first principle of [The Responsive Method](/company/the-responsive-method): be goal-first. Know where you are headed, so speed serves the goal instead of replacing it. But even [being goal-first](/blog/new-hire-first-year-aha) does not answer every question. It still assumes that the work reflects the thinking behind it. AI makes that assumption much less reliable. A strategy document that used to take days to write almost certainly reflected days of [thinking and refining](/blog/strategic-thinking-vs-strategic-planning). Today, we can produce that same document in minutes. We should not assume the relationship between the two is the same as it once was. Finishing something used to be evidence that thinking had happened. Today, it is mostly evidence that something exists. OK, what should we do with that? In some ways, this is the simple part. As I wrote earlier, saving minutes is not the same as spending them well. And AI sometimes does not save time at all — you spend longer prompting, revising, and starting over than you would have on your own. But whether AI saved you an hour or cost you one, you still have to decide if the time was well spent. Here is what I would ask: ## What do I understand now that I did not before? Look beyond what AI helped you produce. Ask what you know now that you did not know when you started. Your understanding of the problem should be deeper than it was before. The work you do next is based on that [deeper understanding](/blog/how-well-do-you-really-know-your-customers). You are no longer measuring the work by what AI produced, but by what you learned. ## Which decision improved because of this? Think about the decision that prompted you to do the work in the first place. You were not researching customers or drafting positioning simply to have another document. You were [trying to decide](/blog/hey-product-manager-do-you-know-why-you-are-building-that-feature) what to do next. Ask yourself whether that decision is stronger because of the time you spent. ## What value did the work create? Think about who benefited because you invested the time. A [prototype built with an AI assistant](/roadmaps/prototypes) gives teammates something concrete to improve instead of imagining it. And it gives the business a chance to learn [before making a larger investment](/blog/how-to-avoid-building-software-that-no-one-uses). Look for a strong connection between the work and its [real impact](/blog/the-one-metric-every-product-team-should-track). ## Did I use the time with intention? Decide what the time is for before you begin. If AI gives you an extra hour, be deliberate about where it goes. If it takes an extra hour, be equally deliberate about whether it was worth it. You might eventually develop a [better instinct](/blog/simplicity-vs-complexity-in-product-development) for where another hour will make a meaningful difference. Every hour deserves the same scrutiny — whether AI shortened it or stretched it. The next time you reach for AI, be just as thoughtful about how you evaluate the time as how you spend it. Look beyond how much time the work took and consider what that time ultimately produced. The answer will not always be obvious, and it will not always be measured in minutes. But you can be confident that you spent the time well because it left you understanding more, deciding better, and creating something that benefited someone else. **Use AI with the full context of your product work — ****Elle is embedded throughout Aha! software****.**