Memory Problem vs Product Problem: What It Means

This article explains the phrase “we didn’t have a product problem, we had a memory problem,” which describes situations where a product or service fails not because of its design or features, but because users (or the organization) simply forgot how to use it, why it exists, or what it was supposed to do. You’ll learn the origin of the idea, how to recognize it in your own work, and practical steps to fix it.

Formula

The calculator estimates how many users have “forgotten” the product based on a monthly churn rate, assuming that churn is driven by memory loss rather than dissatisfaction. The formula is:

Users who forgot = Active users × (1 − (1 − churn rate)^(months / 12))

• Active users (u) – the current number of active users, in count.
• Monthly churn rate (r) – the percentage of users who stop using the product each month, expressed as a decimal (e.g., 5% = 0.05).
• Time since launch (t) – the number of months the product has been available, in months.

The result is an estimate of how many users have stopped using the product over time, assuming churn is purely due to forgetting. It is not a precise measurement, but it helps quantify the scale of a “memory problem.”

Worked Example

Using the default values: 10,000 active users, 5% monthly churn, 24 months since launch.

1. Convert churn to a decimal: 5% = 0.05.
2. Compute the retention factor per year: (1 − 0.05)^(24/12) = (0.95)^2 = 0.9025.
3. Subtract from 1: 1 − 0.9025 = 0.0975.
4. Multiply by active users: 10,000 × 0.0975 = 975.

The calculator shows 975 users (rounded to 0 decimals). This means that if churn were entirely due to forgetting, roughly 975 of the original 10,000 users would have stopped using the product over two years.

Background: Where the Phrase Comes From

The phrase is commonly used in business and product management to describe a failure that is not about the product’s quality, but about the user’s ability to remember it. It echoes the famous marketing adage “out of sight, out of mind.” In practice, it refers to a situation where a product is objectively good—it works, meets needs, and is easy to use—but users stop using it because they forget to return, forget it exists, or forget how to use it after a period of absence.

The concept gained traction in the software industry, where subscription apps and SaaS products often see high churn rates not because of bugs but because users simply don’t come back. It also appears in consumer goods, like a gym membership that people forget to use, or a productivity app that gets buried on a phone’s home screen.

How It Works: The Psychology of Forgetting

Forgetting is a natural cognitive process. The Ebbinghaus forgetting curve, first described in the 19th century, shows that memory decays rapidly without reinforcement. In product terms, this means that if a user doesn’t see a benefit or reminder within a short time after first use, they are likely to forget the product entirely.

This is why onboarding is critical. A user who tries a product once and doesn’t understand its value is more likely to forget it. Conversely, a product that creates a habit—like a daily notification or a streak counter—keeps itself in the user’s memory.

In organizations, “memory problem” can also refer to institutional memory. A team might have built a great internal tool, but after a key employee leaves, no one remembers how to use it, so it falls into disuse. The product isn’t broken; the knowledge is lost.

How to Tell If You Have a Memory Problem

Before you can fix a memory problem, you need to diagnose it. Here are signs that your issue is memory-related rather than product-related:

• Users who do use the product rate it highly (e.g., 4+ stars) but churn is still high.
• Users say “I forgot I had this” or “I forgot how to use it” in exit surveys.
• Usage drops after a period of inactivity, even though the product hasn’t changed.
• Support tickets are mostly “How do I…?” questions that are answered in the FAQ.
• Your team has no documentation, and only one person knows how to operate a critical system.

If these sound familiar, you likely have a memory problem, not a product problem.

How to Fix a Memory Problem

Once you’ve identified a memory problem, you can take steps to address it. The goal is to make the product or information memorable and easy to recall.

1. Improve onboarding. Make the first experience memorable. Show value immediately and teach the core actions in the first session.
2. Use reminders and notifications. Send timely, relevant nudges that bring users back. Be careful not to spam.
3. Create habits. Encourage regular use through streaks, daily goals, or recurring events.
4. Document everything. For internal tools, write clear guides, record videos, and store them where everyone can find them.
5. Re-engage dormant users. Send a “We miss you” email with a simple call-to-action. Sometimes a single reminder is enough.
6. Simplify re-entry. Make it easy to pick up where they left off. Save progress, remember preferences, and reduce login friction.

Common Mistakes and Misconceptions

A common misconception is that a memory problem is the same as a marketing problem. Marketing gets attention, but memory is about retention. You can have great marketing and still lose users if they forget after the campaign ends.

Another mistake is to assume that all churn is memory-related. If users leave because the product is buggy, slow, or doesn’t meet their needs, that’s a product problem. Trying to fix a product problem with reminders will fail. So it’s essential to diagnose correctly.

Also, don’t confuse “memory problem” with “user error.” If users forget how to use a feature because the interface is confusing, that’s a design problem, not a memory problem. The distinction matters because the fixes are different.

Comparisons: Memory vs. Product vs. Marketing

To clarify, here’s a quick comparison of the three types of problems:

• Product problem: The product fails to solve the user’s problem. Fix by improving features, performance, or usability.
• Marketing problem: People don’t know the product exists. Fix by increasing visibility and awareness.
• Memory problem: People know the product exists but forget to use it. Fix by reinforcing memory and habit.

These can overlap. A product might have all three issues, but the fix for each is different. The phrase “we didn’t have a product problem, we had a memory problem” is a reminder to look beyond the product itself when diagnosing churn.

Costs and Limitations

Fixing a memory problem can be cheaper than fixing a product problem, because it often involves changes to communication and UX rather than core engineering. However, it’s not free. Reminders, onboarding improvements, and documentation require time and resources.

The calculator above is a rough estimate. It assumes a constant churn rate and that all churn is due to forgetting, which is rarely true. In reality, churn is a mix of memory, product, and external factors. Use the estimate as a starting point, not a precise metric.

Also, be aware that over-reminding can annoy users and lead to uninstalls or complaints. The goal is to be helpful, not nagging.

Frequently Asked Questions

What is a memory problem in business? A memory problem occurs when users or employees forget about a product, how to use it, or why it matters, leading to disuse even though the product itself is functional.

How do I know if my churn is due to memory or product issues? Conduct exit surveys, analyze usage patterns, and look at support tickets. If users who stay are satisfied and the main reason for leaving is “I forgot,” it’s likely a memory problem.

Can a good product still have a memory problem? Yes. Even excellent products can be forgotten if they don’t become a habit or if users don’t see a reminder. This is common with utility apps that are used infrequently.

What’s the difference between a memory problem and a marketing problem? Marketing gets attention; memory keeps it. A marketing problem means people don’t know you exist. A memory problem means they know but forget to return.

How long does it take to fix a memory problem? It depends on the product and the fix. Simple reminders can show results in weeks, while habit-building may take months. The key is consistent reinforcement.

Is the calculator accurate for my product? The calculator gives a rough estimate based on a constant churn rate. For a precise number, you’d need to track user cohorts and distinguish between memory-related and other churn.

Related

• Delayed VR Accessory: What to Check Before Buying
• Check Message Requests Messenger: How to Find Them
• Motion Tracking Sensor Buying Guide

in t | Time since launch | months | 24 | 0 | 1200
in u | Active users | count | 10000 | 0 | 1000000000
in r | Monthly churn rate | % | 5 | 0 | 100
out m | Users who forgot (est.) | count | u * (1 - pow(0.95, t/12)) | 0