Why I'm Building Flashly

The Problem With Only Studying Product Management

An MBA gives you frameworks, case studies, and a lot of language for talking about product decisions. What it doesn't give you, on its own, is the experience of actually making one and living with the consequences. Case studies resolve in a lecture. Real decisions resolve in production, weeks or months later, often in a way you didn't predict.

That gap is why I started building Flashly. Not because I had a business plan I was confident in, but because I didn't trust myself to actually understand product thinking until I'd been forced to make product decisions with something real at stake, even at a small scale.

Why Not Just Wait for a Job to Teach Me This

I could have waited — finished the MBA, found a product role, learned on the job the way most people do. That's a reasonable path, and I'm not arguing against it. But waiting felt like choosing to stay a beginner longer than necessary, and I've never been comfortable with that when there was a cheaper way to start sooner.

Building something myself, even something modest, is the cheaper way. It's low-stakes enough that mistakes don't cost anyone but me, and real enough that the mistakes still teach something.

What Building It Has Actually Taught Me

The biggest surprise so far is how much of the work isn't building at all. It's deciding what not to build yet, which is a muscle engineering never asked me to use — in maintenance work, scope was usually defined for me by what was broken. Here, scope is a decision I have to keep making, repeatedly, against my own instinct to add "one more thing" before calling something done.

The second lesson has been about feedback loops. In plant maintenance, you find out fast whether a fix worked — the system runs or it doesn't. Building a product on your own, especially early, the feedback is slower and quieter. You have to get comfortable moving forward without the kind of immediate confirmation four years of engineering work had trained me to expect.

Where This Fits Alongside the MBA

Flashly isn't a side project competing with the MBA for attention — it's closer to a lab for testing whether what I'm learning actually changes how I decide things. When a course introduces a framework, Flashly is where I find out if I can actually use it under real constraints, not just recognize it on an exam.

I don't know yet where Flashly ends up. That's honestly fine. The value it's already delivered — a faster, more honest read on my own product instincts — would have been hard to get any other way.