Introduction: Our Mission
As user experience designers, we have one clear goal: to provide our users with an unforgettable experience. But how do we achieve this?
We follow a standard set of activities and procedures that help us understand who, why, and how users access an application. We then research, interpret, and apply this information to meet both user and business needs. The outcome is an experience that is comfortable to use and tailored to our audience.
Recognizing the Whole Team
Often, we focus too much on users and product owners. We forget that another critical group influences a project’s success: the developers.
Developers work behind the scenes. You might not hear from them until you hand over wireframes or a prototype. This typically happens mid-project. At that time, the prototype may include features requested by users or product owners, even if they are difficult to implement.
The Industry Norms
Experienced UX designers know the typical makeup of a development team. A standard team usually consists of:
- One UX architect
- One UI designer
- Two to four mid-to-senior developers
- A project manager
- A product owner
- A business analyst
Despite this structured setup, decisions are often made without consulting everyone. When asked about a UX decision, you might hear:
- “Because I am the professional. I know what I’m doing.”
- “This is what the users want.”
- “Jamie said he wanted it there, so I added it.”
The Problem of Scope Creep
A lack of technical understanding during the design phase can cause errors. For example, a product owner might suggest displaying products based on the user’s address.
A UX designer may pitch the idea, and the team might eagerly develop a mock-up. Later, a developer could point out that there is no simple method to determine the user’s location. They might also mention that this feature could add two weeks to the project timeline. Suddenly, the team must reevaluate the feature’s feasibility, timeline, and cost.
Bad Habits of Designers
Sometimes, UX designers push ideas without understanding technical constraints. We gather user feedback and then present ideas to the development team without consulting them first.
When developers assess the feasibility, they might object to features that are technically challenging or too expensive. This misalignment often leads to miscommunication and delays.
The Importance of Early Consultation
It is essential to explain why a feature may be difficult to implement. Communicate with your developers before finalizing wireframes. Ask questions about technical limitations early in the process. This approach helps prevent scope creep and sets realistic expectations.
Improving Collaboration
Effective communication with developers is key. Here are some steps to enhance collaboration:
- Involve Developers in Discovery: Invite them to join the discovery process or user interviews.
- Educate Yourself: Watch technical tutorials or take a development course to better understand constraints.
- Ask Key Questions: For example, inquire, “Can we get the location through the API?” to clarify technical feasibility.
These practices ensure that you better understand which features are possible and which are not. They save time by avoiding unnecessary meetings and frustrating backtracking.
Final Thoughts
Remember, understanding what your developers do is vital. You are part of a larger team working toward a common goal. Ask questions. Seek clarification. And balance your design vision with the technical insights from your development team.
As one expert put it:
“As a UX person, you must understand the stakeholder/users, most importantly your development team. They tell you to ‘reach for the stars,’ but they are the ones building your rocket ship.”
By learning from and collaborating with your developers, you can reduce misunderstandings, avoid scope creep, and create a better user experience.