Managing Conflicting Stakeholder Priorities

Imagine students is designing a new school backpack, a sports bottle, or even a public bench. Different people will care about different things. Students may want style and comfort, teachers may want durability, parents may want low cost, and a council or company may want safety and easy maintenance. In Design, Materials and Manufacturing 2, this is a major idea in the topic Requirements and Stakeholders: real design decisions are rarely simple because stakeholder priorities often conflict. 🎒⚙️

In this lesson, students will learn how to identify those conflicts, explain the key terms, and make practical decisions using evidence. By the end, students should be able to:

explain what stakeholder priorities are and why they can clash,
apply a simple process for handling conflicts,
connect stakeholder priorities to user needs, societal needs, and engineering requirements,
and use examples to show how designers balance different demands.

What Are Stakeholders and Why Do They Conflict?

A stakeholder is any person or group who is affected by a product, system, or design decision. In product design, stakeholders often include users, buyers, manufacturers, retailers, regulators, communities, and sometimes people who maintain or dispose of the product.

A priority is something a stakeholder cares about most. For example, one stakeholder may prioritise low cost, while another prioritises long life or high performance. Conflicts happen because one design choice can improve one requirement while making another worse.

A simple example is a reusable water bottle. A customer may want it to be cheap, light, attractive, and easy to clean. A manufacturer may want it to be quick to produce and made from one material. A sustainability group may want it to be recyclable and long lasting. A school may want it to be safe, non-toxic, and hard to damage. These priorities can pull in different directions.

In engineering terms, a design rarely has one perfect answer. Instead, students has to compare requirements, judge evidence, and make trade-offs. A trade-off is a decision where improving one feature may reduce another. Trade-offs are normal in design because materials, time, money, safety, comfort, appearance, and environmental impact all compete for attention.

Capturing Needs Before Solving Conflicts

Before conflicts can be managed, the designer must first capture needs clearly. In the requirements process, there are several levels:

User needs: what the person using the product wants or needs in daily life.
Societal requirements: what wider society expects, such as safety, accessibility, sustainability, and legal compliance.
Engineering requirements: measurable statements that turn needs into design targets.

This step matters because unclear needs cause bad decisions. If a team says, “Make it strong and affordable,” that is too vague to guide real design work. But if the requirement is, “The product must withstand a drop from $1.0\,\text{m}$ onto a hard floor without cracking,” then the team can test it.

Consider a classroom chair. Users want comfort. The school wants low cost and easy stacking. Maintenance staff want easy cleaning and repair. Safety rules may require stability and fire resistance. If students only listens to one group, the final design may fail. Capturing the needs of all stakeholders helps reveal where conflicts exist early, before expensive mistakes happen.

A useful method is to collect evidence from:

interviews,
questionnaires,
observations,
product testing,
and existing standards or regulations.

This evidence helps designers move from opinions to facts. For example, instead of guessing that “students like bright colours,” a survey may show which colours are preferred by most users. Instead of assuming that “thicker plastic is always better,” testing may show the minimum thickness needed for strength.

How Conflicting Priorities Are Identified

Once needs are captured, the next step is to identify conflict. students can do this by comparing stakeholder statements side by side.

A conflict often appears when two priorities cannot both be maximised at the same time. For example:

making a product lighter may reduce strength,
using recycled material may affect appearance or cost,
adding more features may increase price,
improving comfort may make manufacturing more complex.

Let’s use a mobile phone case as an example. Users want thinness and style. Parents may want high protection. Retailers may want low cost and good margins. Environmental stakeholders may want recyclable material. A thin case may look stylish, but a thicker case may absorb impact better. This is a direct conflict between aesthetics and protection.

A good designer asks, “Which requirements are essential, and which are preferences?” Safety and legal standards are usually non-negotiable. Style, colour, and minor convenience features may be more flexible. This is why hierarchy matters. Some requirements must be met first, while others are balanced within the remaining design space.

One practical tool is a priority matrix or decision matrix. This helps compare options against criteria such as cost, durability, comfort, sustainability, and manufacturability. Each criterion can be given a weight based on importance. The product with the best overall score may not be perfect for every stakeholder, but it may be the best compromise.

For example, suppose a project team evaluates three materials for a product shell. If one material scores highly for toughness but poorly for cost, and another is cheap but weak, a matrix helps students see the pattern rather than relying on instinct alone. This makes the decision more transparent and easier to justify.

Translating Conflicts Into Engineering Requirements

