You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We now have this great new functionality for subspace templates, but using them is still rough around the edges. Instead of promoting the subspace templates now that they are usable but not great ux-wise, we want to first make the ux presentable before telling the world about this great new feature
Goal
Making the subspace templates look impressive from the moment we present them
Hypothesis
What is your hypothesis on the success of this Epic? Describe how success will be measured and what leading indicators the team will have to know if success has been hit.
Must have scope
Define what is a must-have for launch and in-scope. Keep this section fluid and dynamic until you lock-in priority during planning.
Stakeholders
Describe who needs to be kept up-to-date about this Epic, included in discussions, or updated along the way. Stakeholders can be both in Product/Engineering, as well as other teams like Customer Success who might want to keep customers updated on the Epic project.
Design
Figma file: Comments are highly appreciated. When commenting in Figma, please also leave a note in the comments box below this issue to notify us
The text was updated successfully, but these errors were encountered:
SimoneZaza
added
Align Z-GP
Allowing for a quick way to select the same issues in ZH/GP
and removed
Align Z-GP
Allowing for a quick way to select the same issues in ZH/GP
labels
Nov 18, 2024
Description
We now have this great new functionality for subspace templates, but using them is still rough around the edges. Instead of promoting the subspace templates now that they are usable but not great ux-wise, we want to first make the ux presentable before telling the world about this great new feature
Goal
Making the subspace templates look impressive from the moment we present them
Hypothesis
What is your hypothesis on the success of this Epic? Describe how success will be measured and what leading indicators the team will have to know if success has been hit.
Must have scope
Define what is a must-have for launch and in-scope. Keep this section fluid and dynamic until you lock-in priority during planning.
Stakeholders
Describe who needs to be kept up-to-date about this Epic, included in discussions, or updated along the way. Stakeholders can be both in Product/Engineering, as well as other teams like Customer Success who might want to keep customers updated on the Epic project.
Design
Figma file:
Comments are highly appreciated. When commenting in Figma, please also leave a note in the comments box below this issue to notify us
The text was updated successfully, but these errors were encountered: