We are looking for a Product Designer to join our rapidly growing product team. This is a great opportunity for designers who want to make an impact in a variety of disciplines and help shape the design practice at Lessonly as our team continues to mature.
Your primary responsibility will be to serve as the designer on one of our cross-functional squads (mix of a product manager, QA, and engineers all focused on a shared set of objectives). Because you’ll be the designer on the squad, you’ll have the opportunity to contribute at every step of the way: from user research and requirements gathering to wire framing interactions and visual interface design.
Even though you’ll technically be the designer for your squad, there will still be lots of opportunities to collaborate with the other designer(s) (we have an awesome designer now, and we are hiring another soon). Expect weekly meetings to review recent work, work through problems together, and share ideas. Expect heavy collaboration on things like the design process definition and the development of a style guide and UI library.
How We Work at Lessonly
We are a tight-knit group with diverse backgrounds who value our culture. Individually, we strive to be humble, hungry, and people-smart. As a team we put learners first, we share before we’re ready, we ask clarifying questions, we highlight what’s working, we have difficult conversations, we get agreements, and we make time for life. These aren’t just slogans we put on the wall… these are values we aspire to live by every day.
Role & Responsibilities
Problem/Opportunity research (10-20%)
Success looks like:
The insights gathered around opportunities to improve customer outcomes are sought after and become habitual to the organization as product decisions are made.
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.
Product Managers and Product Designers will work closely on both the contextual/JTBD and usability types of discovery and research. Though not a requirement, PMs will often specialize in the JTBD type, while PDs will often specialize in the usability type.
Problem/Opportunity research analysis (10-20%)
Success looks like:
As you and the squad converge on an area of focus the stakeholders understand and agree on the importance of the endeavor as well as hypotheses around the value proposition.
Research without synthesis is like a beat and lyrics without a song. The research should be the ingredients to the clarity that is required for great product work. However, the compilation and synthesis of the research along with hypothesis creation is what brings true clarity.
Solution definition (40-60%)
Success looks like:
Successful team collaboration to achieve understanding and agreement about desirable, viable, feasible, and usable solutions to big problems.
Next up is probably the most visible aspect of the job. This is when solutions or concepts are created, prototyped, tested, and iterated upon. We will use the full library of techniques such as lo-fi as wire framing, hi-fi live-data prototypes and any of the other techniques in between. 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.
Solution delivery (20-30%)
Success looks like:
Your squadmates relying on you for your strong design opinion while being flexible and open to ideas during the collaborative convergence on a simple, elegant, desirable, viable, feasible, and usable solution and the necessary UX/UI.
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.
Dream big, start small
As demonstrated by being able to understand a problem, dream big dreams on how to solve that problem, consider how might we work backward to the first small steps in that direction, and most importantly helping everyone (stakeholders and teammates) all of the way through this journey.
“Here is what this could be… if you like that, here is how we could get there”
User-centered systems design
As demonstrated by being known to think through the complete experience when tasked with a design challenge. Myopically focusing in on the single task at hand can be detrimental to a software offering. It is important to have the ability to think deeply about the problem at hand and the potential impacts to experience across the rest of the system for the user and internal stakeholders (i.e. our team's ability to build and support the proposed solution).
As demonstrated by being known for the ability to make an estimate, establish a deadline collaboratively, and hit that mark.
Producing value, not work
As demonstrated by being known for asking clarifying questions about the intended impact of the work, weighing options, and devising creative solutions to complex problems.
Research execution and synthesis
As demonstrated by being a proficient interviewer or wanting to learn to be. Talking to customers is a HUGE part of our process. Knowing the right questions to ask and how to make sense of the answer is an important part of the job.
Showing progress via iteration
As demonstrated by being known for taking a big problem and decomposing it into shippable chunks that can ensure all parties are aligned on the outcome.
As demonstrated by having built user interfaces that have been implemented and are visually appealing and on-brand.
Also as demonstrated by the proficiency with at least one screen design tool. If it’s not Sketch, you should be willing to learn Sketch.
Designers on our team should be comfortable spending time diving into the functionality of a pleasing user experience that fits within the current application and should have a visual eye that allows them to design to meet our current standards.
Bilingualism (business and technical)
As demonstrated by being able to translate the non-technical business needs into a clear technical action plan and vice versa, seamlessly.
Web tech (client-side engineering)
Lessonly benefits to help you do better work and live a better life:
Health insurance—dental, medical, and life. We help you stay covered.
Competitive pay, a 401k plan, and equity. Money matters and we like to think about the ways you can win as we win.
Tech Stipend. Helping you with the tech gear you need for the things you do.
Unlimited paid time off. Keeping this benefit simple so it’s simple for you to use it when you want to use it.
Parental leave. Because we think it's important to spend time with your new family.
Drinks and snacks. What’s your favorite LaCroix flavor?
Yoga, Nintendo, and Pop-a-Shot.
Free parking with downtown Indianapolis office.
March 7, 2019