UX Maturity

I have been reflecting on the level of UX maturity within NICTA over the last couple of months. From inside it, it can be a bit hard and the unusual culture of NICTA makes it a bit hard to lock down, but the evidence is all around.

We now have 2 part time designers taking up the ever rising number of projects passing across my desk requiring help. Some are deep engagement and some are more small start-up style short bursts to help get a prototype out for validation.

At the ETD retreat last month, I proposed a separate design stream to run in parallel to the coding exercises… and we had a 13 engineers jump ship to join us!

Screen Shot 2014-05-12 at 3.05.16 pm
Meena displays from her ideation workshop at the ETD Retreat

Projects are engaging me at much earlier points so there is time for considerations of the workflows, organisation cultures within the industry, exposure to the raw data, platform explorations and efforts dedicated to problem definition rather than requesting help when a presentation layer is needed to help sell an idea.

At CeBIT several of projects that I was involved in were on display (see previous post) and such a highly public place with a high turn over of interested people is a great way to catch instant feedback.

We regularly host VIP visits from government, especially at the moment with the funding conversations happening. Each visit has a stop by the design space for a quick presentation of user experience work going into our work and how that makes impact into industry. Each guest, which over time has included both federal and state senior ministers and advisors has been deeply interested in the work we do in consideration with customers, audiences and clients. They ask a lot of great questions and really appreciate the information we have presented.

Image
Bill Simpson-Young and I present how user experience design assists technology making impact in industry to Angus Armour DDG Industry, Innovation, Hospitality & the Arts

In project meetings, I not only hear engineers and academics discuss “users” but also challenge each other on which “users” in particular. And I don’t even bother posting up persona’s anymore to help them!

And today, our CEO mentioned UX specifically in the all hands, with an example of how it has contributed to the Air Quality Prediction Service project, currently going out to market for validation and interest. When the CEO singles it out for special mention, it’s is clear that UX is understood as tool for strategic engagement.

Image
Hugh Durrant-White makes particular mention of my work and UX at NICTA

 

So where we sit on any maturity measure is difficult really say, but it’s most likely midway between superficial and reactive to fully integrated and strategic. Unlike most other companies, NICTA isn’t in the business of creating a suite of products and services which benefit from a unified approach. But we definitely work towards a level of quality and have the very real potential of creating change at an industry level through well considered user experience product design. And this is most definitely achieved by a shared mindset which is clearly emerging within the company.

I am really pleased about the efforts I have worked hard at for the two or so years. Building credibility by providing what teams think they need while gently adding in what I have identified as needs for users; education and skills workshops, regular presentations of successes and well placed, highly visual communication devices (posters and the like) have all produced a shift that I am really proud of.

Maturity refs:

http://uxmag.com/articles/how-mature-is-your-organization-when-it-comes-to-ux

http://www.uxmatters.com/mt/archives/2013/12/applied-ux-strategy-part-1-maturity-models.php

CeBIT 2014

CeBIT is always a great reality check and well worth getting along to for a day.

I remember the first time I went I was at the ABC, and having worked in online media for quite a while it really struck there was so much more out there for ux designers to work with. And thus my goal to get back to software was born.

I’ve attended as a NICTAreen 3 years running, and use the opportunity to gauge interest in the work we do, specifically anything I am working on in context with whomever is checking it out (competitors, potential customers or just interested scientists).

The NICTA stand was well placed this year, right near the entrance and we had some great demo’s and MVP’s on display. While there  I also found time to interview more Start Ups for my upcoming talk at UX Australia about my adventures with Start Ups.

This year I was also full time presenting one of my projects, the EPA Air Quality Prediction System which had a lot positive feedback and clear use cases for much further development including from the senior NSW Government ministers who stopped by to see our work.

A few of other more matured projects were part of the disply, some pics and my contributions in brief below.

Image
Structural Health Monitoring (RMS)
– Iterative UX and product design, IA, GUI, testing, style guide
Image
Air Quality Prediction Service (EPA)
– Initial UX, IA, running the trial release, project management
Image
ePASA Performance Assurance, Jon Gray the project lead is demonstrating the visualisaton of networks and their performances under load.
– Initial UX, GUI, IxD, Data Viz, style guide
Image
Start up alley – Space Tech!!

Comment to blog by Dan Turner

