A composite indicator crosses two or more variables to produce a result — a rate, a ratio, a percentage — rather than displaying a single value taken straight from a field. Why single-field indicators run out Plenty of the numbers a manager cares about do not exist as a field anywhere.
Conditional colour on indicators changes the value or the background automatically when a figure crosses a reference point. A dashboard then communicates status, not just numbers. Why a number alone is not a signal Reading a dashboard should not require remembering what each target was. * Figures that look fine until
To customize indicator format and decimal places, you set the number formatting, the precision, and the styling on the indicator itself. The same underlying figure can read as a currency, a percentage, or an abbreviated number. Why formatting is not cosmetic A figure formatted badly is a figure read badly,
To build a dashboard without a BI tool, you create indicators and charts directly on the records your team already works in. There is no export, no modelling layer, and no delay between an operational change and the number moving. Why the BI layer often creates more work than it
To design internal apps for non-technical teams, you reduce what each person sees to what they need. Adoption failures are almost always navigation failures, not feature failures. Why internal tools get abandoned People do not stop using a tool because it lacks capability. They stop because they cannot find
Keyboard shortcuts for building apps remove the navigation overhead between having an idea and implementing it. Creation, editing, and search all have a key, reachable from anywhere in the platform. Why menu navigation slows building down The cost is not any single click. It is that friction discourages small improvements.
To duplicate a table to start a new process, you use an existing structure as the base and choose whether to bring its records along. The new process inherits the fields you already refined instead of starting empty. Why starting from scratch wastes work The structure of a well-used
Colour conditionals on Kanban cards change a card's appearance automatically when a rule is met. Risk, priority, and overdue work become visible without anyone tagging cards by hand. Why manual highlighting fails Any system that depends on someone remembering to flag a card will eventually stop reflecting reality.
Choosing which view to use for your data depends on the question being asked. The same records can appear as a table, a board, a list, or a dashboard — and each answers something different. Why teams argue about views Disagreements about tools are usually disagreements about tasks. Finance and operations
To customize the top bar of an app, you choose among several display styles — rounded, icons, icons with backgrounds, or text-only — and position the bar where it suits the layout. Why the top bar carries more weight than it looks Learning to customize the top bar of an app
To build a custom home page inside an app, you add a navigation block that points to the tables and apps people need. Instead of relying on the side menu, the app guides users from a central starting point. Why side-menu navigation is not enough A menu lists everything
To resize blocks in an app, you drag from any edge rather than a single corner. Combined with a keyboard shortcut for adding blocks, laying out an internal app becomes a matter of minutes. Why layout matters more than it seems An internal app is used dozens of times a