make model-capability design decisions
ascourtas opened this issue · 1 comments
ascourtas commented
As Product Owners, we want a clear vision of our products and to reconsider the features based on user needs
Do we want models in Foundry or not? The question has been kicked around a bit. Consider:
If Foundry did not have models...
- How would Foundry connect with Garden models?
- What is Foundry's "big sell"?
If Foundry did have models...
- How does it differ from Garden?
- Are models in Foundry usable in Garden?
- Is a Foundry model more meaningful than just a feature-poor Garden model? What could make it more meaningful?
Consider the User Needs established in the Foundry Roadmap
Assumptions:
Acceptance Criteria
Given..., when..., then...
ascourtas commented
Need to discuss how to redefine this one with @kjschmidt913 now that she's directing product.
Should link here any relevant google docs