How do you know what feature to put on a product? Or why isn’t one working? Using UX and Marketing Research, we can figure out what your users want before you try to build it. Or we can find out why your product isn’t working out the way you thought it would.
Then we use the puzzle pieces available (people, resources, and budget) to find the best solution.
What kind of problems can we help you with? Well, we can’t help with a break up, but we can help if part of your business isn’t functioning right (or could be better). Our data-driven mindset and creative problem-solving skills are perfect for finding solutions.
Processes are our specialty. We’re like a mix of business analyst and magic worker. We look at every angle (technology, people, etc.) to ensure your processes are working efficiently and effectively, so no one is losing time or money.
Our Process To Find Your Solution
The Different Design Solution Methods
Human Centered Design
Basically, in Human Centered Design the human comes first. While it seems that’s the way it should always be, sometimes budgets, the boss’ desires, or technology restrictions are the focus.
We rely heavily on research, observation, and collaboration to ensure the people feel the problem has been solved. Often you find during the process, that the real issue was not the one you thought it was.
This is “thinking outside the box.” The process employs creative strategies and approaches that encourage crazy ideas. Then while working through those crazy ideas, you find different perspectives/elements that might be useful for a new solution.
It’s often used for larger issues, like social needs, as there’s not just one solution, but multiple solutions working together for the same goal.
Think of Systems thinking as more ECOsystems thinking. The concept is that if you change ONE thing (like adding a nonnative species), you inherently affect the whole system (like wiping out a habitat).
So when we’re looking at big picture solutions, especially in large organizations and processes, we account for all the possible inputs and outputs that could change how the information flow works.
Case Study: Changing a Process
A digital department acquired a new user experience team. The team was having a hard time fitting into the current project plan. People from all sides were frustrated with the process, as work was often duplicated and/or deadlines pushed due to incorrect or unprovided information.
They needed an updated process so the whole digital department knew where UX fit into projects and how they would interact with the team.
We learned the process, and went to the groups that were in each step. We asked what they didn’t know, what they wanted to know, what wasn’t working, and how they thought it should work.
It was a combination of people not knowing what UX does, nor who did what on the team. And with the new addition, the way the budgets were created would have to change.
The End Result
There were multiple deliverables. The favorite piece was this UX Process Plan. It showed what the team did, who in UX was responsible for what, when UX should get involved, and approval steps.
It also showed disparity between when the UX team was currently brought in versus when they should be. Additional materials showed how they could be integrated earlier into the project to reduce time and costs.