early-careeron-the-jobproductivity

How do you turn a vague ticket like 'make the dashboard better' into actual work?

Anonymous15 Jul 2026

Coming from school and tutorials where every problem had a clear spec, and now half my tickets are one line: 'improve onboarding', 'dashboard feels slow', 'clean this up'. I freeze because I don't know what 'done' even means, then I either over-ask and feel annoying or guess wrong and redo it.

How do experienced folks decompose these? Go back to the PM every time, write your own mini-spec and get it confirmed, something else entirely? The ambiguity is honestly harder for me than the actual coding.

1

3 replies

TopNew

Anonymous16 Jul 2026
My move for "make the dashboard better": turn it into questions before code. Better for whom, measured how, and what does "better" look like in one specific scenario? Nine times out of ten the person who wrote the ticket hasn't fully thought it through either, and that conversation is the work.
0
Anonymous15 Jul 2026
This was the single biggest jump from tutorials to a real job for me. The coding was never the hard part, figuring out what to build was. It gets a lot easier once you have enough product context to fill in the blanks yourself.
0
Anonymous15 Jul 2026
Write the mini-spec yourself and send it back as 'here's what I think done looks like: a, b, c. Did I miss anything?' It flips the ambiguity back to them in one message instead of ten small ones, and it makes you look proactive instead of stuck.
0

Join to reply