Conversation

This framing captures the trouble that persistently plagues role definition in software product teams. My experiences align with Pavel's proposed "fix," but this articulates the situation much more clearly than I've managed.

Quote Tweet

Pavel A. Samsonov

@PavelASamsonov

· Sep 28, 2020

Whichever way you slice it, "clean" handoffs between stages of the software development process create friction and leave each role frustrated due to lack of influence into neighboring spaces. The solution is working in parallel, not expanding your "slice" until burnout. 1/

Show this thread

Diagram showing 6 rough stages of software development: business strategy, user research, UX, UI, front end, and back end engineering. There are four columns with stacked roles and red lines between the roles signifying friction. The first column has product manager, UX/UI designer, and full stack dev roles. The second one has PM, UX designer, UI engineer, and back end dev. The third one has many roles side by side rather than stacked, showing that they work together and there's no "true" handoff. The fourth column just has "unicorn"; it is crossed out.

read image description

ALT

5:57 PM · Sep 28, 2020Twitter Web App

Replying to

My experience too! Caveat: requires people who are willing and able to operate effectively in types of work they are not specialized in; a kind of cognitive fluidity that is not as common as it could be (but may be trainable :)