7 Things Business Leaders Can Learn from UX Designers

Sep 12, 2017 · 6 min read

UX and UI designers are responsible for elevating, shaping, or creating the product experience. Meanwhile, business leaders must take it a step further determining how the success of a product impacts financial projections for the year and customer loyalty for even longer.

What lessons can stakeholders learn from the designers responsible for shaping and realizing large UX projects?

1. Look to UX and UI Talent to Understand Platform Capabilities

Smart stakeholders take the same approach in preparing to guide their teams. By investing time upfront to learn about the platforms where your solution will be represented, you can offer feedback throughout the remainder of the process that will be contextually relevant.

Look to your UX team to educate you at project kick-off. Whether your UX team was brought in to assist with a project or assembled from talent throughout your organization, members will be well-versed applying patterns that make solutions feel native to users familiar with each platform. If designers don’t offer it immediately at the start of a project, ask your team for a quick tutorial on the .

2. Respect the Boundaries Set by Prioritization

Successful business leaders also align around priority before bringing on a design/development partner. Spending time on the frontend of a project to map business drivers creates a springboard for your design team to use in concepting the aesthetics and interactions that will compose your solution. Loosely defining functionality and prioritizing it can help your design team avoid a dramatic course correction mid-project, saving money and time.

When prioritizing your roadmap, consider how many departments or which legacy functionalities the solution should support at launch. How important is speed to market? Are you building an MVP first? The answers to these questions will help your UX and UI team adapt its process to match your goals.

3. Create a Source of Truth for UX and UI

By establishing and documenting the design language, UX and UI teams create a source of truth for the business, development team, and designers on the project. It can also be shared with the rest of the organization to bring other solutions composing a legacy ecosystem into alignment with the new offering. A style guide may include: standards of measurement, color, layout, and functionality. Some teams also choose to add application patterns, brand guidelines, or even language commonly used by the organization in marketing efforts.

Source of truth documentation has benefits beyond design teams. Business leaders can benefit from collaborative inventories, task lists, and status tracking. Investing the time to develop them at the project outset saves confusion and mismanaged effort later.

4. Make It Easy and Actionable to Track UX and UI Feedback

Consider including:

  • Proposed feedback
  • Intended revision
  • Impacted team members
  • Estimated time investment
  • Approval to move forward
  • Status

Sample statuses:

  • Finalized
  • Approved
  • Awaiting approval
  • Flagged for revision

5. Assess a Solution for Its Ability to Scale

6. Ground UX and UI Feedback in the Business Prerogative

Compared to standalone solutions designed to launch a startup product offering, enterprise UX projects often involve reckoning new design with that of legacy products. Rather than assessing the design solely on its application to one solution, consider too how the brand standards being established and design decisions might apply to other product offerings.

7. Build Time Into Projects for Revisions

Businesses who encourage teams to commit to a heavier focus on user testing and feedback within the early stages of the process will minimize large pivots further on. User testing that unearths major concerns after a majority of the development has been completed portends the potential to slow down progress or compromise the timeline because changes would involve major rework.

Find a Rhythm That Works

Comparatively, if user testing occurs near the end of the project, major issues are discovered and the team opts to remove the functionality in question to maintain the release date, the project team risks crippling the success of the solution. This is especially problematic if the functionality removed was foundational to user needs.

Learning from UX and UI Designers

Original post can be found here.

Innovate with us. Click here to access all of our free resources.
Authored by
Emily Genco.

Emily is a brand storyteller & passionate strategist who celebrates the art of language to drive content creation from conceptualization to delivery. She explores new ways to engage audiences through a digital-first approach to marketing. Emily joined the MentorMate team in 2015 dedicated to sharing meaningful content that informs, motivates and inspires.


Written by

Digital Ideas Accelerated // Global software development team, 500 strong // Learn more: http://bit.ly/2jjoQsp