2d • Posts
"Its done when theres nothing left to improve" - I made a mistake
This isn't good for my perfectionism, but I've been obsessing over the perfect OS for the past few years and I have a different take on this Alex video.
But I made a mistake in mis categorizing Product management as a one-off thing, and not as a its a iterative improvement type thing.
I've had this habit to condense everything to a final version (workbook, updated slide deck coursework, case study deck, etc) and realizing it comes with iterative improvements.
But man, thats not the way to do it. Its not like the video, where its one book gets posted and thats it. But its iterative in nature.
If it gets better with use, with feedback, its better to put out that MVP than keep tinkering behind the cave.
So when you have something thats going to be permanently done and posted (e.g. theres just one version) then you get outsided returns for making it super polished. This is a one off project.
But it can be built with people, in public, with feedback, you end up with a stronger and more robust product. Alex made videos and content, and got feedback, and then curated the best in a book.
Luckily this is most processes or production lines, where its expected things will come up, and to make SOPS and workflows
I've been obsessing over how to make the final thing ((write the end book)) without getting feedback, mis classifiying it as a one-off project even though Product Management is that iterative process.
Every since I got into obsidian, I noted my habits and routines, and the partners and clients and before AI the excuse was "I have no time".
With AI, we can have it iterate and solve and implement the fixes as simple as quick feedback cycle.. "hey do this, ok hold on, ok what do you think"
I remember laughing so loud by myself when I built my first vibe coding thing, that I was like this is it. Everything I've done, skills or whatever aren't being made useless, its just giving it immense power to be implemented.
So I tinkered and strategied to the point where I have something that helped a few clients, but still incomplete.
The journey to make something perfect (e.g. a company culture and OS) isn't a one-off deal.
Just what I'm thinking about.
Still super happy with how the program is unfolding. I have a huge workbook update, and cheat sheets and visuals to come out with some bots to support.
But man, I do want to pump on the breaks, and say "well its not perfect on launch", and need to be reminded to say "its good enough and helpful as is".
1
0 comments
"Its done when theres nothing left to improve" - I made a mistake
powered by
skool.com/delegate-and-elevate-1300
Get trained, certified and placed into a company as an AI Scaler
Suggested communities
Powered by