ThemeMoney & Finance
CardCard 25 of 66
Questions5 to explore

Improvements

Optimization, automation & upgrades

Improvements is where you track what is not working well enough and what has already been done about it, so the same problems do not get rediscovered from scratch every year.

Every organization has a list of things it knows should be better: a process that takes too long, a tool that does not quite fit, a manual step that could be automated. The issue is rarely that nobody notices these things; it is that the list never gets written down, so it circulates informally and the same frustrations come up in every retrospective.

Keeping a record of improvements serves two purposes. First, it helps prioritize: when you can see the full list, you can make a call about what to tackle and when, rather than chasing whatever was complained about most recently. Second, it creates institutional memory around what has already been tried, including the things that did not work and why.

Automation and upgrades belong here too. When a tool is replaced or a workflow is automated, it is worth capturing the before and after state so the decision can be understood later, and so the organization does not accidentally reintroduce the old way when the person who changed it moves on.

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 friction points

Keep a running list of recurring problems, slow processes, and workarounds that people have accepted as normal but that actually cost time or cause errors.

Improvement log

When something is changed, upgraded, or automated, record what changed, when, who drove it, and what problem it was meant to solve.

What was tried and dropped

Note changes that were attempted but rolled back, and the reason they did not work; this prevents the same failed experiment from being proposed again with enthusiasm.

Questions to explore

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

What are the three most common complaints about how work gets done, and have any of them been the same for more than a year?
When a process is changed or a tool is upgraded, where does that decision get recorded?
Who decides which improvements to prioritize, and how is that decision made?
Are there manual steps that people have quietly automated for themselves but that have never been rolled out more widely?
If a new person took over a function tomorrow, would they be able to tell what had already been tried and what problems remain open?

Things to notice

Improvement lists that grow without anyone having authority to act on them become demoralizing rather than useful.
Undocumented automation is a liability: when the person who built it leaves, the process either breaks silently or reverts to the manual version.
Treating a workaround as a permanent solution is common; the record should distinguish between proper fixes and things that are still waiting to be fixed properly.