Lessonly

• Product & Engineering

   Assignments:

  Onboarding buddy

  We provide context through communication boosting productivity leading to new llama satisfaction.

  Full Description

  • We provide context through open communication to provide relevant information to the new llama and encourage a process of continued, self-directed learning.
  • We boost productivity by helping the new llama in many situations based on his/her experience and knowledge to become productive in their role quickly and to help build self-confidence allowing him/her to focus on adding value to Lessonly.
  • We help improve new llama satisfaction by reducing the initial confusion and uncertainty faced by all new llamas.

  Requirements

  • Must have a position with the reach of 2.1 or higher
  • For this role, you must be milestone 1 or greater inCommunication
  • For this role, you must be milestone 1 or greater inProduct Knowledge
  • For this role, you must be milestone 1 or greater inInitiative
  • For this role, you must be milestone 2 or greater inCollaboration

  Examples

  An observation relating to  Onboarding buddy  has not been publicly recognized yet.

  Interviewer

  Growing the team is one of the most important things we do... and we interviewers are responsible for helping to decide on our future teammates.

  Full Description

  Success:

  • You are counted on for two things as it pertains to new llamas joining the pack:
    • Help the candidates get a clear idea of the Lessonly culture as well as the different aspect of the job they are applying for.
    • You'll also be vital in helping the hiring manager assess the candidate across a plethora of criteria

  Details:

  • Attend all on-site interviews for a single position
  • Actively work to give the candidate clarity about who we are
  • Actively work to give clarity to the hirer about your perception of the candidate
  • Understanding of the role the interviewee is interviewing for and the why behind the role
  • Prepared on the general background of the candidate
  • Prepared 2-4 questions based on the role and the candidate
  • Be an active listener. Make sure you are present to the interviewee and not thinking about your life while he or she is talking Here are a couple of thing that I try to do before and during an interview.
  • You listen to answers to see if they follow the values of Lessonly. Ask clarifying questions.
  • When preparing questions, you keep in mind the Lessonly values

  Requirements

  • Must have a position with the reach of 1.1 or higher
  • For this role, you must be milestone 1 or greater inCommunication

  Examples

    Observation created over 5 years ago

  Featuring:Ashley S.Interviewer

  I've been with Ashley as she's been on an interview panel for the first time this week. The cool thing is, you'd never know it was her first time!

  Ashley has been asking really thoughtful questions during the interviews that have helped unearth some great details about the candidates we've been chatting with. Not only that, but I feel like she's communicated with our candidates in a way that is super respectful, down-to-earth, and would make me feel a little more relaxed if I'd been interviewed by her.

  I also appreciate in our debriefs how thoroughly she's thought through the interviews to make sure that we hire candidates that are great culture fits.

  Thanks for being an awesome interviewer, Ashley!

  P&E DBW group member

  We engage in meaningful conversations on ways to help the Product and Engineering team do better work

  Full Description

  Success

  • Do Better Work Groups are a way for anyone on the product team to see something they want to see improved, propose a quest to identify the best solution, and once prioritized make that change happen.
  • You, as a member of a DBW group will be successful if you are a part of inspiring and enabling us to do better work!

  Requirements

  • Must have a position with the reach of 1.1 or higher
  • For this role, you must be milestone 1 or greater inInitiative
  • For this role, you must be milestone 1 or greater inCommunication

  Examples

  An observation relating to  P&E DBW group member  has not been publicly recognized yet.

  Escalation mitigator

  We have a robust understanding of the current state of escalations and prioritize the best ways to reduce them.

  Full Description

  Description

  Escalations are necessary, but expensive.

  • Expensive because of the negative impact on Experience of Lessonly’s Customer Service teams
    • Anytime a customer-facing rep cannot answer a question, resolve a problem, or make a change that enhances the value of our offering to the customer in question, it reduces the overall experience.
  • Expensive because escalations are unplanned work for those that could be otherwise improving the system
    • Every moment that is spent NOT making improvements to the system by someone with the skill, access, and knowledge to make enhancements is less than ideal.

  Key Result(s) / Outcomes

  • Observability
    • Stakeholders strongly agree or agree when asked “I know what the escalation trends are, and understand what we are doing to reduce them (so that we don’t have the same ones that are bugging us today be the same ones we are bugged by 6 months from now)”.
  • Outcomes
    • If the above is true, then we can/will have a quarter-over-quarter reduction in known escalations (as defined by any escalation type that occurs more than once per month for at least 3 contiguous months and/or takes more than a day of any tier-2+ person).
      • There will always be new escalation-needs being added, such is the physics of creating software. The purpose of this goal is that the known escalation-needs are consistently being eliminated.
    • Customer-facing team members strongly agree or agree when asked “I am continuously given ever-improving tools, knowledge, or skills from the Empower Squad and/or the other product squads that help me serve customers directly without needing to ask for help”.

  Requirements

  • Must have a position with the reach of 2.3 or higher
  • For this role, you must be milestone 1 or greater in(QA) System Modeling
  • For this role, you must be milestone 1 or greater inTechnical Investigation
  • For this role, you must be milestone 1 or greater inPrioritization
  • For this role, you must be milestone 1 or greater inDecomposition & Sequencing
  • For this role, you must be milestone 2 or greater inCommunication
  • For this role, you must be milestone 2 or greater inCollaboration

  Examples

    Observation created over 6 years ago

  Featuring:Rick G.We don't wait to be told what to do, we take initiativeWe share before we're readyEscalation mitigator

  I ❤️ this message that is hidden away in a CH story. It tells the full tale of what I'm spotlighting: https://app.clubhouse.io/lessonly/story/26584/understand-escalations#activity-26619

  However, the thing that I appreciate about this, was Rick's conclusions that he put at the end of each question he referenced. That made it so I didn't have to guess at anything nor did I have to try and interpret the intent behind sharing the reports.

  Overall this was excellent.

  The only thing I was left wanting was clear next steps. But even with that need still existing I felt this was more than worthy of highlighting!

  ---

  • Engineering

     Assignments:

    --None--

    ---

    • Product Quality

       Assignments:

      Release Manager

      We are responsible for ensuring our application is updated in a safe, effective, and communicative manner.

      Full Description

      Success:

      • You are responsible for ensuring our application is updated in a safe, effective, and communicative manner.

      Details:

      • TBD

      Requirements

      • Must have a position with the reach of 2.2 or higher
      • For this role, it is recommended to be milestone 1 or greater inBusiness and Technical Translation

      Examples

        Observation created over 5 years ago

      Featuring:Kimberly H.Stakeholder / Feedback ManagementRelease Manager

      https://lessonly.slack.com/archives/C73ND911P/p1582829414005400?thread_ts=1582828748.005100&cid=C73ND911P

      Talk about attention to detail, operational awareness, and excellent communication!

      This was simply fantastic!!

        Observation created almost 6 years ago

      Featuring:Patrick F.We ask clarifying questionsRelease Manager

      Patrick joined the team at the start of this quarter. Now that he has been here a quarter I don't know how we used to operate without him. It is not only his thoroughness when it comes to the stories themselves but he thinks about the "soul" of the ticket. What is this actually trying to solve? Is it solving for the entire problem? His attention to detail is staggering and I am grateful he is on the team.

      He was also instrumental in the xAPI testing. It is a tricky process to test xAPI in a review, staging, and production app. He was ahead of it the whole time and made me feel confident we are releasing something we can have confidence in.

      Quality control tester

      Our goal is NOT to test quality in, but instead to help the team build quality in from the start. Moving QA thinking farther left is our prime directive.

      Full Description

      Success looks like

      • Very few priority-1 and priority-2 defect escapees found in production.
      • You'll be successful at this role if the quality control process is one of collaboration and not tension between tester and coder.
      • You'll be successful at this role if the team learns how to build quality in from the start, a bit more every day.
      • We have this role because it is essential to ensuring a high-quality experience for our users. The goal is NOT zero bugs... the goal is balancing speed with risk management.

      Details

      • Measures like the number of remediations, number of written bugs, number of stories tested are all important, but none of them alone tell the story of the value of this role.
        • If there are no remediations happening, that means the engineers are perfect, or we aren't looking deep/wide enough, or maybe we've found a point where we are writing up shippable priority-3, 4, or 5 bugs but they do not need to block the stories. Alone it doesn't tell the story, but it is an indicator
        • If there are no bugs written, this could mean either the engineers are perfect, or our calibration of what constitutes a bug is off, or if remediations are through the roof maybe we have over-calibrated to what should constitute shippable. Alone it doesn't tell the story, but it is an indicator
        • If the number of stories tested is low... well, you should chat with your manager... not sure what this could mean other than bad things 🤔

      Requirements

      • Must have a position with the reach of 2.2 or higher
      • For this role, you must be milestone 2 or greater in(QA) System Modeling
      • For this role, you must be milestone 3 or greater inBug Writing
      • For this role, you must be milestone 3 or greater inTechnical Investigation
      • For this role, you must be milestone 2 or greater in(QA) Risk Assessment

      Examples

      An observation relating to  Quality control tester  has not been publicly recognized yet.

      Product Quality Assurance Enablement Lead

      We serve the function of Product QA, and those executing against its roles. Our goal is continuous improvement of the tools and processes (balancing autonomy and focusing on feedback loops).

      Full Description

      Success:

      • Those executing against the following roles have a continuously improving set of tools and processes (balancing autonomy and focusing on feedback loops).
        • Quality control tester
        • Technical investigator

      Details:

      • You'll help ensure that testability is a consideration in build, and testers know how to raise it as a concern
      • You'll help ensure that things are testable across environments
      • You'll help ensure that testers have a shared understanding of risk and coverage needs across the app, based on current best knowledge and trends
      • You'll help ensure that testers have what they need from a tooling and clarity perspective to level up at the core testing abilities:
        • Technical Investigation
        • Bug/Story Writing
        • System Modeling
        • Risk Assessment

      Requirements

      • Must have a position with the reach of 3.1 or higher
      • For this role, you must be milestone 3 or greater inProduct Knowledge
      • For this role, you must be milestone 4 or greater in(QA) Risk Assessment
      • For this role, you must be milestone 4 or greater in(QA) System Modeling
      • For this role, you must be milestone 3 or greater inMentorship
      • For this role, it is recommended to be milestone 2 or greater inBusiness and Technical Translation
      • For this role, it is recommended to be milestone 2 or greater inDecomposition & Sequencing
      • For this role, it is recommended to be milestone 3 or greater inTechnical Investigation

      Examples

      An observation relating to  Product Quality Assurance Enablement Lead  has not been publicly recognized yet.