How do we know we're solving the right problem?

As designers we spend a lot of time working on projects that already have problems, goals, and expectations set in stone. Often, our contribution is evaluated based on time to completion.

Done usually means design files have been approved by stakeholders and handed of to development, sometimes, never to be seen again.

But how do we know what we made is good or even useful for people. Did we even make the right thing in the first place?

By shifting the focus away from deliverables we can start to prioritize outcomes and reframe our definition of done.

This month we will discuss working with product managers, engineers, and stakeholders how and shifting the definition of done from completing deliverables to measurable improvements customer outcomes.