this is advice i might give to my younger self. (might not).
anyway..
mvp usually means minimum viable product.
but what if you applied it to yourself?
minimum viable person? lol
not minimum as in less. minimum as in essential. stripped down to what actually matters.
think about mvps in product—
they dont try to be everything. they try to be enough.
ship fast. get feedback. adapt. ship again.
dont wait for perfect. they move.
and somehow that makes them better than the thing that took three years and launched once.
so what does that look like for you as the product?
know your core functions.
what’s your lane?
what r u actually good at?
what do ppl come to you for?
put away the rest. (at least for now)
bc trying to do everything probably means you’re not doing anything well enough to make a difference.
so be modular. add skills like plugins.
learn what u need when u need it.
not hoarding knowledge for someday.
just learning the next thing that makes u more capable right now. then adapt.
iterate publicly.
ship versions of work, in real time. so today, not tomorrow.
put work out there before its perfect. let feedback make u sharper.
treat mistakes as data, not failure.
bc the only way to know if something works is to test it.
and the only way to test it is to ship it.
this concept isnt for everyone.
more for ppl who can separate themselves from their work.
where they can deconstruct, rebuild, optimize themselves as the mvp.
builders, designers. ppl who builds tools, apps, widgets, ect.
ppl who can become a prototype. a version.
someone who can upgrade.
a lot of products fail.
good ones iterate until they meet the demand.
maybe ppl work the same way.
maybe ur not supposed to have all the answers set before launch.
maybe u just ship the first version and see what happens.
then build the next one.
—
Until next time,
Riley
p.s. ur not the final build. ur just the current version.
