That’s the really hard question, and likely annoying because I don’t find it easy to outline in hard facts - it’s like the annoying “Soft Skills” section you need on web2 resumes to beat the bots.
My general thinking is:
Low Impact - No direct protocol impact;
- this could straight disbursement of funds (Gitcoin award),
- temp check for some other initiatives that can indirectly impact the protocol (Grants using it to gage community support of Llama),
- funding groups that may impact the protocol indirectly (Treasury Working Group, they won’t carry voting power but have the power of prose),
- and likely items I am not aware of or foresee
Medium Impact - Items that have direct impact on the protocol
- Temp checks to validate contentious items (Treasury diversification with VCs)
- Items currently determined by PT Inc. (what pools to host on flagship [GUSD], partnerships [Aave])
- Items currently performed by PT Inc. with community support (Reserve rate adjustments, Prize adjustments)
- UI changes, Git commits that are not contract related (once further decentralized)
- other things I’ve missed
High Impact - Items that directly impact the protocol and ecosystem
- Partnerships that are more contentious (Fei, Ondo, PoolTogether if it had feedback like Treasury Diversification had)
- Temp check on Sushi LP support from PTIP-36
- Bringing on Part-time/Full-time individuals
- Motions for Ops teams should they feel they are needed
- Contract related Git commits (once further decentralized)
- items I’ve neglected to think about