PONOPT FIELD NOTES · Наука, образование и сообщество

The City as a Living Lab: Testing Innovation with Universities and Residents

Urban living labs test real innovations with universities and residents before public money is spent. Includes setup stages, data risks, and a launch checklist.

An urban living lab is a structured way to test a product, service, or policy with real users in a real neighbourhood before a city commits public money. The strongest models pair a municipality with a university and residents from the start, run time-boxed pilots through agreed stages, and treat most results as learning rather than victory. Decide in advance what you want to learn, who owns the data, and what counts as success. Begin with a narrow problem, explicit criteria, and an honest exit rule for every experiment.

Key takeaways

  • A living lab is a real-life testing environment, not a building: it works when citizens, government, industry and academia co-create and validate an idea where people actually live and work.
  • A university partner supplies research discipline, measurement and students, while residents provide lived experience and honest adoption signals that no dataset can replace.
  • Structure testing in stages — idea verification, co-design workshops, prototyping, then a time-boxed live pilot with agreed feedback rules — so failures surface while they are still cheap.
  • Settle data ownership, consent and decommissioning in writing before installation; one promising health pilot stalled over who could access the data it generated.
  • Expect most pilots not to scale: a veteran municipal lab reports roughly 85% of projects failing, usually on commercialisation and marketing rather than technology.
  • Aim beyond novelty: documentation and organizational learning, more than policy transfer, are what let a proven experiment spread to other districts and cities.

What a living lab is — and why a city would run one

A living lab is not a laboratory in the usual sense. ENoLL, the European network that certifies many of the world's active labs, defines the model as user-centred, open innovation ecosystems built on systematic user co-creation in real-life communities and settings. Instead of isolating a problem behind glass, the city, its residents and partners test and refine an idea in the place where it will actually be used: a street, a housing block, a university campus, a harbour.

The model rests on the quadruple helix: citizens, government, industry and academia participate as equal partners in the same process. Public authorities keep experiments aligned with policy priorities; residents contribute lived experience; industry and academia supply technical capability and research methods. The concept traces back to a Massachusetts Institute of Technology professor who designed a purpose-built home to study how people actually interact with technology, but the modern living lab has moved that kind of testing into everyday environments.

  • Testing happens in a real-life setting, not inside an isolated facility.
  • Users shape the solution through co-creation rather than accepting it afterwards.
  • Partners from the four helix groups design and carry responsibility jointly.
  • The cycle includes evaluating effects and feeding results back into decisions.

Why the university–resident pairing is the engine, not an accessory

A city that simply contracts a vendor rarely gets an honest answer about whether a technology works in its conditions. A university partner brings methodological discipline: defined hypotheses, measurement, evaluation, and students who can run fieldwork at low cost. Residents bring the messy, real-world conditions — habits, weather, distrust, maintenance realities — that a spreadsheet cannot capture. Solutions designed without at least one of these groups tend to fail when they meet the real world.

Successful partnerships span very different scales. Western Sydney University built the Penrith Sustainable Innovation Community with developer Stockland as a testbed for transport, digital building technologies, sustainable materials and climate-sensitive design, involving students in planning and project-based learning. In Istanbul's Başakşehir district, Bahçeşehir University sat on the founding board of a municipal living lab from day one, alongside industry and the municipality. Several European universities now coordinate their separate urban experimentation spaces into a distributed living lab so that a proven approach in one campus can be adapted elsewhere.

  • University: research design, evaluation, instrumentation, access to students and labs.
  • Municipality: problem definition, permits, data access, procurement pathways, public trust.
  • Residents: lived-experience input, co-design, real usage and feedback.
  • A dedicated coordinator who owns the timeline, feedback loops and reporting.

Designing the test: stages before you ever scale

A living lab succeeds when the testing is disciplined rather than improvised. Practitioner guidance, including the Urban Living Lab Way of Working developed by the Amsterdam Institute for Advanced Metropolitan Solutions, treats an experiment as a structured sequence — roughly eight key activities across four interconnected phases — rather than an open-ended co-working space. In Başakşehir's practice, a promising idea moves through defined stages: idea verification, stakeholder workshops, prototype events, then structured real-environment testing with agreed feedback-collection procedures and timeframes.

