Jamie Mill

@jamiemill.bsky.social

Product Design, Research, Strategy, IA and conceptual modelling. Lead PD at Polar Analytics, France jamiemill.com

Sometimes I think I really lose by being a nuanced person. I rarely make strong statements like “we need to prioritise X for the good of the company” or “designers should have those responsibilities”. I see how absurd those absolutes are in complex situations that depend on individuals, contexts.

Arguments I heard at work that don’t hold much water: “We have to build this because we already spent $XXX designing it.” (Sunk cost fallacy) “We have to build this in one big batch because in small batches we’ll move on to other things and there will be no incentive to finish it.”

Many designers are 10 steps behind engineers in the discipline of shaping and shipping software. Here are some things many designers are yet to internalise, that would multiply their impact: 1. Small batch size to reduce risk and speed feedback 2. Walking skeletons to flush out obstacles

Be careful marketing yourself as “self-taught”. Firstly, it’s never true: we all learn from outside sources — peers, books, conferences, videos, short courses. Secondly, it doesn’t sound like a selling point — it implies you’ve missed valuable external perspective.

UX and Product Design folks! I’m here for IA, conceptual modelling, product strategy, hybrid designers/builders, and improving design<>dev collaboration. So far I found the UX Sky starter pack from @spavel.bsky.social. Any other ways to find relevant people and conversations?