All Collections
Best Practices & Tips
Rich formatting for projects and insights
Rich formatting for projects and insights

Learn why and how to capture your team's attention and give them the info they need

Updated over a week ago

Growth team leaders produce tons of writing in their day-to-day work: tickets describing project work, weekly data updates, and quarterly roadmaps, to name a few.

At Panobi, we know that capturing the attention of your team and stakeholders — and giving them information they can absorb — is crucial to keeping the wheels turning.

This communication challenge is why we offer rich formatting for all projects and insights. Add a new project or insight, and you’ll find that the description field (for projects) or the body field (for insights) offers a large array of formatting options.

The benefits — why use rich formatting?

  1. 👀 People are more likely to read

    We triage the things that claim our attention. The world of knowledge work is overflowing with things to read; our brains have to filter out some of it in order to not get completely overwhelmed.

    So, people are more likely to pay attention to things that are easier and more compelling to read — like articles with images, frequent paragraph breaks and section headers, as well as varying formats like lists, quotes, and code blocks.

  2. 🧠 People understand and remember better

    Even after someone has decided to read your writing, they may not absorb all of the information you've provided. The same rich formatting that helps to capture someone's attention also helps them to make their way through all of the material (or whatever's relevant to them) and understand and retain it better.

The mechanics — how to use rich formatting?

  1. 🔗 Add references and links to other work in Panobi

    One of the most magical features of Panobi is the fact that you can easily link to projects, insights, and metrics.

    Just type the hash symbol (#) and start typing to find the title you're looking for. Any reader of your project or insight can then quickly click through to whatever you're referencing, if they want more context. A handy "Mentioned in" section at the end of projects, insights, and metrics will show other places where that work has been referenced — making it easy to hop over and get more context whenever you need it.

  2. 💐 Vary how your text looks

    Variation is key. Make important sentences bold, italicized, underlined, or highlighted. Use H1 and H2 sizing to make your section headers stand out.

  3. 🍢 Break it up into smaller chunks

    Insert a horizontal rule to divide your work into clear sections. Use lists (bulleted or numbered) to present details in an easier-to-parse way that breaks up walls of text. Insert quotations from user research to drive a point home.

  4. 📊 Liberally sprinkle in non-text elements

    Insert images, data tables, and code blocks to give your readers more context. We recommend always adding "before" screenshots to your project descriptions so you can remember the baseline.

Suggested next reads:

Did this answer your question?