Edition no.15. May 12th, 2023

Tana is the Everything OS.

In Tana, you can create a system to manage pretty much anything.

Usually, apps are dedicated to executing a specific function very well, not a wide range of functions, which makes Tana an interesting phenomenon.

With this in mind, I'm writing a series of 4 (or more) letters dedicated to studying and analyzing Tana.

This series comes in preparation for the launch of my Tana Course on learning how to master Tana, called Tana Decoded. (More on this later.)

This edition (15) of The Fis Letter marks the beginning of this series.

In the next few editions, I will explore Tana through the lens of different topics, seeking to understand WHY Tana is so flexible and, at the same time, so powerful.

And, of course, there's nothing more appropriate than to start off with:

• Knowledge Management

Let's make something clear from the beginning.

Knowledge is the fuel of the modern economy.

Everything can be represented by knowledge.

Knowledge represents everything.

This means that Knowledge Management can be used to manage anything.

This is why Tana can manage pretty much anything.

In the Knowledge Economy, a tool to handle Knowledge is a must.

In my opinion, Tana is the best option to handle knowledge.

Join me to find out why:

P.S. Disclaimer. Even though Tana is the most powerful tool to handle knowledge, this DOES NOT mean you should change tools to Tana. That's not my goal here. Other tools are still massively powerful and can handle knowledge really well.

My goal is to talk about a tool that is revolutionizing the PKM space.

💬 4 Quotes

Quote 1

How about we start with a definition of Knowledge Management?

Let me reformat it so it's easier for you to see:

1. Creating

2. Storing and Retrieving

3. Transferring

4. Applying

These are the 4 pillars of knowledge management.

A brilliant tool will handle these processes brilliantly.

Let's take a look at some of these.

Quote 2

The First Law of Thermodynamics states that Energy can neither be created nor destroyed - only converted from one form of energy to another.

Knowledge is a form of Energy.

Creating knowledge is actually converting knowledge.

You convert knowledge from the outside to the inside.

Another name for this is capturing.

You convert (capture) knowledge from the outside, the life you're already living, into the inside, a closed universe where your knowledge exists.

Tana's iOS Capture app is world-class at this.

You can start typing, speaking, photographing, filming, and scanning. And the knowledge will be safely stored in your Tana workspace.

(Ready to be processed with the power of AI)

Quote 3

Yes, I love this quote.

It represents the core concept of knowledge management.

• Retrieval

If you can't retrieve something, it's basically useless.

Tana is again world-class in retrieval.

