Earlier quoted context omitted.
FWIW this is the best kind of job ever for me as well: "when you started you didn't even know if there was a solution." Regardless what the problem is - as long as I know _nobody knows if there is a solution_ it's an instant sugar rush. You are free to bang your head against a stone wall for months trying to crack the damn thing. OFC you need to deliver in the end. And this requires then ruthless "worse is better" me…
Interesting, this is a trap that I've seen multiple senior hires fall into. In my experience "we have a problem but no solution" often means (a) there actually is a solution but it's too expensive to implement, (b) there are organizational reasons why this problem exists and a new hire doesn't have the experience or credibility to navigate it or (c ) there is no solution to the problem or the solution is very complex…
(d) although the initial statement seems credible, the problem is actually ill defined and under specified and therefore not solvable as originally stated.
Example: our start-up plans to "fix health care"