Loading…
17
A client in Denver told me my project updates were too vague to be useful.
They said 'I need to know what you actually did, not just that you worked on it.' Now I list three specific tasks completed, like 'fixed the login error code' instead of 'made progress.' Anyone else get feedback that made them change how they communicate?
3 comments
Log in to join the discussion
Log In3 Comments
hayden_martin295mo ago
Got that same feedback early on. Started listing concrete things like "updated the API call timeout from 30 to 60 seconds" instead of saying "improved performance". Clients just want to see the receipt for the work. It feels a bit robotic at first but it stops all the follow up questions. Now I send bullet points with the actual code files changed or design layers adjusted.
3
phoenixb665mo ago
You actually list the specific files you changed?
3
kelly.keith5mo ago
Absolutely! I learned that the hard way too. Just listing the files I touched saves so much back and forth.
1