jiahong
255 lines
7.5 KiB
Markdown
255 lines
7.5 KiB
Markdown
### 360°绩效考核评分模型图
|
|
|
|
```plantuml
|
|
@startuml 简化版360°绩效考核模型
|
|
skinparam backgroundColor white
|
|
skinparam borderColor #666666
|
|
skinparam arrowColor #333333
|
|
|
|
' 核心元素定义
|
|
circle "被评估者" as Employee
|
|
|
|
rectangle "上级" as Leader
|
|
rectangle "下属" as Subordinate
|
|
rectangle "同事" as Colleague
|
|
rectangle "自我" as Self
|
|
rectangle "客户" as Customer
|
|
|
|
' 评估关系
|
|
Leader --> Employee: 评估
|
|
Subordinate --> Employee: 评估
|
|
Colleague --> Employee: 评估
|
|
Self --> Employee: 评估
|
|
Customer --> Employee: 评估
|
|
|
|
' 整体说明
|
|
note bottom: 多维度评估，全面反映工作表现
|
|
@enduml
|
|
```
|
|
|
|
* 每一位工作人员既是被评估者，也是评估者
|
|
* 评估关系由「合作事项」来决定
|
|
* 评估期间：合作事项的里程碑
|
|
* 评估项：合作实物
|
|
* 评估项所对应的评估依据：
|
|
|
|
|
|
|
|
#### 2.3.1. 绩效考核数据采集与处理的关系
|
|
* 数据里的信息：
|
|
* 各项分数：
|
|
* 数据项
|
|
* 数据值
|
|
* 数据来源的信息
|
|
* 谁给谁打的数据？
|
|
* 谁与谁的组织关系
|
|
* 「谁」的岗位与职责
|
|
* 在项目/任务工作中日积月累的工作记录，岗位职责执行的程度
|
|
* 原始数据项及其数据值以及数据关系是宝贵的财富！
|
|
* 怎么算取决于想要怎么管！
|
|
```plantuml
|
|
@startuml
|
|
skinparam componentStyle rectangle
|
|
actor "张三" as p1
|
|
actor "李四" as p2
|
|
actor "王五" as p3
|
|
actor "赵六" as p4
|
|
frame "绩效管理" as iboss {
|
|
database "360°评分数据" as data
|
|
file "Report" as ui
|
|
rectangle "数据处理\n----\n*传统权重法\n----\n*数字技术\n**消除偏向\n**多模计算" as proc
|
|
database "绩效值" as perf
|
|
}
|
|
p1 -- data
|
|
p2 -- data
|
|
p3 -- data
|
|
p4 -- data
|
|
data --> proc
|
|
proc -left-> perf
|
|
perf -up-> ui
|
|
proc .up. ui
|
|
ui -- p1
|
|
ui -- p2
|
|
ui -- p3
|
|
ui -- p4
|
|
@enduml
|
|
```
|
|
|
|
|
|
|
|
### 数字处理过程
|
|
|
|
```plantuml
|
|
@startuml
|
|
skinparam componentStyle rectangle
|
|
database "360°评分数据" as source
|
|
rectangle "岗位权重R_n" as rate
|
|
file "消除主观算法" as proc1
|
|
rectangle "KPI指标权重" as kpi
|
|
file "多模计算" as mod
|
|
frame "绩效值" as report {
|
|
rectangle "传统权重绩效值" as kv1
|
|
file "数字处理绩效值" as kv2
|
|
}
|
|
source ..> rate
|
|
rate ..> kpi
|
|
kpi ..> kv1
|
|
source -right-> proc1
|
|
proc1 --> rate
|
|
rate --> mod
|
|
mod --> kv2
|
|
@enduml
|
|
```
|
|
|
|
**多模计算**
|
|
|
|
管理要求与数据处理的关系
|
|
* 功不抵过：$f_m(c)\times f_n(d)$，其中$f_m(c)$是功劳值，$f_n(d)$是过失值，
|
|
* 又红又专：$f_i(x) \times f_n(y)$，反之“又臭又硬”是同一个计算方法；
|
|
* 瑕不掩瑜：$\frac{f_i(b)+f_k(e)}{2}$，其中$f_i(b)$是瑜，$f_k(e)$是瑕
|
|
* 木桶理论：$min(f_i(b),f_j(d),f_k(e)....)$
|
|
* 有何长项：$max(f_m(g),f_n(h),f_p(q)....)$
|
|
|
|
根据实际情况可以引入$Rate$来调节相互影响程度，基本可以实现文字表述的意思通过所获得的数据计算/处理来实现管理的效果。
|
|
|
|
### 检验有效性模型
|
|
|
|
```plantuml
|
|
@startuml
|
|
skinparam componentStyle rectangle
|
|
frame "项目1" as report1 {
|
|
database "360°\n评分数据" as source1
|
|
rectangle "传统权重\n绩效值" as rk1
|
|
file "数字处理\n绩效值" as ck1
|
|
}
|
|
|
|
frame "项目2" as report2 {
|
|
database "360°\n评分数据" as source2
|
|
rectangle "传统权重\n绩效值" as rk2
|
|
file "数字处理\n绩效值" as ck2
|
|
}
|
|
|
|
frame "项目3" as report3 {
|
|
database "360°\n评分数据" as source3
|
|
rectangle "传统权重\n绩效值" as rk3
|
|
file "数字处理\n绩效值" as ck3
|
|
}
|
|
|
|
frame "项目4" as report4 {
|
|
database "360°\n评分数据" as source4
|
|
rectangle "传统权重\n绩效值" as rk4
|
|
file "数字处理\n绩效值" as ck4
|
|
}
|
|
source1 -- rk1
|
|
source1 -- ck1
|
|
source2 -- rk2
|
|
source2 -- ck2
|
|
source3 -- rk3
|
|
source3 -- ck3
|
|
source4 -- rk4
|
|
source4 -- ck4
|
|
package "管理决策" as mgr{
|
|
actor "团队管理" as m1
|
|
actor "团队管理" as m2
|
|
actor "团队管理" as m3
|
|
actor "团队管理" as m4
|
|
}
|
|
m1 -up- rk1
|
|
m1 -- ck1
|
|
m2 -up- rk2
|
|
m2 -- ck2
|
|
m3 -up- rk3
|
|
m3 -- ck3
|
|
m4 -up- rk4
|
|
m4 -- ck4
|
|
@enduml
|
|
```
|
|
|
|
|
|
|
|
|
|
将工作期待的文字描述转化为计算方法和对原始数据提出新的数据项，这样的过程进行测算和迭代改进，应该可以达到管理的目的。
|
|
|
|
将简要的文字陈述工作要求/期待，格式化为数据项供人们录入(评价)，系统进行数据处理和输出报告，为了形成闭环可对数据处理的方法及其参数进行选择，最后确认！
|
|
|
|
```plantuml
|
|
@startuml
|
|
skinparam componentStyle rectangle
|
|
file "能按时完成任务里的工作内容\n----\n*尽量别反反复复弄不干净\n*最有有一定的文档及设计\n*能有创新且效果不错为佳\n*积极推动大家来完成工作" as text1
|
|
file "项目管理和需求设计要做好\n----\n*需求不要变来变去\n*能高效组织开发去执行\n*需求文档和计划很清晰" as text2
|
|
file "市场策略和商机的把握很强\n----\n*项目价值很清晰调动积极性\n*组织好合作伙伴相互协同\n*开发阶段目标很清晰" as text3
|
|
rectangle "格式化数据项" as form1
|
|
rectangle "格式化数据项" as form2
|
|
database "360°评分数据" as data
|
|
rectangle "数据处理" as proc
|
|
database "绩效值(多模)" as perf
|
|
file "评估决策UI" as ui
|
|
actor "管理者" as manager
|
|
usecase "调节参数" as adjust
|
|
text1 --> form1
|
|
text2 --> form1
|
|
text3 --> form2
|
|
form1 --> data
|
|
form2 --> data
|
|
data -left-> proc
|
|
proc -left-> perf
|
|
ui <-- perf
|
|
ui <-- proc
|
|
manager -left-* ui
|
|
manager -right-* adjust
|
|
adjust --> proc
|
|
@enduml
|
|
```
|
|
* 核心问题是数据项里是否包含了简要工作要求/期望的文字陈述的信息！
|
|
* 如果不够增加或调整数据项，会不会导致系统越来越复杂！
|
|
* 数据处理的输出如何与直观感受相关联起来？便于调节数据处理的方法及其参数！
|
|
|
|
|
|
#### 2.3.4. 评分模型
|
|
|
|
```plantuml
|
|
@startuml
|
|
skinparam componentStyle rectangle
|
|
actor "张三" as p1
|
|
frame "KPI考核项" as kpi {
|
|
file "结果导向的执行\n----\n*按时交付开发任务\n*保障代码运行稳定\n*精准达成需求指标\n*高效修复程序漏洞" as text1
|
|
file "工作中创新\n----\n*优化开发流程效率\n*提出代码改进方案\n*探索新技术应用场景\n*简化复杂功能实现" as text11
|
|
file "协同工作\n----\n*积极参与团队研讨\n*主动分享技术经验\n*配合跨部门需求开发\n*及时响应协作请求" as text12
|
|
|
|
}
|
|
actor "赵六" as rec1
|
|
actor "王五" as rec2
|
|
database "任务里的\n工作记录" as log#gray
|
|
frame "对张三\n的印象" as image
|
|
frame "对张三\n的印象" as image2
|
|
file "张三在该任务\n里的工作情况\n----\n*系统分析报告\n*个人撰写报告" as report1#lightgreen
|
|
file "张三得分\n----\n*结果导向的执行\n*协同工作\n*工作中创新" as number1#lightgreen
|
|
file "张三得分\n----\n*结果导向的执行\n*协同工作\n*工作中创新" as number2#lightgreen
|
|
p1 --> text1
|
|
p1 --> text11
|
|
p1 --> text12
|
|
rec1 -- log
|
|
rec1 .. image
|
|
log --> report1
|
|
rec1 <-left- report1
|
|
number1 <-- rec1
|
|
text1 --> rec2
|
|
text1 --> rec1
|
|
text11 --> rec2
|
|
text11 --> rec1
|
|
text12 --> rec2
|
|
text12 --> rec1
|
|
rec2 -- log
|
|
rec2 .. image2
|
|
rec2 <-right- report1
|
|
number2 <-- rec2
|
|
@enduml
|
|
```
|
|
|
|
* 基于任务里的工作记录数据，形成任务成员在该任务里的工作情况分析与统计报告，给评分人提供直观的参考；
|
|
* 有些评分项未来可基于任务里的工作记录所产生的报告直接给出评分，有可能吗？
|
|
* 设置有效的评分考核项才是管理的关键！
|
|
* 工作围绕这些评分项(KPI)指标而展开
|
|
* 任务的工作人员关注评分项(KPI)指标
|
|
|