[naiyt]

Hm, "simple changes" are almost never simple. To get it done, the following would likely need to happen:

Project managers would need to write a proposal and use cases. UX/design would need to meet and make wireframes and mocks. Engineers would need to nail down the technical design. The time and costs would have to be approved by management. They'd likely end up discussing the change with their biggest clients to make sure it doesn't interrupt their work flow. Eventually the engineers will be able to write a bit of code to make the change -- at which point QA will get their hands on it when they finally have time.

This is why suggestions like that are typically "put on the roadmap" with little likelihood of actually happening.

[ryanq_do]

This is true to a degree at DO though these changes to language and positioning aren't quite so large to require everything you listed. We rolled out the copy change a few minutes ago to change "Notifications" to "Email Subscriptions" as suggested.

[notwhoyouthink]

I wonder if this change breaks the extension, ha.

I can appreciate the flexibility you're offered even with the A-list clientele you have. In a world of "move fast and break things" I've re-worked that into my own mantra of "move fast and make things better."

In fintech we can't afford -- both figuratively and literally -- to break things, but you still have to allow your teams to take a crazy "bar napkin" idea and run with it without a bunch of red tape or you lose the competitive edge that makes you stand out.

Now changing the wording on a link isn't a crazy bar napkin idea, but it still demonstrates the flexibility you're afforded to make things better and I see a lot of value in that.

[vlunkr]

I think it depends on what type of company DO is. It's renaming one link and moving two others, there's really no need to additional wireframes etc. (This extension did that part for them)

[octavn]

That's pretty much how it works in bigger companies.