Sustainability · Strategic UX and service design
Sustainable design did not need another manifesto. It needed proof.
GreenPixel is a community-led award platform concept. Designers already agreed sustainability mattered; what they lacked was shared criteria and a reason to document the decision. GreenPixel gives them both: criteria they can apply, and proof they can show.
Outcome
A tested concept. Research reframed the problem, from raising awareness to enabling participation. Testing then established what the platform had to prove before a designer would risk submitting real work to it.
Role
Research and strategy lead
Contribution
Desk research and survey synthesis, barrier and stakeholder framing, the strategic pivot, prototype development, translation of test feedback into product changes, and the explanatory video and project poster
Team
Mariana Bozano, Palida Pongmekin, Oluwatosin Kazeem and Duco Boomsma
Duration
Seven weeks · 2025
Context
Master Digital Design Playground project, with guidance from Faraday Digital Agency
Methods
Desk research, survey and interviews, card-sorting workshop, business-model mapping, interactive prototyping, moderated think-aloud sessions and intercept feedback testing
01 · Friction
Good intentions lose when teams cannot define, prove or defend the work.
Almost every designer I spoke to agreed that sustainability mattered. Very few could point at a decision in their last project where it had changed anything. That gap — between agreement and practice — is the problem GreenPixel set out to address.
Delivery pressure
Sustainability is the first item cut when a deadline tightens, because it rarely has a named owner on the sprint board.
Client priorities
Briefs are written around conversion, launch dates and features. Environmental cost is not in the acceptance criteria.
Ambiguous language
“Sustainable design” covers carbon, accessibility, longevity, data and attention at once, so teams cannot agree what is being asked.
Hard to prove
A designer can make a careful decision and have no way to show it mattered afterwards.
No organisational reward
Effort that cannot be demonstrated does not travel into reviews, pitches or portfolios.
Sustainability is rarely rejected. It is quietly deprioritised.
02 · Evidence
The barrier was not awareness. It was method, examples and a reason to document the effort.
I led the desk research and the survey synthesis. The point was not to prove that designers care about sustainability — that was already visible. It was to find out precisely where intention stopped converting into practice.
n=20
designers answered the closed survey questions on familiarity and practice
n=13
of those also wrote free-text answers about what blocked them in real projects
Familiarity with sustainable digital design
- Never heard of it, 2 of 20 respondents
- Heard of it, 10 of 20 respondents
- Basic understanding, 4 of 20 respondents
- Familiar, 3 of 20 respondents
- Actively applying it, 1 of 20 respondents
Closed questions answered by 20 designers. Percentages are not used at this sample size — the counts are reported as they were collected.
The decisive number
Separately from the response counts above, 13 of the 20 respondents placed themselves in the same position: interested in sustainable design, but not yet applying it.
A single respondent described themselves as actively applying it. That imbalance, rather than any lack of goodwill, set the direction of the project.
What card sorting actually resolved
We printed every candidate guideline the team had gathered and asked participants to group them. The value was not the groups themselves. It was watching where people hesitated.
Ideas overlapped heavily, and the same intention appeared in three different vocabularies. Participants argued about wording far more than about substance, which told us the language was doing the blocking.
Sorting collapsed that sprawl into themes, and those themes became the lenses the product now uses. The workshop produced more than twenty guidelines, which only became usable once they sat under a small number of named categories.
It also produced the finding that redirected the project. Participants could organise criteria willingly and still not describe why they would ever submit their own work against them. Criteria clarified the standard. They did not create participation.
Evidence
Interpretation
Design decision
Evidence
13 of the 20 respondents were interested in sustainable design but not yet applying it
Interpretation
The blocker was not belief. It was the absence of a method and of permission to spend time on it
Design decision
Give designers a lens they can apply, not a position to agree with
Evidence
One respondent described themselves as actively applying it
Interpretation
There was almost no visible practice to learn from, so each team started from zero
Design decision
Publish recognised work as reusable, inspectable examples
Evidence
Card sorting produced heavy overlap and inconsistent language across ideas
Interpretation
Sustainability was too broad to act on as a single instruction
Design decision
Group the workshop output into five named lenses instead of one long list
Evidence
Participants could not describe what a good outcome looked like
Interpretation
Without shared criteria, effort could not be compared, defended or rewarded
Design decision
Define criteria per entry category and require reasoning with each entry
Evidence
Business-model mapping showed the proposition only held with agencies, jury members and partners in it
Interpretation
A designer-only tool had no source of legitimacy and no reason for an organisation to care
Design decision
Design for an ecosystem rather than a single user
Mapping the model early kept the team honest about who the proposition had to work for. Designers supply the work, agencies decide whether the time is defensible, jury members lend judgement, and partners lend legitimacy. Removing any one of them collapsed the reason to participate — which is why a designer-only tool was never going to be enough.
The research did not tell us what to build. It told us what the product would have to earn.
03 · Finding the why
Before designing the platform, we needed a reason for anyone to take part.
This was not open ideation. It was a structured attempt to connect user motivation, organisational value and platform behaviour — and to rule out the directions that could not carry all three.
Four tensions the board kept returning to
Why would a designer participate at all, when the work is already delivered?
Who validates that a claim about sustainability is credible?
What makes the effort visible to anyone outside the project team?
What does good actually look like, in a form that can be compared?
Directions we ruled out
The guideline system
Guidelines explained sustainable design well, but nothing in them created a reason to document the effort or share it. That made them necessary and not sufficient — so they were kept and given somewhere to lead, rather than discarded with the directions above.
This is the decision the rest of the product is built on: the guideline system became Improve, and the award became Prove.
Every direction we ruled out failed on the same question: who has a reason to act on it?
04 · Pivot
Guidelines could explain sustainable design. Recognition gave people a reason to act.
GreenPixel did not become an award platform because awards looked attractive. It became one because recognition answered the specific barriers the research had surfaced.
The brief
A manifesto and a guideline hub that explain sustainable digital design and rely on intrinsic motivation
The reframe
A community-led award that makes effort visible, comparable and worth documenting, with guidelines retained as the working half
The diagram reads from the outside in. Around the edge sit the barriers the research had already established: the assumption that this is a developer concern, time pressure, ambiguity, the difficulty of measuring impact, and the absence of shared criteria.
The inner petals are the levers we could actually design for — labelled Self, Community, Reinforcing and Recognition on the board.
Read together they describe a motivation loop rather than a feature list. Self is the designer's own standard, Community is the peer group that makes that standard visible, Recognition is the moment the effort is named, and Reinforcing is what makes the loop repeat rather than run once.
Recognition is also where the platform borrows credibility it cannot generate alone. A jury and named partners supply the legitimacy that turns a personal claim into something an agency can defend to a client.
Measurement becomes meaningful when effort is visible, comparable and recognised.