When solving a problem, it’s easy to get lost in the process. As more variables are introduced, it can be hard to keep everything straight and predict where you’ll end up. This is especially prevalent in UX or service design projects where astute organization and accurate documentation mean the difference between an innovative solution and absolute failure.
It’s 3 months after your company’s new product launches and there seems to be an ominous feeling permeating through the cubicle walls. Then it hits your inbox, an email emblazoned with a red exclamation point and the subject line “ATTN Product Team: Staff Meeting.” Clicking in, you see the somewhat passive-aggressive message from your director stating that the team is about to get slammed. The product launch has been a near failure and changes need to be made ASAP. It’s crunch time.