My changing role in an ultrasmall development team
Being PO, scrum master, prompt designer, tester, eval writer and UX designer in a team of 3 means rethinking roles and processes on a daily, almost hourly basis.
I am currently product owner, scrum master, prompt designer, tester, eval writer and UX designer in a team of 3. In such a setting, there’s no other way than to rethink roles and processes on a daily, almost hourly basis. Typically my role was further constrained by the given: ‘POs don’t code, designers design blablabla’.
Real life example: we don’t have a front-end designer and no time to do the whole wireframe stuff. Instead, I spec on data level, my developer codes something that is good enough, and I review. Which is a waste, because I do have design expertise, just not enough time to design it all upfront.
UX copy review: typically: table with screenshot with remarks. Request: do review in GitLab, but still with comments. Asked Claude Code: show me the UI preview and make that table. Claude: If you like, I can make those changes for you in the code, and put them in a separate branch. Asked my dev team what they thought of this. Result: joint decision that I have clearance to review and PR editorial changes & UX copy.
Downside: it’s easy for devs to just accept the changes, even though I still included the table. That way, the learning effect is lost, and we miss one pair of eyes that could have caught final issues.