Removing an obsolete field can simplify a database or silently sever the work built around it.
Database owners need cleaner schemas, while contributors need views, forms, relations, and workflows to keep working.
Who you’d be doing this for
“I found six fields nobody uses, but one of them might still power a form someone relies on.”
Stuart Schmidt · Knowledge Manager
Maintains a shared operational database used by product, operations, and support colleagues.
What is at stake
Knowledge managers leave obsolete fields in live databases because hidden dependencies make removal risky. You must weigh schema simplicity against the continuity of views, forms, relations, and workflows.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- schema simplicity vs workflow continuity
- helpful warnings vs database complexity
- dependency accuracy vs query cost
- first-version speed vs reusable abstractions
Why Notion
The database block must let knowledge workers evolve operational records without becoming database administrators.
Written with these in mind
Not your kind of problem? 24 more at Notion, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.