/  Deliver

  • On any project hundreds, thousands even, of new ideas, bugs, rethinks, unplanned situations, new uses and so on occur.

    Who decides what should be fixed (and why) – and how they should be fixed?

    • Your Senior Dev / Tech Lead almost inevitably has a huge say
    • Project managers too – even if, say, on a bonus to ship by a certain date(!)
    • Often, especially in Agile, entire Dev teams debate the issues
    • The UX person/lead is lucky to be part of the above...

    How well does this process usually work?...>>


    Things change

  • Judging by normal people's experience of tech: we don't do so well.

    Each planned User Experience is a chain of events, every piece of every screen thought through, as strong as its weakest link.

    However good our original design effort, though – as the project continues, the blizzard of changes breaks those user experiences.

    But how do other industries do it?...>>


    Aaaaaargh!

  • In the building trade, say, the Architect makes the calls.

    Sure, she consults the builders and others concerned.

    But it's the architect who has in her head all the different users of the building and all the different things we're trying to deliver for them.

    It's the architect who knows whether a proposed fix for one problem would impact some other important user experience.

    UX Designers are the Architects of the software & web industries.

    What would happen if a tech firm let their Designers make all the on-project calls?...>>


    Things change

  • There's one big tech firm where the designers make the on-project calls (UX Designers for software, Industrial Designers for hardware)

    - so products come out with all their myriad UX intentions intact

    - so normal people love these products like no others

    - so this firm can charge almost any price

    - so they're the biggest firm on the planet


    Designers make the calls