Empowering Nigerians, one workshop at a time!
That was the vibe I brought to @bravpuls_tech community, where tens of them learned how @fedibtc works and the power it gives to them through its #superapp
I will always say, Stay EMPOWERED!
#Bitcoin#thecoachayobami#freedom
BITEDU Network is a non-profit organization advancing Bitcoin education through curated, accessible, and high-quality learning resources.
Join our mission and be part of building a sounder future. Register through the link below to join our community.
https://t.co/LLxZkP1rt9
Day 11/30
π€ You used to avoid feedback π.
"Let me finish first."
That "you" is me.
I built AgroLynk quietly. Then demoed it.
People didn't care about half what I built.
Feedback isn't for after. It's for while you're building.
#m4acelearningchallenge
What a day!
I attended the build with Ai hosted by @gdgoc_unilorin and it was really interesting and insightful.
Even though I wasn't actively a Dev I joined the Dev session and the theme: Building with Google ai studio and Antigravity was really interesting.
#BWAI
Day10/30
π€ User journey mapping taught me something.
I knew what AgroLynk did, but not how users would move through it.
Mapping it showed: too many steps, too many places to get stuck.
Still learning to see through their eyes, not mine.
#m4acelearningchallenge
Day 9/10
π€ Finding pain points isn't easy.
A user says "I need this feature."
But the feature isn't the pain. The broken workflow is. The wasted time.
Now I ask: "What's frustrating you?"
Still learning to listen deeper.
#m4acelearningchallenge
Day 7/30
I used to think PM was about building solutions.
Now Iβm learning itβs about understanding problems.
Get the problem wrong,
and everything else doesnβt matter.
#m4acelearningchallenge#ProductManagement
I'm starting to realize how easy it is to assume things in product.
You see a problem and think you understand it.
But do you?
A problem assumption might not matter to the user. Or might not exist at all.
Assumptions aren't real until you validate them.
#m4acelearningchallenge
I've been looking at "users" wrong.
I thought users were one group with one mindset.
But two people can use the same product for completely different reasons.
So when we say "the user wants this"β¦ which user?
Still figuring this out.
#m4acelearningchallenge
Day4/30
π€ MVP isn't what I thought.
At first, I thought it meant "build small, launch fast."
But it's deeper.
MVP = learning fast without wasting effort.
π You're not building to impress.
π You're building to be wrong earlyβ¦ and correct quickly.
#m4acelearningchallenge
They say ship fast. At first, I agreed.
But then I paused⦠because shipping without clarity? That's just chaos with a deadline.
Building an MVP that isn't complete, saying "We'll fix that along the way," just to meet a deadline that can be changed?
Day3/30
π€I used to think about the difference between a Product and a Feature.
But then, something clicked.
If you can separate it and people still pay for it β product.
If you remove it and it feels incomplete β feature. I used to miss that a lot.
#m4acelearningchallenge
Day 2/30.
They say PMs sit between business, tech, and users.
At first, I just moved on.
But then I paused. Because that's a lot to balance. Users want simple. Engineers think systems. Business wants results.
And one person has to make it all work. #m4acelearningchallenge