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
{{ message }}
This repository has been archived by the owner on Dec 4, 2024. It is now read-only.
The rebranding will require changes in the web application and landing page.
Not clear yet whether this issue is big enough to be discussed inside the roadmap process but here for visibility.
What is your hypothesis?
n/a
What value does this bring to our customer and/or our mission? What is the goal?
Rebranding should translate as soon as possible into the interfaces for multiple reasons.
How do we measure it?
n/a
Links:
// Include useful research, such as user tests, competitive analysis, metrics, or surveys.
Part 2: Shaping the problem
// Once the problem statement has passed the Great Filter, work with the team on the problem statement and elaborate on the following points to create more certainty around the problem and possible solutions. Make sure to identify dependencies and invite the necessary stakeholders early into the shaping process.
Problem Owner
// Who is responsible for leading the shaping process of this problem statement. Owner should be assigned directly after the Great Filter meeting. PM will assist.
Non Goal(s)
// Controlling the scope of solving the problem.
Solution
// At the end of the process, if possible, leave only the solution here that you want to be considered during the prioritization vote. Move all other solutions or ideas to Alternative solutions.
Solution 1
// Provided structure is here for guidance and can be altered.
Overview
Rough Scoping & Timeline
// At a high level, what's included in V1 vs. later versions? How big of a project is this? What's the roll out / testing plan?
Risk(s), Key Trade Offs & Decisions
// For example, were there any alternatives considered? What are the value, usability, feasability and business risks and how could we address them?
Concept Mocks
Alternative solutions & ideas
Open Questions
The text was updated successfully, but these errors were encountered:
@johannesmoormann the rebranding will touch mobile, too. Even though the epic would be different, we have the same problem. Should I create a separate problem statement?
Color changes
Illustrations changes
And, since we'll be touching most of the screens anyway, we could also touch up interface appearance and update it to iOS 15 (and make it ready for upcoming iOS 16).
Part 1: Define the problem
What problem are you trying to solve?
The rebranding will require changes in the web application and landing page.
Not clear yet whether this issue is big enough to be discussed inside the roadmap process but here for visibility.
What is your hypothesis?
n/a
What value does this bring to our customer and/or our mission? What is the goal?
Rebranding should translate as soon as possible into the interfaces for multiple reasons.
How do we measure it?
n/a
Links:
// Include useful research, such as user tests, competitive analysis, metrics, or surveys.
Part 2: Shaping the problem
// Once the problem statement has passed the Great Filter, work with the team on the problem statement and elaborate on the following points to create more certainty around the problem and possible solutions. Make sure to identify dependencies and invite the necessary stakeholders early into the shaping process.
Problem Owner
// Who is responsible for leading the shaping process of this problem statement. Owner should be assigned directly after the Great Filter meeting. PM will assist.
Non Goal(s)
// Controlling the scope of solving the problem.
Solution
// At the end of the process, if possible, leave only the solution here that you want to be considered during the prioritization vote. Move all other solutions or ideas to Alternative solutions.
Solution 1
// Provided structure is here for guidance and can be altered.
Overview
Rough Scoping & Timeline
// At a high level, what's included in V1 vs. later versions? How big of a project is this? What's the roll out / testing plan?
Risk(s), Key Trade Offs & Decisions
// For example, were there any alternatives considered? What are the value, usability, feasability and business risks and how could we address them?
Concept Mocks
Alternative solutions & ideas
Open Questions
The text was updated successfully, but these errors were encountered: