Job title speciality mapping
Context
We are using the stages.yml file as SSOT for group metrics. In our current DBT models, there must be a matching label (using the scoped group
label, aka group::%
) to group name in this file. Otherwise, we are unable to map data back to respective groups. At the department level, there isn't an issue because team members have the correct department. However, the job title speciality (aka group name) is dependent on manual entry.
MR Rate, a measure of productivity and efficiency, is calculated using the job title speciality field in Workday. A group’s MR rate is the ratio of MRs (as mapped back using logic above) to the number of team members in the group.
Problem
- Team members aren't being included in MR Rate because their job title speciality does not match what's listed in the stages.yml file.
- Team members aren't being included in the MR Rate because they have not updated their job title specialities when the group name changes.
- Changes in Workday only reflect correct data going forward. In other words, if a team member realizes their metrics aren't being populated and suddenly correct their job title speciality, only forward updates are included.
Since the values in Workday do not map back to our SSOT, we need to find a solution to map these values back to actual groups as defined in our SSOT.
Some of these values can be cleansed and map back to an existing group. Others don't.
Findings
There was a job title speciality audit taken place in 2023 and this field was updated in DB on 4-15-23. Here’s the breakdown of the job title speciality:
JOBTITLE_SPECIALITY | COUNT(*) |
---|---|
Govern: Threat Insights | 14 |
Verify: Runner | 13 |
Systems: Distribution | 13 |
Systems: Gitaly | 12 |
Create: Source Code | 11 |
Verify:Pipeline Execution | 11 |
Package: Package | 11 |
Govern: Security Policies | 10 |
Manage: Authentication and Authorization | 10 |
Deploy: Environments | 10 |
Data Stores: Tenant Scale | 10 |
Secure: Static Analysis | 10 |
Secure: Composition Analysis | 10 |
Verify: Pipeline Authoring | 9 |
Plan: Project Management | 9 |
Govern: Compliance | 9 |
Data Science: AI Assist | 9 |
Systems: Geo | 9 |
Data Stores: Global Search | 8 |
Fulfillment: Utilization | 8 |
Plan: Optimize | 8 |
Manage: Foundations | 8 |
Fulfillment: Billing and Subscription Management | 8 |
Data Stores: Database | 8 |
Create: Code Review | 8 |
Verify: Pipeline Security | 7 |
Monitor:Respond | 7 |
Create: Editor | 7 |
Manage: Integrate | 7 |
Plan: Product Planning | 7 |
Fulfillment: Fulfillment Platform | 7 |
Fulfillment: Purchase | 6 |
Fulfillment: Provision | 6 |
Analyze: Product Analytics | 5 |
Data Stores: Application Performance | 5 |
Monitor:Observability | 5 |
Analyze: Product Intelligence | 4 |
Data Science: Anti-abuse | 4 |
4 | |
Secure: Vulnerability Research | 4 |
Growth: Acquisition | 4 |
Create | 3 |
Plan: Knowledge | 3 |
Secure: Dynamic Analysis | 3 |
Product Intelligence | 3 |
Plan | 2 |
Secure, Govern, Data Science, Growth | 1 |
Manage | 1 |
Code Review,Create:Code Review | 1 |
Fulfillment | 1 |
Composition Analysis | 1 |
Secure | 1 |
Plan: Knowledge,Create:Editor | 1 |
Enablement | 1 |
Verify | 1 |
Analytics,Manage: Compliance | 1 |
Govern, Anti-Abuse, Growth | 1 |
Dev | 1 |
Threat Insights | 1 |
Monitor:Visualization | 1 |
Data Stores | 1 |
Growth | 1 |
Ops | 1 |
Next steps
- Quantify how many team members are not included once mapped back
- Determine solution