KINNOVIS

Define use case as precise as possible, also note down the user intent. This information can be available via:

1. The feature request / insight
2. Talks you had with stakeholders
3. Support conversations

Define the approach. This is the most time intensive task, but also your area to shine. Here your value as a PM will be created. Things that can help you to here are: 

1. You own product knowledge
2. Research (<a href="https://help.kinnovis.com/en/articles/7983755-research-resources">find a detailed list here</a>)
3. If you still have, not enough information, then consult Alex, Oliver, Martin or Andreas 
4. Write down your approach. 
   1. How can you solve the use case? 
   2. Which products (manager, booking portal, customer portal, JaneGPT) have to be touched? 
   3. Which screens have to be touched? 
   4. If the feature is complex, add resources to understand it better (e.g. flowchart)

As we right now have more design than PM resources, it's more important to start with designing the screens than to have the feature perfectly defined. 

1. Click on feature
2. Click on save time with a template
3. Choose EPIC template
4. Define use case as precise as possible, also note down the user intent. This information can be available via:
   1. The feature request / insight
   2. Talks you had with stakeholders
   3. Support conversations
5. Define the approach. This is the most time intensive task, but also your area to shine. Here your value as a PM will be created. Things that can help you to here are: 
   1. You own product knowledge
   2. Research (<a href="https://help.kinnovis.com/en/articles/7983755-research-resources">find a detailed list here</a>)
   3. If you still have, not enough information, then consult Alex, Oliver, Martin or Andreas 
   4. Write down your approach. 
      1. How can you solve the use case? 
      2. Which products (manager, booking portal, customer portal, JaneGPT) have to be touched? 
      3. Which screens have to be touched? 
      4. If the feature is complex, add resources to understand it better (e.g. flowchart)
6. As we right now have more design than PM resources, it's more important to start with designing the screens than to have the feature perfectly defined. 

If you are done with the definition, you can push the feature (ticket) to Trello.

If the feature is big or hard to understand, you should schedule a Kick-off meeting with the designer. In the Kick-off meeting, PM should explain the designer the intended goal. The use case and the approach should be clear to the designer. But it is not a must that the designer understand everything fully, it's more important to start with the screens than to have the feature 100% defined. If the feature is very lightweight, a Kick-off meeting is not needed. 