the more i learn about project management / product thinking
the more i realize the job is less about “having answers”
and more about constantly trying to bring clarity when things feel messy.
most boards jump straight into technical tasks
with statlet, i’m trying to start from user goals first
then break that down into what actually needs to be built
feels much clearer than just listing dev work
@KaiXCreator building statlet - a privacy-first product analytics tool
currently working on defining the MVP and structuring the workflow before any code
trying to get the foundation right first
@mchulet building statlet - a privacy-first product analytics tool
currently working on defining the MVP and structuring the workflow before any code
trying to get the foundation right first
setting up a kanban board sounded simple
but i got stuck on basic things like:
what actually goes into backlog
how small a task should be
what “ready” really means
still figuring it out, but it’s starting to make sense
@csaba_kissi working on statlet (privacy-first analytics tool)
spent this week defining the MVP + setting up the kanban flow
trying to get clarity before building...
starting something new
managing a product from scratch as a PM
it’s called statlet - a privacy-first analytics tool
before writing code, i:
defined the problem
broke down the MVP
set up a kanban board
will share what works / what doesn't as i go
@TTrimoreau Hey! I’m a co-founder building https://t.co/fnjh79fcAh a SaaS for link management & analytics.
Wearing multiple hats across product, tech, marketing and early growth.
Always happy to connect and learn from fellow builders 🤝
Just finished a PMI course on prompt engineering for project managers.
Realization: good prompts are basically good requirements - context, constraints, and clear outcomes.
Same skill, new tool.