Stupid question? Do I understand this correctly?
When building software is this how life works?
Words, ideas, pencil and paper stick figures > Designer > Someone who can build (engineer)
Is that typically how this works?
Does that process look differently if you build with no or low code tools?
Thank you. I know this is basic.
There are a million different ways to do this, and although you're overlooking some of the details, your basic process is correct. If you're unfamiliar with how this all works, I'd really recommend picking up a copy of Lean Startup (or just spend a few hours reading articles about the methodology).
Think of product development as a cycle. The process that my company follows when building products for our clients looks like this:
But if you want to skip a few steps, already feel like you've validated your idea, are willing to take some risks, or want to do it on the cheap, you can basically boil it down to Design and Development. Depending on the scope and scale of what you're trying to build, the simple version of this could be a real rocky road, but you'll have fun and learn a lot.
Thank you. I'll get back into lean startup. I initially read that with business/sales filter. Don't build a full blown product that no one wants. Build a little MVP and show it to people....I didn't mean to diminish the full cycle,just trying to simplify for my pea brain.
👍🏻 yup, don't overthink it too much, but be ready to fail (and recover), too.
If you've never done this before, the best piece of advice I can give is: "build it and they will come" is bullshit. Everyone likes building stuff and (almost) no one likes marketing and selling it. In my experience, this is where 90% of startups/products fail.
thank you, that's great advice. Selling is the only experience I have and I've never had someone breaking down the door with credit card in hand. :)