My thoughts

As a designer, it's important to understand the problem. Very often designers gravitate toward solution-first processes. I used to fall into this category. It offers quick outcomes which some stakeholders love, but long-term problems.

As I matured as a designer, I've learned it's better to solve the users' problems, rather than adding features that impress your peers. Even if this means seeking out separate cohorts to understand how they're using a product and what they'd like to improve. Obviously, this can take more time, but it's like getting a flu shot, 10 minutes at the doctor is better than 4 days in bed. This seems like an obvious thought, but it often get's lost, no matter how small or large the company.

Sometimes you need to take a risk, but as a specialist, we can hedge our bets. Exploring ideas is extremely important, but making sure you explore the right ideas is just as equally important. Working for a marketing firm early on in my career taught me to make fast decisions, rather than getting lost down a rabbit hole. While working in large companies, I learned that fully understand a problem will cost less down the road. Efficiency is key and it's something that I strive for.