Open LexaMichaelides opened 2 weeks ago
Please add your comments by July 12!
☝️ This looks good to me. The main "concern" I would have is that the consistency reviewer would always end up being the team lead, which is probably not intended.
☝️Well presented. This seems better than what we have today and low risk enough to try.
Proposer: @LexaMichaelides Host: @fastfadingviolets
This new process should be designed to be ongoing, but decisions are not forever and we can always change it if we try it and find ways to improve it.
Constraints:
Participation:
Reminder of some useful distinctions for contributing to the discussion: 🔎 Clarification: asking a question about the content of the proposal (e.g., "can you decline an invitation to be in a review group?")
☝️ Reaction: a comment with no question (e.g., "some people are split across practice areas") -> could be converted to a clarification with care (e.g., "how does a person who is split across practice areas have their L/R reviewed by their team lead?"). Reactions do not block the proposal, even if they are concerns held with strong conviction.
🛑 Objection: a risk or a backward movement for the organization that is backed up by evidence (e.g., has happened before). Objections are different from reactions -- valid objections can and should block the proposal and require the proposer to integrate a solution into the proposal.
Proposal V4
I propose that for Hypha's annual L/R reviews (which correlate directly to salaries), we adopt the following process:
Individual assessments
Consistency and budget checks
Implementation
Roles: Using a different piece of Percolab advice, I've tried to describe the people who would fulfill certain functions in the process. This could be one person, or a group of people fulfilling the role. What matters is that, within the org, we can fill each role at the start of the process.
Operationalization log Bullet list of implementation details to figure out which are not necessarily part of the proposal: