IcePanel Docs
  • 🧊Welcome
  • 🏁Getting started
  • Core Features
    • Modelling
      • Model objects view
      • Connections list
      • Groups
    • Diagramming
      • Diagrams section
    • Organizations
    • Landscapes
    • Domains
    • Global search
    • Dependencies view
    • Imports
    • Exports
  • COLLABORATION
    • Comments
    • Share links & embeds
  • Ownership teams
  • Roles & permissions
  • Visual Storytelling
    • Flows
      • Flows section
    • Tags
    • Technology choices
  • Future state design
    • Drafts
    • Versioning
  • Reality linking and integrations
    • Linking to reality
    • Code repo linking
      • GitLab
      • GitHub
      • Bitbucket Server
      • Azure DevOps
    • Inaccuracy score
    • REST API
  • 🎓Expert help
    • Training
    • Pilot
  • 🎨Templates
    • IcePanel
    • E-commerce
    • Low-code
    • Marketplace
    • RSS feed
    • Bank
  • ❓Other information
    • Glossary
    • SSO - SAML
    • UI theme
    • Hotkeys
    • Troubleshooting
Powered by GitBook
On this page
  • What is the Recommendation Score?
  • Improving your Recommendation Score

Was this helpful?

  1. Core Features

Recommendation score

Last updated 5 months ago

Was this helpful?

Diagrams are only helpful if your audience can easily understand your message. Confusing diagrams are just as bad (or even worse) than no diagrams at all. IcePanel's Recommendation Score gives you tips to make your diagrams crystal clear for viewers.

What is the Recommendation Score?

The Recommendation Score is out of 100 and is based on 3 things:

  1. Naming of your model objects, diagrams and flows - Don't leave them empty!

  2. Descriptions of your model objects, diagrams and flow steps - Take the guesswork out by briefly describing everything to explain why it exists and what it shows.

  3. Open questions - Answer and resolve all questions to help out your teammates and keep your docs up-to-date!

Improving your Recommendation Score

How to get 100% on your Recommendation Score:

  • Name all model objects, diagrams, and flows with easy-to-understand names.

  • Describe every model object - When everything is described, others can jump in and understand your diagrams and documentation much more easily. Keep descriptions simple and digestible. It may seem simple, but others may not always have the same context.

  • Answer and resolve all open questions so that everyone gets the answers they were waiting for and add things to the diagrams or docs where it makes sense.

Recommendations to add descriptions
Page cover image