Home > Articles > Programming

Interfaith Marriage: Experience Design Meets Agile Development, Part 2

To date, most advice for a marriage of methods between experience design and agile development has focused on how experience designers can accommodate agile developers. In Part 2 of his two-part series, author Larry Constantine delves in to the ingredients needed for improving the marriage between the two essential parts.

See Part 1 of this article.

Like this article? We recommend

In Part 1, I looked at some of the conflicts and incompatibilities between experience design and agile development. To date, most formulae for a marriage of methods between these two have focused on how experience design can accommodate to agile development. In Part 2, I look at some things developers and development teams ought to consider in order to make the relationship work better.

Process Improvement

What would be required for a better marriage between experience design and agile development? I think the main ingredients are straightforward:

  • Respect
  • Equality
  • Knowledge
  • Independence

These may seem like simplistic slogans borrowed from social work, but for each area, there are very specific things that can be done to make agile development better able to deliver highly usable systems through collaboration with experience design.


We are all professionals, yet developers too often look down on experience designers as muddle-headed, touchy-feely types drawing on soft-science impressions and unsupported opinion. To be honest, I have also known some designers who see developers as narrowly focused, socially inept techno-nerds stuck inside their code. In truth, programmers and designers alike need to learn to be better at acknowledging and deferring to each other’s expertise.

Programmers need to accept the expertise of user experience and interaction designers independent of whether it is based on informed judgment, professional experience, or new evidence. A programmer would never sit still for an experience designer telling them which programming language to use or which methods belong with which object classes. On the other hand, I have watched countless times as programmers argued with designers over the placement or operation of user interface widgets or over what would be the best way to offer a feature to users. Designers do not insist that programmers defend their algorithms or database architecture or demonstrate superiority with comparative testing of alternative code, yet interaction designers are often told to “prove it” with user testing results. I have even seen cases when user testing confirmed the judgment of the design team, but the developers, convinced that they knew better than both end users and experience designers, programmed the user interface the way they wanted to anyway.


Designers and developers need to be co-equals in the development process. I confess that I have personally come to believe that, for greatest success in most instances, experience design should drive the process and that, for the most part, user experience issues should trump implementation issues. If it comes down to the position and opinion of the developers on the one side and the designers on the other, most of the time, the outcome is better if the nod goes to the best design. However, in practice, a more workable compromise is to consider developers and their concerns and designers and theirs as equally important.

In cases of irreconcilable differences, rather than filing for divorce between the design team and the development team, the decision should go to binding arbitration. In most organizations, the product owner is probably the most appropriate arbiter, because the product owner is most likely to have the broad perspective on the varied and competing short- and long-term objectives for the product. In general, it is the product owner who bears the most direct responsibility for balancing conflicting forces to achieve product success.

Obviously, only major issues should be escalated to this level; we don’t want to involve management in every little disagreement. Mutual respect and equality means that sometimes ease of programming will trump ease of use or that features and characteristics that are recognized as absolutely essential for usability will be reluctantly deferred for later release. The operant word here is sometimes.


One of the most effective ways to build mutual respect and equality is through knowledge. We need to learn much more about each other’s skills and areas of expertise. In the Carnegie Mellon/University of Madeira dual-degree program in human-computer interaction in which I teach, all students, including artists and psychologists, are expected to acquire a basic knowledge and demonstrate elementary ability in software engineering and user interface programming. We do not expect everyone to become a software engineer or professional programmer; we do believe that to design user interfaces well requires knowledge of what goes on both in front of the screen and behind it.

Conversely, every programmer on the agile development team should have some training and background in usability and user interface design—at least enough so that he understands basic usability and design principles and has thoroughly accepted that his own personal preferences are not usually representative. (“We are not our users, and we are not like them.”) It’s not that hard. Training developers in interaction design is one of the ways Lucy Lockwood and I got into trouble with the human-computer interaction establishment, but thousands of developers around the world have learned the rudiments of designing software for use. Most of them will never become full-fledged interaction designers, but they will be better partners in the design and development process.

Another argument for spreading the skills is that even the most thorough presentation and interaction design will not and cannot cover everything down to the lowest detail, and will always fail to anticipate some interaction or presentation issues. In practice, programmers inevitably end up making many user interface design decisions on the fly—everything from whether or not to align certain visual components to creating unanticipated error messages to deciding whether column headers on a grid display should be active to sort on that column. Not only does knowing the fundamentals of interaction design contribute to better teamwork and more successful collaboration with designers, but it is also in keeping with the ethic of cross-training and fungible skills that permeates agile methods.


