So much great advice. Not sure I agree with "borrow other people's brains" but this is personal hahaha. I tried that for a while and it made things worse. Too many perspectives = maaaassive decision paralysis all over again.
What I did was pick ONE expert perspective and stuck with that. I think it also helps in terms of A/B testing.
You do a wonderful job of creating fomo of all the projects I want to do lol. I know Iβve said it before. I need an agent that can build everything you suggest for me. Can you create a blueprint for that agent lol?
I've found that one of the big shifts for me in getting more out of AI was the shift from coming up with a solution to a problem and asking it to implement that to just giving it the problem. Turns out Claude Code is better at figuring out solutions than I am a lot of the time!
Huh, that's pretty interesting - I don't think I've ever really asked it about UX issues, since I'm mostly building internal tools for myself. Nice to hear that it's good at that as well. I'm just increasingly trying to build the reflex of giving it problems to solve, so I'll try to add UX to the list there.
βYou can collect all the frameworks you want. You can implement all the tactics. But if you donβt know what problem youβre actually solving, youβre just guessing with confidence.β
You said it all. An interminable issue in business and life. Good article.
i love this idea so much. iβve been asking AI to tell me what my blind spots are. and i LOVE your idea of asking it what questions you SHOULD be asking! as the goes, βyou donβt know what you donβt know!β (or something like that π)
Questions over answers is the right frame. The teams I see failing with AI are the ones asking "how do we use AI?" instead of "what's our most painful workflow?"
My approach was backwards at first. Built an agent, then looked for problems it could solve. Should have started with the problem. Once I flipped that - "what takes me 2 hours but shouldn't?" - the agent became genuinely useful.
The strategic question isn't about AI capability. It's about problem clarity.
What. an. amazing. post!!!
So much great advice. Not sure I agree with "borrow other people's brains" but this is personal hahaha. I tried that for a while and it made things worse. Too many perspectives = maaaassive decision paralysis all over again.
What I did was pick ONE expert perspective and stuck with that. I think it also helps in terms of A/B testing.
Thanks for this! Bookmarking for future use :)
Thanks Mia, glad u find it helpful :)
Haha yeah I guess borrowing other people's brain can lead to analysis paralysis as well. But it's useful to identify the blind spot π
And what's most important is to take action and refine them along the way.
So true! :)
Love this series of questions, Wyndo!
Though I'm curious... how much time did you end up spending on that growth example to get to the bottom :)
haha too many wasted hours Jenny :)
More questions. Less tell me what do to. ππ»
This is how we do it ππ»
You do a wonderful job of creating fomo of all the projects I want to do lol. I know Iβve said it before. I need an agent that can build everything you suggest for me. Can you create a blueprint for that agent lol?
well, openclaw can do it for you though :)
β€οΈ
gotta figure that out first haha.
The question generation process is super cool. Thanks for sharing
hope it's helpful for you!
Thank you this help me. Start.
Omg THANK YOU so much!! This is...amazing! I was gonna say life changing lol but thought that was a bit OTT. Gonna try this right now!
haha appreciate this exciting comment! glad u find it useful :)
This resonates and Iβm definitely going to take this approach going forward
glad u find it useful!
I've found that one of the big shifts for me in getting more out of AI was the shift from coming up with a solution to a problem and asking it to implement that to just giving it the problem. Turns out Claude Code is better at figuring out solutions than I am a lot of the time!
true!
esp while building apps, I would just ask it to identify problems to solve based on pain points on UX and rank them based on impact.
Most of the time, through back and forth, it manages to find right solutions given the right context provided.
Huh, that's pretty interesting - I don't think I've ever really asked it about UX issues, since I'm mostly building internal tools for myself. Nice to hear that it's good at that as well. I'm just increasingly trying to build the reflex of giving it problems to solve, so I'll try to add UX to the list there.
βYou can collect all the frameworks you want. You can implement all the tactics. But if you donβt know what problem youβre actually solving, youβre just guessing with confidence.β
You said it all. An interminable issue in business and life. Good article.
Applies to anything life :)
Amazing to read for all of us - creators here on Substack!
I was recently asking myself same questions, so it was just in time :)
Glad to know it came just in time :)
This is such a great essay on a strategic and productive way to use AI!
This is how we can keep sharpening our brains; otherwise, they will atrophy :)
i love this idea so much. iβve been asking AI to tell me what my blind spots are. and i LOVE your idea of asking it what questions you SHOULD be asking! as the goes, βyou donβt know what you donβt know!β (or something like that π)
exactly!
this is to reveal and tackle βwe dont know what we dont knowβ
we need to understand what we are missing so we can improve them!
Questions over answers is the right frame. The teams I see failing with AI are the ones asking "how do we use AI?" instead of "what's our most painful workflow?"
My approach was backwards at first. Built an agent, then looked for problems it could solve. Should have started with the problem. Once I flipped that - "what takes me 2 hours but shouldn't?" - the agent became genuinely useful.
The strategic question isn't about AI capability. It's about problem clarity.