Agile user experience challenges

Bringing user experience into an agile development process can be challenging, and at this point there is still no cookie cutter formula for implementing it successfully. It is very tempting to believe this formula exists, especially when attending a conference and some presenters speak about how they successfully incorporated UX into the agile process. The reality of integrating user experience in to an agile development process is challenging and it is not done overnight. In this post, there are a few thoughts to consider.

Diana DeMarco Brown’s article “Five Agile UX Myths” posted in Journal of Usability Studies (http://uxpajournal.org/five-agile-ux-myths/) highlights many important points. In my opinion, the most important point was how there are multiple ways to do agile UX and just because the “one sprint ahead” works for one organization, it may not work for others. I think the best thing to do is to gain inspiration from other organizations, and then try different approaches to find out which way works best for your unique situation. To make the transition successful it can be good to be prepared for different issues and problems that may arise. Here are my top 3 things to keep in mind:

  1. UX sprints works fundamentally different than development sprints
  2. Upfront work is important for both UX and developers
  3. User research can still be done even if you move at the speed of light

UX sprints work differently

Sophia Voychehovski, brings up an important point in her UX week 2013 presentation (https://www.youtube.com/watch?v=bbPTbN4Q_pw). Her point is that development teams normally split their work into sprints according to functionality (see picture to left), while UX sprints usually cut across functionalities as the fidelity of the design improves with each iteration (picture to the right).

Image showing how development sprints are split into features while UX sprints are split into fidelity level

The reason for this mismatch is that design is approached holistically to make sure the different elements fit with one another across different areas of the design. If the design process is forced to work in development sprints, inconsistencies and suboptimal interactions can occur between different parts of the system. This could cause inconsistency, if one feature might be optimized for the first function, and later on as the next functionality is built, some parts need to be reused (to maintain consistency). However, to support both functionalities the feature may need to be tweaked a bit. Now that tweak has to be in the backlog (on a “to-do” list) of changes for the first functionality. As the process goes on, the backlog will grow even more.

One way to overcome this issue is to allow designers enough time in the beginning of the project to get a holistic view of the system (can be low fidelity). Once they have the overview of the system they can be much more effective working in the developer sprints and most likely decrease the backlog.

Upfront work is important

Many agile projects don’t want any upfront work since that is the “waterfall method” (which is the devil himself). Once the project starts the team has some planning time to create an overview of the project and the product they are creating. The UX project also needs this planning time, the difference is that the UX project often needs a longer planning and exploratory phase than the development team. Unfortunately, most of the time everything has to happen according to the development team’s timeline, so the UX team is super rushed and may not have enough time to prepare and do proper user research.

With incremental improvements of an old system this issue may not be as severe. If only minor tweaks are required, the UX designers already have a holistic view and can therefore jump right in to the development sprints with ease. So, the primary factor for determining the magnitude of this issue is how drastically the system will change.

One client I worked with was both the main UX person in the project as well as the project manager. His general approach was to create a high level design and discuss it with his development counterpart, before a project kicks off. This ensured that they both got a clear estimate of the development possibilities and the effort required for the project. Once they were done with this general planning, they took it back to management for approval of the project. As they presented the project they were able to provide more accurate estimates. (It can be hard to work in this method if you have internal billing, because if the project is not approved no one will pay for the upfront work).

As the project kicks off, he did not disclose to the rest of the team he had already created an overview of the design. Instead, they only discussed use cases and potential issues. He purposely stayed away from discussing solutions, since he did not want the engineers to start focusing on technologies and lock themselves into narrow thinking. After they all seemed to agree about use cases, issues, and features to include, he revealed the design and asked what changes would need to be made to deliver what they discussed. After the team made tweaks, they all had a high level overview of the system. As they started to work in their sprint, everyone understood how the different parts would come together and be presented to the end users in a cohesive way. This method also helps facilitate discussion between developers and UX professionals and enables the developers to provide good interaction ideas and be a valuable asset in the UX process.

Another company handled the upfront work in a completely different way. They included the developers in the upfront UX work. This company worked in tight teams so during the research and design phase, the developers worked alongside the UX lead and became her assistant. This allowed the developers to help develop test scripts, design concepts, etc. and once it was completed they set off to start implementing the new solution. This way of working has many benefits. For example, the developers have a better understanding of the users, they need less clarification regarding the design, and they will have an easier time communicating if any changes are needed.

User research can still be done

Some UX designers who are working in sprints may feel as if they don’t have time for everything. They need to develop designs for the next sprint at the same time as they are answering questions and making sure the current sprint’s design is implemented correctly. Unfortunately, since they don’t have enough time, they sometimes have to sacrifice the inclusion of the user (interviews, usability tests, surveys, etc.).

The best way to solve this issue would be to split up the workload and have one UX designer and one UX researcher. The researcher can set up all research, conduct the research and debrief the designer (or the whole team) in the end. If in-person research is conducted, the key thing to keep in mind is that the researcher will need to plan and schedule participants before they know exactly what the state of the design artifact will be available.

Another solution is to rely heavily on online tools and conduct all research online. Some benefits of online research include rapid turnaround time for participant recruitment, and many of the tools provide good analysis capabilities. If online tools are the solution, make sure to still include a final test, which is conducted in-person. It is important to conduct the final in-person test because many of the panels consist of professional test takers, who tend to be more computer-savvy and overly positive toward system/product, which could skew your research.

Final words

Independent of how you are planning to implement agile UX in the workplace, expect the need to iterate on the process since it will not be perfect from the start. It is also important to try different methods and critically evaluate what worked and what did not work, and how you can improve the process of becoming more agile.

© David Juhlin and www.davidjuhlin.com, 2016

Inside-out vs. outside-in strategy

A company’s strategy can be driven either by internal or external factors. Even though it usually consists of a mix, the strategy usually tends to put more focus on one than the other. The model I use primarily focuses on the three lower levels in my Levels of UX Strategies framework: Company, UX division and project.

inside out_outside in_V2

Inside-out companies

These companies usually look at their internal resources and capabilities then try to find a way to leverage them to reach their business goals. The analysis they use can be Porter’s five forces, SWOT, etc. and from these form a strategy that leverages their strengths and downplays their weaknesses. As they go through analysis they might also identify areas of improvement in order to execute their desired strategy.

For example, a company might create a never-before-seen chemical composition. After discovering it, they have to come up with a utilization of this material in order to monetize it. University spinoffs are a good example of this type of company.

Outside-in companies

Outside-in companies on the other hand start by trying to identify what problems the customers have, then try to figure out how to solve it. After conducting marketing/user research, they might conclude that their customers want a certain product or service to fulfill their needs. Then they try to figure out how they can deliver that product or service to their customers. They might also be looking at competitors and world events that might provide ideas of how to better serve their customers.

For example, Amazon has realized free shipping and rapid delivery are important to customers, so they are continuously trying to improve the delivery time while keeping shipping costs low. Amazon did not have experience with alternative shipping methods such as drones, but they realized it would be a crucial step to deliver packages rapidly so they acquired this competency to satisfy their customers.

Basically, an outside-in company looks for ideas outside of the company, while inside-out companies look within the company.

Considerations at the company level

It might be easy to jump to the conclusion that it is better to be an outside-in company, but don’t be too quick to judge. In the events when customers don’t know what they want, the outside-in company might make the wrong conclusions. For example, would a hotel customer have verbalized they wanted a service such as Airbnb? Or would the cell phone customers have told Apple they wanted Appstore before it was built? These type of innovations usually have to come from ides within the company (or requires an organization with a very high design thinking maturity).

You can also run in to the problem with conflicting “wants” from customers. For example, if Southwest airlines finds out that passengers want to be served lobster on their flights, should they start to serve the lobster? It is true that the customers want it, but they also want a cheap flight. Since Southwest knows their cheap flights are of more value to customers than gourmet meals, the lobster is a “want” they should ignore.

As you can see, it is extremely important for outside-in companies to interpret the research accurately and to understand customers’ underlying desires and how they stack up against each other. This is a very hard task and giants such as Coca Cola made a tremendous fail when they introduced “New Coke”.

I can’t say that one or the other strategic choice is better than the other, but the important thing is that the mix blends well with other strategic decisions that the company makes.
The reason it is important to understand if the company is an inside-out or an outside-in is because it will influence the role of UX within the company. For the companies leaning towards an outside-in strategy, UX can take a more central role and bring new insights and ideas that can lead to initiation of new projects. On the other hand, companies that lean towards an inside-out strategy, the UX role is more as a supportive function that has a limited ability to drive change. Also, within the inside-out company, it might be hard to sell research or design that is based on insights gained from competitors since the culture are more focused on the internal parts of the company.

UX Division

When looking at the inside-out/outside-in scale for the UX division level, it is more about how the UX processes within the division are set up. An inside-out division has more of a focus on building their own methodologies for design and research, while the outside-in company have more of an inclination to search outside the company for inspiration of methodologies.

As an example, let’s say a UX division realizes they need to work in a more agile way. The inside-out division would look inside the company and might notice the developers are using scrum (an agile development method) and then decide to send some staff members to scrum training. This training might even be provided internally from someone in the development team.

On the other hand, the outside-in UX division might send a person to a conference in order to learn how other UX divisions successfully implemented agile methods. Afterwards, they decide if they should use scrum or some other agile method. Once they decide on the method, they can send staff off to third-party training.

In this example, the inside-out division would most likely implement something that works well when collaborating with developers and other divisions in the company, but might not be as efficient within the UX division. The outside-in division would instead find a method that works very well internally, but might not be as efficient when collaborating with other divisions in the company.

Further on, since the inside-out division has a tendency to build their own methodologies, they also tend to have well established processes and methods they rely on. The benefit is a more streamlined process that better predict time estimates. It will also be easier to communicate with other stakeholders that only know the very basics of UX. The outside-in UX divisions on the other hand, tend to allow designers and researchers more freedom in selecting methods and procedures. The benefit of more freedom is that designers and researchers can apply more appropriate methods if it is required.

The strategic choice between inside-out or outside-in will have an impact on the staffing of the UX division. The outside-in companies need more of the “A-type” individuals. Their employees need to be self-motivated, taking initiative, and have a broad skill set so they can apply the right methodologies for different situations. The inside-out company can have more junior employees as well as more of the B and C individuals that might not have enough self-motivation to expand their knowledge on their spare time. The reason the inside-out companies can get away with more junior employees is because they can lean on the processes to support them in their role. This result in the inside-out division being able to operate with a lower cost, not just from a salary perspective, but also since they train employees internally and might not have to send staff off to learn skills unfamiliar to the company.

An inside-out UX division is able to operate on a lower budget. It tries to maximize the value delivered through standardized procedures at the same time as keeping the cost down. Outside-in divisions can often deliver higher quality work for an additional cost. The decision regarding the mix of inside-out and outside-in strategy the UX division consist of depends on the company’s setup and what can provide the highest net benefit for the company. In other words, the UX division should strive for the mix that provide the greatest gap between the additional value created and the cost.

UX Projects

Let’s face it, most UX projects (should) involve users to some extent so it is easy to think of them as outside-in projects where knowledge is gained from participants outside the company. However, UX projects also have inside-out attributes to them. Consider this example. An online company is concerned why their shopping cart abandonment rate is high. Therefore they initiate a project that will investigate this. A UX researcher investigates it and finds out their shipping time is too long.

Another company might launch a project with the goal to see how they can improve the experience for their customers. After the UX researcher has done some investigation they find out that the customers think their delivery times are unacceptable. This example is more of an outside-in project than the first company’s project since this one starts at the user, while the first one starts from the business analytics.

So why does it matter where on the inside-out/outside-in scale the project falls? I would say that it has to do with funding. A project based on internal data (more inside-out) and a concrete problem to solve is more likely to be funded since it is easier to make a business case and gain stakeholder buy-in. I.e. it is clearer what the return of investment will be. When selling the more outside-in projects (more exploratory), the business sponsors (or someone else), whose budget it is coming from, are taking a larger risk than if they invest in a project with a narrow focus. If exploratory studies are important to the organization, one way to circumvent this tendency (to pick the safer projects) would be to provide the UX division with a budget to conduct their own exploratory projects.

Conclusion

The inside-out vs. outside-in framework is very simplified, yet all companies fall somewhere between these two extremes. Even though the framework is simple, it is worth considering where your company/UX division/projects fall and how this impacts your company.

© David Juhlin and www.davidjuhlin.com, 2016

Levels of UX strategies

UX strategies exist in many different levels and here I have tried to break it down to a framework that I find useful. Even if some of the levels overlap to some degree, there are the five main levels: Global, Industry, Company, UX Division, and Project.

Graphic representation of the 5 levels of US strategy. The 5 levels has layers similar to an onion. The furthest out is the Global level, followed by the Industry level, thereafter comes the Company level and the UX division level. Finally the furthest in is the project level.

UX strategy at the global level

On this level we need to consider how UX can impact the entire industry by interacting with other industries. For example, if the grocery store industry makes it easier for farmers to sell their crops to stores through some online system, will more farmers sell to the grocery stores instead of going to the farmers markets? This type of change would most likely increase the number of suppliers and thereby also increase the competition among suppliers, which in turn would benefit the grocery store industry. On the other hand, if all grocery stores provide this system, large farmers may start to use the tool to compare which grocery store would pay the highest price. This will result in unwanted competition in the industry that benefits the farm industry instead.

It is therefore important to understand how your company’s initiatives might change the entire industry if competitors implement the same system. If you don’t consider this level, you might unintentionally make the industry worse off in the long run. It is perfectly fine to make this type of decision that makes the industry worse off, as long as it is a part of the overall strategy and has been planned for.

UX strategy at the industry level

At this level it is important to analyze the competitor landscape and how your company stands in comparison to them. Are you providing a premium product or are you primarily going for lower costs? For example, if you manufacture Mercedes, you might need to spend more on the infotainment system than Dodge. Another important factor here is also to understand if UX is really a differentiating factor. For example, in the coal manufacturing industry, will a better experience on the website really be beneficial?

The reason you need to think about UX strategies on this level is that you don’t want to waste your company’s resources on UX when it actually isn’t that important. What if one of the coal companies would spend a lot of resources to improve their website, when sales primarily is generated through representatives? Would it not have been better to invest in providing training for their representatives or alternatively hire another representative?

UX strategies on the company level

After understanding external factors such as industry effects and your position in the competitive landscape, you are now able to start looking inside your company. At this level, you would be looking at the company’s structure. For example, should the company have an internal UX division or primarily outsource the UX activities?

This is important because you want to make sure the structure inside the company is set up to support the overarching goals. If the UX is critical for the company’s success, but the website design was outsourced. It will be hard to make smaller tweaks and continuous improvements.

UX strategies on the UX division level

The UX division level can be referred to as a functional level in other strategic frameworks. Since we are focusing on UX, I am only looking at that specific function in the company therefore labeled the UX division. At this level you need to analyze things such as processes. For example, should the researchers only be included in the end to test the design? If you have an outsource strategy, this might be enough since the company you outsource the design to should do the upfront research. Another area of consideration should be your staffing. Do you have the right people to fulfill the planned strategy?

The reason this is important is because you need to be able to execute the strategies that you set up. If the company’s direction is to be the UX leader in the industry and you only have designers or only have researchers on your team, this may present great challenges for your strategy.

UX strategy at the project level

In this model, the lowest level is the project level. Sometimes the projects are linked together into a larger project and sometime they are stand alone. This is how UX practitioner traditionally thinks about UX strategy. We try to understand the business goals and the users’ goals, and then create a UX road map. Many times the roadmap needs to be flexible, within limitations, since the project is rarely as linear as you might want. For example, you may do some initial information architecture research and you struggle to get it right (users can’t find information for a critical business goal). This might force the team to spend more time on the information architecture. In turn, this results in not being able to fit the four planned moderated usability tests due to time and/or budget. This could lead to either cuting it down to three moderated tests or conducting two unmoderated tests and two moderated.

It is important to understand UX at this level in order to maximize the UX for each project even though there are constraints (budget, time, resources, etc.). If the company can excel at this level they are off to a good start. They will be able to produce a better UX than expected of a company with similar UX spending.

© David Juhlin and www.davidjuhlin.com, 2016

Know the company’s position in the marketplace before devising a UX strategy

There is not one universal UX strategy that is completely effective for every company. In fact, all businesses must carefully consider how to implement a proper UX strategy around their business and industry. Therefore it is imperative the UX strategy starts on a high level and take the overall business strategy in to consideration.

As the UX strategy is being developed, some of the really important questions that need to be addressed include:
• How important is UX to our company?
• How can we strategically position our UX, given our role in the marketplace?
• Do we have the necessary resources to build out the selected UX capabilities?

Industry can be a major determinant of the level of user experience needed. Online retailers, for instance, would likely want to consider a higher level of spending in UX since their online presence is the main vehicle for interacting with their customers. A local electrician, on the other hand, typically don’t need great UX since they often secure most of their work through referrals from existing clients and sites like Angie’s List. For the handyman, it’s better to focus on the in-person customer experience than creating a hearty digital user experience.

Furthermore, different UX needs may exist for companies within an industry segment. For example, it may be more important for Uber to have good UX than for yellow cabs since Uber relies on in-app sales whereas yellow cabs simply pick people up off the street, with no online interaction.

This is not to say that developing a strong UX is not important for companies, rather that it’s a matter of allocating resources appropriately based on the company’s core competences and position in the marketplace. I believe that many companies underspend on UX as a whole, but even more importantly, they are spending money on UX resources inefficiently because they don’t understand how the UX strategy fits into the larger picture.

A major differentiator for McDonalds is its ability to find locations for new restaurants – a capability they have built up over time. Burger King, on the other hand, tends to follow McDonalds’ lead and expands to locations nearby new McDonalds spots. While there are drawbacks to Burger King piggybacking off of McDonalds’ strategic decisions, they can also enjoy the benefits of freeing up resources and spend elsewhere. Being a follower is not always a bad strategy, if the company can focus their efforts in another business area. In addition, it requires thoughtful consideration about how the UX strategy and team is developed in the company to leverage their position in the marketplace.

For some companies, this means they should abandon their attempts of pushing the boundaries of designs and accepting a follower role. Still we see many companies contracting design agencies to create something “new” and “better” than much larger competitors. For me, this is a puzzling proposition. A company with one-tenth the market cap as Amazon accepts the reality that they would be facing a large uphill battle in replicating Amazon’s delivery and distribution system, but for some reason, with UX, they still seem to believe they can become industry leaders.

Of course, for smaller company with big UX aspirations, there are tactics that can optimize UX spends and build up the necessary capabilities. For those looking to be leaders, such tactics may include properly assessing budgetary allowances for exploratory research and constantly iterating off prior designs through consistent user experience testing. Research is also important for those not seeking to become industry leaders in UX, only that these research efforts may want to start by looking at the UX of high-powered websites in order to understand which elements works best and which do not.

With a better understanding of their place in the market, companies can optimize a vision for their UX strategies. After determining whether to be a UX leader or follower, other things such as budgetary spending and team compositions can be considered.

© David Juhlin and www.davidjuhlin.com, 2016