← 返回教程首页 | 视频图文笔记 第 22 / 23 期

Workday 直播课:组织生效日期、Position/Job 配置模型的切换锁死与 Job Profile→Family→Group 岗位架构搭建

The Job Architecture Mistake Costing You Hours Every Month

频道:Workday Learner Community 时长 1:34:26 发布于 2026-07-15 26 段对照 · 全片覆盖 原视频 ↗
⏱ 每节的 时间点 对应视频画面,点开原视频拖到该时间即可对照。
标题党注意——本片标题《The Job Architecture Mistake Costing You Hours Every Month》像是一篇讲“某个岗位架构错误每月浪费你多少工时”的观点视频,但通读全片字幕确认:实际是 Workday Learner Community 的一堂直播教学课(讲师风格:白板手画+Workday 租户实操),系统讲三个核心概念——①组织(回顾组织为何用 effective date 1900/2000、能否自建自定义组织类型)②人员配置模型(Position vs Job Management、切换锁死、hiring restrictions 挂载位置、继承语义、available for overlap、后门建位)③岗位架构(Job Profile→Job Family→Job Family Group 三层搭建)。标题里的“Job Architecture”只在最后约 01:17–01:34(不到全片 1/5)出现,且没有任何“具体某个错误 / 每月损失工时”的量化叙事,属标题与内容不符(内容为真、标题夸大且窄化)。全片是纯教学,无课程招生 / 报价 / 带货。【篇幅判断】约 20–25 分钟是答疑 / 课堂互动 / 排障 / 面试 coaching 而非主线:开场 00:00–00:08 学员问改位置名与 remote 位置、是否回退;00:19–00:20 面试 trick 问题(为何用 1900 而非 1975);00:22–00:28 让学员猜两图哪个是 position;00:51–00:53 overlap 能否改、job requisition 是什么、是否一对一;01:01–01:16 中场休息+排障学员租户(建位/改模型被审批拦,讲师去另一租户改流程审批);01:16–01:17 白板 vs PPT 投票;01:32–01:34 作业澄清与提问。主线实操约占 2/3。【与前两期关系】第 6 期《Staffing Model 与 Job Profile》已用幻灯片对比 Position/Job Management 并讲建 Job Profile;第 10 期《Job 与 Position》已讲 job catalog 层级与建 job/建 position 的审批差异。本片不复述这些概念,增量在于现场租户实证的边界规则与画面证据:①改模型的硬锁——只要有 open position 就看不到 Edit Staffing Model,且关闭后落入 Unavailable to Fill、历史记录仍永久锁死模型(00:38–00:44 三帧组织页+表格);②Job 模型上 set hiring restrictions 后,组织菜单只剩 Edit Hiring Restrictions、不再有 Edit Staffing Model(00:43–00:44);③staffing model 只在建时继承,改父不改已建下级、而 organization assignments 会向下继承(00:45);④hiring restrictions 挂载位置对比(Position 挂单个 position、Job 挂 supervisory org)、job 侧“可填”显示的是 job profile 不是 position;⑤组织 effective date 1900/2000 的迁移期根因、以及 Maintain Organization Types→Custom 自建组织类型(前两期未讲);⑥岗位架构“为什么值百万美元”的跨国货币/城市成本论证(画了 Software Developer→Russia/England→London 映射树),以及三层实操中画像计数 3324 Active→3326 Active 的可核对细节。【字幕与数字声明】字幕为 YouTube 自动生成,术语误识较多(supervisory 常被写成 supervisor、Cure 前缀被读成 Q/cured、staffing 偶漏),正文统一改用正确术语,quote_en 一律逐字保留字幕原样不改语法。字段名/层级名/数字(如 Organization ID SUPERVISORY_ORGANIZATION-6-6040、Close Date 10/02/2025、Availability/Earliest Hire 10/01/2025、Job Profiles 3324 Active 3 Inactive→3326 Active 4 Inactive、45 items、Positions without Job Requisition 6 items、画像 Cure Workday Analyst - 1/2/3、Beats Workday Analyst - 1/-3、地点 Cure Amsterdam/Boston/India - South、9 画像/3 族/2 组的作业数字)均照画面逐字记录;白板手写字迹模糊处标(待核对);口播与画面不一致以画面为准并写明。本片为屏幕共享+白板,画面丰富,26 段均有独立画面(无“极少画面需置灰”的情况)。
3:00

