Added this to Reverse Engineering:

• This use of TPG’s resources would have to be solve the strategic problem even though (former) TPG’ers would now defer to the verticals for how.
• Loss of TPG budget would have to be acceptable if this strategy does not work as expected.

I'm not sure how to capture those as Barriers. In short, this strategy relies on verticals being attuned to what they/the org needs, and also it's harder than other possibilities to change our mind about this one, if needed. TPG as a group would no longer exist as an influence.

TPG will meet in 30 min increments until we resolve all the comments in Pos7 and move tests to the master spreadsheet.

We have agreed to run high-level tests on this before continuing work on other barriers and tests that may become irrelevant.

Except there were concerns about running tests, and therefore inviting stakeholders to review the deck, while it is still messy. So we're going to try to get the comments resolved. The backup plan will be to create a duplicate copy of the first section of the deck, for stakeholder consumption, while we grind the sausage in a private copy of the deck.

There is a summary deck that we will use for customer input. In the case that customers are interested in this possibility, we will then invest in cleaning up this deck:
https://docs.google.com/presentation/d/1kzA44lTmYUywhW2e3NKnPVVq6amBSuysEkEQskLJxTg/edit#slide=id.gf5149c8d8_0_0

Further work is not valuable at this time.