Advice on data and filtering

Hi willfrancis​ 

One way or another, you should include in your model a table that relates Capabilities (assuming that's what each row of your current table represents) and Objectives.

Your current method of expanding the Objective column to six columns is not convenient for filtering.

The table relating Capabilities and Objectives (I'll call it Capability Objective) might look like this, with one row per combination:

Capability Objective can then be related to your original table using an appropriate key column (I invented Capability Key for illustration) with a bi-directional many-to-one relationship, and optionally to an Objective dimension table with a single directional many-to-one relationship.

Putting this together, the model might look like this:

You would then apply filters to Objective[Objective].

Note: You don't have to include the Objective table but I prefer to in case there are other Objective-related attribute columns that might be added.

Sample PBIX attached.

Would something like this work for you?