The second part in a multi-part series about the "Lean UX" approach to product development at TheLadders.
Last time we met, I introduced the concept of "Lean UX", and discussed how we're putting it to work in the development of our mobile application. We got our arms around the core hypotheses, and did some quick tests with users. Next, we wanted to see how our concepts would shake out with recruiters - because after all, we can't make job seekers happy if they aren't hearing from the people who have the jobs.
The Meaning of "Team" (and why it's essential to Lean UX)
Before going further, please allow me a brief interlude on what it means to be a "team" at TheLadders. We work in a loose agile/scrum approach (more buzzwords!) - which essentially means that cross-functional teams take on a problem statement and solve them independently. While the size of the teams vary, they often follow this configuration: development team (3-5 engineers including Q/A), a scrum master (or tech lead), a product owner, a UX designer, and a Visual Designer. (Additionally, copywriters work across teams.) The scrum master, product owner and UX designer form a sort of trifecta of team leadership, but in general, the entire team collaborates around creating solutions.