改位置名:走 Related Actions 不是点三个点

改位置名:走 Related Actions 不是点三个点
  • 画面为 ECHO India 位置/组织相关页,学员反馈点三个点后像“新建位置”而不是改名。
  • 讲师纠正用词:那三个点叫 Related Actions;面试别说 “hover over the three dots”,要说 related actions。
  • 下一步路径:Related Actions→Location→Edit Location Name。
  • 此段属开场答疑,非岗位架构主线,仅作为“改位置名入口”的示例保留一帧。

"Yes. Never say hover over the three dots in an in an interview. Always tell related actions."— 面试时别说“把鼠标移到三个点上”,要说 related actions(相关操作)。

3:40

Edit Location Name:位置字段带出且必填

Edit Location Name:位置字段带出且必填
  • 弹窗 “Edit Location Name”,提示语原文 “Effective date can be left blank if the location has no effective-dated names and you want to correct the name.”
  • Location 字段带红色必填星号,已自动带出 “ECHO Delhi”;Effective Date 空(MM/DD/YYYY);按钮 Cancel / OK。
  • 背景位置清单为 ECHO India,Locations 2 items:ECHO Delhi(+91 86756 74986)、ECHO INDIA Remote;顶部搜索 “echo”。
  • 讲师解释:以为要填“新位置名”是误解——Location 字段必填且自动带出,正因为你要改的就是这个位置本身。

"No, it is mandatory because you are trying to change the name for this."— 不,它是必填的,因为你要改的就是这个位置的名字——所以这里已经自动带出了。

5:30

改名要生效日期:回填有下游影响

改名要生效日期:回填有下游影响
  • 画面 View Location 页(蓝色头部,Location Information 页签)。
  • 改位置名会要求 Effective Date;可回填(如 9/1 建的改到 8/1 系统允许),但会产生下游影响——该位置若已被任何 worker 记录使用,报表输出会不准,故有下游影响时应用未来的生效日期。
  • 某些场景(如 business process)系统不允许 back-dated 改动,因为流程可能已对多个员工执行过,只能当天或未来日改。
  • 顺带纠正 remote 位置判定:给了真实 PIN 邮编就不算 remote——remote 无 work address,只有 home address(此点在 00:04:40,窗口内)。

"if I back date it, let's say this thing was created let's say September 1st and if I want to change it August 1st, the system will allow me change it, but that will have downstream impacts. Your report output will not be correct if this location is being used in any worker records"— 若回填日期,比如 9/1 建的改到 8/1,系统会允许,但有下游影响——只要该位置被任何 worker 记录用到,报表输出就会不准。

10:00

Maintain Organization Types:五页签

Maintain Organization Types:五页签
  • 画面 “Maintain Organization Types” 页,页签 Costing(选中)/ Hierarchy / HR / Pay / Custom;Costing 下子项 Company(选中)/Cost Center/Location/Region/Program/Fund/Gift/Business Unit/Grant/Project/Appropriation/Allocation Pool。
  • Company 内容:Position Assignment——Show in Change Organization Assignments and Job Requisition = Yes、Allow Reorganization Tasks (like Move Workers, Assign Workers) = Yes;Options——Required = No、Unique = Yes;Note:Organizations with exceptions can be found on the Organization Exception Audit report。
  • 讲师:Workday 交付的组织类型不止五类(还有 region、region hierarchy、matrix 等),可用 Maintain Organization Types(不是 create,是 maintain)在 Custom 页签自定义组织类型。
  • 增量:前两期讲 staffing/job,未展开“可自建组织类型”的入口。

"Sorry, it's not create, it's maintain. This is just additional thing I'm showing you. You don't have to create it. Maintain organization types. You will find a tab here, custom."— 抱歉,不是 create,是 maintain;这只是多给你们看的,不必真去建。Maintain Organization Types 里有个 custom 页签。

10:40

在 Custom 报表里加一行自定义类型

