---
# System prepended metadata

title: Success V2

---

# Success V2: Evolving with Polkadot

## Mandate
## Objectives
## Team Organization





----
----
----
----

## Mallorca Retreat
- Q4 transition period?
    - Why do we think we need to have a transition?
    - Change from teams lifecycle to tech stack.
- Focus on Impact. Impact on what?
    - Making life easier for builders.
    - High Impact, high effort tasks: sub-divide them in steps.
    - ![](https://hackmd.io/_uploads/HyjDvRixT.png)
- Current KRs
    - https://www.figma.com/file/GkOvmHP8xqyadSiVP92YVD/Builders-Teams-KRs---OND-2023?type=whiteboard&node-id=0-1
    - Great execution, bad impact.
    - Why?
        - Lack of information. Things like the polkadot-sdk renaming could have been nice to know beforehand and prepare for it hand in hand with the responsible teams. In the future this will be key with engineering updates.
        - Lack of flexibility. First two weeks of the quarter are to be dedicated to deeply understand the hypothesis we had when building the KRs. If at that moment in time we realize this does not help the way we want, then we should have a conversation around it. Either pick another one or change that one to become more impactful (example: User Stories from SE).
        - Lack of clarity on impact. We never went back to the overarching objectives to measure impact against those.
- We need to start thinking about merging teams. 
    ![](https://hackmd.io/_uploads/rJKC_Coga.png)

    - Product improvements: both builders and pioneers.
        - What is the product? Polkadot? Substrate? Cumulus?
    - Conviction: uncertainty when building is also an issue. Builders responsible here too.

|                                                                                                                                        | Product Improvement | Conviction |
|--------------------------------------------------------------------------------------------------------------------------------------|:---------------------:|:------------:|
| Identify the friction between our products to be able to provide insightful information on their usability and nourish their adoption. | 95%                 | 5%         |
| Decrease time to Parachain.                                                                                                            | 95%                 | 5%         |
| Enable future builders to build without us.                                                                                            | 70%                 | 30%        |
| Empower teams to take an active role for maximizing ecosystem value through healthy competition.                                       | 50%                 | 50%        |

### Slides Design
1. Market prediction + success objectives.
    - Market prediction actually shows that the challenges we are facing are the ones that we knew we were going to face.
    - Objectives that we had as success. Where we think we did well and where we didn't.
2. Builders Objectives. Rundown through these and how they connected to the overarching success ones. Surprise, surprise, nothing tied to conviction. That changes!
3. Current cycle
    1. Lessons learned; retrospective. Main one is impact!
    2. KR's rundown. Message: great job in executing, team doing good here, proud. However not impactful work.

Positive, negative/challenges/obstacles impact things.


    