Explore CareerPlug's Assignments

Choose Organization Growth Framework
Exploring CareerPlug's growth framework
Choose Starting Position
Starting with the position: Product Owner - L3.1 (aka Senior Product Owner) (Check out Product Owner - L3.1 (copy from 2025-11-03 04:33:30 -0500))
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
  • CareerPlug

     Assignments:

    EOS (entrepreneurial operating system) holds their managers to LMA (Lead, Manage, and hold Accountable). This Assignment is meant to reflect the leadership aspect of that concept.

    Full Description

    The L in LMA

    When I reflect on taking on this Assignment, I answer Yes to all of the following (or if I answer No, I have a plan on how to get to Yes):

    1. I am giving clear direction
      • Creating the opening, a compelling vision, V/TO™
    2. I am providing the necessary tools
      • resources, training, technology, and time / attention
    3. I am letting go of the vine
      • Delegate and Elevate™ and GWC™
    4. I act with the greater good in mind
      • Company vision, my actions, my decisions, walk the talk, company needs first
    5. I am taking Clarity Breaks™
      • "On" the business, creating clarity, protecting my confidence, blank pad
    Requirements
    • Must have a position with the reach of 3.1 or higher
    Examples
    An observation relating to  EOS LMA  has not been publicly recognized yet.

    We take the ideals of "continuous improvement of daily work" to its most actionable level. We join Tiger Teams when we think we can help make something better. We see a need, and fill a need.

    Full Description

    A tiger team is a specialized, cross-functional team brought together to solve or investigate a specific problem

    This is a concept that CareerPlug has used many times in the past. Product has recently made use of them as well.

    Requirements
    • Must have a position with the reach of 1.1 or higher
    • For this role, you must be milestone 1 or greater inCollaboration
    Examples
    An observation relating to  Tiger Team Member  has not been publicly recognized yet.

    • Brand

       Assignments:

      We uphold and advance CareerPlug’s Brand Guidelines and assure visual consistency across all mediums... while ensuring our client/partner-facing teammates have exactly what they need to evangelize the value!

      Full Description

      ONE Number

      • "ticket-taker => strategic partner" health score
        • Ticket-taker rating
          • Requester sentiment (CSAT) averaging "agree" on a 6-point likert scale of the following statement: "When I need collateral it is delivered with incredible service; meaning I felt heard, truly felt like a collaboration, the entire process was easy to work with, was spot on to my needs, timely, and effective (effective meaning; it helped make prospects aware, leads inform, buyer's engaged, and benefactors (such as hiring managers and employees) excited)"
        • Strategic Partner rating
          • Client/Partner-facing teammate sentiment averaging "agree" on a 6-point likert scale of the following statement: "Our collateral that is intended to make prospects aware, leads inform, buyer's engaged, and benefactors (such as hiring managers and employees) excited is constantly getting better and better... it is as if the collateral designers know what we need way before we do such that I rarely have to make any requests"

      Details

      define: Collateral = the guidelines, tone/voice, content, materials, imagery, templates, presentations, webinars, articles, eBooks, original research, social media content, videos, newsletters, infographics, landing pages, etc needed


      Brand Collateral = Long-term (meaning multiple [3+] years; to establish who we are as a company... a laser focus on our mission)
      Marketing Collateral = Medium-term (meaning multiple [4+] quarters; changes by focus and strategy of the moment... campaign-based)
      Sales Collateral = Short-term (meaning, it could change per partner / meeting – regardless, it changes the most frequently)

      Fishing metaphor: Brand is deciding if we fish or hunt – marketing is the lures and equipment – sales is the act of fishing.

      As collateral designers, we uphold and advance CareerPlug’s Brand Guidelines and assure visual consistency across all mediums... while ensuring our client/partner-facing teammates have exactly what they need to evangelize the value! We do that by continually working towards pushing the relationship to the right of the "ticket-taker => strategic partner" paradigm.

      We also don't stop at Brand, Marketing, and Sales Collateral. We also help with internal presentations as well as any employment branding assets needed.

      Requirements
      • Must have a position with the reach of 1.1 or higher
      Examples
      An observation relating to  Collateral Designer  has not been publicly recognized yet.
    • Product

       Assignments:

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

      Full Description

      Escalation Engineers who take on the Document Writer assignment work to ensure that escalations caused by lack of product or process knowledge are rare. They proactively update existing documentation when they see something incorrect out of date, create documentation (Guru cards, Loom videos) relevant to Escalation work (mitigations, processes, etc.). They work with Product Marketing/Technical writing/other squads to close knowledge gaps in the Help Center/Guru.

      One Number

      • Trust Score of the Product Team Guru Boards (how this will be measured... coming soon)

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

      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).
      Requirements
      • Must have a position with the reach of 1.1 or higher
      • For this role, you must be milestone 2 or greater inProduct Knowledge
      • For this role, you must be milestone 2 or greater inCommunication
      • For this role, you must be milestone 2 or greater inCopywriting
      Examples
      An observation relating to  Documentation Writer  has not been publicly recognized yet.

      A team/squad is a collection of individuals coming together to accomplish some mission. To accomplish a mission, the team needs to make forward progress. We are the facilitators of this forward progress... ensuring that with every action we take brings us closer to achieving our mission 💪🏾 We know it takes a team to succeed, and are committed to ensuring WTWT and collaboration. Regardless of our processes, meeting style and cadences, and communication methods; we ensure progress (next steps, priorities, and deliverables) are as clear as possible.

      Full Description

      Outcomes

      • PRESENT
        • All squadmates agree: "I am informed... meaning I know what is most important and what we are doing about it"
        • All squadmates agree: "I am supported... meaning I have nothing in my way of making progress"
        • All squadmates agree: "I am connected... meaning I know what the next steps are, who is accountable for each TODO, and how the TODOs and next steps are aligned with the progress we are trying to make"
      • FUTURE
        • All squadmates agree: "When thinking about the next 2 quarters; I am informed about and connected to the progress (in the form of OKR3s) we may be taking on"

      Details in Guru

      Important note: Facilitators are just that... facilitators. They should NOT be the ones doing all of the "doing". They ARE here to make sure someone is accountable for the "doing".


      This Assignment was inspired by Assignments from other organizations, such as Squad Manager

      Requirements
      Examples
        Observation created about 2 years ago

      https://careerplug.slack.com/archives/C04MX9Q620M/p1691766564273579

      1. Stated the intent right out of the gate
      2. In a public channel so others could follow if needed
      3. Sharing context of the asks being made in a clear and kind way
      4. Ends with a service attitude of busting blockers!

      Great example of forward progress facilitation!

        Observation created over 2 years ago

      https://careerplug.slack.com/archives/C016NHU9JMD/p1685624723633419

      From Lizzie:

      Jaclyn has been a rockstar on a recent State Farm project! State Farm will now have open description on job templates - a big move for State Farm - which has been lead by our fearless leader Jaclyn. Being a team of one I depend heavily on teamwork within CareerPlug to be successful and Jaclyn's WTWT on ths project will only further help me, and CareerPlug, in our goals. Cant wait to share all this hard work with our clients!

        Observation created over 2 years ago

      https://docs.google.com/document/d/1ILq1VS7Hz76DDNTOjKoOct6B-SdknniOZHLP-LT5_30/edit#

      Why aren’t Premium users setting up Autopilot?

      This is a question that B asked (I know others helped, and as I find out to what extent folks helped I may add them to this observation... for now, I know B was at the center of it).

      ❤️ - First, this is the right question to ask!! Product at many places is about getting features out the door. But that is NOT how we get down at CP. We...

      Continuously deliver value that clients/partners love – and work for the business

      ... Which means we set an outcome for ourselves and we scratch, claw, and fight our way to that outcome through relentless iteration. But, that is very uncomfortable for most product folks as we were conditioned to "shut up and deliver features". The fact that this question is being asked by an IC engineer speak volumes! It is an example of the exact type of culture we need to have if we are to achieve exponential results 💪🏾🙌🏾

      Organization of the documents/assets

      ❤️ Let's look at the titles within the document; Background on the problem (that has data), Approach to solving this problem (which orients us to what is to follow), Step 1: Brainstorm ideas/testable hypotheses about why accounts are not setting up AP , Step 3: How might we test/validate our assumptions? (which was moved to FigJam, which IMO is the appropriate place)

      ❤️ Then in the FigJam, the issues were put into an affinity map, and then organized further into what is essentially an opportunity tree.


      All of this gives me tremendous confidence that we are headed in the right direction as it pertains to creating rocks that are incredibly aligned for the quarter!!

        Observation created almost 3 years ago

      https://careerplug.slack.com/archives/C02V4M2QD46/p1674659829798089?thread_ts=1674658266.707579&cid=C02V4M2QD46

      As I was reading this thread I had a roller coaster of emotion.

      A squad being inundated by feedback... how will they handle it? With grace, collaboration, and tenacity... YES 💪🏾

      Uh oh, they are now talking about how they are going ro organize the feedback and how they are going to manage the "duplicate suggestions"... will they try to reinvent the wheel? Nope... Daniel came in with concise, clear, and IMO correct direction... YES 🙌🏾

      Ok, but what about next steps... they are dealing with all kinds of shit; bugs, small tweaks, and larger possible enhancements... will they drown, wander, or gain clarity? Drop the mic level of clarity!!!... HELL YES ❤️

      Daniel.. well done sir... well done!

        Observation created about 3 years ago

      https://careerplug.slack.com/archives/C040GL35TFG/p1663259542335699?thread_ts=1663259527.031509&cid=C040GL35TFG

      The thing I love about this update is its simplicity and organization. Also, Forward Progress Facilitation when dealing with a cross-departmental group is doing that Assignment on Hard Mode.

      Love the three categories: Decisions Made, Next Steps Identified, and Other Updates.

      Also love how concise it is (a skill I personally have been working on for a couple of decades and can't crack 🤣).

      Well done!

      If I had a note, it would be that we should link to the places with more detail / where the work is being done. Ideally ProductBoard given the cross-departmental nature of this.

      We ensure our early adopter program(s) all run as smoothly, pleasantly, and effectively as possible... where the goal is continuous learning through deep connections with key external stakeholders

      Full Description

      One Number / Key Results

      • Early adopter triple L
        • Learn what is and isn't working (evaluative study... both quantitative [they use the things we build and answer the questions we ask] and qualitative [they allow us to interview them])
        • Loyalty (early adopters are usually more loyal the more they feel they are a part of the creative process... as such the retention of these folks should be markedly higher)
        • Learn what could/should be next (generative study... where we step completely outside of the CP offering and converse with them about their daily needs, wins, struggles, possibilities... their social, emotional, and function opportunities)

      Potential activities

      • Managing the Partner Advisory Board
      • Managing the Labs section of product.careerplug.com
      Requirements
      Examples
      An observation relating to  Lab/CAB/PAB custodian  has not been publicly recognized yet.

      We are the builder, thinkers, the foundation for our business. Our business exists to provide value primarily via software – and we have the tremendous honor of being the caretakers of the software. Our motto as Product People is; Continuously Deliver Value – that Clients and Partners Love – and works for the business.

      Full Description

      This Assignment is different. There is no specific accountability other than to uphold the principles and values that come with being a member of Product.

      We hold ourselves to a very high standard, and this Assignment is intended to be an acknowledgment of that fact. The things we all must do to call ourselves Product People.

      • We are experts of our Product...not just our squad's functional area
      • We are students of the game... meaning we see process not as a set of commandments to be followed, but as guidelines that help us achieve our actual goals. Speaking of goals...
      • We are knowledgable about our business... meaning we know enough about our business and the market in general to make informed decisions
      • We know this is a team sport... meaning collaboration is a skill we seek to hone every day
      • We are outcome-focused... meaning we don't seek to just build software... we seek to make a difference... to change human behavior and deliver real results.

      This is not all of what it means to be on Product... but, it is a solid start. As such every member of Product must have this Assignment, and in the spirit of the 80:20 rule, let's set this to 20% for all positions. It'll remind us that the growth framework does NOT aim to capture 100% of your time, energy, or thoughts. The hope is that setting 20% of your job description to being something that does NOT have an observable outcome, it'll reinforce this idea.

      Requirements
      Examples
      An observation relating to  Product Teammate  has not been publicly recognized yet.

      We ensure that our technical partnerships are healthy. That means clarifying expectations, managing communication, and ultimately being accountable for success (win-win makers).

      Full Description

      Outcome:

      • TBD
        • Something about the health (budget, responsiveness, and general return on investment) of the partnership as defined by the exec team (finance and ops primarily)

      Required Activities:

      • ?? Annual budget... can explain/justify the cost/benefit ??
      • ?? Health reviews (quarterly, monthly, or on the weekly scorecard) ??
      • ?? Internal point-of-contact for issues and general communication between organizations??

      Details in the Handbook

      Requirements
      • Must have a position with the reach of 1.1 or higher
      • For this role, you must be milestone 1 or greater inBusiness Knowledge
      • For this role, you must be milestone 3 or greater inCollaboration
      • For this role, you must be milestone 2 or greater inCommunication
      Examples
      An observation relating to  Technical Partner Manager  has not been publicly recognized yet.

      • Design

         Assignments:

        We collaborate on the in-app guide needs

        Full Description

        We are the folks that fulfill the requests identified in this guideline doc

        Requirements
        • Must have a position with the reach of 1.1 or higher
        • For this role, you must be milestone 2 or greater inCollaboration
        • For this role, you must be milestone 2 or greater inCommunication
        Examples
        An observation relating to  In-app guide admin  has not been publicly recognized yet.

        We are relied upon by our squadmates for our strong design opinion (simple, elegant, brand-aware, desirable, viable, feasible, and usable) while being flexible and open to ideas during the collaborative convergence

        Full Description

        Success:

        • Your squadmates relying on you for your strong design opinion while being flexible and open to ideas during the collaborative convergence
        • Simple, elegant, brand-aware, desirable, viable, feasible, and usable solution and the necessary UX/UI.

        Details:

        • We move fast. We move together. Dual-track agile best describes our product delivery model. Meaning, at all times a squad is active in both discovery and delivery. This is admittedly very difficult to manage, but the payoff is worth the cost. Iterate, iterate, iterate.
        Requirements
        • Must have a position with the reach of 1.1 or higher
        Examples
          Observation created over 2 years ago

        https://www.figma.com/file/F82bcspL84tZBkKyJ5iASy/Q3-Pulse---Empowerment-Loop?type=whiteboard&node-id=56-809&t=v9v7wYvL6UBsFNVg-4

        I'm not sure what went down, and I really want to know, BUT I'm all about outcomes, which is change in human behavior... and I think the outcomes I'm seeing are VERY compelling.

        T, you did a design that was met with a lot of feelings 😬. After reading the comments, I was worried about what was next for Engage, and how y'all would make it out of this roadblock.

        Then today I see you have a version that was clearly iterated on, but left some of what I thought were incredible improvements over the current design (the drawer for all of the things instead of trying to do thing in-line, more clear way to engage with response convos/comments, showing a history of thoughts instead of just the one recommendations and TODOs next to each other, clear actions to take).

        So what I'm assuming is that the conversation went smoothly and everyone felt heard, collaboration happened and not compromising.

        If I hear different, I may change this OGO, but at the moment I'm in awe.

        Well done!!

        Side note: I don't love the placement of "ask this question again"... but that is a tiny thing 😉

      • Discovery / Shaping

         Assignments:

        We take in stories, feedback, complaints, and solution requests (from customers) – and convert them into Product gold called Insights

        Full Description

        Our ONE Number

        • TBD (likely an attestation of the quality of the insights when converting insights into opportunities... maybe something about teammates recognizing Product as a group that knows our clients/partners nearly [if not more] than our client-facing teammates)

        Note: There are three types of Insight Excavators. Customer Insight Excavators are expected to talk directly to the users of the software; be it client or partner. Stakeholder Insight Excavators are expected to interact with the internal team to gather their expertise and perspective. Market Insight Excavators are expected to talk to the buyers of the software. All three are expected to do generative and evaluative research... just focusing on different personas

        Details in this Guru card (coming soon)

        Accountable for

        • Excavate insights from the [Insights Portal] such that the insights are used to influence all phases of ProdDev (including all defined below in the cVd6 definition as well as the Product Strategy):
        • Primary work product is the Interview Snapshot

        Link to Guru card with details coming soon


        Curious to see an example of how strategy => discovery => shaping => learning could work? Here is an example of how to organize Continuous Value Delivery.

        Requirements
        Examples
          Observation created about 3 years ago

        https://careerplug.slack.com/archives/C01SG5UDH7E/p1660759506882389
        https://careerplug.slack.com/archives/C02V4M2QD46/p1660759437221819

        The first...

        It is hard being the first to do a thing. Maybe everyone is looking at you to set the tone for how that thing is to be done thereafter. Maybe it feels like putting your "neck out" too far. Maybe it is easier to follow the status quo.

        Fuck the status quo.

        The thing I love the most about Berg taking our qualitative analysis to a new level with this interview snapshot is that she finished.

        • It was accompanied by a Loom where she goes over it
        • It was posted in a public channel where not only can her squadmates consume it, but stakeholders as well
          • Bonus points... it was posted in TWO public squad channels 💪🏾
        • It had an impact! (examples of what people said below)

        Wow, I LOVE that snapshot!!!! That’s fantastic :fire: :raised_hands::skin-tone-2: I was able to take about 5 minutes and read through and and really get a great picture of the struggles and opportunities from that interview :heart:

        omg I could am cry :sob: (edited)
        i am cry

        This is super digestible!!!

        Wow! This is great. Thank you :raised_hands::skin-tone-3:

        We seek evidence that helps us decide on the direction we will take. There is a saying "if all we have are opinions, let's use mine... but if we have data, let's use that". CareerPlug aspires to be data-influenced in all product decisions. We are the engine that powers that influence.

        Full Description

        Our ONE number

        • TBD

        Constellation measures of success

        • Quantitative evidence plays a vital part in product solution design
          • Value Shapers agree "We used data to help shape the best solution possible"
        • Insights are uncovered that helps better support our customers
          • Client/Partner-facing teams (Partner Management, Hiring Expert (Customer Support and Consultation), and Implementation (Professional Services)) agree "Data helped me serve our clients/partners better"
        • All Pluggies agree "Product has easy to understand, and clearly impactful metrics... they inspire excitement and provide clarity into the impact of the work Product does"

        Details in Guru


        Curious to see an example of how strategy => discovery => shaping => learning could work? Here is an example of how to organize Continuous Value Delivery.

        Requirements
        • Must have a position with the reach of 1.1 or higher
        • For this role, you must be milestone 2 or greater inData analysis / synthesis
        • 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 about 3 years ago

        https://careerplug.slack.com/archives/C01SG5UDH7E/p1660753177339599

        “If we have data, let’s look at data. If all we have are opinions, let’s go with mine.”
        ― Jim Barksdale

        Without data, you're just another person with an opinion.
        ― Deming


        I love it when these quotes show up as true in daily product work!

        Engage was debating whether or not the next iteration should include the ability to modify the job title. Then AW came swooping in with amazing data to help answer the question!

        I did a little more digging on the usage for adding job title: It looks like about 55% of users are adding job title after creating a new user. Perhaps because it’s at the top of the current Add New User form and maybe they think it’s a required field. Only ~9% of users are editing the job title when editing an existing user. This is making me feel less strongly that this is something to worry about now.

        She offered both sides of the argument giving reasons along the way. This is collaboration. This is the way to use data for decision making.

        We ensure the opportunities on our opportunity tree are organized and rich with evidence that supports further investment. This evidence comes from everywhere, but is primarily sourced from Insights.

        Full Description

        Our ONE Number

        • TBD (Likely the sentiment of the Oppty Greenkeepers. How easy is it to determine the most impactful work maybe?)

        As Insights to Opportunity Alchemists (I/O Alchemists) it is our responsibility to ensure we are listening to every input possible (direct client conversations, partners, support, operations, engineering, design, product marketing, client education/experience, and everything in between) to add opportunities to our Opportunity Tree. These opportunities – when at their best – will be inspiring, compelling, and clear. They should inspire an emotional reaction to those that read them. Readers should feel the pain, the need, the desire. They should be on the edge of their seat ready to storm the field and help our clients realize the value (or currently lack therefor) depicted in the opportunity. There should be evidence (both qualitative and quantitative). There should be target personas, clear strategy alignment, and above all else a hypothesis or measure of success.

        I/O Alchemists are also responsible for the organization strategy of products, components, features, and sub-features within ProductBoard. If a squad does have their Opportunity Tree housed outside of ProductBoard, the I/O Alchemist is responsible for ensuring the two stay in sync with one another.


        Curious to see an example of how strategy => discovery => shaping => learning could work? Here is an example of how to organize Continuous Value Delivery.

        Requirements
        Examples
          Observation created over 2 years ago

        https://www.figma.com/file/pBfsHKGoFAb5n3bhfSf3F5/Attract-Opportunity-Tree?node-id=0-1&t=JEjQ0PDo66lXNrUB-0

        THIS IS THE WAY!!!!!

        So much to love about this.

        ❤️ - Instructions... in the FigJam there is a "How to use an Oppty Solution Tree" section that cites the sources, and walks us through everything we need to know to traverse this tree! I also love that it is an iteration on other oppty-tree instructions floating around out there. We MUST improve how we go about doing the work, and David showed that in a big way with this.

        ❤️ - The oppties... are mostly from the perspective of the hiring manager, which is just so excellent!!

        ❤️ - The solutions... are plentiful and very relevant!! Only one oppty has only one solution... the rest have 2+... which indicated the oppty is just that, an oppty and not a solution in an oppty disguise!!

        ❤️ - The experiments... exist! Most of the time folks skip the experiment part and stay focused on the solutions. I had decided we weren't ready to talk experimentation, because many of our experiments didn't have an initial hypothesis, weren't short enough to have the cost/benefit needed, and weren't measured in a way that was clear to all. So instead I've nudged us towards KIS measures, some born of Launch effectiveness measures, and helping Core introduce a multivariate testing solution. But, seeing those orange circles gives me an indication that my man David is ready to continue to elevate our quest to iterate our way to exponential results/success.

        Love this David and Chris!!

        Now the next test is how do we keep it this clear once we get folks collaborating with us... solutions that impact multiple outcomes and oppties... and how do we keep this tree green. For now, I'm absolutely wow'ed!!!

          Observation created over 2 years ago

        https://docs.google.com/document/d/1ILq1VS7Hz76DDNTOjKoOct6B-SdknniOZHLP-LT5_30/edit#

        Why aren’t Premium users setting up Autopilot?

        This is a question that B asked (I know others helped, and as I find out to what extent folks helped I may add them to this observation... for now, I know B was at the center of it).

        ❤️ - First, this is the right question to ask!! Product at many places is about getting features out the door. But that is NOT how we get down at CP. We...

        Continuously deliver value that clients/partners love – and work for the business

        ... Which means we set an outcome for ourselves and we scratch, claw, and fight our way to that outcome through relentless iteration. But, that is very uncomfortable for most product folks as we were conditioned to "shut up and deliver features". The fact that this question is being asked by an IC engineer speak volumes! It is an example of the exact type of culture we need to have if we are to achieve exponential results 💪🏾🙌🏾

        Organization of the documents/assets

        ❤️ Let's look at the titles within the document; Background on the problem (that has data), Approach to solving this problem (which orients us to what is to follow), Step 1: Brainstorm ideas/testable hypotheses about why accounts are not setting up AP , Step 3: How might we test/validate our assumptions? (which was moved to FigJam, which IMO is the appropriate place)

        ❤️ Then in the FigJam, the issues were put into an affinity map, and then organized further into what is essentially an opportunity tree.


        All of this gives me tremendous confidence that we are headed in the right direction as it pertains to creating rocks that are incredibly aligned for the quarter!!

        As an organization, we launch together. That means alignment and unity across multiple departments. Within Product, we have special responsibilities to ensure the success of the monthly product launches (as well as any insta-launches). We, launch coordinators, are the captains of the product launch journey.

        Full Description

        ONE number

        • Operations, Client and Partner Success, People, and Product Pluggies (strongly) agree: “I was prepared to not only serve our clients at an expert level, but I am able to bring excitement to our clients about the changes we’ve made to our product.”
          • Sales and Marketing will be handled by the other half of the Launch Coordinator duo.

        Details in Guru

        This Assignment was inspired by Assignments from other frameworks, such as Squad Progress Communicator, Launch coordinator, and Agile Coach


        Curious to see an example of how strategy => discovery => shaping => learning could work? Here is an example of how to organize Continuous Value Delivery.

        Requirements
        Examples
          Observation created almost 3 years ago

        https://www.loom.com/share/7e242094b4fb4eacac5f5ce79c4c5fd2

        I really liked a few things with this:

        1. Clear and concise
        2. Historical context w/ demo of "the old way"
        3. Showing the value of "the new way"

        Great example that other should use as an example when creating these PLC videos 💪🏾

        We take in stories, feedback, complaints, and solution requests (from the market/buyers) – and convert them into Product gold called Insights

        Full Description

        Our ONE Number

        • TBD (likely an attestation of the quality of the insights when converting insights into opportunities... maybe something about teammates recognizing Product as a group that knows our clients/partners nearly [if not more] than our client-facing teammates)

        Note: There are three types of Insight Excavators. Customer Insight Excavators are expected to talk directly to the users of the software; be it client or partner. Stakeholder Insight Excavators are expected to interact with the internal team to gather their expertise and perspective. Market Insight Excavators are expected to talk to the buyers of the software. All three are expected to do generative and evaluative research... just focusing on different personas

        Details in this Guru card (coming soon)

        Requirements
        Examples
        An observation relating to  Market Insight Excavator  has not been publicly recognized yet.

        We set the annual+ goals and strategy (strategy is how you’re planning to go about accomplishing that goal) within the boundaries of the company Vision, company Goals, and company Strategy.

        Full Description

        Our ONE number

        • Leading: Trios strongly agree with "I can answer with confidence what the overall product annual goals are and the product strategy that formed them"
        • Leading: Stakeholders strongly agree with "The reasons why this squad is focusing on this strategy (field of opportunities) is not only clear, but gets me excited for the future / impact on the business strategy"
        • Lagging: When annual squad goals are hit, it results in the lagging indication outcomes defined at the Company Strategy level.

        This Assignment is very similar to Opportunity Tree Caretaker. The only difference is in scale. Where Oppty Forest Groundskeepers focus on the annual and multi-year sized objectives, the Oppty Tree Caretakers focus on the quarterly sized objectives. The motions are very similar however.

        Below, in the Oppty Tree anatomy section, you'll notice that the "roots" are product strategy. We are the ones that tend to the ground so that the roots of the opportunity trees are healthy.

        One day, if the entire company uses MAAP, we will break out those who set the company goals and strategy from those that set the product goals and strategy. However, for now this one Assignment is also responsible for helping set both.


        Below are concepts that are needed to be understood in order to fully grasp this Assignment

        You'll see these repeated in all Discovery/Shaping Assignments


        Opportunity Tree anatomy

        • The Seeds aka Company Strategy
          • When we ask "How might we achieve our company mission/vision" it results in...
          • The 1-3 year outlook; Exec team accountable, everyone responsible
        • Roots aka Product Strategy
          • When we ask "How might we achieve our company strategy" it results in...
          • The viability and value impact measures the Betting Table sets annually; VP Product accountable, everyone in Product responsible
        • The Trunks aka the annual OKRs
          • When we ask "How might we achieve our product strategy" it results in...
          • The primary objectives and key results a squad devises in response to the annual strategy (lagging indicators)
        • The Branches aka the Opportunities
          • When we ask "How might we achieve the annual OKRs"
          • The 1 - 2 big-bet-cycle sized needs, wants, desires, and/or problems represented by leading indicator desired outcomes
        • The Leaves aka the Solutions
          • When we ask "How might we achieve the outcomes defined in the opportunities given to us within the appetite set" – this is called Shaping...
          • When we ask "How might we deliver the value hypothesized by the shaped work" – this is called Launching...
          • When we ask "How might we sense and respond to what was launched and help us iterate to achieve the value we set out to achieve" – this we refer to as Continuous Learning
          • Ultimately, Leaves are the things we build that we hope deliver value to clients that works for the business
        • The Fruit aka the Client Results
          • If all goes according to plan, the Leaves will bear fruit that clients/partners love! This will give us more nourishment which feeds the roots and produces more seeds

        Continuous Value Delivery Crew (cVd6)

        This Assignment is special in that it is a direct member of the "cVd6". The collection of 6 key Assignments needed for continuous value delivery. Though many other Assignments are necessary, the following are the skeleton of any ProdDev initiative.

        1. Actively listen to clients, partners, and stakeholders...
          • "Those who are closest to the customer, will win" – Product Fact
          • Insight Excavators seek out, dig for clarity via inquiry (or excavate 😎), synthesize, and log (via snapshots)
          • Their primary workspace is the Insights tab on ProductBoard
        2. Convert the raw excavated Insights into refined Opportunities
          • Opportunities come in a few shapes and sizes. From small Value Enhancements to Big Bet Oppty Canvases. It is the responsibility of the Insight to Opportunity Alchemists to perform the wizardry necessary to do this conversion. They are responsible for ensuring the Oppties are clear, have evidence, and a desired outcome.
          • Their primary workbench is the Features tab in ProductBoard (taking Insights on the Insights tab and connecting them to products, components, features, and sub-features)
        3. Prioritize and appetite-ify the Opportunities
          • Opportunity Tree Caretaker's primary *Given they are the deciders, the Caretaker's primary workbench is the "Top 7" on the roadmap tab in ProductBoard (pulled from the products, components, features, and sub-features on the features tab)
        4. Shape solutions that may result in the desired outcome at the center of the Opportunities
          • Value Shapers design, prioritize, decompose and sequence... what we call Shape... what is built
          • Their primary workbench are the Oppty Canvases, specifically the project brief / guided tour within them
        5. Build the solution
          • There are too many Assignments involved in building to list here. The Value Shapers are expected to be the leaders ensuring the value is built well.
        6. Launch the Value
          • Launch Coordinators are the air traffic controllers of all launches. Their primary job is to ensure all teammates (strongly) agree: “I was prepared to not only serve our clients at an expert level, but I am able to bring excitement to our clients about the changes we’ve made to our product.”
          • Their primary workbench is the Portal tab of ProductBoard, where we showcase what we've launched (as well as the internal roadmaps, which will include launch effectiveness measures where appropriate)
        7. We launch to learn
          • Launching is but a single step in the endless flow of continuous value delivery that the CP Product team subscribes to. We are not a feature factory, but instead we aspire to be a true Product team. If we aren't learning (what works, what doesn't, and how it impacts client results and business outcomes), then we are not doing our job. Data Analysts ensure we are learning from every launch. Taking those learnings and converting them into Insights (and the continuous flow starts all over again... if done well it is like fission, where it never stops and gets more and more powerful over time).

        This sequence starts with clear company goals and strategy that lead to clear product/squad goals and strategy. The responsibility of ensuring the goals and strategies at that level are clear falls to Opportunity Forest Groundskeepers.

        Requirements
        Examples
        An observation relating to  Opportunity Forest Groundskeeper  has not been publicly recognized yet.

        We ensure the opportunities we focus on are in alignment with the product strategy and give us the best chance at achieving our ultimate goals of continuous value delivery. We succeed if the Oppties we select results in helping us meet our product strategy goals.

        Full Description

        Our ONE number

        • Leading: Squadmates strongly agree with "I can answer with confidence why we are focusing on the big bet work we are shaping, building, and launching"
        • Leading: Stakeholders strongly agree with "The reasons why this squad is focusing on this opportunity is not only clear, but gets me excited for the future / impact on the business strategy"
        • Lagging: When oppty desired outcome is hit, it results in the lagging indication outcomes defined at the Product Strategy level.

        We help the Insights => Opportunity Alchemists with organizing the products, components, features, and sub-features within ProductBoard's feature tab. However, it is our sole responsibility to put in the appetite. We also have major influence over the squad's "top 7".

        This Assignment is accountable for the outcomes of the opportunities selected being the best thing for continuously delivering value that clients/partners lave – and work for the business. As such, this is a high stress Assignment.

        If the squad is using Kanban, the Betting Table will take this Assignment.
        If the squad is using Empowered ShapeUp and the Tournament of Value, the Betting Table will take this Assignment.
        If the squad is using Continuous Value Delivery, the squad will decide if the full trio takes on this Assignment or if a specific member (usually the Product Manager) will take it on.


        Curious to see an example of how strategy => discovery => shaping => learning could work? Here is an example of how to organize Continuous Value Delivery.

        Requirements
        Examples
        An observation relating to  Opportunity Tree Caretaker  has not been publicly recognized yet.

        What is self-serve? Getting clients to take the actions that are best for them / put them in the best position to achieve their results. Especially important in a SMB / 1:many model. We scientist put our goggles on and are constantly working to improve every aspect of our self-serve motions!

        Full Description

        One Number

        • TBD

        Details

        Us, Self-Serve Scientists, are laser focused on driving results...
        ... be it client results such as introducing and helping arrive at the launch effectiveness of new functionality that we believe will lead to better results...
        ... or driving clients to activate and begin a trial...
        ... or running tests encouraging clients to upgrade to a new plan.

        Executing on this Assignment involves a blend of marketing, product development, and data analysis. Our focus is split between understanding and leading clients to the offerings we create (can't have value delivered that you love if you never try it) and the "works for the business" aspect of our motto. Increasing user acquisition, engagement, retention, and revenue. We experiment with different marketing channels, optimize conversion funnels, and leverage data analytics to understand user behavior and preferences. We value creativity, agility, and a data-informed approach to decision making. We are constantly seeking new, unconventional ways to reach and expand the user base, and are adept at using analytics to track performance and iterate quickly based on insights gained. This Assignment requires a deep understanding of the product, the market, and customer needs, coupled with the ability to execute growth initiatives iteratively and incrementally depending on the decomposition and sequencing needs of the initiative.

        We are also the most collaboration-required Assignment next to maybe Launch Coordinators. We cannot work on our own... we must establish squad-style collaboration relationships with key stakeholders.

        Requirements
        Examples
        An observation relating to  Self-Serve Scientist  has not been publicly recognized yet.

        We take in stories, feedback, complaints, and solution requests (from stakeholders) – and convert them into Product gold called Insights

        Full Description

        Our ONE Number

        • TBD (likely an attestation of the quality of the insights when converting insights into opportunities... maybe something about teammates recognizing Product as a group that knows our clients/partners nearly [if not more] than our client-facing teammates)

        Note: There are three types of Insight Excavators. Customer Insight Excavators are expected to talk directly to the users of the software; be it client or partner. Stakeholder Insight Excavators are expected to interact with the internal team to gather their expertise and perspective. Market Insight Excavators are expected to talk to the buyers of the software. All three are expected to do generative and evaluative research... just focusing on different personas

        Details in this Guru card (coming soon)

        Requirements
        Examples
        An observation relating to  Stakeholder Insight Excavator  has not been publicly recognized yet.

        We shape the solutions aimed at the desired outcome within Opportunities. We are the missionaries within Product obsessively focused on the five big value attributes while seeking continuously improved ways to deliver value that our clients/partners love and work for the business.

        Full Description

        Our ONE number

        • Hypothesis Hit Rate (combo of three concepts)
          • Oppty quality checking
            • I recently heard a good metaphor for this. You can be asked to design a vase, or to design a way for people to be able to appreciate flowers. Oppties are "How might we allow people to appreciate flowers". Assumptions are "I think putting them on the dinner table will bring joy". Solutions are... a vase. Value Shapers are given a mission of "How might we allow people to appreciate flowers". The oppty is a good oppty if you can clearly state the why, what, and who. The measure of Oppty quality checking is a checks and balances measure. The opportunity tree caretaker agrees "Working with this value shaper makes me better at writing opportunities... they are collaborative in seeking clarity and ensuring everyone is aiming at the most important thing... Continuously Delivering Value that Clients and Partners Love – and Works for the Business"
          • Learning Frequency
            • We aim for continuous.. in order to do that we must be testing assumptions continuously. When you have a squad with great Value Shapers, squadmates agree "We are deliberately learning so much... meaning, 3+ opinion-shifting and/or assumption-(in)validating learnings per quarter".
          • Oppties, Assumptions, and Solutions separation... decomposing oppties into assumptions, experiments, and ultimately iterating on solutions.
            • Great value shapers are incredible at devising a set of assumptions (prioritizing the riskiest of them). Designing experiments to test them keeping in mind the cost/benefit of the learning and risk mitigation. And ultimately delivering solutions that get at the desired outcomes in the oppties! Stakeholders agree "I know what the squad's assumptions are, how/if they are testing them, and how these insights are resulting in higher quality software... as seen by the squad hitting or exceeding between 60-80% of their stated launch effectiveness hypotheses"

        Full Description in Guru Card

        This Assignment was inspired by Assignments from other frameworks, such as Discovery Manager


        Curious to see an example of how strategy => discovery => shaping => learning could work? Here is an example of how to organize Continuous Value Delivery.

        Requirements
        Examples
          Observation created over 1 year ago

        https://careerplug.slack.com/archives/C010D2AQA0Z/p1707774919895089

        The best embrace feedback. The best embrace collaboration. The best embrace transparency.

        It is so incredibly hard, especially in Product where everyone believes their ideas are the best ideas. And this fact stops most from getting feedback, from collaborating, from exhibiting transparency.

        B is NOT most.

        I can honestly say, this is one of the best messages I've ever seen in my 20 year career.
        ✅ - Early... so folks know that their voices matter
        ✅ - Focused on outcomes... so folks know we aren't choosing the "coolest idea", we are going to bet on the thing that helps us achieve the outcome
        ✅ - Proactive... notice this is in the HX channel!!!
        ✅ - Cross-functional... B is a TECH LEAD. Usually you'd see this from design or product management. I'm CERTAIN the full Pre-Hire Trio discussed this (and if after posting this I get that confirmation, I'll attach them to this OGO)... but seeing a tech lead truly get in the discovery and shaping is AMAZING!!

        LFG!!!

      • Engineering

         Assignments:

        We take slices of work (epics/scopes) and break them into specific, actionable stories/tasks so that we can ship as effectively as possible.

        Full Description

        Our ONE Number:

        • Cycle time should be below 3 days for your squad
          • The theory is that if cycle time is low, it is likely because the stories are appropriately sized. If they are appropriately sized, and the squadmates feel as they know exactly what is next best to work on, you are executing this role at a very high level.

        Deliverables:

        • Actionable stories/tasks

        Details

        • Usually, only one per squad per quarter
        • Takes the epics/scopes and ensures that stories/tasks are decomposed in such a way that it will ensure the best flow for the squad.
        • Usually a full stack engineer or a very technical product owner/manager. Stories can, but likely shouldn't need much work done to them after you have done your magic to them.

        AKA

        • Story backlog groomer

        From our recent job description

        You will take the slices of work (epics/scopes) and break them into specific, actionable stories/tasks so that we can ship as effectively as possible (which means the stories/tasks are as small and as clear as possible). Ultimately we want stories/tasks/PRs that help us with forecastability and understandability on a pursuit of continuous value delivery.

        How we decompose and sequence the stories requires an understanding of the UI, backend, and the other "build" constraints. Though you’ll be doing your best if you’re getting help from your squad.

        Success looks like:

        • We use multiple metrics that help us measure the health of our delivery. One of them that helps us identify if we have bottlenecks is story cycle time. You’ll be successful if stories are a similar size and therefore have a relatively consistent cycle time.
        Requirements
        • Must have a position with the reach of 1.1 or higher
        • For this role, you must be milestone 3 or greater inDecomposition & Sequencing
        • For this role, you must be milestone 2 or greater inCollaboration
        • For this role, you must be milestone 2 or greater inCommunication
        Examples
        An observation relating to  Builder Task Shaper  has not been publicly recognized yet.

        We write the software that drives the value delivery of our offering

        Full Description

        This is an Assignment primarily for App-Dev Software Engineers. However, site reliability, software in test, and escalation engineers may take on this Assignment. For specific notes to the types of folks taking on this Assignment see the bottom of this description

        The One Number we are accountable for

        • Likely Value Launched, Effectiveness... more on this coming soon, but for now check out this Guru card

        Supporting / leading indicators we pay attention to (aka constellation measures)

        • Coming soon

        Things you might deliver/do

        • Coming soon

        Notes to the different types of engineers

        • Escalation Engineers
          • Escalation Engineers who take on the Code Author Assignment execute against the things that will make everything better – T1/T2 mitigations, remediation of bugs that squads don't have the capacity to handle, implementation of functionality that we know will help reduce resistance and/or increase value for us, our stakeholders, or our customers.
        Requirements
        Examples
        An observation relating to  Code Creator  has not been publicly recognized yet.

        We put teammates first by using code reviews as a way to help them continuously improve while continuously delivering value

        Full Description

        Code reviewers help in our quest to push quality to the left by giving actionable feedback on code including (but not limited to) the following areas:

        • Test Coverage
        • Performance
        • Security
        • Coding Conventions
        • Architectural patterns

        We put teammates first by using code reviews as a way to help them do their best work

        • We offer advice and resources to share knowledge and teach others
        • We discuss the advantages and disadvantages of different approaches
        • We aim to balance the number of PRs we create with the number of PRs we review

        Notes:
        As an engineer grows their engineering skills, they will be able to tackle larger and more complex code reviewers. A good guideline for what an engineer would be able to review successfully is to compare the complexity of a PR to their current ruby/rails milestones. Participating in code reviews for code at higher ruby/rails milestones is a great way to get more experience and grow, but having a more senior engineer to approve/act as a second set of eyes can be a good guardrail for safety.

        Requirements
        Examples
        An observation relating to  Code Reviewer  has not been publicly recognized yet.

        • Operations

           Assignments:

          Escalations are inevitable, but we ensure recurring escalations are reduced/eliminated altogether

          Full Description

          Escalations are necessary, but expensive.

          • Expensive because of the negative impact on Experience of CareerPlug’s client-facing teams
            • Anytime a client/partner-facing rep cannot answer a question, resolve a problem, or make a change that enhances the value of our offering to the client/partner 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.

          The One Number we are accountable for

          • Quarter over quarter reduction in known escalations - there will always be new escalation needs popping up, but we shouldn’t let the same ones linger for months.

          Supporting / leading indicators we pay attention to

          • 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-3+ agent).
              • 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.
            • Client/Partner-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”.

          Escalation Engineers who take on the Escalation Mitigator assignment have their pulse on the escalation trends happening from T1 up. They share this knowledge across the product organization to help build feedback loops between other teams and the squads. They work with Platform Squad PO to prioritize and shape mitigations to resolve the most common escalations - allowing our users and teammates to self-serve and resolve their issues faster and with less friction

          Requirements
          Examples
            Observation created about 2 years ago

          https://careerplug.slack.com/archives/C02T0CYA8GZ/p1691507297298429

          Sometimes when mitigating escalations, the right thing to do is:

          1. Wait until you see a pattern that makes the cost/benefit worth exploring
          2. Build a thing that makes the need go away
          3. Build a thing that empowers an earlier tier to meet the need
          4. Update documentation (internal or external) that addresses the need

          But, sometimes, especially in hi-trust environments, the thing to do is to empower and train earlier tiers. This is the hardest of the options, but an amazing one if you can get it done.

          CW has been reporting on the fact that IP Address allow-listing has been the top escalation for a long while.... BY FAR.

          She investigated multiple ways to mitigate this escalation, but apparently came to the conclusion that it would be best to empower and train T2 to be able to handle these requests. Therefore making the turn around time that much faster, clients that much happier, and removing that much bureaucracy from the CP universe.

          Well done!

          We ensure everyone is aware of what is going on when there is an incident

          Full Description

          Coming soon... a document that resembles this

          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 2 or greater inProduct Knowledge
          • For this role, you must be milestone 1 or greater inBusiness Knowledge
          Examples
          An observation relating to  Incident Communications Lead  has not been publicly recognized yet.

          We ensure our software is operating such that there is little to no disruption in value delivered

          Full Description

          The One Number we are accountable for

          • Mean time to awareness
            • How long it takes to recover from a severity-2+ event (app going down, major functionality having issues, major bug released into production)

          this definition and outcome need some work

          Supporting / leading indicators we pay attention to

          • Mean time to restore (this is actually a lagging indicator... but the better we make ourselves aware, the more urgent things will be fixed appropriately)
          • # of issues we notice and act on Before they are submitted by clients/partners vs issues we act on after they inform us
          • Squad Performance metrics feedback loop health

          Links to dashboard that showcase these measures... coming soon

          Things you might deliver/do

          • Logging certain events in New Relic so that we can monitor their health
          • Having the data to know if things are going well or off the rails
            • Knowing success rate on builds

          Examples

          • Make sure we are handling AirBrakes
            • We know if the integrations goes down
            • EEs know the process and following
            • They are fixed (folks know what to do)
          • not that things are fixed, but we know about it and know the impact
          • ensure nightly processes actually run
          • Making sure the value we have promised to deliver consistently
          Requirements
          Examples
          An observation relating to  Operations Reliability Agent  has not been publicly recognized yet.

          We want all builders to agree with: “I feel safe enough to build high-value functionality, quickly, and that is in a large part due to how we execute on our testing strategy”

          Full Description

          The One Number we are accountable for

          • TBD

          Supporting / leading indicators we pay attention to

          • Test suite run time (ideally under 10 minutes locally and 5 on CI)
          • No test suite flakes

          Links to dashboard that showcase these measures... coming soon

          Things you might deliver/do

          • Documentation/creation of processes around our testing strategy
            • When should we write unit tests
            • When should we write request specs
            • When should we write feature tests
          • Optimization of the test suite for performance
          • Optimization of the test suite for effectiveness
          Requirements
          Examples
          An observation relating to  Test Automation Architect  has not been publicly recognized yet.

          Escalations are necessary, but they are also expensive (slow for customer and can be disempowering for tier1/2 agents). We Trainers focus on ensuring T1/2 have the knowledge they need to curb the need for escalation

          Full Description

          Escalation Engineers who take on the T2 Enablement assignment are dedicated to helping T2 level up their skills. They own the T2/T3 sync, and provide regular feedback on how the HX team can improve their bug submission skills. Working with the Escalation Mitigator, they resolve trends with escalations that don’t need a code change or can’t be solved through documentation alone - this can be giving other teams access to other tools and teaching them best practices, training them on how to use mitigations, or teaching them about more technical parts of the app like the API or webhooks that will allow T2 to solve issues for our clients without needing to bring things to T3.

          ONE Number

          • Reduction in the percentage of escalations that need T3 input by type (if there is a training on how to troubleshoot/investigate - a smaller percentage of those types of escalations should reach T3 post training)
          Requirements
          Examples
          An observation relating to  Tier 1/2 Trainer  has not been publicly recognized yet.

          We ensure Tier-II has what they need to succeed

          Full Description

          Tier 3 Agents support T2 and the rest of the company by verifying/routing bugs and other errors to the correct squad, investigating/answering product questions, and completing tasks that can only be performed through the rails console.

          Our ONE number

          • 90%+ of internal teammates who submitted tickets that reached T3 slightly or strongly agree that they got the information they needed to solve their issue in a timely manner.
          • Escalation cycle time
            • On average we agree that a conversation is needed if escalations take more than 2 hours per.
            • If/when an escalation is going to take more than 2 hours, everyone knows why and likely agrees with you
          Requirements
          Examples
          An observation relating to  Tier-3 Agent  has not been publicly recognized yet.

          We are the Subject Matter Experts for a functional area of the app.

          Full Description

          Our ONE number

          • TBD

          Details in Guru

          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 inSoftware Investigation
          Examples
          An observation relating to  Tier-4 Agent  has not been publicly recognized yet.

          We are the last line of defense, the ones that must remediate the pain by any means necessary. The department, the business, and ultimately our clients/partners rely on us to ensure we can continue delivering on our mission.

          Full Description

          Key Result(s) / Outcomes

          • "One number" TBD

          Supporting leading indicators

          • Response time SLA
          • Case CSAT score SLO

          Links to dashboard that showcase these measures... coming soon

          Things you might deliver/do

          • Coming soon
          Requirements
          • Must have a position with the reach of 1.1 or higher
          • For this role, you must be milestone 4 or greater inProduct Knowledge
          • For this role, you must be milestone 2 or greater inCommunication
          • For this role, you must be milestone 4 or greater inSoftware Investigation
          Examples
          An observation relating to  Tier-5 Agent  has not been publicly recognized yet.
      • Leadership

         Assignments:

        We serve a specific function and the people executing against its Assignments. Our goal is continuous improvement of the tools and processes (balancing autonomy and focusing on feedback loops) to ensure everyone knows what success means, has the tools to achieve success, and are engaged throughout the journey in pursuit of success.

        Full Description

        The ONE number

        The people taking on the Assignments within the function* I serve, agree or strongly agree to the following statements:

        • I know how I’m being evaluated on these Assignments.
        • I receive actionable (meaning timely, frequent, specific, and observation-based) constructive feedback on my performance within the function Assignments.
        • I receive actionable (meaning timely, frequent, specific, and observation-based) recognition (public or private) on my performance within the function Assignments.
        • I have the tools to meet or exceed the outcomes listed within the function Assignments.
        • I have the processes and environment to meet or exceed the outcomes listed within the function Assignments.
        • We are continuously improving in how we go about executing these function Assignments.

        Note: This SHOULD have a direct impact on the eNPS score of the employees taking on these Assignments (where they select 8+ on a 10-point scale to the question; “I’d recommend a friend come to work here”). However, given that full engagement is more inclusive than their Assignments, it doesn’t feel right to have that as a part of the measure of function leads.
        Note: We refer to functions as domains in OurGruuv... they are synonymous


        All functions/domains are listed here

        Requirements
        Examples
          Observation created almost 2 years ago

        https://careerplug.slack.com/archives/C036NV818A1/p1698941823493789?thread_ts=1698941629.004889&cid=C036NV818A1

        I have been dreaming of ways to improve clarity, consistency, acknowledgment-of-human-uniqueness, fairness, and ultimately fostering of a habit of continuous improvement in growth frameworks since 6 months into being a manager.

        Recently, I've been on a kick that one of the few attributes that fosters a healthy growth framework and growth culture is the measure of how frequently the framework is updated. Staleness is the breeding ground for the decomposition of the culture-of-growth ideals.

        Christina had a judgment. They then did the hard work of teasing apart that judgment into Observations, Feelings, and Unmet needs. This is very hard, but the single best path to actionable improvement.

        They then Spoke Up and Stepped Up in a way that was going to help outside of this one instance... but help sustainably, forever! Instead of making a request, they decided they'd improve the thing we should all be relying on as a guideline for how to improve... the growth framework!

        Talk about SUSU... they are even proposing to get rid of a concept that I personally introduced. Which shows me that they want improvement, not appeasement.

        :snoop-nod: Can't wait to see the end result!

        Bringing new folks into our community 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

        The ONE Number

        • Combinatorial
          • Applicant experience as measured by Glassdoor reviews of the interview process
          • Interviewer experience as measured by interviewers (strongly) agreeing "I knew what was expected of me in the interview, and the interview was run very smoothly... I trust that we are going to make an unbiased and mutually beneficial decision with who we hire, in large part because of how the interview process was run!"
          • Results as measured by the new hire being above the "bar" (People Analyzer, values and GWC) for at least the first 6 months

        Handbook

        Requirements
        • Must have a position with the reach of 3.1 or higher
        • For this role, you must be milestone 1 or greater inBusiness Knowledge
        • For this role, you must be milestone 2 or greater inProject Management
        Examples
        An observation relating to  Hiring Manager  has not been publicly recognized yet.

        We help those we serve achieve their personal growth and work goals – using servant leadership principles of empowering and trusting, transparency, providing clarity, and ensuring 360-degree accountability.

        Full Description

        ONE Number

        • Combinatorial with four inputs
          • Orientation effectiveness 🚧 - open question... does this encourage gaming the system? Managers will be incetivized to say their folks are higher milestones than they have been able to demonstrate?
            • New hires, within 3 months, are no longer apprentices (achieved all of the appropriate milestones) on any of the required Assignments for the Position.
          • 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”.
          • Employee Engagement 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 as measured by your manager (strongly) agreeing: "I am confident you know how those in your care are doing, what the biggest issues are, and you have a plan to improve them as well as a feedback loop to know if your actions are working"
          • EOS's M in LMA (see below... there are 5 questions that we have to say yes to)

        EOS' M in LMA

        When I reflect on taking on this Assignment, I answer Yes to all of the following (or if I answer No, I have a plan on how to get to Yes):
        Note: Here is a checklist PDF

        1. I keep expectations clear
          • Mine and theirs, Roles(seats, Assignments, responsibilities, etc), Core Values, Rocks, and measurables
        2. I am communicating well
          • Me and them, you know what is on each other's mind (no assumptions / no unstated expectations), 2 emotions, question-to-statement ratio
        3. I have the right Meeting Pulse™
          • Even exchange of dialogue, reporting measurables, keeping the circles connected
        4. I am having Quarterly Conversations™
          • The 5-5-5™, the People Analyzer™ (Core Values and GWC™)
        5. I am rewarding and recognizing
          • give positive and negative feedback quickly (24hrs), criticize in private, praise in public, the Three-Strike Rule
          • Note: EOS says "be their boss, not their buddy", and I, AR3, vehemently disagree with this being a necessary aspect of management, which is why it is not going to be a part of the people management within Product. Buddy away... so long as you can still hold each other accountable.

        Above is the accountability, below are some strategies Product employs to achieve the One Number.


        Systematize Clarity

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

        Within the Product team, we do that in various ways. One of those ways is seen by the fact that most Positions which require this Assignment will also be required to be a Function Lead for the appropriate function/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 our vision.

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

        Requirements
        • Must have a position with the reach of 3.1 or higher
        • For this role, you must be milestone 2 or greater inCommunication
        • For this role, you must be milestone 2 or greater inCommunity
        • For this role, you must be milestone 2 or greater inGoal Management
        • For this role, you must be milestone 2 or greater inMentorship
        Examples
          Observation created almost 3 years ago

        360 review - manager survey

        https://careerplug.slack.com/archives/C5B73NC0Y/p1666099801024479

        Here is what I love the most about this:

        1. It is experimentation on how we can improve our daily work
        2. The daily work you wanted to improve was how we can do People Management better... which is often a neglected Assignment when folks think about improving daily work
        3. From what I've heard from you, Canaan, it helped give a more rich C/S/D to your folks

        Honestly, I wish I'd have done this for you... or I should say, I'm disappointed I didn't... yet.

        It is stuff like this that will make continuous improvement a habit... and as continuous improvement becomes a habit, exponential results become a real possibility.

        I want to be clear... I do have a differing opinion on how this type of feedback should be given... but the thing I love about this is that it is out there and done. What I want us to do isn't ready yet... but we shouldn't wait for better, we should always be making progress forward... and that is what you did here 💪🏾

        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 CareerPlug 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 2.1 or higher
        • For this role, you must be milestone 1 or greater inCommunity
        Examples
        An observation relating to  Recruiter / Sourcer  has not been publicly recognized yet.

        We support the squads. Ensuring they have the context, coaching, and we ask increasingly better questions that will help set them up for success.

        Full Description

        Quadmates agree; “Having you as an orbiter is great! You don’t tell us what to do... you don’t give us the answers... But I feel extremely supported in the pursuit of outcomes I’ve been asked to deliver on. I feel coached, I can trust you have the context we need to be successful, and you ask the great questions that get us to think”

        Requirements
        • Must have a position with the reach of 2.1 or higher
        • For this role, you must be milestone 2 or greater inCommunication
        • For this role, you must be milestone 2 or greater inCollaboration
        • For this role, you must be milestone 3 or greater inMentorship
        Examples
          Observation created 10 months ago

        Starts with observing an issue by (conversing with her direct report)[https://careerplug.slack.com/archives/C037Z53KPHQ/p1713276253909209].

        Then she identifies a potential solutions and steps up to execute the solution.

        Then owned it, and lead the 5 dysfunctions of a team workshops.

        Ensured it was not in the squads way (additive and unobtrusive)... and handled the scheduling to ensure it stayed that way.

        Has had (great communication)[https://careerplug.slack.com/archives/C037Z53KPHQ/p1736174398474009?thread_ts=1735833915.695419&cid=C037Z53KPHQ] with the management team.

        But more importantly than any of that... I've personally heard from multiple members of the team that they found it to be really valuable and the issues they were dealign with are beginning to melt away 💪🏾

        Speak Up Step Up - Results - Improvement of Daily Work - Without anyone complaining about it?!?!?! Rare and wonderful!!

      • Product Marketing

         Assignments:

        We lead the creation, maintenance, and monitor the feedback loops of the execution of go-to-market strategies for new products, features and updates that drive engagement and adoption, and work cross-functionally

        Full Description

        AG to fill this out :-)


        • Lead the development and execution of go-to-market strategies for new products, features and updates that drive engagement and adoption, and work cross-functionally across product, hiring experts, retention, implementation, partnerships, sales, design, product owners, and marketing
        • Develop product positioning and messaging
        • Develop high-quality content to achieve business objectives for CareerPlug’s products – demos and guided product tours, how-to and user guides, product videos, webinars, blogs, slides, website pages, and data sheets
        • Drive and execute on our competitive intelligence plan so it shapes our view of the market and assess how we win by evaluating competitors and customer insights
        • Be the internal expert in understanding our buyer personas, user personas, and customer stories
        Requirements
        Examples
        An observation relating to  Go-To-Market Strategist  has not been publicly recognized yet.

        We ensure the help center is as effective as possible

        Full Description

        One Number

        • Coming soon

        Owning the underlying operations that come with managing a help center such as monitoring and reporting on effectiveness analytics, handling duplicating content across the three help centers we now support, and a collection of other duties related to help center maintenance (to be filled out by AG soon)

        Requirements
        • Must have a position with the reach of 1.1 or higher
        Examples
        An observation relating to  Help Center Maintenance Operator  has not been publicly recognized yet.
      • Product Operations

         Assignments:

        As an organization, we launch together. That means alignment and unity across multiple departments. Within Product, we have special responsibilities to ensure the success of the monthly product launches (as well as any insta-launches). We, launch coordinators, are the captains of the product launch journey.

        Full Description

        ONE number

        • Operations, Client and Partner Success, People, and Product Pluggies (strongly) agree: “I was prepared to not only serve our clients at an expert level, but I am able to bring excitement to our clients about the changes we’ve made to our product.”
          • Sales and Marketing will be handled by the other half of the Launch Coordinator duo.

        Details in Guru

        This Assignment was inspired by Assignments from other frameworks, such as Squad Progress Communicator, Launch coordinator, and Agile Coach


        Curious to see an example of how strategy => discovery => shaping => learning could work? Here is an example of how to organize Continuous Value Delivery.

        Requirements
        Examples
        An observation relating to  Launch Coordinator – Sales & Marketing  has not been publicly recognized yet.

        We ensure that all stakeholders can rely on the product sources of truth. When they need to know... they can find out – just like ✨ magic 🪄

        Full Description

        One number we are accountable for?

        • All Pluggies agree: "I am confident that when I need to find some info about what Product has done, is doing, or is considering doing – not only can I find it, but it is answered such that I have exactly what I need"

        Details in Guru

        Requirements
        Examples
        An observation relating to  Sorcerex of Truth  has not been publicly recognized yet.

        We directly help clients, partners, and even technical partners be set up for success and when needed overcome the hairiest hurdles

        Full Description

        When you think of Technical Account Management... think of someone with Tier-3, maybe even Tier-4 level technical ability, but with Consultant level customer service (we interact directly with clients/partners). We are creative, resourceful, and a Jack/Jill of all trades. Be it a deep API integration question or a marketing analytics campaign troubleshooting, we either know the answer or will find it quickly.

        ONE number

        • CSat from the clients, partners, AND the internal stakeholders (account executives, account managers, or partner managers)
        Requirements
        • Must have a position with the reach of 3.1 or higher
        • For this role, you must be milestone 2 or greater inBusiness Knowledge
        • For this role, you must be milestone 1 or greater inCollaboration
        • For this role, you must be milestone 3 or greater inCustomer Service
        • For this role, you must be milestone 2 or greater inCommunication
        Examples
        An observation relating to  Technical Account Manager  has not been publicly recognized yet.
      • Quality

         Assignments:

        There can be no Value without Quality. We ensure we are building that quality in. From selecting opportunities, to shaping solutions, how we decompose and sequence the build out, and even how we do staged rollouts of our launches. We are looking for ways to ensure quality at every turn.

        Full Description

        Our ONE Number

        Focused on the "Post-Launch bugs" column

        Details in Guru

        Requirements
        Examples
          Observation created over 2 years ago

        https://careerplug.slack.com/archives/C02GWTK9WFM/p1690226899258309

        Not sure who in the squad had this idea, so I'm attributing to to Jaclyn for now.

        The idea of doing a FULL SQUAD walk-thru before putting an offering through PLC is genius!!!

        • Builds confidence within the squad, ensuring everyone is aware of and owning what we are presenting
        • Builds confidence of the squad from PLC, because what is presented is very likely more defensible

        This reminds me of a "Product Yoda" quote...

        "Collective squad ownership leads to Love.... Ownership leads to higher quality, higher quality leads to more confidence, more confidence leads to more trust, more trust leads to more autonomy, more autonomy leads to faster iteration, faster iterations lead to more REAL client value, more client value leads to more client love"

        • Product Yoda

        Thanks for taking a step closer towards the wonderful world of Product Love

          Observation created over 2 years ago

        I challenged the Onboard Squad to be crystal clear with the help they need from Implementation with their rock this quarter. It is a big deal because we are likely asking them to change their rock to help us with ours. 😬

        I was expecting a one-page write up going over the basics. But the homie Daniel said "nah... here is a fully fleshed out video series with accompanying assets to ensure there is extreme alignment"!

        ❤️ - The GSheet, because it makes the goal extremely clear
        ❤️ - The demo videos, because it makes it real easy for ANYONE with access to come in and help

        Daniel, this was excellent... making WTWT a breeze with this type of preparation.

        WELL DONE 1️⃣ 2️⃣ 3️⃣ 👏🏾 ✨🙌🏾✨

        The full message below so others will have an example of great preparation

        Sup Implementation! Onboard squad here asking yall for help with getting 584 Accounts have at least one new hire complete the the basic Onboard process by EOQ. To do that we need your help with updating all the state tax forms and helping us create an out of the box onboarding task set that we can share with our beta partners.

        1. Project numero uno is updating all the state tax forms. So that no account of the 584 is blocked from using them with their new hires. Here is a video with more detail. Here is the State Form Excel we are working from.

        2. Here are a few training videos for the project above

        3. https://www.loom.com/share/a8a21e80dafa4456a81e7e24aa65f022

        4. https://www.loom.com/share/eeb0db7eead14393a2030345ff92085e

        5. https://www.loom.com/share/2a410797aebd4400b194feacca6f6666

        6. Project numero dos is creating an out if the box onboarding task list using our current task list tool in the platform. We know that partners are looking to ramp up their new hires as quickly as possible while helping them connect with their team culture. Clint, Ashley J, and Natalie have been collaborating on what this out of the box solution could look like (check it out here). We need your help creating this in our platform using the tools we have already. Here is a video with more detail. Ill be adding more training videos of this side of the platform. Stay tuned!

        There can be no Value without Quality. We ensure we are building that quality in. From selecting opportunities, to shaping solutions, how we decompose and sequence the build out, and even how we do staged rollouts of our launches. We are looking for ways to ensure quality at every turn.

        Full Description

        Our ONE Number

        We focus on the "Pre-Launch bugs" column

        Details in Guru

        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 inSoftware Testing
        Examples
        An observation relating to  Pre-launch--Built-in-quality Guard  has not been publicly recognized yet.

        We ensure a quality experience by reducing those pesky issues that might pop up in places where no one is looking

        Full Description

        The One Number we are accountable for

        Focused on the "Regressions" column

        Details in Guru

        Requirements
        • Must have a position with the reach of 1.1 or higher
        • For this role, you must be milestone 2 or greater inSoftware Testing
        • For this role, you must be milestone 3 or greater inProduct Knowledge
        • For this role, you must be milestone 1 or greater inProject Management
        Examples
        An observation relating to  Regression Reducer  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