在 Custom 报表里加一行自定义类型
  • 画面 “Organization Types - Maintain Custom Organizations”(45 items,1–45 of 45),编辑态新行 “*Organization Type Name” 输入 “Cure Custom Organization”。
  • 报表列含 Use as Financial Worktag / Use as HR Worktag / Available for Payroll Costing Allocation / Required for Payroll Costing Allocation / Custom Organization Worktag Dimension / Worktag Usage / Allows Hierarchy / Used by Organization Subtypes / Allow Reorganization Tasks (like Move Work Assign Workers) / Show in Change Organization Assignments and Job Requisition。
  • 已有行示例:Camp Hierarchy(Allows Hierarchy ✓,subtype camp)、Campus(Financial worktag ✓,Worktag Usage Financial,subtype CAMPUSES)。
  • 讲师步骤:edit report→点加号→给 name(如 cure/custom organization)→要允许层级就勾 allows hierarchy→选 used by organization subtype→roll up 不需要→OK。

"if I have to create one, I'll go in the edit report. And click on the plus sign. I'll give organization type name, let's say, cure."— 要建一个的话,进 edit report,点加号,给个 organization type name,比如叫 cure。

11:30

Create Custom Organization:仅两必填

Create Custom Organization:仅两必填
  • 弹窗 “Create Custom Organization”,仅两个带必填星号的字段:Custom Organization Type *、Reorganization *;按钮 Cancel / OK;顶部搜索 “create custom”。
  • 背景仍是 Maintain Custom Organizations 报表,可见 Camp Hierarchy / CAMPUS / CAMPUS HIERARCHY 等行。
  • 讲师:create custom organization 时输 “cure” 就能选到自定义类型;因为处理的仍是组织,所以要给 reorganization event;在 subtype 里只会看到 department(因为前面只允许了它)——subtype=department 为口播,此帧未展开该字段。
  • 讲师强调这只是演示“能自建”,不必真去建。

"I have to select a custom organization type. And here, if I type in cure, I will have that. Now, obviously, I have to give the reorganization event because again, we are working with different types of organization."— 我得选一个自定义组织类型,这里输入 cure 就能出来;显然还要给 reorganization event,因为我们处理的仍是各种组织。

16:20

组织为何用 1900/2000:迁移期承接回溯数据

组织为何用 1900/2000:迁移期承接回溯数据
  • 画面白板:左侧圆 “Company with legacy [system]”、中间矩形框、右侧 “Workday” 圆、下方矩形框(旧系统→Workday 迁移示意)。
  • 讲师:从旧系统(ADP / PeopleSoft 等)搬到 Workday 时,员工可回溯到 1975;Workday 必须在“那天”就有对应的 supervisory organization、location、cost center、company,迁移数据才能把人放进正确组织;故实施期建的每个组织都用 effective 1900 或 2000(实施期最佳实践)。
  • 实施完成、数据迁好后再建新组织用当天日期即可——那不再是 legacy 回溯数据。
  • 增量:前两期未讲“为什么用 1900/2000”的迁移根因;这是面试常问 trick 题(为何不用公司成立年)。

"your Workday system must have the supervisory organization to hold that employee, must have the location as of that date, must have the cost center, must have the company available in the system as of that date. That is why every organization we create this is during the implementation effective 1900 or 2000."— 你的 Workday 系统必须在“那天”就有对应的 supervisory organization 来承载该员工、有 location、有 cost center、有 company——所以实施期建的每个组织都用 1900 或 2000 生效。

29:40

对比图:CHAIR = POSITION,每形状唯一

对比图:CHAIR = POSITION,每形状唯一
  • 画面白板:顶部 “STAFFING MODELS” 下分两支——左 “Position Management” 框内是方 / 菱 / 三角 / 星四个不同形状,中间标签 “CHAIR = POSITION”;右 “Job Management” 框内是四个相同圆。
  • 讲师揭示答案:说左边是 position management 的都答对——每个形状代表一个唯一 position;Workday 里 position 俗称 “chair”(椅子),你坐的那把椅子就是你在 Workday 里的 position。
  • 右边四个相同圆即 job management。
  • (与 00:36:20 为同一白板的两步:本步刚画出形状并标 CHAIR=POSITION,下一步才补两侧要点。)

"everyone who said that the one on the left-hand side is position management is actually correct. Because each individual design here, shape, refers to a unique position. And in Workday's world each position is referred to as a chair."— 说左边是 position management 的都答对了——这里每个形状都代表一个唯一的 position;在 Workday 世界里,每个 position 都叫一把 chair。