Boxes and Arrows wont’ let me post (I get stuck in a duplicate post error message loop) Here’s the article:http://boxesandarrows.com/we-dont-research-we-buildReally good to read and I would like to contribute to the conversation, so my response is below 🙂

I’ve written a few blogs on this topic also, so won’t reiterate those same ideas here:

http://hilarycinis.wordpress.com/2013/10/01/ux-advice-for-start-ups-especially-in-emerging-technology/

http://hilarycinis.wordpress.com/2013/10/10/171/

http://hilarycinis.wordpress.com/2013/10/30/ux-activities-in-australian-startups-tech23/

I have many strong feelings on this topic, and the startups themselves are only a part of the machine.

VC’s aren’t asking for ux evidence (in Australia, anyway) and so are making assumptions it’s included in the business and marketing plans.

The startups are often very confused about how to talk to customers and don’t understand they will have a range of needs from multiple user types. Blank and Ries are great reads but I also feel they have repackaged user experience work where it could sound like we are nagging about stuff the start ups feel they are already doing. I often go to great lengths to unpack the segments in the BCM where UX fits, and how these activities are extensive in order to get a clear picture.

I have quite strong feelings about marketing strategies having too large an influence in this conversation. Marketing comes later when the business knows it’s product or service and how it fits in with people’s lives. It’s totally arse-about.

I also suggest that business school educators start to look at user/customer experience seriously as part of the curriculum. I find it very difficult to get traction in conversations with business mentors about how early ux activities can assist in selecting a direction with more confidence, rather than setting up a business around a feature or a product and hoping for the best. The jargon used obscures the pain that startups can experience – pivoting and the culture of failure are nice terms for very difficult periods of time.

I see many similarities between StartUps VC activities and the entertainment industry funding machine.

We know that ux isn’t a magic wand to ensure success but when added to domain expertise and customer/user feedback it can add structure and assist with decision making when there are too many unknowns.

Maybe incubators need a ux on staff full time to assist across the teams. I work with Incubate doing this in Sydney, although not full time but I do run a workshop and follow up each round they do and I have found it really educational and I get some good feedback. I guess the proof is in the success of each business.

NICTA year 2 in review

I have experienced several moments of career death and rebirth. Those feelings that get mistaken for dead ends, where the frustration feels overwhelming or something happens that deeply disappoints and you start looking for a new job.

At the close of my second year at NICTA I have felt these moments a few times.

The first was a frustration of “not being listened” to. On complaining to my husband (my only true confidente)  he reminded me that perhaps this was only a perception (which was true, I was focussing on the ones who didn’t, not the many who did)  but that also I have a habit of throwing too much at people and expecting them to just grasp it. I needed to be realistic and patient and do things in smaller slower pieces. He, as usual, was wise and right.

Second was a severe feeling of redundancy because my projects seemed to drag on for ages, while other project of just a single developer and no designer got built and out into the light in what felt like less time. I wondered if I was adding bloat or secretly disliked for complicating things? Again I complained to my husband and he was gentle but also asked me if maybe I was being egocentric. He most likely offered a lot of suggestions but that was the one I heard. Fortunately I had the presence of mind to examine this realistically and recognised this was indeed true. I was remembered that its not unusual for projects to take years and then lucky if they get built anything like they have been designed. I had come from 10years in media where everything I did got built, fast and to an enormous audience. I had also worked on some very high profile products that launched with a lot of publicity and now that was no longer normal I was struggling with feeling valid.

Third, NICTA had a funding scare after the change of federal government. I panicked and started looking for new roles. I discovered the idea of leaving NICTA was immensely depressing. So I withdrew from the two applications I had started on and found a space of faith and would stay with NICTA and trust that faith, and regardless of the outcome I would be ok.  This was extremely freeing and very clearing. And, it turns out to be ok as the funding is secure and NICTA is moving in very exciting directions as a result.

Fourth, was my delve into, and subsequent distancing from the start up community. I truly believe UX is really important for startups but found no-one wanted to know. Eric Ries was preaching pieces of ux practises in his BCM methodology so “entrepreneurs” figured they either didn’t need it or know it all. UX as a frame of mind for these folks seems the most appropriate to their needs and good luck to them. Besides its mainly all luck anyway and while some quality UX would benefit them, its not a magical formula and they are really gambling again very high odds.

