> For example, one of our teams had the requirement "Allow end users to programmatically configure widget xyz". Now, widget xyz has a janky design and a table w

> For example, one of our teams had the requirement "Allow end users to programmatically configure widget xyz". Now, widget xyz has a janky design and a table with 50 columns associated with it. > So what did this team do? They took that internal table definition, made a CRUD api that exposes the whole thing, and moved on. > Tell me, how do you fix something like that like that? That's genius! You can now use your metrics from that API to determine how the users are actually using it to provide more value. Are they hooking into something they shouldn't? Well then they are missing a feature and that is an opportunity for you to build that feature for them.