This is a factorization problem , like so many in engineering. Putting unrelated things on the same board is expensive, because you have to constantly compare

This is a factorization problem , like so many in engineering. Putting unrelated things on the same board is expensive, because you have to constantly compare those apples and oranges to prioritize, estimate multi-ticket release dates, and so on. Splitting things to different boards can also be expensive, because you have to prioritize resources at a higher level across boards. And if you break up dependencies, suddenly you have to flip between boards to answer questions. It sounds like somebody was sick of the drawbacks in the second paragraph. But maybe the issue isn't that you need a monolithic board, it's that you need to make sure the boards are split in the right way.