Recommended task role approach for disabling a field that is editable by default

Scenario:

Default view allows editing a field. We want most users to NOT have access to edit the field. Creating a Persona would turn off the ability to edit, but would require assigning most users the role to have that as default, and thus we had to add that task role to a lot of business roles. So to have the standard view and be able to edit the field, it is the absence of the task role that gives the standard role and allows edit. That presents problems where governance level users also have to have other roles that cause them to see the persona (and removes ability to edit the field). What is the recommended approach for this type of scenario?