As I dive deeper into poketto.me, I keep running into an increasingly tricky question:
How much time should I spend exploring new features — and how much actually building them?
Having worked as a Product Owner, Manager, and Director, envisioning exciting new features comes naturally. And with poketto.me, the possibilities seem endless:
🎧 Personalized podcasts
🗞️ AI-curated newsfeeds
📝 Automatic summaries
📬 Individualized daily digests
🖊️ Highlights, annotations, organization tools
🔍 Full-text search and even personal knowledge management (PKM)
But here’s the catch:
My capacity to actually build these things is limited. Stacking ideas into a never-ending backlog doesn’t help if I never act on them. Worse — would I even want poketto.me to become a cluttered collection of disconnected features? There’s real value in the simplicity of the core “save for later” use case.
Balancing idea exploration with focused execution is hard — especially when resources are tight. Here’s what’s been helping me decide where to focus:
➡️ *Tie ideas back to a clear vision.* Sure, PKM features could be cool. But do they really serve poketto.me’s long-term vision? Probably not. How about podcasts or curated newsfeeds? Those are much closer to “helping people read better.”
➡️ *Focus on learning.*
Drawing from Eric Ries’ Lean Startup approach:
Which feature would give me the most valuable insights for the least investment? What can I prototype quickly to get feedback and learn from real users?
➡️ *Reality check your ambitions.* Some ideas sound amazing but require way more resources than I can invest right now. I allow myself to jot them down — but I won’t waste energy obsessing over them. Not yet, at least.
For more thoughts on this: https://ralphmayr.com/posts/2022-12-08-on-frameworks/