Not all product features are created equal. Some are straightforward – let’s call them 1D features. They add a narrow bit of specific functionality to the product and often sit in isolation.
But then there are 4D features. They introduce dimensional complexity. They are the cross-cutting features that are interwoven in the product and create hidden connections. They make every feature now – and in the future – a little harder to reason about.
The classic 4D feature in enterprise SaaS is Role-Based Access Controls (RBACs). Every new feature added to our product must now consider how various roles intersect with RBAC. Or whether a specific feature – and any other connected features – are available to the current user.
4D features add a silent tax on everything your team builds.
Product and design will need to consider the 4D feature in every PRD. Engineering will need to build code abstractions for it. And your marketing, sales, and support teams will need to consider it in customer facing comms, support docs, and in sales calls.
Now there’s an obvious 2x2 matrix here where you’ve got 1D vs 4D on one axis and low value vs high value on the other.
Of course we should try really hard to never build a low value 4D feature. But the time will come when you have to build RBACs, add localization to your product, or implement pricing tiers with feature gates.
You’re going to have to build 4D features. But at least now you and your team have a name for it and know it what means for future feature work.