Deciding between card chat or channel determines whether context survives. A discussion about one record belongs to that record; a discussion about the process belongs to a channel. Why it matters later The difference only becomes obvious when someone new inherits the work. * Decisions about a specific case lost in
To navigate a large workspace, stop browsing. Once a workspace holds dozens of apps and tables, searching is faster than any menu structure can be. Why menus stop scaling A hierarchy that made sense at ten items does not at a hundred. * Scrolling a side menu to find something used
To design action buttons, separate them from the fields people fill. A button competing for attention with twenty inputs is a button people miss or press by mistake. What goes wrong with buttons They are added to the form and disappear into it. * Approval buttons lost among input fields * Actions
To use conditional colour well, apply it to the few things that should change someone's behaviour. Colour applied everywhere carries no information at all. How colour stops working Each rule is added for a reason and collectively they cancel out. * Every field given its own colour scheme * Five
To use attachment fields well, give each document role its own field. One field holding everything makes it impossible to know what a record actually contains. What one catch-all field costs The files are there and nobody can tell what they are. * Six documents in one field with no
To use user fields for ownership, treat them as structure rather than as labels. A user field drives assignment, routing, notification, and often what a person can see. What a user field enables More than recording who is responsible. * Routing an approval to the right person automatically * Scoping permissions so
To use date fields correctly, store each meaningful date separately. A single date field asked to mean several things breaks the moment you need to report on any of them. Where date handling goes wrong Dates look simple and cause disproportionate trouble. * One date field meaning request, approval, or due,
Choosing between a checklist or subtasks depends on whether the items need to be owned. A checklist confirms; a subtask assigns. What each is for They look similar and behave differently. * A checklist records that something was verified * A subtask records that someone is responsible for doing something * A checklist
Choosing between a formula field or automation comes down to whether the value should follow its inputs forever or be fixed at a moment in time. Why the distinction matters Both produce a number. They behave differently when the inputs change afterwards. * A formula recalculates whenever its inputs change * An
Deciding between a connected field or text field is the most consequential structural choice in most builds. Text is faster to create and produces duplication that compounds over time. What text costs when it should be a connection The same entity ends up existing many times, slightly differently. * One client
Choosing between single select radio or tags looks cosmetic and is structural. The difference is how many values a record may hold, and that determines what the field can drive. What goes wrong when they are mixed up The symptoms show up on boards and in reports. * A record appearing
Learning to choose the right field type matters because the choice determines what becomes possible later. A value stored as text cannot be summed, compared, or used in a threshold rule. What the wrong type costs The consequences appear weeks after the decision. * Formulas that will not calculate * Approval thresholds