This repository has been archived by the owner on Nov 18, 2024. It is now read-only.
"First Class" and Prioritization #9
ALRubinger
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In another discussion, @csuwildcat says:
Let's align on this. :)
This is very important, but we don't classify it as "first class".
We build financial infrastructure and its ecosystem. We prioritize generalized, extensible architecture. First class: solving our north star use cases. That gives us focus and scope. Where Decentralized ID is a prerequisite to financial exchange, it becomes first class. Where it's not, we guide our first class work towards a Decentralized ID outcome we eventually want to see. In time everything should come together.
Because it's all equally important, but not all urgent at the same time.
You bring up a supporting argument I agree with:
I think this rule of thumb makes sense. If we solve the first class stuff with 80% the effort, another 20% is fair to invest in "important not urgent" areas. If that ratio slides to involve extra additional effort, let's assess the investment/return of straying from our focus.
Does this sound like a reasonable way of prioritizing our work?
Beta Was this translation helpful? Give feedback.
All reactions