Skip to content
Fast Company Executive Board

The Fast Company Executive Board is a private, fee-based network of influential leaders, experts, executives, and entrepreneurs who share their insights with our audience.

Why designers should have a zero tolerance policy for unclear business requirements 

Here's how designers can navigate and resolve situations when asked to produce amidst confusion or uncertainty about the problem being solved. 

Designers should have a zero tolerance policy

[Adobe Stock / weedezign]

Profile photo of Jason Ferrell

Over my career as a design leader, I’ve learned that one of the most important ways designers can build influence and demonstrate impact is by being insatiably curious about the business you’re in. Demonstrating this curiosity is key to building credible, meaningful relationships with other functional partners.

But in many ways that’s only the beginning of designing with impact. With this article, I’ll focus on one of the most useful ways to capitalize on these relationships—navigating and resolving situations where designers are asked to produce amidst confusion or uncertainty about the problem being solved. 

EMBRACE AMBIGUITY WHILE STEERING FOR CLARITY

Early in my career, an executive mentor gave me simple, but sage advice: “Always know why you’re working on the project you’re working on.”

Nearly two decades later, that advice stands out as some of the most practical I’ve ever received and which I’ve paid forward on numerous occasions. I’m reminded of this memorable exchange often because I frequently encounter situations where dysfunction among cross-functional teams, or dissatisfaction with design output tracks back to a fundamental disagreement on, or lack of ability to answer, this very question. 

This is not to say designers should expect to work in a context of complete clarity. Rarely do environments like this exist. What’s more, many designers—like me—thrive in proverbial white space. Some of the most fulfilling work I’ve done stems from an origin of uncertainty—times where instinct or the triangulation of insights has merely pointed toward a mysterious problem space, but where clarity of the solution has been elusive.

The presence of ambiguity, however, doesn’t excuse unclear business objectives or requirements. When these are not expressed, clear, or fully understood, designers are set up for failure. Therefore, applying discerning judgment at this stage of the work is critical.

To some degree, the rise of sophisticated digital design tools has worked against our field in this regard. The ease of these tools, the depth and breadth of UI libraries, and pressures to produce quickly result in designers starting with high fidelity design output when, in the past, this level of fidelity would have been reserved for later stages in the process. Teams tend to think the risk of producing early, high-fidelity work is low. The risk, however, is misalignment on the problem being solved and how success will be measured.

This misalignment creates a wedge between design and business teams that isn’t clear until it’s too late. Too often, the misalignment doesn’t become visible until designs are produced, and, as a result, fault can disproportionately land at the feet of the design team. The reality is misalignment on business requirements isn’t the fault of any one team, but of the collective. 

DON’T DESIGN WITHOUT REQUIREMENTS. BUT ALSO DON’T DO NOTHING.  

Many templates are available online for documenting requirements and while they may be titled differently (product requirement documents, business requirements documents, briefs, etc.), four dimensions are ubiquitous in the most useful versions:

  1. Business Context: How does this work fit into the strategic context of the business
  2. Customer Insights: What value are we creating for users?
  3. Success Measures: How will we know if this work is successful?
  4. Constraints: Are there feasibility or viability guardrails this work needs to stay within?

Simply put, designers should avoid the pressure (or temptation) to design without thoroughly internalizing these requirements.

In times where these requirements have not been produced, designers can apply their facilitative skills to help the team create them. While rare, designers could find themselves in cross-functional teams that resist defining requirements—where the team insists the design work is necessary as an input to requirements. While that might be necessary in rare instances, documenting that as the purpose of the design work is equally critical. 

KNOW THE DIFFERENCE BETWEEN USEFUL AND NOT-YET-USEFUL REQUIREMENTS

Good cross-functional teams understand the need to document requirements. Great cross-functional teams know how to document them with a level of clarity that focuses everyone on a shared goal, and reduces the risk of misalignment and the disappointment and frustration that can follow in its wake. As such, defining clear requirements is a skill in and of itself. While that responsibility typically rests with the product or business owner driving the work, it’s equally important that designers, engineers, and other members of the cross-functional team develop the judgment of evaluating and providing feedback on requirements to ensure they’re useful. 

As a general rule, I’ve found two patterns of requirements that are less than useful: They’re either too vague or they prescribe a solution prematurely. 

PUSH BACK ON UNSUBSTANTIATED CONSTRAINTS

Upon ensuring useful requirements exist, cross-functional teams are able to have higher-order debates. The topic of which constraints should be accepted is one of the most consequential to the customer experience. As a result, I’d argue designers should be so bought into constraints that they feel ownership for the trade-off decisions that resulted in them.

For designers to get to this level of support, it requires curiosity and comfort building on their own understanding of the business or technical domains the constraints are rooted in (see my last article for further suggestions on this point). 

Operating with this mindset will position designers to be more successful pushing back on the subset of constraints that are unsubstantiated. In fast-moving environments, teams will understandably, and most of the time unknowingly, perpetuate outdated perspectives on business viability or technical feasibility. This practice unintentionally limits the set of solutions that are possible. Designers play a very important role in ensuring teams operate with intention and clarity on the constraints they accept.

The time teams spend ensuring requirements are clear, well documented, and debated is time well spent. Driving for this level of clarity won’t be perceived as a conflict when teams are operating from a place of trust and shared goals, and designers have demonstrated an equal accountability for the business problem they’re solving just as much as they have the customer problem.