Explore Lessonly's Assignments

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

Showing only relevant Assignments

  • Lessonly

     Assignments:
    --None--

    • Product & Engineering

       Assignments:
      --None--

      • Product

         Assignments:
        --None--

        • Product Design

           Assignments:

          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.
          • Designing for MVP + additional releases

          Feedback loop/deliverables:

          • The feedback loop for this role is qualitative... how complete are the designs as measured by your squadmates.

          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
          Examples
          An observation relating to  UI Designer  has not been publicly recognized yet.

          We facilitate design activities aimed at collaboration, clarity, and alignment

          Full Description

          Success

          • Business / workshop goals achieved in time allotted (ex: Decisions made, solutions identified and spec'd, etc)
          • Confidence in presentation and activity management
          • Keeps all participants engaged. (ex: everyone participates equally)
          • Selecting the best activities for the type of outcome desired + group dynamics
          • Knows when to pause on the agenda to dig into a conversation vs. save until after the session.

          Feedback Loop/Deliverables

          • Workshop agendas and activities
          • Next steps after workshops
          • Post-workshop survey (for large, special facilitation)

          Details

          • This is a critical role in product discovery, as collaborating with 3+ people is challenging in and of itself. A facilitator alleviates the load of a discovery team bearing the weight by themselves
          • Sometimes, tricky product and/or collaboration problems call for a leader to facilitate that collaboration. This role delivers on that collaboration with confident, thoughtful leadership in the room, and creates an enjoyable experience that arrives at needed goals.
          Requirements
          Examples
          An observation relating to  Design Facilitator  has not been publicly recognized yet.

          As design reviewers, our goal is to make our application (and ourselves) more awesome!

          Full Description

          Success

          • Giving thorough, thoughtful design critique while upholding our company core values.
          • In early reviews, asking the right questions to evaluate if our users will understand, enjoy, and benefit from the designs
          • In late reviews, ensuring designs meet standards and cover all aspects of the checklist (accessibility, mobile, error states, unhappy paths, design system adherence, tone)

          Feedback loop/deliverables

          • Attendance at design critique sessions
          • When necessary, whiteboarding or real-world examples sent to the designer

          Details

          • This role should be played by many on the design team, as we create a supportive and collaborative atmosphere.
          • It's important that even non-milestone 2 designers participate, but they should not be the only participants in a design critique.
          Requirements
          Examples
          An observation relating to  Design Reviewer  has not been publicly recognized yet.

          We create, prototype, test, and iterate concepts in collaboration with the entire squad in pursuit of desirable, viable, feasible, and usable solutions

          Full Description

          Success:

          • Validating and learning as quickly as possible with collaboration being a major key. Our value of sharing before ready is most applicable to this role.

          Things you'll do

          • Utilize Lean UX methods used to create successful team collaboration to create desirable, viable, feasible, and usable solutions to big problems.
          • Create, prototype, test, and iterate concepts
          • Use the full library of techniques such as lo-fi, wireframing, hi-fi live-data prototypes and any of the other techniques in between.

          Feedback loop/deliverables:

          • Designs that enable clarity of how a problem will be solved.
          • Validated solutions to the problems/unmet needs proposed
          • When necessary, you'll work with the Opportunity shaper and Discovery engineer to flesh out the execution section of investment canvases

          Details:

          • Solution definition is the most visible aspect of the designer position: creating, prototyping, testing, and iterating upon solutions and concepts.
          • We will lean on you to influence best design practices when it comes to choosing prototype fidelity, finding ways to learn and validate, collaborating within and between product teams, and encouraging the sharing of ideas and concepts early on.
          • Iteration and Sharing Before Ready are two concepts at the center of what it takes to be successful in this role. Trying to go it alone will ultimately lead to failure. You should think of yourself as a shepherd of the solution, not as someone who owns it in isolation.
          Requirements
          Examples
            Observation created over 5 years ago

          https://lessonly.slack.com/archives/C8H3ENQ2J/p1582565374007400

          Just wanted to give a quick shout out to Ashley on something small, but amazing.

          I'd love for us to do more of this style of collaboration. Small bits along the way. Sharing early and bringing in feasibility and viability as you go. I believe this is vital to the continuous discovery/design/delivery methodology we are striving for.

          I absolutely love this!

          Keep it up!!


          • Product Research

             Assignments:

            As Generative User Researchers we help define (with evidence) the problem/unmet need we’d like to design a solution for.

            Full Description

            Success looks like:

            • Research initiatives and insights have a meaningful and consistent impact on how decisions are made, both within and outside of Product.
            • Understand potential customers and current customers that fall into the ideal customer profile dictated by the company/market strategy. Success is understanding these customers better than anyone.

            Feedback loop/deliverables

            Details:

            • You’ll notice that much of the language being used comes from the double diamond style of thinking. We build software to solve real problems for real people. The first step in doing that is having a deep understanding of the problem we are trying to solve and the context of those that are trying to make progress. Defining the Why.

            Relevant excerpt for illustration

            • This excerpt from the book Inspired illustrates a useful take on research as an important part of the prod dev process:

            ... when we talk about how we do product discover, we are continuously doing two kinds of rapid learning and experimentation. One kind of learning is qualitative, and the other is quantitative.

            Especially with the qualitative learning, some of our research is generative, which is understanding the problems we need to solve; and some of our research is evaluative, which is assessing how well our solution solves the problem.

            User researchers are trained in this range of qualitative techniques (and some of them are also trained on the quantitative techniques as well). They can help you find the right type of users, craft the right types of tests, and learn the most from each user or customer interaction.

            The key to tapping into the real value that these user researchers can provide is to keep in mind that the learning must be shared learning.


            • This excerpt from a blog post illustrates the difference between evaluative and generative research:

            The goals of generative and evaluative research are very different.

            Generative research helps you define the problem you’d like to design a solution for.
            Evaluative research evaluates an existing design (in prototype form or in final form).

            Requirements
            Examples
            An observation relating to  Generative User Researcher  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