Any good marriage allows for independent thought and activity, which can be a problem for meshing the work of user experience designers and software developers. The impulse to launch immediately into productive work on day one is understandable and all but universal for both designers and developers. Designers start sketching screen layouts or product designs in first meetings, and programmers start writing little bits of code as soon as they can get their hands to the keyboard. And management makes the matter worse by pushing for visible deliverables from day one.

I recall one agile design project I worked on under a seemingly impossible deadline. On the third day of the project, a senior manager dropped into the design team’s situation room to see how we were doing and immediately asked to see some screen designs. While his anxiety escalated, we explained that we wanted to figure out what it was we were designing and what it should do before we began drawing pictures of the final product. What a radical idea! We chose to build a rich, detailed task model using essential use cases and to figure out from that what screens were needed and how they were interconnected before we even started sketching low-fidelity prototypes. It frustrated the manager, but enabled us to awe him later when we delivered a breakthrough prototype.

Alas, doing much in the way of upfront field study, modeling, and design conflicts with agile principles. One way to resolve—or at least reduce—this conflict is to decouple design and development. Many teams have devised variations on a one-sprint-ahead model, in which the user experience effort is chopped up into short segments running concurrently with development, with the user experience team staying one cycle ahead and delivering just-in-time input to user stories. Another proven approach that is more in keeping with the needs of experience design is to use an initial triage aimed at what engineers refer to as a separation of concerns.

Good experience design requires at least some initial field research in order to build a rich understanding and reliable insight into users and user needs. In most contexts, field work makes the most sense when it is done upfront and, although there are ways to streamline and accelerate field work, such as by model-driven inquiry, the activity can only be compressed or cut so far without markedly increasing the risk of building the wrong system for the wrong audience.

Instead of prolonging a so-called sprint zero or resorting to the silliness of sprints minus one to N, upfront user experience activities can be allowed to proceed at their own pace without delaying development if, early in the project, designers and developers engage in an explicit triage process. Based on what is known and understood at the time, the triage separates the anticipated features and functions, content, and capabilities of the product into three buckets:

  • Interface
  • Internal
  • Interdependent

The interface bucket includes those things that have a direct and substantial impact on user experience or for which a significant amount of design thinking may be required to get it right. Examples include most aspects of the so-called presentation layer, such as screen layout, information display, or menu structure, as well as workflow, navigation architecture, and the like.

The internals bucket includes those things that are largely independent of interaction design or with little or limited impact on user experience. More or less pure examples might include most things falling under the rubric of “model” in a model-view-controller architecture or such things as computation algorithms, database organization and implementation, and communications protocols.

The third catchall category, the interdependent bucket, includes anything that entails a substantial mix of interface and internal design issues or that is ambiguous or indeterminate given the state of knowledge at that point in the project.

The purpose of this triage is to enable the development team to begin iterative, incremental development of things from the internals bucket while the user experience team completes field work and devises an overall user interface architecture and high-level design and begins work on various things in the interface category. Of course, it is rarely possible to make a truly clean separation of interface, internal, and interdependent issues, but in my experience performing this triage allows a considerable amount of concurrent engineering of software along with design of user interaction while reducing risk and restricting later changes to a manageable minimum, even with an imperfect partitioning.


In sum, what I am proposing is a fairly simple formula for better relations with experience designers: Learn more about experience design, respect your design colleagues and their expertise, treat them as equal partners in the process, and facilitate independent but coordinated activity that allows for a deeper and broader initial design effort. I don’t believe these suggestions require radical reworking of most agile development, but they do demand that developers make more accommodations and meet their partners in the process half-way.

Now, may your union be a long and prosperous one!

Larry Constantine is an award-winning interaction designer, a pioneer in software engineering, and a novelist. Under his pen name, Lior Samson, his first novel, Bashert, has already been published and a second, The Dome, is slated for October release. Both are fast-paced political thrillers with technology twists—stories “to feed the inner nerd,” as one reviewer phrased it. They are available from Amazon and http://www.liorsamson.com. Constantine’s day job is as Institute Fellow at the Madeira Interactive Technologies Institute and as professor at the University of Madeira.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020