Swap Viable for Valuable in MVC

Why is this change being made?

In light of our continued progression to add depth over breadth and our renewed focus on quality and usability, I wonder if it would help pave the way to explicitly change our perspective on what we mean when we say MVC. What if we change the "V" from viable to valuable?

Just about anything can be cable of working or functioning adequately if you're willing to satisfice and be good enough but to truly provide value, equivalent worth, utility, or desirability... now that's stepping things up.

This change would put Value in the foreground and viability as a default expectation or facet of an MVC as opposed to the inverse as it feels now. By making it part of the initials themselves it will be a rallying cry. It says that we're truly shifting our paradigm and focus. Value is our guiding principle and primary driver when we consider the solution.

Author Checklist

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
• If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
  • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

---