The real skill in managing conflict is turning different needs into clear engineering requirements. This means converting words like “safe,” “comfortable,” or “modern” into measurable or testable statements.

For example:

“safe” may become “the product must have no sharp edges and must pass impact testing,”
“lightweight” may become “mass must be less than $500\,\text{g}$,”
“durable” may become “must survive $10\,000$ opening cycles,”
“easy to clean” may become “surfaces must have no gaps wider than $2\,\text{mm}$ where dirt can collect.”

These requirements help resolve conflict because they create a shared target. Instead of arguing about whether a product is “too bulky,” the team can compare the actual measurements against the target values.

Good engineering requirements are usually:

clear,
specific,
measurable,
realistic,
and testable.

This is important in Requirements and Stakeholders because vague statements cannot be checked. A testable requirement can be verified by inspection, measurement, or user testing.

Real-world example: designing a public bench. Local residents may want comfort, visitors may want attractive styling, the council may want vandal resistance, and accessibility users may need armrests and appropriate seat height. A possible engineering requirement could be: the seat height shall be between $430\,\text{mm}$ and $480\,\text{mm}$, the structure shall support a static load of $2.5\,\text{kN}$, and the surface finish shall resist weathering for outdoor use. These requirements do not solve every disagreement, but they give the design team a fair basis for decisions.

Methods for Balancing Stakeholder Priorities

There is no single perfect method for every project, but several approaches help students manage conflicts well.

1. Use evidence, not guesses

Evidence can come from surveys, product tests, and market research. If one stakeholder group is louder than others, evidence helps stop the design from being biased.

2. Separate must-haves from nice-to-haves

Must-haves are essential requirements such as safety, legal compliance, and core function. Nice-to-haves are features like premium finishes, special colours, or extra accessories.

3. Use compromise thoughtfully

A compromise means accepting a middle ground. For example, a chair might not be the cheapest possible, but it may be strong enough, comfortable enough, and affordable enough for the client. Compromise is normal in engineering, but it should still meet the core requirements.

4. Test prototypes

A prototype is a working model used to check ideas. Testing a prototype shows whether the chosen balance really works. If users say a handle feels comfortable, but tests show it causes pressure points after $10$ minutes, the team can redesign it.

5. Record decisions clearly

When a design team chooses one option over another, it should explain why. A written rationale makes the process transparent and useful for future changes.

For example, if a company chooses a recycled polymer instead of a glossy virgin plastic, the reasons might be: lower environmental impact, acceptable strength, and better alignment with sustainability targets. Even if the finish is slightly less shiny, the evidence may justify the decision.

Why This Matters in Requirements and Stakeholders

Managing conflicting stakeholder priorities sits at the centre of the topic Requirements and Stakeholders because design begins with people, not just materials or machines. User needs tell students what the product should do. Societal requirements show what the wider world expects. Engineering requirements turn those expectations into something testable and buildable.

Without careful management of conflict, a design may become too expensive, unsafe, impractical, or unpopular. With careful management, students can create a product that is balanced, realistic, and fit for purpose.

This skill also links directly to materials and manufacturing. Material choices affect weight, cost, sustainability, appearance, strength, and production methods. Manufacturing choices affect accuracy, speed, waste, and consistency. So when priorities conflict, the designer must think across the whole system, not just the final shape.

Conclusion

Managing conflicting stakeholder priorities is a core design skill. students should remember that different stakeholders often want different things, and those wants can conflict. The job of the designer is to capture needs carefully, identify where conflict exists, translate needs into engineering requirements, and use evidence to make balanced decisions. In Design, Materials and Manufacturing 2, this approach helps turn broad demands into practical solutions that can actually be made, tested, and used. ✅

Study Notes

A stakeholder is anyone affected by a design decision.
Stakeholder priorities often conflict because one improvement can cause another requirement to worsen.
User needs are what the user wants in daily use.
Societal requirements include safety, accessibility, sustainability, and legal rules.
Engineering requirements are measurable statements that guide design and testing.
A trade-off is a compromise where improving one feature may reduce another.
Evidence from surveys, tests, and observation helps designers make fair decisions.
A decision matrix can compare options using weighted criteria.
Vague ideas like “strong” or “comfortable” should be translated into testable requirements.
Good requirements are clear, specific, measurable, realistic, and testable.
Prototypes help check whether a design really balances conflicting priorities.
Managing stakeholder conflict is a central part of Requirements and Stakeholders and connects directly to materials selection and manufacturing decisions.