In this episode, other than saying "done" a lot, we tackle the question of how we know when our work is complete.  Is the definition of done based on time, deliverables, contract terms, solving a particular problem, the ability of the team to move forward, or based on some form of metrics? Hop into this pod to hear us hash this out in our usual fashion!

This episode we discuss breaking up with clients or peers and the heartbreak that may or may not go along with it ;)  We talk about different scenarios, how we have tackled them in the past and what we have learned through the process. Come with us as we explore the world of relationships!

This time we try to dissect and unravel UX strategy. While UX inherently involves strategic thinking are there specific UX strategy deliverables? Is all of our work a strategy deliverable? How do we define and sell strategy? Where does it fit within product and business strategies? Join us as we wind down this curious path...

In this episode we dive into the idea of titles and roles: why are there so many? and what do they say about what we actually do? We discuss how skills can vary across UX roles and how we might ensure that people understand what we do based on our titles. We also get into the overlap of skillsets that are shared with other roles that may or may not fit under the UX umbrella, and how we navigate and collaborate in those scenarios. So what is in a title anyway? Have a listen to get our take!

Today we talk estimates! (super exciting eh?) But it is one of those things we have to do and getting right is tricky. We dig a little deeper into pricing (one of our previous episodes) and we discuss the details to our estimating process. What do we typically include and how do we handle scope creep/overages to protect ourselves?  We also discuss how we might approach estimating from a value/outcomes perspective vs screen by screen when it comes to the design work. Get your spreadsheets out and join us :)

Today we talk about problem statements, yay! We discuss how you actually get to defining the problem and how that ties into discovery. We try to dig into the activities we could be/are doing, and what has or hasn't worked in the past. 

In this week's episode we talk about the discovery process. We look at client expectations, our own definitions and objectives for what we coin "discovery", as well as current pain points and ideas to improve our processes.  Come discover with us!

We often get asked to do "best in class" assessments or to design best in class solutions but who decides what this means? Who defines what's considered "the best"? What is it trying to answer or how does it support the underlying design problem? What do client's mean when they are looking for this, and how do we do a better job having discussions about before we scope? We may not have any answers, but we sure do have a heated discussion!