Explore Lessonly's Assignments

Choose Organization Growth Framework
Exploring Lessonly's growth framework
Choose Starting Position
Starting with the position: Product Manager - 4.3 (aka Director, Product Management) (Check out Product Manager - 4.3)
Choose Assignments
Now it is time for you to build your unique job description! Simply go through and add a checkmark next to all of the Assignments you'd want to take on.
Click to copy the URL to share this exploration

Showing only relevant Assignments

  • Lessonly

     Assignments:

    We engage in meaningful conversations on ways to help the Lessonly organization do better work.

    Full Description

    We engage in meaningful conversations on ways to help the Lessonly organization do better work.

    • For example, we may take part in the following initiatives:
      • Connections Committee
      • Diversity and Inclusion Advocates
      • Marketing Blog Blitz
    Requirements
    • Must have a position with the reach of 1.1 or higher
    • For this role, it is recommended to be milestone 1 or greater inInitiative
    • For this role, it is recommended to be milestone 1 or greater inCommunication
    Examples
      Observation created about 5 years ago

    Over the last couple of weeks, Casey and I have had some great conversation about how things are going. There are things that she was willing to tell me that i needed to hear. She also was interesting in hearing some of the things I had to say. She is interested in how I am doing as well as my opinions of our organization from a fresh perspective. This not only shares how she cares about me as a person, but about the place show works. This is an interaction that is outside her reporting structure, but she cares


    • Product & Engineering

       Assignments:

      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.

      We are obsessed with the intersection between product usage metrics (such as weekly active usage) and business metrics (such as renewal cycles). Our prime objective is to identify quantitative evidence that will help CX, services, support, and product make better decisions about how each of them serves our customers

      Full Description

      Key Result(s)

      • Quantitative evidence plays a vital part in opportunity prioritization
        • ... as measured by qualitative feedback from the Opportunity Shapers
      • Insights are uncovered that helps better support our customers
        • ... as measured by qualitative feedback from the post-sales customer-facing teams (Account Management, Customer Support, Professional Services, and Customer Implementation)
      • The bi-weekly metrics all-hands has easy to understand, and clearly impactful metrics that Product can share with the rest of the organization to inspire excitement and provide clarity into the impact of the work

      Details

      Things you might deliver/do

      • We are responsible for understanding how Salesforce data, when blended with Product-usage data, impacts our ability to better understand and potentially even predict the business outcomes
      • We are responsible for doing the exploration needed to empower CX to make even better recommendations to customers about their training program effectiveness
        • Helping CX uncover patterns in how the best-performing programs function so that they can help their customers better.
      • We may partner with operations on deciding on and maintaining the business intelligence tooling (think Tableau or other BO tools)

      • If the data does not exist that we need to be able to answer a question, you are relied on to help prioritize modifying the platform to allow for the data to be captured, or captured in the proper format.

      Illustrations

      • This excerpt from the book Inspired is a well-written summation of the expectations and value of this role:
      Requirements
      Examples
        Observation created over 5 years ago

      hjkhkj

        Observation created about 6 years ago

      https://lessonly.slack.com/archives/C047M50C0/p1568211454034800

      LOVE THIS!

      Unexpected, but valuable. Keeping the most important thing, the most important thing. Which is...

      Are we allowing people to do better work with the things we build.

      Usage is a leading indicator to this.

      Thanks Justin!

      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

      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!

      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.

      We are the ones that bring organization and clarity to the Discovery process.

      Full Description

      Discovery can be tough given your goal isn’t to deliver an artifact, but instead to deliver continuous learning. We are responsible for ensuring our Discovery Crew always has the next step, regardless if it is desirability, feasibility, or viability, we are the glue that holds a Discovery Crew together.

      Key Result(s) / Outcomes

      • Learning frequency/cycle-time, meaning there is clarity as to where we stand on the following three constructs, and we are continuously moving forward in all three:
        • Value: Will the overall solution be desired and useful to customers?
        • Feasibility: Can our delivery crew build what we need with the time, skills, and technology we have?
        • Viability: Will the overall solution have the desired business outcome?
      • Learning clarity
        • ... what value/unmet need/opportunity are we aiming to impact?
        • ... who is doing what to ensure we are focused on bringing clarity to the value goal?
        • ... when is our next major milestone, and what blockers are in the way
      • Discovery crew cohesion
        • Squads have two sets of crews within them… delivery crews and discovery crews. You are responsible for making sure that everyone on the discovery crew feels connected, informed, and supported (this slide has been used in the past as a way to help ensure alignment).
      • Stakeholder management
        • Consulted Stakeholders (PSC or POC members) should feel confident in the progress and direction of the discovery.
        • Informed stakeholders (all Lessonly employees, but specifically those that attend Team Shares and rely on the #Product-Weekly-Updates) should feel confident in the progress and direction of the discovery.

      Submit change suggestions in this GDoc

      Requirements
      Examples
      An observation relating to  Discovery Manager  has not been publicly recognized yet.

      We are obsessed with product usage metrics because they are the leading indicators of how successful our squad, software, and the company are.

      We believe the influence of data is critical in nearly all decisions, from how successful a feature is... how successful a campaign is... how successful a type of customer is … how successful a launch is.

      Full Description

      We believe the influence of data is critical in nearly all decisions, from how successful a feature is... how successful a campaign is... how successful a type of customer is … how successful a launch is.

      Success looks like:

      • Quantitative evidence plays a vital part in product solution design
        • ... as measured by qualitative feedback from Solution Designers
      • Insights are uncovered that helps better support our customers
        • ... as measured by qualitative feedback from the post-sales customer-facing teams (Account Management, Customer Support, Professional Services, and Customer Implementation)
      • The bi-weekly metrics all-hands has easy to understand, and clearly impactful metrics that Product can share with the rest of the organization to inspire excitement and provide clarity into the impact of the work
      Requirements
      • Must have a position with the reach of 1.1 or higher
      • For this role, you must be milestone 1 or greater inData
      • For this role, it is recommended to be milestone 1 or greater inDesign Collaboration
      • For this role, it is recommended to be milestone 1 or greater inProduct Discovery
      • For this role, you must be milestone 2 or greater inProduct Knowledge
      • For this role, it is recommended to be milestone 2 or greater inInitiative
      Examples
      An observation relating to  Product engagement analyst  has not been publicly recognized yet.

      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
      Examples
        Observation created over 6 years ago

      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--

        • Development

           Assignments:
          --None--

          • Tech Leadership

             Assignments:

            We are all about helping the squad to get stuff live faster and more predictably, not by cracking the whip but by removing obstacles that get in the way.

            Full Description

            This excerpt from Marty Cagan's book Inspired speaks to the success of this role better than we could:
            "Delivery managers are a special type of project manager whose mission is all about removing obstacles—also known as impediments—for the team. Sometimes, these obstacles involve other product teams, and sometimes they involve non‐product functions. In a single day, they might track down someone in marketing and press them for a decision or an approval, coordinate with the delivery manager on another team about prioritizing a key dependency, persuade a product designer to create some visual assets for one of the front‐end developers, and deal with a dozen other similar roadblocks.”

            Key Result(s) / Outcomes

            • Blocker/impediment management/removal
              • Creates an environment where raising blockers/impediments is safe
              • For each of the active work-in-progress stages of the story workflow, we (the squad) get a B or higher as our score
              • If we are NOT meeting a B, we have a plan identified or are working on a plan to get to a B in a particular story stage
            • Checkpoint and Quarterly delivery goals are hit > 90% of the time
              • If applicable for your squad, Daily and/or Weekly goals are also hit > 90% of the time
              • Communicated effectively with the Epic Shaper and Squad Progress Communicator
            • Squads are able to answer forecastability questions, such as:
              • What is our squad’s current capacity?
              • What capacity do we gain if we add folks?
              • What capacity do we lose if we remove folks?
              • What is the current risk of ongoing projects?
              • How confident are we in the above answers?
            Requirements
            Examples
              Observation created over 5 years ago

            https://lessonly.slack.com/archives/C8UPX4UPM/p1581707334029900

            I don’t think I need to add more to this.

            This post was so clear, and inspired a tremendous amount of confidence that we are truly believing in the feedback-loop philosophy.

            Well done y’all, well done!

              Observation created almost 6 years ago

            https://lessonly.slack.com/archives/G8Q5B0EVA/p1580215718016900

            In my opinion, this is a big part of what delivery management is about.

            • Who can help? Architects
            • Why is it important (with some color in there for good measure)
            • Who will benefit (specific, and playing at folks' emotions)

            Loved this!

              Observation created about 6 years ago

            https://lessonly.slack.com/archives/C8UPX4UPM/p1571263756008600

            This note starts with a dose of awesomeness with a call out to the momentum. Therefore bringing brightness to the room, while about to have a semi-difficult conversation.


            I really appreciated the fact that the following message made me feel unworried, because I believe there are clear indications the squad has their eye on the ball with statements like; "slowed down by two back-end blocker stories... merge conflicts". Talk about delivery operational awareness!


            Reflection without a gameplan for change is often pointless. So I was thrilled to read things like; "if we can get those into review tomorrow morning and be proactive about seeking reviewers". This shows a plan and how the plan differs from what we might have been doing.


            Then with statements like this; "I think we can have all of Epic 1 done by end-of-week and start testing with customers on Monday. @adam, I'm sure you're eager for this, so I'll keep you posted on our progress tomorrow."
            ... it exudes a quote I love, which is

            Keep the most important thing, the most important thing.

            In this case, the most important thing is getting working software in the hands of our customers so that we can keep the learning going strong! This reminds me of a Jeff Gothelf quote

            Keep measuring and learning even after you ship.
            ... it’s all discovery and we learn from everything we make; be it a paper prototype, or the next feature in your production software. I agree with him.

            🙌🏾


            This is a great example of us calling out when we are behind, when we are ahead, and when we are on pace, and what is the most important thing for us. Delivery management = operational awareness = self and squad accountability = excellence.

            I think overall the squad was a little behind their goals at the time of writing this. I'd love to see us lean into that difficult conversation a bit and express the psychological safety and clarity that comes with simply stating it plainly. The goal isn't perfection, the goal is alignment, togetherness, and communicating reality so that we as a tribe can react, learn, and grow from the highs and lows of our journey.


            It ended in such an inspirational way that I'll end this with that same sentiment:

            Let's keep up the momentum, and keep helping each other out tomorrow! :fire:

              Observation created over 6 years ago

            I had a few high priority stories that were in need of remediation. Haley kindly picked up one of them for me and in the course of doing so discovered that there was some weirdness with the story. It's been more of a headache then the original remediation seemed to suggest and I am really grateful for her picking it up and sticking with the story.

      • Management

         Assignments:

        Our sole goal is to help fill the top of the funnel with "Hell Yeah" candidates

        Full Description

        Key Result(s) / Outcomes

        There isn’t a formal quantitative measure, however, once you are in a leadership position, recruiting becomes at the very least a passive part of your job.

        It does not mean it is a primary responsibility, or that you are running the recruiting process. It does mean that you are making time to have conversations with people outside of Lessonly for networking purposes. It does mean that when you do have an active opening, you are helping the Talent team member and if you have time you are proactively reaching out to candidates to have discovery calls before officially putting them in the process.

        Details:

        • Work with the hiring manager to identify the ideal candidate profile
        • Coordinate with the other recruiters for the given position to ensure you are not all reaching out to the same candidates
        • Devise relatable messages to send to prospective candidates that paint a clear picture of what the opportunity is
        • Cultivate relationships with the community to ensure we have a great pipeline of candidates when positions open back up
        Requirements
        • Must have a position with the reach of 1.1 or higher
        Examples
        An observation relating to  Recruiter  has not been publicly recognized yet.

        We strive to influence those we serve to achieve their own goals as well as their work goals via clarity, trust, accountability, empowerment, and being an example of the Lessonly values and definition of an ideal team player.

        Full Description

        There are three aspects to technology management at Lessonly. The core philosophy that all Lessonly managers adhere to. Systematizing clarity with appreciative inquiry and feedback loops. Mission control, meaning a focus on outcomes in nearly all we do.

        We will end this description with some examples of measures that technology managers will be held accountable for.

        The core philosophy

        The Lessonly Management philosophy is the underlying engine behind everything else within this role. This lesson is the source of truth for this philosophy.

        Positions that require this role will be required to have achieved an early milestone of the required abilities for the craft of your domain, to help us make good decisions for our teams.

        Positions that require this role will be required to have achieved a milestone 3+ for business knowledge to help ensure we can give good context to our team goals.

        Positions that require this role will be required to be milestone 3+ for {mentorship} and {community}, given how vital it is for us to care for the person more than the employee.

        These are the most important aspects of management at Lessonly, however, there are three other keys to success for management on the technology team.

        Systematize Clarity

        Another critical aspect of Lessonly management is seeking clarity (finding out what is working) and giving clarity (ensuring folks know what matters most and why it matters).

        Within the tech team, we do that in various ways. One of those ways is seen by the fact that positions which require this role will also be required to be an enablement lead for the appropriate domain, to ensure we are continuously working through this clarity feedback loop.

        Systems with feedback loops are a great way to ensure accountability. Accountability to those we serve… being able to hold those we serve accountable, as well as accountability to our teammates. Knowing we can rely on each other.

        Balancing autonomy and alignment to make room for innovation...

        Building systems with feedback loops so that it is clear what winning is…

        Leading with the principles of appreciative inquiry…

        These are all vital for the thought work which we are responsible for. Our work product isn’t physical, and can’t be measured purely quantitatively. This means it is on us to foster an environment that embraces uncertainty… encourage a team that embraces constantly changing definitions of clarity… a culture that embraces continuous improvement.

        Mission-Control… means focus on Outcomes

        We are laser-focused on iteratively, continuously, relentlessly adding value to the vision of making continuous training possible for all customer-facing teams.

        The best way to do that is to be continuously learning and improving.

        Outcomes, as opposed to outputs or activities, ensure we are all aiming at the same target/rowing in the same direction.

        It also gives freedom to have trial and error, which is one of the most tried and true ways to have lasting growth.

        Types of managers

        The Lessonly technology team greatly values flexibility and adjusting strategy (how we organize to solve problems) based on the strengths of the individuals on the team(s) in question. Therefore, the positions which require “people management” (or the term I prefer, accountable servant leadership), will also not all look the same. Here is a non-exhaustive list of some potential types. \

        Key Result(s) / Outcomes

        • Onboarding effectiveness
          • Time from hire date to a non-apprentice (achieved all of the appropriate milestones) on all of the required roles for the position. Ideally, 3 months from hire.
        • Career journey guidance effectiveness
          • When those you serve are asked the following question, 80%+ of them (strongly) agree: “When I look back from a year ago to where I am now... what I have achieved… how I’ve grown, I am excited about the progress I’ve made”.
        • OfficeVibe 10 key drivers
          • We do not hold anyone accountable for these measures directly, because it incentivizes behaviors we don’t want to incentivize… however, managers will have access to and should be aware of the opportunities of things we could do as well as the impacts of the things we have done on these measures. So the measure here is awareness of and a plan of action around this employee engagement data.
        Requirements
        Examples
          Observation created almost 6 years ago

        I want to give a well-deserved shout out to our awesome engineering managers.

        First off, to Brea, who is making a point spending time getting to know each and every engineer on the team personally. It's really helped me to feel valued by her, and I'm sure will help her relationships with her reporting engineers start off a lot more smoothly. There are a million things she could be doing to be learning about Lessonly, our codebase, how managers here work, etc, but the fact that she has spent time getting to know us (and at more than a group level) shows me that her people are her biggest priority and that's huge. Thanks Brea!

        And then of course to Casey, who has been working tirelessly as the solo manager for months now and, even though I wasn't here for most of those months, I feel confident saying she probably never complained. In the time I've been back since being on leave, I've been impressed at how she manages to meet with all of us, answer questions, write up stories, do code reviews, lead hiring, and still manage to be her positive, happy self that we have all come to appreciate. Thanks, Casey, for being a great manager while also leading and lifting up the team in so many ways. We are glad you decided to spend your superpowers on us here at Lessonly. :)

          Observation created about 6 years ago

        This morning, Gardee reached out to me with the following message:

        Hey Hey! Each quarter I work with --name is redacted-- on gathering feedback from teammates they work with day in and day out. Given that, I wanted to see if there were any observations/feedback (I took a look in ourgruuv already but wanted to ping for any additional things) you would like for us to discuss :slightlysmilingface:

        HELL YEAH!!!

        Way to be a proactive manager and go out and gather the feedback.

        Some might wait and see... others might try and have an in-person convo, but asking in a digital forum allows the person you are asking to take their time and give thoughtful feedback.

        Also, asking for observations shows that you want things that are actionable and not judgments that we are forced to unpack.

        I love, love, love this as an example of ways a manager can help their folks grow.

          Observation created over 6 years ago

        Wow... just wow.

        First, she tried something new, and added clarity as to how the new thing should flow:
        https://lessonly.slack.com/archives/C8UPX4UPM/p1564432055022900
        https://lessonly.slack.com/archives/C97TXG1PW/p1564432252002200

        Then, the retros happened... all three of them (I wasn't there, so I can't say how they actually went, but as an outside observer, I was impressed with what happened).

        Then, she didn't let the things that were discussed die on the vine... no, she took it upon herself to write up the note for all three, with clear actions, and clear ownership of who is going to take on which actions:

        https://lessonly.slack.com/archives/C97TXG1PW/p1564675008018100
        https://lessonly.slack.com/archives/C8UPX4UPM/p1564675014002100
        https://lessonly.slack.com/archives/C97TXG1PW/p1564670582013700

        I'm damn near in tears of pride and excitement (I cry a lot, so tears of joy, sadness, and pride are relatively common, but I will say they only come when something in the world hits me in my soul).

        Here's why...

        I've tried retros of all shapes and sizes. I've hated retros of all shapes and sizes. They are often well-intentioned, but it is really difficult to get a group of adults to open up and share in such a way that useful progress can be gleaned from it.

        When looking at the result of this, I think of our value of critique, not complain. Clearly, what happened in those retros is people opened up, put themselves out there, and critiqued and not complained! I see no way clear action items like this could be found without that happening.

        This shout out is aimed at Casey, but let's be clear, I'm thrilled with the vulnerability and teamwork that had to be shown by the entire Practice and Tech Services squads. Also, I Casey got the idea for this new format from Aaron (:highfive: man!!)

        Casey, it has been amazing to work with you from day one, and every day I am a bit more in awe. Thank you for being you!!

        Let's keep it rolling... ONWARD!!

        Our goal is, by continually refining the design of the org, to give the department as a whole the best chance of success

        Full Description

        Success:

        • You'll look at each squad and it's evolving mission, combined with the organizational goals, combined with budget and current personnel status and continually work on devising plans that give each squad the best chance of success.

        Details:

        • You'll ask yourself... do squads have what they need to be successful from a policy and personnel perspective?
        • You'll propose net-new roles and positions (such as software support engineer, when the needs of tech services became clear).
        • You'll re-establish the measure of success for positions, such as changing tech services into essentially three sub-squads, with the goal of making things smoother.
        Requirements
        • Must have a position with the reach of 3.2 or higher
        Examples
        An observation relating to  Squad organizational design architect  has not been publicly recognized yet.

        Bringing new folks into our tribe is one of the most important activities any of us will do. We ensure a good candidate experience, a great interviewer experience, and ultimately a talent/opportunity fit we are excited about.

        Full Description

        Success:

        • Facilitating the hiring process such that candidates have a pleasant experience (as measured by things like Glassdoor reviews).
        • Making decisions on who we will make offers to, such that the talent/opportunity fit is high.
          • Meaning the fit is great for them and the direction they are wanting to take their career, and Lessonly and the direction we are wanting to take the squad/discipline/department/company.

        Handbook:

        • You are responsible for getting the job posted
          • Drafting the job description and working with Talent to have it posted on lessonly.com/hiring and appropriate job boards
        • You are responsible for the interview structure
          • Identifying the interview team
          • Setting the interview structure
        • You are responsible for managing candidates in the workflow and communication
          • Making the decision on which candidates will progress to which states
          • One specific communication requirement is that within the Clubhouse card representing a position you are hiring for, you are required to post a weekly update similar to the following:
            1. Applications actively being reviewed: All-time: ## | In-Progress: ##
            2. Theresa Interview: All-time: ## | In-Progress: ##
            3. Woven Work Simulation: All-time: ## | In-Progress: ##
            4. Hiring Manager Interview: All-time: ## | In-Progress: ##
            5. Final Interview: All-time: ## | In-Progress: ##
            6. Offers Sent: All-time: ## | In-Progress: ##
        • Making the final hire recommendation (making the offer by working with the P&E Talent representative as well as the {budget/comp manager} if you are not taking on that role).

        Incomplete Lesson - Hiring Manager’s Handbook

        Requirements
        • Must have a position with the reach of 3.1 or higher
        • For this role, you must be milestone 3 or greater inMentorship
        • For this role, it is recommended to be milestone 1 or greater inCommunity
        Examples
          Observation created about 5 years ago

        I'll post the original message at the bottom (can't link because it was a DM).

        This is how it should be done!!! What is it? Setting up interviewers for success. A few specifics:

        1. Brea had to turn around a hiring gameplan in hours because of a non-usual situation with a specific candidate... and did so!
        2. Brea gave clear background and context to what is happening in the interview
        3. In an effort to ensure the interview is as smooth as possible, she assigned each person with a specific value, skill, behavior, or knowledge she wanted them to check for.
        4. Finally, she was aware enough to realize that since folks probably weren't used to our new ATS, that she should give a bit of guidance/training on that as well.

        Overall an excellent way to set up an interview for success. An excellent show of adaptability given the time frame this was all put together under.

        The time crunch isn't something we will get used, to but damn does it feel good to know we can rely on each other to step up when needed to kick it into a higher gear temporarily.

        Well done!

        Good morning and Happy Thursday! We have an engineering candidate, [redacted], joining us Friday. :tada: He’s interviewing for a Senior Software Engineer position (his focus will be on SRE and data needs to start and eventually help us grow a data team). [redacted] has interviewed with Lessonly previously about a year ago and was offered a position the timing didn’t work out. Here’s some more info about him:
        Jobvite Summary: [redacted link]
        Woven Results: [redacted link]
        LinkedIn: [redacted link]
        Here’s an overview of Friday’s schedule:
        09:30 AM to 10:00 AM, Conversation with: Brea
        10:00 AM to 10:45 AM, Technical/Culture Interview with: Tyler, Kristina, and Makenzie
        10:45 AM to 11:00 AM, Break
        11:00 AM – 11:45 AM, Culture Interview with: Kim, Ashley, and John
        11:45 AM to 12:00 PM, Break
        12:00 PM to 12:30 PM, Hiring Manager interview with: Brea, Andrew, and Theresa
        Let’s take the following parts of the scorecard as our focus areas for interview questions. Feel free to ask questions that don’t focus directly on these areas after you’ve covered these areas - also feel free to swap with someone if you want. Let me know if you have any questions!
        @kim

        • Business and technical translation
        • Prioritization @Ashley
        • They work to meet deadlines, and if they can’t, they proactively communicate progress and make a plan
        • We have difficult conversations @John
        • They have strong opinions weakly held (No brilliant jerks)
        • They are willing to give and receive both critical and appreciative feedback @tyler
        • Troubleshooting/debugging
        • Technical Investigation
        • Prioritization @Kristina
        • Collaborative
        • Mentorship
        • Comfortable with change
        • Empathy @Makenzie Bontrager
        • They recognize when to ask for help and when to utilize their resources effectively
        • Self-awareness
        • Initiative A few notes on Jobvite since it’s a newer tool not widely used: Please login ahead of time by selecting the first link in the calendar invite and make sure you can see the Evaluation Form. If you have issues logging in, let’s chat. All fields on the evaluation form are required to submit it, so please select NA for those you don’t have a strong opinion on. I’ll be putting a quick debrief meeting on the calendar here shortly, and please let me know if you can’t make it Friday so we can find a replacement. Thanks! Brea
          Observation created over 6 years ago

        Hiring is hard.

        It is time-consuming, it is nerve-wracking, and it is easy to get overwhelmed with the work of shepherding candidates through the process.

        However, it is the single most important thing we can do to continue our journey to be the greatest product team so that we can help fuel the greatest organization which is here to push forward one of the greatest missions of our time :-) (couldn't help myself :-) )

        When someone comes in and finds a way to improve any part of it, I'm thrilled.

        In this case, Rick posted an update from the week of what was done, and where his head is at.

        https://app.clubhouse.io/lessonly/story/29768/hire-product-quality-engineer#activity-30491

        That is HUGE... and here's why... clarity and transparency are better work.

        We love transparency here. So, posting an update like this directly impacts folks' ability to follow along and be a part of the process. Also, anyone who is interested never has to ask "where are we with that", because it is in the right place, it is concise, and it is clear.

        :spidey-dance:

        Great job man... keep it up!

          Observation created over 6 years ago

        We're currently hiring not one but two mid-senior engineers, for which there's a lot of competition these days. I saw on Twitter yesterday that an engineer I admire had just been laid off and could could be a fantastic addition to our team. I let Casey know (she's the hiring manager for this position) and she followed up that day via Greenhouse and even replied on Twitter, referencing one of the candidate's blog posts she enjoyed for a personal touch: https://twitter.com/case_eee/status/1135723324414341127

        Compared with other teams who responded to this person with a generic "We're hiring" message, Casey's prompt and thoughtful response made me feel proud of how she represented our team. And of course the goal here—bringing folks we can all learn from and growth alongside on to our team—has a direct impact to each of us. Thanks, Casey!

        We are the trusted facilitators of some of the most sensitive data we have within the organization... the budget and salaries. Our goal is fair, consistent, responsible, and equitable decisions regarding budget management.

        Full Description

        Success:

        • You are a trusted facilitator of some of the most sensitive data we have within the organization... the budget and salaries.
        • You help ensure we live our value of having an equitable compensation strategy. Including but not limited to:
          • Base compensation
          • Bonus compensation
          • Spot bonuses (such as Llama bucks)
          • Expenses (including lunches, books, etc)
          • Work-related incentive compensation aka stipends (such as incentives for working holidays or for volunteering for on-call)
        • You are trusted to converse with and explain compensation decisions to your direct reports, and when called for to a larger audience.
        • All employees for which you are responsible (strongly) agree to the following:
          • I am paid fairly within the industry for my position
          • The incentives and stipends inspire me and show that the organization cares

        Details:

        • Must have an understanding of the budget process.
        • Must have an understanding of the basics of the Lessonly business from a financial standpoint
        • Must have experience or a strong desire to research and synthesize market data as it pertains to compensation
        Requirements
        • Must have a position with the reach of 3.1 or higher
        Examples
          Observation created over 5 years ago

        asdf

      • Product

         Assignments:
        --None--

        • Product Delivery Management (Product Ownership)

           Assignments:

          As an organization, we launch together. That means alignment and unity across multiple departments. Within the P&E team, we have special responsibilities to ensure the success of a monthly product launch. We, launch coordinators, are the captains of the product launch journey we take every month.

          Full Description

          Success: Monthly launches

          • All of the features launching are in demo accounts 3 weeks prior to the launch date
          • All of the features launching launch on-time
          • Usage goals (as defined by the squad) are defined and measured against post-launch

          Details

          Things you might do/deliver

          • Launch Epic that includes the details of what is launching, when it is launching, and the overall launch plan
          • Launch Stories that include:
            • Rake tasks to enable features in proper customer accounts
            • Demo account preparation and seeding of data if needed
            • Feature flag organization and cleanup
          • Define usage goals of the features that are launching
          • Measure against usage goals post-launch and communicating the results to the organization
          • Help the product operations committee finalize pricing and packaging, and then help enablement with what they might need in order to effectively enable on it.
          Requirements
          Examples
            Observation created about 5 years ago

          https://lessonly.slack.com/archives/CGS75SABY/p1599838143066600?thread_ts=1599837460.065700&cid=CGS75SABY

          Outcomes, baby, outcomes!!!

          We don't do actions and create outputs for our health... we do it to change human behavior... we do it to make people's lives better, / easier.

          Something as simple as having screenshots in the product board roadmap card made a big impact and reinforced a habit (that the answers AEs and AMs are looking for might just be in the roadmap).

          I love the opportunity to shout out outcomes as opposed to activities and outputs. So I'm thrilled to write this OGO. Well done!

            Observation created almost 6 years ago

          Alec has been working on creating a presentation to demo the new Usernames functionality to the company - as a part of that, he iterated on what the presentation was going to consist of. There are many great aspects of the presentation that include: outlining the why behind the investment, shouting out the individual team members who were a big part of the success of that project, and lastly the CUSTOMER TESTIMONIAL!

          It is one thing to acknowledge great work on delivering a feature into reality BUT it is another to understand and share what impact the feature is going to have on our customers. This shoutout is for Alec in seeking out and getting a customer to record a video about the value that the Usernames feature is going to provide to our customers. This gives energy to our internal team who built this, those who will support it, and those who will sell it!

          Here is the presentation with the customer testimonial: https://docs.google.com/presentation/d/1lUMJ6CEe6hKN0Me056VGEZ7cf47pPxA9zLQnJ7lxfIQ/edit#slide=id.g58bf794290_0_61

          We serve the function of Product Delivery, 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).
            • Epic backlog groomer
            • Blocker buster
            • Launch coordinator

          Details:

          • You know the value of low dependencies, and as such will help identify and reduce dependencies between epics (keep things small and smooth)
          • You know that done means in production, and therefore will help coordinate timing with testers (e.g. looking for things with delivery date targets and communicating with testers on test progress)
          • You have a view into the cross-squad release goals and can help ensure we meet our commitments (monthly releases and marketing campaigns)
          Requirements
          • Must have a position with the reach of 3.1 or higher
          Examples
          An observation relating to  Product Ownership Enablement Lead  has not been publicly recognized yet.

          We are all about identifying solutions for customers and prospects so that they can get to value faster with Lessonly

          Full Description

          The Account Executive/CX Manager will be the primary person building a relationship with the prospect. The solutions consultant will assist by running pilots and digging deep into the needs of the prospect/customer. You as a solutions engineer are the most technical and product-knowledgeable person of this three-person cross-functional sales squad. Your goal is to answer questions about “how might we” be able to meet the needs of this prospect/customer with existing platform configuration options

          Key Result(s) / Outcomes

          • Time-to-value
            • Accelerating the pre-sales process
              • [Required] The average ticket resolution time for a pre-sales support request to an engineer is at or below our 3-day goal of resolution
              • [Nice-to-have] For deals that require a touchpoint with a solutions engineer, the average sales cycle time is below the current cycle average of 60 days
            • Accelerating the implementation process
              • [Required] The average ticket resolution time for an implementation request to an engineer is at or below our 3-day goal of resolution
              • [Nice-to-have] The average time of implementation is reduced from the average of _ days when a customer requires working with a solutions engineer
          • Clarity of possibility
            • [Required] We will survey the AE or CXM that asks for a solutions engineer, and our ultimate goal is that we stay below 5% of the engagements answers (D) from below:
              • A Solutions Engineer was brought into your pre-sales or implementation discussion with a customer or prospect. Which of the following best describes the outcome:
                • A: A solution was identified for my customer or prospect using existing Lessonly functionality
                • B: A potential acceleration was identified and evaluated on behalf of my customer or prospect
                • C: It was identified that the customer or prospect request isn’t in alignment with our vision and work and therefore we wouldn’t support the request
                • D: None of these three above items were accomplished
          Requirements
          Examples
            Observation created almost 6 years ago

          This is on behalf of Rachael Hartsell (member of the CX team) and a shoutout she gave at the all-team. Today Alec hopped on a call with one of our champions to talk about some SFTP solutions. We had talked about some solutions beforehand and while we are on the call Alec was asking questions of the customer. He proposed another solution that we had originally built for one of our customers that I wasn't aware about. The fact that he was so prepared and based on he was able to suggest a solution based on what the customer said in the moment.

          We ensure it is clear and accessible for stakeholders to know the answer to "where are we with that project?"

          Full Description

          Key Result(s) / Outcomes

          • We hit 80% of our internal early adoption goals for the labs account
          • Only 3 "shoulda been in the lesson" questions needing to be asked per checkpoint across all squads (Weekly Product Updates) via Ask the Expert
          • Only 1 "shoulda been in the roadmap" questions needing to be asked per checkpoint across all squads

          Details

          Things you might deliver/do

          • If folks go to the agreed-upon place (weekly update, roadmap, etc), they will be able to see a clear view of progress that is easy to understand by a wide range of stakeholders (basically, every member of the Lessonly team).
          • You will communicate changes (scope, timeline, etc) both effectively and as early as possible.
          • You are also responsible for updating the Weekly Product lesson and coordinating with the Product Enablement team for the monthly round-ups and launch coordination.
          • Demoing functionality at all-team meetings when we can
          • Enabling functionality in our internal About Account and labs.lessonly.com
          • Announcing availability to internal folks via Slack or in an all-team meeting
          • Updating checkpoint goals and results to the P&E department
          Requirements
          Examples
            Observation created about 5 years ago

          https://lessonly.slack.com/archives/CGS75SABY/p1599838143066600?thread_ts=1599837460.065700&cid=CGS75SABY

          Outcomes, baby, outcomes!!!

          We don't do actions and create outputs for our health... we do it to change human behavior... we do it to make people's lives better, / easier.

          Something as simple as having screenshots in the product board roadmap card made a big impact and reinforced a habit (that the answers AEs and AMs are looking for might just be in the roadmap).

          I love the opportunity to shout out outcomes as opposed to activities and outputs. So I'm thrilled to write this OGO. Well done!

          Continuous learning, continuous prioritization to ensure continuous value delivery, continuous communication to all stakeholders. That is our job as epic shapers. We take the work that migth seem big and scary and help make everyone feel safe and confident that we will deliver!

          Full Description

          Objective

          As epic shapers we create, groom, and prioritize epics that take into account date-based commitments (if one has been set), stakeholder communication, and squad capacity awareness and rally the team around a plan to take on and deliver value through epics.

          Key Results

          • Optimize Learning Frequency
            • A project is decomposed/sequenced in a way that delivers value to customers as early as possible and therefore creates consistent (weekly is the goal) learning moments for a squad. Ideally we are learning weekly about things such as:
            • How customers will use the feature
            • What bugs/edge cases we might have missed
            • Are we meeting our hypotheses and measures
            • and more!
          • Each epic is written and sliced in a way, that when complete it accomplishes one (ideally all) of the following:
            • We are able to enable the functionality or work into a customer account to deliver value
            • We have progressed in de-risking the following:
            • ... Feasibility: Can our delivery crew can build what we need with the time, skills and technology we have?
            • ... Viability: Will the overall solution have the desired business outcome?
            • ... Value: Will the overall solution be desired and useful to customers?
          • in regard to commitments made by the squad, stakeholders (Internal P&E team members and cx squad members), have a clear view of and confidence in:
            • ... what value is going to be delivered
            • ... who it is going to be delivered to
            • ... when it is going to be delivered

          Details

          Things you might deliver/do

          • Write epics for a squad that takes into account date-based commitments (if one has been set), stakeholder communication, and squad capacity awareness. Great epics also take into account feasibility de-risking and customer value/impact learning.
          • You will be responsible for decomposing the big initiative into epics that tell a story while providing value along the way as early as possible
          • Responsible for prioritizing the epics. Working closely with the other roles to ensure stuff like bugs, tech debt, enhancements, and net new work is all sequenced in a healthy way.
          • Organize epics into milestones in Clubhouse

          AKA

          • Squad progress communicator (Initiative to epic)
          • Epic writer

          Even more details that need to live in a lesson:

          • If folks go to the agreed-upon place (weekly update, roadmap, etc), they will be able to see a clear view of progress that is easy to understand by a wide range of stakeholders (basically, every member of the Lessonly team).
          • Usually, there is one per squad per quarter.
          • Initiatives are usually big. They might even span multiple quarters.
          • In this role, you will be responsible for decomposing the big initiative into epics that tell a story while providing value along the way.
          • Good epics are ones that take into account date-based commitments (if one has been set), stakeholder communication, and squad capacity awareness. Great epics also take into account feasibility de-risking and customer value/impact learning.
          • You will communicate changes (scope, timeline, etc) both effectively and as early as possible.
          • You are also responsible for updating the Weekly Product lesson and coordinating with the Product Enablement team for the monthly round-ups and launch coordination.
          • Responsible for prioritizing the epics. Working closely with the other roles to ensure stuff like bugs, tech debt, enhancements, and net new work is all sequenced in a healthy way.
          • The strength and value is not that the person in this role making prioritization / technical decisions for epics but that they can facilitate the communication between the technical world (story prioritizer) and PM world (initiative prioritizer) using epics as their medium in order to make sure that "what is being worked on" is in alignment with "what we need" (and in what priority as a part of that).
          Requirements
          Examples
            Observation created about 5 years ago

          https://lessonly.slack.com/archives/CGS75SABY/p1599838143066600?thread_ts=1599837460.065700&cid=CGS75SABY

          Outcomes, baby, outcomes!!!

          We don't do actions and create outputs for our health... we do it to change human behavior... we do it to make people's lives better, / easier.

          Something as simple as having screenshots in the product board roadmap card made a big impact and reinforced a habit (that the answers AEs and AMs are looking for might just be in the roadmap).

          I love the opportunity to shout out outcomes as opposed to activities and outputs. So I'm thrilled to write this OGO. Well done!

            Observation created over 5 years ago

          As we on Assess prepare for the launch of Certifications, we had a bit of an "oh, shit" moment today where it seemed like maybe we weren't all in alignment about what a Certification is. I felt a little scared, since that's not where you want to be 5 months into a project the month it's supposed to launch. So Justin called a meeting with Ashley, our designer, and me as Discovery Engineer. A lesser leader might have played the blame game ("who needs to work overtime to fix this?") or gone full command-and-control ("Here's my plan—make it happen"), but if you've worked with him, you know that's not Justin. Instead, and I've seen him do this before, he approached the situation from a place of curiosity, asking questions like "How did we get here?" Maybe it's because he has a million kids and has seen it all, but Justin's calmness immediately put me at ease, and his confident curiosity—like of course we're going to figure this out—was infectious, keeping us focused on problem-solving. It turned out we were mostly in alignment anyway, and had just made some small divergent, decisions over the course of the project that we're finally having to square, and now have a plan to. If you struggle with crucial conversations like I sometimes do, take a page from the Book of Kime and stay confidently curious.

            Observation created almost 6 years ago

          I am grateful for how these 4 have been communicating on this project. This is a complex project for a variety of reasons. We are splitting up the frontend and the backend. Linking elements in our app is a difficult endeavor. The way these four have communicated to one another and to me has been such a joy. Whether it be Waseem posting killer updates in the channel, Joshua and Joseph presenting their findings on technical deep dives, or Ethan walking me through expectations on epic breakdown, everyone has chipped in to really get this off the ground.

          I have been inspired to bring the level of clarity I have found here in other aspects of my job.

            Observation created almost 6 years ago

          This thread speaks to it: https://lessonly.slack.com/archives/CPHPVJSTH/p1574698910011200

          This is a great discussion and approach to taking on what could be a larger project in Linked Elements. The team was able to work together to identify and slice up the work in order to get value into the hands of customer faster. Alec said it in his summary here:

          We are going to structure the epics so at the end of each element the element is fully implemented. This means that at the end of epic two the paragraph element will have all of the linked element functionality. Then epic three will be the photo element fully implemented.

          • This will mirror how the platform team rolled out a role management, a fully functional piece of a larger whole. This means we can learn more about the entire linked element process earlier.
          • It gets to value quickly. We have been hearing for years from clients about the linked element functionality. With this plan, we will allow admins to do this whole process faster!
          • It will make the delivery manager role more smooth. Because of this plan, each epic will look similar technically speaking. The first element will take the longest because we have to implement all of Linked elements but after we will be able to determine with reasonable accuracy how long each element takes to build start to finish.

          As a result...

          • This enables the squad in efforts of successful decomposition of ideas into shippable units of work to deliver customer value, validate P&E assumptions, or both
          • Developing right-size slices of work that fit into the checkpoint and quarterly goals
          • Thinking through the stack in a way that promotes flexible story creation (e.g. model/database, API, routes, react components, UI).
          • Your squad consistently gets slices of work into customers hands for testing as early as possible in the lifespan of a project
            Observation created about 6 years ago

          https://app.clubhouse.io/lessonly/epic/27348#activity-32580

          This is how acceptance criteria should be written.

          This level of detail should be at the story level to ensure clarity.

          However, I'd put this level of detail in the epic in scenarios where there is less design, or complicated logic, or a delivery team that doesn't find joy in pushing the boundaries on the details.

          We are the documenters... we ensure that the most important parts of how our application is supposed to work never gets forgotten.

          Full Description

          Success:

          • No one on the P&E team has to ask how new functionality is intended to work
          • None of the direct stakeholder (enablement, product marketing, and customer support) has to ask how launched functionality is intended to work (can be measured with a decrease in tickets that could be solved by having documentation in place)
          • Documentation is created, reviewed, and added to Zendesk Guide before the feature is launched and passed to Customer Support and Customer Experience prior to launch to create support articles

          Note: The scope of this role is it is responsible for creating a manual that inspires the customer-facing and enablement documentation but is NOT responsible for writing customer-facing and enablement documentation

          Details:

          Here is lesson that outlines internal documentation on the P&E team

          With every launch and every new feature, there are many details about the feature that we on the product have in our heads. These include:

          • Overview of the feature
          • How the feature works
          • Screenshots
          • Demo Video
          • and more!

          We have a goal to properly document the feature launching for both P&E and inter-departmental stakeholders.

          Things you might deliver/do

          • Create a story for creating documentation in each epic
          • Create documentation and move it through the review process
          • Add documentation for each feature to Zendesk Guide
          • Maintain documentation in the now and future
          • Share documentation easily with stakeholders via Zendesk Guide
          • The Feature Documenters (at least one person from each squad) will get together to create a Feature Documenters Handbook where they will agree on how documentation will be written, organized, and styled in the internal knowledge-base (Zendesk Guide).

          Here is an example of what success looks like

          Requirements
          Examples
            Observation created almost 5 years ago

          We had to respond to an RFP (Request for Proposal).

          There was a question about permissions, and I immediately knew that there is one person I definitely needed to bring in... THE HAMMER!!!

          I asked Kim how she would respond to this RFP question, and a couple of short hours later, she knocked it out of the park! Here is the doc she wrote up.

          Made me even more confident that Kim not only has my back, but she does nothing half assed.

          Well done... we all appreciate you!

            Observation created almost 6 years ago

          Documentation 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.

        • Product Discovery Management (Product Management)

           Assignments:

          We serve the function of Product Management, 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).
            • Initiative backlog groomer
            • Generative researcher
            • Evaluative researcher

          Details:

          • How we go about making initiative-level decisions, communicating those to the stakeholder, and inspiring the team... it is your job to ensure product managers have the proper tooling and processes to execute on these goals.
          • The investment canvas is the most visible manifestation of Product Management enablement.
          Requirements
          • Must have a position with the reach of 3.1 or higher
          Examples
          An observation relating to  Product Management Enablement Lead  has not been publicly recognized yet.

          We take the product strategy and work towards building the right thing by identifying, communicating the importance of, and prioritizing the opportunities we have. Our goal is to inspire stakeholders, the squad, and most importantly the customers by making the Why clear for every bet we make.

          Full Description

          Success looks like:

          • Alignment. You succeed in this role if the big 5 stakeholders understand and agree on the importance (hypotheses around the value proposition) of the investment. Big 5 stakeholders are:
            • External customers
            • or internal if the initiative is aimed at a group like services or CX
            • Internal business stakeholders
            • Such as CX, CS, Sales, Services, Finance, Execs
            • Design
            • Quality Assurance
            • Engineering
          • You are able to clearly articulate the implications derived from research insights to appropriate stakeholders, as well as propose and gather consensus on hypotheses around the value proposition of each product initiative.

          Feedback loop/deliverables

          • Completion, prioritization, and presentation of investment canvases.
            • All work doesn't need an investment canvas, but most work will fall under one. Your job is to ensure the investment canvases are complete. Three other roles participate in the investment canvas creation, but this is the role that is responsible and accountable for the canvases to be clear and complete.
            • Generative researchers and Evaluative researchers are responsible for the evidence, while you are accountable and consulted
            • Solution Design Leads, Hypothesis testing prioritizers, Squad progress communicators, and Discovery engineers are responsible for the execution section, but again, you are both accountable and consulted
            • You are responsible and accountable for the essentials and evaluations, while you should consult all of the roles from above.
          • Canvases will be judged by their effectiveness at conveying the why and the what on the journey towards cross-functional alignment.

          Details:

          • Research without synthesis is like a beat and lyrics without a song. The research should be the ingredients to the clarity that is required for great product work. However, the compilation and synthesis of the research along with hypothesis creation is what brings true clarity.
          • Creating Investment Canvases
          • Determining Desirability (in current, future, and potential markets) working with Biz Intelligence Engineers as well as Solution Discovery leads
          • Determining Feasibility (design, build, test, market, sell, support) working with Discovery Engineering
          • Determining Viability (financially, is the juice worth the squeeze?) working with finance and ops
          Requirements
          • Must have a position with the reach of 2.1 or higher
          Examples
          An observation relating to  Opportunity shaper  has not been publicly recognized yet.
  • Explore Options
    At this step you'll be able to choose different positions or roles that will take you down different paths along your journey. It'll give you an idea of what areas to focus on next and if you do focus on them, what it may take to get to where you are going