Not Every Product Feature Is an Operation

“Operation” is a convenient navigation label. It is also easy to stretch until it means every feature in an application.

When that happens, the product loses useful distinctions. Identity becomes an operation. Team membership becomes an operation. Reports, tools and content all enter the same catalogue because they happen to appear in the same Console.

The interface may still work, but its language no longer explains the system beneath it.

Classify by product meaning

An operation is work performed on or with product records: managing dishes, organising menus or running orders. Other capabilities have different roles.

• Identity explains which Entity is selected and how it is represented.
• Team explains who can act and with what access.
• Finance presents authoritative facts and reports.
• Tools produce bounded outputs, sometimes through an external provider.
• Overview summarises and links; it does not automatically own the work it displays.

These areas can remain peers in one Console without sharing one classification.

Language reveals architecture

Names influence where code and permissions accumulate. If everything is an operation, developers may build one operation registry with enough options to represent unrelated capabilities. Product copy then describes navigation categories instead of actions and observable results.

More precise nouns improve both interface design and implementation. They reveal which domain owns a capability, which records it uses and what outcomes a user should expect.

Review the catalogue from the bottom up

For each feature, list its real records, actions, states and outputs. Then ask whether the parent label accurately summarises them.

A Finance report over recorded sales should say what the user can review. It should not be described as a generic operation merely because the link sits beside operational tools.

What we do at FireUX

FireUX treats Identity and Team as first-class Console peers. Finance is classified by its authoritative reporting job. Overview is the Console home, and a Tool remains tooling even when Overview links to its result. Operational catalogues contain capabilities whose product meaning is genuinely operational.

This is the language counterpart to a Console being a surface rather than an owner.

Good information architecture does more than arrange links. It gives every part of the product a name that remains true in the interface, source code and permissions.