Usually the thing being migrated from.
Trello holds lightweight boards, frequently created by teams outside any central administration and shared more widely than anyone tracked. Our work is consolidating boards into the governed estate, and the access questions that surface on the way.
Trello holds work that started outside the governed estate. Most of our involvement is moving that work into a system where access and reporting are answerable.
What it is
Trello holds lightweight boards, frequently created by teams outside any central administration and shared more widely than anyone tracked.
What it does
Low friction to start
Which is its strength, and is also why it accumulates outside administration.
Sharing that outruns governance
Board access is granted by the person who made it, which is fine until somebody asks who can see it.
Where it fits
L2, platform and migration. It is usually the source rather than the destination. Boards created outside the governed estate are where work and access sit without an owner, which is precisely the pattern the rest of the Stack exists to fix.
What we do with it
Consolidating boards into the estate
Moving work that matters into a governed system, and retiring what does not.
Finding what is out there
Boards nobody administers are the same problem as accounts nobody owns, one level up.
Licensing cleanup after consolidation
Boards billed separately keep billing after the work moves, which a renewal audit catches.
Where it earns its place
An organization consolidating shadow tooling
Boards holding real work outside any access review, found during a migration inventory.
A team that outgrew it
Work that now needs workflow, permissions, and reporting has outgrown a board, and moving it is straightforward.
Questions we get
Should we keep using it?
Licensing
Trello is often billed separately from the main estate and is a common find during a licensing audit. That reconciliation sits with the rest of the estate in licensing and renewals.