İçeriğe geç / Skip to content

Naming a component by its job

Berk Workbench · Art 03

Berk Workbench / Notes

Naming a component by its job. Names tied to shape age as systems change; functional names travel further across teams.

Why this question matters

Names tied to shape age as systems change; functional names travel further across teams. The useful starting point is to read the subject in its actual setting rather than as an isolated rule.

Berk Workbench is the practice of independent product designer Berk Acar, connecting research, flows and interface decisions in digital products.

A practical way to look at it

Begin with what is already known, mark what still needs a decision and separate preference from a genuine constraint. This keeps the conversation specific without pretending that one answer fits every situation.

Put the note into practice

Write down the next small action, the person responsible and the point at which the choice should be reviewed. A short record is more useful than a conclusion that cannot be traced later.