A Simple Team Template Became a Product-Rules Project
Adding team to Cardlyx, a digital business card service, first looked simple: an administrator would create a and employees would use it to make their cards. The hard part was deciding how every field should behave, not building the itself. Decisions included whether employees could change the company name or profile photo and whether later changes should affect cards already created.
Each field also needed rules for whether it was required, shown, editable, or locked. The design had to balance an administrator’s need for consistent company information with members’ freedom to manage their own details. The finished feature includes team , field controls, member , -based setup, and usage reports for administrators and members.
Defining these product rules took longer than writing the feature, so development greatly exceeded the original estimate.
Key points
- The itself was easier to build than its and update rules.
- Every field needed separate rules for , editing, locking, and whether it was required.
- Changes to a raised questions about cards that had already been created.
- The final scope included member , guided setup, and usage reports.
- Writing down roles and exceptions before coding can reduce unexpected rework.