33:40

模型挂在监督型组织并逐级继承

模型挂在监督型组织并逐级继承
  • 画面为租户首页(Good Evening, Heather Jennings 团队首页,含 Team Highlights / Announcements / Important Dates 卡片)。
  • 讲师:staffing model 直接建在组织上——第一个 CEO 组织用 create supervisory organization 时赋 Position Management,之后逐级向下继承,“直到你想改它”为止。
  • staffing model 只适用于 supervisory organization,location / location hierarchy / cost center / company 都没有——因为只有监督型组织能招聘/配置人,其余都是组织分配。

"when we were creating our very first organization using the task create supervisory organization we assigned it position management. And the same gets inherited in every organization ... However, levels down it will inherit until we want to change it."— 我们建第一个组织(create supervisory organization)时赋的是 position management,同样的值向下继承到每个组织;一层层继承,直到你想改它。

35:10

改模型入口:Organization→Edit Staffing Model

改模型入口:Organization→Edit Staffing Model
  • 画面组织 “Cure Sr. Manager Benefits”:Type Supervisory,Superior Organization “Cure Director Total Rewards”,Organization ID SUPERVISORY_ORGANIZATION-6-6040,Staffing 页签显示 “Staffing Model Position Management”。
  • 讲师路径:改模型走 Related Actions→Organization→Edit Staffing Model(不在 Reorganization 里);是个简单 task,但不是人人有权——只有 organization administrator / senior administrator 有。
  • 改回也走同一路径:job management 改回 position management,同样 Related Actions→Organization→Edit Staffing Model,改完即回(口播 “It's back. Simple”);但他随即预告“catch”——这个切换是有条件的。
  • 条件在下一段揭晓:有 open position(哪怕一个)就不能再切模型;此时能改正是因为该组织没有 open position、员工数为 0(00:36:01–00:36:59,窗口内)。

"I'll just click on the related actions. There's an option not reorganization, organization, and you will find an option that says edit staffing model."— 点 Related Actions,选项不在 reorganization 里、在 organization 里,会看到一个 edit staffing model。

36:20

两模型要点逐条写全

两模型要点逐条写全
  • 画面同一白板补全——左框下要点 “Most Control / Each position with its unique HIRING RESTRICTIONS / Option when employee vacates the position / Change…”;右框下要点 “Speed hiring/ bulk hiring / HIRING RESTRICTIONS applied directly on Supervisory organization / NO Option employee vacates the position”;CHAIR=POSITION 仍在。
  • Position Management:每个 position 有各自 hiring restrictions,员工离职时可选继续用/转团队/关闭 position,控制最强。
  • Job Management:hiring restrictions 直接挂在 supervisory organization,全员同约束、同 location、同 employee type、同 manager;人走即无位可替,只能另招,适合 speed/bulk hiring。
  • 区别前两期幻灯片:这里是白板现场把两侧要点逐条写全。

"the primary difference between position management and job management is individual positions have their own control ... Because individual position has its own characteristics and we prefer to call them as hiring restrictions. Each and every position has its own hiring restrictions."— position management 与 job management 的首要区别是——单个 position 各有其控制,每个 position 都有自己的特征,即 hiring restrictions,逐位各异。

37:40

Create Position:数量/标题/限制页签

Create Position:数量/标题/限制页签
  • 画面 “Create Position” task:Supervisory Organization = “Cure Sr. Manager Benefits”(只读),字段 Position Request Reason、Job Posting Title *、Number of Positions * = 1;页签 Hiring Restrictions / Qualifications;Availability Date *、Earliest Hire Date *;按钮 Submit / Save for Later / Cancel。
  • 讲师:走 Staffing→Create Position(三个点里出现 staffing 选项正因为这是配置模型相关);随便填 job posting title “Workday analyst”、availability date 10/1,其余留空,先建 1 个 position 演示后能否改模型。
  • 注意口播把组织说成 “Q or senior manager benefits”,画面实为 “Cure Sr. Manager Benefits”。

"Go to staffing, create position. ... I'll quickly add a job posting title here. Workday analyst. I'm just adding dummy data. Availability date, let's say starting October 1st."— 进 staffing、create position。我快速加个 job posting title——Workday analyst,只是填假数据;availability date 就设 10 月 1 日。

38:40

建位后 Edit Staffing Model 消失

建位后 Edit Staffing Model 消失
  • 画面组织页展开 Related Actions 下拉,看不到 Edit Staffing Model;讲师问学员能否看到,答案是不能。
  • 系统自带校验:只要有 open position(哪怕一个),就不能把该组织改回 job management;此前能改正是因为没有 open position、员工数为 0(staffing 处显示 zero、无列出)。
  • 讲师补:position 不能 delete,只能 close(关闭)。

"Because the system has its own validation that once you have open positions, even one position, you cannot change it back. ... You can close the position. You cannot delete a position."— 因为系统有自己的校验——一旦有 open position,哪怕只有一个,你也改不回去了。你可以关闭 position,但不能删除 position。

40:00

关位落入 Unavailable to Fill,模型仍锁死

关位落入 Unavailable to Fill,模型仍锁死
  • 画面 “Cure Sr. Manager Benefits” 的 “Unavailable to Fill” 页签,定义原文 “A closed or frozen Position, one where the Availability Date hasn't been met, or one with a future dated Fill.”;Closed Positions 1 item:Position Restrictions “Cure Workday Analyst (Closed)”、Close Position Transaction “Close Position: Cure Workday Analyst”、Close Date 10/02/2025。
  • 讲师:即便关了位置、Staffing 页空了,仍改不回 job management——该 position 的历史已挂到组织上;“Everything that we create has a timestamp… Even if you delete it or close it or mark it as inactive, it is still in the system”。
  • Unavailable to Fill 页签也是关了之后才出现(此前该页签都不存在)。
  • 增量:这是“历史永久锁死模型”的关键画面证据,前两期未给。

"Even though we opened a position and closed it, there's a history of that position that gets associated with your senior manager benefits. Everything that we create has a timestamp to it."— 哪怕我们开了一个位置又关掉,这条 position 的历史仍会挂到你的 Sr. Manager Benefits 组织上——我们创建的每样东西都带时间戳。

43:10

Job 模型改挂组织:Set Hiring Restrictions

Job 模型改挂组织:Set Hiring Restrictions
  • 画面 “Set Hiring Restrictions” task:Supervisory Organization = “Cure Director Total Rewards”,字段 Hiring Restrictions Request Reason;Hiring Restrictions 组:Availability Date *、Earliest Hire Date *、No Job Restrictions(复选框)、Job Family(下拉);Submit / Save for Later / Cancel。
  • 讲师:Job management 组织没有 Create Position,取而代之的是 Set Hiring Restrictions;hiring restrictions 就是 location、job profile、availability dates、job family、time type、worker type 等;本例给 Workday Analyst 画像、地点 Cure India - South、full time、employee→regular。
  • 对比:Position 侧限制挂在单个 position,Job 侧限制挂在 supervisory org;一旦在组织上设了限制,就再也看不到 Edit Staffing Model。

"in case of job management, the system knows that this is a job management organization. There's no create position. Instead, the option is set hiring restrictions. Hiring restrictions are nothing but your location, your job profile, your availability dates, your job family, time type, worker type, all those things."— 在 job management 下系统知道这是个 job 管理组织,没有 create position,选项换成 set hiring restrictions;所谓 hiring restrictions 就是你的 location、job profile、availability dates、job family、time type、worker type 这些。

44:20

设限后只剩 Edit Hiring Restrictions

设限后只剩 Edit Hiring Restrictions
  • 画面组织 “Cure Director Total Rewards”,Staffing Model 已为 “Job Management”;Related Actions 展开并在 Organization 子菜单里可见 Edit Hiring Restrictions,但没有 Edit Staffing Model。
  • 页面 Available to Fill 1 item 显示 Job Profile “Beats Workday Analyst - 1”、Worker Type Employee、Worker Sub-Type Regular——job 侧“可填”的是 job profile,不是 position。
  • 讲师确认这就是 job 与 position 的一个主要差异:设了限制后,只有 Edit Hiring Restrictions,没有 Edit Staffing Model。

"Does anyone see edit staffing model? I do see edit hiring restrictions, but can anyone see edit staffing model? No."— 有人看到 edit staffing model 吗?我只看到 edit hiring restrictions,谁看到 edit staffing model 了?没有。

45:00

模型只在建时继承,改父不动已建下级

模型只在建时继承,改父不动已建下级
  • 画面组织 “Cure Sr. Manager Benefits”(Staffing 页签,内容区暂空),作为“改父前就已存在的下级”的示例。
  • 讲师:Cure Director Total Rewards 改成 job management 前,下级 Cure Manager Benefits 已在 position management 下建好;改父组织模型不影响“已存在”的下级——它们保持原位;但若新建下级,它会继承 job management。
  • 即 staffing model 继承的是“你创建那刻的属性,之后的改动不再传导”;组织分配(organization assignments)改动则会向下继承,staffing model 不会。
  • 增量:这条“改父不改已建下级”的继承语义,前两期未点明。

"The existing organization will not have any impact. Okay. But if I create a new subordinate for Cure Director Total Rewards, that will have job management. That will inherit. But the existing one will not have any impact."— 已存在的组织不受影响。但如果我给 Cure Director Total Rewards 新建一个下级,它会继承 job management;已有的那个不受影响。

48:30

后门建位造测试数据:地点可多选

后门建位造测试数据:地点可多选
  • 画面 “Add Profile for Location” 多选弹窗(针对 “Cure Sr. Manager Benefits” 的 Job Profiles),背景 Create Position 表单(含 Job Description Requirements、Location、Time Type 等)。
  • 讲师:他建 position 用“后门”方式(直接 create position),因为顾问/分析师要造大量假数据、假员工,走 job requisition 太慢(审批多、不管用不用 Workday Recruiting);这里一次建 5 个 position,地点可多选、time full-time、worker type employee/contingent/contract。
  • 比喻衔接:椅子的“椅套”代表 job profile(即你的职责)。

"this is a back door entry. We create positions right there and then hire people in it and make them our test dummy data. So, it's very simple for position management, go to staffing and create position."— 这是“走后门”的做法——我们当场建 position、再把人招进去当测试假数据。所以 position management 很简单:进 staffing、create position。

54:10

Position Restrictions 表:逐位各改各的

Position Restrictions 表:逐位各改各的
  • 画面组织 Staffing 页,“Staffing Model Position Management”,“Positions without Job Requisition 6 items”;表列 Position Restrictions / Job Profile / Location / Availability Date / Earliest Hire Date / Time Type / Worker Type / Worker Sub-Type / Job Restrictions。
  • 可见行 “Cure Workday Consultant-2 (Unfilled)”“Cure Workday Consultant-3 (Unfilled)”,Job Profile “Beats Workday Analyst - 3”,Location 含 Cure Amsterdam / Cure Boston / Cure India - South,日期 10/01/2025、Full time、Employee、Regular。
  • 讲师:create position 时可填 head count(数量)一次建多个;再对单个 position 走 Position Restrictions→edit,单独改它的 job profile、worker type、worker subtype——这正是“每个 position 唯一”的体现。

"the system ask for a head count. Number of positions. How many positions do you want? And the number we define, that gets created. Now with each individual position I have the ability to change the hiring restrictions."— 系统会要一个 head count——你要建几个 position,你定的数字就建几个。然后我能对每个单独的 position 改它的 hiring restrictions。

55:40

雇佣路径与适用场景:Position 从位雇、Job 组织层批量雇

雇佣路径与适用场景:Position 从位雇、Job 组织层批量雇
  • 画面为 position 的 Position Restrictions 侧板(Cure Workday Consultant-2 (Unfilled)、Supervisory Organization “Cure Sr. Manager Benefits”),Related Actions→Hire 子菜单展开、多条 Hire Employee 入口——正是“从 position 走招聘”的画面证据;背景组织 Staffing 表可见。
  • 雇佣路径:position management 招聘从 position 走(Related Actions→Hire,contract/regular 走不同自定义流程);job management 里没有 position 这个概念,hiring 发生在组织层——雇进来的人共用同一 job profile、location、time type、worker type,所以 job 侧限制只设一次。
  • 适用场景:job management 多用于 speed/bulk hiring、多为 part-time——USPS 司机、Amazon 送货员、仓库工、Uber Eats 骑手,不论 MIT 毕业还是辍学,有驾照、无犯罪记录即可;建一条 job requisition(如 25 个仓库工)一直开着,来一个合格就招一个。
  • position management 则每个 position 有专门技能要求(与 job 的批量低门槛形成对照)。

"We only have to set the hiring restrictions once. You can see here available to fill, and these are your hiring restrictions. This is the job profile, not the position. There's no concept of position in job management per se."— job 侧限制只需设一次。你能看到 available to fill,这些就是你的 hiring restrictions。这是 job profile,不是 position——job management 里根本没有 position 这个概念。

58:40

薪资区间与头数责任:为什么公司普遍选 Position

薪资区间与头数责任:为什么公司普遍选 Position
  • 画面组织 Staffing 表(Position Management,多行 position;讲师口述 head count of six employees)。
  • 薪资差异:job management 下 part-time 有固定时薪、不议价;position management 若招 senior Workday analyst,薪资有 min–max 区间、按技能与面试表现来回谈,且审批多、耗时长。
  • 系统并不禁止用 job management 招 25 个软件开发,但“要不要细控”是业务决策——技能各异用 position、要求雷同用 job。
  • 头数责任:position management 让报表更好做——讲师有 6 个头数,作为经理对每个 head count 负责;要新增 head count 必须定义理由(带预算分配)并走审批;job management 只有高层概览、不严格。
  • 这也是很多公司即便不真用 overlap(宁可关位再开)仍普遍用 position management 的原因之一;讲师称他从业至今没见过公司真用 job management。

"in case of job management, you create the part-time worker employees position and you have a fixed hourly rate, they'll get it. There's no negotiation on that. But in case of position management, if you're hiring a senior Workday analyst, their salary will have a minimum and a maximum range."— job management 下给 part-time 员工一个固定时薪、没有议价;position management 下招一位资深 Workday 分析师,薪资会有最低—最高区间。

1:22:10

岗位架构三层 + 跨国映射树

岗位架构三层 + 跨国映射树
  • 画面白板——左侧嵌套框完整标注 “JOB ARCHITECTURE”(顶标题)→ “JOB FAMILY GROUP” → “JOB FAMILY” → “JOB PROFILE”;右侧画了映射树:椭圆 “SOFTWARE DEVELOPER” 指向 “RUSSIA”、向下到两个未标椭圆,另 “ENGLAND” 指向 “LONDON”(选中框)。
  • 讲师:job profile 定义职责;相似 job profile 归为 job family,相似 job family 再归为 job family group。示例 Workday 初级/资深/associate 归入 “Workday family”、ServiceNow 系列归入 “ServiceNow family”,两者同属 “enterprise application” 这个 job family group。
  • 为何值钱:一个 software developer 画像在中国/美国/印度/新加坡/俄罗斯含义都不同(货币、本地化、技能),接上薪酬差异更大(currency、type of employment、job classification、worker 等);伦敦比曼彻斯特贵、德州 vs 加州/纽约不同——所以公司愿花数百万做 job re-architecture。
  • 与前两期:Ep10 讲过层级与建 profile;此处增量为“完整三层嵌套图 + 跨国复杂的论证”。

"Having similar job profiles, we club them together and we call it a job family. Having similar job families, clubbing them together, we call it a job family group."— 把相似的 job profile 归到一起叫 job family;把相似的 job family 再归到一起叫 job family group。

1:24:40

Create Job Profile:字段与命名

Create Job Profile:字段与命名
  • 画面 “Create Job Profile” 表单:Job Profile Name * = “Cure Workday Analyst - 1”、Default Job Title、Job Code * = “Cure1234”、Include Job Code in Name(复选框)、Job Family(下拉)、Description / Job Profile Summary;Submit / Save for Later / Cancel;右侧统计 “Job Profiles 3324 Active, 3 Inactive”。
  • 讲师:字段很多但演示只需给名字;务必在每个画像里用你自己的唯一前缀(cure)便于识别;job code 在此租户被设为必填(本非强制),先试 1234 提示已占用,改用 Q1234(可字母数字);job family 还没建稍后建;management level 随手填(后续再讲)。
  • effective date 都用 10/1;接着复制建第二个(manager)、第三个(direct)共 3 个画像。

"For our use case, we'll just give it a name. Do not forget to use your unique alias in every job profile because it will be easy to identify. I'll give it cured Workday Analyst 1. Job code here, they have made it a mandate thing."— 我们这场景就填个名字。别忘了在每个 job profile 里用你自己的唯一别名,好识别。名字叫 cure Workday Analyst 1;job code 这儿被设成了必填。

1:26:40

建 Job Family:建时即挂画像

建 Job Family:建时即挂画像
  • 画面前景 “Create Job Family” 弹窗(Effective Date * 空,Cancel/OK,搜索 “CREATE JOB family”);背景 “View Event”:Create Job Profile 记录 For “Cure Workday Analyst - 1”、Overall Status “Successfully Completed”、Effective Date 10/01/2025;右侧面板已把 “Cure Workday Analyst - 1” 归入 Job Architecture,统计变为 “Job Profiles 3326 Active, 4 Inactive”(较建前 3324/3 增加,印证已建 3 个)。
  • 讲师 thumb rule:想建什么就在搜索框输入并前缀 create,90%+ 都有 Workday 交付的 task(01:26:36–01:26:50);建前刚连建 3 个画像(analyst / manager / direct 三个 management level),口播 “I've created three different job profiles”。
  • 建 family 起名 “Cure Workday family”,建 family 时就能把已建的画像当场关联进来(口播 “I can associate them here, which I would prefer to do”),之后画像即归属该 family。
  • 归入后导航到任一画像即可看到它挂在 family 下(01:27:44–01:27:48);这一层是下一步 job family group 的基础。

"Whatever you want to create, type that in search bar and prefix it with the keyword create. In more than 90% of the cases, there will be a workday deliver task that you can use."— 你想建什么,就在搜索框里输入它、前面加 create——90% 以上都有 Workday 交付的 task。

1:28:10

建 Job Family Group:归入 family

建 Job Family Group:归入 family
  • 画面 “Create Job Family Group” task:Effective Date 10/01/2025、Job Family Group Name * = “Cure Enterprise Applications”、Job Families(下拉,暂空)、Job Family Group Summary、Inactive 复选框;OK / Cancel。
  • 讲师:最后建 job family group,起名 “Cure Enterprise Applications”,可在此直接把 job family 包含进来(目前只有一个)。
  • 为何还要 family/group——报表与规则:给“某 job family group 里所有员工”发一次性奖金,只需一条条件 “job profile group 等于 enterprise applications”;否则要把每个 job profile 逐个挂条件,规模到 5000–10000 人会很乱。

"And give it a name, Cure Enterprise Applications. I can include the job families here itself. So far I only have one. ... Why do we create family and groups? Reporting needs."— 起名叫 Cure Enterprise Applications,我能在这儿直接把 job family 包含进来,目前只有一个。……为什么要建 family 和 group?为了报表需要。

1:30:10

三层落地可见 + 招聘用 family 收窄画像

三层落地可见 + 招聘用 family 收窄画像
  • 画面 “View Job Family Cure Workday Family”:Job Family Name “Cure Workday Family”、Part of Job Family Group “Cure Enterprise Applications”、Job Profile 列出 “Cure Workday Analyst - 1 / - 2 / - 3”、Inactive No;前景 Create Position 弹窗(Supervisory Organization * 输入 “cure…”)。
  • 讲师:画像直接挂在 position 上;建 family/group 是为报表/条件用。作为 recruiter / hiring manager 建 position 时若不确定有哪些可用画像,选 job family group/family 就能列出该族下所有画像,省去翻类别——这是 family/group 的另一好处。
  • 作业(口播,非画面):建 9 个画像(Workday analyst 1/2/3、ServiceNow analyst 1/2/3、payroll analyst 1/2/3)、3 个 job family(Workday/ServiceNow/payroll)、2 个 group(enterprise applications、HR functions),供下一概念 compensation 复用。

"Now here in job profile, if as a recruiter or the hiring manager, I don't know what Workday analyst job profiles we have available in the family option. I can select my job family group and it will give me a list of all the profiles that are available."— 这里在 job profile 上,如果作为 recruiter 或 hiring manager,我不确定 family 里有哪些可用的 Workday analyst 画像,我可以选我的 job family group,它会列出所有可用画像。