1.7 KiB
1.7 KiB
aliases, Is A, Belongs to, Status, Owner
| aliases | Is A | Belongs to | Status | Owner | |
|---|---|---|---|---|---|
|
Task | 24q4 | Done | person-luca-rossi |
Update team role descriptions
As the team expanded from a solo operation to include person-sara-ricci (editor), person-paco-furiani (sponsor sales), and occasional contributions from person-matteo-cellini (technical consulting), the informal role definitions needed to be documented. This task created clear role descriptions for each team member, including responsibilities, decision-making authority, and communication expectations.
The role descriptions serve as the basis for compensation reviews, goal-setting, and conflict resolution. They also help when onboarding any future team members by establishing the organizational structure clearly.
Acceptance criteria
- Write role descriptions for all current team members (Luca, Sara, Paco, Matteo)
- Define responsibilities, decision-making authority, and reporting lines for each role
- Specify communication norms (async by default, weekly sync, response time expectations)
- Review role descriptions with each team member and incorporate feedback
- Store in the vault as a referenceable document
Notes
- The most valuable outcome was clarifying decision-making authority. Previously, person-paco-furiani and person-sara-ricci would defer to person-luca-rossi on decisions they were fully empowered to make independently, creating unnecessary bottlenecks.
- person-matteo-cellini's role was formalized as a quarterly advisory engagement (4 hours/month) focused on technical architecture decisions for Laputa.
- Role descriptions are stored in procedure-team-roles and will be reviewed annually.