This sequencing is what turns a living lab into a risk-reduction tool. At the start you commit almost no money; each stage is a decision gate. Only ideas that clear early verification and co-design earn a real-world pilot with a defined duration and known success criteria. That disciplined funnel lets both the city and the entrepreneur discover what fails while failure is still cheap, so the city does not pay for an expensive collapse at full-scale deployment.

  • Idea verification: does the problem and proposed fix make sense locally?
  • Co-design workshop: refine scope with residents and domain experts.
  • Prototype: build the cheapest credible version.
  • Live pilot: fixed period, agreed metrics and feedback rules.
  • Review and replicate only on compelling evidence; otherwise stop.

Governance, consent and data — the part most cities underestimate

The hardest problems in a living lab are rarely technical. Who owns the data generated during a real-environment test? Who can consent on behalf of residents, and what happens to a household's data when a pilot ends? Başakşehir's experience is instructive: a compact device that measured dozens of health parameters from a single drop of blood was technically impressive and used by tens of thousands of people over several years, but a dispute over who could access the health data it helped generate proved unresolvable and contributed to the project's end.

Agreements over data ownership, privacy and decommissioning should be signed before the first sensor is installed. In many jurisdictions, processing data about identifiable people in public space carries specific legal duties, and permission to use a space is not the same as permission to collect data about its users. This is general guidance, not legal advice: consent forms and data-sharing terms should be reviewed by a qualified lawyer familiar with your jurisdiction.

  • Define data ownership and reuse rights in writing before launch.
  • Identify the lawful basis and consent model for each data stream.
  • Decide how long data is kept and how it is destroyed after the pilot.
  • Establish what happens if a partner leaves or a project is discontinued.

Why most pilots don't scale — and how to design for durability

The honest statistics are sobering. Over more than a decade, Başakşehir supported roughly 150 startups and projects, and its leadership reports that around 85% did not become lasting successes. The common failure is rarely the product: teams can build working platforms but then struggle with marketing, sales and a sustainable business model. Living labs are often not commercially oriented, and small ventures in emerging markets face thin seed funding and weak venture capital, so technically strong founders drift into outsourced work.

A city can design around this. Pair technical validation with a realistic route to market from the start, involve commercial partners early, and decide in advance whether the city itself will become a first customer or investor. Durability also means the lab outlives any single experiment or funding cycle: training residents, running competitions and maintaining relationships build a population of people who know how to propose, test and defend an idea. Otherwise the lab becomes a project that dies when the grant ends.

From local experiment to systemic change

The ultimate test of a living lab is not the novelty of its pilots but whether successful experiments become routine policy, procurement or infrastructure. Researchers studying urban experimentation warn of a 'pilot paradox': successful experiments do not automatically translate into systemic transformation, because organizational structures and cultures differ too much between cities. What matters most is organizational learning — knowledge that travels from person to person, not just into reports. One example cited by practitioners is a bus technology successfully adopted elsewhere not through policy transfer but through engineers meeting counterparts face to face.

Documenting each pilot's context, method, results and the conditions that made it work is what enables replication. Publications such as the AMS Urban Living Lab handbook describe a multilevel framework and key activities for moving from isolated experiments to systemic change. A solution proven on one campus or in one district should not remain local; it becomes a template other districts and cities adapt, which is precisely how a living lab pays back its cost to the public.

Urban Living Lab Launch Scorecard

