Most teams we talked to before building Rowlark had the same setup: a spreadsheet for the real plan, a board for daily work and a slide for the status meeting. Each one was correct on the day it was made.
Copies drift
The trouble with three copies is that they disagree within a week. Someone moves a card but not the row. Someone updates the date in the sheet but not on the slide. The status meeting turns into a reconciliation meeting.
We decided early that Rowlark would have exactly one copy of the work. A view is only a way of looking at rows: a filter, a grouping, a sort and a layout.
What a view is allowed to change
A view can hide columns, group rows and order them. It cannot hold data of its own. When you drag a card to another column on the board, you are editing the status cell of a row. When you stretch a bar on the timeline, you are editing two date cells.
That rule made some features harder to build. A board column that exists only on the board, for example, is not possible. We think the trade is worth it, because every person on the project sees the same answer.
What we learned from early teams
Teams that moved to one table stopped asking for status in chat. The answer was already in the view they used. The weekly meeting got shorter, and the people closest to the work stopped spending Friday afternoon updating slides.
If you are moving from several tools, start with the table. Import the sheet everyone trusts, then add the board and timeline as views on top. You can bring the rest over later.


