CareerPlug

• Product

   Assignments:

  Product Teammate

  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

  • Must have a position with the reach of 1.1 or higher
  • For this role, you must be milestone 3 or greater inProduct Knowledge
  • For this role, you must be milestone 2 or greater inProcess Knowledge
  • For this role, you must be milestone 1 or greater inBusiness Knowledge
  • For this role, you must be milestone 1 or greater inGoal Management
  • For this role, you must be milestone 1 or greater inCollaboration

  Examples

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

  ---

  • Discovery / Shaping

     Assignments:

    Value Shaper

    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

    • Must have a position with the reach of 2.1 or higher
    • For this role, you must be milestone 2 or greater inBusiness Knowledge
    • For this role, you must be milestone 2 or greater inCollaboration
    • For this role, it is recommended to be milestone 1 or greater inData analysis / synthesis
    • For this role, you must be milestone 3 or greater inProduct Knowledge
    • For this role, it is recommended to be milestone 1 or greater inQualitative Research
    • For this role, you must be milestone 1 or greater inProduct Discovery
    • For this role, you must be milestone 2 or greater inDecomposition & Sequencing

    Examples

      Observation created over 1 year ago

    Featuring:Brittany A.(4) Work Together, Win TogetherPrinciple #4 - We continuously improve how we workCollaborationStakeholder / feedback managementValue Shaper

    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:

    Code Reviewer

    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

    • Must have a position with the reach of 2.1 or higher
    • For this role, you must be milestone 2 or greater inCollaboration
    • For this role, you must be milestone 2 or greater inEngineering Communication
    • For this role, you must be milestone 1 or greater inData Modeling / Management
    • For this role, it is recommended to be milestone 1 or greater inEngineering Prioritization
    • For this role, you must be milestone 2 or greater inRuby
    • For this role, it is recommended to be milestone 2 or greater inRails

    Examples

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

    Code Creator

    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

    • Must have a position with the reach of 1.1 or higher
    • For this role, you must be milestone 1 or greater inProject Management
    • For this role, you must be milestone 1 or greater inData Modeling / Management
    • For this role, you must be milestone 1 or greater inEngineering Communication
    • For this role, you must be milestone 1 or greater inEngineering Prioritization
    • For this role, you must be milestone 1 or greater inEstimation
    • For this role, you must be milestone 2 or greater inRuby
    • For this role, it is recommended to be milestone 2 or greater inRails
    • For this role, it is recommended to be milestone 1 or greater inDecomposition & Sequencing
    • For this role, it is recommended to be milestone 1 or greater inSoftware Testing
    • For this role, it is recommended to be milestone 1 or greater inEngineering Systems Management

    Examples

    An observation relating to  Code Creator  has not been publicly recognized yet.