The Gain is an required **input to be written in Gain Intl
. Its a decimal number superior or equal to $0$. Here’s a cheat-sheet to input a Gain:
$0$: This tasks provides no value on its own to Stockly (which is the case for most tasks, ex split tasks, reviews, process reviews, etc)
<aside> 🤔 Some tasks don’t bring anything to Stockly in isolation and are done only because they’re blocking another one which has Gain. For example, analysing a demander documentation has no value of its own, it’s done only because it’s required for the go-live of said demander.
</aside>
$0⁺ - 1$
: Very low impact tasks. Typically, SEV5 tickets, tickets impacting less than 10 order lines and/or purchases a day. Tasks whose impact doesn’t scale with the network size.
$2 - 4$
: Low impact tasks. Typically, SEV4 tickets, tickets impacting less than 30 order lines and/or purchases a day. Tasks whose impact doesn’t scale with the network size.
$5 - 14$
: Typically SEV3 tickets, tickets impacting 1 to 5% of GMV Score per day, small features, productivity wins impacting a few teams.
<aside> 👁️🗨️ ‣ with Gain $≥ 5$ and Work Duration ≥ 3 must have inputs validated by a Team Leader.
</aside>
$15 - 34$
: Typically SEV2 tickets, features with significant impact of the network (5% - 25% of GMV Score)
<aside> 👁️🗨️ ‣ with Gain $≥ 15$ and Work Duration ≥ 10 must have inputs validated by either @Camille Devaux, @Pierre Vigand, @Elrendio or @Eliott .
</aside>
$35 - 57$
: High impact tasks. Tasks impacting almost all the network, impacting significantly our margins, volume or productivity.
<aside> 👁️🗨️ ‣ with Gain $≥ 35$ and Work Duration ≥ 20 must have inputs validated in Pole Leader Alignment
</aside>
$58+$
: Ground breaking tasks. Strategic tasks with a huge impact of the company’s viability and trajectory, SEV1 tickets.
<aside> 👁️🗨️ ‣ with Gain $≥ 58$ and Work Duration ≥ 30 must have inputs validated @Elrendio & @Eliott.
</aside>
If the ‣ is not an Integrate Partner
Task:
Compute its importance relative versus Integrate Partner
Tasks and other ‣. For example, if a task brings more value than two other combined it should have a higher gain than the sum of their gains.
If the ‣ is an Integrate Partner
Task, Gain is computed from the ‣:
Prioritisation Score | ‣ Gain | Example |
---|---|---|
10 | 58 | Business Potential = 1 - Very High |
Churn Risk = 1 - High | ||
✅ Is a Brand | ||
9 | 48 | Business Potential = 1 - Very High |
Churn Risk = 1 - High | ||
❌ Not a Brand | ||
8 | 39 | Business Potential = 1 - Very High |
Churn Risk = 2 - Medium | ||
7 | 31 | Business Potential = 1 - Very High |
Churn Risk = 3 - Low | ||
6 | 24 | Business Potential = 2 - Strong |
Churn Risk = 2 - Medium | ||
✅ Is a Brand | ||
5 | 18 | Business Potential = 2 - Strong |
✅ Is a Brand | ||
4 | 13 | Business Potential = 2 - Strong |
Churn Risk = 3 - Low | ||
3 | 9 | Business Potential = 3 - Moderate |
Churn Risk = 2 - Medium | ||
2 | 6 | Business Potential = 3 - Moderate |
Churn Risk = 3 - Low | ||
1 | 4 | Business Potential = 4 - Low |
Churn Risk = 3 - Low | ||
0 | Invalid Input | Invalid Input |
$$ \text {Tech Task Gain} = \frac{PrioScore*(PrioScore+1)}{2} + 3 $$
This formula is an arbitrary formula, it tries to represented the quadratic importance of partners experienced in real life. It doesn’t perform very well in extreme case, in which case you may override the gain.
Tasks must include a justification of the [🖊️ Internal Gain](https://stockly.notion.site/Internal-f7229920b4a04bb28babb972ff23842f), except if it comes from an external computation as for ‣ or from the migration of a Ticket, in order for other members to challenge the Gain.
Not dated, missing estimation of issue and of gain.
❓ Why ?
In the past 90 days before January 8, 2024, there was 20 tickets asking to block distribution for expensive product resulting in ~40H of works. We expect to be able to reduce this time to ~10H with this feature.
The Gain of a task $T$ has 3 components:
Override
<aside>
💥 In very specific cases a gain_out_override
can be used
</aside>