...
Before you start consider:
who Who is your audience? are you creating a liveboard for yourself, your team, or for a presentation? understand your audience’s goals and decisions that need to be made
your Your flow - it is typically best to start with high level KPIs or metrics that speak to the goals of your discussion and then dive into supporting detail as necessary
make Make it actionable - this starts with know your business questions, goals, and KPIs. Ensure your arguments are supported clearly and concisely.
...
Less is More - not only can too many visualizations be overwhelming for your audience, it can be overwhelming for load times and costly to compute. Focus on critical information and use explore or drill down functionality to explore details. 10 to 15 answers is a good high-range target per tab.
Avoid small visualization clusters - this can be overwhelming for an audience to consume and can increase load time as more answers are querying simultaneously on your liveboard.
Avoid wide tabular charts - 5 to 8 columns is a good range for charts and pivot tables. Less is more here again as you add more columns, your metrics become less valuable. More columns also require more loading time and can require intra-scrolling within the answer.
Avoid massive date ranges - keep your searches recent to load faster. If you need to do a longer historical comparison, consider breaking your time buckets into larger chunks (e.g. if you’re doing a 3 year comparison, consider quarterly time buckets for comparison rather than months).
Use your tabs - if there’s just too much to share, utilize tab functionality to organize your data story, reduce load time, and increase focus for your audience(s).
Use liveboard filters - setting filters on your liveboard is a great way to reduce querying time and focus your liveboard on the most pertinent information. Default time filters are a great way to enhance loading time for your boards.
Strategically use column summaries - when including a table in your liveboard, consider whether or not column summaries are necessary for that answer. If they are not, it’s best to turn them off since it will increase querying time to calculate the summaries in addition to the rest of the content in the answer. If they are, consider what columns you actually need summaries for and, instead of turning summaries on for the entire table, select the necessary columns and turn on individual summaries (in the answer - edit chart configuration > configure > under ‘visible column’ click on the desired value > summary > select ‘display summary’)
For more details, check out this ThoughSpot community post.
...