Organizational Memory
Bugs & errors card, MethodKit for Memory & Reminiscence
Card 6 of 66 · MethodKit for Memory & Reminiscence
  • ThemeProduct & Offering
  • CardCard 6 of 66
  • Questions5 to explore
Product & Offering

Bugs & errors

Errors in experiences, products & services

The bugs and errors your team already knows about are part of the product's memory too, and ignoring them in your documentation creates invisible technical debt.

Every product or service accumulates known issues over time: the edge case that reliably breaks the checkout flow, the error message users always call about, the workaround your support team has memorized. When this knowledge lives only in a ticket tracker or in certain people's heads, it creates real risk.

Documenting errors well means more than keeping a bug list. It means capturing the context: what triggers the issue, who it affects, how severe it is, what the current workaround is, and what would need to happen to fix it. That context is often lost when the person who found the bug moves on.

For customer-facing errors especially, there is value in being explicit about what users experience versus what the internal cause is. Customer service teams need to know what to say; product teams need to know what to fix.

What to capture

For this part of the company brain, what is worth writing down and keeping current. The goal is not a complete archive but a living record that new people can read and returning people can trust.

Known issues log

Maintain a shared list of recurring bugs and errors, including when they were first noticed, how often they occur, and the current status (open, workaround in place, fix scheduled, resolved).

Severity & impact notes

For each issue, note who is affected and how badly: a cosmetic glitch is different from a blocker. This helps prioritization and makes the log useful for people who did not discover the issue themselves.

Workarounds & responses

Capture any known workarounds and the language used to communicate issues to customers. Support teams should not have to reinvent these answers each time.

Questions to explore

Use these on your own or in a group. There are no right answers, only better conversations.

  1. Where do known bugs and errors currently get recorded, and who has access to that record?

  2. Are there issues that keep coming up in customer support that are not tracked anywhere as a product problem?

  3. When a bug is resolved, is that resolution captured in a way future team members can learn from?

  4. How do you currently communicate known issues to customers, and is that response consistent?

  5. Are there errors or workarounds that only one or two people know about because they have never been written down?

Things to notice

  • Bug trackers and product memory are not the same thing: a ticket system tracks tasks, but it often loses the broader context (why a bug matters, what was tried, what the workaround is) once a ticket closes.
  • Customer-facing error documentation (what to say, how to apologize, what to promise) is often missing entirely, so each support interaction starts from scratch.
  • Resolved bugs sometimes carry lessons that never get written down, meaning the same root cause gets rediscovered later by a different team.