9 ms·

Yeah, that would be the modern solution. As far as I can tell even Salesforce has tried that with role-specific views that are customizable. But somehow it just

Yeah, that would be the modern solution. As far as I can tell even Salesforce has tried that with role-specific views that are customizable. But somehow it just converges back to everyone having everything all over again, but this time with 8 different frontend views to be maintained.

mattmanser 6y ago
I've worked on these sort of problems, and I can guess why. What happens is that a new field gets added, and whoever's adding it claims it's really "important" and needs to be seen by everyone. It'll invariably set as mandatory to be filled in too. 2 years later and some integration breaks because the integration doesn't set that field and you end up looking at that really important field and every single project has it set to exactly the same value. Repeat ad nauseum. The other thing I've seen a few times is when assessments or a bonus depends on some field so they make it visible to everyone. Then the bonus scheme changes, but they never hide the fields that no-one cares about any more.
- monkeybutton 6y ago
  > when assessments or a bonus depends on some field Ugh, this reminds me of a mess I inadvertently participated in.. A certain employee, on an unrelated team to mine, decided to to go down the route of becoming an agile/scrum master/evangical and somehow got "reduce instances of X" as their personal KPI/development goal one year. Soon after this, they're pinging myself and other team leads on slack whenever X field is filled out on JIRA and demanding justification. Eventually because of this harassment I just stop filling out the field, leaving it as the default value and just verbally communicating the fact to whomever needed to know. Later on I find out that I wasn't the only one that took this route,And guess what happened next! The scrum master is promoted to a management position, in part due to their stellar KPIs! Excellent work all around!
zxienin 6y ago
Someone has to pay for complexity. Let that be vendor and it’s engineering. Rather end users.

mattmanser 6y ago

I've worked on these sort of problems, and I can guess why. What happens is that a new field gets added, and whoever's adding it claims it's really "important" and needs to be seen by everyone. It'll invariably set as mandatory to be filled in too. 2 years later and some integration breaks because the integration doesn't set that field and you end up looking at that really important field and every single project has it set to exactly the same value. Repeat ad nauseum. The other thing I've seen a few times is when assessments or a bonus depends on some field so they make it visible to everyone. Then the bonus scheme changes, but they never hide the fields that no-one cares about any more.

monkeybutton 6y ago
> when assessments or a bonus depends on some field Ugh, this reminds me of a mess I inadvertently participated in.. A certain employee, on an unrelated team to mine, decided to to go down the route of becoming an agile/scrum master/evangical and somehow got "reduce instances of X" as their personal KPI/development goal one year. Soon after this, they're pinging myself and other team leads on slack whenever X field is filled out on JIRA and demanding justification. Eventually because of this harassment I just stop filling out the field, leaving it as the default value and just verbally communicating the fact to whomever needed to know. Later on I find out that I wasn't the only one that took this route,And guess what happened next! The scrum master is promoted to a management position, in part due to their stellar KPIs! Excellent work all around!

zxienin 6y ago

Someone has to pay for complexity. Let that be vendor and it’s engineering. Rather end users.