Late last year I was in an offsite were the researchers as well as developers were not only talking about the users but were challenging each other about what kinds of users, and presented information drawn from their interactions with them! I barely had to speak all day. For a moment I felt robbed of my job… but then what better evidence of two years of explaining, reframing, coaching, guiding, presenting and creating can you asked for?

Regularly overhear researchers discussing interaction design or user needs. It comes up without prompting in meetings and talking to our customers is now understood as neccessary.

UX as a frame of mind is emerging holistically within the NICTA culture and this a wonderfully new kind of validation I hadn’t expected.

I have also successfully lobbied for a second designer and we have a great collaboration space now. Our department director is extremely progressive and supportive. Working with researchers who genuinely love to learn and share what they know and are so unaffected by how smart they are has been a rare gift.

My husband has been and continues to be a great listener, has insight into me I don’t have and is an amazing grounding force. Once my ego and fear was removed (and maintained to continually) I am now having a great time and look forward to the next 12 months.

Hackdays.

I’ve been a “participant” at hackathons since my Yahoo! days. Back then I would help out with the very occasional interaction design solution or a bit a fancying up an otherwise average looking dev built UI.

Sadly, this hasn’t really changed despite best efforts, so I’m really thinking UX has no place in hackathons… actually neither does a UI specialist.

Hackathons, or hack days, as far as I can see are one or both of these:

  1. Get a quick and dirty build going to test a product idea
  2. Get a quick and dirty build going to experiment with data

Now, it’s realistic not to expect customer interviews or testing. But you’d think some kind of UX would fit into each of these but in reality no-one wants to include any kind of UX activities despite the obvious ones of proposition, task fulfilment or just basic heuristics in the UI.

Actually, the only thing I get asked for to help out with hack days is a quick and dirty logo design.

It’s not that UX isn’t done, its just that a specialist isn’t needed.

User Experience at hack days is automatically within the team. They are the user group, because they are generally solving a problem they are familiar with as subject matter experts. When it comes to validation, its a great way to knock up that solution as an early prototype to get folks playing with it. Just like with startups, a UX practitioner isn’t considered necessary because everyone is holding UX as a frame of mind. As they should 🙂

In the case of the data experiment, any conversations of the “who is going to use this” type are just going to get in the way. It’s entirely inappropriate to set customer/audience needs down during these kinds of hacks. If a user type or scenario is presented it seems to be reverse engineered for the end-of-day-pitch.

I know at times it doesn’t feel like it but we’ve all such done a brilliant job of evangelising UX, that hack day participants automatically consider, at the very least, the basic ideas of another person using their thing.

So from what I’ve experienced and observed, the best we can do to help out is:

  • At a hack day any UX work needs to be done prior in preparation and presented as an optional inclusion because the main obstacle for UXers at hack days is of course is lack of time.
  • Designers can also supply recommendations for development libraries or frameworks that have solutions in place for interactions and front end assets.
  • Take time to examine the data and the hack days goals. If there is a competition, consider the criteria for qualifying. In some cases the audience isn’t someone unknown group of customers but the judges.

UX in context for Startups

I just replied to a great post 500 startups checklist for investing in a startup by David Cummings. Its helped me think more about the difference between user experience work in established companies, compared the time poor, urgency driven, passion rich startup.

In Australia, where UX considerations in startups is pretty low, I’m working on documenting and providing coaching for startups around this, please feel free to reply with your comments or thoughts.

UX in context for startups, addresses the concept validation as well as the usability. These user experience activities are usually held by the founder when discussing the project with customers (as part of validation, not marketing) as well as the rest of the cross-functional team as a frame of mind, rather than a set of build activities. These are ‘softer’ and definitely lean, rather than the rigourous customer/audience insight led work done by a much larger team.

User Experience considerations are present in almost every stage of a startup’s activities, owned by each of the team members in whatever way they can do it. Founders are considering the market constantly and designers know someone has to use the thing they are creating a face for. Developers are deeply occupied by technology concerns which leaves little time for ‘thoughtfulness’ about an end user, but they do understand extremely well that without the technology and/or platform there is nothing for anyone to use.

In context for startups, I am seeing UI and UX being bolted together too often not because it’s a richer skill set, but because they are misunderstood activities.

  1. Good usability and a pretty presentation won’t create a good user experience; it won’t magically transform a bad product or service into a good one.
  2. Weeks of ‘proper’ ux research and collected data synthesis doesn’t cut it for a startup. There is no money and no time.
  3. Lean UX is highly appropriate; engaging a uxer for the long haul can be difficult as the work ebbs and flows

