Lessonly's Assignments

• Positionsare simply the titles, which represent the expected reach (team, department, company, etc) each employee is expected to have at Lessonly.

These are critical to ensure consistent and therefore fair pay (each position should have a small salaray range in which everyone is paid within)

• Assignmentsare a collection of responsibilities needed for Lessonly teams. What outcomes and impacts your teammates can expect from you

• Abilitiesare the tools we value/recognize at Lessonly. They are the tools you need to complete those role responsiblities... HOW you do it

• Valuesare the aspirations we strive for at Lessonly

More details about Assignments, including tips on how to organize themHide details

Many organizations do not delineate between an employee's Position, and the Assignments they take on.
OG believes that even though this standardization / uniformity might seem simple and harmless, it is actually devestating to clarity.
This is true for one simple reason... no two people are the same! So we should stop trying to drive more and more uniformity onto our workforce... we should lean into an individual's strengths and helpt them self-organize to form unbeatable teams!

However, this does not mean we have pure chaos. It means that if we break down the work that needs to be done into collections of responsibility, we can sanely and simultaneously give employees a unique-to-them job description and have a well-oiled team with no responsiblities falling through the cracks.

This is what Assignments are; hats you wear that represent the expectations or the specific set of responsibilities to a project, squad, team, department, or Lessonly as a whole.

Another downfall that organizations who do not distinguish between a person's standardized set of responsibilities (one role = your position) suffer from is that this rigidness doesn't take into account the fact that your responsiblities shift and morph over time.
Sometimes an engineer will play part of a product owner role. Sometimes a technical product manager will take on a role that is usually completed by an engineer. This is the key to clarity!

Assignments should be building blocks of clarity, that can be expertly combined to put folks in a position where they can utilize their strengths every day.

So when should you separate out a Assignment?

• Is this collection of responibilities always done by a single person? It likely should be one role.
• Is there a realistic situation where it would be played by two separate people? It likely should be split!
• As a manager, do you have folks that do excellent on a few of the responsiblities, but need improvement on others? Consider splitting so that you can be clear in your feedback!

Unstated expectations are resentments waiting to happen.

Therefore, OG strives forClear Expectationswhich leads to great habits, which leads to the team flow state, which leads to theLessonly Gruuv!