Work through this checklist before installing a single sensor or launching your first pilot. Each line is a control point with an owner and a written confirmation, so the lab starts with partnerships, ethics and governance in place rather than improvised.

  1. A narrow urban problem and a measurable desired outcome are stated in writing.
  2. Quadruple-helix partners are identified: a university, the relevant municipal department, an industry or vendor voice, and residents.
  3. A dedicated coordinator with budget and authority owns timelines and feedback loops.
  4. A real-life site where the solution will actually be used is chosen and permission to run the experiment is obtained.
  5. A memorandum defining goals, roles and decision rules is signed by all partners.
  6. Stages are agreed: idea verification, co-design, prototype, and a time-boxed live pilot.
  7. Success criteria and an honest exit rule are agreed in advance for every experiment.
  8. Data rights, consent model, retention periods and deletion procedures are settled in writing.
  9. A lawyer familiar with the jurisdiction reviews consent forms, data-sharing terms and privacy policy.
  10. A path to adoption is defined: who will be the first buyer or investor, and how results reach procurement or infrastructure.
  11. A plan exists for resident training and for sustaining the lab beyond the current funding cycle.

Questions people ask

What is the difference between a living lab and a regulatory sandbox?

A living lab is a real-life environment for co-creating and testing an innovation with residents, universities, government and industry; its purpose is to find out whether a solution works with real users in real conditions. A regulatory sandbox is a special legal regime that temporarily exempts a project from certain rules so it can be tested lawfully. The two often combine: the lab provides the place and methodology of the test, while the sandbox provides the legal permission. Many countries, including Russia, have their own mechanisms for experimental legal regimes, and their conditions change, so verify the current rules in your jurisdiction.

How do we recruit and keep residents, rather than only motivated activists?

The people who show up first are usually energetic and sustainability-minded, but they are not representative of everyone who will eventually use the solution. To broaden participation without losing the depth of early co-creation, first understand why many residents do not engage and what would make them want to join. Practical measures include involving users at every stage from needs identification to implementation and scaling, offering clear incentives, holding meetings at convenient times and places, and honestly reporting how resident input shaped the decision. Consider co-design and participatory formats, and design scenarios that also benefit people who will never own the flagship technology involved.

Should the lab be run by the city or by the university?

There is no single answer; it depends on resources and objectives. A municipally anchored lab stays agile and close to procurement but may lack commercial and research expertise. A university brings methodology and students but may struggle to access city territory, data and decision pathways. A practical solution is to separate roles under one coordinator: the administration opens the site and the route to adoption, the university designs and evaluates the experiment, and residents and industry join the co-design. Some cities create regional platforms that link research institutions, companies and citizens, which spreads coordination cost and strengthens legitimacy.

Isn't a failed pilot a waste of public money?

Not if the experiment is designed as learning. The purpose of a lab is to surface failure while it is cheap, before an expensive full-scale rollout. Value lies not only in the pilot's result but in the organizational knowledge the team gains along the way. Researchers describe a 'pilot paradox': even successful experiments often fail to become systemic change, because what must travel between cities is knowledge and enabling conditions, not just the technology. Define in advance what you want to learn and document the conditions of success, so even a 'failure' pays back through clarity about what does not work and why.

What data and privacy questions should we settle before launch?

Start with four: who owns the data collected in the real environment and on what terms it can be reused; what is the lawful basis and consent model for each data stream; how long data is retained and how it is destroyed after the pilot; and what happens if a partner withdraws or the project is discontinued. Remember that permission to use a site is not permission to collect data about its visitors. Because data-protection rules differ by jurisdiction, treat these as general starting points and have consent forms and data agreements reviewed by a qualified local lawyer.

Sources and further reading

Sources were checked when this page was generated. Confirm changing dates, rules and prices with the original publisher.

  1. European Network of Living Labs — Who We AreEuropean Network of Living Labs (ENoLL)
  2. From Happiness to Innovation: The Başakşehir Living Lab StoryEuropean Network of Living Labs (ENoLL)
  3. Learning in the Real World with Urban Living LabsAmsterdam Institute for Advanced Metropolitan Solutions (AMS Institute)
  4. The Urban Living Lab Way of Working HandbookTU Delft / AMS Institute
  5. 'Living Lab' Showcases Sustainable NeighbourhoodWestern Sydney University
  6. The ULALABS project lays the foundations for a European distributed Living LabUniversitat Autònoma de Barcelona
  7. Университетские кампусы как живые лабораторииUrbis et Orbis, Российско-Армянский университет