What do you think of the astrolabe dashboard?

The dashboard is not a fancy summary for people who already know the dashboard, but it is a first-level sense of direction for users. It should answer three questions in the shortest space: what is the most important theme of this disk, where is the main tension, and which line should be started from.

If a dashboard is just a small arrangement of tabs, it's not doing its job.

What users want most when they open a page isn't more data, it's priority. What the dashboard should really do is to premise high-weight information, such as the Big Three, the ruler of the life, the center of gravity of the stars, key palaces, or one or two aspects that can best set the tone. It is not a stand-in for the complete text, but a navigation of the text.

The more the abstract layer knows how to make choices, the easier it will be to read the text.

In a mature product structure, every conclusion on the dashboard should be able to find expansion and evidence in the text. In other words, the dashboard does not create a new narrative, but compresses the main line of text to the user in advance. In this way, users will naturally form a reading expectation and know why each subsequent chapter exists.

If the outline and development can match up, the credibility of the product will increase.

When users use the dashboard, the best way is not to focus on each point to understand it one by one, but to first grab the recurring keywords, such as relationships, career, emotions, security, mobility, structural pressure, migration or learning. Once the subject words are stable, the following text reading is no longer a wandering, but a verification and refinement.

Dashboards are most useful when they provide direction for reading from the beginning.