I suffered a lot from this when I started using Roam Research. (Please note this is due to both Roam's data structure and my lack of experience. If I were to do it again, I would solve this problem in Roam. Tana just makes it much easier.)

Tana has a perfect combination of Supertags and Live Queries that make it extremely easy to find anything that you create (if you add a Supertag to it!)

For example, items that are captured with a Supertag can be found in the respective Live Queries.

Quotes will be found in the Quotes Live Query.

Threads will be found in the Threads Live Query.

Quote 4

You can only transfer or apply knowledge by finding it.

And Einstein put it quite beautifully… But modern-day intelligence is not limited to finding information.

Modern-day intelligence is information that finds you when and where you need it.

Yes, finding information is great.

Information finding you is AMAZING.

This is possible in Tana!

You can set up Live Queries inside the places where you will use that information, so that information finds you whenever you want to find it.

Inside a Project page, you can surface Project Notes from any location in your workspace, given they are linked to the project.

This allows you to always have knowledge close by.

So you can focus on what matters.

📄 3 Notes

1. Basic Knowledge Representations

Now let's dive into how knowledge is represented.

Knowledge Management depends on Knowledge Representation.

Knowledge initially resides in one person’s mind and is restructured or resurfaced in another person’s mind.

Knowledge Representations are the different paths through which knowledge can be restructured.

According to Markman, 2013, there are 3 basic ways to represent knowledge:

1. Spatial Models

2. Feature Models

3. Network Models

Spatial Models of representation are those which rely on the visual or spatial representation of information, where all of the encoded knowledge is visually accessible and within reach.

This makes Spatial Models effective for small amounts of knowledge, but not as suited for larger amounts of knowledge, since it depends solely on space to encode information, which is not enough for either large amounts of depth (detail) or breadth (reach).

Feature Models of representation use symbols to represent different types of information. Features act much like a sign in Semiotics theory.

They communicate a meaning that is not the sign (feature) itself, to an interpreter.

dFeatures may be visual, conceptual, and mathematical.

Network Models of representation use a graph structure of nodes and links to convey knowledge.

The critical aspects for representing networks are the structure of the networks (nodes and links) and the labels on the nodes and links.

A very important aspect of Network Models is Semantic Networks, which represent specific relations between concepts, as well as the propagation of relations.

These 3 models are fundamental to how Tana works.

Spatial representation is present in every tool that uses a screen. This is not a big deal.

What Tana does very well is to put BOTH Features and Networks as core to the product.

Features are best represented by fields, which are features belonging to each object (an object is an instance of a Supertag.)

And everything in Tana works inside a Network.

It's actually funny because Tana creates the Network using fields (features). This is what allows Tana to have Semantic Networks, with specific relations that can propagate through the graph.

In Summary, Knowledge is very well represented in Tana.

2. Knowledge Visualization

For any representation of knowledge to be consumed and understood by a human, it must first be visualized.

There is a fascinating framework for Knowledge Visualization presented in Burkhard, 2005, which expands on this topic of visualizing knowledge.

Burkhard outlines a framework to categorize the transfer and creation of knowledge. (The framework may also be used for the other two processes of storage and retrieval, and application.)

The framework is based on four perspectives that can be considered when creating visual representations:

• Function

• Knowledge Type

• Recipient

• Visualization Type

The questions that guide these perspectives are:

• Why should knowledge be visualized? (aim)

• What type of knowledge needs to be visualized? (content)

• Who is being addressed? (recipient)

• Which is the best method to visualize this knowledge? (medium)

What I like the most about this framework are the functions that Burkhard suggests for why knowledge should be visualized.

These 6 options of Coordination, Attention, Recall, Motivation, Elaboration, and New Insight are very interesting to guide possible use cases of Knowledge Management.

This is not limited to Knowledge Visualization.

Knowledge Management is as much about visualizing as it is about managing.

Rating Tana from 1-10 in these functions:

• Coordination: 7

• Attention: 7

• Recall: 10

• Motivation: 8

• Elaboration: 9 

• New Insight: 9

I won't justify my ratings because this letter is getting too long 😂.

3. Tana has Networks and Hierarchies

Finally, I wanted to finish up with the idea that even though Tana works as a Network, it can easily represent a Hierarchy!

Hierarchies are how folders work.

Tana can emulate folders even though this is not the original data structure in Tana, which is a Network by essence.

Hierarchies (Trees) are a subset of Networks (Graphs); the only thing that changes are some additional constraints.

This means Tana can easily represent a Hierarchy.

You just need to add those constraints. ↓

The Project Supertag I shared before is an example of this:

By adding a Live Query inside a Supertag, I created a hierarchy.

The Live Query inside the Project acts as a folder, and "Notes are living inside that folder".

(With a HUGE difference that Notes can ALSO live in other places.)

Another simpler example:

Here, I made a Live Query that brings all #child nodes that belong to the #parent. This is possible by using a field that connects to the #parent Supertag.

See that every node that is created inside the search is auto-initialized with the Parent already defined.

This Live Query is, by all "positive" means, a folder.

Tana allows you to have the benefits of a hierarchy without the rigidity of an actual hierarchy.

🔗 2 Links

Link 1: How Tana Works, video by me!

This was my first YouTube video! Yay! 😝

I published it a couple of weeks ago but didn't promote it much. 😅

Here, I explain the most important mindsets for beginners to understand Tana and start using it effectively.

Link 2: Levels of PKM, by Tiago Forte

In this short article, Tiago goes through different stages of Knowledge Management.

It's interesting to see how the 4 processes of knowledge management are spread out across these 4 different levels.

There is a clear progression, where some processes (storing) belong to lower, simpler levels, and others (application) belong to more mature levels of knowledge management.

That's it. Thank you for reading!

See you next week, my friend!

Cheers,

Fis