Inspired by a problem.

I didn’t decide that I wanted to start a brand out of the blue. In my last post (New York + New Friends), I indicated that this journey began with:

1. Identifying a meaningful problem or challenge that exists, and an opportunity to help solve and create value;

Like many others, Habelo started with identifying an unmet need. It was about 5 years ago that I recognized a skincare opportunity… something that I actively wanted to address for myself. (Without stealing the thunder for a much-later launch, there was a part of me that seemingly aged faster and more aggressively than the rest of me!) And while I knew that it was a common concern, I found that there wasn’t a simple, effective solution out there.

That need was exacerbated in 2020 during the pandemic, so I MacGyver‘ed a fix while working from home and it worked. But it was also messy, inconvenient, expensive, and time-intensive… ultimately, not realistically sustainable over time, especially as the world opened back up and I wasn’t tethered to my desk chair at home.

The Habelo brand journey is fundamentally the creation of an effective, elegant solution for a problem that exists (vs. me checking some randomly invented personal career progress goal).

I began by creating a clear
“Problem Statement.”

Once inspired by a problem, the work on Habelo began with drafting a problem statement. It sounds simple — but this was (and is) the foundational first step in product development and a touchstone for everything that follows. Getting super clear upfront helps to ensure that the product, service, or solution that is created actually does the job that it’s intended to do — solving the problem and delivering on it’s promises.

Not only does this statement help you get clear about what you are trying to solve, but it is also the reason that someone would buy your product (as long as it actually solves the problem). The problem statement is not the solution itself — that comes with the work that follows.

I liked how Greg Coticchia said it in his Forbes article:

“The world’s greatest innovators are master problem spotters and solvers. They have a radar for identifying friction. Then—and only then—they apply their product development chops to find a solution that doesn’t exist or improve on existing solutions that don’t fully solve the problem. But pinpointing problems isn’t genetic—it’s a learned skill.“

Here’s a good reference from Scott Kiekbusch, for writing one yourself: How to Write Effective Problem Statements & Deliver Products That Matter

Even if you are not developing a product,
knowing how to create a strong Problem Statement is useful

I’v found that even when I’m thinking about developing a product or service, when I take the time to get really crisp in how I articulate a problem (declutter all of the competing ideas and possible solutions in my head), it helps me be more effective and efficient in solving any problem at hand.

Perhaps one of the biggest benefits — to me — is that if I put in the effort to define the problem well from the start, it makes communicating the challenge (and influencing other people to care, engage, participate, invest in success, etc.) so. much. easier. and more effective. Together, everyone is clear and focused on the real issue vs. having the squirrel effect of bright, shiny, competing ideas.

Try it out on something as simple — see how it helps you (and people around you) get to better solutions and outcomes.

Newsweek article by Nicolas Cesare and Entrepreneur article both are helpful.

Cheers.