The RPG Framework (Part 3 of 11)

The Player Support Newsletter: 26 JAN 2025

Introduction: Clear Expectations

---

Job descriptions tend to be minimally helpful in understanding what the reality of the job is actually going to be. I feel like one of the reasons for this is the tendency to use it as a sort of marketing tool. Recruiters have positions to fill and are paid to do so quickly. Trying to convince as many people as possible to apply is a valid tactic. Another reason is that the writer is usually not the person with the most intimate knowledge of what the job requires. To be clear, I don’t blame HR and recruiting teams for this, it’s really a team activity if you want it to well. Getting information and expectations aligned across all of these people and teams can be additionally challenging when everyone says that they just don’t have the time.

We can improve our recruiting processes, but another line of mitigation exists in the direct management of the employee. In marriage, you do not have to acquire perfect knowledge about the other person to have a healthy and happy relationship. Experts say that people can change significantly over time, so a deep commitment to always try to work things out is more effective than an attempt at perfect knowledge and flawless alignment before starting. There are similarities in accepting a serious job. I try to hire managers who are seriously committed to helping each of their employees, but every one of these relationships starts with two people who know little about each other. What matters is the consistent effort and commitment to creating a better tomorrow together.

The following is a description of what I call Section I of the framework, titled “Class”.

---

Class

---

Class Creation

Warrior, Rogue, Mage, Hunter, these basic archetypes are always present because they are interesting, clearly defined, and distinct from each other. When writing a job description one should be looking to create such clarity. Just as each job class defines