Invisible Product Decisions: When the Tool Built to Help You Remember Punishes You for Forgetting

I started using Notes App for three reasons: I like writing but I don't like posting, I have a short memory, and I value privacy and security.

I like having a place where I can simply write. Ideas, thoughts, things I want to keep, things I might want to publish one day. Without having to think about who will read them, who will like them, or who will comment. I write and save. And there is a certain irony here: I use a tool to store the things my memory cannot.

Recently, I forgot the password to a locked note. The result? I lost the content forever. There is no way to recover the password. Contacting is useless.

Technically, the system is robust and impressive. But as a Product Manager, I don't see this as a technical failure. I see it as a strategic product decision.

Apple deliberately prioritised a strong privacy narrative: "Not even we can access your data," at the expense of recoverability. Between giving me a safety net — a "recover password" option — and protecting the brand's reputation for absolute privacy, the brand won.

Between UX and reputation, reputation won.

And I am not necessarily saying this is the wrong decision. I am saying it is a decision. And that is exactly what interests me as a Product Manager.

Because we often look at a product and think only about what it allows us to do. But some of the most important decisions are hidden in what the product deliberately does not allow us to do.

Apple could create a recovery mechanism. There could be some way of proving that I am the owner of the account, the device, or the information and recovering access to the note. But the moment there is a way to recover something, another question appears: if there is a way to recover it, is there also a way for someone, under certain circumstances, to exploit that mechanism?

And this is where a seemingly simple UX decision stops being just UX. It becomes security. It becomes privacy. It becomes reputation. It becomes brand positioning.

Forgetting is not an edge case. It is a statistically expected human behaviour. We forget passwords, PINs, appointments, names, where we put things, and even what we wrote. That is precisely why we create products to compensate for our human limitations. Calendars exist because we forget appointments. Alarms exist because we forget schedules. Password managers exist because we cannot memorise dozens of different passwords. And Notes exists, in part, because we cannot keep everything in our heads.

So there is a certain irony when a tool created to help us remember requires us to be perfect at precisely the thing humans are not perfect at: remembering.

By treating forgetting as a serious user failure instead of a predictable scenario, the product reveals its true priority.

Security that requires human perfection is not user-centric. It is brand-centric.

But here is where the discussion becomes more interesting. Are security and tolerance for human error necessarily on opposite sides?

It is easy to say that there should be a recovery option. But recovery comes with a cost. The easier it is to recover something, the less absolute the protection may become. The more mechanisms we create to help the user, the more possibilities there may be for someone to exploit those mechanisms.

So we have a conflict. The user says: "Help me recover what is mine." The security team asks: "But how do we know it is really you?" The brand asks: "What if this recovery mechanism is exploited and destroys the trust we have built?"

And the product sits in the middle.

That is why I believe some of the most critical product decisions are rarely just technical. They involve risk, reputation, and positioning.

When everything works, almost every product looks user-centric. The real test happens when something goes wrong. When we forget a password, lose a phone, change a number, make a payment that does not appear, delete something by mistake, or simply can no longer do what the product expected us to do.

That is when we discover who the product is really protecting.

And perhaps that is why, as Product Managers, we should ask more questions that start with "what if?" What if the user forgets? What if they lose the device? What if they misunderstand? What if they click the wrong button? What if they no longer remember what they created?

Not because we should build a solution for every possible mistake, but because every "what if?" forces us to reveal a priority.

In the case of Apple Notes, that priority seems quite clear. Between giving me a safety net and maintaining an architecture where even Apple cannot recover the content, the second option won.

Why?

Because the cost of a headline saying "Apple Can Access Your Notes" is, for them, greater than the cost of the silent frustration of millions of users like me.

And here is perhaps the most interesting part. Apple is not only protecting my data. It is protecting a promise. Privacy has become part of the product, but also part of the brand. "Not even we can access it" is much more than a technical feature. It is a narrative of trust.

So allowing easy recovery could solve a UX problem, but it could also weaken the promise that supports part of the brand's positioning.

Not every product decision is made to maximise user convenience. Some are made to protect the brand promise.

And the user normally does not see that decision.

I see a locked note. I see a field where I enter the password. I see that I cannot get in. I do not see the discussions between Product, Engineering, Security, Legal, Privacy and Brand. I do not see the risks that were considered. I do not see the scenarios that led to that decision.

I see only one thing: I forgot my password and lost my note.

That is why some product decisions look small to the person using the product but are enormous to the people building it.

A simple decision like "we will not allow this password to be recovered" carries an entire philosophy behind it. It tells us what the company considers more important to protect.

And this experience left me with a question that I find more interesting than asking whether Apple should allow password recovery:

How do we balance robust security, brand narrative and reputation, and tolerance for inevitable human error?

Because human error will happen. The user will forget. They will click the wrong thing. They will misunderstand. They will lose something. They will change something. They will do exactly what the product ideally should have anticipated.

The question is: how far should we go to protect users from the consequences of their own mistakes? And, at the same time, how far can we go without compromising what we are trying to protect?

Perhaps the challenge of a good product is not to eliminate every risk. Perhaps it is to decide which risks we are willing to accept.

I lost a note.

Apple protected a promise.

And that is precisely where we realise that some of the most important product decisions are invisible to the user — until the day something goes wrong.