So here’s where every UXer I know is about to yell at the screen. In context for startups, User Experience is a frame of mind; it’s a shared function in a cross-functional team. And the basics can be learned and employed very easily by anyone in the team.

User experience practices help identify conceptual issues, which is especial important with emerging technology and innovation as there are mental models under challenge with customers/audiences. There are simple approaches when talking to customers/audiences that will capture the needs (rather than wants) and not freak you out.

Startups are a punt, they can start out as one thing then suddenly become something else entirely. The user experience work needs to be lean, flexible, disposable and a group effort.

Now having said all the above, if you are lucky enough to find a uxer who can ALSO do UI design, nab them as they (well, we…) tend to solve both issues on the fly at the same time, not because we combine them, but because we understand the differences deeply.

Pop over and read UX advice for start-ups, especially in emerging technology for more about UX considerations and separation of UX and UI work.

WiseHunch have a great poster describing how to talk to customers

Luxr.co do a good job of coaching if you have the time and cash

UX advice for start-ups, especially in emerging technology

A key and very obvious part to developing a platform, product or service is understanding who might use it.

This is an extremely open ended consideration, and user experience in conjuction with user interface work with your start-up will go along way to providing some guidance on it.

UX for emerging technology startups most often starts with:

  • Proposition definition
  • A hypothesis created from domain expertise
  • Hunches
  • Desk research
  • Best practises and UX heuristics
  • Talking to potential customers

It is then refined over time, with input from the team and potential customers/audiences.

It is important that investors are not a voice in this conversation to avoid biases but usually this work should be done prior to going for funding as it would form part of the business plan.

UX further assists as:

  • It indicates you are listening to your customer or audience (through interviews and research)
  • It provides focus for development goals (by defining value propositions, use cases, work flows, customer task analysis)
  • It reduces costs by providing guidance and framework for the minimum thing you can launch with AND expect income from
  • It assists in understanding why and when a pivot occurs
  • It provides well defined measurement benchmarks after launch for feedback and testing
  • It will eventually inform your marketing plan as the customers/audiences are already identified
  • It will reduce your marketing budget as the offering should be good enough to speak for itself
  • Moves from a marketing mind frame to a service mind frame – rather than trying to convince a customer, there is consideration for their needs. This helps them to LIKE you, are more likely to be forgiving of glitches and more loyal to you long term.

At some point during the UX work, it will become apparent that a front end needs to be designed e.g. lo fi mocks and prototypes, plus descriptive content and some kind of branding. The benefits  of UX led UI development are:

  • It is an easily understood sum total of abstract concepts
  • Creates a customer conversation that has direction without being leading – reduces bias
  • Gets your investors/customers/audiences excited because it’s a physical step toward reality
  • Provides the means to measure and validate your offering
  • Directs the removal of ALL friction points like guest checkout, consistent descriptions, information heirachy, access to help, identifies what is automated and what could use a mechanical turk, demonstrates mobile first
  • Describes why + how + doing

Business analysts working with developers are capable of providing some of these activities, however a user experience specialist and a frontend/GUI designer will provide clear user advocacy which will then dovetail into business and development activities.

© 2013 Hilary Cinis

I know nuuuuthink!

Since last week I’ve realised (quite welcomingly) that I know nothing. This is true in my personal life as well as my professional life – this blog is considering the latter only.

In a previous post I whinged about designer elitism and I have to say I was guilty of it myself.

I am about to mentor a design student from sydney university and I’m terrified. Here I am, 20 years in the biz and I feel like the truth is this: No one knows anything, really. We are all just exploring and validating retrospectively as we go to prove we are an expert in something.

Today I saw this: http://dvice.com/archives/2012/10/ethiopian-kids.php And it blew my mind.

These tablets and the apps in them weren’t researched, designed and tested for illiterate, non-digital children.

Yet they got it, adapted and excelled. I’m having a really big moment that’s challenging me professionally and I am liking it.

By the way, I think that Ethopian experiment is a game changer, it is heartening and very moving. It gives me hope for the human race as it’s surfacing the basic qualities of humanity. Curiosity, exploration and tool creation for more exploration.