仕事の優先軸は「緊急度」と「ユーザーへの影響度合い」の2軸で決定します。
緊急度は「納期、締め切りに近いか否か」によって変わります。
ユーザーへの影響度合いは、その仕事がユーザーにすぐ影響することとユーザーの体験がより豊かになるかどうか
によって測ります。
最優先は緊急度が高く、ユーザーへの影響度合いが大きいものに着手します。
次は、緊急度は低いが、ユーザーへの影響度合いが大きいものに着手します。
これは中長期的にユーザーへの貢献のために準備をしていおく必要があると思うからです。
Rating
50
Translation / English
- Posted at 15 Aug 2021 at 23:41
Priority of the work is decided by two factors; the "emergency level" and the "influence level to users."
The emergency level depends on "how close the work is to the delivery date or deadline."
The influence level to users is defined by whether the work immediately affects to users and makes user experience more prosperous.
As the top priority, we start the work which emergency level is high and influences much to users.
Next, we deal with the work which emergency level is low but influences much to users.
This is because I think we need to be prepared for the contribution to users in the medium to long term.
The emergency level depends on "how close the work is to the delivery date or deadline."
The influence level to users is defined by whether the work immediately affects to users and makes user experience more prosperous.
As the top priority, we start the work which emergency level is high and influences much to users.
Next, we deal with the work which emergency level is low but influences much to users.
This is because I think we need to be prepared for the contribution to users in the medium to long term.
Rating
50
Translation / English
- Posted at 16 Aug 2021 at 00:07
A job priority is determined by two axes called 'degree of urgency' and 'degree of user impact'.
The former varies whether 'the delivery deadline is approaching soon or later'.
The latter is measured to see how immediately the work will affect users and if it could enrich their experience.
The one we work on with top priority comes with high urgency and large user impact.
The next one would be of low urgency but large user impact.
This is for the need to prepare for user contribution in a mid to long run.
The former varies whether 'the delivery deadline is approaching soon or later'.
The latter is measured to see how immediately the work will affect users and if it could enrich their experience.
The one we work on with top priority comes with high urgency and large user impact.
The next one would be of low urgency but large user impact.
This is for the need to prepare for user contribution in a mid to long run.
3番目は緊急度は高いがユーザーへの影響度が小さいものに着手します。この場合、仕組み化をして、極力社内人的リソースを割かないようにするか、外注を検討するなどを検討します。
最後は緊急度は低くユーザーへの影響度が小さいものに着手します。この場合は、そもそも着手するべき仕事なのか代替手段がないかについてチーム内に相談し、場合によっては廃止することを提言します。
以上が私の仕事優先順位の付け方です。
Rating
50
Translation / English
- Posted at 15 Aug 2021 at 23:54
The third, we make a start in the work which emergency level is low and influence level to users is minor. In this case, we minimize to allocate in-house resource as much as possible via structuring, or consider outsourcing.
The last, we work on something with low emergency and small influence to users. In this case, we discuss within the team whether we should really work on it or we have any substitution, and for some cases we propose to eliminate such work.
That is how I put priority to my work.
The last, we work on something with low emergency and small influence to users. In this case, we discuss within the team whether we should really work on it or we have any substitution, and for some cases we propose to eliminate such work.
That is how I put priority to my work.
Rating
50
Translation / English
- Posted at 16 Aug 2021 at 00:17
The third one we would work on is the one with high urgency but low user impact.
In this case we will structure a framework to minimize the internal resources or outsourcing, etc.
Lastly we would work on the one that has low urgency with small user impact.
In this case, discuss internally to see if it is something you should work on or seek for an alternative method. Depending on the case, you must propose abolishing it.
That is all for my way of prioritization.
In this case we will structure a framework to minimize the internal resources or outsourcing, etc.
Lastly we would work on the one that has low urgency with small user impact.
In this case, discuss internally to see if it is something you should work on or seek for an alternative method. Depending on the case, you must propose abolishing it.
That is all for my way of prioritization.
