Spaces, Challenges + Opportunities are all very similar to each other. Having 3 different concepts is simply very confusing for our users, as well as bringing a lot of complexity into the platform.
The intention is to have a single entity, Space, that can then have child spaces i.e. subspaces. Then the different ways in which spaces are used, at different levels, is controlled by a combination of templates and UX design.
Longer term it may also be that we want to support more than the 3 we essentially now support. Also a lot of customers / usage right now is satisfied with 2 levels.
In essence this is about creating a general Space concept, which can then be adapted to support multiple types of usage / methodologies via the template that is applied. Currently the platform enforces a hierarchy with structure that is often not relevant / right: it needs to be more flexible.
Initiative / goal
Simplifying the platform, both for end users and in terms of functionality to be maintained.
Hypothesis
Space, Challenge and Opportunity can be represented by a single concept i.e. Space
The term subspace is much easier for users to comprehend when using the platform as they have already internalized the concept of space.
Space as a concept together with templates is rich enough to make a "challenge subspace", "goal subspace", "opportunity subspace"
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
Description
Spaces, Challenges + Opportunities are all very similar to each other. Having 3 different concepts is simply very confusing for our users, as well as bringing a lot of complexity into the platform.
The intention is to have a single entity, Space, that can then have child spaces i.e. subspaces. Then the different ways in which spaces are used, at different levels, is controlled by a combination of templates and UX design.
Longer term it may also be that we want to support more than the 3 we essentially now support. Also a lot of customers / usage right now is satisfied with 2 levels.
In essence this is about creating a general Space concept, which can then be adapted to support multiple types of usage / methodologies via the template that is applied. Currently the platform enforces a hierarchy with structure that is often not relevant / right: it needs to be more flexible.
Initiative / goal
Simplifying the platform, both for end users and in terms of functionality to be maintained.
Hypothesis
Space, Challenge and Opportunity can be represented by a single concept i.e. Space The term subspace is much easier for users to comprehend when using the platform as they have already internalized the concept of space. Space as a concept together with templates is rich enough to make a "challenge subspace", "goal subspace", "opportunity subspace"
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