Description
Writing is a critical skill that is important across all roles and positions.
The only reason this isn't active is that we have to write good criteria for the description and milestones.
Milestone 1
I have observed this person showing a consistent, comfortable, continuous, and clear positive impact to a squad when wielding this ability, and therefore I would put them in situations where they can employ this ability with only a small amount of guidance
Milestone 2
I have observed this person showing a consistent, comfortable, continuous, and clear positive impact to a squad when wielding this ability, and therefore I would put them in situations where they can employ this ability, with no assistance as well as being a trusted active or passive mentor to others
Milestone 3
I have observed this person showing a consistent, comfortable, continuous, and clear positive impact to multiple squads when wielding this ability, and therefore I would put them in situations where they can employ this ability as well as being considered an expert within this discipline
Milestone 4
I have observed this person showing a consistent, comfortable, continuous, and clear positive impact to a squad when wielding this ability, and therefore I would put them in situations where they can not only employ this ability but where they set the tone for this at the company level
Milestone 5
I have observed this person showing a consistent, comfortable, continuous, and clear positive impact to not just internal teams but the community/industry in general when wielding this ability, and they are recognized by the community/industry as an expert
Configuration Health
- ✅ Associated with 3 roles
- ✅ Has been referenced in 1 piece of public recognition
- ℹ️ No one has achieved a milestone on this ability
- ⛔️ Last updated: almost 6 years ago
- ℹ️ Last conversed about: almost 6 years ago
Role & Position Requirements
- Feature Documentersmust be milestone 1+
- Launch Coordinatorsmust be milestone 1+
- Squad Progress Communicatorsmust be milestone 2+
Examples / Observations
Observation created almost 6 years agoFeaturing:Raphael A.We put learners firstWe inspire others to do better workWe don't wait to be told what to do, we take initiativeWe put the team before ourselvesCopywritingFeature DocumenterDocumentation is vital for a software company. That is true for all aspects of our app but particularly user management. Lessonly cannot exist without learners, so the action of making it clear and easy to get users into Lessonly is important. Even though I know all of that creating documentation can be seen as the least fun aspect of software. It is more fun to build new stuff than to write in painstaking detail about the stuff you just built.
With all of that being said, it only makes what Raphael did more impressive. We recently wrapped up the development of SCIM for OneLogin. We were left with the documentation piece. I tried my best to get it started but we reached a point where we had to set the JSON user schema and I was lost. Raphael (who got involved late to the project) was able to familiarize himself with the code base and write some killer documentation (found here: https://docs.google.com/document/d/1zaEPLM1wtiDHBth9owIG29R2c-3oYWq04jPtxvH-5P0/edit#)
This is the definition of a team player. Hopping onto a project and helping out any way you can no matter what. Raphael has always been game for these sort of things but I was reminded again by this.
Conversations about Copywriting
This section is for Lessonly folks only. Sign your team up to find your Gruuv!