By Daniela Papadakis Bared
Having an idea is exciting.
For a moment, everything feels incredibly clear.
You see a problem. You imagine a solution. You start thinking about what it could become.
Then you start talking to the people who actually experience the problem.
That’s when things get interesting.
As I’ve started exploring an idea in legal technology, one of the biggest lessons I’ve learned is that having a good idea and understanding a real problem are two very different things.
I started with assumptions about what people needed.
The more I listened, the more I realized that the most valuable part of the early process wasn’t explaining my idea.
It was asking questions.
Your Experience Is a Starting Point, Not Proof
Some of the best ideas come from problems we’ve experienced ourselves.
That’s certainly true for me.
My own experience in law school made me think differently about how students access information, organize materials and navigate the learning process.
I knew what had frustrated me.
I knew what I wished had been easier.
And I knew there were things about the experience that felt unnecessarily outdated.
That personal experience gave me a place to start.
But it didn’t prove that I understood the entire problem.
My experience was one experience.
Other students may struggle with completely different things.
Something I found frustrating might not bother someone else at all. A solution I would have wanted might not be something another student would use.
That’s why personal experience can inspire an idea, but it can’t be the only evidence supporting it.
Eventually, you have to get outside your own perspective.
Asking Is More Valuable Than Assuming
One of the first things I started doing was talking to law students and people who had recently gone through the experience.
Not selling them anything.
Not trying to convince them that my idea was good.
Just listening.
What resources do you actually use?
How do you study?
Where do you find your materials?
What frustrates you?
What takes too much time?
What do you wish were easier?
The answers matter, but so does the way people answer.
Sometimes someone describes a problem you hadn’t considered.
Sometimes they confirm something you’ve experienced yourself.
Sometimes they tell you that something you thought was a major issue really isn’t that important to them.
All three outcomes are useful.
The purpose of early research isn’t to prove yourself right.
It’s to get closer to the truth.
People Don’t Always Experience the Problem the Way You Think They Do
This is probably one of the most interesting parts of exploring a new idea.
You begin with a version of the problem in your head.
Then reality starts editing it.
Maybe the problem is bigger than you thought.
Maybe it’s smaller.
Maybe you’re focused on the wrong part of it.
Maybe the real frustration happens one step earlier.
Maybe people have already created their own workaround.
Those workarounds are especially interesting.
When people are consistently sharing documents, creating spreadsheets, building informal systems, asking the same questions or finding creative ways around an inefficient process, they’re telling you something.
They’re already trying to solve the problem.
You just have to pay attention.
Don’t Fall in Love With the Solution Too Early
This is difficult.
Once you imagine a product, you naturally start becoming attached to it.
You picture what it could look like.
You think about features.
You imagine people using it.
You start mentally building a company before you’ve fully established whether the problem is important enough to solve.
I’ve had to remind myself to stay more attached to the problem than to any particular version of the solution.
Because the solution can change.
And it probably should.
If new information tells you that your original idea isn’t quite right, changing direction isn’t failure.
It’s learning.
I’d rather discover early that an assumption was wrong than spend months building something based on it.
A Survey Can Tell You Something. A Conversation Can Tell You More.
Collecting responses has been incredibly useful.
It gives you patterns.
If enough people mention the same frustration, you start paying attention.
But I’ve also learned that a checkbox or short answer can only tell you so much.
A conversation allows you to ask:
Why?
Why is that frustrating?
What do you do instead?
How often does that happen?
What would make that easier?
Would solving it actually change anything for you?
Sometimes the most valuable insight comes from the question you didn’t originally plan to ask.
That’s why I think understanding a problem requires both data and conversation.
Numbers can show you a pattern.
People can help you understand what the pattern means.
Not Every Problem Needs a Company
I think this is an important question for anyone interested in entrepreneurship.
A problem can exist without being a business opportunity.
People can complain about something without being willing to change their behavior.
Something can be inconvenient without being painful enough to solve.
A potential solution can be useful without being something people or organizations would actually pay for.
That’s why understanding the business side matters too.
Who experiences the problem?
Who benefits from solving it?
Who would use the solution?
Who would pay for it?
Those may not always be the same person.
A product can solve a genuine problem and still fail if the business model doesn’t make sense.
For me, that’s part of what makes entrepreneurship interesting.
You’re not solving one puzzle.
You’re solving several at the same time.
Validation Isn’t About Getting People to Agree With You
When you’re excited about an idea, positive feedback feels good.
“I love that.”
“I would use that.”
“That’s such a good idea.”
Those responses are encouraging.
But encouragement isn’t necessarily validation.
What people say they would do and what they actually do aren’t always the same thing.
Real validation requires looking beyond compliments.
Are people already trying to solve this problem?
How frequently does it happen?
How much time, money or effort does it cost them?
Would they change their current behavior for a better solution?
Would the organizations involved see enough value to adopt something new?
Those questions are harder.
They’re also much more useful.
Building Starts With Listening
I’m still early in this process.
I don’t have every answer.
And I’ve actually become more comfortable with that.
The goal right now isn’t to pretend I know exactly what the final product should look like.
It’s to keep learning.
Talk to more people.
Ask better questions.
Challenge my assumptions.
Understand the institutions involved.
Figure out which problems are simply annoying and which ones are genuinely worth solving.
Then build from there.
I used to think entrepreneurship started with an idea.
Now I think it starts a little earlier.
It starts with curiosity.
With noticing that something could work better.
With asking why it works the way it does.
And then having enough humility to listen when the people experiencing the problem tell you something different from what you expected.
The idea might be what gets you started.
Understanding the problem is what gives you something worth building.