Whether you're working in files and folders, or in a database like Notion, the problem is the same. You have to figure out where to put data (which folder, which table) before you write it.
In @tana_inc, you start by writing data, then the nodes flow into tables through searches
In @tana_inc, you start by writing data, then the nodes flow into tables through searches
It's not just tables - we can view live search results in different ways: as a list, gallery, board. But here you'll see that I'm searching an entire workspace for a few fields. Fields aren't owned by a table. Many types of node might have the same fields
https://twitter.com/RobertHaisfield/status/1576399579339030528?s=20&t=hXbMdNc8KyEbdoDYivATKA
We have an "End-user(s)" field that we use as metadata for #feature requests, #bug reports, and #frictions. In Notion, those would be three different tables. In Tana, I could easily create a table out of all nodes with a specific end-user, regardless of their tag or location. 
I could also start with a "Related Feature" column and find all observations and requests with that field filled in for a specific feature.
As a product manager, this sort of flexibility is insane - it lets you model your domain and create moldable dashboards you edit in place.
As a product manager, this sort of flexibility is insane - it lets you model your domain and create moldable dashboards you edit in place.
This table comes from a search that picked up multiple nodes in my outline here. You start by writing the data, and the visuals arise from your questions.
This example shows how awesome Tana is for taking and distilling notes from user interviews
This example shows how awesome Tana is for taking and distilling notes from user interviews
https://twitter.com/RobertHaisfield/status/1577091010353516544?s=20&t=uofd12J3Tb33hHpAZWxoZw
• • •
Missing some Tweet in this thread? You can try to
force a refresh
