BENV0141 Chap.6 Inclusive Smart-Energy Innovation
Inclusive Smart-Energy Innovation
Inclusive Smart-Energy Innovation treats vulnerability as a relationship between a person and the demands of a system. A product or tariff may exclude through cost, tenancy, interface, equipment, data, language, health or support requirements. Human-centred innovation begins with needs discovery, moves through co-creation and testing, and allows evidence to change the service.
Trial success must be interpreted cautiously when free equipment or intensive support removes barriers that will return in a live market.
What this chapter covers
- 01
Relational vulnerability
- 02
Needs discovery
- 03
Co-creation
- 04
Prototype and trial
- 05
Ability and willingness
- 06
Scalable protection and support
Worked example · free
Develop an inclusive heating-service hypothesis
- 2Treat the user description as an evidence hypothesis, not a universal persona.
- 2Audit tenancy, equipment, payment, digital, language and support demands.
- 2Reduce requirements through simple controls, assisted access and cost protection.
- 2Define recruitment, outcome and failure tests before scaling.
Key terms
- Relational vulnerability
- Vulnerability created or intensified by the fit between circumstances and system demands.
- Co-creation
- Developing a service with affected people rather than only for them.
- Market access
- The practical ability to obtain and sustain a service under ordinary conditions.
Inclusive Smart-Energy Innovation FAQ
Why can a successful trial mislead?
Trials may provide free devices, recruitment help, technical support or temporary protections that will not exist at scale. Satisfaction under those conditions does not prove affordability, ordinary access or market viability.
What is relational vulnerability?
It locates vulnerability in the interaction between circumstances and system requirements. This avoids treating a demographic label as a fixed deficit and reveals which service demands can be redesigned.
How should a persona be used?
Use it as an evidence-grounded design hypothesis that organises needs and constraints. Validate it with participants, avoid exceptional stereotypes and do not treat one invented character as representative proof of a whole population.
What is the difference between ability and willingness?
Ability concerns resources, permissions, equipment and support needed to participate. Willingness concerns whether the offer is acceptable given trust, control, privacy and priorities. A household may value the outcome yet lack ability, or be able to join and reasonably decline.
Why should discovery precede a product choice?
Starting with a preferred device narrows the problem and can misread rejection as user resistance. Needs discovery identifies the valued service, constraints and existing practices, allowing technology, tariff, business model and support to be redesigned together.
What should a pilot risk register contain?
Name the mechanism, affected group, likelihood or signal, mitigation, responsible actor and escalation route. Include unaffordable purchase, service failure, loss of control, unequal data access, exclusion and unfair distribution of system costs.
When is co-creation meaningful?
Participants must be able to change requirements, safeguards or the service proposition, not merely react to a finished concept. Record what decision each activity informs and explain how conflicting needs or negative evidence alter the next design stage.
How should drop-out be interpreted?
Treat departure as evidence about the interaction between the offer and participant circumstances, not simply missing data or lack of interest. Record when people leave, the service demand or consequence involved and whether redesign, support or protection could have changed the outcome. Compare drop-out with recruitment and temporary trial conditions. Feed the finding into the next design decision.
Assessment move
Revise inclusive innovation as a learning cycle rather than a launch sequence. Begin with the problem space and the service outcome. Record the assumptions made about users, housing, payment, technology and support. Convert each assumption into a question that discovery or co-creation can test. Use personas only after reviewing evidence, and label them as hypotheses.
During prototyping, separate ability from willingness and access from benefit. A participant can value an outcome yet lack permission, equipment or funds; another can join but reasonably reject data or control risks. For trials, document every temporary resource that removes a market barrier and ask how it will be sustained.
Build a risk register with mechanism, affected group, mitigation, responsible actor and escalation route. Include product failure, unequal data access, unaffordable purchase and unfair system-cost distribution. Finish by naming what the service cannot solve, such as poor fabric or low income, and connect users to actors with authority over those conditions.
A defensible innovation proposal remains open to redesign when evidence contradicts its original concept. For practice, take one proposed service and write an assumption ledger covering need, access, operation, payment, trust and benefit. Mark which assumptions come from evidence and which remain hypotheses.
Design one discovery activity and one live-use test for the highest-risk assumption, stating the decision each result could change. Audit recruitment for who is absent and list every temporary trial resource that would disappear at scale. Finally, rewrite the concept after a negative result rather than defending the original product.
This exercise trains evidence to change design and keeps inclusion attached to ordinary delivery, not exceptional pilot support.