20 years in UX, 6 months as product owner.
One product, one team, right?
That’s the theory.
UX and dev are not always marching to the beat of the same drum whether down to the team set up, culture or methodology. I have not yet come across the perfect solution to marrying sprints with UX, no matter how lean the UX or outcome focused the dev approach.
I know the pain of coming up with a ‘great’ UX solution: end-to-end, easy to use, covers all the pain points, nails all the details, harmoniously blends with existing flows…
And then the shock of seeing only pieces of it implemented. The famous first phase. The frustration of dev “tickets” missing the whole picture.
Mr Potato Head without the potato body and no mouth.
So now I’m in the other camp. No longer just the UX user-advocate role, but the one who has to say which is the most valuable “piece” because the whole thing would take just way too long and so by the time it was done, nobody would care.
Time, money and value. Maximum value, minimum everything else. Using the leanest approaches I can to try and cover the most ground.
Fundamentally, the question has changed. Before, if it was what would make the best outcome in the most frictionless way possible, now it’s, perhaps, what will make the most impact in the shortest time possible.
It has the feeling of downsizing, like in the movies. Moving from a mansion to a caravan. More austere, some tough decisions, generally not as romantic as it sounds. There’s potential for it to be somewhat liberating, and it is certainly a good exercise in focus. Cut out all the noise and see what is left, and hope it’s still understood and fun as Mr Potato head, and not just as sad and scary like a few body parts.